Hi,
suddently, for no apparent reason, the barometer of my SpeedyBee F7 V3 stopped working and it's always on "red" plus it's always reading 0.00 on sensor page.

Using INAV 5.1.0

diff all: https://pastebin.com/GYE3QKni
dump: https://pastebin.com/PUHZEntc

I didn't try anything since this is kind of a surprise, as far as i remember i didn't changed anything in the config - prior to the problem - that could lead to this.

If you made no changed to the config and it happened all of a sudden then its probably a faulty component which is not very uncommon in this hobby.

(26-Nov-2022, 11:07 AM)kafie1980 Wrote: If you made no changed to the config and it happened all of a sudden then its probably a faulty component which is not very uncommon in this hobby.

I realized that if I reset everything the barometer comes back online.
When I go to install the GPS and compass (M8Q 5883) the barometer stays red... Almost as if there is some crosstalk between the two

The barometer and compass if connected via the same I2C connection may cause issues if one of the I2C devices is noisy.

I2C devices will not crosstalk since they will communicate with the host based on their I2C address (I am just simplifying things here and not going into actual detail).

Disconnect the compass and see how it behaves?

(28-Nov-2022, 11:09 PM)kafie1980 Wrote: The barometer and compass if connected via the same I2C connection may cause issues if one of the I2C devices is noisy.

I2C devices will not crosstalk since they will communicate with the host based on their I2C address (I am just simplifying things here and not going into actual detail).

Disconnect the compass and see how it behaves?

Should I physically detach the SDA and SCL wires right?
Setting the compass to "None" in the config tab in INAV doesn't solve it...

Yes, physically detach the SCL/SDA wires and test.

(28-Nov-2022, 11:24 PM)kafie1980 Wrote: Yes, physically detach the SCL/SDA wires and test.

Wires detached
FC reset => Baro ok
Port 4 set on GPS => Baro red
Whole GPS unit detached => Baro ok

Try the GPS on a different UART as you may have a conflict caused by UART 4.

(28-Nov-2022, 11:39 PM)kafie1980 Wrote: Try the GPS on a different UART as you may have a conflict caused by UART 4.

I will! The curious thing is: 
I'm using the port provided by the FC so no soldering was needed.
How is it possible that a port explicitly created for the GPS (as per SpeedyBee specs) interferes with something that is already on the board?

ow that I think about it, this FC has 5 UART.
UART1 is currently used for VTX
UART2 is currently used for RX
UART3 is currently used for CAM
UART4 is reserved for ESC telemetry
UART6 should be used for GPS but somehow fails.

Even if this solved the problem, it would create another one (where do I put the thing I removed from some of the other UART?)

If setting the baro to MSP instead of BMP280, it goes blue and this is the behavior when I pick it up and move a bit: https://imgur.com/a/ojHGRtT
This is the behavior when I pick it up but the GPS is disconnected (blue even with BMP280): https://imgur.com/a/clXUtYq

You can use any full UART pair and swap them around.

Just avoid UART1 or UART3 on a F4/F7/H7 flight controllers that power themselves up when a USB cable is connected to the FC (Snow reported this on the forum a while back).

If your Baro is not connected via an MSP connection then its just fake baro data and not real. MSP protocol can only be used with specific units such as the Matek M8Q-CAN which output GPS/Compass/Baro data via MSP.