FrSky Access Receiver f.port connection trouble

[nano-tech]

Hi there,

got an R8pro receiver which communicates via access so you can choose between f.port or s.bus telemetry
I use an FrSky integration cable connected from r8pro sbus out to spirit 2 unit at rud port (orange an brown pins) and to ELE/PIT/AIL port just the red wire from integration cable (to signal pin)

if I set f.port communication in the spirit app, theres no deflection at any servo in the diagnostic tab.
if I set the communication to futaba s-bus, all works fine.

tried also an x8r with universal firmware, same here.

help me please

[ZeXx86]

If using SBUS you do not need to use any other cable - stright one is enough.

But for integration and telemetry you need the integration cable.

For FPort both channel data and telemetry goes together - this require FrSky integration cable.
You also need to power up the receiver.

Please check this page:
https://manual.spirit-system.com/index. ... rSky_FPort

You also need to switch receiver output to FPort. By default it is set to SBUS. This must be done in your radio.

[nano-tech]

Thanks for your answer, but all those settings i already tried.

what i got

Archer R8 pro
FrSky integration cable

cable is wired like supposed to do in the manual
receiver is switched to f.port with my X20 radio
receiver powered separately from my SBEC

but either with f.port or f.bus or what else, no communication with the spirit 2 and the receiver

There's just comm if I switch the sprit to futaba s-bus mode, without changing the cabling
it exactly done like you said : https://manual.spirit-system.com/index. ... rSky_FPort

[Mattes61]

Hello,
you wouln't try FBus ? That's a better and faster protocol and available with the X20 -
One thing you should keep in mind: explicitly only set 16 channels in your remote control, that's really relevant! The whole thing won't work with the setting in the remote control with 24 channels, as Spirit doesn't support it at the moment, so I suspect that's your "problem" -

What FBL do you have, Spirit GT or Spirit II ? You have said nothing about it -

Regards

Edited: new picture added the picture before was not completely correct (20.05.24, 13.03 Uhr)

Addendum: You have to use the SPort-interface for FPort or FBus, see in the added scrennshot -

[nano-tech]

Hello Mattes,

thanks for your reply.
I got an spirit2 unit wired as shown in your diagramm. using an other plug solved my problem, don't know why.
for now i use the f.bus protocol, which runs fine but no integration at all on my x20s.

if anyone know to solve the integration problem, i'll be very happy.

regards

[Mattes61]

Hello,
if you have firmware 3.6.2, I believe that you have no telemetry -

Do an firmware update back on 3.6.1 and you will have Integration back again -
There is an thread of me with the problems with firmwareupdate from 3.6.1 to 3.6.2 here in the board:
https://www.spirit-system.com/phpBB3/vi ... =20&t=6078

This is an known issue and will be fixed with 3.7.0 that we will get in a few days as Tomas said -

What version of ETHOS are you using ? I am using on my Horus X10S Express the new 1.57 and the integration works fine -

Regards

[ZeXx86]

Hello,

the issue is related only to YGE ESC telemetry. So there should be no problem that is related to this thread.

[ZeXx86]

Hello,

can you verify that you can see any Spirit telemetry sensor?
If FBUS is working it should all work. FBUS is also recommended protocol.

[nano-tech]

HI,

i can see about 10 or 12 items at telemetry, don't know the exact ammount at the moment.
but got no integration.

switched to f.bus in spirit 2 unit and f.bus in the receiver.
checked 16 channel settings in transmitter and receiver.

no further idea

thanks for your support