0 Members and 1 Guest are viewing this topic.
If it was factory equipped, probably a NCE decoder. I don't think Atlas ever used TCS. Lenz/NCE/ESU
I just had a look at the decoder installs section of TRW, and there’s a good tutorial by Rick Brodzinsky, putting an ESU 73100 into an Atlas GP38-2. Check out Rick’s opening commentary … “The NCE board was not functioning well (needed >30% throttle to move, then minimal speed control, and no response from decoder even on programming track)”. Seems like there’s a veritable history of shoddy NCE decoder performance. How companies get away with this crap is so annoying.
Just curious - having to use unusually excessive values for cv2 might be unconventional, but I suspect that there is no potential harm being done, right? I mean, the corresponding voltage values are readily within the intended operating parameters with respect to both the loco motor and the decoder, correct? I guess that the main downside is that, with, say, a value like cv2 = 100, there is then a much narrower “band” left over which cv’s 5 & 6 can “do their thing”. I dunno. Why is it so much to expect things to work out-of-the-box?
Completely disassembled the loco - there was just a negligible amount of factory grease in the vicinity of the worm gears (and it was by no means old/sticky/hardened in any way). Put a tiny amount of LaBelle oil in the usual places, a careful smear of fresh grease on the worms, and buttoned it all back up. Unfortunately, nothing changed … pathetic start-up performance remains. Just ordered an ESU 58751 Micro DCC Direct Atlas Legacy sound decoder; here’s hoping that will set things right.