Issues connecting I2C sensor to H743-WING-V3

justin12 · May 6, 2024, 8:10pm

Hello,

I am using an array of 6 ELVH-L02D HAAH-C N5A4 pressure sensors connected together to send pressure data over a single I2C connection.

When I connect it to a Cubepilot Cube Orange (running ArduPlane 4.4.0), I have no issues and the sensors connect and report values as expected.

However, when I connect the sensors to a Mateksys H743-WING-V3 (trying on both ArduPlane V4.4.0 and V4.5.1), they are not detected at all. But, if I connect a different I2C sensor to the Wing-V3, a mRo I2C Airspeed Sensor (JST-GH - MS4525DO), it is detected without any issues.

I have linked a log file with the H743-WING-V3 running ArduPlane V4.4.0 with the pressure sensor array connected.

Any help would be greatly appreciated.

Oli1 · May 6, 2024, 10:45pm

Can you post a log file of the Cube orange where the baros are working?

justin12 · May 7, 2024, 1:08pm

I apologize for my late response.

Here is the log file from the Cube orange with the sensor array running.

https://1drv.ms/u/c/3110368cc373f46a/EUFo9afB92RNluJpnTI9LiwBpYLKoKpMbLBf1cRfpjoTQw?e=vSA5Zz

Oli1 · May 7, 2024, 2:04pm

No worries. Hm, I had hoped for a config issue or I2C DevID collision. Alas.

Can you try setting BARO_PROBE_EXT to 1?

geofrancis · May 7, 2024, 2:09pm

I wonder if this is related to the i2c issues I was having with sensors on the H743.

github.com/ArduPilot/ardupilot

H743 I2C bug

opened 01:32PM - 10 Nov 23 UTC

geofrancis

I have been upgrading a boat from a Omnibusf4pro to a Matek H743 Wlite. but I ha…ve ran into an issue with the i2c bus where setting an address of 0x70 on my sr04 sonar adapter (default for maxbotix i2c sonar) causing the i2c bus to lock up and stop detecting devices. the sonar was working on the omnibusf4pro before I changed over the controller so I thought I might have damaged something. I originally thought it was a wiring issue, so tested the adapter on a different H743 and it had the same result I thought the atmega168 might have got damaged somehow, so I swapped it for another 168 and same result. I thought it could be an issue with the 168, so I changed it for a 328 and same result so just to rule out some kind of software problem, I connected yuris i2c sensor adapter that runs on a 168 with address 9 and it worked fine. so i went and got the original 168 and tested it again with the original omnibusf4pro and it works, so now I know it's definitely not a sensor or adapter software or Arduino issue. I tried changing the sonar adapter to the same 0x09 9 address as the sensor adapter and it shows up on the i2c scanner and i can get it to work using the lightware i2c driver set to i2c 9 so its not a hardware issue. If I change the sonar address back to its default 0x70 112 without doing anything else it will show up for a few seconds, then the i2c bus stops until I unplug it. The compass is connected as i2c device 13, you can see it going offline after i change the sonar adapter i2c address. ![Screenshot 2023-11-10 131856](https://github.com/ArduPilot/ardupilot/assets/5570278/39717487-b5b7-46d5-8574-0f5409b781cf)

try changing one of the sensors to i2c address to 0x09 to see if it starts working.

does the compass work with the other sensors attached to the same i2c bus?

justin12 · May 7, 2024, 2:47pm

Setting BARO_PROBE_EXT to 1 doesn’t seem to change anything.

I’ve also tried setting ARSPD_BUS to 0 as it says in the I/O Mapping section of the quick start guide. Doesn’t seem to effect anything either.

justin12 · May 7, 2024, 3:00pm

We order the ELVH-L02D HAAH-C N5A4 pressure sensors with a fixed address. So I can’t change any of their addresses unfortunately.

The compass does work with sensors attached as well.

geofrancis · May 7, 2024, 3:04pm

have you used the i2c scan script to see if they are detected?

github.com

ArduPilot/ardupilot/blob/master/libraries/AP_Scripting/examples/i2c_scan.lua

-- This script scans for devices on the i2c bus
local address = 0
local found = 0

local i2c_bus = i2c:get_device(0,0)
i2c_bus:set_retries(10)

function update() -- this is the loop which periodically runs

  i2c_bus:set_address(address)

  if i2c_bus:read_registers(0) then
      gcs:send_text(0, "Found I2C at " .. tostring(address))
      found = found + 1
  end

  address = address + 1
  if address == 127 then
    address = 0
    gcs:send_text(0, "Found " .. tostring(found) .. " devices")

This file has been truncated. show original

justin12 · May 7, 2024, 3:10pm

Yeah I’ve been using it to see if the sensors have been picked up. It’ll report the mRo I2C Airspeed Sensor (JST-GH - MS4525DO) with address 0x28 but it doesn’t report any of the other pressure sensors when I connect the sensor array.

justin12 · May 7, 2024, 3:13pm

Is it possible there is a voltage issue on the I2C2 port on the ~~H742-Wing-V3~~ H743-Wing-V3?

Oli1 · May 7, 2024, 3:54pm

Do you have a single one of the baros that you could try instead of the array or are they all fixed together?

justin12 · May 7, 2024, 5:19pm

Yeah I’ve tried using a single one before and it is picked up on the Cube Orange but still not detected on the H743.

I tried powering the sensor array with power from the one of the 9V pins ~~(even though its 5 volts)~~ then through an external 5V regulator and I’ll pick up 2-4 of them but the rest don’t show up. Seems like a power issue of kind.

Oli1 · May 7, 2024, 6:42pm

Are you using the pre built binaries of AP or did you use the online builder or build it yourself?

Did you look into the I2C bug mentioned?

justin12 · May 7, 2024, 7:46pm

Yeah I am using pre-built binaries loaded from Mission Planner.

The bug doesn’t seem related as I still can get all of the sensors to show up (or more often a combination of the sensors) when using power that is not from the I2C line, but very inconsistently. It seems to be a noise issue since moving my hand over the circuit sometimes effects whether all of the sensors are picked up or not.

geofrancis · May 7, 2024, 8:54pm

have you tried adding some pull up resistors?

Oli1 · May 8, 2024, 9:40am

When we’re getting into the electrics… can you measure the voltage of SCL and SDA on both the Matek and the Cube and let us know if the results differ?

justin12 · May 8, 2024, 4:37pm

Here are the voltages I measured on both the H743 and the Cube Orange. I also included measurements from the mRo I2C airspeed sensor for a reference for a working I2C sensor on the H743.

I also did double check and I am in fact getting negative voltages from the SCL and SDA lines when using the power from the I2C for the sensor array.

H743 - I2C Power

Pin Measured	Voltages
4v5	0.9V
SCL	-0.4V
SDA	-0.4V

H743 - mRo I2C Airspeed Sensor

Pin Measured	Voltages
5v	4.85V
SCL	3.16V
SDA	3.17V

H743 - 5V regulator power

Pin Measured	Voltages
SCL	2.96V
SDA	2.98V

Cube Orange

Pin Measured	Voltages
SCL	3.17V
SDA	3.05V

Oli1 · May 8, 2024, 5:14pm

In that case I believe that @geofrancis suggestion to add pull up resistors might help, see Internal pull-up resistors are insufficient for I2C for a start.

justin12 · May 9, 2024, 5:26pm

I tried using some 2K Ohm resistors and that seemed to cause them to show up, but was never able to read data off of them.

Unfortunately all of the sensors have stopped working so we have to wait for new sensors to arrive before I can continue working on this.

geofrancis · May 9, 2024, 7:30pm

do you have an arduino board like an esp32 or RP2040 you can use to test them?