2020-03-17, 01:37 PM
(2020-03-16, 10:10 PM)DanielGoedhuis Wrote: Thanks for the quick reply.
It didn't quite solve the problem yet, though. Removing the I2C-app solved the problem of the stuck start-up screen (which is annoying, because it blocks all other screens; improvement suggestion to move this screen to a corner and make it smaller)
But then I don't have the sensors anymore. Reinstallation of the I2C-app re-created the problem.
I'm trying now different approaches, and update this post later
Update:
I installed Moitessier App, because that has I2C functionality as well, if I recall correctly, in an effort to pinpoint the problem. Now the start-up blocks on the checking of Moitessier HAT (which I don't have).
Update 2:
Uninstalled Moitessier, I2C and Pypilot. Deleted in .openplotter/openplotter.conf everything in the sections [I2C], [Pypilot] and [Moitessier], and deleted the connections in Signal K
Rebooted and start-up works, but still without I2C functionality (logically, because the apps are uninstalled).
Checked with i2cdetect -y 1, which only very slowly gave answer: address by address, instead of all addresses at once, and no address found at all!
I shut down the Pi completely (instead of rebooting it all the time), removed and replaced the sensors, and that did the trick. i2cdetect gave correct addresses.
Re-installed I2C and Pypilot apps, and it works again, including connections to Signal K.
Learnings: perhaps some bad wiring on my I2C bus? Or a temporary power problem on the bus?
Who knows, bad wiring causes similar effects. Sometimes you also get paranormal effects when 2 programs try to read the same device.
thanks for reporting