Open SloMusti opened 5 years ago
Theories for why this may occur are the following:
Hardware watchdog test, given that an infinite loop trap is put in place: https://github.com/IRNAS/environmental-module-firmware/blob/master/env_firmware/env_firmware.ino#L74 to be able to determine if the CAN module fails to initialize. Given that the hardware watchdog is enabled prior to this, this loop is broken after 18 seconds as the timeout is defined and thus we can conclude the hardware watchdog works correctly and also the CAN module will keep trying to reinitialize until successful.
Test method:
This is a desired strategy as the device in current use-case is nto performing any useful functions if CAN does not work.
The issue appears to occur intermittently on some devices, currently observed on modules TOP1 and BOTTOM4, that after a few weeks of operation the device stops responding until a power cycle occurs. Nothing more is known at the moment.