Skip to main content

The data:  I have a pretty big, complex, layout:  25 x 40, multi-level, 5 TIU's [Version 4.20], 10 AIU's, 20 Lionel 180w bricks [4 per TIU] for 20 blocks.  SUPER mode is a requirement.  Wired a la Broskowitz.

 

The problem:  VERY slow response....several seconds per command.  Unacceptable.... I HOPE!

 

Testing done:

1.  Tether a TIU to the remote:  Very fast response.  [Like it should be!]

2.  Change a TIU to NORMAL mode:  Very fast response. [Like it should be.]  Of course, this mode stifles operations.....

3.  Checked, tightened all 'transceivers'......TIU's & remote; again a la Barry B.

 

Key Q:  How to fix it?

One suggestion:  Upgrade to Version 4.30 [?]  4.31[?].  Presumably, SUPER mode has [much?] faster responses.

Related rumor:  These still have bugs.

 

OTHER SUGGESTIONS SOLICITED!!!!

 

Original Post

Replies sorted oldest to newest

Phil,

 I haven't seen it in Barry's book....

I don't see how you could miss it. However, it won't correct whatever is wrong, rather, it will just mask the symptoms.

 

Regardless, it's described on pages 43-44:

DCS release 4.0 or later provides two different operating modes for the DCS Remote. To set the Operating Mode, use the thumbwheel to scroll to OPERATING MODE and press the thumbwheel to select it

• Select Normal mode by scrolling to NORMAL and pressing the thumbwheel to select it. The display will show SET TO NORMAL

• Select Speed mode by scrolling to SPEED and pressing the thumbwheel to select it. The display will show SET TO SPEED

• Press the Menu key to return to the top level menu

 

When Normal is selected, the DCS Remote will operate at the speed it did in previous releases of the DCS software. When Speed is selected the response time of the DCS Remote is improved. This is accomplished by instructing the DCS Remote to ignore responses from the TIU when a command is issued. Further, the DCS Remote will not display any error messages that may result from commands that the TIU could not successfully complete. The downside of selecting the Speed operating mode is that the DCS Remote will be unaware of any errors that may occur (Under DCS 4.10 when operating under Speed mode and a subsequent command that requires Normal mode to execute correctly is issued, such as Add Engine, DCS will temporarily switch into Normal mode to execute the command and then will switch back into Speed mode)

 

This and a whole lot more is all in MTH’s “The DCS O Gauge Companion 2nd Edition", available for purchase as an eBook or a printed book at MTH's web store!

 

Last edited by Barry Broskowitz

Phil g,

   In most cases you will find 99% of what a DCS runner needs in Barry's book, he is a great technical writer, however technical writing and my engineering mind do not always match up, and sometimes I must look in different places in his book than my logical engineering mind is directing me, to find his technical info.  This is why most engineers are not good technical writers, we stink at it.  Technical writing is a gift in itself, when you think the book lacks the technical info you need, look again

99% of the time you will find it in a different place in the book.

PCRR/Dave  

Last edited by Pine Creek Railroad

Speed mode definitely solves the problem of waiting for an acknowledgement from the locomotive/TIU. It is especially effective when running multiple trains with multiple operators and moving from zone to zone.

 

We took it a step further at the club and put together a separate setup track with its own TIU and require members to add/edit their engines on the setup track only with a tether connection. That prevents the remote from reaching out to the other TIUs when adding an engine and potentially grabbing an engine running on the layout. This also forces the added locomotive to associate with TIU#1 even though the remote stores the information.

Phil,

Sometimes the command from the remote is not received [esp. via QUICKSPEED], with the result that no change occurs.  I then must re-issue the command.  So far tho', on balance, the SPEED mode has more +'s than -'s.

Actually, what you've done is trade a slow response and/or error messages for NO response.

 

As I said previously, Speed Mode doesn't fix anything, rather, it masks symptoms. Where before you would get a slow response or maybe an error message before a response, as the remote resends commands, now you'll get no response at all.

 

Speed Mode works just like TMCC. A command is issued once only and no response from the TIU is required, expected or acted upon. The remote becomes deaf as a post.

 

You still have the same problem in your layout, however, it now presents itself differently.

Last edited by Barry Broskowitz

Add Reply

Post
The DCS Forum is sponsored by

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

×
×
×
×
Link copied to your clipboard.
×
×