Adrian Olsen

I’ve been trying to source a LokProgrammer, but all the obvious UK-based retailers seem to be out of stock. Does anyone know of a source in the UK where I might obtain one (new or used?) Thanks

Hi Nik, the problem was solved by swapping the polarity of the programming wires coming out of the DCC Command Station. I’ve no idea why that fixed it (I thought test-boards with polarity agnostic), but it did and all now working well

I’ll try that and let you know, Nigel….stand by…… thanks again for the tip. it certainly wouldn’t have occurred to me to try it ! 😳

Ok, this MYSTERY SOLVED. Nigel’s suggestion came up trumps! I switched the polarity of the Programming leads into the Test-Board, and bingo! All fine now. 😃👍🏼 What’s strange is that I understood that Test-Boards were polarity agnostic. Anyway, all’s now well, and the decoders are now being Read with ease ! Thanks to all for the input (especially Nigel 👏👏👏)

To provide a bit more explanation, I attach three photos featuring a RAILS 21 Pin decoder. The one on the left (showing Loco Address 3) is plugged into the Digitrax DCS Mainline connections. It is running perfectly, with the motor responding to controller commands. The middle photo is trying to read CV8 with the Programming connections attached to the ESU Board. As you can see, all the Function lights are illuminated, but what you can’t see (but is happening) is that the motor is running at max revolutions! Then the Read procedure times-out with an error message and no CV reading. Finally, the photo on the right is using exactly the same Read procedure but on my friend’s drM Test-Board. Result, a successful reading of CV8, reporting 36 (DCC Concept’s NMRA Code). As I say, all very odd, and not a little frustrating!

No, Railcom not involved. I’m not using the Z21 either…my DCC system is Digitrax (DSC210+)

Thanks Rob, see my reply to Steven, above……. Someone else has mentioned the ‘coreless motor’ issue to me too, but then why would they run successfully when I switch them from Programming Mode to Normal Running Mode? I’ve also posted a question on the ESU Forum…..I’ll report back if I get anything from there.

Thanks Steven This motor runaway is happening with both 8 and 21 Pin RAILS decoders (made by DCC Concepts), indeed several of each ! I’ve also ensured that they’re connected to the Board the correct way around, so I don’t think that’s the cause. Indeed, when I run them ‘on mainline running’, they behave perfectly, its only when I try to READ the CVs in the Programming Mode (with the programming wires connected) that the runaway happens……as I say, its all very odd. I haven’t yet been able to try it on another DCC system, but that’s my next step. For the record my Test-Board is the 53900 version.

Thanks for your relplies. Yes, this remains a mystery at present. I’m totally baffled by the behaviour of these decoders on the ESU Board. More investigation needed.

I’ve recently bought a new ESU Decoder Test-Board. I have been trying to (re)programme and/or reset several previously used ‘Rails’ Decoders (made by DDC Concepts), both 8 and 21 pin versions. My Command Station is a Digitrax DSC210+ with a DT602 Controller. I am reasonably familiar with DCC and its workings. I’m not a newcomer or novice. Now, here’s the problem. 1. When testing the said decoders on the ESU Test-Board for normal running (on the main), they all work fine. The controller’s commands are activated by the decoder, with the Test-Board motor running and the Function lights illuminating, all as expected. Write commands are actioned too (in POM mode). 2. HOWEVER, when I then switch to Programming Mode (with an appropriate switch of power leads from the command centre) and then attempt to Read/Write any of the CVs, the motor just runs at top speed, all the Function lights come on, and the CVs won’t read or write. It’s all very strange, not least given the significantly reduced voltages used in Programming Mode. 3. When I try exactly the same Programming exercise on a borrowed dRM Test-Board, no issues. Read/Write executed with no problems. So my questions are thus: 1. Can the ESU Test-Board only be used for programming ESU decoders? 2. Has anyone else experienced the same issue? 3. Is there any reason why an ESU Decoder Tester would NOT work with a Digitrax Command System? Any thoughts or comments welcome, with thanks.

Thanks for this……my tests suggest it might be the DCS210+. 🫤

I have a DCS210+ with DT602 Controller. I seem to have developed a problem when trying to read/write CVs on the Programming Track (no issue writing with POM method). All has been fine up to this week, when things started to go awry. I’ve checked the wires from the appropriate sockets on the 210 into my decoder tester board (ESU) - all seem fine. When I try to read or write a CV, the decoder/motor runs off at high speed and won’t stop, nor will it read the requested CV. Only way to stop the run-away motor is to disconnect power and reset. Has anyone experienced a similar issue? Any observations and/or suggestions welcome. thanks

If its possible the loco is causing this issue, I will also try installing the decoder on my decoder testing board and see if that helps.

Nigel, thanks ever so much for this comprehensive response. I will follow up your suggested approach. Certainly, I’ve been able to READ other decoders on the Programming Track (and on JMRI) using this Digitrax combination - notably those made by DCC Concepts, so maybe its not the set up. This one is the only Zimo decoder I have; bought for a specific loco that needed a small 6 pin decoder. Anyway, I’ll try your very logical process and try to isolate the reason I’m struggling with this particular decoder. As I say, its all very frustrating. I’ll keep this thread posted on my progress (or lack thereof). All the best Adrian

Thanks for these replies. It would appear that I can Write to this decoder with the DT602, but it doesn’t Read CVs on the Programming Track nor on the Main. Is this a known issue with this Digitrax system? My Command Station (DSC210+) is connected to JMRI (on my PC) using the usual USB cable connected to COM3, and the DT602 is connected with a LocoNet cable to the Command Station. All very frustrating