If it did run before does not in any way mean the code was not wrong.
There are circumstances were coding errors won’t cause harm but they are still errors.
The compilers and/or optimizers might mitigate some effects on one platform but not on the other.
If you are 100% sure it’s only running vanilla Tinker with a clean device OS (including bootloader), then a HW issue is most likely.
A particle serial inspect log would be good to see.
I do have an arris modem, I turned off IPV6 routing and this seemed to have stabilized the connection so that it can reconnect to the mesh network, but continues to disconnect. Before turning that off it would disconnect and never reconnect until I power cycled the Argon.
I was supplying regulated power (5V) via VUSB and GND. This afternoon, I found a power supply mistake in my wiring (which explains why the board got a bit hot).
The wiring was fixed and now I am having a stable mesh network. I will continue to monitor.
Here are the remaining problems:
Sometimes, when updating Argon/Boron firmware, Xenons also flash Magenta!
When Argon/Boron is reset (via System.reset and without power cycle), Xenons in the mesh never restart. They keep flashing cyan rapidly followed by a couple of yellow or red flashes, then fast cyan for a while …
Are people still experiencing this SOS 7 “Exit” issue? I have one Xenon which reboots itself about every two minutes with red LED blinking seven times. It doesn’t matter which sketch I’m using, I’m seeing this with empty loop() and setup() as well. This also happened with rc-25 and now with rc-26.
Also the Xenon does this if it has been set up to Boron mesh or Argon mesh - no matter, and the setup sequence of Xenons to the mesh network doesn’t also matter. I have also tried changing the power supply / using USB only. Nothing seems to help.
Wanted to follow-up with this thread to let everyone know that a fix for the SOS-7 issue has been released with v0.8.0-rc.27. The issues was tracked to a problem with the Nordic 802.15.4 driver. Instructions for upgrading are available below. We’d love to know if applying the release fixes the issue SOS-7 issue that you’re experiencing.
Note that we have seen some reports of change in behavior for rc.27 when users call the Mesh.subscribe() function within the setup() loop that can result in a separate SOS-10 code which we’re currently investigating. If this issue affects you, please note the following workaround.