Specifications

Engineering Standard –NSW
Signalling SMS 02
Cerberus Level Crossing Monitor Equipment
March 2005 Version 1.2 © Australian Rail Track Corporation Page 94 of 118
This document is uncontrolled when printed.
inputs against the circuits for the crossing and make the relevant
changes by adding or deleting inputs.
Edit the new ".exp" file for the crossing. On the first line of the file
change 000 to the level crossings ID number. ID numbers are in the
range of 001 to 199 for Western Region. 200 to 399 Southern
Region. 400 to 599 for Northern Region. 900 to 999 for Metropolitan.
Note that each Level Crossing in ARTC must have a separate ID
number. Change the rest of the first line to have the name of the
crossing, it kilometerage, and the date. Change the title of the file
from generic.exp to your chosen name name.exp. Also update the
date and comments section so that a record is kept of modifications
made to the file
Modify the TEST Switch expression to the relevant type.
If any input have used back contacts then change its name to the
form “NOT_NAME”. Check is the input is used in the expressions. If it
used the for each time it is used change the name form “NAME” to
“*NAME” and make an additional expression at the beginning of the
expression file of the form “*NAME = !NOT_NAME” which will
correct the inversion due to the back contact.
Find each expression line starting with ";;" or ";" and examine it and
the adjacent expressions to see which are applicable. Delete those
not applicable and remove the ";;" or ";" to bring the commented out
expressions into use.
If the Level Crossing has interlocked signals or other special
conditions like an adjacent ground frame then examine the
*NOT_STOP, *NOT_START, *STICK_WARN, *STICK_FAIL
expressions must be checked and either deleted or modified.
Additional expressions may be added to check for track failures,
detection failures, or additional alarm or warning conditions.
Examples of these are:
*TRACK_FAULT =T 1 h 0m 0s
!*TRACK_UP *DETECT_FAULT =T 30m
0s !6NK & !6RK
If the crossing is not being remotely tested then replace the
*NO_TEST expression with:
*NO_TEST =T 36h 0m 0s TEST_ZK.
Edit the new ".cfg" file for the crossing. Change the title of the file
from generic.cfg to your chosen name name.cfg. No other
modifications are to be done to this file.
A number of warnings are included in the generic configuration files
regarding deleting of variable and inputs such as Special
Intermediate variables. Please adhere to these warnings.