ESU LokSound Select Micro Trouble

DCESharkman Mar 17, 2019 at 1:15 AM

  1. DCESharkman

    DCESharkman TrainBoard Member

    3,474
    390
    45
    Hello,

    Well I think I have a bad decoder. I am using the LokProgrammer to save the sound profiles and I get errors saying

    upload_2019-3-16_18-12-56.png

    This was a Kobo installation. I have others that work just fine. So this was suing version 5 of the LokProgrammer, but the same thing happens on the version 4 of the LokProgrammer.

    All other locomotives are working fine.

    So I guess this one is dead, or is there some way to revive it?
     
  2. jdcolombo

    jdcolombo TrainBoard Member

    1,133
    192
    25
    Does the engine run? I assume not, but you didn’t specifically say.
    Is there a keep alive connected to the decoder? If so, disconnect it and try again.

    John C.
     
  3. DCESharkman

    DCESharkman TrainBoard Member

    3,474
    390
    45
    The engine does not run, and I am not sure about a keep-alive. The decoder was installed by Kato Kobo.
     
  4. jdcolombo

    jdcolombo TrainBoard Member

    1,133
    192
    25
    It is possible you have a bad decoder, but it is equally possible that the decoder isn’t picking up track power. I’d remove the shell and inspect the red and black wire connections. Use a continuity tester to make sure power is getting from each side of each truck to wherever the connection is for the red and black wires.

    If you have continuity to the red and black wire connections, then also check the connections to the motor. If those connections are OK, and the loco is still completely dead, then you probably have a dead decoder. KOBO should replace it, but be aware that the LokSound Select Micro is no longer in production. It is being replaced by the LokSound V5 (the V4 and Select decoders are no more, both replaced by the V5). And there is a rumor that the V5 Micro has a production problem, which has delayed its premier indefinitely. So it might be a while before you can get a replacement.

    John C.
     
  5. DCESharkman

    DCESharkman TrainBoard Member

    3,474
    390
    45
    Thanks John, I will see if there is a wiring issue. It turns out I have a few other units doing the same thing. What is strange is that the decoder ran just fine several weeks ago......
     
  6. jdcolombo

    jdcolombo TrainBoard Member

    1,133
    192
    25
    Hi David.

    If the decoder ran fine a few weeks ago, then I suspect you have an electrical problem. If the KOBO install uses a PC board for electrical pickup from the frame, this is the first place to look. Often these boards are just slightly loose, or get just slightly corroded, just enough to interfere with electrical continuity. If it worked in the recent past, the decoder itself is unlikely to have spontaneously combusted, and I’ve had similar messages on my LokProgrammer, all due to a bad electrical connection. Often it is a change in temperature/humidity that can cause this, though that should be less likely where you are. In the Midwest, it causes all kinds of issues!

    John C.
     
  7. DCESharkman

    DCESharkman TrainBoard Member

    3,474
    390
    45
    Northern California has had some weird weather so there may be something to that!
     
  8. RBrodzinsky

    RBrodzinsky Staff Member TrainBoard Supporter

    4,852
    1,455
    72
    This sounds suspiciously like what Jeff Sinks had happen with one of his Kobo installs. There was nothing actually wrong with the decoder, but I ended up doing a full decoder reset (from the LP drop down menu) after removing it, then reinstalling. May just be a cold solder point on one of the power wires. And Kelley does write the project data as "default" to the decoders, so a reset returns the decoder back to "as received", not some nebulous state of manufacturer shipped.
     
  9. DCESharkman

    DCESharkman TrainBoard Member

    3,474
    390
    45
    Well I have an update. I got a notification that there was an update LokProgrammer. I updated LokProgrammer and now there is no issue. Recognized and ran the locomotive without issue.
     
  10. jdcolombo

    jdcolombo TrainBoard Member

    1,133
    192
    25
    Like those simple solutions!

    John C.
     

Share This Page