ImmersionRC | EzUHF R/C Control System
20
Appendix B: Diagnostics
Problem
: Rx LED doesn’t light
Check BEC voltage and polarity. Power the Rx via USB temporarily, if this causes the LED to light, and
‘beat’ when the Tx is powered on, then the BEC/Rx pack should be tested.
Problem
: No response from the Transmitter
The transmitter should beep three times when the R/C transmitter is powered on.
If it doesn’t, try powering the transmitter via USB, if the beeps are heard when powering this way, the
cable between the R/C Tx, and the EzUHF Tx, should be investigated.
Problem
: Tx and Rx are correctly powered, but servos don’t move.
1.
Ensure that the R/C transmitter is not in PCM mode, this is a common mistake. The transmitter
must be in PPM mode in order for the EzUHF Tx to successfully decode the servo positions.
2.
Ensure that the UHF Tx and Rx have been correctly bound together. See the section ‘Binding’
earlier in this document.
Problem
: Tx beeps continuously, even when not in Bind mode
Beep codes can identify the source of the problem. Combinations of long, and short beeps will be
emitted, and can be identified using the following table.
_ .
Transmitter internal error, return for service (Xtal)
_ . .
Transmitter internal error, return for service (TxOvfl)
_ . . .
Detected PCM as opposed to PPM, change R/C Tx Mode to PPM
_ . . . .
PPM not detected at power-up (Tx connected to HT input?)
. . .
PPM Timeout, connection problem between R/C Tx and EzUHF
Common problems are
_ . . .
which indicates that the R/C Tx is in PCM mode, instead of PPM. The
EzUHF (and all other equivalent systems) require PPM as input, and not PCM.
Anoter common problem is
_ . . . .
which indicates that a PPM signal was not sensed, generally
indicating that the R/C Tx is connected to the wrong connector.