1) Check your decoder manual. It will list factory default values for all programmable CVs. Try using these defaults as a starting point. Then you can fine-tune from there.
2) If you've got the CV values pretty well botched (most of us have done this at least once), most MRC decoders have a reset CV. Setting this to a particular value resets all CVs to the factory default. Again check your manual. You can find MRC decoder manuals online at
www.modelrec.com/train-controls/dcc-decoders.asp
3) Based on the way you describe your problem, I'd suggest that you clean EVERYTHING: a piece of test track, the loco wheels, the pickups. Many locos come with lubricants and just plain gunk from the manufacturing process, and DCC doesn't allow you to "blast through" this with higher voltages like DC does. Also, connect your booster directly to the test track, in case the wiring to your layout is giving you problems.
4) It's possible that the decoder is defective. From what I read on this forum and others, MRC decoders are notorious for having a high failure rate out-of-the-box.
Good luck!
n1vets333 wrote:Thank you I will attempt cleaning everything and try to reset the cv's, what is an average startvoltage though? Do all engines have different ones, it says I could program from 1 to 32. How do I determine which number will work good?
The method that was explained to me is trial-and-error. Start by setting CV2, CV3, and CV4 all to zero. Put the loco on a test track or the layout, it doesn't matter which. Select it on your controller. Set the throttle to Step 1 and see if the loco JUST BEGINS TO MOVE. If it doesn't, use ops programming to change CV2 to 1. Exit ops programming and again see if the loco will just creep on throttle step 1. Keep reprogramming CV2 to incrementally larger values until the loco just starts moving on throttle step 1. When it does, you're done.
If the loco moves too fast on throttle step 1 when CV2 is 0, then that's the best you're gonna do with that decoder in that loco.
This is all covered in your manual. All locos will respond differently, you must establish the start voltage by trial and error.
Put the loco on the main and set your throttle for "prog main track". Now turn the throttle till engine moves forward. To have the engine move sooner simply up the " Start voltage " value up till you get the movement you want. A value between 1 and 32 is less a head ache than 1 to 255 !... Once you have start voltage, Top voltage is simply your choice of how fast the loco runs around.
ACC/DEC are simply momentum. Put a value of 20 and then work up or down from their. Just be aware the loco will start slow BUT IT WILL TAKE LONGER TO STOP (DEC).
n1vets333 wrote:thank you all your advice is very helpful. I finally have the decoder installed and the loco is responding to my commands. Here are a couple of other thyings maybe you could help me with. When I put the light on it got so bright that the bulb blew, how do I avoid this?
P2K's use a low voltage (1.5v?) bulb. Your decoder puts out too much voltage for the stock bulbs. Put in 16v bulbs, or resistors and LEDs/low voltage bulbs.
n1vets333 wrote:Also the engine will start rolling sounds will function then out of nowhere the loco will reset and start all over again, what does this sound like to you?
That sounds like a normal MRC decoder.
Rotor
Jake: How often does the train go by? Elwood: So often you won't even notice ...
If you want to program a CV, enter a CV number. Press ENTER. Then enter CV data. Press ENTER. "CV#" will flash again, prompting you to program another CV. To skip, press ENTER.
If you followed the procedure ( and gave the address of the loco/decoder you are working on) you should have made changes to decoder's CV.
You should also get familliar with programming on the programming track. you will be able to read the CV's and confirm your changes are being taken right.
If all else fails, read the manual.
WalleyeThe method that was explained to me is trial-and-error. Start by setting CV2, CV3, and CV4 all to zero. Put the loco on a test track or the layout, it doesn't matter which. Select it on your controller. Set the throttle to Step 1 and see if the loco JUST BEGINS TO MOVE. If it doesn't, use ops programming to change CV2 to 1. Exit ops programming and again see if the loco will just creep on throttle step 1. Keep reprogramming CV2 to incrementally larger values until the loco just starts moving on throttle step 1. When it does, you're done. If the loco moves too fast on throttle step 1 when CV2 is 0, then that's the best you're gonna do with that decoder in that loco.
I was fiddling with an Atlas N unit (I'm told it may be an older one - came in a box with a plastic tray instead of a foam cut-out protecting it). Put an MRC sound decoder in it (Item #0001636) and it only starts moving in speed step 5 even with CV2 set to 32.
Seems from another thread that sound units can require a higher start voltage than non-sound DCC locomotives so maybe that's part of it.
I have a newer Atlas Geep (with the same decoder) that I can play around with, so I'll see if that's any different.
I started playing around with throttle curves a little but ran out of time.
I picked up the MRC Wireless PC interface and so all of this fiddling has been a breeze. The web page suggests emailing MRC with comments - and I have a few ideas for improvements. Anyone know what email I'm supposed to use?
n1vets333Also the engine will start rolling sounds will function then out of nowhere the loco will reset and start all over again, what does this sound like to you?
Seems like a momentary open in your circuit. I had this trouble with an Atlas N GP that I had run on a club layout (really dirty track apparently!).
After cleaning the wheels by dampening some paper towel with rubbing alcohol and letting the wheels of the rear truck spin on it (while getting power from the front truck) it was clear why they weren't making good contact. Repeat the process to clean the front truck while getting power from the clean rear.
Of course, it's tough to do this if you're not getting good enough contact to power the wheels so they can spin, but it worked ok for me after a bit of fiddling.
Once the track and locomotive wheels were clean everything worked fine for me - no more loco resets.
NSColsMP6 I was fiddling with an Atlas N unit (I'm told it may be an older one - came in a box with a plastic tray instead of a foam cut-out protecting it). Put an MRC sound decoder in it (Item #0001636) and it only starts moving in speed step 5 even with CV2 set to 32. Seems from another thread that sound units can require a higher start voltage than non-sound DCC locomotives so maybe that's part of it. I have a newer Atlas Geep (with the same decoder) that I can play around with, so I'll see if that's any different.
Fooled around with the start votlage of a second Atlas N GP (newer motor design I believe) and I was able to get it to start in speed step 3 (of 28) with CV2 set to 32.
Sound decoders in my experience (and I think most people's) tend to be very finicky about clean track, and a re-set like you describe will happen even on track where the engine otherwise seems to run with no trouble.
BTW since you recently installed the decoder, double check and clean all the engine's wheels. I had a sound decoder I installed where it kept re-setting no matter how much I cleaned the track...eventually I found a little bit of flux from when I soldered the decoder's connections had gotten on a wheel and running the engine was spreading it on the track. Once I cleaned the wheels it ran fine.