Skip to main content

Okay, so I have the DCS Remote Commander that comes with the RTR sets.  Last year when I bought both it and my original SD70 everything worked fine.  I bought a second SD70 from a fellow forum member and finally had time to put it on a test loop today.  It is the only engine on the track, I know that you can't run two at a time with the commander.  When set on the track, it powers itself up and sits there and idles.  It does not respond at all to the remote.  At one point, it even took off (not too fast) on its own.  Not for a second do I believe the engine is faulty, I even had a video of it running sent to me prior to shipping and I definitely trust the guy.  So and I missing something?  Does the engine need reset?  If so, is that something I can do? 


Any suggestions or help?


Thank you

-Mike

Original Post

Replies sorted oldest to newest

Mike,

 

First, you most certainly can operate two PS2/PS3 engines at the same time with the DCS Remote Commander. You just cannot operate them independently of each other.

 

If the new engine immediately powers on when you turn on power, either there's something wrong with it or with the DCS Remote Commander.

 

Place both engines on the track together and turn on power. If ones stays silent and the other powers up, the one that powers up is the problem.

 

If both power up, the DCS Remote Commander is the problem.

 

If both stay dark and silent, press Startup on the handheld. Both should power up. If not, the one that doesn't power up has a problem. If neither one powers up, the DCS Remote Commander has a problem.

Last edited by Barry Broskowitz

Barry,

 

I stand corrected then!  I assumed that if you had two on one loop, only one would respond.

 

Okay, I will give that a try.  Out of 4 times I put it on the track, it came on twice and stayed off twice.  Do the Remote Commanders just go bad?  After having it out for maybe a week last year, its been put away since.

 

But I'll give that a try and report back. 

 

thanks

-Mike

It is connected via lighted lock on.  Okay, the original engine starts up and runs just fine.  The "new" one... does not respond at all. When it does not power itself on, if I "wiggle" the back of it a little bit, it turns itself on.

 

If it is indeed the engine (which is what it sounds like), any idea what it could be?

 

Thanks

Mike

Mike,

 

It sounds like there's an intermittent break in the electrical path between either the pickup rollers and the PS2 board, or the wheels and the PS2 board.

 

Clean wheels and pickup rollers, and test for electrical continuity from the rollers to the board, and from the wheels to the board. Look for broken wires, possibly inside their insulation, or loose connectors.

Last edited by Barry Broskowitz
Originally Posted by mrmacher:

Could this engine have not been "factory reset" when you received it. 

That's sure what it sounds like to me.  If the previous owner was operating with full DCS and then shipped the engine to you, there's a better than even chance that he did not re-set it to factory default before shipping.  That needs to be done via the full DCS system.  Sure worth a try!

The problem sounds to me like the engine isn't getting power until it gets "wiggled". This would indicate to me that the engine isn't seeing the watchdog signal and therefore isn't responding to DCS. Rather, it powers up after the watchdog signal has come and gone, and does so in conventional mode.

 

When it gets pushed around a bit it makes contact and starts up in conventional mode. This would indicate a loose power connection between the pickup rollers or wheels, and the PS2 board.

 

If it wasn't for that, I'd also suspect that the engine is in need of a Factory Reset or a Recover Engine command.

Last edited by Barry Broskowitz

" I bought a second SD70 from a fellow forum member and finally had time to put it on a test loop today. "

 

Just a thought here, and I'm kind of new to all this still, but the above line jumped out at me calling for the full DCS reset, as this is the one that he is having trouble with. Surely might be worth a try? Especially if that forum member had a full DCS system. If not then I'll get out of the way.

Ok...first, I'd like to thank all of you for taking time out of your evening to help.  I was just at Patrick's for his big train meet.  Bob (I hope he finds this because I can't remember what he told me his display name was) had a FULL DCS System setup.  When I told him what was wrong, he stopped running his own NYC engine and helped me out.  I told him (maybe he told me, can't remember) that it might need reset (my initial thought and later read thats what you guys suggested).  Put it on his little set up he had, reset, works.  So, thats all it needed.  Came home, put in on the little loop I set up and it works just fine.

 

Problem solved.  I have the full DCS System.... in the basement.....in the box.....never set up.  I was in a rush today and it probably would have taken me forever to figure out how to reset it.  Thanks to helpful people in this hobby, I didn't need to go far to find help, so thank you all (and Bob).

 

-Mike

Post
The DCS Forum is sponsored by

OGR Publishing, Inc., 1310 Eastside Centre Ct, Ste 6, Mountain Home, AR 72653
800-980-OGRR (6477)
www.ogaugerr.com

×
×
×
×
Link copied to your clipboard.
×
×