02-01-2026, 08:13 PM
Here's a good tidbit when all seems lost....
Over the past month or so, I've encountered locos that seem to have lost their DCC mind (I ended up having 4 on my desk today with the issue). When they're in a consist, I'll notice that they literally aren't pulling their own weight. Pull them out of the consist (physically and DCC clear), put them on the programming track, hit "read" and I can't even get them to spit out their current address. My Prodigy system generates an "ERR" message on my handheld. Since I don't know the address, none of these locomotives respond to DCC commands.
However, for most of the recent "mind loss", when I hit the "read" button while on the programming track, the lights will flash a couple of times in succession, which I've come to understand must mean that the decoder is getting power and is communicating with the DCC system.
To resurrect one of these locos with "mind loss" .... reset the decoder to the factory default settings by setting CV08 to a value of 008. Even though you don't know the decoder address, you can do this by placing the locomotive on the programming track (making sure it's the only loco on that track) and getting in programming mode and setting CV08 to a value of "008". After this value is entered, you should be able to read that the decoder address is now "0003" (for systems with four-digit addressing). I usually check functionality on the main track running with an address of 0003 (forward, backward, lights on and off, sound check if it's a decoder with sound capability). If all is well, back to the programming track to program at least the address I want (usually the road number). Recheck functionality on the main track after that.
I think I've found the current cause of mind loss for my locomotives - I had a piece of track prior to a switch on my storage level delaminate from the roadbed and caused havoc when running through that switch - loco derailment and short circuits as a result. I'm thinking that prolonged exposure to a short circuit condition may cause the decoder to lose it's memory...
Over the past month or so, I've encountered locos that seem to have lost their DCC mind (I ended up having 4 on my desk today with the issue). When they're in a consist, I'll notice that they literally aren't pulling their own weight. Pull them out of the consist (physically and DCC clear), put them on the programming track, hit "read" and I can't even get them to spit out their current address. My Prodigy system generates an "ERR" message on my handheld. Since I don't know the address, none of these locomotives respond to DCC commands.
However, for most of the recent "mind loss", when I hit the "read" button while on the programming track, the lights will flash a couple of times in succession, which I've come to understand must mean that the decoder is getting power and is communicating with the DCC system.
To resurrect one of these locos with "mind loss" .... reset the decoder to the factory default settings by setting CV08 to a value of 008. Even though you don't know the decoder address, you can do this by placing the locomotive on the programming track (making sure it's the only loco on that track) and getting in programming mode and setting CV08 to a value of "008". After this value is entered, you should be able to read that the decoder address is now "0003" (for systems with four-digit addressing). I usually check functionality on the main track running with an address of 0003 (forward, backward, lights on and off, sound check if it's a decoder with sound capability). If all is well, back to the programming track to program at least the address I want (usually the road number). Recheck functionality on the main track after that.
I think I've found the current cause of mind loss for my locomotives - I had a piece of track prior to a switch on my storage level delaminate from the roadbed and caused havoc when running through that switch - loco derailment and short circuits as a result. I'm thinking that prolonged exposure to a short circuit condition may cause the decoder to lose it's memory...
Check out my "Rainbows in the Gorge" website: http://morristhemoosetm.wixsite.com/rainbows