I have a loco with an NCE decoder which use to work. Currently I can control the light, but I cannot run the loco. I am using NCE Power Cab and other locos are running. If I put the problem one on the programming track and do a factory reset, then reset the address, the loco does the little jog between each item. This is suggesting the motor or connected, but maybe I am wrong? Any other ideas on what may be wrong? I did use the Recovery Programming in the Power Cab and the loco jogged between each setting. Then set the address and it jogged for that as well.
1 Like
I donât know for sure but Iâve heard others have a âconsistâ loaded into CV 19.
Sometimes even a reset preserves this. At least check CV 19 to be sure. It should read 0.
https://ncedcc.zendesk.com/hc/en-us/articles/205929955-Consist-Troubleshooting
Good Luck, Ed
2 Likes
Hello All,
Welcome to the forums!
I am not familiar with NCE mobile decoders, but I do have an NCE 5A Power Pro System.
Most of my motive power has Digitrax mobile decoders; both sound and non-sound.
I also have TCS, Bachmann 2-function decoders, Märklin mfx+ digital decoder, and ZIMO.
A standalone programming track is hooked up to my desktop computer running JMRI Decoderpro through a Digitrax PR3 (superceeded by the PR4).
Some decoders require you to remove the unit from the tracks to cycle the power after writing Value 8 to CV 8, whether programming on the main or using a programming track.
Hope this helps.
1 Like
Which NCE decoder is it?
I donât know why the engine is ânot runningâ. If it ran before, it could be in a consist. If you are trying to program it to the same number it was before, the PowerCab will remember it was in a consist and the loco will do whatever the consist wants it to do.
So as Ed said check cv19 and make sure it is zero.
That said, the jog you are reporting could be completely normal. Used to be that decoders would cause the loco to jog whenever a cv was changed during the programming process. This was the decoders method of reporting that it was alive and well and acknowledging it had received the input signal.
1 Like
As Maxman says, that âjoggingâ is normal, Iâve programmed new decoders in the last year that do that. It just means itâs getting the signal for the new programming.
I also thought the problem could be a consist issue. The factory reset should change the short address to 003 and the long address to 0003. Before changing the address to itâs normal address, try running it on 003 and see if it responds. If so, it probably means itâs normal ID is part of a consist and needs to be removed for it to work on itâs normal ID.
1 Like
I have the NCE PH-Pro and locomotives being programmed on the Programming Track typically jerk forward a slight bit. That is normal behavior.
CV19 is zero and I went through all the instructions to clear any consists, which I should not have anyway since I only run single loco units.. I have even set the unit to a different address.
I mentioned the âjogâ when programming to state that the decoder is capable of controlling the motor.
This is an On30 street car. There is not much room for electronics unless I want them visible. It is an NEC N14SR which was squeezed a bit between the âfloorâ of the car and the motor. After posting I noticed that sometimes the system would act as if there is a short when I placed the loco back on the track. I am thinking I need a new decoder.
1 Like
Before installing the decoder, did you check to be sure that the motor was isolated from the frame?
Would the unit still jog back and forth when programming it if that was not the case? I would not think this would occur if that was true. It did run but hasnât been used for about 2 years. Was in the box that entire time. The motor is isolated from the wheels and the power pickup is via
1 Like
I went back and re-read your opening post. I see that the loco used to run. Sorry, I missed that. So, it is an NCE decoder. Have you reset it, CV8=8?
Yes, I reset cv8=8. I also used the NCE Powercab reprogram feature. On top of that, as a result of an previous reply in this thread, I found the NCE âIn Depth Locomotive Decoder Troubleshooting guideâ and followed those instructions, which state setting CV30=2 for their decoders. And I did power cycles of the powercab (which cycled the loco as well) between each.
I can control the light, but not the motor.
2 Likes
Two strikes against me. I spoke from memory which is always dangerous. Duh! The NCE decoder reset is CV30=2.
Before I withdraw from this thread in shame, let me ask you this. Following the reset, the cab number defaults to 3. Have you tried to run the loco with an address of 3?
âActs like there is a shortâ, and squeezed at installation? But still jogs?
Have you tried removing the body and unsqueezing the decoder?
The fact that the motor still jogs means to me that the decoder is still viable. If it were dead youâd have no movement.
1 Like
It is possible to blow the motor tab(s) and still get lights. Iâm not saying that the motor tabs are blown, but this all still remains a mystery.
Yes, but he says that the engine moves.
Correct, a mystery. Like trying to figure out which piece is missing from a 1000 piece puzzle without opening the box.
1 Like
Well, if a jog means the engine moves, then so be it.
I also have an NCE system and on occasion have lost control of a loco. The loco would be getting power but not signal. Clean the track and/or wheels, sometimes itâs the simple things cause the biggest issues.
1 Like
Is it possible to blow the main motor control circuitry but still get the motor to activate the âjogâ? That seems something of a stretchâŚ
1 Like
As I mentioned, I am Iâm not saying that the motor tabs are blown. It is normal for loco motives to jerk a little on programming track. As part of programming, the decoder needs to momentarily divert power via the motor to generate an acknowledgement pulse back to the DCC system.
The OP indicates that the locomotive âjogsâ on the Programming Track but does not run on the main layout, yet he can control the lights. So, the decoder does not seem to be the problem.
The OPâs problem remains a mystery at this point.