I have an ESU LokSound Select Micro DCC Sound decoder, and about three months ago there was a weird sound file on the N scale SD-26 that I had. I tried to run the locomotive, but it would not respond to ANY commands, whether light, sound, motor control. I tried all addresses (the actual address, address 3, etc.). Nothing worked. I tried to reset the locomotive using CV8 = 8 and that did not work either. I have a LokProgrammer as well, and I even tried resetting the sound file, and that did not work because the program said that I could not load a V35. or version 4.0 sound file onto it. I'm confused because I got this decoder about four years ago. It has to be a V3.5 Select Micro, but the LokProgrammer doesn't do anything to program it. I read the files on the decoder using the LokProgrammer, so I know the LokProgrammer is detecting it. My PowerCab NCE DCC system is not detecting it for whatever reason, saying "Cannot Read CV." The sound file is for my SD-26. Can anyone provide any insight as to how I can get the sound to work again and to load the right sound file? Whenever I read the decoder information on the SD-26 using the LokProgrammer (of which I downloaded and installed the latest version 5.0.7), it says the following (of which I cannot copy and paste): Manufacturer: ESU Model: LokSound Select direct / micro Flash: 32 Mbit Manufacturer ID: 00000097 Product ID: 02000080 Serial Number: FFC5D853 Sound Lock: Unrestricted Firmware Version: 4.17.9249 (7/4/2018) Firmware Type: MutliDcc Bootcode version: 0.2.32 (6/9/2015) Production info: FFFFFFFF Production Date: 11/23/2015 Like I said, I cannot read or write CVs using the LokProgrammer. Please help!
You cannot load a V3.5 or V4 sound project, since the decoder is a Select. You need to try loading a Select project (they are different formats) With the LokProgramer, try forcing a microcode update. That may help “wake up” the decoder, if Reset doesn’t work. Did you use the Reset command from within LokProgrammer? (Not really sure what you meant by “resetting the sound file”: a Reset is at the decoder level, not the sound project level, and does not erase the current sounds.) After sending the Reset, remove all power to the loco, and then reapply power to check.
Rick, I'm glad you chimed in good sir! I loaded a sound file that took about 26 minutes, but the locomotive still will not respond to any command on the LokProgrammer or the NCE DCC system. I loaded a 75858 for a 567D3 engine sound, and that seemingly did nothing. I tried to do a reset, and that did nothing via the LokProgrammer.
I also tried to turn on the lights and sounds using the decoder tester of of the LokProgrammer, and that did not work either.
If your Power Cab reads back can’t read CV- usually means there is no power getting to the decoder.Try attaching some jumper leads right to the decoders red and black track leads- eliminate the loco drive wheels etc.
It is very weird. Usually, if you can read, the decoder info, you can read else where. In LokProgrammer, the two things to try is " Programmer | Reset Decoder " and " Tools | Update decoder firmware " . Both of those should "wake up" the decoder. Your decoder info shows the most recent firmware level, but you can force a refresh of it. I guess the other question haven't asked: are there stay-alive capacitors attached to the decoder? If yes, disconnect temporarily.
Have you tried to down load a different sound file to the decoder-use jumper leads. What comes up when the ESU programmer does this-
The LokProgrammer said the decoder firmware was already up to date, but I refreshed the firmware to try to wake it up as Rick said.
This is very strange. I updated the firmware and loaded another project onto it, and it will still not respond to commands from the LokProgrammer using the Decoder Tester function. I cannot turn on lights, blow the horn, nothing
I think something is wrong with the wheel material. I have cleaned the crap out of them, but I don't think electricity is getting through. I did a conductivity test, and it's hit and miss. Sometimes it works, sometimes it doesn't. The wheels look like a dirty brass color instead of like a polished silver color.
So somehow it worked for a about 30 minutes, and I ran the locomotive around the layout. However, when I took it off and tried to read the CVs using the LokProgrammer again and used the Decoder Tester of the LokProgrammer, there was a different sound on the decoder, AGAIN! It was not the 567D3 sound, but some other sound file. Either the decoder is hosed up somehow or the sound file is corrupted (which I downloaded directly from the ESU website). This is very frustrating.
So I even loaded a new sound file, and I cannot get the damn thing to play back or make the lights go on using the LokProgrammer. Either I'm doing something wrong with the LokProgrammer or the sound files, every one I've "loaded" so far, do not work. It took me 25 minutes to load another sound file.
I don't understand why and how the LokProgrammer can read the decoder information yet fail to read CVs on it.
If I can't reset the decoder, if I can't read CVs either using my PowerCab or the LokProgrammer, and the decoder seemingly won't take new files, can the assumption be made that the decoder is dead? If it's dead, then why can the LokProgrammer still read the decoder information (not CVs) under Read/Write CVs ---> Decoder Information using the LokProgrammer? If when I replace the sound file with another one, why would it not stop the process in about 1 minute if the LokProgrammer can't detect a decoder? I'm about done with this stupid decoder and might get another one.
Several un-awnsered questions? Did you use jumpers to the decoder (this eliminates wheels chassis and other places where poor contact is ) I have see wheels where the nickel plating has worn down to the brass, very poor conductor! The caps are a PITA to dis connect , did you dis-connect them?
I did use a jumper on one side, but I don't have two jumpers. I have not disconnected the caps because it worked for about 30 minutes (I ran the loco around my layout for that long, and it worked great). As soon as I took it off and tried to read the CVs again using the LokProgrammer, it went back to some random sound file that sounded nothing like a 567T engine. I have new wheels coming to me from Atlas. Once I replace those, I will see if that fixes the problems.
