A driver command to operate railway crossings assembled around the core assets :
<kuid2:368725:20525:4> NSWGR railway crossing control, bi-directional tracks, double-track fixed road length, no fixed tracks
<kuid2:368725:20517:4> NSWGR railway crossing control, bi-directional track, single-track fixed road length, no fixed tracks
<kuid2:368725:20526:4> NSWGR railway crossing control, bi-directional tracks, multi-track fixed road length, no fixed tracks.
The stated railway crossing core assets are operated by default by directional trigger assets placed on the railway track approaches to the crossing.
However, trigger operation can be changed to driver command operation by editing the crossing core asset's properties (open the Properties editor in Surveyor).
Driver command operation is useful when a railway crossing is situated within a yard where trains shunt back and forth across a crossing or approach near to a crossing without passing over it until a large delay has occurred.
There are 2 options for closing the crossing by this driver command. The first option will allow the crossing to re-open automatically once the train has passed the crossing. The second option will hold the crossing closed until countermanded by another driver command to open the crossing.
To enable automatic re-opening of a crosssing, a track mark must be added immediately before an oncoming train enters the crossing in each direction of travel ('Down' and 'Up').
In the Down direction, the track mark must be named in the format '<locationID>_crossing mark_<index>_down'.
In the Up direction, the track mark must be named in the format '<locationID>_crossing mark_<index>_up'.
For example, for a crossing instance named 'HR_crossing control_1' (locationID = 'HR' and index = '1'), the Down track mark is named 'HR_crossing mark_1_down'.