Set up of REVO (CC3D) with iNav Configurator 7.1.1

[wcfung]

I am setting up the FC (full REVO) with RX being Jumper R8 (see attached spec) which is FrSky compatible. I can't get the Rx signal getting thru to the FC, as seen in iNav, having tried all different options in Rx and Ports pages of iNav. Have following questions :--

1. For the Jumper R8 Rx, Under Rx TYPE in iNAV Configurator, should I choose "Serial" or "MSP" ?
2. Under Serial Rx Provider, what should I choose ?
   
   
   

Thank you for help.

[sensei-hacker]

Your last screenshot states that the protocol is Sbus.
That is a serial protocol.

Sbus is a bit weird, though, because it inverts the signal compared to standard serial. So using sbus requires that another inverter be used to flip the signal back over to normal serial UART communication. Your board should have an inverter on uart 1.

I see in your screenshots you tried UART 3. That won't work because uart 3 is a standard UART, not inverted. Only UART1 is flipped.

This documentation may also be helpful for you.

https://github.com/iNavFlight/inav/blob/master/docs/boards/Revolution.md

[wcfung]

Thank you for yr reply. I tried Serial Rx in Ports page, and only then will I be given option to choose "SBUS" in Serial Receiver Provider. I chose "ON" and then "OFF" under Serial Port Inverted, In both cases, the receiver signal CANNOT get thru to the FC. See links to the screenshot:-- https://drive.google.com/file/d/1mxC_1mkKR7VMvYstQHwIIUODVXfMgw3x/view?usp=drive_link https://drive.google.com/file/d/1KDwl-jk4giZN1azfdImWU2gruGXUe5eq/view?usp=drive_link Not sure what did I miss. Any clue ? Thank you.

…

On Sat, May 17, 2025 at 10:05 PM Sensei ***@***.***> wrote: Your last screenshot states that the protocol is Sbus. That is a serial protocol. Sbus is a bit weird, though, because it inverts the signal compared to standard serial. So using abus requires that another inverter be used to flip the signal back over to normal serial UART communication. Your board should have an inverter on uart 1. I see in your screenshots you tried UART 3. That won't work because uart 3 is a standard UART, not inverted. This documentation may also be helpful for you. https://github.com/iNavFlight/inav/blob/master/docs/boards/Revolution.md — Reply to this email directly, view it on GitHub <#10873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5VK72B24WGBR3HNCKWQYL27AIKZAVCNFSM6AAAAAB5LK6EICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMJYGIZTMNQ> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sensei-hacker]

I requested access to those files.on your Google drive.

Recall only UART1 has an inverter on that board. Did you move it to UART1? (Yeah Sbus is a hassle).

[wcfung]

Sorry, forget about the link restriction. https://drive.google.com/file/d/1mxC_1mkKR7VMvYstQHwIIUODVXfMgw3x/view?usp=drive_link https://drive.google.com/file/d/1KDwl-jk4giZN1azfdImWU2gruGXUe5eq/view?usp=drive_link

…

On Tue, May 20, 2025 at 4:29 PM Sensei ***@***.***> wrote: I requested access to those files.on your Google drive. Recall only UART1 has an inverter on that board. Did you move it to UART1? (Yeah Sbus is a hassle). — Reply to this email directly, view it on GitHub <#10873 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5VK72NJPBWIXM54QSY6UL27O3FFAVCNFSM6AAAAAB5LK6EICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRRGI4DANA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[sensei-hacker]

That looks about right as far as the INAV setup.
So then the question would be how it's wired and how the receiver is configured.

[wcfung]

I replaced the Jumper R8 receiver with a standard Spektrum compatible receiver with PPM output, and then selected UART1 Serial receiver, with SPEK 1024 (or 2048) as Serial receiver provider, nothing changed. Still no receiver signal getting thru to FC. On Tue, May 20, 2025 at 5:20 PM Frankie Fung ***@***.***> wrote:

…

Sorry, forget about the link restriction. https://drive.google.com/file/d/1mxC_1mkKR7VMvYstQHwIIUODVXfMgw3x/view?usp=drive_link https://drive.google.com/file/d/1KDwl-jk4giZN1azfdImWU2gruGXUe5eq/view?usp=drive_link On Tue, May 20, 2025 at 4:29 PM Sensei ***@***.***> wrote: > I requested access to those files.on your Google drive. > > Recall only UART1 has an inverter on that board. Did you move it to > UART1? (Yeah Sbus is a hassle). > > — > Reply to this email directly, view it on GitHub > <#10873 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AD5VK72NJPBWIXM54QSY6UL27O3FFAVCNFSM6AAAAAB5LK6EICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRRGI4DANA> > . > You are receiving this because you authored the thread.Message ID: > ***@***.***> >

[sensei-hacker]

I replaced the Jumper R8 receiver with a standard Spektrum compatible receiver with PPM output, and then selected UART1 Serial receiver, with SPEK 1024 (or 2048) as Serial receiver provider, nothing changed. Still no receiver signal getting thru to FC.

That makes sense if it was set for PPM output given that PPM isn't serial.

[wcfung]

The wiring is as simple as the attached diagram. The receiver (Jumper R8) is configured in iNav Configurator.......given that I selected UART1, and MSP in Ports page. In Receiver page, I selected "MSP" as Receiver Type (there is no option for SBUS). With this combination, there is no signal getting to the FC.. Just weird. I have been using R8 and Revo in Ardupilot suite (Mission Planner id the configurator) for many years and it is quite straight forward and user friendly. Thank you for yr continued support.

…

On Tue, May 20, 2025 at 5:54 PM Sensei ***@***.***> wrote: That looks about right as far as the INAV setup. So then the question would be how it's wired and how the receiver is configured. — Reply to this email directly, view it on GitHub <#10873 (reply in thread)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AD5VK7YJ3MEINCHBATONG5D27PFDPAVCNFSM6AAAAAB5LK6EICVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTGMRRGM2TANA> . You are receiving this because you authored the thread.Message ID: ***@***.***>