ICE Tube Clock Firmware Comparison
Moderators: adafruit_support_bill, adafruit
Please be positive and constructive with your questions and comments.
- Wilcoxon
- Posts: 1
- Joined: Sat Apr 27, 2019 4:05 am
Re: ICE Tube Clock Firmware Comparison
Do you recommend always keeping the firmware up to date, Jarchie?
- jarchie
- Posts: 615
- Joined: Sun Jun 24, 2012 2:16 pm
Re: ICE Tube Clock Firmware Comparison
I guess the short answer is "no."Wilcoxon wrote:Do you recommend always keeping the firmware up to date, Jarchie?
The long answer?
The last update I made to my firmware was several years ago. I consider the firmware to be a finished product at this point, and do not intend to make any more changes. I will probably only update the code if problems are found (e.g., if bugs are found or if the project fails to compile in some future version of the avr-gcc compiler).
I would suggest looking at the current list of features in the firmware/README file. If there's a new feature you want, then maybe installing the latest version is worthwhile. Consider also that upgrading the firmware might be a fun project (or not fun, depending on your temperment). Use your own judgement.
Anyway, as always, good luck and happy hacking!
- nix_clk_dd
- Posts: 38
- Joined: Tue May 21, 2019 2:15 pm
Re: ICE Tube Clock Firmware Comparison
Hi John,
I'm going to build an Ice Tube clock soon. I found several kits online, but I like the improvements you made and it would be a cool experience to source the parts from DigiKey and OSHPark. I would say I'm a beginner, but I've successfully built a nixie tube clock from a kit.
There are a couple questions that I have.
1. If I don't currently have anything to write the firmware to the microcontroller. would the flashing service from DigiKey work? Upon placement of an order of the ATmega328p, I can send them the firmware.
2. Do you have a parts list of the components modified from the original board and everything needed to take advantage of all the improvements (minus maybe the GPS functionality)? I'm almost certain I'm still missing things after reading your github README files.
Thank you so much! I know this is a lot to ask.
I'm going to build an Ice Tube clock soon. I found several kits online, but I like the improvements you made and it would be a cool experience to source the parts from DigiKey and OSHPark. I would say I'm a beginner, but I've successfully built a nixie tube clock from a kit.
There are a couple questions that I have.
1. If I don't currently have anything to write the firmware to the microcontroller. would the flashing service from DigiKey work? Upon placement of an order of the ATmega328p, I can send them the firmware.
2. Do you have a parts list of the components modified from the original board and everything needed to take advantage of all the improvements (minus maybe the GPS functionality)? I'm almost certain I'm still missing things after reading your github README files.
Thank you so much! I know this is a lot to ask.
- jarchie
- Posts: 615
- Joined: Sun Jun 24, 2012 2:16 pm
Re: ICE Tube Clock Firmware Comparison
Sorry I missed the notification of this post in my email... I hope this doesn't come too late.
There are some compile time options that you wouldn't be able to change if you go this route, such as Adafruit vs xmas style buttons. Check out the hardware/config.h file for a description of the compile-time options. The defaults are probably fine for most people, and most of the options are for the hardware configuration.
My suspicion is that it might be cheaper (and perhaps more fun) to program the chips yourself. If you go that route, the USBtinyISP is what I find easiest.
As far as GPS is concerned, you might as well keep the default support in the firmware (config.h). The clock will detect that there is no GPS attached and everything will work fine.
Hope that helps. And if you run into problems or have more questions please let me know. Happy hacking!
I've never tried it, but there's no reason why it wouldn't work. I can post a binary somewhere. And they would also need to program the fuse bits, lock bits, and eeprom as well as the flash program memory.nix_clk_dd wrote:1. If I don't currently have anything to write the firmware to the microcontroller. would the flashing service from DigiKey work? Upon placement of an order of the ATmega328p, I can send them the firmware.
There are some compile time options that you wouldn't be able to change if you go this route, such as Adafruit vs xmas style buttons. Check out the hardware/config.h file for a description of the compile-time options. The defaults are probably fine for most people, and most of the options are for the hardware configuration.
My suspicion is that it might be cheaper (and perhaps more fun) to program the chips yourself. If you go that route, the USBtinyISP is what I find easiest.
It sounds like you might want my modified boards. Check out the hardware/README, especially the "Collecting the Parts" section. The components that I bought years ago are all in the hardware/BOM.csv file. (BOM = bill of materials)nix_clk_dd wrote:2. Do you have a parts list of the components modified from the original board and everything needed to take advantage of all the improvements (minus maybe the GPS functionality)? I'm almost certain I'm still missing things after reading your github README files.
As far as GPS is concerned, you might as well keep the default support in the firmware (config.h). The clock will detect that there is no GPS attached and everything will work fine.
Hope that helps. And if you run into problems or have more questions please let me know. Happy hacking!
- nix_clk_dd
- Posts: 38
- Joined: Tue May 21, 2019 2:15 pm
Re: ICE Tube Clock Firmware Comparison
Thanks for the response!
How does the microcontroller actually make the connection to the programmer? I don't have any experience with Arduino devices or flashing chips. Some images I've seen online show the chips on a breadboard connected to the programmer but I don't seen anything detailing this in the documentation.
Once thing I noticed when searching for the crystal oscillator is that there are two versions of the Abracon AB38T-32.768KHZ
https://www.digikey.com/short/p4ww9h
All else being equal, here are the differences:
AB38T-32.768KHZ
Frequency Tolerance: ±20ppm
Operating Temperature: -10°C ~ 60°C
AB38T-32.768KHZ-B7
Frequency Tolerance: ±15ppm
Operating Temperature: -20°C ~ 70°C
I wonder if these differences would result in slightly better timekeeping. The B7 is only $0.04 more, so it might be the obvious choice unless it somehow interferes with your automatic rate correction code.
Thanks again!
I might go that direction. The USBtisyISP is easy enough to build, but once again I feel like I'm missing something. :)jarchie wrote: My suspicion is that it might be cheaper (and perhaps more fun) to program the chips yourself. If you go that route, the USBtinyISP is what I find easiest.
How does the microcontroller actually make the connection to the programmer? I don't have any experience with Arduino devices or flashing chips. Some images I've seen online show the chips on a breadboard connected to the programmer but I don't seen anything detailing this in the documentation.
That CSV is VERY helpful.jarchie wrote: It sounds like you might want my modified boards. Check out the hardware/README, especially the "Collecting the Parts" section. The components that I bought years ago are all in the hardware/BOM.csv file. (BOM = bill of materials)
Once thing I noticed when searching for the crystal oscillator is that there are two versions of the Abracon AB38T-32.768KHZ
https://www.digikey.com/short/p4ww9h
All else being equal, here are the differences:
AB38T-32.768KHZ
Frequency Tolerance: ±20ppm
Operating Temperature: -10°C ~ 60°C
AB38T-32.768KHZ-B7
Frequency Tolerance: ±15ppm
Operating Temperature: -20°C ~ 70°C
I wonder if these differences would result in slightly better timekeeping. The B7 is only $0.04 more, so it might be the obvious choice unless it somehow interferes with your automatic rate correction code.
Thanks again!
- jarchie
- Posts: 615
- Joined: Sun Jun 24, 2012 2:16 pm
Re: ICE Tube Clock Firmware Comparison
Our discussion might be getting a bit off-topic for an alternative firmware thread, so I'm replying here.
Please be positive and constructive with your questions and comments.