OpenTX FrSky integration S-Port (un-inverted/inverted)

[Mattes61]

Hi Tomas !
I'm a bit confused now, no integration cable is necessary with SpiritPro at all?
That would mean a normal connection from SBUS to RUD and only SPort to the middle PIN of the Sys interface? Did I understand that correctly now ? Or do you mean only cable assignment on the Sys-Port like first Pin GND second PIN SPort and third Pin Signal from SBUS ?

What kind of firmware is then necessary on the receiver? Sbus/S.Port version D16 V1 or D16 V2.1.0 ? I think it probably won't be an FPort firmware?! That would be great information now, because I plan a similar use with FrSky receivers -

Thanks a lot for your answer !

Regards
Matthias

[ZeXx86]

That would mean a normal connection from SBUS to RUD and only SPort to the middle PIN of the Sys interface?

Yes, this is correct. But only in case of inverted signal it can work.

[jasc]

S.Bus and S.Port are both inverted protocols. That relates to what is considered 1 or 0 a high or a low. The Frsky Standard is inverted signal levels, but in Frsky words its of course "uninverted".
So any Input-pin that is supposed to accept SBus or S.Port has the correct inversion so it works.

Ports that are multi-functional (like the SYS port on Spirit or Copter flight controllers UART) dont have this inversion. Some processors (F3, F7,H7) have a built in inversion that can be set by software. But others dont have that.

Frsky aknowleded that some time ago and offered pins where you get the "uninverted" signals for SBus and Sport/Fport. Well, Frsky sometimes calls this inverted SPort. And now you have all the confusion that is needed...

So, from my point of view:
Spirit doesnt have a software inverter. So you need a hardware inverter (the integration cable) or you have a receiver with an "uninverted" S.Port pin. R.XSR e.g. also have a tiny tiny pin for that.

[ZeXx86]

Yes, that is correct.
Spirit Pro has embedded inverter for SBUS but not for FrSky cable.
Spirit GT has inverters for everything.

[Dudemeister]

Well, I tried it again with the R161, and it didn't work, so it's probably an issue with the un-inverted pin location, it's not where that image points to, but I have an RX4R somewhere, and that has a dedicated un-iverted solder pad (well, it's inverted in FrSky parlance, but we all know they're the ones that are backwards). I'll try that one when I find the receiver.

It's good to know the Spirit Pro does support a standard un-inverted signal directly. I'll report later when I get it installed

[Mattes61]

Hi Mattes61,

When I said I wanted to do this with a single cable, I wasn't talking about using a single cable for S-BUS and Telemetry, the only only Spirit unit that can do that is the Spirit GT via F.Port, and the R161 only support F-Port v2 and the Spirit GT wants F.Port v1.

Hi Dudemeister,
one hint to your statement that SpiritGT needs F.Port v1 - Then I say, only when I flashed F.Port v2.1.0 on the R161 did the telemetry work, with F.Port V 1.0 nothing worked at all! I connected an R161 directly to the SpiritGT on my XLPower520 and it works perfectly -

See also an interesting video of John on Youtube (RcVideoReviews), here the link:
https://www.youtube.com/watch?v=jJk7NxI ... deoReviews

Maybe you should flash the firmware Sbus/S.Port - D16 v2.1.0 on your R161, with your SpiritPro configuration, maybe then it works too ?! Flash the R161 and test it - I think this is the solution - If it still doesn't work, then at least it's worth a try!

Regards
Matthias

[Dudemeister]

Are you saying the information in the online manual is wrong or out of date?

No matter, the GT is already wired and working fine on another bird. The question here was about the Pro, which doesn't support F.Port.

Also, as you can see from the video you linked (which BTW is for the iKON FBL, not the Spirit), F.Pport v1 on the R161 will provide channel command signals only, no Telemetry.

v2 will provide Telemetry, but according to the manual, f.Port v2 is not supported, unless you know something we don 't?

[Mattes61]

Hello Dudemeister,

I have proofed that my statement is correct for F.Port V2.1.0 in this thread and there is nothing more to say believe it or not -
Just use the search function in the forum, you'll find my thread there - if you don't feel like it, then just don't do it -
Regards

[ZeXx86]

Hello,

there are two different versions labeling from FrSky for F.Port. Spirit units have full support for F.Port that has public documentation.
It works with ACCESS F.Port 2, yet we can't guarantee all will work, since there are so many receivers we simply have not tested all.
Moreover some FrSky receivers are implementing only partial support for F.Port, some very old receivers without telemetry or integration support.
F.Port v1 has full support for telemetry and integration.
Please note there are at least F.Port v1, F.Port v2, F.Port v1 2.0.
In any case you will get full telemetry and integration if receiver has support for this with F.Port.

[Mattes61]

Hello,
below is the link to my thread at the time, where I had the topic with the R161 and its firmware - (Configuration with the SpiritGT and F.Port use) - the fact is, only with the firmware for F.Port use - D16 v2.1.0 (Radiomaster) did I have the corresponding success that that worked with the telemetry! This is an ACCST D16-Firmware and no ACCESS-Firmware !!

The whole time it was all about the R161 - anyone who likes to try it should do it - the name of the firmware is as it is, but it works!

The idea was then simply that you could try the firmware for Sbus/S.Port - D16 v2.1.0, the whole thing can be reset to the original version without any problems - nothing can break, so there's no reason not to test -

Here the link to the problem at that time with the firmware of the R161 (Radiomaster):
https://www.spirit-system.com/phpBB3/vi ... 1&start=10

Greetings
Matthias