- Posts: 31
- Thank you received: 1
V355 bug
- Ty_Eeberfest
-
- Offline
- Administrator
-
1 year 7 months ago #9106
by Ty_Eeberfest
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic V355 bug
Did you update the firmware in the ESP8266 WiFi module when you updated the clock? If not, that is probably the problem.
bitbucket.org/isparkes/nixiefirmwarev2/src
bitbucket.org/isparkes/nixiefirmwarev2/src
Look into it later when the dust is clearing off the crater.
Please Log in or Create an account to join the conversation.
- Ty_Eeberfest
-
- Offline
- Administrator
-
1 year 6 months ago #9270
by Ty_Eeberfest
Just to follow up... I was able to reproduce the problem here with Rev.2 V.355 when I loaded it on my Modular clock and WiFi module. It's a legit bug, the source of the problem has been located, and Ian tells me he's fixed it and will make it available very soon. Not sure if it will still be called 355 or rolled to 356.
Look into it later when the dust is clearing off the crater.
Replied by Ty_Eeberfest on topic V355 bug
lays wrote: Hi Ty,
Yes, i updated the esp and the atmega, reverting back to 353 solved the problem
Just to follow up... I was able to reproduce the problem here with Rev.2 V.355 when I loaded it on my Modular clock and WiFi module. It's a legit bug, the source of the problem has been located, and Ian tells me he's fixed it and will make it available very soon. Not sure if it will still be called 355 or rolled to 356.
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.169 seconds