Konrad
Very Strong User
OK so this was a XPS issue and not a FrSky. So why is it listed as a FrSky concern in the OpenTX header notes? I'm not one to follow issues for products I don't use.
www.open-tx.org
So to be clear this has nothing to do with FrSky or the use of FrSky products as approved by FrSky? Jim Drew doesn't have a license from FrSky to use the ACCST protocol?
So this is a case of FrSky getting tainted by the clones.
Quickly getting lost here! (I'm not about to spend time at RCGoofs! Is this issue covered at GIT HUB? Is there an intelligent discussion of the issue? I'm looking for a statement from FrSky/OpenTX that would say this PXX issue does not apply to FrSky hardware as it is intended to be used. FrSky's poor understanding of the data packet issue that drove ACCST v1 to ACCST v2 really has me uncomfortable with any and all FrSky RF engineering)
OpenTX 2.3.10
www.open-tx.org
So to be clear this has nothing to do with FrSky or the use of FrSky products as approved by FrSky? Jim Drew doesn't have a license from FrSky to use the ACCST protocol?
So this is a case of FrSky getting tainted by the clones.
Quickly getting lost here! (I'm not about to spend time at RCGoofs! Is this issue covered at GIT HUB? Is there an intelligent discussion of the issue? I'm looking for a statement from FrSky/OpenTX that would say this PXX issue does not apply to FrSky hardware as it is intended to be used. FrSky's poor understanding of the data packet issue that drove ACCST v1 to ACCST v2 really has me uncomfortable with any and all FrSky RF engineering)
Last edited:
