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!

Problems with an Atlas NJT GP40

3202 views
18 replies
1 rating 2 rating 3 rating 4 rating 5 rating
  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Saturday, June 12, 2010 10:38 AM

 I did a reset on one of my GP40's and the 128 did the trick. I actually remembered to write down my changed CV settings before doing so, saving me the time to speed match with the others.

Springfield PA

  • Member since
    December 2001
  • From: Trois-Rivieres Quebec Canada
  • 1,063 posts
Posted by jalajoie on Saturday, June 12, 2010 9:20 AM

If I recall correctly CV49=110 is an error that first appeared on Tony's web site.

Jack W.

  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Saturday, June 12, 2010 7:45 AM

 Hmm Book says 128. I'll have to visit the Atlas forums to comment after trying it on one of my loco's   I also notice that you can also just reset the sound volumes to factory default.

Springfield PA

  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Saturday, June 12, 2010 7:35 AM

 Is CV49 supposed to be 128?

I saw a post on the Atlas forums to set it to 110.  

I'll have to do some more reading. 

Springfield PA

  • Member since
    December 2001
  • From: Trois-Rivieres Quebec Canada
  • 1,063 posts
Posted by jalajoie on Friday, June 11, 2010 6:48 PM

There is no need to read a QSI decoder in order to do a factory reset.

Simply Set CV49 to 128

                 CV50 to 255

                 CV56 to 113

It can be done on the main or the program track.

Jack W.

NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Posted by NJT on Friday, June 11, 2010 6:06 PM

 Thats what im going to do. My system wont let me reset the engine on a test track, due to the system not being able to read it for some reason, so im going to use the magnetic wand Atlas says to use.

Tony
  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Friday, June 11, 2010 4:07 PM

 Sounds like it's time for a reset of the decoder.

Springfield PA

NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Posted by NJT on Friday, June 11, 2010 3:57 PM

 Thats not the problem. I have it set so that the engine idles the whole time while not being used.

Tony
  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Friday, June 11, 2010 2:28 PM

 Atlas does have the auto silence feature. It's set by CV51.5  The setting tells the loco to silence after a programmed time of inactivity.  Maybe that's what you're seeing?

 

Springfield PA

  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Friday, June 11, 2010 2:22 PM

 There might be an auto silence feature enabled to silence the loco if it's inactive and idling for awhile. Some sound loco's have the feature available so that you don't have to hear them when parked. I'll have to look it up but I believe that feature might be available on Atlas.

Springfield PA

NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Posted by NJT on Friday, June 11, 2010 1:32 PM

 I ran it today and i identified another problem with it. If i select it with my digitrax controller, the engine cuts out, even with it idling, but if i select a different engine and leave my NJT GP40 idling, it does not cut out, so im really beyond myself now............................ 

Tony
  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Thursday, June 10, 2010 8:59 PM

 This definitely sounds like a turnout issue. Do you have access to a camera to your layout pics here?

In the mean time just run the loco you're having the problem with, but don't include any rolling stock. See if you can identify problem areas with the loco only.

Springfield PA

NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Posted by NJT on Thursday, June 10, 2010 6:37 PM

 I want to say shorting out because it does it most on switches, but it also does it on my main line where its all flex track, so thats why it makes me wonder why this engine is doing this.

Tony
  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Thursday, June 10, 2010 2:13 PM

 How are you determining that it is shorting out?  Also where is is shorting? Turnouts etc.

 

Springfield PA

NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Posted by NJT on Thursday, June 10, 2010 1:30 PM

 Shorting out.

Tony
NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Posted by NJT on Thursday, June 10, 2010 11:33 AM

 Im using Digitrax and iv tried it on DC and it runs great with no problems, and it will short out, (or cut out if you want to call it that) anywhere, not just on a certain section of track. Im going to try and use the magnetic wand to try and reset it, and try it on another section of track with DCC. Im sure its not the one I had before because I did a few things to it to make sure that I would know if they sent the same one back to me. 

Tony
  • Member since
    May 2008
  • 4,612 posts
Posted by Hamltnblue on Wednesday, June 9, 2010 3:29 PM

 First, what is the system you are using?

Have you tried it on a single piece of track with the DCC system hooked up?

Does it run at all and short at a specific spot or as soon as you put it on the track.?

Are you sure they didn't just send the same one back to you?

Try placing just one of the trucks onto the track to see if it runs.

Springfield PA

NJT
  • Member since
    July 2008
  • From: NJ
  • 18 posts
Problems with an Atlas NJT GP40
Posted by NJT on Wednesday, June 9, 2010 10:43 AM

 Hi all. I recently bought an Atlas NJT GP40 with sound and DCC in it and when I went to go put it on the track, i noticed that it would constantly short out. So first I checked everything on my layout to make sure nothing was out of place or lose wires or anything metal was laying on the tracks. After that, i decided to send the engine back to walthers in exchange for a new one. When I got my new one today, it was doing the same exact thing. All my other Atlas engines and other engines run perfectly fine, but this one.

Does anyone have any ideas as to whats wrong?

 

Tony

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!