Its only my humble opinion, but I would steer clear of the CS3 Brake Macro until it is fleshed out a bit more.

Page 7/8 of the Online help section on Event Macros offer some insight ...


But to answer your question,
yes -macros including, the Brake Macro are, "called" from another event.

The best I can describe this is that it is like a station master setting/authorising a train into a block,
where the end of the block is indicated by the signal and the brake and stop sensors are
suitably placed in advance of the signal.

And while the Brake Macro may be loaded(preped) with a Loco , this is a placeholder,
and if your calling event has a Loco in it , or the event is triggered by a Locomotive function key,
then then the Macro will inherit that Loco reference.

There are 3 sensors that may be configured

PROVIDED the signal in the "Semaphore Container" is RED (OR the Pause - Flag is on) ...
- sensor 1 [S88 BRAKE] (optional) = change to CREEP/HALF speed (actually the speed you set in the V-Min container)
- sensor 2 [S88 Stop] the most essential = stop (Go to speed 2, the locos inertial will still apply)
- sensor 3 [OverLap] (optional) = emergency stop
If the signal is GREEN and the pause button is OFF, then the sensors are ignored with no breaking/resuming

At sensor 1 the CS3 will memorize the speed the loco is running at, and then proceed to set the speed to CREEP/HALF

When the Semaphore Signal is set to GREEN (and the pause button is not being used) the CS3 will issue
a command to restore the loco to the speed it stored earlier.

The emergency container is optional and allows you to link to a function (or another event)
should the emergency sensor be triggered when the signal is RED.
This might be a simple "Set CS3 toStop" command, or a command to play a Klaxon sound clip through the speaker)