Thanks again for the tips, and yes I am using Lenz v3.6 and have both an LH 100 that I use to program with, and an LH 90 that I prefer to use to run locomotives (I like the knob better than the push buttons). My next step is to try to insulate the bottom of the decoder with "black" tape, and if that doesn't work, I'll contact both NCE and Lenz for their input. You're right about having dificulty programming with the LH90, it's a pretty cumbersome process, the LH100 is much more straight-forward. Now if the syntax in the translation in the manuals was a little more "Englisher" all would be well! Gerry S.
Gerry
My club uses Lenz also. Since we have upgraded to version 3.6 some NCE decoders would not run at all. All other decoders work great. Even some NCE decoders will work also. This drove me crazy for a while. Why only some and not others would work. It seems that with Lenz version 3.6 that Railcom is enabled by default in the LV102 boosters. This would explain why the decoders worked in one district powered by an LV101 booster but not the other districts. If you have an LZV 100 command and booster in one box then Railcom will be enabled in version 3.6. Since the club does not use Railcom then simply disabling it was the easy fix. There are settings you can change to keep Railcom enabled if need be.
I have not had too much luck with programing with an LH90. If you have access to an LH100 throttle it would be a little easier to disable it. Remember if you reset the command station you will have to disable Railcom again.
Pete
I pray every day I break even, Cause I can really use the money!
I started with nothing and still have most of it left!
Thanks for the reply and the tips. I'm going to try the idea about putting tape between the decoder and the top of the chassis and motor. I have to get my patience back first, though. Thanks again. Gerry S.
Did you put electrical tape on top of the motor to prevent the decoder's circuit traces from touching it? Did you put a 1,000 Ohm resistor in the leads to each LED unless the NCE instructions specifically state that one is not necessary? When you soldered the decoder wires to the trucks you may have created a short from a blob of excess solder touching the frame.
Hello all, I'm hoping someone can figure out why I'm having an issue with a replacement decoder in a Bachmann geep. I use a Lenz 100 (w/ an aux. LH90) to operate my layout. I found a replacement decoder from NCE for a Bachmann "DCC on board" GP38-2 that promises to smooth out throttle response and improve noise and slow running characterisitcs. After installing the new decoder (soldered the four truck wires and two motor wires plus front and rear LED's supplied with the decoder) and clipping the three capacitors (per NCE directions), I first placed the loco on the program track (again per NCE directions). The default address read out as #3 so moved the loco onto the main. There was a quiet buzz and the command station shut down from detecting a short (no shell at this point). I reset for the short, replaced the loco onto the main and bzzzt! I double checked my soldering points, put a strip of "black tape" under the motor and all seemed okay). However, same result. My frustration level reached it's apogee at this point so I removed the NCE board and put the Bachmann back in and voila, it lives! Any thoughts? Gerry S.