Hi, I am running Openplotter 4 on a RPi 5 with a MacArthur hat.
I have added the following I2C devices and configured the values to go into signal K with no problem:
- AHT30
- BMP388
- ICM
However, after adding an ADS1115 sensor, when I go to edit a value to pass to signal K, once I click OK, all the sensors in the I2C app disappear. Although I can see the data is still being sent to Signal K, I just can no longer see or edit any of the sensors. Adding them back in brings them up, as long as I dont try to add the ADS1115.
Tried rebooting, still shows an empty list of sensors.
I am running I2C 4.2.0.
I've tried turning on debugging and opening through terminal, but not getting any debugging prints from I2C app.
Going to configure A0:
[
attachment=3057]
And after pressing OK:
[
attachment=3056]
Is this a bug, or am I doing something stupid?! The latter is most certainly a possibility!
This seems to be a bug. I will try to reproduce it ASAP.
I am experiencing exactly the same problem with a ads1115 connected through a PICAN-M HAT, the only difference is that the only i2c parameter which is updating in Signal K is the last ADS1115 input and any others which had been successfully edited before the ADS115 input. After a restart of the Raspberry Pi, all of the I2C inputs disappear from Signal K.
The presence or otherwise of other i2c devices is not relevant. The simple fact is that you cannot add an ADS1015 or ADS1115 successfully. Even if it is the only device, as soon as you edit it the i2c panel shows no devices.
I have just regressed the installation back to openplotter 3 and using I2C 3.4.2 the ADS1115 sensors could all be edited and installed correctly using exactly the same method I had been trying in I2C 4.2.0. I hope this helps with those amazing people who have developed this package, it is an amazing setup for a noobie like me.
Hi,
I have the same issue. I hope it can be fixed. I do not really want to go back to v3...
Thanks
I had very strange behavior on the i2c bus with an RPI5. It would not tolerate any run greater than 200mm and once I broke the 4-5 mark on i2c devices it became very unstable and acted erratic.
Adding an Adafruit LTC 4311 Active I2C terminator resolved the issue. May not be your problem but it is worth a try.
Hello,
I also have this same problem: impossible to enter a SK key for the ADS1115 sensor. This erases all other I2C sensors.
Have you found a workaround other than going back to V3?
My configuration: OP4 on RPi5/NVMe Pimoroni + Mac-Arthur hat
Thanks
(2024-09-17, 10:04 PM)Opie91 Wrote: [ -> ]I had very strange behavior on the i2c bus with an RPI5. It would not tolerate any run greater than 200mm and once I broke the 4-5 mark on i2c devices it became very unstable and acted erratic.
Adding an Adafruit LTC 4311 Active I2C terminator resolved the issue. May not be your problem but it is worth a try.
Hi. Thank you for the suggestion, I added the LTC 4311 I2C terminator to see if it might work and re-tested the system. In this case it didn’t resolve the issue.
I hope it is a minor software incompatibility in the change from OP3 to OP4 which can be found soon. I will try using an ADS1015 in the meantime and see if those are compatible with OP4.
I will report back with my findings, don’t hold your breath though it could take me some time.
(2024-11-17, 06:40 PM)Kit_buyer Wrote: [ -> ] (2024-09-17, 10:04 PM)Opie91 Wrote: [ -> ]I had very strange behavior on the i2c bus with an RPI5. It would not tolerate any run greater than 200mm and once I broke the 4-5 mark on i2c devices it became very unstable and acted erratic.
Adding an Adafruit LTC 4311 Active I2C terminator resolved the issue. May not be your problem but it is worth a try.
Hi. Thank you for the suggestion, I added the LTC 4311 I2C terminator to see if it might work and re-tested the system. In this case it didn’t resolve the issue.
I hope it is a minor software incompatibility in the change from OP3 to OP4 which can be found soon. I will try using an ADS1015 in the meantime and see if those are compatible with OP4.
I will report back with my findings, don’t hold your breath though it could take me some time.
I have just installed the ADS1015 and tested it and it behaves in the same way in OP4 as the ADS1115, in that it can be added, but when it is edited and a Signal K name allocated to any of the channels, all the entities in the I2C list disappear.
Considering the system works as expected in OP3 with the ADS1115, I am guessing that there might be a bug in OP4 with these analog to digital converters.
(2024-11-13, 02:21 PM)ckoissa Wrote: [ -> ]Hello,
I also have this same problem: impossible to enter a SK key for the ADS1115 sensor. This erases all other I2C sensors.
Have you found a workaround other than going back to V3?
My configuration: OP4 on RPi5/NVMe Pimoroni + Mac-Arthur hat
Thanks
Hello,
I have been unable to find or devise a workaround, sorry. I am now hoping that someone will find the bug and be able to fix it, the only solution I have found is to revert to OP3 - not ideal, as you say.