Prometheus Alarm Clock

A few updates. I finally selected the Nixie Cathode clock set-up I will use for this project. I was looking around for some viable kits. I looked at prices, set-up, Arduino Compatibility (more on this later), and Serial communications capabilities. First, because I am on a college campus, I have limited access to hardcore-DIY hardware tools such as solders, power sources, and spare breadboards. Therefore, I needed something that would require minimum set up to start. At the same time, because I am programming the main clock in Python 3, it would be great if I could use Python to communicate various commands to the nixie clock from the RPi (such as updating the clock using NTP, or flashing the display to signify a successful alarm set).

Next, I wanted to make sure the clock would be compatible with the Arduino specification. This is because I wanted to take advantage of a Python Library for the Raspberry Pi called NanPy. This library allows you utilize the Arduino controller as a "slave" via I2C. Or in other terms, this would allow me to run the nixie clock firmware directly on the Pi, and communicate the directions to the various components on the nixie clock it through serial usb > Arduino > nixie tube interfacing components > nixie tubes. This was necessary because I don't actually want to run a clock independent from my main clock program on the Pi. Using this method, the main clock program can directly modify the variables such as the display time, flashing the display, turning the clock nixie display on/off because the program is running on the Pi.

I looked at many different clocks, and talked to their manufacturers Although I did not end up buying their product, I feel it is right to mention their names since they were so helpful in my journey to find the right clock. The first clock I was looking at was the Complete Nixie Clock Kit Bundle from PV Electronics based in the U.K. Pete from customer support was very helpful in helping me understand their product. Getting this, I would have to assemble everything scratch, and the only way to communicate the Pi with the clock would be to to "hack" the built in GPS signal, which was designed to take input from a GPS time module (sold by PV Electronics as well) which gave the clock information about location information.

Next I looked at the kits sold by NixieShop.com. Petro the brand and shop owner was very helpful in getting me information on his clocks (and for anyone trying to work on a similar project as mine, his product is perfect as well). His clocks are pre-assembled and shipped as a complete product. Furthermore, NixieShop has a variety of products, and he has very high reviews on eBay. The clock provided everything I was looking for (Arduino compatibility, moddable firmware that could communicate via serial usb to the Pi). The only thing that made me switch to my final choice was price (But even that was only about a $30 difference, plus Petro's product all come with cases which mine does not).

The final clock kit I looked at was GRA and AFCH's kits. Their NCS314 Shield Kit came with everything I was looking for, and also was basically a shield for the Arduino rather than a Arduino compatible kit. Furthermore, (unlike other models on the market) the model uses full static displaying mode rather than multiplexing mode (all digits light simultaneously rather than 1 by 1, which makes for easier variable programming). Next, I also appreciated that they uploaded their schematics and firmware openly on on Github. (https://github.com/afch) Finally, they sold the whole kit (minus the Arduino itself) for $90, which came out to be $110 including shipping which was a the biggest selling point for me. Buying the Arduino separately, the whole kit came out to be $140.

In other news, I managed to draw up a basic implementation chart for the whole clock, which I will upload to the Github page.

Happy Halloween everyone.

Oh boy, it seems like I REALLY have to start from the basics. My school recently switched from their own custom ISP services to adopt the eduroam standard, which allows anyone from member universities to continue using their school login to have access to the secured WiFi of any other school while they are there.

While I am sure this has many benefits, the school disabled ssh and VNC access on the Guest Accounts for security reasons, and I was therefore forced to configure my Pi to connect to eduroam.

Although the school provided a shell script, which is supposed to automate PEM key authentication, setting up the wpa_supplicant and /etc/network/interfaces files, the shell script failed to set up my Pi to work with eduroam.

Therefore, I spent all weekend discovering a solution to do connect the Pi to the Internet. If anyone else is having the same problem, I suggest going to the project github page, where I have posted detailed directions for how I got it to work.

Although tedious, this was a great experience as it allowed me to dive into very Linux-y tools, concepts, and methodologies such as NetworkManager, PEM authentication, and different models of network encryption.

Check on Github for the source code by hberg32. His project has inspired mine, and I am definitely planning to use at least some of it.

He compiled some of his Python into PYC files, so I need to figure out a way to decompile this so I can view the source.

In a frenzy to gather information about nixie tubes, different language supports, trying to get my Pi to log into my school's encrypted network.