Trains.com

Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

Athearn Genesis SD70M-2 DCC locomotive will not come to a full stop

1581 views
5 replies
1 rating 2 rating 3 rating 4 rating 5 rating
  • Member since
    July 2017
  • 2 posts
Athearn Genesis SD70M-2 DCC locomotive will not come to a full stop
Posted by Matt RR on Monday, July 10, 2017 12:52 AM

Gentlemen:  I am new to the forum and relatively new to DCC.  I have two Athearn Genesis SD70M-2 DCC locomotives that will not come to a full stop. I have reset them to factory settings and when its reset to #3 it operates fine and will come to a full stop.  As soon as I reprogram the locomotive back to its road number it will operate fully except it will not come to a full stop when I turn the speed down to zero, the locomotive crawls at a slow speed, approximately at a No.2 speed on the 28 speed dial, all other functions operate normally.  I have tried reprogramming on my program track and main track and same issues comes back.  I am using a MRC Prodigy wireless system.

I am familar with CV's and don't know if I need to reset a CV or do I have a more significant problem.  Any and all assistance would be appreciated.

  • Member since
    February 2002
  • 76 posts
Posted by bandmjim on Monday, July 10, 2017 4:07 PM

Sounds like it is something you are doing in the programming process.

But also check what CV 2 and CV 4 are set at, and set them both to zero ( 0 ) if not so and try again, if that does not cure the problem try setting the loco to a short address of anything other than three (3) after you do the factory reset and see how it acts it might be something you are doing trying to set it to a long address.

  • Member since
    July 2017
  • 2 posts
Posted by Matt RR on Monday, July 10, 2017 5:38 PM

Bandmjim, thank you for your suggestion.  I read both CV and they were set at 0. I then set a new four digit road number and the locomotive stop using speed 28 when turned down to 00.  So I thought SUCCESS I reset the road number back to 8023 which was the original road number and again same problem when I go forward and then stop the engine continued to crawl slowly.  So I then set the speed to 128 and there was the answer.  The speed was still set at 002 and that is why the locomotive continued to crawl.  I recently had a friend over and he likes to always use speed setting of 128 and must have shut off power to the track with the locomotives crawling at a low speed and the locomotives retained that in memory.  When I turn on the system all my MRC cabs are automatically set at speed 28.  Thank you for your assistance but this issue was certainly a surprise and a new lesson learned.

  • Member since
    February 2002
  • From: Reading, PA
  • 30,002 posts
Posted by rrinker on Monday, July 10, 2017 6:01 PM

 Makre sure CV29 is a proper value for 28 speed steps and the type of address you are using, either long or short, and not set to activate a speed table. But speed 0 is speed 0, none of that should matter, not even CV2, since that's the start speed at step ONE. Very strange. 

 Have you tried a DIFFERENT address? Maybe there is an issue with the cab and the address you are trying to use. Since it works fine on 3 - try somethign like 15 to see if another short address is ok, and try an alternate long address like 1234. That will help narrow down just what sequence causes the problem.

                                   --Randy

 


Modeling the Reading Railroad in the 1950's

 

Visit my web site at www.readingeastpenn.com for construction updates, DCC Info, and more.

  • Member since
    July 2009
  • From: lavale, md
  • 4,644 posts
Posted by gregc on Monday, July 10, 2017 7:19 PM

rrinker
Have you tried a DIFFERENT address?

do you have a 2nd controller?   if so, what loco address is it set to?

greg - Philadelphia & Reading / Reading

  • Member since
    October 2002
  • From: City of Québec,Canada
  • 1,258 posts
Posted by Jacktal on Monday, July 10, 2017 10:09 PM

My guess is that these engines didn't have their numbers properly dispatched (erased) from the command station after a previous use so that stored previous commands are polluting the present ones.

Subscriber & Member Login

Login, or register today to interact in our online community, comment on articles, receive our newsletter, manage your account online and more!

Users Online

There are no community member online

Search the Community

ADVERTISEMENT
ADVERTISEMENT
ADVERTISEMENT
Model Railroader Newsletter See all
Sign up for our FREE e-newsletter and get model railroad news in your inbox!