Hi RaspberryShake community!
I am opening this topic because I face issues when trying to communicate between my RaspberryShake 1Dv8 and an USB Real Time Clock (USB Real-Time Clock (RTC) for Raspberry Pi | The Pi Hut and github here: https://github.com/sbcshop/USB-RTC-Software).
For the record, I wanted to add this functionnality to the RShake because the network is sometimes unavailable at my remote site, and I wanted to keep a good time-reference for the data.
The problem I face is the following:
I have a raspberry 4 for tests at the office. When I plug the USB RTC and run the codes from the RTC gitlab, I succeeds everytime both in time reading (from RTC to RSpi OS) or in time writing (from the RSpi OS to the RTC).
It succeeds at the 1st attempt, and takes 0 second.
when I run the same code on the Rshake (raspberry 3), I face various issues. Sometimes, it is possible to read or write the time from/to the RTC. But I takes generally hundreds to thousands of communication attempts (and around 10 seconds) to get one “successful” date-time communication.
But most of the time, it takes forever because no communication attempt succeeds…
My question is -in brief!- : do you have any idea what could cause such a difference between my test raspberry (which runs accordingly to the expected behavior) vs the rshake (issues) ?
I am wondering what could cause such trouble…
Thanks for sharing your opinion, any ideas welcome!
Pierre, from France