Spektrum release paper on 3rd party integration

I saw that they released their document on 3rd party integration. Not sure if it can help the Deviation project or not.

www.spektrumrc.com/ProdInfo/Files/Remote...facing%20Rev%20A.pdf

They also mentioned contributing codes to Cleanflight and Raceflight recently.

i think deviations protocol is probably what this was aimed at, i remember reading a while back on rcg a post by one of the spektrum devs stating that the guys who reverse engineered the protocol still had some things wrong, this perhaps is a way of them finally helping out?

I think they just see they are loosing market share they must show ther goodwill and this is already reverse engineered anyway, so no real secret.
They are aware, it is no longer the case that Chinese RC is not accepted....It is proven that many cheaper brands are reliable and there is a mass market with all those drones.

Same for open source community, almost all flight controllers are open source and TX are moving that way, future is bright for Open Tx Deviation etc etc.
If Spektrum would be open source and implemented all ideas from the community, they would have been the biggest RC vendor now.

They could still do plenty of stuff, f.i. make a nice " open" flight controller, with onboard RX and telemetry functions. Maybe starting some of those open project more people will buy again spectrum Tx.

Myself, I try if possible only use open source projects, from esc, to RC, to flight controller etc etc.

In recent weeks, they have formed a FPV team. Released FPV Mini X racer more like the DIY hobbyist are building. As well as a host of components... motors, ESC and FC. I think they just want to ensure Spektrum link is done right so it's reliable. So by contributing code and making pull request to Cleanflight and BetaFlight, they ensure their stuff works well. Glad to see that happening.

FDR wrote: I think this is only the "protocol" used between the satellites and the rx or flight controller...

You're probably correct. I only learn about it when the DTFc guys didn't put an obvious 3.3v pad. And ppl were calling it a fail or looking for 3.3v points to tap into.

They replied with the location for 3.3v. But not recommended to run Spektrum SAT because of the closed nature and not implementation guidelines from Spektrum. Then someone that I assume is from Spektrum chimed in saying they got that implementation guide I linked to above. And have started contributing codes to Cleanflight and BetaFlight.

Yup, this is the satellite protocol, which had also been reverse engineered, which is how it got into various flight controllers as well as cloned Rx's.

Spektrum also switched to an open protocol designed for use with flight controllers.

All in all, I'd say this was a good sign. Unfortunately, they probably won't release the specs for the RF Module/MCU interaction used by deviation, because that's really an internal protocol and not one normally visible to the end user. But we can hope!

Spek guys are working on Raceflight too.