Originally Posted by: Mark5 
Thank you so much for that Johnjean.
"- no need for insulated stop sections, Rocrail sends the proper stop command to the loco...(etc...)"
So that is exciting. So much to figure out all at the same time, its about spending time, studying without cracking my head.
Sometimes wish there was more of a step-by-step guide. I am willing to dedicate time to it, I just want to do a small test layout with a siding or two, some signals, reed or circuit switches; that way I can learn as I walk myself through using the CS3 with Rocrail in tandem.
There is a step by step instruction guide here
https://wiki.rocrail.net/doku.php?id=stepbystep-enThere are tutorials on youtube like this one
https://www.youtube.com/watch?v=tf_V-Ghm0YEThere is an English Rocrail forum wherefrom you can get help here (but you need to register first
https://forum.rocrail.net/viewforum.php?f=95Originally Posted by: Mark5 
Having Rocrail know where the trains are at any given time will be essential for my extensive shadow yard. Most curious to understand how RocRail knows the actual train number and not just any random train triggering the reeds?
One key article in Rocrail is a block, usually, a track section before a signal, with one, two or more sensors. The block can be free (no train), reserved (expecting a specific train), occupied (the specified train has arrived as reported by sensors associated with the block.
The train comes from another block (origin block) and a route when activated, allows to go from origin_block to destination_block
So basically, you tell ONCE, where (in which block) each train is and Rocrail manages the transfers from an origin block to a destination block thanks to sensors.
Knowing in real time, which loco (train) is where, it is capable of sending digital order to the appropriate loco to accelerate, slow down, stop WITHOUT any external device (signal with an isolated section, slow-down modules, etc. Signals are ONLY FOR DECORATION.
Reed contacts work with Rocrail but are not the preferred approch. The best IMO, is to have occupancy sections in Blocks (20 cm before the signal is called IN and the rest of the block is called ENTER. In this way, if a consist remains in the block, there will be no collision as the block will not be accessible to other trains as long as the occupancy remains.
Another advantage of this is (1) you don't bother to install magnets on one or other vehicle (which one?) and (2) ANY train can become a shuttle train (loco is behind) without ANY hardware change or addition. Each axle is detected (Märklin 3 rails system).
Typical Rocrail speed controls (most used ones):
- V_max maximum speed for the loco type
- V_cruise normal speed between station
- V_mid station speed when approaching a red signal
- V_min minimum speed for precise positionning of for staging blocks (stockpile trains behind each other on a single track in relation with each train's length
Originally Posted by: Mark5 
And I have the necessary equipment it appears:
Link s88, reed switches, circuit switches, CS3, m83 (and kit), k83, etc and yes the book 03093.
One of the reasons to build a test layout is to keep me from buying more than I need and to get rid of excess from acquired lots. This way I can narrow down to as many specifics as I can before and during the track planning process.
Thanks again for all the immensely valuable suggestions, comments and feedback.
Mark
One key to success is to start with a small, simple, modifyable layout in conjunction with a Rocrail demo layout.
I started Rocrail in late 2013 and in 2014 it was like this
Test intensively before landscaping
And in 2019 may layout was like this
If I can do it you can too even without the book BUT with patience, with the forum and an open mind.
Start small, step by step,
never leave one step until it works fine, then archive the 5 Rocrail files on your PC and only then make changes
Sorry as you may see I am a big fan of rocrail (although a simple user)
Cheers
Jean