pringleman83 / zeus-trigger Goto Github PK

When interval time is set in the intervalometer options anything up to and including 32 seconds is fine. 33 seconds and numbers after that glitch the variable out (to a negative number). Using hours, minutes and seconds instead of just seconds also shows some inaccuracies (but nothing crazy seen just yet). Likely to be something I've done int the getSeconds(), getMinutes() and getHours() functions.

This had occurred on and off in the past and it put it down to a loose wire. Eventually i replaced the button assuming it to be damaged. however, it's doing it almost all the time now.

I've tried swapping out the arduino board. Same result.
I've tried using the board externally with blink code on the same pin (also reading the pin in Serial.println(). That appeared to work accurately.

As I'm using internal pullup resistors, I'm considering converting the project to use external pullup or pull down resistors.

I'll keep the issue up to date until resolved.

When debugging is enabled (enabling a number of Serial.println() commands displaying variables), sometimes, the OLED screen will fail to initialise. This results in the failure message being sent to the Serial display.

Previous trouble shooting found that the error occurred when dynamic memory was above 43%. I added "while(!Serial);" to the setup() function and this appeared to fix it. That wa suntil dynamic memory increased slightly further.

For now, dynamic memory is lower and the issue isn't showing. It is however present and so I'll be thinking of a way to solve it.

Avice I've received is to put any sconstant strings into the flash memory to reduce dynamic memory usage. I've also just learned about referencing variables in functions (I understand that'll reduce the use of dynamic memory and make it more stable if it can be safely implemented). I need to be careful with the flash memory though as we're at around 62% with most features still to be implemented.