I need some help from this august body of experts. The other day I fired up my Digitrax DCS 240 to run some trains and my DT402 started to beep continuously. I tried powering the system off and on again to see if rebooting the command station would fix it -- no dice. In addition to beeping it would not allow me to acquire a loco -- not that I expected it to, mind you. At this point the throttle was plugged into my DCS 240. I tried plugging it into my 2 UP5s to see if I could get a different result at either location -- same thing happened. I then tried my DT402D to see if the wireless throttle would work. While it also beeped continuously, it did acquire the last loco stored on it, which happened to be on the tracks. I could control all the sound functions and direction, but the throttle constantly increased the speed of the loco without my turning the knob. While I could dial it back, once I stopped dialing the speed down, the throttle began increasing it incrementally again.
I checked for stuck buttons on both throttles and double checked all of the loconet connections -- all appear fine. Since it's happening to both throttles and on all of my loconet outlets, I'm assuming there must be an issue with the DCS 240. The last time I ran trains was about a week ago with no problems. I keep looking for info about continuous beeping, but have yet to find an answer. Any thoughts?
That sounds like two throttles selecting the same loco. Just use the loco reset button on the front to clear it out.
If it still happens - unplug all the loconet cables from the DCS240 and plug in a throttle right to the front panel. If that works, you have something messed up in your loconet wiring. Connect one wire at a time workign away from teh DCS240 until the problem happens again, the issue is then between the last connection that worked and this last piece you added back in.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Sure enough both throttles did have the same address programmed. Sometimes it's the little things that get us!
Thanks!