I got the Omnibus F3 AIO board and flashed it with INAV 1.7.3. In the GUI, I set the receiver type to to PPM. However, in the Receiver tab, the default setting shows AETR5678 (not 1234). I am using a FlySky FS-i6s radio and AETR are fixed to channels 1234.
I flashed the same board with Cleanflight and it showed AETR1234. I also had used INav with a SP Racinh F3 board and there two it showed AETR1234. It is only the combination of Omnibus F3 with INAV that is producing AETR5678.
Any clue? How can I get inav with Omnibus to have AETR1234.
I think you are misinterpreting the meaning of this in th GUI
AETR5678 means that channels 1 to 4, which are the usual joystick channels are mapped to AETR and the 5678 means that the remaining auxiliary channels are mapped to channels 5,6,7&8 and onward if you have a TX/RX more than 8 channels
the snap below is from my Omnibus F3, iNav 1.7.3 default settings
BUT what I am puzzling over is why the colour bar representation has throttle at 4 and yaw (rudder) at 3
However if you look in CLI dump you’ll see that it maps these 4 channels as AETR1234 which I think is the confirmation you are looking for that all is as you want it
You explanation makes sense (and clarifies things to me) but it solves half the problem. The other unsolved issue is that the channels in the GUI (in the receiver tab) do not react to the stick movements. I am using a PPM receiver and already set the receiver type to “PPM” in the Configuration tab (my understanding is that this is all that is required foe stting up a PPM receiver, i.e. no need to physically remove the Sbus bridge/transistor on the FC board).
Do you have anything else on UART3? If so that is probably the problem as PPM requires use of UART3
If not, check the 0R links to the left of the PPM Pin, maybe your board was not set correctly at the factory
If not already done so, have a look a this sites guide for this FC
I’ll try to find time tomorrow to power up my board in PPM and see if I get the same problems
The issue is definitely not the receiver. I’ve used it many times with the same transmitter, even with the same Omnibus board but with Cleanflight and Betaflight. The problem happens with this FC when running iNAV.
Sorry to hear about your board
When bench testing new stuff instead of using a LiPo I power off a variable DC supply with current limit set at a few hundred milliamperes higher than I’m expecting the board to take, then when I do something stupid (often ) the board is saved
Sorry if this sounds like advice too late
I’ll post again when I’ve played tonight
Although this worked I’ll not be trusting it in flight.
The forums do talk about some workarounds which I’ll try later.
“(0) Full erase flash latest FC firmware (1) Connect, goto configuration tab, select RX_SERIAL, save and reboot. (2) Connect, goto ports tab, turn on SerialRX on UART3, save and reboot Sounds like Serial RX configuration, right? (3) Connect, goto configuration tab, verify RX_PPM has revived. (4) Goto receiver tab and see your PPM receiver working!!!”
There appears to be a later version of iNav,1.8.0 which I’ll try. The release notes show changes to receiver configuration and selecting so maybe this has been resolved.
Need to leave it now, will carry on in the morning
I’ve done a little video, trying to upload it, watch this space !!
I’m going to leave this post now (my intention for my board is Futaba SBUS, this problem just intrigued me)
I’ll keep an eye out for any new releases of iNav for PPM
Has anybody else on the forum experienced and solved this?