DCS Commander Questions

Normal.

It's an early version of DCS.

Thanks

Another question - did this make it to O gauge or just in HO?

O scale has it- but not all engines have that feature. Mostly a PS3 Premier feature.

Example, a Railking Rugged Rails PS2 3V starter engine- probably not.

My O-gauge L-shaped layout is dual-wired with Lionel's TMCC and MTH's DCS.  The hand-held controller for the DCS Remote Commander is slower reacting than TMCC. Further, the DCS system requires a "line of sight" path from the controller to the receiver clipped to the track. In my case, I must remember to stand in "the right place" to communicate a DCS command; i.e., not behind an "L" corner.  Otherwise, it works OK.

Mike Mottler    LCCA 12394

.

I have three questions about the Remote Commander. (Maybe more )  I have Legacy Cab 1L system and was considering adding a Remote Commander to run a few MTH engines. I guess Mike can answer these questions, since he has a similar setup.

The DCS Remote Commander will only operate one MTH Proto 2 or Proto 3 engine at a time, correct?

Do you need to remove all MTH engines but one from the track when using the Remote Commander?

Does the Remote Commander have to be "reprogrammed" to communicate with each different MTH engine when it's put on the track, or do you just aim it (line of sight) at whatever engine's on the track and go?

@Mike H Mottler posted:

My O-gauge L-shaped layout is dual-wired with Lionel's TMCC and MTH's DCS.  The hand-held controller for the DCS Remote Commander is slower reacting than TMCC. Further, the DCS system requires a "line of sight" path from the controller to the receiver clipped to the track. In my case, I must remember to stand in "the right place" to communicate a DCS command; i.e., not behind an "L" corner.  Otherwise, it works OK.

Mike Mottler    LCCA 12394

.

The problem- MTH used the name twice for 2 radically different devices- just another reminder when asking technical questions- like it or not, you need to mention the product number so that we know EXACTLY what product we are discussing.

The 50-1028- the original DCS Commander Controller- was mostly aimed at HO scale and specifically outputs DC, was intended also in conjunction with DCC passthrough, and could be used for other scales. https://mthtrains.com/50-1028. It was made starting around 2013--- and is no longer made and not really supported. Last firmware update was 2011 version 1.4. Compare that to DCS TIU and Remotes at version 6.10 https://mthtrains.com/dcs-software-downloads

Much later and VERY different, the 50-1033 DCS Remote Commander Set, is a lower capability remote control option for DCS, and in some ways, the lowest current offered tier of actual DCS control made. https://mthtrains.com/50-1033 This came out later in 2010. A recent batch of these just shipped this spring and there are no firmware updates no computer interface for updates on these. They are the bare minimum level of DCS control.

Again, the names are similar but they are VERY different devices.

@breezinup posted:

Three questions about the Remote Commander:

The DCS Remote Commander will only operate one MTH Proto 2 or Proto 3 engine at a time, correct? False in it's own way. This is a simple device- it transmits commands to native DCS ID 1. It requires any engine to work with it be reset to ID1. So technically, if multiple engines are on the track and set to ID1, then they respond kind of like and all engines command.

Do you need to remove all MTH engines but one from the track when using the Remote Commander? See the rule above. If other engines had been added to a DCS system (TIU, or DCS Explorer) and thus have an ID other than 1, they won't respond.

Does the Remote Commander have to be "reprogrammed" to communicate with each different MTH engine when it's put on the track, or do you just aim it (line of sight) at whatever engine's on the track and go? NO, then ENGINE needs to be reset to factory defaults to return to ID1. Caveat, while there is a command sequence that the Remote DCS commander can reset some PS3 engines- not all engines have chain files (firmware) that supported that feature. What that means is, you may need something like a Zcontroller or other transformer with conventional bell and whistle- or even in some cases, a full DCS setup (example TIU or DCS Explorer) capable of performing the reset to get the engine correctly to ID 1.

That basic 50-1033 is what I was referring to. I only have a couple MTH engines (both Proto 3) and was considering getting one of those to operate them.

Vernon, thanks very much for the information. It sounds like, bottom line, the Remote Commander doesn't have to be reprogrammed for each engine, as long as all are set to default ID 1, but only one MTH engine can be on the track at one time.

@breezinup posted:

That basic 50-1033 is what I was referring to. I only have a couple MTH engines (both Proto 3) and was considering getting one of those to operate them.

Much of what I just answered and outlined is in the manual https://mthtrains.com/sites/de...ction/50as10109i.pdf

* The DCS Remote Commander will
ONLY operate locomotives equipped with
M.T.H. Proto-Sound 2.0 and 3.0 systems.
Locomotives equipped with Proto-Sound
2.0 must be the 3 volt model. The 3-volt
model can be distinguished by its square
battery charging jack typically found on the
bottom of the locomotive or under any
removable hatches on the top of the body.
Locomotives will ONLY operate with the
DCS Remote Commander if they are set to
the factory default settings. If the Factory
default settings must be reset, the reset
procedure - in some cases - can be done
with the Remote Commander by following
the procedure on page 7 of this manual. If
that procedure fails to reset the locomotive,
then a conventional transformer (like the
M.T.H. Z-500, Z-750, Z-1000 or Z-4000)
can be used by pressing the bell and whistle
buttons in the order described on page 7 of
this manual.

One note and a discussion that has happened in the past- while the manual states explicitly that ONLY PS2 3V models work with the remote commander, there are examples where PS2 5V has been said to work.

Thanks again. Yes, I seem to remember hearing something in the past about if your engine isn't set to default ID 1, you're out of luck unless you find someone with the MTH transformer, or else buy one yourself, to change the ID. Since my engines are PS3 and are new, I assume they're on ID 1 already, and this shouldn't be a problem.

Thanks for that great explanation Vernon.

I also have the DCS Remote Commander system on my layout, along with a Z1000, and my trusty old Swiss Buco transformer (I haven't hooked-up my Z4000 as it won't run some of my early PS1 loco's). I have toggle switches between each power source so I can power the single line layout with whatever transformer I need to run the different types of loco's I have.

Never thought about running two PS2 or two PS3 loco's at the same time on the same line using the DCS Remote Commander......food for thought!!!

And yes Mark, I also have found a slow reaction time when pressing the red "change direction/stop" button on the hand-held remote, if the loco is a distance from the "line of sight" receiver. To my way of thinking though Mark, when you get used to it, it is far less troublesome than the fully blown/expensive DCS system that often gets mentioned here.

Just my two cents worth.

Peter.....Buco Australia

@breezinup posted:

Thanks again. Yes, I seem to remember hearing something in the past about if your engine isn't set to default ID 1, you're out of luck unless you find someone with the MTH transformer, or else buy one yourself, to change the ID. Since my engines are PS3 and are new, I assume they're on ID 1 already, and this shouldn't be a problem.

You're thinking of the DCS Remote Commander, there's no problem setting the ID with the DCS Commander.  These are two totally different products.

DCS Commander

DCS Remote Commander

@gunrunnerjohn posted:

You're thinking of the DCS Remote Commander, there's no problem setting the ID with the DCS Commander.  These are two totally different products.

DCS Commander

DCS Remote Commander

That's what I understand. As I mentioned, though, the DCS Remote Commander is what I have. I understand that I'd have to get something like a DCS Commander, or find someone who has one, in order to change engine IDs.

If I get more into operating DCS engines, from what I've been able to gather, the upcoming WiFi WTIU will "solve all problems," and take care of all contingencies, although at a pretty steep price. I guess just the thing for big DCS operators. In the meantime (and maybe longer), like Mike Mottler, I guess, the DCS Remote Commander may serve my needs. I'll see.

Thanks again to Vernon , and John, for the information.

FWIW, I never found a 5V PS/2 locomotive that wouldn't work with the DCS Remote Commander if it was first Factory Reset using the full DCS system.  That's most likely 99.44% of the problems using the DCS Remote Commander with PS/2 or early PS/3 engines.  Around 2014, there was a mod to the PS/3 software to allow a special key sequence on the DCS Remote Commander to reset those engines to run with the DCS-RC.  Earlier engines HAD to have a Factory Reset using the full DCS.

Aaaannnddd…..another question🤔

Can I bring up time and distance for PS2/PS3 engines on the DCS Commander? Don’t see anything in the operator’s manual!

@gunrunnerjohn posted:

FWIW, I never found a 5V PS/2 locomotive that wouldn't work with the DCS Remote Commander if it was first Factory Reset using the full DCS system.  That's most likely 99.44% of the problems using the DCS Remote Commander with PS/2 or early PS/3 engines.  Around 2014, there was a mod to the PS/3 software to allow a special key sequence on the DCS Remote Commander to reset those engines to run with the DCS-RC.  Earlier engines HAD to have a Factory Reset using the full DCS.

Glad you mentioned that, GRJ. One of my engines, although with Proto 3, was from 2013, so it may need a Factory Reset to operate with the DCS RC.

@breezinup posted:

Glad you mentioned that, GRJ. One of my engines, although with Proto 3, was from 2013, so it may need a Factory Reset to operate with the DCS RC.

If it has never been added to a DCS system it will work without issue. The earliest PS2 5-volt systems are the only ones that may need a factory reset from a full DCS system in order to work with the DCS Remote Commander (if they have never been added to a full DCS system).

And as GRJ mentioned earlier, I've never run into a PS2 5-volt engine yet that can't be run with DCS-RC after a Factory rest from a full DCS system.

Having a problem now adding engines to DCS Commander. Have added 7 separate PS2 and PS3 engines smoothly, so far, while playing around to get comfortable using this device. Now, every additional engine I attempt to add brings up “add Er”, and the screen defaults to eng1. Also the M for momentum is on, and doesn’t shut off when power is disconnected. And, pressing, and holding, the reset button doesn’t bring the  word “reset” to the screen, so the reset process can’t be started. Ideas appreciated. Thanks.

Mark- I run DCS engines with a remote commander and TMCC with a Cab 1L. Both work fine together. As stated, the RC only will control one engine at a time, and it has to be at the factory original address. The RC remote is a little slow to respond to button pushes.

I have run both PS and TMCC engines at the same time and it works fine. I mounted the RC under the fascia board on the edge of the layout since it is a IR- line of sight, control signal.

Bob

Bob - this thread was hijacked by, and the topic conflated with, questions about the DCS Remote Commander, when it was started by me about the DCS Commander, 2 completely different devices.

Please read Vernon Barry’s eloquent explanation of that difference in the first few posts in the thread.