I have a Depth sensor (BAR30 - v.1) and Celsius Fast-Response Temperature sensor (v.2) connected to I2C Bus Splitter, which is connected to Pixhawk I2C.
This has been really problematic as I’m frequently getting an error message and then without warning, the depth sensor drops out.
This is really annoying, so I had no choice but to unplug the temperature sensor and the splitter from the Pixhawk and use only BAR30. Then finally the BAR30 can
Anyone else can relate to my problem, or is there something else that I can do to fix this?
To have the depth sensor is the more (most) important thing, but I was hoping to use the Fast-Celsius sensor for scientific work.
Details:
BlueROV2, version 3
Raspberry Pi 3+
Pixhawk 2.4.7
QGround Control: v4.2.8
Ardusub: 4.1.1
BlueOS: v.1.1.0
Newton Subsea Gripper (v.2)
Ping2 Sonar Altimeter & Echosounder
I know both sensors have been recognized as it has worked before—depth sensor - temp, and Fast-Response sensor.
I don´t believe the communication cables are “too long” as they come originally from BlueRobotics. I have not tested to shield them, if the I2C is sensitive to noise and such then this is something that is worth checking out.
The power supply is sufficient as my battery is brand new 15,6Ah and the cells are even and hold voltage good.
I still have to put an oscilloscope on the data cables/lines and check the signal. That is something that would be worth checking out.
It will take some time to go through some of those tests as I´m using the ROV for science work and it´s very important to have the unit reliable.