Hi all,
I've decided to use this opportunity to upgrade to a Prodigy Advanced Squared System, but just wondering if anyone has seen or heard of this issue:
* Currently running a MRC Command 2000 (it started acting up a few months ago out of the blue)
* Non-decoder equipped locos run fine.
* Decoder equipped locos do one of two things:
- If programmed by the command 2000 recently, they start normally, but won't respond to commands to stop for a very long time and slow down gradually like momentum is being used, when it's not, the slider is completely off but the engines keep going! Engines will not respond to the direction button and only run in one direction.
- If not programmed by the command 2000 recently, engines take off at full speed when the Command 2000 is powered on and will not stop.
Further tests:
I have tried hooking up to just one piece of flex track and get the same results with that or the entire layout. Does not seem to matter.
At least one Athearn locomotive got unusually hot running with a decoder on this system. In fact the engine had just been idling for a while.
What's up with that?
Rob
Wow that is an old one. The MRC manual is dated 1996.
As far as the loco's that are acting like they have momentum, chances are that they are doing just that. They may need programming to turn momentum off. Should be CV3 and 4. The ones that are taking off at full speed will need cv29 set so that DC mode is turned off. Very hot decoder in an Athearn. Might be an MRC decoder?
Springfield PA
Sorry I should have specified, the decoders in all my locos are digitrax.
I know that momentum never got programmed, or locos set to DC mode, so it's a mystery to me how this is happening. I guess it's a good thing the '90's can have their antique back! ;)
I just hope none of my decoders, or locos have been fried.
If they're running they're probably not fried but it's not good to run them too hot. I don't know what the track voltage is on that unit but it might help to measure it if you have a meter. To check the CV values I'd take the loco's to someone who has a system that can program including an LHS if they're equipped.
Good Luck
If I am not mistaken DCC locomotives never perform the same on DC as they do on DCC or at least this is whats een posted here. I have no desire to test that theory but that sounds like what your experiencing.
If I may ask why are you messing with that old clunker if you have dcc equipped locomotives?
You can still find pages from the manual on their site: The last link even shows you how to make a reverse loop that you control manually:
http://www.modelrec.com/resources/trainSound/COMAND2K%201_3.pdf
http://www.modelrec.com/resources/trainSound/COMAND2K%204_6.pdf
http://www.modelrec.com/resources/trainSound/COMAND2K%207_8.pdf
Okay new Prodigy hooked up. The locomotives programmed with the old command 2000 still have the momentum issue! (AKA they take forever to stop using the throttle, the only thing that stops them fast is the hard stop button on the Prodigy controller). This is AFTER they've been re-programmed by the new Prodigy system.
Locomotives not programmed with the malfunctioning Command 2000 seem to work fine and respond to commands quickly. Have I permanently damaged the decoders in some of these other locomotives?
*pulling my hair out*
Try resetting the problem decoders. If they are Digitrax, set CV8=8. That will reset all CVs to factory default, and it will run on address 3. See if it still has the problem. IIR, the COmmand 2000 could set momentum but the value was determined by the position of one of the throttles, not very precise. You may have accidently programmed momentum into the locos.
--Randy
Modeling the Reading Railroad in the 1950's
Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.
Thanks, Randy! Will give that a try and report back!
No luck. Upon programming CV 8 to 8 the reverse light works on the main but it doesn't respond to address 3. (or any address)
After several tries, I did a test and programmed a value of 7 into CV8 and read it back. It came back with a value of 8 so I'm not entirely sure I'm even successfully programming.
Thoughts?
CV8 is read only, it should be the manufacturer ID for the decoder. It should read back 129 for a Digitrax decoder. Attempting to set it to 8 tells it to reset (for Digitrax - other decoders have different reset procedures). If it's reading 8 then it is simply showing you the last value programmed. Are you doing this on the program track or in Ops Mode? Send it a couple of times, then remvoe the loco fromt he rails and put it back on and see if that clears it. If it's not responding to address 3 after a reset then it's not actually resetting.
Oh yeah - which Digitrax decoders are these? If you've had them as long as you've had the COmmand 2000 they may be older ones that don;t have the reset feature. This page on the Digitrax website shows which CVs need to be changed to reset the older decoders: http://tsd.digitrax.com/index.php?a=1518
To clarify I am using Digitrax DH123 decoders exclusively all purchased within the last 5-6 years max.
The system is a brand new Prodigy Advanced Squared.
Let me make sure I have the procedure right:
I hit program once to program on the program track and hit enter. I then enter to skip through the Address and other input options down to the last one, CV. For CV I enter 8 and then it prompts for data value and I enter 8. It then *sends* to the loco and takes me back to the CV prompt. I hit enter to get out of the program mode.
Then I try on the main track or attempt to read the CV on the program track by hitting program 3 times which takes you into the read options. Does this sound right?
Thanks guys!
Rob_C To clarify I am using Digitrax DH123 decoders exclusively all purchased within the last 5-6 years max. The system is a brand new Prodigy Advanced Squared. Let me make sure I have the procedure right: I hit program once to program on the program track and hit enter. I then enter to skip through the Address and other input options down to the last one, CV. For CV I enter 8 and then it prompts for data value and I enter 8. It then *sends* to the loco and takes me back to the CV prompt. I hit enter to get out of the program mode. Then I try on the main track or attempt to read the CV on the program track by hitting program 3 times which takes you into the read options. Does this sound right? Thanks guys! Rob
Assuming you have a program track correctly connected, yes. You can't read on the main though.
If it won't reset, try setting the following CVs on the program track: CV1=3, CV2=0, CV3=0, CV4=0, CV5=0, CV6=0, CV29=6
It shoudl then run on address 3. If the CVs read back the set values but it won't run on address 3 after that, somethign is not right witht he decoder. If the CVs don't actually read back the correct values, you may have an issue with the program track. Try reading back one of the ones that works - CV8 should respond as 129 which is the Digitrax manufacturer ID. If the loco works fine but does not read back, you probably have the program track set up incorrectly. Check the manual to make sure you're doign that part correctly, as the ones that run fine should have proper CV values to behave in a normal fashion.
After setting CV8 to 8 remove the loco from the track for a couple of seconds and then select loco address 3 and try to run. Resetting the decoder should set the address to 3.
UPDATE: Okay initial problem solved. Today I started using the second controller I purchased to go with the system, and even though they are identical, and the display shows everything, apparently no signals from that controller were doing anything, be it program or trying to run trains.
I switched to the original controller and the programming worked fine and the operation is now normal.
So my question now is, why is the second controller not able to grab a locomotive or program? Sorry newbie questions here!
Sorry, that was dumb! Found it in the manual. That's what I get for breezing through the manual assuming it's all obvious. ;)
Everything seems to be fine now. Lots of re-programming to do!
Always good to see when the problem is figured out. Best way to learn these things is doing it the hard way.