Skip to main content

Replies sorted oldest to newest

Jim,

First, the DCS Remote Commander will work with any PS2 or PS3 engine that has its factory default settings.

Second, your engines may have been test run with DCS either at MTH off at the store where you bought them. If they were added to a DCS Remote at that time and then were not reset to factory settings, they won't work with the DCS Remote Commander. In that case, they need to be factory reset before the DCS Commander can operate them.

From page 204 of TheDCS Companion 3rd Edition:

Newer PS3 engines, manufactured starting in 2014, may have the capability to perform a Factory Reset through a combination of button presses (SND, DIR, -). This is made possible by revised firmware in newer (2014) PS3 engines. 

Otherwise, a DCS engine cannot be reset to its factory default values using the DCS Remote Commander. A Factory Reset command must address the engine by its actual DCS ID#, which a DCS Remote Commander, which is a one-way communications device, can never discover. Further, while a transformer reset, in conventional mode, will return almost all of the engine's values to their factory settings, it will not reset the engine's DCS ID#. It is necessary to use a either a DCS Remote and TIU, or a DCS Commander, to reset all of a DCS engine's settings to their factory defaults, including the engine's DCS ID#. 

 

DCS Book CoverThis and a whole lot more is all in “The DCS Companion 3rd Edition!"

This book is available from many fine OGR advertisers and forum sponsors, or as an eBook or a printed book at OGR’s web store!
Last edited by Barry Broskowitz
stan2004 posted:

When you initially apply power to the track (with Remote Commander attached) do the engines start up (sounds, lights) or are they silent and dark?

No response at all. They stay dark without light or sound. I wouldn't mind so much if their catalog description had told us it didn't work with all their engines. The last MTH engine I purchased was the Imperial CP Royal Hudson so none are recent.

Jim,

I wouldn't mind so much if their catalog description had told us it didn't work with all their engines.

Please read my post above yours. Disregard the catalog - it's wrong. The DCS Remote Commander works with all DCS PS2 and PS3 engines. They come up dark and silent because it's working the way it's supposed to work!

You just need to get your engines reset to factory defaults. To do so, unless they are newer PS3 engines, you'll need access to a DCS TIU and Remote, or a DCS Commander standalone unit.

Last edited by Barry Broskowitz

Yes I read the comments about a reset. That info is also on the directions inside the sealed package. IF I had a DCS system to do a reset, I would not have bought or needed the commander set. It seems to me my engines should be at factory settings. I only made the thread so someone else would not assume what I did. But they moved it here so I guess others still won't know.

Last edited by Jim 1939
Jim 1939 posted:

No response at all. They stay dark without light or sound.

So the engines can at least hear the Remote Commander which tells all engines to start up silent and dark in command mode. This practically rules out something on your layout degrading the DCS command signal.

The last Hail Mary is to take 2 seconds to confirm you didn't swap the polarity of the wiring between the Remote Commander and your track.  That is, Red jack goes to center-rail, Black jack goes to outer-rail.  This reversal has been known to happen...and would cause the observed behavior.

I suppose the takeaway is even if one doesn't plan to use DCS, if you're buying an MTH DCS engine from a store, eBay, new, used, whatever, it's worth asking if the engine is/was factory-reset.

 

The DCS club members were able to reset the Royal Hudson so it now runs from the commander. It was a stubborn reset but they got it.  I just wish that OGR had left this thread on the 3r forum so others could learn from it. It wouldn't have hurt MTH to put a little more information on the outside of the package. Thank you for all the helpful post and I learned last night why the engine was not in factory settings. It was test run at the store before I brought it home and the store DCS assigned it a new number. I did not know theses things and there are a lot more like me out there.

Jim

 

Jim,

I learned last night why the engine was not in factory settings. It was test run at the store before I brought it home and the store DCS assigned it a new number. I did not know theses things and there are a lot more like me out there.

It's unfortunate that MTH's instruction manual that accompanied your DCS Remote Commander was erroneous in stating that the device would work only with PS3 and 3 volt PS2 engines, when it actually works with all PS2 and PS3 engines. However, you learned that it would work with all of your DCS engines, via posts on this thread, on April 24th, the same day that you started this thread.

Further, you didn't learn why the engine wouldn't work as you wanted it to "last night". Again, you learned this via those same posts on this thread. The fact that you almost a month to call the store and confirm that this was the source of your problem was entirely under your control.

The DCS Remote Commander is, in my opinion, an exceptional product, particularly at it's reasonable price point. I highly recommend it for anyone that desires to get a taste of DCS before committing to purchase the full set. It also bears repeating that it works with any DCS engine, PS2 (3 or 5 volt board) or PS3.

Lastly, the DCS Remote Commander can be of use to those who have a full DCS setup with TIU and Remote. It can work in concert with an existing DCS layout as an inexpensive remote control that allows a visitor or child to control an additional engine on the layout. It can also be used as a "watchdog signal generator" for sidings on an existing DCS layout. Both of these functions are described in The DCS Companion 3rd Edition, which has an entire section devoted to the DCS Remote Commander.

Last edited by Barry Broskowitz

Barry some of your remakes are uncalled for. I wrote an honest thread from what I knew. I also returned with info as I learned. The store you are referring to was Wild Bills Trains and sadly the owner had to close due to an illness he will have to fight an uphill battle to defeat. A person with your knowledge of DCS should be trying to help people not put them down.

Jim

Jim,

A person with your knowledge of DCS should be trying to help people not put them down.

Yes, I agree. However, wouldn't you agree that my post on 4/24 was somewhat helpful? Actually, it tuns out that it was exactly correct:

"First, the DCS Remote Commander will work with any PS2 or PS3 engine that has its factory default settings.

Second, your engines may have been test run with DCS either at MTH or at the store where you bought them. If they were added to a DCS Remote at that time and then were not reset to factory settings, they won't work with the DCS Remote Commander. In that case, they need to be factory reset before the DCS Commander can operate them."

I must admit that, based on the tone of your previous posts, I somewhat expected that you'd take offense where none was offered.

some of your remakes are uncalled for

So, tell me exactly which of my remarks was "uncalled-for"?

Last edited by Barry Broskowitz

this is why I bought the commander all in one unit, you can do a feature, factory reset on any 2.0 or 3.0 engine or the commander it's self. give any engine a new address, my opinion it's better then the remote commander.  some day I might go back to full DCS, just don't see the need when I can install 99 dcs engines on my commander. 

gunrunnerjohn posted:
DL&W Pete posted:

some day I might go back to full DCS, just don't see the need when I can install 99 dcs engines on my commander. 

Let's see...

Four channels vs. 1

DC or DC vs. 6A DC only

Wireless remote.

I'm sure there are a lot more reasons.

If you don't have a full basement layout, then you won't need four channels. I can run my commander from AC or DC power, run 4 different trains at once on 4 different tracks. You just can't walk around with it, plus it cost $350 less then full DCS.

Just as an FYI...

On Sunday, I E-mailed MTH to advise them that there was an incorrect statement in the DCS Remote Commander instruction manual, as regards which engines could be operated with the device. A few minutes ago I was notified that the copy of the manual on the MTH Protosound2.com web site has been revised.

The manual now states, on page 4, the following:

* The DCS Remote Commander will ONLY operate locomotives equipped with M.T.H. Proto-Sound 2.0 and 3.0 systems.

A copy of the revised manual may be viewed or downloaded by clicking here.

Add Reply

Post
The DCS Forum is sponsored by

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

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