-
Notifications
You must be signed in to change notification settings - Fork 166
User Guide: Spektrum Binding
**Note: this process requires a recent bootloader (0x83) due to delays from earlier bootloaders. It will also not work on boards without a USB Sense connections such as FlyingF3 and FlyingF4 **
Binding satellite receivers can be a tricky process, to find the combination of bind pulses and protocols that produces a good signal. This difficultly comes from the fact the protocol is not well documented, nor are the receivers. If possible, it is much easier to use the traditional bind procedure your transmitter recommends with the satellite attached to a standard receiver.
Start GCS with your controller connected. Go to [System tab], in the left pane go to [Browser] > [Hardware settings] and set the DSM bind value to a non-zero value (e.g. 3). Save your settings. Note: The DSM bind value and prototype (e.g. DSM2 or DSMX 10-bit) are not critical for this step - any combination of settings should be capable of getting your satellite receiver into bind mode.
Disconnect your USB cable. Connect battery to your ESCs to power the FlightController (ensure that the ESCs are connected to your board). On power up the LED on your satellite receiver should start blinking rapidly, indicating that it is in bind mode. Note : After connecting the receiver, If your satellite receiver LED does not start blinking, then it did not enter bind mode. One potential cause of this problem is bootloader latency. To enter bind mode, the satellite receiver needs to receive a series of pulses within approximately 100 ms of receiving 3.3V. Most boards can not separately control the VDD provided to the satellite receiver, and so it is important that the delay introduced by the bootloader and firmware loading is on the order of 100 ms or less .
If you successfully entered bind mode on the satellite receiver, power on your TX in bind mode and wait for the blinking LED to turn solid. Turn everything off, reconnect the USB and set the DSM bind value back to zero. Power cycle the controller and then turn on your TX. The satellite receiver LED should be solid. If it blinks then it indicates that your TX was turned on before your controller - retry with the TX initially turned off. Enter the input configuration wizard and check if GCS responds to your TX controls. If not, then it indicates you need to experiment with port settings for the receiver
This is a list of known good combinations, originally sourced from the OpenPilot wiki
Transmitter | Transmitter settings | Satellite Receiver | Port setting | DSMxBind value | Result |
---|---|---|---|---|---|
DX10 | Lemon Satellite | DSM2 | 9 channels | ||
DX8 | Frame rate DSMx | Spektrum DSMX | DSMX (11-bit) | 9 | 8 channels |
DX8 | Frame rate DSMx | OrangeRX | DSMX (11-bit) | 5 | 8 channels |
DX7 | OrangeRX | DSM2 | 5 | 7 channels | |
DX7 | Lemon | DSM2 | 2 | 7 channels | |
DX6i | OrangeRX | DSMX (10-bit) | 5 | 6 channels | |
DX6i | OrangeRX R100 | DSMX (10-bit) | 3 | 5 channels | |
DX6i | OrangeRX R100 | DSM2 | 3 | 5 channels | |
DX6i | JR Remote Satellite Receiver | DSM2 | 5 | 6 channels | |
DX6i | Spektrum AR6210 receiver | DSMX (11-bit) | 9 | 6 channels | |
Dx7s | Frame rate DSMx/ 11ms | Spektrum DSMx | DSMX(11-bit) | 9 | 7 Channels |
The JR DSM2 is fully compatible with the Spektrum DSM2, so the settings should be identical.