¿ªÔÆÌåÓý

ctrl + shift + ? for shortcuts
© 2025 Groups.io

DR5013 problem - it sees a short when there isn't one


 

I've been configuring two new DR5013's and almost had everything right when a new symptom developed -- a locomotive would run into the block for a foot or two, and then the DR5013 would act as if a short had developed. It would retry a number times and then stop - sending a "Global Power Off" message on the LocoNet. I put a RRampMeter on the DR5013 and it was showing .10 amps when the locomotive was not moving (and about 12.3 volts). As long the locomotive was not moving the power was fine (it's a sound loco with a LokSound V5 decoder, and the sound continues to run). As soon as gave ANY throttle (even only 1 notch), the DR5013 would shut down. Pressing the Reverse button on the DR5013, turning track power off and back on would bring the power back, as long as the throttle on the loco was at 0. Thinking I had misconfigured it, I brought up the Configure program and reset it back to defaults. Same symptoms. I hadn't fully configured my other DR5013, so I reset that back to defaults and swapped it in. Same symptoms. I took the DR5013 completely out of the circuit (of course I can't run across the reversed joints), but the loco runs fine that way -- no shorts and never goes above 0.83 amps at 15.5 volts (with the loco running fast. Running slowly it stayed around 0.40 to 0.50 amps. With loco at idle, it was about 0.10 and with it out of the reversing block completely, it was 0.06 amp (just about what it takes to run the RRampMeter).

The environment is the main block is controlled by a Digitrax DCS240 (that's where the two reversing tracks are), the power disctrict has A DCS100 running as a booster. There are two LocoNets - one for the trottles, the UR92 duplex receivers and throttles. The seond LocoNet has a BDL168, a BXP88, and RR-Cirkits devices running the signals, Tortoises and panel buttons and LED's. There are 2 DCC Specilities circuit breakers on the DCS240 circuit, but the DR5013 are wired direct to the command station. The wiring is not new -- the DR5013 are replacing 2 DCC specialities reversers so I can get addtional information from the track (RailCom feedback). My JMRI has two LocoBuffer USB's to connect to the layout (JMRI is what controls the signals). I have never connected more than one DigiKeijs device to the computer at the same time, and the DR5013 Commisioning manual indicates that that is permissible. The LocoBuffer's are Opto-Isolated, so they should not cause problems.

I'm completely at a loss here - does anyone have any suggestions? Do I have a configuration issue (I don't see how as I have reset them back to default, and they both behave the same way). Or do I have two that have failed the same way?

Scott Walton


 

¿ªÔÆÌåÓý

Scott

I have 2 x 5013 and I see this fault regularly, at least once a week and I have moved the 5013 to where I can press the reset button easily.

Iain


Iain Morrison

07767 456746


From: [email protected] <[email protected]> on behalf of Scott Walton <jscottwalton@...>
Sent: Saturday, May 16, 2020 3:48:59 AM
To: [email protected] <[email protected]>
Subject: [Digikeijs EN] DR5013 problem - it sees a short when there isn't one
?
I've been configuring two new DR5013's and almost had everything right when a new symptom developed -- a locomotive would run into the block for a foot or two, and then the DR5013 would act as if a short had developed. It would retry a number times and then stop - sending a "Global Power Off" message on the LocoNet. I put a RRampMeter on the DR5013 and it was showing .10 amps when the locomotive was not moving (and about 12.3 volts). As long the locomotive was not moving the power was fine (it's a sound loco with a LokSound V5 decoder, and the sound continues to run). As soon as gave ANY throttle (even only 1 notch), the DR5013 would shut down. Pressing the Reverse button on the DR5013, turning track power off and back on would bring the power back, as long as the throttle on the loco was at 0. Thinking I had misconfigured it, I brought up the Configure program and reset it back to defaults. Same symptoms. I hadn't fully configured my other DR5013, so I reset that back to defaults and swapped it in. Same symptoms. I took the DR5013 completely out of the circuit (of course I can't run across the reversed joints), but the loco runs fine that way -- no shorts and never goes above 0.83 amps at 15.5 volts (with the loco running fast. Running slowly it stayed around 0.40 to 0.50 amps. With loco at idle, it was about 0.10 and with it out of the reversing block completely, it was 0.06 amp (just about what it takes to run the RRampMeter).

The environment is the main block is controlled by a Digitrax DCS240 (that's where the two reversing tracks are), the power disctrict has A DCS100 running as a booster. There are two LocoNets - one for the trottles, the UR92 duplex receivers and throttles. The seond LocoNet has a BDL168, a BXP88, and RR-Cirkits devices running the signals, Tortoises and panel buttons and LED's. There are 2 DCC Specilities circuit breakers on the DCS240 circuit, but the DR5013 are wired direct to the command station. The wiring is not new -- the DR5013 are replacing 2 DCC specialities reversers so I can get addtional information from the track (RailCom feedback). My JMRI has two LocoBuffer USB's to connect to the layout (JMRI is what controls the signals). I have never connected more than one DigiKeijs device to the computer at the same time, and the DR5013 Commisioning manual indicates that that is permissible. The LocoBuffer's are Opto-Isolated, so they should not cause problems.

I'm completely at a loss here - does anyone have any suggestions? Do I have a configuration issue (I don't see how as I have reset them back to default, and they both behave the same way). Or do I have two that have failed the same way?

Scott Walton


 

Unfortunately, this is not a problem that I can live with -- the loco might move 2 inches or so and then stop. I might put up with with once a month or so, but not whenever it moves!

Scott


 

I can now verify that it was NOT the DR5013. I swapped the PSX-AR back in and got the same problem. Turns out to be a track gremlin! There was a loco sitting on another track (not a reversing track), two blocks away. When that locomotive was moved away, the problem dissappeared. That area had recently been sceniced -- I don't know if that was releated to the problem. Now I just need to see what is going on in that area of the wiring. Then I can get back to making the short circuit pause go away (I was closing and throwing a non-existant turnout via a script, based on block occupancy and several other turnouts to do that). It will be interesting to see where and why the interaction with the other loco turns out to be.

Scott