Using 2 remotes and 1 TIU

Each engine must have the exact same DCS ID# in all remotes in which it has been entered. Otherwise, only the last remote to which an engine has been added will be able operate the engine.

Depending upon how Amy engines you have in each remote, it might be wise, necessary, to delete all engines form all remotes and then add them back, one engine at a time, two each remote in turn.

Everything that you need to know about DCS is all in MTH’s “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 MTH's web store!

One way to fix this is to dup the contents of the remotes so all of them have the same engine list.

John,

drodder posted:

I have been running into a problem with have 2 remotes. I'm getting some kind of overlap with engines, meaning when I load engines to the remotes 2 engines start when I pick one to start. Is it just a matter of changing the address on one of the engines. I'm using two remotes (might be three later) so I can have multiple engines on each of my 3 main lines with different people running each main line. Any help with this would be great.

Dan

It does sound like 2 engines have the same ID if both start up. Take one off the track and change the address of the other. Now add the engine that you took off the track.or delete the engine  and add them back one at a time using a programming track. Make sure  the engine has the same address in each remote (as mentioned0

Barry Broskowitz posted:

John,

One way to fix this is to dup the contents of the remotes so all of them have the same engine list.

If different engines have different DCS ID#'s in different remotes, that may or may not work. How do you know if any one remote has all the right DCS ID#'s?

Barry, are you saying if I clear a remote out and then backup a "master" and restore it to the cleared remote that the numbers will be different?  How can that be?

I don't have all the engines on all of the remotes. Track one engines on remote 1 and track 2 engines on remote 2. One of the engines on remote one when started also started an engine on remote 2. I did try the changing address thing and it seamed to work for a while but I add more engines and had a couple overlaps. Would it make sense to make a master list of my engines (1 thru 99 lets say) and when I load them to the remote (weather 1 or 2) and use the list location number as there address? Would that stop the engines from starting together? Now that I'm thing of it, is the problem in the DCS remotes or the boards in the engines?

What you're describing  happens when one doesn't use a programming track with multiple engine receiving power else on the layout.

Ex, we have 7 or 8 remote with 4 tiu ,

To add engines we use a  programming track  so only that track has power with a perfect DCS signal.

Using the programming track or equivalent one engine only.

We add one engine to one remote, and then the same engine to remote #2 ,making sure the  engine the engine has the same ID now in both remote,,, We do the same for the remaining remotes.

Yes a list might be a good way to keep track of your engines once you get them added correctly.. (we have one)

Here's what may throw you a curve,,,,, a weak or dead engine battery, the engine will revert back after power down to it's old id & settings.   

I do have a program track, just for loading and testing engines. I do not have any engines on multiple remotes. All of my engines are PS3 or PS2 with super caps and a couple Lionel with ERR boards. Sound like a list would be my best bet.

Bring up one engine at a time on your remote and check the address on the left. Say if it's address is 10, make sure the address is 10 on the second remote. If it isn't you need to change the address to be the same as the other remote.

Menu / System / Engine Setup / Edit Engine / Edit Address / Select Engine /  Select the address

Do the same with the other engines.

A little more complicated than that Joe, you need to verify which of the mis-matched addresses is the actual engine address, or you'll just make both of them wrong.

John,

are you saying if I clear a remote out and then backup a "master" and restore it to the cleared remote that the numbers will be different?  How can that be?

No, not at all.

What I'm saying is that there may not be one remote that's correct in the first place. He really needs to reset his remotes and do one of two things:

• Add each engine sequentially to all remotes before moving on to the next engine to add
• Add all engines to one remote, back it up and then restore it to all other remotes.

OK, that makes sense.   I figured you meant something different as I know you are "somewhat" familiar with DCS.

I DO NOT HAVE ANY ENGINE ON MORE THAN ONE REMOTE. I have (at the moment) 2 engines on remotes 1 and 3 engines on remote 2. All 5 engines are different engines. My Iowa interstate on remote 1 started my MTH demonstrator on remote 2 but after that they both locked up. I cleared both remotes and loaded the Iowa on remote 1 (address 1) and the demonstrator on remote 2 and moved to address 2, now they are working fine. Added a NS SD40 to remote 1 and it loaded on address 2 and at this point everything was working fine. Added a Santa Fe F3 to remote 2 on address 3 and now the NS started the demonstrator on 2. So my point is... I need to make a list of engines and assign address to each engine and no matter what remote they are on use that address only. I'm not adding every engine I have to every remote just so I don't have people trying to run someone else's engines.

You're obviously missing the basic point!  If you reset all the remotes and then add three engines to one remote, they'll be numbered #1, #2, and #3.

If you now pick up another remote that has also been cleared, and add three different engines to that remote, the will also be numbered #1, #2, and #3.

See the problem?

That John is exactly what I didn't know was the problem. I thought it read the engine as a number and not the remote assigning a number. That is why I asked the question. Thank you.

The numbers are somewhat "fluid".  If the engine has been reset, or the current engine number is already in the remote, the remote will assign a new number based on what is free in that remote.  However, if you have an engine #63 in the above scenario with only 1,2,3 occupied, it will remain as #63.  Understanding how DCS handles engine numbers is key to preventing issues with multiple remotes. 

Bottom line, sometimes the remote will assign a number and change the engine to match, and sometimes the current engine number will remain as is and simply be recorded in the remote.  What happens depends on the contents of the remote and the current number of the engine being added.

It is a little confusing at first, and if you think managing a layout with one set of engines and multiple remotes is confusing, consider our club scenario.  We have a modular show and a dozen or more people show up with DCS locomotives.  They all have their remote with tons of engines loaded, and of course the numbers are all over the map!  If we just let them plop the engine on the tracks with three other DCS locomotives from other members and their remotes, it would be pandemonium.  We ended up having club remotes and each member gets assigned locomotive numbers.  They change their locomotive to one of the assigned numbers to run.

I can't imagine this on that size of a layout. I have a great deal of respect for the large club layouts using DCS or Legacy (or both like mine), lots to keep track of. I have managed 6 engines at once on mine but after a while it makes my head hurt. LOL

Drodder, instead of trying to keep a remote for each loop, one should just put all locos into one remote.  The save it to a computer using Loader 5.0, and then clone the other remotes. 

Your problem now is that you have multiple engines with the same ID. 

I have 4 remotes, each of which is identical to the others, even t the soft key arreangement, since I used the cloning process

I have now loaded all engines on one remote and cloned the others with my putter. I seem to be have a signal loss problem also. The fun is running away fast.

Weak remote batteries ?  

I thought about that too, so I changed the batteries. Sometimes the engine comes on when power is turned on, next time it runs away or I can't find the engine with the remote. All over the place right now.