One of the CORE2-ROS’s just stopped connecting to the cloud randomly. It has been configured, code has been flashed to it from the cloud and ROS nodes were running on the RPi 3 to interact with the code on the CORE2.
At some point we tried the Rosbot code, when we uploaded that it gave an invalid bin file error or another error that said ‘programming in progress’. At once, the code was flashed to it and we started the rosserial. But that could not sync with the CORE2 anymore and gave the “Can’t sync with device” error."
We rebooted the CORE2-ROS and tried to flash other code via the cloud to the CORE2-ROS, only to find outthe CORE2-ROS won’t come online in the cloud again.
The blue light is solid, which means that it is connected to the internet. But because the time is not synchronizing, I am setting the time manually to the right time. This used to work before as well. At this point the blue light starts blinking, while I am still connected to the RPi 3 with RDP or SSH. It is still not connecting to the cloud.
So there’s 4 problems in this topic:
- The invalid bin file error is back
- Sometimes flashing the code to the CORE2 gives ‘programming in progress error’
- The RPi 3 can’t sync with the CORE2 with rosserial
- The CORE2-ROS can’t connect to the cloud before and after the system time is synchronized. Blue led is flashing but I can still connect to it via RDP or SSH.