Hey everyone, I’m trying to build a rover using an Omnibus F4 Pro v2. I flashed the board with the bl.hex rover file using iNAV as per instructions and was able to connect it to Mission Planner and is being recognised properly.
However, I’m facing a few issues- there’s no movement on the virtual horizon, the RX isn’t being detected, and the GPS also isn’t recognized.
I’ve flashed the latest stable firmware available for ArduRover (OmnibusF4Pro) as of now and also installed the latest version of Mission Planner. I’m using an ELRS receiver with SBUS output (I’ve removed the required inverter resistor from the board), and an M10 GPS module with a compass.
I’ve also tried flashing older versions of the ArduRover firmware and re-flashed the board a couple of times, but the issue still persists.The board was working perfectly with INAV before I made the switch.
Has anyone run into something similar or have any suggestions?
Well, none of the hardware is recognized so no surprise the Gyro isn’t working. It must be the wrong firmware for whatever is on that board. I have never liked Omnibus FC’s and they have been copied countless times over and given various version names.
It’s probably the same firmware you flashed but download the .apj file from here anyway and use Mission Planners “load custom firmware” option to flash it. Omnibus F4Pro Rover
Thanks for your help, I tried flashing .apj file via mission planner but still no progress. None of the hardware seems to be working. Is there anything else I could try?
the board looks fine, the only thing i can see that your doing different is flashing with Inav. I think it might be an issue , can you flash the BL firmware using STMCubeProgrammer in DFU mode.
Flash it to Betaflight and back to Ardurover. When you flashed the .apj file you should have gotten a message “firmware already installed” or something like that if it was what you installed initially. So, perhaps something got screwed up the 1st flash.
