126
Troubleshooting Intermittent Horn/Whistle With Wireless
Throttle function 2 activates the horn or whistle of a sound decoder. It is given special priority in
the hierarchy of software within the Command Station because it literally tests the absolute
response time of the entire DCC system.
With thousands of installations of EasyDCC wireless equipment, it is impossible to create an
exhaustive list of all causes of this symptom. So, we'll start with the most common cause and
work downwards towards the least common. In all cases, all of these causes result in exactly the
same symptom – the horn/whistle shuts off before commanded to do so.
Cause #1: Specific to QSI decoders
As delivered from the factory, there is an incorrect value programmed into CV11, which is the
DCC packet timeout value. For proper operation of the horn function, CV11 must be
programmed to a value of 0. Use either the programming track or OPS programming to change
the value.
Cause #2: Duplicate Wireless or Tethered Throttle IDs
All throttles must have a unique ID number programmed into them. ID programming is not
obvious but we have been surprised how many operators have accidentally changed the ID. It is
also possible that a plug-in throttle might have accidentally been assigned an ID within the
wireless throttle range. Use the Command Station diagnostic tools (SHOW ID, etc) to verify
proper and unique IDs for ALL throttles.
Cause #3: Duplicate Wireless Frequencies Used
For each XF-Series wireless receiver, it can accept up to 8 throttles each on their own unique
frequency. Each throttle must be set for SCAN mode and each throttle must set to its own
frequency.
For RF1300 throttles, the throttle can only be received by an XF-series Group-1 receiver. Inspect
each DIP switch setting and confirm no two throttles are on the same frequency and make sure
the.
For T9000 throttles, verify that each unit is on the desired frequency without duplicates.
Cause #4: Loss of Signal – Reception Black Holes
When a wireless throttle loses contact with the wireless receiver, the command station has
special software routines that protect against horns and whistles being stuck on. This occurs
when the operator pushes the F2 key, and then steps into a poor reception area. When this
happens, the Command Station no longer receives the throttles signals but knows that the F2 key
was previously command ON. After a period of NON-RECEPTION, the command station turns
off the horn automatically. The solution to this cause is simple, improve the reception. This can
be done by repositioning the receiver or by adding additional receivers in areas known to have
reception problems.
Cause #5: External Jamming of Frequencies
Somewhat related to #3 and #4, this cause is a bit more difficult to assess. The most common
symptom will be one throttle that always seems to have trouble. This is usually a sign that an
external jammer has rendered the frequency unusable. Your only solution is to remove the
jamming source after confirming your own equipment is not the cause (see #3). If your
equipment is OK and you can not locate or disable the jammer, you must declare that frequency
unusable and move to a different frequency. There are some guidelines related to jamming in the
orange Operation manual.
Cause #6: Transmitter Congestion at the Receiver
This cause is not very common so it is listed last. For this case, the cause is the physical proximity
of several transmitters to the radio receiver. Initial installations where the receiver is simply
placed near the command station and connected with the modular cable are where this cause
usually pops up. This is why the orange Operation manual includes suggestions for how to find
the best location.
To Next Page
Loading...
Need help?
General