MTH engine problems running with DCC

[guysmiley]

Hi there,

I'm new to this forum and to model trains. I've got an MTH Berkshire that is running with a Digitrax controller. All of the DCC functions appear to work all the way up to 28. The problem is that suddenly it stops and starts all on it's own. I set the throttle and it runs for a bit, slows down and stops and then starts back up. The sound stays on so it's not loosing power. It's like the throttle signal is dissapearing. I don't know where to start looking for the problem, the trottle controller or the train. I'd appreciate any tips. I looked at the wheels and they don't appear to be covered in gunk or anything but like I said, I have no idea what I'm doing.


Thanks,

Garrick.

 

[jonyb]

I assume this problem doesn't happen with other engines?

 

[oxfordlawn]

If you look right now under "active topics" theres a thread called 'Disgusted'. Seems you are not the only one with a problem with MTH loco. I have no experience at all but find it interesting 2 threads with similiar problems with same company

 

[guysmiley]

I'm very very new to the hobby and this is my first and only engine.

I'm going to look at the other post.

Garrick.

 

[Motley]

You need to reset your decoder back to defaults.

Program on the main.

Select loco 55

Select CV 55

Select value of 55

Now your engine should be at the default address of 3

If that doesn't work, try calling MTH tech support, they are very helpful.

 

[blackz28]

You need to reset your decoder back to defaults.

Program on the main.

Select loco 55

Select CV 55

Select value of 55

Now your engine should be at the default address of 3

If that doesn't work, try calling MTH tech support, they are very helpful.

YES THIS SEEMS TO BE THE digital HOLY WATER FOR THOSE SATANIC BEAST

 

[guysmiley]

I tried the CV 55 thing and the engine responded to the command however the symptom is still happening. I've got to think it's the controller at this point. The train was working fine on a borrowed Digitrax controller and then worked fine on this new controller for a couple of hours. Then suddenly the symptom started. I'm going to try and use the "borrowed" controller again to test it out. If it's not the controller then it has to be dirty wheels or a bad track connection (something blocking the signal).

Any more hints?

Thanks,

Garrick.

 

[guysmiley]

I may have stumbled across a solutions:

Zephyr Xtra - Reset to Factory DefaultArticle Details Last Updated
10th of August, 2011

Would you like to...

Print this page

Email this page

Post a comment

Subscribe me

Add to favorites

Remove Highlighting

Edit this Article

Quick Edit

Export to PDF
User Opinions (0 votes)No users have voted. How would you rate this answer? Helpful Not helpful Help us improve. Why was this unhelpful?

Thank you for rating this answer.


To reset the DCS51/DCS50 to factory settings:

If you change command station option switches and experience unexpected results, just set OpSw 39 to “c” (closed) to reset the unit to the original factory settings.

1. Press the PROG key. The display shows the last decoder programming mode used.

2. Press the SWITCH key. The display shows the last switch used and its commanded position.

3. Use the numeric keypad to enter the number of the Option Switch you want to change; in this case 39.

4. Press the "c/-" key to set the OpSw to closed and reset DCS51/DCS50.

5. Press EXIT when finished. The DCS51/DCS50 display will show "-cS-" to indicate that you are running in command station mode.


I (or one of the kids) must have hit a button or two by accident. As of now the problem appears to be resolved.

Thanks for the tips.

Garrick.

 

[Motley]

Well that's good.

As for the blame it on MTH responses. Take that suckas! LOL

 

[guysmiley]

Well that's good.

As for the blame it on MTH responses. Take that suckas! LOL

As with most things, I have nobody to blame but myself! I'm still learning this DCC thing, it's a far cry from what I had when I was a kid!

Thanks again to all those who contributed.

Garrick.