- Posts: 1122
- Karma: 1
- Thank you received: 120
Modular clock problems
1 week 3 days ago #12453
by Ian
Replied by Ian on topic Modular clock problems
Your analysis is right:
The combination "Found I2C slave (Nixie clock) (default) 105" and "Communicating with: Clock not found!" means that the WiFi module knows that there is a clock there, but does know know how to communicate with it. The status string also confirms this upper case letters means that the thing we are referring to is "on":
"W" - WiFi is connected
"N" - NTP time is valid
"S" - The SPIFFS file system was mounted
"U" - OTA Update is possible
"A" - Authentication for the web configuration is turned on
"d" - Debug mode is off
The "Display time" means that the NTP for some reason got an answer back that it could not interpret. I'm looking at this now, seeing if I can figure out why it got an answer back that looks valid "2021:02:21 17:37:27", but after processing it internally came back with an invalid answer "2000:01:09 12:29:06".
So: Next steps: Can you power off the the clock and power it on again, and let me know the version number that is shown for 1 second at start up?
In the meantime, I'll try to figure out if there is something funky with that time string that I don't know about.
The good news is that we can fix this remotely, because the "OTA" option is enabled. I can send you a new package to install via browser if we need that...
The combination "Found I2C slave (Nixie clock) (default) 105" and "Communicating with: Clock not found!" means that the WiFi module knows that there is a clock there, but does know know how to communicate with it. The status string also confirms this upper case letters means that the thing we are referring to is "on":
"W" - WiFi is connected
"N" - NTP time is valid
"S" - The SPIFFS file system was mounted
"U" - OTA Update is possible
"A" - Authentication for the web configuration is turned on
"d" - Debug mode is off
The "Display time" means that the NTP for some reason got an answer back that it could not interpret. I'm looking at this now, seeing if I can figure out why it got an answer back that looks valid "2021:02:21 17:37:27", but after processing it internally came back with an invalid answer "2000:01:09 12:29:06".
So: Next steps: Can you power off the the clock and power it on again, and let me know the version number that is shown for 1 second at start up?
In the meantime, I'll try to figure out if there is something funky with that time string that I don't know about.
The good news is that we can fix this remotely, because the "OTA" option is enabled. I can send you a new package to install via browser if we need that...
Please Log in or Create an account to join the conversation.
22 hours 12 minutes ago #12484
by Ty_Eeberfest
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic Modular clock problems
Only Ian can answer your question about your order. Order processing is above my pay grade
Best way to get a video to us is to upload it to YouTube and post a link here. I'd prefer you post a simple URL link instead of using the video embedding feature of the forum since embedding is tempermental and IMO not to be relied on.
OTA updating applies only to the ESP's firmware. At this time it's not possible to flash the Atmega on the clock board OTA. Maybe some day. Since you are already flashing without OTA I'd recommend you stick with what seems to be working for you. I think your best bet is to make sure you have the latest versions of WiFi and Clock firmware from the repo, make sure you are compiling the clock firmware with the correct REV3 vs VER2 setting for each board, and flash away. I don't fully understand what is going on with your "weird digit" issues but it would be nice to confirm or eliminate firmware as the cause once and for all.
Best way to get a video to us is to upload it to YouTube and post a link here. I'd prefer you post a simple URL link instead of using the video embedding feature of the forum since embedding is tempermental and IMO not to be relied on.
OTA updating applies only to the ESP's firmware. At this time it's not possible to flash the Atmega on the clock board OTA. Maybe some day. Since you are already flashing without OTA I'd recommend you stick with what seems to be working for you. I think your best bet is to make sure you have the latest versions of WiFi and Clock firmware from the repo, make sure you are compiling the clock firmware with the correct REV3 vs VER2 setting for each board, and flash away. I don't fully understand what is going on with your "weird digit" issues but it would be nice to confirm or eliminate firmware as the cause once and for all.
Look into it later when the dust is clearing off the crater.
Please Log in or Create an account to join the conversation.
Time to create page: 0.128 seconds