User Manual

O
PERATING MODE
:
LED and Buzzer:
Button1 – ID change
Button2 – When pressed during operation for more than 3 sec the output power is reduced to 1mW for a range check.
When pressed during power on a binding procedure will be initiated
When pressed shortly 3 times during normal operation changes working modes
Buzzer – – beeps 3 times on power ON after detecting PPM signal on the PPM input
LED Single blinks - DSM2, 1024, 22ms
Double blinks - DSMx, 2048, 22ms
Auto – constant ON.
Functionality:
Power ON:
When powered up the module is waiting for valid PPM signal to be detected.
As soon as PPM signal is detected the buzzer generates three short beeps (0.1s) indicating that the system is ready.
When module starts transmitting RF packets red LED is will blink according to the working mode selected.
Binding procedure:
After power ON with the Button2 detected pressed and valid PPM signal present the module generates three sort beeps and
enters binding procedure.
The module sets output power at 0.006mW and starts binding procedure. Your receiver will be bound in the mode based on:
Your receiver capability
Number of channels provided by your radio via PPM signal
Working mode selected in your Tx module
After that the module generates three short beeps. If the bind was unsuccessful it generates one long beep. After binding
procedure is over the module enters the regular transmitting mode and stays in this mode until power turned off.
The settings for transmission will not be changed if the binding procedure was unsuccessful. If the binding procedure was
successful the settings will be changed to the new ones.
Please note: it is recommended to have at least 2 meters between transmitter and receiver (depending on conditions such
as WiFi signal presence) to have successful binding. If your binding was unsuccessful try different distance between
transmitter and receiver.
ID change:
Every ORX 2.4GHz Transmitter module has one GUID (Globally Unique Identifier), no another ORX 2.4GHz Transmitter
will share it. The ORX 2.4GHz Transmitter module still has a Change ID button as a safeguard.
This is provided for the near impossible case where another transmitter (not ORX) can control your model without binding.
This near impossible case could happen as there are other DSM2/DSMX system manufacturers and they could use the
same GUID.
When powered up with Button1 pressed the new ID will be generated. The procedure of new ID generation is initiated
regardless if PPM signal present or not. After detection of Button 1 pressed module waits for 3 sec then generated a new ID
and buzzer generates long beep(0.3 sec). After this the module waits until the button 1 is released. When button is released
the module detects PPM signal from the radio. In Spektrum mode following binding procedure is necessary.
Channel assignments:
Your transmitter’s channel assignments may not be the same as the JR/Spektrum receiver channel assignments. This
means the channel assignments on your DSM2/DSMX receiver’s case may not match the typical controls on your
transmitter (e.g., the JR receiver throttle connection may actually correspond to Futaba transmitter aileron output or settings
in your transmitter are AETR and your receiver or bind`n`fly model requires TAER option). You may need to connect your
servos into receiver ports with different labels depending on the brand of transmitter you are using. Alternatively, you may
be able to remap the transmitter’s controls to the corresponding DSM2/DSMX receiver channels if your transmitter supports
such a feature.
Fail Safe:
Fail Safe features are setup in your receiver. Please read your receivers manual carefully to setup this feature. It is very
important that you pay attention to the channel assignments. As mentioned above, on the JR/Spektrum receivers the
throttle is on the receiver’s CH1 (labeled as ‘THRO”) while the throttle output from your transmitter may actually be on a
different channel. You need to be certain that you have all of the controls hooked up to the proper receiver connector and
that all your controls are functioning properly before setting up Fail Safe