BATMANFIXED!!!!!!
I am happy to hear that Brent.
DCC can be very unforgiving. Several years ago one of my critters was acting up so I did a factory reset. After that the decoder seemed to be totally dead. I tried all sorts of things programming wise but nothing worked, so I decided the decoder was faulty.
To make a long story short, the problem was simply that I was inputting address 03 incorrectly on my NCE PowerCab. I was putting in address "003" instead of "03". The display shows the address as '003' when it is actually '03', so I was simply putting in the address that the display showed.
Fortunately a fellow forum member pointed out the error of my ways, but unfortunately I had already removed the decoder and in the process I managed to destroy part of the shell. I still haven't fixed it.
Dave
I'm just a dude with a bad back having a lot of fun with model trains, and finally building a layout!
I have been following this thread, but I have offered no replies because I had no answers. But now that Brent has solved the problem, I will offer these comments.
I also have the NCE Power Pro 5 amp wireless system. I use the Advanced Consist option quite often because I run my passenger train locomotives in AA and AB consists. I also run diesel freight locomotives in consists. I never use Old Style Consists.
That said, there have been occasions where I clear a consist and CV19 is not cleared even though I follow the NCE instructions for clearing consists. In fact, it happens often enough that when a locomotive has lights and sound but no movement, CV19 is the problem.
I no longer waste time putting the locomotive on the Programming Track to check CV19 to see if that is the problem. I simply use the Ops mode on the mainline to set CV19 to zero, and that solves the problem.
I blame all of this on the NCE command station. I don't know why CV19 is not reset to zero, but it often not reset to zero.
I have never documented the problem and the solution in writing to remind myself of this recurring issue, but I'll bet if I went down to my layout right now, this very problem will occur on at least one consist.
Rich
Alton Junction
Rich.
The same with my Power Cab system. Weather it's user error ( probably), or the offending locomotive had a disconnect from dirty wheels or track. It happens. On the clubs Lenz system I would old fashion consist two advanced consist sets and sometimes have difficulty breaking them up. Or one locomotive never got the message. I then found it easier just to use two throttles for the pusher section. But an extra throttle was not always available.
Pete.
wrench567 Rich. The same with my Power Cab system. Weather it's user error ( probably), or the offending locomotive had a disconnect from dirty wheels or track. It happens.
The same with my Power Cab system. Weather it's user error ( probably), or the offending locomotive had a disconnect from dirty wheels or track. It happens.
I would rule out dirty wheels and dirty track because I have checked that out on my layout. It still could be, but that is not my experience.
As to user error, I cannot claim to be infallible as an operator. But, in this case, I will rule out operator error because, over time, I feel that I have developed sufficient expertise with Advanced Consisting to do it right.
My conclusion is that there is some type of flaw in the NCE system, either the command station or the wireless throttle. I have often wondered if the CV19 error could be eliminated by using a tethered throttle. In other words, I consider the wireless system as a "throttle of interest".
wrench567 . Stixx hit on it about ten posts ago. Old fashioned consist!!!!! There was nothing wrong with the decoder at all. The consist is held in the command station. As long as the locomotive is on the track it will only be controlled by the consist address. Pete.
. Stixx hit on it about ten posts ago. Old fashioned consist!!!!! There was nothing wrong with the decoder at all. The consist is held in the command station. As long as the locomotive is on the track it will only be controlled by the consist address.
There could be an issue with the wireless throttle. But the same thing happens with the wired Power Cab. Because of computers, things that would take days to screw up now only takes seconds. When the Power Cab was version 1.1. I never noticed any problems. After the upgrade chip to version 1.6 when I exit program track for some reason the bell is on F4. I have to unplug the tether and restart the cab. Then everything is normal. Strange behavior indeed.
Stix.
You don't have to tell me about bonehead moves. I'm a master at it. One of my steamers wouldn't run. Instead of address 9827, I was putting in 8927. The font at quick glance the 9 looks like an 8 and vice a verse. Note to self. Put on glasses before operating!!!!
Been there done that. Will be across my headstone.
wrench567 Rich. There could be an issue with the wireless throttle. But the same thing happens with the wired Power Cab. Because of computers, things that would take days to screw up now only takes seconds. When the Power Cab was version 1.1. I never noticed any problems. After the upgrade chip to version 1.6 when I exit program track for some reason the bell is on F4. I have to unplug the tether and restart the cab. Then everything is normal. Strange behavior indeed.
hon30critter BATMAN FIXED!!!!!! I am happy to hear that Brent. DCC can be very unforgiving. Several years ago one of my critters was acting up so I did a factory reset. After that the decoder seemed to be totally dead. I tried all sorts of things programming wise but nothing worked, so I decided the decoder was faulty. To make a long story short, the problem was simply that I was inputting address 03 incorrectly on my NCE PowerCab. I was putting in address "003" instead of "03". The display shows the address as '003' when it is actually '03', so I was simply putting in the address that the display showed. Fortunately a fellow forum member pointed out the error of my ways, but unfortunately I had already removed the decoder and in the process I managed to destroy part of the shell. I still haven't fixed it. Dave
BATMAN FIXED!!!!!!
Dave, In my endless reading trying to resolve the problem, the conflicting advice on how many "0" to add when programing a CV was enough to drive you nuts, especially CV 8.
This little exercise in frustration has taught me a few things at least and that is never a bad thing. I came across a guy with the same problem on FB and suggested the delete from consist button and he was up and running again in no time.
I have two Rapido FP7As and one "B" unit and they have been in and out of consist a lot. I will hit the delete from consist button for all of them just to be sure. I haven't tried it yet, but I wonder if I will still get the "can not read" notice on the programming track for the "B" unit?
I was seeking help on the ESU forum and those guys sure like to make you feel stupid, not here though, it is a better fit for me. Thanks for all your help.
Brent
"All of the world's problems are the result of the difference between how we think and how the world works."
Brent.
We have all been there. Especially when DCC was in it's infancy. I couldn't tell you how many decoders I have had to reset because of a simple problem that with a little deductive reasoning could have saved the day. I have had decoders get scrambled when someone else shorted the track. And when someone broadcast program instead of POM. Before disabling DC in CV29 would rocket your train across the layout. Flashing lights, melted shells, and buzzing motors were all part of the learning curve.
When something weird happens. The first thing that goes through my head is. What was the last thing I did before it messed up? Then work back from there.
Like the Pink Floyd song. Welcome to the machine.
Hi Batman, when you get "cannot read CVs when on the programming track, usually this is the decoder issue. replacing the decoder with a new one usually fixes this and by extension, other problems.
know2go Hi Batman, when you get "cannot read CVs when on the programming track, usually this is the decoder issue. replacing the decoder with a new one usually fixes this and by extension, other problems.
I sent it back to Rapido and they said it was definitely a bad decoder and it is currently on its way back across the country homeward bound.