Hi everyone,
I have Airbot Omnibus F4 Nano V6 flashed with INAV target FIREWORKSV2. I've connected a FrSky RXSR via FPORT using a bidirectional inverter to UART1 (using RX & TX lines from converter). Softserial is disabled. This setup is working fine on two other F4 flight controllers (Matek F405, Matek411).
I also connected a magnetometer to SPI/UART3 and a UBLOX7 GPS to UART6.
FPORT & telemetry are working fine with this setup, as long as I don't configure GPS. When GPS is turned on in configurator/cli, I won't get the INAV telemetry data anymore. It does not matter, if GPS wires are pysically connected or not. I also selected a different UART for GPS (without connecting a GPS device), but the problem stays the same: no telemetry when GPS is turned on.
When (re)booting with GPS turned on, I get telemetry data (even the GPS-related telemetry items) for about 2 seconds, then telemetry is gone again.
So I'm not sure what's wrong. Is this a config problem, a hardware limitation or even a bug?
I attached my current diff for reference.
Thanks in advance and happy flying
INAV_cli_RetroCopter_20210212_213354.txt
Hi everyone,
I have Airbot Omnibus F4 Nano V6 flashed with INAV target FIREWORKSV2. I've connected a FrSky RXSR via FPORT using a bidirectional inverter to UART1 (using RX & TX lines from converter). Softserial is disabled. This setup is working fine on two other F4 flight controllers (Matek F405, Matek411).
I also connected a magnetometer to SPI/UART3 and a UBLOX7 GPS to UART6.
FPORT & telemetry are working fine with this setup, as long as I don't configure GPS. When GPS is turned on in configurator/cli, I won't get the INAV telemetry data anymore. It does not matter, if GPS wires are pysically connected or not. I also selected a different UART for GPS (without connecting a GPS device), but the problem stays the same: no telemetry when GPS is turned on.
When (re)booting with GPS turned on, I get telemetry data (even the GPS-related telemetry items) for about 2 seconds, then telemetry is gone again.
So I'm not sure what's wrong. Is this a config problem, a hardware limitation or even a bug?
I attached my current diff for reference.
Thanks in advance and happy flying
INAV_cli_RetroCopter_20210212_213354.txt