Skip to main content

Replies sorted oldest to newest

Originally Posted by Barry Broskowitz:

John,

If you have multiple remotes and TIU's, is it possible in normal operating to get duplicate ID's for the engines?

Typically, only if you add them to multiple remotes out of sequence.

 

What has this to do with the ALL command? The ALL command doesn't modify DCS engine ID#s.


This is exactly why we assign each member a string of addresses   Any engines they run at an open house or operating session have to have those addresses assigned.  We have about 16 remotes floating around and had problems with duplicate addresses.  I remember one time one of my trains started up and went in reverse out of the yard with a 40 car string of hoppers.  

 

So if I get this right let me give an example  I have a remote with three engines in the Active list  Three other remotes are also in use with a number of engines in their active lists.  If I use the All command I can control my three engines without worrying any other engines will be affected by my command as long as they dont have my addresses.  This sounds like a pretty good way to get around the lashup bug that is out there

Originally Posted by Barry Broskowitz:

John,

If you have multiple remotes and TIU's, is it possible in normal operating to get duplicate ID's for the engines?

Typically, only if you add them to multiple remotes out of sequence.

 

What has this to do with the ALL command? The ALL command doesn't modify DCS engine ID#s.

Barry, I was responding to the previous comment by Dave, did you read the whole thread?

Ben,

So if I get this right let me give an example  I have a remote with three engines in the Active list  Three other remotes are also in use with a number of engines in their active lists.  If I use the All command I can control my three engines without worrying any other engines will be affected by my command as long as they dont have my addresses. 

Yes, that's essentially correct.

I knew going in the All button controlled only active engines in my remote. Say these engines are addressed as 1 2 and 3. Someone else has engines on the same layout or a layout close by will my All button give commands to engines addressed as 1 2 and 3 in other remotes?

 

One workaround is mentioned above by assigning channels. Another would be TIU addresses. i.e. A show where there is an adjacent layout. One layout would use TIU 1 and the other TIU 2. This would prevent other remotes from controlling trains on the wrong layout.

 

This brings up another hypothetical question. If we were all at a train show and there were 5 DCS layouts next to each other all using multiple TIUs and super mode. Can this be setup as 5 different supermodes? Layout 1s TIUs and remotes set on TIU 1. Layout 2 TIU 2 etc etc.

 

Too answer my own question, it would seem yes as each handheld only address the TIU number assigned to it. I doubt TIUs have to be set as 1 to be in supermode.

Last edited by F&G RY

Jim,

Someone else has engines on the same layout or a layout close by will my All button give commands to engines addressed as 1 2 and 3 in other remotes?

Yes, it will, if the TIUs have the same number as your TIU.

If we were all at a train show and there were 5 DCS layouts next to each other all using multiple TIUs and super mode. Can this be setup as 5 different supermodes?

No. Supermode is Supermode.

 

Further, there's a little known bug in DCS that will address all TIUs as being in Super TIU mode even if only one has actually been set to Super mode.

Layout 1s TIUs and remotes set on TIU 1. Layout 2 TIU 2 etc etc.

If each layout has only one TIU, why use Super TIU mode at all? Just number TIUs differently from each other or tether each TIU to its remote.

 

You should also understand that it's not the TIUs that are set to Super TIU mode, rather, it's the remotes.

 

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!

 
 

Barry in my scenario each layout used multiple TIUs thus each layout would be in supermode.

 

By your above post tethering handheld to a TIU would eliminate the air signal so other TIUs would no pick it up.

 

Is this true? I put my handheld in supermode and address engine #5 will this address every #5 engine active or not and assuming it is on a active DCS track on every layout in RF range assuming my Handheld is not tethered.

 

I know these scenarios sound a little crazy but certainly can come. Maybe not 5 layouts but certainly 2 next to each other can and will come up. The answers should be the same as worst case scenario.

A tethered  remote only communicates with the tiu it's tethered to. We use one tethered for  programming engines on a small siding while the rest of the layout continues on.

 

Scenario.. If you added all 5 tiu and set them to super mode  in your remote you could talk to any tiu  .( Providing you're in range).

 

It always hasn't been this way but is now.

I tried putting things in supermode. Had to go to TIU setup and it gave choices of TIU 1 with softkeys of NOR or SPM.

 

With no TIUs powered the handheld set TIU 1 (address?) to supermode.

With no TIUs powered tried changing TIU address out of RF range.

 

Changed TIU address to 3 then tried changing to supermode. Screen came up TIU 3 with choices of NOR or SPM.

 

This is actually getting strange. If my TIU is set to supermode it will control all engine addresses on any active DCS track within RF range at this point assuming no tether. If I pick another handheld set to TIU 1 NOR it will only control those engines on active tracks with a TIU 1 signal. Pick up a 3rd handheld addressed to TIU 3 NOR same thing over and over till 5.

 

Will do more experiments as I have more ?s.

Gregg. Then a tethered remote does not send out a RF signal. Can a TIU receive a RF signal if it is tethered to a remote?

 

A scenario: engine #5 running on your mainline. A engine on your programming  track addressed as #5. The programming track is active by a tethered TIU at the same TIU address as the mainline. Give a command via another handheld to the engine #5 on the mainline. Do both engines react to the command?

Jim,

Is this true? I put my handheld in supermode and address engine #5 will this address every #5 engine active or not and assuming it is on a active DCS track on every layout in RF range assuming my Handheld is not tethered.

Yes, all powered #5's will  be activated.

 

Simply put, a remote in normal TIU mode or Super TIU mode will always attempt to talk to any TIU that it knows about, i.e., that has been entered unto it.

 

Further, if a remote is in Super TIU mode, due to a DCS bug it will always attempt to talk to any TIU, regardless of whether or not that TIU has been entered into it.

 

The solutions are

  • Tether single-remote layouts 
  • Use different DCS ID#s for multiple TIU layouts
  • Use different engine numbers on different layouts.

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!

 
 

Jim,

Then a tethered remote does not send out a RF signal. 

No, it does not.

Can a TIU receive a RF signal if it is tethered to a remote?

No, it cannot.

Does supermode amount to this? One handheld addressing all 5 TIU addresses at once.

That is a gross oversimplification of the process.

 

I suggest that you stop experimenting and get an understanding of how things work before you mess things up completely:

  • You can add a TIU that's not powered up (because the only changes made are in the remote).
  • You can change a TIU between Normal and Super mode that's not powered up (because the only changes made are in the remote).
  • You cannot edit a TIU that's not powered up because the TIU is actually changed..

I have nothing messed up. Trying to learn this stuff before my club goes to DCS and we run into problems with an interaction with other layouts.

 

It happened once before when we were controlling and loading engines with the group next to us. None one in our group and only one person in the other group knew to change TIU addresses.

 

That maybe a oversimplification of the process but it essentially what is happening to the trains.

 

 

Experiment: I power up mt STD gauge layout leaving my O-gauge layout off. Change TIU address to 3. Power up my O-gauge layout with TIU set at address 1. The handheld will not power up engines as it can not talk to TIU 1. This is correct.

 

I change the handheld to supermode. It says TIU 3 NOR SPM. It then controls my O-gauge TIU also. This is correct.

 

At first, I thought it read it would only control TIUs set to address 3. What it really means is that pressing the NOR softkey the handheld will be set to address 3.

Hey Jim... I don't know of a way to change the start up direction . I usually go by the book for lash-ups . As far as one unit only receiving the command, can't that also happen to a by the book lash-up. Would you believe QSI(not MTH proto-1) could change the engine start up direction with feature five  20 years ago. Hey  maybe dcs could have this feature in the near future.

Yep! having fun with dcs  is not always about running trains. I've been in a few situations were I had my remote screen completely blank and also a engine with no sound .lights or anything. just a faint relay click. got'em all back, just don't know how.

 

I use the all command often.  It will run everything on the active engine screen.  I usually run two trains on each main line.  On my catenary lines I run three trains on the same track in the all mode.  This way the Z4K is only powering the three locomotives.  All the passenger cars are powered from a ROW transformer to the center rail.

Originally Posted by F&G RY:

Gregg

bring up engine. Menu,control,DIR control. This edits direction cycle. F/R F/F R/R there is no R/F. 

 

Not sure: but I think the lead engine board makes the trailing engine boards act like slave boards in a traditional lashup thus avoiding the above problem.

Yep. No R/F but maybe in the future . On the other hand.... QSI (not MTH)conventional was  very similar to DCS command except the  features were accessed with whistle, bell, pulses and raising and lowering the transformer handle in conventional mode. Quite a system for it's time. Maybe there's a reason why we don't have this feature yet. 

Post
The DCS Forum is sponsored by
×
×
×
×
Link copied to your clipboard.
×
×