I was making great progress in setting up my new decoder as I wanted. However, I did something (? ? ? ?) this evening that has mucked up the works. I have tried to reload the V5 sound file for a Challenger, I have tried to read the decoder and I get the following: "Detected decoder not supported". What the heck, anybody have a clue for me, is it correctable? Any info is appreciated. Regards, Carl
Try doing a decoder reset in LokProgrammer. And force a firmware update. May or may not work. do you also have JMRI? If so, on programming track, try to get it to identify the decoder. Sometimes JMRI can see the decoder while LP can’t. If JMRI can, then do the decoder reset from there (in program track mode, there is a menu option for Reset)
Thanks for the reply Rick. I am totally confused and turned off by ESU sound decoders. They are too complex, have no decent manual help and are costly. I'm ready to stop using sound all together. Now, I had read all info and saved on Decoder Pro so I just printed that info. The firmware version is 5.3.122. I am using Lokprogrammer 5.0.14 and this firmware is listed as supported. However, I tried a reset and no t supported is the message. That also applies to anything I attempt to do to the decoder. A strange thing is that on JMRI it recognized the decoder and in fact I had sounds, no motor movement but sounds. However, while silent the deoder pops and grunts very faintly like it is way off. ? ? ? Thanks again, Carl
Ok, if JMRI is recognizing the decoder, then the issue is probably a clean connection for the LokProgrammer. Make sure the wheels are clean, and the programming track is clean. If no motion, make sure you don’t have Drive Hold or a brake on. Cycle through the function keys to make sure everything is off.
With the V 5 You have to disconnect the decoder from power (Lift the loco off the tracks) for a few seconds before the new settings will work. I've also found that once you've gotten the Detected decoder not supported message sometimes it helps to unplug the power from the Lok-Programmer and restart the program. I like the ESU Decoders but i think they took a step backwards with the V5. Having he Next18 connector on all versions of the LokSound Micro 5 makes them thicker and harder to squeeze into many locos where the V4 fit with ease. The new V 5 LokSound micros have been a true disappointment for me to the degree that i now have several Soundtraxx decoders on my workbench instead of ESU LokSounds Decoders Sorry ESU I don't like to post negative reviews about any product. But they are what they are and my opinion is what it is. David
Thanks, my friends, for your responses. My face is red, worked on changing a radiator hose out in the sun today, but also because I caused my "not supported" problem myself. I started testing and programming this LS 5 with it connected to my ESU decoder tester via LP 5.0.14. All went well and was able to play sounds, change sounds and all the fun things. I, in some cases, was not seeing the expected results so I downloaded LP version 5.0.13 and moved my project to it and that's when the problem started. What I found is that the Sound file firmware 5.3.122 is not supported on the LP version 5.0.13. I deleted that version and went back to the LP 5.0.14 and everything works fine again. My bad, my stupidity. Carl
