Two thumbs up.
Pete.
Final update on Loksound issue. I contacted ESU in PA and got a quick reply via e-mail. Sent the offending decoder to them and six days later received a replacement. I installed it and all is working well. Great service from the Loksound folks! Thanks to all who responded to my issue.
Unfortunately it's not just model trains. Imagine having a half million dollar bulldozer sitting for almost 9 months waiting for a transmission controller. They replaced it once and the replacement quit within an hour. They have trucks waiting for parts too. Glad I'm retired. The poor mechanics are taking a beating from the bosses for stuff out of their control. With shortages the costs get multiplied by a factor of 10. Before I retired, a trucks brake job was under $100 a wheel. Now two shoes, hardware kit and drum is over $500.
Pete
During covid, parts became increasingly hard to source. In order to keep production up to some degree, components were sourced from where ever they could be found, which lead to some poorer quality parts that just didn't work as well as they should. We are still seeing the repurcussions of those inferior parts unfortunately.
Mark.
¡ uʍop ǝpısdn sı ǝɹnʇɐuƃıs ʎɯ 'dlǝɥ
I am hearing there were a batch of Walthers GP-9's with bad decoders.
Henry
COB Potomac & Northern
Shenandoah Valley
I still have some version 3.5 decoders that require the 100 Ohm speaker. And I also have the original blue case programmer too. I have also standardized on Loksound. The fact that they upgrade even the early programmer instead of forcing you to buy a new one is a testament to the loyalty to their customers. Unless the locomotive has a factory installed sound decoder, I will choose Loksound. Other brands may be as good, but the customer support is second to none. Slow speed performance, easy CV changes using the programmer, and choice of sound sets is great.
Good luck and hope it comes back soon.
Yes, I am glad it is just plug in and adjust CV's! I have used Loksound since version 3.5 and remember the task of hard wiring them! Aggh! I have had other decoders but decided to use only Loksound for consistentcy in programming and maintenance. I really like the "traction motor" sound in the 5.0's! With a LokProgrammer adjusting CV's is relatively simple and I particularly like the low-speed characteristics of these decoders. The defective decoder is in the mail! Appreciate all the help from the forum.
trnj Well, ESU already contacted me and instructed me to send the decoder back for a replacement. End of this saga!
Well, ESU already contacted me and instructed me to send the decoder back for a replacement. End of this saga!
It's great that they are supporting their products. Shame that you have to go through the hassle. At least it's an easy plugin instead of a board replacement or a hardwired.
I am sorry you and others are having this problem and that's coming from a Loksound guy.
Is it a coincidence that Matt Herman left just as this started happening? Probably not.
When components were hard to find, they probably sourced a component, from our friends on the other side of the world that was not up to snuff.
I tried reading a good decoder and then writing it to the "invisible" one but the programmer simply does not "see" the decoder in the engine sitting on the test track and thus cannot write to it. All the plugs are secure and as I said, it works on other engine projects. Thanks though. I intend to call ESU in PA when their troubleshooters are answering the phone Thursday. I also plan to call the guys at Yankee Dabbler, a great bunch, to see if they have any suggestions. I purchase all my decoders from them. Til then, I am done trying! I do have an older Atlas S-2 I might steal a decoder from until the replacement comes. Really like the Bowser Baldwin VO 660 I just bought, decaled and weathered in anticpation of putting a decoder in. Sigh!
My thanks to all who responded! Much appreciated.
Hi trnj,
Based on how thoroughly you have checked the LokProgrammer this is not likely to be the cause of your problem, but I had the same thing happen recently. I discovered that the plug on the programming track had come loose.
Cheers!!
Dave
I'm just a dude with a bad back having a lot of fun with model trains, and finally building a layout!
trnj I think the decoder is good but something happened that makes it "invisible" to the programmer.
No, I think your decoder is what as known as "bricked" DecoderPro is not the cure. This has been happening with increasing regularity with people using the Lokprogrammer and V5 decoders; requiring a trip back to ESU. In the ESU forum there is no user fault that causes this, that I can tell. Sometimes simply changing the address will kill the decoder.
Someone said reading the exact same model of a good decoder then writing to the bad decoder might unbrick it.
Thanks to all who replied to my question. Good advice from all. (1) Yes, the LokProgrammer responds to my other engines very well. (2) I do have the latest update from ESU for the programmer. (3) I removed the decoder and checked all my solder joints with a multimeter with the pins on the decoder buddy. Continuity is confirmed and the engine did intially work on the test track. (3) I did attempt to confirm the exact dedoder since I use the 21 pin 5.0 as well as 5.0 micro for some engines. But, alas, the programmer will not recognize the decoder, even after I confirm that it is indeed the proper one. The programmer simply does not register that a decoder is present. I get the exact same result when having no engine on the track to test! Thanks just the same. I think the decoder is good but something happened that makes it "invisible" to the programmer. I do not know anything about Decoder Pro but perhaps it would recognize the engine,
Ensure you have the most recent version of the LokProgrammer software. Older versions may not recognize the firmware of a new decoder.
Additional troubleshooting tips here: LokProgrammer Troubleshooting
As always, clean track and wheels are important.
Make certain that you have the EXACT decoder model in the toolbar dropdown showing:
Lokprogrammer by Edmund, on Flickr
Sometimes I've opened an older file for a locomotive that I've upgraded from a Loksound Select to a Lok-5 and I'll get the 'does not recognize' or 'Not an ESU decoder' pop-up and can not continue.
Click the pulldown menu and see all the choices of decoders. They have to match what you are trying to program exactly.
Good Luck, Ed
It sounds like you tried other LS decoders and they read fine. Am I correct so far?
Check the offending locomotive for a disconnect to the motor, and track. Sounds like you may have a bad solder joint.
I just installed a Loksound 5.0 21 pin decoder using a Decoder Buddy Mini (so easy!) and then began a download of sound files on the LokProgrammer. The decoder performed properly, with lights and sound functioning and with the loco running both directions on the track. Then while adjusting the CV's for volume and running characteristics, I got the message "No supported decoder could be found." I attempted to return to default configuration usinf CV F-8/8 to no avail. Then I attempted a firmware update but the programmer would not recognize the decoder. The programmer works with other Loksound decoders previously installed including the 21 pin and some "wired" micro-decoders. And, yes, it was wired correctly. It worked well for a few minutes! Now it will not run at all, either using #3 or the number assigned by me. Any suggestions would be appreciated.