Openplotter 3 - I2C - Your Raspberry Pi is too old - Printable Version +- OpenMarine (https://forum.openmarine.net) +-- Forum: OpenPlotter (https://forum.openmarine.net/forumdisplay.php?fid=1) +--- Forum: General discussion (https://forum.openmarine.net/forumdisplay.php?fid=2) +--- Thread: Openplotter 3 - I2C - Your Raspberry Pi is too old (/showthread.php?tid=4381) |
Openplotter 3 - I2C - Your Raspberry Pi is too old - buri - 2022-12-22 Hi, I enabled i2c and I can see my sensors, but System Check says: Checking I2C sensors... | I2C enabled | openplotter-i2c-read not running | Access to Signal K server validated ↳Your Raspberry Pi is too old. pi@openplotter:~ $ sudo i2cdetect -y 1 0 1 2 3 4 5 6 7 8 9 a b c d e f 00: -- -- -- -- -- -- -- -- 10: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 20: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 30: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 40: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 50: -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- -- 60: -- -- -- -- -- -- -- -- -- 69 -- -- -- -- -- -- 70: -- -- -- -- -- -- 76 -- pi@openplotter:~ $ My model according to https://elinux.org/RPi_HardwareHistory c03112 Q2 2019 4 Model B 1.2 4 GB (Mfg by Sony) Is that really too old?? I can see in the code (the only reference I could find to "Your Raspberry Pi is too old" with Google), that this message is shown, when the /dev/i2c-0 is in "ls /dev/i2c*" pi@openplotter:~ $ ls /dev/i2c* /dev/i2c-0 /dev/i2c-1 /dev/i2c-10 /dev/i2c-20 /dev/i2c-21 /dev/i2c-22 pi@openplotter:~ $ What can I do? RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - buri - 2022-12-22 I got the values from the Sensor into SignalK successfully using this SignalK Plugin: signalk-raspberry-pi-bme280 - https://www.npmjs.com/package/signalk-raspberry-pi-bme280 I don't know why Openplotter thinks my raspberry is too old. RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - nebosa - 2022-12-22 Hi after setting up my hardware clock on a CM4 I get the same message. I had to add the following lines in the boot.txt for the watch: dtparam=i2c_vc=on dtoverlay=i2c-rtc,pcf85063a,i2c_csi_dsi RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - Copprhead - 2022-12-29 I just installed Openplotter on a new computer and got the same message in the status bar of the I2C app. As a result I cannot add my sensors. Hardware:
I2C seems to be working, sensor is shown at address 76 Code: pi@openplotter:~ $ sudo i2cdetect -y 1 Software: Installed from image 2022-07-18-OpenPlotter-v3-Starting-stable-64bit-img Available updates installed. I2C Sensors 3.3.7-stable GPIO 3.1.0-alpha /boot/config.txt excerpt: Code: dtparam=i2c_arm=on RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - Sailoog - 2023-01-10 I will take a look at this soon RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - Didier B - 2023-02-03 Hi Sailoog, I got same issue, when validating for Buy/Nobuy decision a batch of 20 Pi4 8Gb, are there any news about this 'too old' message ? The question is : Should I go for a NoBuy EDiT PS : The issue only shows from V3 upward Does this means all boards manufactured after a certain (secret date) will not be acceptable for V3 and upward Is this constraint due to SignalK ? Is there a possible work around ? RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - Sailoog - 2023-02-03 do not panic, this is obviously a software issue, next on the list... you can buy as many RPi4 as you want, if you find them... it seems that /dev/i2c-0 not only appears in RPi1, it also appears in RPi4 under some conditions. If I am not wrong, everyone suffering from this error has manipulated config.txt manually, right? I am not able to reproduce it but it has an easy fix. RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - Sailoog - 2023-02-04 Fixed in openplotter-i2c v3.3.10. Test and report please. RE: Openplotter 3 - I2C - Your Raspberry Pi is too old - Copprhead - 2023-02-18 The error message is gone. My BMP280 at address 76 can be configured. Data is shown in Signal K server and dashboards. (I removed the SignalK-BMx280 plugin which I had used before.) Great job! Thanks Sailoog! |