I think there are two aspects you may wish to incorporate

1) some means to virtually track a locomotive as it moves around the blocks and yards
2) the concept of "inheritance/override" of a Loco

for tracking, you may have a preference , I make use of the CS3s virtual sensors and a number of IFs

Inheritance/override is where you have an Event that is initially set up (designed) using a dummy loco placeholder.
If you run the event directly, the subsequent tasks are actioned on that dummy loco
HOWEVER
If you call the event from a function of another loco, then the events target loco will inherit the ID of the calling loco.

Thus by tracking a loco around the layout, when it triggers the exit sensor when leaving a previous block, it will "prime" the block/brake event it is about to enter with its own ID.


The CS3 has a function where you can post a locos name against a sensor or signal
It you be nice if there was a way to "read" this ID and use it directly. At this point I have not worked out if that is possible, wuld love to here if someone has cracked this easter egg from Maerklin

Hi Jos
Here, a Digital operator using a CS3 and Rocrail from France. I started using the CS2 and then CS3 memory / events fonctions and now I use Rocrail since 10 years.
I think that to-date, the CS3 has no real tools to manage / update the location of each train in a way usable for medium to large layouts.
It seems that Märklin is working on this but the hurdles are the small screen and small processing power compared with those of a PC.
In softwares like Rocrail (RR) there are some mechanism to help:
- you indicate where each loco is located (only once at first use)
- RR is in charge to move trains (a) preparing the route - checking no interference with other validated routes (b) reserving the route and all related track pieces to avoid collisions, (c) start the train, (d) when the train arrives at the destination block, slow down the speed, update the trains position to the new arrival block, free the origin block and the route and track pieces so that they can be used by other trains
- because RR knows the location of each train, exactly like what you wish Jos, when the train is detected at the destination block, if it must stop or change speed, it will simply send digital commands to the locos without requiring any interruption of power in front of signals.

NOTE: When above I mention RR, it is just an example and surely other train control softwares do the same. So please don't get angry at me

There are many benefits to this approach (that could appear maybe on the CS3 or CS4 later):
- simplified wiring (no need to have insulated stop section ahead of a signal)
- the loco can be anywhere in the train (front or rear or in the middle) and still the train will stop at the right place without calling for special train wiring, slider inversion, etc
- the signals are NOT needed anymore except for cosmetic reasons (nice in shadow stations and other hidden zones
- RR can propose three modes of operation (aquarium mode), schedule mode, manual mode
- bi-directional block and lines are available without any complication whatsoever

And the present CS3?
- as mentionned above, there are tricks to follow a loco in a layout so that the CS3 remember which loco to stop or start. It can be using a real turnout position or a virtual one but this is good only for 2 or 3 locos not many more I think

Just my opinion
Cheers
Jean
PS: I have no financial interest with RR just saying that using your laptop and a CAT5 or CAT6 cable between it and the CS3 and you are in business. With RR you have full access to all possibilities and you pay (help the team) the amount you wish when you wish. So you may start now (costed me 5€ for the cable and thats it although it is fair to donate to RR if you are satisfied.
Here is a flavour of what you can do with it (full automatic operation, mixing the aquarium mode and the schedule mode

Hi Tie
.
This is not quite correct. You may see Rocrail and others as a shift register: sensors are conventional and have the only capability to detect that A TRAIN is there (not which one but because IT IS EXPECTING a specific train it is almost as if..) BUT:
- train control s/w (TCS like Rocrail) must be told ONCE which train is where (on which block) and then the TCS updates the ,location of each train.
This is why when a train arrives at its destination block, if the signal is red, the TCS knows to which loco it needs to send a stop command
- when the TCS sends a train to another block, then the TCS detects when the train arrives in the new block and updates the train position (making the previous block free for other trains
- on a TCS you must enter your whole layout (on one page or multiple pages). The TCS now is able to see what track pieces are used and in which position AND to reserve them (No other train can use those track pieces until the train has reached its destination.
- A ROUTER on the TCS, designs the routes and the position of each needed track piece.

I am far from having described a TCS but we can see that the CS3 with its present update is very far from having all these features
Cheers
Jean

If there is a turnout failure, then the train is diected to another track and most of the time a GHOST train (an other, non-expected sensor is triggered) is detected causing the power to switch-off to avoid collision.
Jean