0 Members and 1 Guest are viewing this topic.
Thanks for the replies guys.Yes, Switching mode not activated, tried F7 a few times, no difference. Yes, Everything is working fine except for the speed. Same happens even when I put a different locos file in this decoder.I have Cv53 is set to 120, like all my locos. I set it back up to 140, after an auto tune no difference, but I will try upping it some more.It does seem to me that full voltage is not getting through the decoder. When I do an auto tune the loco doesn’t go very far, about 2 feet only that’s about half the normal distance and it doesn’t get to the normal speed before stopping and ringing the bell. When I checked cv53, after the auto tune, it read only 34. Normally I get around 60 to 70 and then I set that back to 120. Cv54 was also very high in the 200’s.Never had this before. So next is change the decoder, as I think I have eliminated any other possibilities, at least what I can think of. I even changed some of the decoder wires that looked like they may have broke a strand or two with all the tearing apart and putting back together that’s been going on, thinking maybe that might raise resistance to current flow somewhere.I did run this loco on someone’s digitrax layout before this and I’m now wondering if that could have done something to the decoder. It ran fine on his layout and with his digitrax throttles.
Use LokProgrammer to force a reset, and force load microcode?
I'm curious, how much does a LokProgrmmer cost?Does it replace JMRI? If not, does it function well with it?
LokProgrammer is ESU proprietary device which only runs with ESU software. JMRI does not talk to it. While it can program generic CVs for any decoder, it only uploads sound files onto ESU decoders. It also has a DCC throttle function for testing (any brand decoder-equipped) models on the programming track
Use LokProgrammer to force a reset, and force load microcode?Quote from: Steveruger45 on December 12, 2019, 07:53:40 AMHi Rick, Thanks for chipping in. Not sure I understand what you mean. Pls explain. Thanks
Hi Rick, Thanks for chipping in. Not sure I understand what you mean. Pls explain. Thanks
Steve, The LokProgrammer hardware/software can do a CV8 type reset plus you can make it reload the decoder firmware. V5.0.10 has a firmware upgrade anyway so it couldn't (fingers-crossed) hurt anyway. I think the firmware applies to the V4 and Select, but maybe not. In any case you can still reload it.
What John said! Since it really sounds like the decoder has gotten a bit scrambled, was suggesting trying to force it back to normal.
Yes, like John mentioned, try new decoder if you have a spare one. All the things you describe seem to point to the decoder.Since you mentioned enabling and disabling the switching speed, I find it curious that it made no difference. I would have thought that even if the decoder ran the motor slow in normal mode, switching speed would have caused to run it extra slow.I don't think that a DCC trackl power can damage a decoder, unless the voltage is cranked way up (for H0 or 0 scale). But then I would expect the decoder to just fry (blown caps or diodes for example), not to just behave strangely.