Skip to main content

Reply to "Weak DCS signals, Failed TIU Output Drivers, and Design Solutions devloped under collaboration between AGHR and MTH"

Adrian! posted:

More TIU channels has some drawbacks. One of the biggest flaws in DCS is that it operates serially. So when you add an engine or do a read it does something like this"

for (TIU=1;TIU<5;TIU++){for (channel=1;channel<4;channel++){LOOK FOR TRAIN!}}

Meaning it goes TIU by TIU channel by channel 1-by-1 to add engines, read, or anything else. Nothing is done in parallel. Adding engines takes literally 3-5 min with our 5-TIU setup (compared with 20 seconds on my single TIU layout). If you use the wifi APP things get frustrating after 2 TIUs. It just takes tooooo long to read, find engines, and stuff. Often the app will give a TIU timeout if all the checks don't finish in time.

 

One if the big ones I missed here is the panic reaction time. If you're like me you often run 2 or 3 trains from one remote. So someone screams "your train is about to hit my train" on a block that's serviced by TIU #5. Even if you're super fast and you select the correct engine the remote takes a good 30-40 seconds to poll TIUs #1 to #4 before it will poll #5 and switch to that engine as the active one in the app or on the remote. By then it's already a train wreck.

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

×
×
×
×
×