-
Notifications
You must be signed in to change notification settings - Fork 11
1 Hardware Software Requirements
Two different classes are supported with different LUA software for each category:
- Taranis type: X9D, X9E, QX7, X-Lite, Jumper T12 and
- Horus types: Horus 12,Horus 10, Jumper T16, Radiomaster TX16s
The transmitter must be running OpenTX 2.2.4 or later and have firmware with both lua and luac support (select the other options as desired). Update the transmitter firmware if necessary using OpenTX's Companion program.
The receiver must be fully Frsky compatible, supporting bi-directional SPort or FPort telemetry communication.
Note: while most Frsky receivers have SPort capability, those with early versions of their software may not be fully compliant. Be sure that they are running the latest Frsky firmware for that receiver type.
Only a few receivers currently support FPort: the R-XSR, and the R9 series. The beta software for the XSR and X4R and other receivers does not function. Use them in SPort configuration.
SPort: XSR, R-XSR, X4R, X6R, X8R R9mm, R9mini
FPort: R-XSR, R9mm, R9mini
FPort2: Archer series
Any autopilot running ArduPilot firmware dated after November 2020 has support for these scripts using Sport, Fport and recentely FPort2. Note that current stable releases may not support this unless they were dated after this date.
Some autopilots' UARTs can be configured to connect to the receiver's SPort or FPort pin directly, while others may need a bi-directional inverter or cable. See here for more information.
The autopilot should be configured for Frsky passthrough if using Sport or here if using FPort.