Ice tube LEADING MINUS SIGN IS ON W/REV 2.2 FIRMWARE
Posted: Wed May 10, 2023 4:20 pm
Hello EVERYONE, I had recently written in with an issue with Xmas-Ice-Tube clocks that were being restarted by the watchdog timer every 8 seconds
viewtopic.php?t=198641]
\
The cause of the problem was that I had inadvertently turned on the external clock module when I recompiled the code — so now that is off, the clocks start up and run normally. However, I have a second problem that I do not have an answer to. It seems like go with the re-compiled code that there is a negative sign in front of the clock data and it's always on. I scoured the Internet with Google today looking for an answer. I found none. I read through the code today, I could not find anything to turn negative sign on. Also, I looked at some of the data sheets for IV – 18 tubes cannot tell which pin controlled the negative sign.
To Confirm the behavior, I went to the GitHub repository and download the latest firmware and used it to compile new firmware that I then used my USBtinyISP to program 2 ATMEGA chips — the negative sign is still on on both clocks.
Just to be clear, the clocks that I built all used version 2.2 firmware on revision D boards that I ordered from OSHPark.
So I ask the experts here what could cause the leading negative sign to be turned on and what should I do to get it turned off.
Thanks for any help you may offer,
Johnny Brian
Modules turned on are:
#define XMAS_DESIGN
#define TEMPERATURE_SENSOR
#define XTAL_TURNOVER_TEMP 400 // deg C / 16
#define XTAL_FREQUENCY_COEF 34 // -ppb / (deg C)^2
#define BDAY_ALARM_MONTH 1
#define BDAY_ALARM_DAY 2
#define OCR0A_MIN 20
#define OCR0A_SCALE 11
#define OCR0A_MAX OCR0A_MIN + 10 * OCR0A_SCALE
#define SUBDIGIT_MULTIPLEXING
#define VFD_TO_SPEC
#define OCR0A_VALUE 192
#define AUTODRIFT_PRELOAD 255
#ifdef EXTERNAL_CLOCK
#define AUTODRIFT_SLEEP 1600 // ~5 ppm
#else
#define AUTODRIFT_SLEEP 2800 // ~2.8 ppm
#endif
viewtopic.php?t=198641]
\
The cause of the problem was that I had inadvertently turned on the external clock module when I recompiled the code — so now that is off, the clocks start up and run normally. However, I have a second problem that I do not have an answer to. It seems like go with the re-compiled code that there is a negative sign in front of the clock data and it's always on. I scoured the Internet with Google today looking for an answer. I found none. I read through the code today, I could not find anything to turn negative sign on. Also, I looked at some of the data sheets for IV – 18 tubes cannot tell which pin controlled the negative sign.
To Confirm the behavior, I went to the GitHub repository and download the latest firmware and used it to compile new firmware that I then used my USBtinyISP to program 2 ATMEGA chips — the negative sign is still on on both clocks.
Just to be clear, the clocks that I built all used version 2.2 firmware on revision D boards that I ordered from OSHPark.
So I ask the experts here what could cause the leading negative sign to be turned on and what should I do to get it turned off.
Thanks for any help you may offer,
Johnny Brian
Modules turned on are:
#define XMAS_DESIGN
#define TEMPERATURE_SENSOR
#define XTAL_TURNOVER_TEMP 400 // deg C / 16
#define XTAL_FREQUENCY_COEF 34 // -ppb / (deg C)^2
#define BDAY_ALARM_MONTH 1
#define BDAY_ALARM_DAY 2
#define OCR0A_MIN 20
#define OCR0A_SCALE 11
#define OCR0A_MAX OCR0A_MIN + 10 * OCR0A_SCALE
#define SUBDIGIT_MULTIPLEXING
#define VFD_TO_SPEC
#define OCR0A_VALUE 192
#define AUTODRIFT_PRELOAD 255
#ifdef EXTERNAL_CLOCK
#define AUTODRIFT_SLEEP 1600 // ~5 ppm
#else
#define AUTODRIFT_SLEEP 2800 // ~2.8 ppm
#endif