Hey, here's an update on our debugging process:
- We've run our two 3G Electrons with our full code suite since Wednesday, and they are still going strong! Running this long without a freeze has been rare among our 2G Electrons, so great news there!
- The Tinker software has run on thirteen 2G Electrons over the weekend with unreliable cellular coverage - none have freezed This is basically unheard of with 2G Electrons in the environment we run them in.
These results should be good enough to conclude that the Tinker software works with 2G Electrons in our desired setting; meaning there's something between the Tinker code and our "barebones" code that does not play nice. One of the differences is SYSTEM_MODE; AUTOMATIC vs SEMI_AUTOMATIC. The reason we're not running AUTOMATIC is that we need the devices to be responsive for user interaction when offline and as fast as possible when they boot up. It is not enough for the devices to wait until connection is established for them to be usable. With that said:
- Are there any important undocumented differences between these modes that may cause our freeze?
- Are there any stock code examples (like Tinker) available with SEMI_AUTOMATIC that we can test on our devices?
In the meantime we will modify our own barebones code to run STSTEM_MODE(AUTOMATIC) and see what happens.