MCB – OD Basic Description, Equipment, Layout, Operation, Maintenance, Circuit Flowchart and Signallers Guide This document is not endorsed by Network Rail. It is NOT for installation, commissioning, testing, faulting or maintenance purposes, it is for information only. Network Rail’s own documents must be followed at all times. REMEMBER this is uncontrolled and therefore any measurements or procedures stated may have changed to a newer standard. ALWAYS consult NR documents before any work takes place.

©Copyright F. M. Spowart

Page One of Nineteen

v1.8 July 2016

MCB – OD Page Two of Nineteen

Basic Description of MCB – OD system: The MCB OD system was introduced for two main reasons. Conventional MCB’s using CCTV requires the signaller to confirm that the crossing is clear. There have been a few instances where the signaller has ‘confirmed’ that the crossing was clear, when in fact it was not, resulting in near misses and a collision. This is primarily down to lack of concentration when trying to control other crossings and trains at the same time. The other reason is due to many signalboxes being closed and transferred to ROC’s (Rail Operating Centre’s), and with these closures, many CCTV controlled crossings would become too much for a single ROC to handle, so crossings would need to be automated. As half barriers are subject to abuse by road users, full barriers are now preferred. This is where the MCB – OD (Obstacle Detectors) are now the ‘eyes’ on the crossing. Used elsewhere in Europe, they have been a success. However, other countries only use a primary RADAR to detect vehicles. Pedestrians are not accounted for except in the UK where it is a legal requirement. Therefore, as well as a primary RADAR called a POD (primary obstacle detector) to detect vehicles, we have a high-level complimentary LIDAR called a HL COD (complimentary obstacle detector) to detect adult pedestrians. As well as the high-level (HL)COD, some crossings, subject to a 9-day census, may have a low-level (LL)COD where the crossing is used by children frequently. All UK crossings as a minimum have a POD and a HL COD. ALL the RADAR’s and LIDAR’s MUST confirm that the crossing is clear before signals will be allowed to clear. The POD has two multiprocessors that must be in agreement before it allows a crossing clear confirmation; this is classed as a ‘SIL3’ interlocking (similar to an SSI interlocking). The POD uses reference reflectors (RR) (triangular mirrors) to determine the area under surveillance as it scans a 140 degree area. If the POD cannot not see all the RR’s, it will never give a crossing clear. The actual (target) area of the crossing is set-up using the on-site PC using reference markers and angles inputted into the system. All RADAR’s and LIDAR’s (PODS & CODS) are set-up using a very lengthy process that could take up to three days to complete per crossing. Level one staff are trained to maintain and fault the equipment and make minor adjustments to the reference reflectors. Only level two staff are trained to adjust and set-up the equipment. Therefore Under NO circumstances should level one staff alter any other settings other than what they are trained to do, or the RADAR’s could be damaged/moved and give a false crossing clear. The POD cover shouldn’t have to be removed by level one staff. Serious damage could occur to the moving RADAR inside and render is out of action. The POD’s alone cost in the region of £60,000. The LIDAR screens are now protected by automatic electric shutters that keep them clean during idle mode. Note: during auto OD operation, all personnel, MUST be outside of the detection zone (the crossing deck, and outside of the barriers), and behind all COD’s and reference reflectors or a false obstacle WILL be detected and stop signals from clearing and fail the crossing.

MCB – OD Page Three of Nineteen

On-site crossing clear (CC) and LCU controls (for maintenance, faulting or failure): LCU: Two control pedestals are provided at the crossing. One is a normal LCU unit which provides control of the crossing during complete failure, maintenance or engineering work. CCU: The other pedestal contains the CCU (crossing clear unit) controls. If the OD’s fail and crossing clear cannot be confirmed by the RADAR and LIDAR’s, then a level crossing attendant (LXA) will be called. Inside the unit is a three position switch, (left for all signals on, middle for normal (auto) and right for CCU mode). In CCU mode and once all the barriers are detected down, two buttons will flash. The LXA will then confirm CC by sight and then push BOTH buttons to confirm this. Signals will then be able to clear. All signals on is used if an incident then happens after CC is confirmed.

Note: earlier CCU’s were called ‘XCU’s, but should now all be changed.

Basic operation: The actual crossing circuits in the MCB – OD are very similar to that of a conventional MCB, but many new relays have been added to do with the OD part. The crossing sequence is started by a train striking-in and the ‘minimum road open time’ applies. Roughly at the same time, the POD and COD’s (named as detectors from this point) activate and self-test (6-7 seconds) and the COD shutters lower (2 seconds). After the ambers and red road lights, the entrance* barriers come down and the detectors scan the crossing. After scanning and confirming crossing is clear (CC), the exit barriers fall after the 10 second anti-trapping* feature (the time given to allow any vehicles or pedestrians to escape if they happen to be trapped by the entrance barriers). *On two barrier operation, this is not applicable.

Once the exit barriers have lowered, the detectors scan the crossing. The POD scans three times to

confirm. The COD’s also confirm crossing clear. Once all detectors are in agreement they are given a

STOP command and their outputs are frozen (just as the picture goes blank with CCTV crossings) and

the signal will clear.

Note: Between the DN KR(2) picking and the last clear scan, (OD)(SCAN) JPSR (4 second timer) will

pick and then pick the (CC)SR and only then confirm that the crossing is clear.

The shutters on the COD’s come up after CC confirmation. If however, the exit barriers come down (or all if two barrier operation) and then an obstacle is detected within four seconds, they will raise themselves. The RADAR detectors will continue to scan the crossing. The failure to give crossing clear is registered with interlocking (ABM(2) relay) and a second attempt will commence (ABM(3) relay). If a second attempt has proved unsuccessful, again registered by the interlocking (ABM(4) relay), the exit barriers will raise and no longer be in automatic mode and will effectively ‘fail’ in the air, although this is not technically a failure and an object has been seen by the detectors and have therefore done their job. If this happens, intervention will be required by the signaller (he will be given indications saying that an obstacle has been detected). He will be required to lower the barriers by button then after having red roads confirmed lit, all barriers intact (BOOM CR) and down indication, they will caution the train passed the red signal. Note: Under ABSOLUTELY NO CIRCUMSTANCES will the BOOM CR be strapped out at any time. If the BOOM CR fails and cannot be repaired – an attendant must be called and be on site BEFORE you leave. He must stay in place working in CCU mode until the BOOM CR is in full working order.

MCB – OD Page Four of Nineteen

Once the train has passed, the barriers will be required to be raised by the signaller and then the crossing will reset. It will then require the S&T to go out and determine the cause of the detection whether false or not. Critical failures of the RADAR POD will result in the (OD F2) SR relay dropping and failing the crossing. If this happens, the POD will require powering down, waiting for one minute, powering back up, waiting one minute and then the OD RESET button pressing to reset the (OD)(CYC)SR. It will then take approx 30-40 seconds to respond to commands. For Modular Signalling reset procedure see page 11.

Barrier Protection Management (BPM):

On some crossings where they are close to road junctions where there may be a risk to ‘blocking back’, a system called BPM (barrier protection management) is used. This is where one or more of the barriers may fall onto a queuing vehicle and therefore rip it off. To overcome this, sensing wires are cut into the road surface under where the barrier will fall and if triggered will stop the barrier from lowering AND it’s opposite one too. BPM indications are provided to the signaller should it be triggered. Once the vehicle(s) moves clear, the barriers will lower as normal.

DVR, Recording Equipment and ‘Dropbox’: All OD crossings are equipped with HD video monitoring equipment including red light cameras and ANPR cameras and a ‘SA380’ datalogger. Both are recorded 24hrs a day onto a DVR. The DVR also records Redscan (LIDAR COD files) and RWMON (RADAR POD files). Not only do these provide evidence of possible mis-use and incidents, they are also used to aid in fault finding, for example a false or real obstacle detection that stopped a crossing clear being given. A storage system called Dropbox is used at all crossings that enable video footage, datalogger files, Redscan and RWMON to be downloaded to it and then any person logged in Dropbox will be able to view them to either prove a failure or for another technician nationwide to read the files and determine a cause. Files must be downloaded on site to Dropbox to enable remote viewing. Videos from the DVR can only be viewed from a PC (see below). All other files can be viewed via a PC or an i-Device, such as an iPad or iPhone, (app downloaded from the Apple App Store). Dropbox also contains site specific information, OD manuals and the signallers fault finding (FF) guide. On no account should any files be deleted from Dropbox unless it was you who originally posted it and it is no longer required. DVR files are deleted after 48 hrs so it’s imperative that any evidence is gathered immediately and stored on to Dropbox should any allegation be made. For security reasons, Dropbox log-in details and email addresses are not listed on here – see your line manager for these. To view video files on a PC, the h.264 file has to be converted to play. To do this, download a free copy of “VLC media player” (search Google for it). When installed, go to the h.264 file, right click it and choose “Open with… “ and then choose VLC media player and it will start playing. Once this is done, it will remember what you chose to open it and will open by just double clicking on the file if it needs to be viewed again.

MCB – OD Page Five of Nineteen

Basic crossing equipment layout and brief description: Note: this must be viewed in colour to appreciate diagram below

Equipment/key Brief Description

RADAR primary obstacle detector (called the ‘POD’). Rotating dish inside that scans the crossing at 140 degrees known as the

surveillance area. Its primary function is to detect vehicles on the crossing. The actual area detected is set by the reference reflectors (see below).

LIDAR complimentary obstacle detector (called the ‘COD’). Primary function is to detect objects that the POD cannot detect, such as people. Comprises of

either one high level (HL) LIDAR at all times (two minimum per xing). A low level (LL) LIDAR (two minimum per xing)is fitted when the crossing is frequently used

by pedestrians. Can have up to 6 CODS (12 in total; 6x HL & 6x LL Lidars).

The reference reflectors (or known as corner reflectors). They do not however define the corners. They are fixed into position and are used as a reference to where the POD scans to determine the detection area. Anything outside this

area is disregarded.

Scanned area of the HL LIDAR of COD A. This is to within 25mm of the nearest barrier. It overlaps the scanned area by COD B and covers the whole area within

the crossing and 25mm short of the nearest barrier.

Scanned area of the HL LIDAR of COD B. This is to within 25mm of the nearest barrier. It overlaps the scanned area by COD A and covers the whole area within

the crossing and 25mm short of the nearest barrier.

140 degree Scan area of the POD

‘COD B’

‘COD A’

˃1.5m ˃4m

˃2.5m

2 to 3m

B A

REB

MCB – OD Page Six of Nineteen

Scanned area of LL LIDAR of COD B. The scanned area covers the deck of the crossing, usually to the edge of the BOMACS; (660 – 780mm from the running

edge of the rail)

Scanned area of LL LIDAR of COD A. The scanned area covers the deck of the crossing, usually to the edge of the BOMACS; (660 – 780mm from the running

edge of the rail)

The Radial Non-Detection Zone. This is a 2 – 5m zone to ensure reliability during falling snow or heavy rain etc. Even though the nearest COD has its own non-

detect zone, the furthest one will detect any objects.

CCU: Crossing Clear Unit. This is equipped with a three position switch for SIGNALS ON/NORMAL/CROSSING CLEAR.

‘Signals on’ puts all signals to red. Crossing clear enables a LXA to override the OD’s and observe crossing clear and depress two buttons below to confirm. This

is for either OD failure or whilst crossing testing/observation of software.

LCU: Local Control Unit. For use to operate the crossing fully when it has either failed completely or when engineering works on or near crossing. Note that this

has a two minute timer that will render it non-controllable after first being opened, only if the RAISE button is required.

The detection zones. As seen on the PC in the REDSCAN program. These zones

are labeled B2, B1, A1 and A2.

The buffer zone. This is the area that must be free from fixed objects, such as

pedestals, lighting columns, fences etc.

The crossing deck known as the target or surveillance area. 1 metre from the

barriers or any trackside furniture such as lighting columns etc.

Brief description of levels and measurements:

The RADAR (POD):

A

B

RADAR BEAM:

Min: 2m max: 60m

Deck

140x1 degree tranches

C3

C2

C1

Follows crossing 1m from barrier & crossing furniture

Radar Heights: C1: 50min (+22)cm C2: 50 (+5/-2)cm C3: 50min (+28)cm

MCB – OD Page Seven of Nineteen

The Reference Reflectors:

The LIDAR’s (HL & LL COD):

See the SMS’s for all current installation and maintenance measurements as these may change in the future.

Note: LL heights should be as close as possible to maximum height levels as stated.

Max: 90 degree angle

Less than 60m away

Middle of bracket to base starting height: 880mm (final height determined on set-up)

(top of base): 20mm below the nearest rail head. (SPT base used)

Max 20.4m range from centre of post

2 to 5m non-detect zone

(LL) Height of laser from deck: LL LIDAR (children frequently use crossing):

100 to 175mm LL LIDAR: (adult frequently use crossing):

130 to 280mm Absolute minimum is 100mm.

Distance from COD to anti-trespass guards: 460mm

(HL) Height of laser from deck: Min top of beam height: 390mm

Max bottom of beam height: 610mm

Deck

MCB – OD Page Eight of Nineteen

The operating system:

The MKII DVR and the PC are housed in an REB next to the crossing. Several passwords are required to enter the DVR (MKI only), RADAR and LIDAR programs for taking readings or making observations only. Settings must not be altered by staff without the set-up (Level 2) competence.

Passwords:

The Mark I DVR ONLY (all these should have been upgraded to Mark II):

Username: 1

Password: 1

To access the RADAR program called ‘RWMON’ on the PC:

Username: None (not applicable)

Password: H*******L (all uppercase)

To access the LIDAR program called ‘REDSCAN’ on the PC:

Username: R*****N (all uppercase)

Password: O***X (all uppercase)

The RADAR & LIDAR program passwords are not all shown for security reasons.

To access the RADAR (POD) program (RWMON) for maintenance purposes:

Important: you must ask signaller for permission and put crossing onto CCU mode in pedestal before entering software programs or crossing will show failed.

To open program: 1. Open ‘RWMON’ from desktop, and click OK. 2. Question asked ‘reconfig required’. 3. Select ‘Nein’ (no). 4. Select ‘Program’. 5. Choose ‘Password’. 6. Enter Password (see page above). 7. Select ‘OK’. 8. Choose ‘Configuration’. 9. Select ‘Create/change GFR’. 10. Choose the “active GFR file”. 11. ‘CRC checksum’ appears, ‘OK’ it. 12. ‘OK’ the next menu (Note; this contains info for the record card). 13. Choose ‘Configuration’ 14. Select ‘Test Mode Target Display’.

Test mode target display appears. To remove the blue crosses to give a clear edge of the surveillance area, choose ‘Options’ and then select ‘Corner Points’.

To Close the RWMON program: Important: you must follow these instructions, or the crossing will not return to auto mode.

1. Select ‘Configuration’ 2. Choose ‘Test Mode End’ 3. Select ‘Program’. 4. Choose ‘End’. 5. Confirm by selecting yes. 6. If you are in CCU mode, put switch back to normal and close the door. 7. Confirm with signaller that crossing is showing auto.

MCB – OD Page Nine of Nineteen

To access the LIDAR (COD) program (Redscan) for maintenance purposes:

To open the Redscan program: 1. Select ‘Redscan’ from desktop. 2. When open, in small window on the left, select the LIDAR (COD) you wish to view. 3. Select ‘Connect Detector’ in the top left. 4. Once active, tick box called ‘Vertical’ to give a true view from the COD.

The scanned area will give information on how it is set up. Objects in detection area will show up as a white circle with a RED outline, these will ‘occupy’ the OD. Objects outside the detection area that will not occupy the OD will show up as white circles with BLUE outlines.

To close the Redscan program: 1. Select ‘Disconnect Detector’. 2. Close the program. 3. Confirm by selecting ‘Ja’ (yes). 4. If you are in CCU mode, put switch back to normal and close the door. 5. Confirm with signaller that crossing is showing auto.

Using Dropbox to store POD error files:

1. Open RWMON program (see page five). 2. Select ‘Configuration’. 3. Select ‘Protocol Data’ at bottom. 4. Click Document button in middle (C:\Documents and Settings….). 5. Select ‘My Documents’. 6. Select ‘Dropbox’. 7. Choose crossing name if applicable. 8. Select ‘Support Files’. 9. Choose RADAR you want to view; POD or COD. 10. Enter a date and time in this format: YYYY.MM.DD_TTTT (For example: 20150518_0935). 11. Open 12. Select at top ‘Protocol’ or ‘Error’ memory to view. 13. Select ‘Start’. Note: if Protocol is selected, it will count the memory blocks (wait). 14. ‘CRC checksum’ appears, click OK. 15. View files. 16. Choose ‘End’. 17. Close window in normal way. 18. Use Windows START button > My Documents > Dropbox to check files have stored.

Notes: Reset memory button on step 12 erases last error memory. In window in step 15, “TAR” means the number of pixels the RADAR cannot see, so the higher the number the bigger the object. “CNR” means the number of reference reflectors seen by the POD.

Capturing Redscan screenshots of the LIDAR’s and saving to Dropbox:

1. Open REDSCAN program (see above). 2. Choose LIDAR from window on left. 3. Select ‘Window Capture’. 4. Select ‘Save’. 5. Select ‘Dropbox’ file in My Documents. 6. Name the file in this format: YYYY.MM.DD_TTTT (and the crossing name). 7. Check in the ‘Dropbox’ folder in My Documents that screenshot has saved. 8. Close Redscan program (see above).

MCB – OD Page Ten of Nineteen

CCTV Access:

1. Open Sitepoint program (no username or password required*). See below if blank screen appears. 2. To review a video file, click on Review button at top left. 3. The playback window opens. 4. Click on the Calendar and select the date and time of the footage to review. 5. Press Play. 6. To alter the playback speed, select a different speed by clicking on fast forward double

arrows. See a more comprehensive playback guide below.

*Known problem with Sitepoint Program (not remembering preset password and shows a blank white screen):

If this occurs, follow these steps:

1. Open Sitepoint program (blank white screen). 2. Press ‘ESCAPE’. 3. Click on ‘CONNECT’ at top right of screen. 4. On connection window, drop down ‘site’ and choose ‘this machine’. 5. Click ‘connect’ if password filled in. If password box empty, enter ‘olympus346’ and press

connect. 6. Go to step 2 as above on ‘CCTV access section’.

Comprehensive Playback Guide:

There are up to 16 pictures on the Sitepoint program, many of which are duplicated. To make it easier to view back, as numerous duplicated pictures can confuse diagnosis, follow steps below.

1. Make sure you are on ‘live’ view. 2. Choose ‘layout’. 3. Select 4x4 view. 4. You should now see all 16 pictures. If not, and only some are showing, delete them by

closing each individual camera window. 5. Click on ‘cameras’. 6. A window appears with icon and number of each camera; use the mouse arrow to drag each

camera in order up to 16 into each window. Ignore PTZ icon. 7. Now choose and make a note of the cameras you are interested in, such as both barriers,

and both set of lights, (usually four pictures in total). Once this is noted, you shouldn’t have to do steps 1 to 7 again. It will be a good idea to note these down locally for others.

8. Click on ‘live’. 9. Choose ‘layout’. 10. Choose ‘quad’. 11. Click on ‘cameras’. 12. Again using mouse arrow, drag the same camera numbers you made a note of. 13. Now choose ‘review’. 14. Click on the Calendar and select the date and time of the footage to review. 15. Press Play. 16. To alter the playback speed, select a different speed by clicking on fast forward double

arrows. Be aware that some pictures may lag, which may appear as one barrier raising/lowering before the other which will hinder diagnosis. Keep an eye on the playback time in each window to check they playback at the same rate. If not, delete suspect camera and choose the other duplicated view.

MCB – OD Page Eleven of Nineteen

Using Modular signalling system to search for faults and errors:

This is particularly very handy to search for historic faults and filter the equipment right down to a specific item and ignore the rest, such as a boom CR showing failed, as the main fault screen will probably show an extensive view of all faults and errors from several weeks previous. 1. Open modular signalling menu (see below). 2. Choose ‘reports’ at the top. 3. Choose ‘alarm reports’. 4. Change date and time to and from for your search. 5. Click on radio button for ‘filter by alarm type’. 6. Check each box for all alarm types you require to check for alarms. 7. Click on ‘show reports’.

Each fault/error will now be displayed if there is any and how many times they have occurred.

MCB - OD and Modular Signalling:

The system is split between the OD system files and the Modular files. To select one or the other, press the button on small white splitting box below the keyboard. Two lights signifying system one or two is displayed. To switch back press the button again.

The Modular Signalling OD Reset Procedure:

The reset button used to reset the POD when the system is controlled by modular signalling does not exist and it is reset by logging into the modular signalling system. To reset the OD, follow this guide:

1. LOWER BARRIERS 2. Close and lock LCU/CCU. 3. Log-on to technician’s facility by selecting ‘Access’ from top left window. 4. Type in user name: M********r (not fully shown for security reasons). 5. Select ‘maintainer’ role from drop down menu. 6. Enter the password: M*******r1 (not fully shown for security reasons). 7. Select ‘AOC’ from top of window. 8. Select ‘Take Control’ from drop down menu and ‘Area Control Selection’ will appear. 9. Select interlocking “tech’s controls” and select ‘take control’. (Once selected, writing will

go grey). If someone is logged in remotely, they must release their control first. 10. Close that window. 11. Select ‘Apply or Remove Control’ and a ‘Request Technician Control’ window appears. 12. Click on roundel next to ‘Level Crossing’. 13. Within the ‘Select Object’ column select the level crossing from drop down menu. 14. Under the ‘Select Technician Control’ column choose ‘Apply: Reset Level Crossing’. 15. Enter a valid reason for resetting the OD in the ‘Reason for Control Application’. 16. Click ‘Issue’. 17. A ‘Control Request Confirmation’ window will appear. Enter LC ID as it appears in step

13 and click OK within 30 seconds (or it sends you back). 18. The next window will show “request successful”. Click OK. 19. When finished remember to release control by selecting option under ‘AOC’. 20. Log off by selecting ‘Access log off’. 21. Ask signaller to raise barriers (they will have no indications at this point). 22. Lower again, then raise, then select AUTO on signallers panel and indication should be

restored. For more information, see manual M1512/TF MN00098 Page 100.

MCB – OD Page Twelve of Nineteen

Handing back barriers after being on local control:

1. Ensure barriers are down first (via LCU) if not already. 2. Turn the LCU switch to NORMAL and close and lock the door and remove the key. 3. The signaller must then place their switch to LOWER to bring into correspondence. 4. The signaller can then raise the barriers and then set the switch to AUTO.

Note: there are no specific instructions for coming out of CCU mode, but it is recommended that the barriers are in the raised position before doing so.

Maintenance Procedures – helpful information: Important: these notes do not cover all of the maintenance requirements – always follow the current tests as stated in the SMS’s.

SMS OD01: Radar Maintenance:

As part of this SMS you have to do a test walk to see if it is still in spec from the initial installation. To do this you have to open the RWMON program to view the surveillance area.

1. On the PC, open RWMON 2. On the startup window, click OK 3. It asks ‘Reconfigure required?’ choose ‘Nein’ 4. Select ‘Program’ 5. Select ‘Password’ 6. Enter password H*******L (not disclosed for security reasons) 7. Select ‘Configuration’ 8. Select ‘Read Out Configuration Parameters’ 9. Choose Channel A or B 10. Select ‘OK’ 11. Select ‘Configuration’ 12. Select ‘Test Mode Target’(surveillance area is then displayed)

It is a good idea to mark out the walk test area in chalk before asking an assistant to walk it. Have the assistant walk (feet together and in a slow shuffling motion) the test area as stated in the OD manual/SMS in a counter-clockwise direction slowly. If your assistant ‘disappears’ within the surveillance area, ask them to go back and re-check slower. Carry out any other SMS checks. If an object is seen on the surveillance area before initial test: Point the mouse arrow over the object and obtain the ‘angle’ of the object. This is displayed as the ‘Alpha: ….’ number (for example ‘34’) at the bottom amongst the coordinates. After obtaining the reading, open ‘Test Mode Power Density Spectrum’, this opens a graph. Enter the alpha number in the small window. This will then show the object as a yellow peak in between two purple markers (which is the surveillance area). However, the number you enter may not be the actual true angle of the object. The current threshold value is 0.22v, so if you go back and enter for example ‘33’ and bring it up on the graph, the threshold reading at the bottom may be higher or lower. If it is lower than 34, it is not the true angle. Go back and try ‘35’. Again if this is has a lower threshold than 34, then 34 is the true angle. Follow current guidelines on what to do if a false object is seen after you have confirmed it is indeed not an actual object in the surveillance area. REMEMBER: level one maintenance staff MUST NOT adjust any settings or equipment that will alter the surveillance area.

MCB – OD Page Thirteen of Nineteen

To end RWMON: Important: you must end RWMON program, or the crossing will not return to auto mode.

1. Select ‘Configuration’ 2. Choose ‘Test Mode End’ 3. Select ‘Program’. 4. Choose ‘End’. 5. Confirm by selecting yes.

OD02 SMS: Lidar Maintenance:

Note: clean the LIDAR’s and remove any false objects, such as weeds, debris etc before any tests are carried out. Before carrying out a walk test, check the beam heights using the ‘LAC’ (the orange triangular device with beam sensor tool). There is no point carrying out a walk test if any of these beams are not to spec, as this must be rectified first. REMEMBER: level one maintenance staff MUST NOT adjust any settings or equipment that will alter the detection area. Note: Level one or two is NOT the same as the SFI levels. As part of this SMS you have to do an internal and external test walk to see if it is still in spec from the initial installation. Internal walk test:

Open the Redscan program (see page nine on how to do this). Once in Redscan and connected to the correct LIDAR, alter the horizontal orientation only if the crossing requires it, for example, you need to view the crossing as you were viewing from above. If you do alter the view, you must then adjust the COD name to warn future testers that it has been altered. To do this, open properties window, click on the name of the COD, and enter ‘HORZ’ to the end of the name only. Lower the barriers. Have an assistant do an internal test first. Start by walking slowly from one of the barrier pedestals with both feet together, arms down the side with one arm brushing along the barrier. Watch the correct COD display for your assistant walking. If they disappear, go back and re-check slower. Follow along the barriers, then the edge of the road, and the edge of the bomacs, have your assistant every few metres walk out of the detection area and check they disappear and come back when returned to the detection area. You must also check that the other COD sees your assistant by periodically switching over to it on the PC. Complete the entire outer detection area until you reach the starting point. Carry out the same test on the other COD. And any other HL or LL COD’s. External Walk Test:

Using the Redscan program set onto the correct COD, have your assistant starting at a pedestal, walk along the barrier and check that they are not detected. Every one metre have them push the skirt into the road and check it is also not detected, this is to ensure that high wind pushing the skirt will not give a false detection. Carry out the same test on the other barrier on all COD’s.

MCB – OD Page Fourteen of Nineteen

The COD (LIDAR) non-detect zone:

This zone is to ensure that rain or falling snow is not detected close to the COD, but a person is detected for the entire area if they walk towards a COD. This is tested as follows: Have your assistant walk behind the COD under test and make sure they are not seen on Redscan. Ask them to walk out from behind the COD and they should seen but not detected (white dot with blue outer circle) until they reach the outside of the zone (the half circle line on the program) where they will then been seen as a white dot with outer red circle (detected). Ask them to walk to the other COD (change over the COD on Redscan) and they will be detected for the entire area even inside the “non-detect” zone. Ask them to walk behind that COD and carry out the same test, ensuring that they will be detected (blue circle icon) in the ‘non-detect’ zone on the starting COD within the circle, and then be detected (red circle icon) when leaving the circle. Remember to swop over the COD on Redscan for the return walk. See the diagram below for clarity. Carry out the same test for all COD’s.

Note: the coloured blue or red circles must be seen throughout the walk. Complete ALL SMS tests and close any programs afterwards (see above on how to do this).

“Non-detect” zone Blue: detected, but will not

be seen as an object (clear)

Red: detected; object seen

(occupied)

Walk start point

Switch over to the other

COD around here

Black lines: area not

detected

Walk finish point

“Non-detect” zone

Switch back over to the

other COD around here

MCB – OD Page Fifteen of Nineteen

Circuit Flowchart:

Train occupies strike-in TC on approach

TPR drops

TAR picks

(A LOW) JR picks (MROT) picks

20 SECOND TIMER STARTS FOR (A LOW) JR &

AFTER 20 SECS...

10 SECOND TIMER FOR (MROT) STARTS &

AFTER 10 SECS...

LOWER SR drops

CON SR drops

(ABM)SR (1) drops

(OD) (START) SR picks

(OD)ZR drops

HER drops

AMBER ROAD LIGHTS LIT

HJR drops AFTER 3 SECONDS...

HJPR drops

RED ROAD LIGHTS FLASH

YODALS START SOUNDING

AFTER 5 SECONDS...

(CON)JR drops

(CON)JPR drops

(OD) (RUN) picks

LOWER R(1) drops

ENTRANCE BARRIERS LOWER

DN KR(1) PICKS

B

RECR picks

RECPR picks (if no lamps failed)

(LL COD A) (FRE A) R picks

(LL COD A) (FRE B) R picks

(LL COD B) (FRE A) R picks

(LL COD B) (FRE B) R picks

(POD) (ACT B) R drops

(POD) (ACT A) R picks (UP) KR drops

(A LOW) JR drops

(MROT) drops

(POD) (ACT A)SR picks

(POD) (ACT B)ZR picks

A

This is the minimum time

between trains striking in on

opposite lines to ensure

vehicles and pedestrians have

time to exit

1st attempt at closure recorded

Crossing is set to AUTO with correct indications for the OD’s to work

MCB – OD Page Sixteen of Nineteen

B

(LOWER) (2) CR drops

(LOWER) (2) JR STARTS TIMING

AFTER 10 SECONDS...

(LOWER) (2) JR drops (LOWER) R (2) drops

EXIT BARRIERS LOWER

A

(POD) (FRE B)R drops

(POD) (FRE A)R picks

(POD) (FRE A) SR picks

(POD) (FRE B) ZR drops

(OD) (CLR) R picks (DN) KR (2) picks

(DN)SR picks (BARRIERS PROVED DOWN & LOCKED)

(OD) JR picks

AFTER 4 SECONDS...

(OD)(SCAN) JPSR picks

(CC) SR picks (xing confirmed as clear)

XZGR picks

ALL CONDITIONS MET: signal clears

(OD)STOP SR picks

(OD) START JR STARTS TIMING

AFTER 3 SECONDS...

(OD) START SR drops

(OD) (CLR) R drops

YODALS STOP SOUNDING

(OD) (STOP) SR STARTS TIMING

AFTER 3 SECONDS...

(OD) (STOP) SR drops

(OD) ZR picks (OD’s Idle mode) A

(OD) RUN JR drops

NO OBSTICLE DETECTED

THROUGHOUT (TO

(OD)(SCAN)JPSR PICKING)

OBSTICLE IS

THEN

DETECTED

B

(OB.D) SR picks

E

Box F

Refer to these relay

conditions when the OD’s

are scanning and have not

detected an obstacle.

MCB – OD Page Seventeen of Nineteen

TRAIN PASSES THROUGH AND

ACTIVATES XASR & XUSR IN SEQUENCE,

AFTER ALL CONDITIONS MET, THE (CON)

SR RE-PICKS AND CROSSING RETURNS

TO NORMAL. (This is the same as normal

MCB crossings. (See MCB notes).

A B

(POD) (FRE A) SR drops

(OD) (CLR) R drops

(OB.D)SR drops

Z (RAI) SR(2) picks

(ABM)YJR starts

timing

(ABM)SR(2) drops

EXIT BARRIERS RAISE

RADARS RE-SCAN CROSSING

& CLEAR (NO

OBSTICLE)

2nd closure attempt recorded

EXIT BARRIERS DROP

1st closure failed

1 of 2 Stick paths

for (ABM)SR(3)

lost

(OD) (CLR) R picks

(OB.D)SR picks

Z (RAI) SR(2) drops (ABM)SR(3) drops

RADARS RE-SCAN CROSSING

(ABM)YJR has

started timing.

After 30

seconds, and

after

Z(RAI)SR(2) has

repicked, it will

hold it up

preventing any

further

attempts to

reclose the

crossing

A

If crossing remains clear 4 seconds after exit

barriers are down the (OD)(SCAN)JPSR picks. Go to

box ‘E’ above and continue.

Relay conditions as

above (see box F)

The POD and/or COD relays pick and

drop according to which

RADAR/LIDAR has seen the obstacle.

Note: This flowchart is based on a

four barrier type crossing. If fitted

with just two barriers, these will rise

if obsticle detected and fall again

when obsticle cleared.

MCB – OD Eighteen of Nineteen

A

OBSTICLE

DETECTED

(OD) (CLR) R drops

(OB.D)SR drops

Z (RAI) SR(2) picks

EXIT BARRIERS RAISE

(ABM)SR(4) drops

Two closures failed.

AUTO function is now

lost, no more attempts

to close crossing will

be made.

Alarm to signaller. He will need to

lower on button

The POD and/or COD relays pick

and drop according to which

RADAR has seen the obstacle.

Signaller selects LOWER

LOWER NPR picks

(ABM)ZR picks

Z(RAI)SR(2) drops

EXIT BARRIERS LOWER

SIGNALLER CAUTIONS TRAIN

ACROSS THE CROSSING

After the train has passed, and no others are approaching,

the signaller will raise barriers on manual. LC will reset as it

had seen a obstacle and not a fault. Technician will have to

observe detection area and determine the cause.

MCB – OD Page Nineteen of Nineteen

It may be a good idea to affix this to the signaller’s panel to aid them in diagnosing properly an OD fault. Sometimes the OD has not actually ‘failed’ and has done its job by seeing an object on the

crossing, therefore a different priority is needed on how quickly an attendance is required.

MCB – OD signaller’s indications

To be read in conjunction with signallers fault finding ‘FF’ guide.

Indication Normally (NO SIGNALLER INTERVENTION) Other Indications/comments. (p--) see page in ‘FF’ guide

UP STEADY WHITE FLASHING (p8)

AUTO STEADY WHITE FLASHING (p8) NO LIGHT (p9)

WORKING EXTINGUISHED OR STEADY WHEN INITIATED IF MANUAL LOWER INITIATED AND NOTHING

HAPPENS, (SEE p10)

RED ROAD LIGHTS

STEADY RED (WHEN ROAD LIGHTS ARE WORKING)

FLASHING (p10) EXTINGUISHED (p10)

DOWN FLASHING WHITE (WHEN BARRIERS DOWN) AWAITING FOR OD’s TO SAY XING IS CLEAR OR DOWN

DETECTION IS LOST (ONLY AFTER SIGNAL OFF)

DOWN STEADY WHITE (WHEN OD’s SAY CROSSING

IS CLEAR) IF NOT STEADY AFTER 4 – 6 SECONDS THE OD’s

HAVE SEEN AN OBSTACLE (SEE p11)

DETECTOR EXTINGUISHED STEADY RED (p12) FLASHING RED (p12)

STEADY WHITE & AUTO FLASHING (p12)

LOCAL XING CLEAR

EXTINGUISHED FLASHING (p13) STEADY WHITE (p13)

EXTINGUISHED WITH ALARM: (TAKEN OUT OF CCU)

OD FAILED STEADY WHITE FLASHING RED (p13) STEADY RED (p13)

FLASHING WHITE: FAULT CLEARED, SIGNALLER ACK

OD FAULT EXTINGUISHED

FLASHING WHITE (& OD FAILED GOES OUT) (p14)

STEADY WHITE (p14) EXTINGUISHED WITH

ALARM (p14/15)

STANDBY (POWER)

STEADY WHITE FLASHING RED (p15) STEADY RED (p15)

FLASHING WHITE (p16)

FAILED STEADY WHITE FLASHING RED (p16) STEADY RED (p16)

FLASHING WHITE: CROSSING BACK IN ORDER (p16)

ACKNOWLEDGE (BUTTON)

EXTINGUISHED ILLUMINATED (WITH ALARM) WHEN SIGNALLER

ATTENTION IS REQD Note: signallers understanding of the OD functions is imperative to their operation should failure occur.

Not following the instructions in the FF guide, may increase the failure severity. Reliable information given to the signalling technicians during and after failure will greatly increase chance of rectification – please note

these down or take a photograph to record them.

Handing back barriers after being on local control: 1. Ask attendant to lower the barriers if not already. 2. Ask attendant to turn the LCU switch to NORMAL, close and lock the door and remove the key. 3. Signaller must then place their switch to LOWER to bring into correspondence. 4. Signaller can then raise the barriers and then set the switch to AUTO.

Note: there are no specific instructions for coming out of CCU mode, however, it is recommended that the barriers are in the raised position before doing so.

From MCB-OD notes (F. Spowart) Version 1.8 July 2016 (UPDATED)

Signallers fault finding ‘FF’ guide can be found in Dropbox under ‘Manuals’.

Copyright F. M. Spowart July 2016 Version 1.8