Running Remote Commander and DCS Remote

For the DCS remote commander, just wire it to the track loop in question without anything connected to the input power, that will run it in "passive" mode.  Run the transformer directly to the tracks.

As for running both DCS and the DCS Remote Commander, clearly that won't work on the same set of tracks, the signals will be stepping on each other.  I think you can probably run them on separately powered track segments, though I've never personally tried it.

Why do you want to use the DCS Remote Commander since you have the full DCS system?

The only way I see to use the TIU and the DCS remote Commander together on the same tracks is to turn off DCS on the TIU channel and just use it to kill the power, and control the train with the DCS Remote Commander.  Is that what you're trying to accomplish?

John,

As for running both DCS and the DCS Remote Commander, clearly that won't work on the same set of tracks, the signals will be stepping on each other.

Actually, that works just fine! Been there, done that!

I thought the Commander would be easier and less likely to cause grandchild error when running a train.  They seem to have "button problems" with the DCS remote. The younger kid would be able to run his train while the DCS trains ran.

So, do I simply connect the Remote Commander Receiver to outputs on the terminal block coming from the TIU and going to the tracks or use the variable output on the Z4000 witih separate wires going to the tracks or do I still need to wire a Z 1000 to the tracks? I understand I will have to have the infared signal

See? Electricity in this case makes me leery of doing some thing wrong. Barry? Please tell me how you would accomplish this on a smaller layout capable of three train operation. 

Well, that amazes me!  How exactly don't the signals step on each other?

Given Barry's answer, I'd just connect the transformer through the TIU and then connect the DCS Remote Commander directly to the output to the track.  I'm surprised that works, and I'm going to have to see it to believe it.   I think I'll dig out the DCS-RC in the closet and give it a try.

John,

Think about it.

The DCS signal, unlike TMCC or Legacy, isn't "always on". Rather, it's only on when a command is being sent. The  DCSRC acts just like an additional another remote, albeit one that can only address an engine with e very specific DCS ID#.

Additionally, both send the same watchdog signal that affects all DCS engines regardless of their DCS ID#.

I wasn't sure they wouldn't step on each other, but that makes sense, I'll have to give it a go.

I guess in answer to the OP's question, the DCS RC will only be active on a single TIU output, as the other connections would presumably be to different power districts, right?

Barry, what do I have to avoid to keep the locomotive from becoming invisible to the DCS-RC?  As long as I don't do an Add-Engine, will it remain at it's current default ID?

One last point of clarification.

John, you wrote "connect the transformer through the TIU and then connect the DCS Remote Commander directly to the output to the track."

I already have a Z4000 connected to a TIU feeding a terminal block so do I connect the rerceiver to the terminal posts feeding the track? or are you suggesting a separate transformer wired to the TIU?  If so, which of the TIU terminals input/output would be safe to use? 

I apologize for my lack of understanding and I really would like to do this correctly.

If you have the transformer feeding the TIU, then the TIU feeding the track, you should just have to connect the DCS-RC directly to the track connections.  That can be at the terminal posts feeding the track or even directly to the track, same difference.  Don't change anything about the working TIU connections.

John,

the DCS RC will only be active on a single TIU output, as the other connections would presumably be to different power districts, right?

That's correct.

Barry, what do I have to avoid to keep the locomotive from becoming invisible to the DCS-RC?  As long as I don't do an Add-Engine, will it remain at it's current default ID?

You, that's correct. Once a DCS engine is added to a remote, it can no longer be controlled by a DCSRC.

This and a whole lot more is all in "The DCS O Gauge Companion 2nd Edition", now available for purchase as an eBook or a printed book from MTH's web store site! Click on the link below to go to MTH's web page for the book!

Already have the book.

John,

Already have the book

I know, however, the plug is intended for those who do not!  

Thanks for the input. 

I connected the RC as directed with the + and - from the terminal posts feeding the track.I didn't  make a connection to the receiver's VAC input though.  The receiver light is on and flashes when a key on the remote is pressed but nothing happens. The loco doesn't start. 

 I have new batteries in the remote and I am within range (a foot).I reset the locomotive and it doesn't show on the DCS handheld. The Z 4000 is set at 18.

Again, I must be missing something simple.  What could it be.

GGG is on to it, you MUST be at a factory reset condition for these to function with the DCS-RC.

....and you must have a sufficiently charged battery in the engine or the Factory Reset won't "take".

To test your battery, allow your engine to startup then remove track power and see if it plays the shutdown sequence completely.  If so it should be fine.

Can you try a different loco and do a factory reset on it, and try it with the RC.  If still no joy, I would think the RC is bad.   If this is new I would send it back for a replacement via dealer or MTH.  Some of them have not worked out of the box.  G

Thanks for thte tips.  The shut down sequence plays throughand battery checks show the battery is OK.  Is getting a number without a description of the locomotive normal when a person tries to add the locomotive back into the DCS?  I am getting a number without any information. 

The blank ID is normal for PS/2 upgrades, only the MTH tech folks have the proper software to permanently load a name.

I've never understood why for the upgrade kits that capability isn't offered to the end users that buy the kits...

If this is an MTH factory engine, then it should have the name come up.  Did you try a factory reset on a different engine and try it with the RC?  G

I tried another engine, went through all the suggested steps, and the results were the same.  The receiver light flashed and nothing happened after a button was pressed.  I am leaning toward the GGG's suggestion of a bad Commander.  I will be the first to suggest I am still not doing something even though I am following all the directions. I am sure its something simple.

The two locomotives I tried were both MTH factory PS 2 engines - not upgrades.  I am afraid to try another engine for fear of a bad outcome but I will.

Interesting about the name coming up or not. and I did use a dedicated track witih no other engines able to setart.

It is possible the RC bad and or the layout room has an effect on it.  I had one customer whose complained the RC didn't work.  Put it on our layout and it worked fine.  Controlled his engine and others (factory reset).

He took it home and still did not work.  His layout had two levels though it wasn't very large, and it was in a metal enclosed sunroom.  I can not explain why it would not work on his layout.  He bought the full DCS and runs trains fine that way.

You could try a small loop  in a different room and see if the RC works with your engine.   G

Sounds like a good plan.  I too have a small layout (20 x 12) with two levels though the room is drywall and has laminate flooring.  Putting a loop together would be something the grandkids could help doing - two birds with one stone sort of thing.

Let us know how it works out.  G