Pixhawk 4 - I2C sensors not found

[EliotBR (Eliot)]

@Guillaumeee

I set the parameter BARO_PROBE_EXT to 768 and it works now ! I found my BAR 30 sensor.

Good to hear

@Guillaumeee

So it is possible to use the pixhawk 4 with ardusub 4.2.0 dev.

Indeed.

@Guillaumeee

Now I also added a celsius fast response temprerature sensor on an I2C splitter but I don’t receive any values. Nothing in temperature(3). I only have the T° value from the BAR 30 in temperature(2).
Do you have any clue ?

I can replicate that here. We tried setting BARO_EXT_BUS = 3, which got the Celsius to work but stopped the Bar30 from working. Wouldn’t suggest trying it - it’s not simple to get back the other way.

We’re looking into this, but not sure how long it will take to fix. It may just be a parameter issue, but may also require changes to ArduSub - we won’t know until we have a working solution.

@Guillaumeee

when I only have the video and lose the control/telemetry, I restart the computer and it works.

Glad you’ve at least got a workaround. A few notes:

• If you’re restarting the topside computer perhaps there’s some kind of firewall issue or something.
• If you’re restarting the onboard computer, does the mavproxy service come up in the web interface?
  • If it does then it might be sufficient to reboot the autopilot (from the web interface).
  • If it doesn’t then you can likely reboot just the onboard computer (from the web interface) rather than having to power cycle everything.

---

By the way, I’ve just re-read your initial post and seen that you got a Pixhawk 4 because your initial Pixhawk 1 (from us) failed. If you haven’t had your BlueROV2 for very long then it might be worth contacting support@bluerobotics.com - they may be able to send you a replacement. Pixhawk quantities are very low, but if we’ve sold you a product that didn’t perform reasonably then that’s on us to fix.