TBS Crossfire telemetry integrantion

[minim]

We hope to include this in 3.3.1. Thank you for your patience

Did it get included? I tried flashing 3.3.1 to my Spirit GT now but I can't see it. I also have problems with using Sbus from crossfire now (no special cable) but on my Spirit II units this isn't a problem. Could this be due to spirit GT having some built in logic for inverted/not inverted sbus? I can select N.I.Sbus in my crossfire module.

edit: I can get it sorta working but there def is something wrong now with the channels. I got ch1 throttle, 2 ail, 3 elevator, 4 rudder, 5 gyro, 6pitch. In spirit now I have to set ch2 throttle, ch3 ail, ch1 ele, ch4 rud, ch5 gyro, ch6 pitch. The aileron is maxing out at 118% at mid stick but it works in left direction. Pitch I have to set to -51 (-100 is normal) to get it to -100 in spirit settings and I can't get it higher than 82% on max stick output. So it's not possible to fly it without aileron atm.

edit2: If I abandoned the wizzard and rebooted the spirit it somehow sorted out the channel mess again. Now aileron and pitch behaves like it should. I guess I just won't be able to run the wizzard then but it's better then not beeing able to fly it

[ZeXx86]

It was not included yet unfortunately. There are so many pilot requests and so many questions we are unable to make it working yet. We have to do everything at the same time, because then people are not satisfied without responding them.

Spirit GT should work in the same way as Spirit 2. Setup Wizard should not make a difference, but Futaba S.BUS must be selected to make it work.
Channel mapping should be at default - same for all Spirit units.

After reboot channel centers are calculated again. Maybe there was some channel out of range - default OpenTX settings are that it is out of range. So all channels must be configured to have +/- 87% travel range.

[minim]

Ok. No problem, was just curious if I missed it somehow.


Weird that I haven't had this issue with my spirit 2 yet but I will try as you suggested and run the wizzard with channels set at 87% of travel range. I think I'm down with 83% or around that to get -100 to 100 in spirit now but I always start fresh with transmitter at -100 to 100 so it would explain my issue. Futaba S-bus was set and it did work to some degree since some of the channels was ok.

[DjWang]

Is it safe to assume that I will need the FrSky integration cable for ųspirit if/when this feature is available?

[ZeXx86]

Hello,

it is very likely that no special cable will be needed for TBS Crossfire.
Fortunately window for adding the support is free, so I feel it will end up in 3.3 almost certainly.

[Michldigital]

Is TBS working incl. telemetrie?
Thinking about using my Mambo for the next heli

[jasc]

Your working on crsf integration?!
THAT IS GREAT

Hope to see it soon !

TBS made some big improvements with the new CRSFv3 radio link dropping to only few ms latency. And ExpressLRS is even faster but also using crsf protocol between receiver and flight controller and that for a fraction of the price of all commercial systems

See here https://theuavtech.com/rc-control-link-modules/

[jasc]

Could you please give an update on this

[slendrian]

Exciting news! Can’t wait [emoji3]

tx16s (+/- 83%) + tbs tx micro module + tbs rx diversity nano here.

Seems like TBS has some kind of cooperation with Radiomaster since they even sell tx16s in their webstore.

[jasc]

Hello,

it is very likely that no special cable will be needed for TBS Crossfire.
Fortunately window for adding the support is free, so I feel it will end up in 3.3 almost certainly.

Can you give a new timeline ?