“Signal Strength” optimization vs Track blocks vs DCS/power feed ?

Daniel,

is there anybody suggesting that the optimal approach is to create a track block for each DCS/power feed, even if using only one TIU channel?

That is exactly what should be done for optimal DCS signal.

Would this really improve anything or create other issues?

Not doing so will, in the vast majority of instances, cause issues with DCS engine control.

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!

So there is no misunderstanding, no one is saying that a single different TIU channel should be used to feed each block.  If you want to run conventional, separately fed & toggle switched blocks is the key to multi-train operation.

I agree with the second sketch, except that I would not cut the track just to the left of the switch.  That would leave the switch unfed.   I sever the center track electrical connector under the switch, so it ends 3 blocks.

Thanks for the answers gentlemen.  Much appreciated.

For RJR:

No misunderstanding here; My question was not for conventional usage, but for "DCS Signal Strength" optimization even if only on TIU channel is used, as per the drawing.  Thanks.

For everyone, one additional question:

With that "isolation approach" and only one DCS/Power feed per block track, does the equal length of all wires from the terminal block to the each block track still really matter ? (i.e balanced star - homerun wiring)

Thanks,

Daniel

The so-called requirement for equal length of wire is an "urban legend."  Doesn't matter.

Finally, if we push that "isolation approach" to the simplest layout (i.e. a loop), the optimization would be as per the following drawings,  Right ?

 As per DCS Operator's Manual - fifth edition - p.11

Would be optimized with the following center rail isolation (red line):

Thanks,

Daniel

Yes

Gentlemen,

    In reality only one Block with one drop using one TIU channel is needed to run these small DCS layouts that are pictured, because with 12-13 track joins the DCS signal should be around 10 even with a switch on the layout, especially if you put a magic light at the head of your single small terminal block, if you even need it.  With bigger DCS multi level layouts and more switches, the engineering design for setting up the DCS changes, using terminal blocks and magic lights in different locations thru out your DCS layout.  Keep the 12 track join rule in mind when designing DCS blocks, and build using that discipline, if you want max signal strength thru out your DCS layouts.

Remember to test your DCS signal strength as you build your layouts.

PCRR/Dave

All, an FYI...

If all you have is a simple loop with no more than 12 track joins, one drop is probably just fine. However, I'd cut and insulate the center raIl in one place so as to have an actual block, rather than a loop. Even better would be to have two center rail cuts making two blocks, which would allow two drops rather than one.

The reason to avoid a loop is the same logical reason to make blocks in the first place, i.e., this severely limits the possibility of a DCS engine getting the same command twice.

To add to the others providing very good advice here, I can tell you from personal experience that the 2nd loop plan you show here will work MUCH better than the first. It makes quite a difference. I have tried both on a few different occasions with temporary layouts.