Display stops updating without any error indication

[zdeseb]

It occured to me that MoonClock froze with the same value on the display.
When this occurs, user does not know that there is a problem and that the displayed number could be few hours or days old.

Of-course solution is quite simple un/plug the power but the problem is that you do not have any way to realize that you should do that :-)

BTW: I saw in the code many print() statements but don't know how to get them :-)

Zdenek

[the-papi]

If you have Linux, you can read the output of print() using screen /dev/ttyACM0. Can you provide it?

[gorrdy]

This is a bug that happens sometimes. It is probably caused by exception in the python code. Solutuon is to check the code where these exceptions can happen and fix it there.

Would it be possible to have the whole cycle in code.py in python's 'try'? It would just reset the moonclock except of stopping it.

[the-papi]

Would it be possible to have the whole cycle in code.py in python's 'try'?

It's a possible "solution", but it's fucking ugly. However, it may work as a temporary workaround before merging #3.

[zdeseb]

It's a possible "solution", but it's fucking ugly. However, it may work as a temporary workaround before merging #3.

I am glad that I've not started rewriting the code yet as I see how much work has already been done :-)
And the code is definitely worth rewriting but python is not among my native programming languages so I was lazy to do it.

I could try to catch the error (already realized how to connect to console output from my OS) but I guess that it would be waste of time because it could be anything (WIFI problem, temporarily unavailable internet connection or the API).

I will apply the proposed 'try' hotfix and am looking forward to the merge ;-)

[zdeseb]

It's a possible "solution", but it's fucking ugly. However, it may work as a temporary workaround before merging #3.

FYI @the-papi : I've tried to run #3 version for a while (about one day) and ended with following error

Auto-reload is off.
Running in safe mode! Not running saved code.

You are in safe mode because:
CircuitPython core code crashed hard. Crikey!
Crash into the HardFault_Handler.
Please file an issue with the contents of your CIRCUITPY drive at
https://github.com/adafruit/circuitpython/issues

[the-papi]

It's a possible "solution", but it's fucking ugly. However, it may work as a temporary workaround before merging #3.

FYI @the-papi : I've tried to run #3 version for a while (about one day) and ended with following error

Auto-reload is off.
Running in safe mode! Not running saved code.

You are in safe mode because:
CircuitPython core code crashed hard. Crikey!
Crash into the HardFault_Handler.
Please file an issue with the contents of your CIRCUITPY drive at
https://github.com/adafruit/circuitpython/issues

This is issue of the ESP32 (or circuitpython?). Sometimes it behaves strangely when copying new code, and I don't know why. It's not a problem of my code.

If your moonclock has been reformatted and is now labeled CIRCUITPY instead of MOONCLOCK, don't worry. Mine too. It has zero effect on functionality.

@gorrdy can confirm that these weird problems (read-only filesystem, random disconnection from PC, Input/Output error, etc.) just happen sometimes. You need to reconnect moonclock and try to copy new source code again.

[gorrdy]

This is probably solved by PR #7