Programming NCE DCC problem

[Anonymous]

Glad to hear that you have the problem sorted out.

Enjoy.

David

[Anonymous]

Well, as promised - here's what was causing the trouble and almost made me return the system - the power connecting track !
I had those old brass tracks lying around that have leads to connect track power. So I used them. Turns out thye have some kind of capasitor in them underneath. That thing was causing the problem on programming track and of course no problems when I used them on my DC layout.
Live and learn !

[Anonymous]

I have the Powerhouse Pro. When I got it home it would not read the decoders in my engines. The problem was that the top circuit board connector had come adrift from the bottom board. The distributor advised me that this would have occured in transit.

Yeah right. From my observation of the inside of the unit there was no way this came adrift due to transit. Plain and simple, it was a matter of lack of quality control.

Other than that the NCE unit is a dream to use.

David

[Anonymous]

Guys, I finally found the problem. You'll never guess what it was !
I'll post it tomorrow with pictures - too tired now...

[cacole]

Did you remove the jumpers from the corners of the Kato DCC socket before you plugged in the decoder? I know this sounds dumb, but it is possible to plug a decoder into the Kato socket without removing the shorting jumpers. Even if you had the decoder plugged in backwards, it should still program, because a backward decoder just reverses the motor direction.

[dehusman]

Put another engine on the programming track. If you still get "255" then the problem probably isn't the locomotive.

Put the engine on the main and try to run it on engine number "03" or "3".

Take off ALL the other engines and put the engine you want to program on the main. Select "Programing on the main". See if it will read the decoder. If it doesn't then the problem is probably in the locomotive. If it does program the locomotive then somewhere you have a bad connection to the programming track. Check to see if the programing track feeders are loose where they connect to the command station.

Dave H.

[mlw8542]

What you describe is usually caused by an open/poor connection, but also can be caused by a short (motor not isolated, etc.). Do not apply full track power untill you are sure there are no shorts, or the magic smoke will come out. This is why NCE recomends placing all new decoder installs on the program track. Also be sure that all functions (lights etc.) are turned off when programing, this too can cause a 255.
Hope this is helpfull, John S.

[Anonymous]

dimastep,

Forget the fact about plugging the decoder to the rails. You are well beyond that. I would strongly suggest at this point that you call NCE and tell them the probelm. I have had problems in the past, but they have been great about fixing and or replacing defective equipment.

Unfortunately, that is what 255 means. but you are right you should be able to place your decodered engine on the programming track, enter the programming function and program away.

bob A.

[Anonymous]

Guys, I just wanna say I really appreciate everyone's help !

So what is the purpuse of programming track ?

Assuming I have an engine with the plug and decoder with the plug. Shouldn't I be able to plug decoder in engine, put on programing track, which is completely separate peice of flextrack, and swithc to programming track mode.

To be honest, I don't understand this thing about plugging decoder to rails and system directly. You can't even do that with NMRA-plug decoders.

Ah, I'll have a great weekend :)

One question though - has anyone ever fried thier PowerHouse Pro even though things look normal i.e. it displays text perfectly, lights are OK.
That's my main concern now.

[Anonymous]

OK,

Under the "20 minute test", you would use the decoder separate of the engine. So, the black and red wire would connect to the Power Pro and the Grey and Orange wire would connect to the track. From what you have told me so far, you are well beyond that. That is something you do with an engine that doesn't have a decoder in it and you just want to make sure that the system is working.

When you took your procab and hit program so that the screen showed programming track, then the engine should be on the programming track completely isolated from the main. At the same time the led on the Power pro should be blinking. If the deocder ran for a few minutes and then stopped, either the decoder is bad, or you have a problem with the power leads to the track for both normal operation and well as the power leads to the programming track.

Hence the request to meter the power output.

Hope this clears that up.

[Anonymous]

QUOTE: Originally posted by michealfarley

In the "running in 20 minutes" test mode that NCE describes in the manual, the locomotive must be on the rails before you attempt to program the decoder or it will not work.

This is where I am lost :(
On which rails and where should the decoder be ?

I plug the decoder in my Kato (the plug is already there) and put it on programming track. Then I press Program 4 times to get into track programming mode, and the decoder manufacturer comes as 255 - probably meaning decoder not found.

Was I correctly performing the steps above ?

[Anonymous]

Steady when on main track, blinking when in programming mode on programming track

[Anonymous]

if you look at the front of the Power Pro, is the led lit steadily or is it blinking?

I guess i would check the connections, to make sure that they are tight coming into and out of the base.

[Anonymous]

Well, the funniest thing is - it ran for a little bit on all default settings and now it doesn't run anymore. Nor does it run with diferent decoder. So either something is wrong with wiring or something with the PowerPro system itself.

[Anonymous]

Unfortunaly, it would not be the first time that a batch of decoders is bad. I would meter the tracks to make sure that there is sufficient power Compare that to the manual.

Does the engine run at all on Address 3?

[Anonymous]

I have the Tony's recommended power supply.
I have 5 identical decoders and engines with dcc sockets.
Will play more with it, seems like it is the wiring somewhere.

[Anonymous]

three things:
One how much power do you have supporting the system? Volts?


Two do you have another dcc equipped engine?

three, do you have another Decoder to try?

[Anonymous]

The thing is I have Kato with NMRA plug and my decoder also comes with the plug. So all I did was plug it in the loco and then try to program on programming track.
Was there something else I missed ?

[michealfarley]

I have found with my NCE system and decoders that I will often get an incorrect manufacturer code (often 255) when the decoder isn't installed properly. I usually tale this as a sign that I need to go over my installation before retrying. The NCE decoder must have a load connected to the motor leads in order for the system to program the decoder. If you simply hook up the rail power to the decoder, it will not program. In the "running in 20 minutes" test mode that NCE describes in the manual, the locomotive must be on the rails before you attempt to program the decoder or it will not work.

[Anonymous]

i have NCE. Usually when progamming on the main it is selective as to what CV you wi***o change, which I believe you are attempting to do, the only thing that is shown is what CV you are trying to progam and then it allows you to enter a value. Otherwise if you are using the programming function and the engine is not on the programming track. you will get 255 because it can't find it and the power to the rest of the railroad is shut down to prevent mis-programming of another engine.

[Anonymous]

Actually this isn't even programming part, but seems like detection of the decoder.
I am prety sure I got everything connected right to the programming track but decoder not getting recognized.
Anyone had this issue with NCE system and decoder D13SPR ?

[Anonymous]

Normally, when the programming track thows up 255 is because the system is not reading the decoder. Usually one of two reasons. One, there isn't enoug power getting to the programming track, or your progamming track, may be touching the main line. check you cuts.

[dehusman]

Sounds like you are not completing the programming process, you are stopping before it finishes. Are you sure you are programming on the programming track or programming on the main? NCE will do either.
What engine number did you give it? The default number is 03. What are the other values you get while running through the programming sequence?

Dave H.

[Anonymous]

I just received my PowerPro and there is something strange with it.
It came with D13SRP decoders that have a plug. I plug it in, made sure numbers allign, then go to programming track and the decoder manufacturer code comes as 255, so is version and short address.
The weirdest thing is that if I have no locomotice on programming track and try to program, the decoder also comes as 255, instead of saying something like
"cannon determine decoder"

Any idea what's wrong ?