Specifications

ManualsBrandsDataplex ManualsComputer equipmentDPX-213

RailCorp Engineering Manual — Signals — Equipment Manual

Cerberus Level Crossing Monitor Field Equipment Manual TMG E1261

Issued August 2012 UNCONTROLLED WHEN PRINTED Version 2.1

Lamp Offsets The lamp offset is used to compensate for variations in

the lamp currents at particular locations. On each lamp

circuit their are two values. One labelled FU (Flasher Up,

flasher contact 12 and 11 made), and one labelled FD

(Flasher Down, flasher contact 12 and 13 made). The

lamp learn offsets are limited to greater than -10.0 and

less than +10.0. Negative offsets are due to lamp

currents that are less than expected. Positive offsets are

due to lamp currents that are greater than expected. Both

FU and FD values should be within 2 counts for flashing

lamps. Only the FU value is used for steady lamps.

Offsets are normally set using Lamp learn but may be

manually adjusted.

6.2 Customising Generic expressions

A set of generic configuration data files have been created. These are called generic.cfg,

generic.io, and generic.exp. When the data files need to be defined for a new Level

Crossing these generic files are copied as file names having a unique identifier for the

particular level crossing. A batch file has been created for this purpose. It is invoked by

the DOS command line "NEWEXP name" or in “Cerberus’ with a menu selection. Please

note that the name chosen must be 8 characters or less without spaces.

e.g. typing in >newexp name

The specific configuration data files are then edited using any TEXT file editor or word

processor. If you are using a word processor such as Word 6.0 for Windows you need to

make sure that the edited file is saved as a ‘Text Only’ file.

Edit the new ".io" file for the crossing. Change the title of the file from generic.io to your

chosen name name.io. Also update the date and comments section so that a record is

kept of modifications made to the file. Either delete the line starting with ";;" if these inputs

or variables are not applicable to the particular crossing, or delete the ";;" to make them

applicable. They mostly relate to booms. Check the 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 RAC must have a separate ID number. Change the rest

of the first line to have the name of the crossing, it kilometreage, 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.