NORMAL vis a vis SPEED control via the remote

hi did you make sure both remote n tiu have the same rev software! the latest rev is 6.10  I would update rev if you have not already done that! 

Alan

The locomotive to TIU communications typically seems to be the most touchy, so your analysis is probably correct.  Updating the software is very unlikely to affect this issue.  The usual causes of this king of issue is the same as for any DCS signal issues, proper track wiring, clean track, and eliminating any potential signal loops.

John,

The usual causes of this king of issue is the same as for any DCS signal issues, proper track wiring, clean track, and eliminating any potential signal loops.

I absolutely agree. Phil's issue is most assuredly DCS-signal related.

Phil and I have exchanged several E-mails in this regard. He declines to acknowledge that Speed Mode simply masks the symptoms of poor DCS signal issues and doesn't actually resolve anything. He isn't keen on troubleshooting the underlying issues and therefore wants to believe that Speed Mode simply makes his problems go away. Hence, his conjecture that his layout is "unique". That's not exactly news, since every layout is, indeed, "unique".  

Regardless, if he believes that Speed Control is a "solution", that's fine. However, DCS signal strength issues have a way of coming back and causing problems at the most inopportune times.

GRJ:  Thanks for supporting my hypothesis.    The "king of issues";  interesting comment!

Barry:  Please note the following,  which I've said B 4:  The SPEED option DOES INDEED "resolve" something!  It allows me to operate my RR without so many problems.  I also KNOW that it may "mask" another problem.  Finally, replace "unique" by "rare',  as I did in my opening statement.

BOTH:  Please define/describe "signal loops",  and how I might find and fix them......

Phil,

The SPEED option DOES INDEED "resolve" something!  It allows me to operate my RR without so many problems. 

You need to work on your vocabulary. Only the symptoms are masked, nothing is resolved.

Regardless, try to fix the problem or don't try to fix the problem. I've already fruitlessly spent too much time attempting to make you understand what actually is the problem and what is not a solution. Maybe someone else will have more success than I've had.

Touche'.  I should not have used the word "resolve".  Rather,  SPEED mode both masks the problem AND permits me to enjoy DCS.

I'd still like to learn more about "signal loops".  Is it in your book?

I'm not in the knowledge dept. with GRJ and Barry, but I do have a DCS system that works very well. Blocks, which are well described in Barry's book are what made a HUGE difference in my layout and eliminated all my DCS error messages that I was getting. Like ENgine not found, not on track, out of range, etc. I've forgotten what they all were as I have not had a DCS error message in over 3 years. Other than when I try to start an engine and forget to turn on the power to the spur first, of course. But that's operator (me) error, not DCS's fault. I got all my layout wiring information from Barry's book, tried to follow it as closely as I possibly could. That includes the block info. Also used the MTH terminal blocks specifically made for the recommended wiring and OGR's twisted pair wire. 

Thx, RTR12.  I'm pretty sure that we [Don Grabski did almost all of my wiring.] followed all the BB 'rules', too.....But I don't have the great performance that you do.  Mine is a pretty complicated RR:  5 TIU's  [Super mode, of course],  9 AIU's,  77 turnouts, and many different levels;  from above your head to 2' above the floor.

Phil, to analyze your problem would require a lot of data, like number of blocks, wire gauges, power layout, etc.

My 36x16 layout does not follow BB wiring (was built before his book, using the MTH manual), uses common bus, has about 70 toggle-switched blocks and 40 turnouts, 2 tius, 4 aius.  All power wire is 14 gauge.  Common bus, which also serves accessories and lighting, does not pass thru tius.

Works fine.

Have you several remotes and, if so, do they all have the issue?

RJR:  I just tested another remote.....Same deal.  So we can't blame it on the remotes.  It still seems to be that last part of the 'acknowledgement':  TIU to remote.  This is what 'hangs-up"  NORMAL mode....

I'm still hoping for more info on "signal loops";  from either GRJ or Barry.

Yes, your layout is much, much larger than mine so I guess that would open the door for many more problems. I will defer to the much more knowledgeable folks here.