Hello,
My shake was working perfectly and suddenly it stopped working.
It seems to be stucked booting.
Maybe you can help me with some ideas on how to fix my problem.
RSH.R1740.2023-07-04T14_13_49.logs.tar (4.0 MB)
Maybe you can help me with some ideas on how to fix my problem.
RSH.R1740.2023-07-04T14_13_49.logs.tar (4.0 MB)
Hello matiro,
I’m sorry to hear this about your RS3D, and thank you for posting the logs from the Shake itself.
From them, it appears that, during the booting process, the Pi board is not able to see the blue Shake board above it:
2023 185 14:06:26: Unable to read Firmware version number off of Serial Port /dev/serial0 after trying for 15 seconds, cannot continue!
2023 185 14:06:26: Is the Pi computer connected to the Raspberry Shake Board? Please confirm and try again.
Furthermore, these lines in the logs, tell us that there is something going on between the boards and the sensors:
2023 185 13:30:34>> Y??Q?ÁÊQ?FDIÀDªÔUmUªW$ÁY??EËBYTXIð?S?ãÄE
2023 185 13:30:34>> Y??e?W?
2023 185 13:30:34>> te?E??ôîOk3I]º?]Y ]]?Ü_k?M?DW27S??Ë?AÐE
2023 185 13:30:34>> 'QA JU
2023 185 13:30:34>> x???U?Z]?ÄL]ª
As you can see, there are errors mixed with some ‘gibberish’ that cannot be successfully interpreted. My first thought would be to check and see if the power supply is delivering a stable voltage between 5.0 and 5.2V and a current of at least 2.5A at all times, as a decrease in power could lead to data services interruption. If you have another Pi power supply that you know is in working condition, please try to exchange the current one with that, and see if the Shake now properly boots.
A second check that you can do is to see if all the connections between the sensor, the blue Shake board, and the Pi board are still solid and free from dirt or any other element that could compromise transmission. This is important, in particular, if the Shake is located in an environment where dust or moisture can affect it. If needed, you can find assembly guides here in our manual: Assembly Guide — Instructions on Setting Up Your Raspberry Shake
When doing this, please make sure you are using proper ESD (ElectroStatic Discharge) protection (such as gloves, etc.), as electronics do not like static electricity too much.
If all these checks come out as positive, then I would recommend re-burning the microSD card, and see how the Shake behaves with a freshly-installed system. I will leave the burning instructions here for your convenience:
- Please take the microSD card you have and format it before burning the new Shake OS image
- Make sure, when you format it, that the shown capacity is the maximum (i.e. if the SD card is 32GB, then the capacity should be near or equal to that value). This is to check that no partitions have been involuntarily and erroneously created. They could be the cause of the error we see now
- Take care to format the SD card in a FAT32 File System (or exFAT if the SD card is 64GB or larger)
- Download the new Shake OS image from here: https://gitlab.com/raspberryShake-public/raspshake-sd-img/-/raw/main/raspishake-release.zip
- And follow the microSD burning instructions from here: raspishake-microSD-card-software-Instructions.txt · main · raspberryShake-public / Raspshake Sd Img · GitLab
Thank you for your collaboration!
Thank you very much, i checked the power supply, and apparently that is the problem, the usb-c to usb-b adapter is loose and loosing conection. I’ll try to find a new one.
2 Likes
You’re more than welcome!