SOP Remotely Checking Gate Sensors

From PTAGISWiki

	Standard Operating Procedure
Subject:	SOP Remotely Checking Gate Sensors
Author:	Troy Humphrey
Approved by:	S.Livingston 12/22/08

Objective

The objective of the procedure is to guide the reader through the steps necessary to investigate a gate trouble alarm or simply to view the performance of the gate sensors and the anti-slam logic of the slide gates at GRJ, GOJ and LMJ.

Scope

This procedure describes how to open RSLogix500 and what to look for when trouble shooting a gate trouble alarm. It does not cover PLC program changes and caution should be taken when performing this procedure. While this procedure is intended to be used for remote checking, portions of the procedure can be applied if the reader is on sight and using the utility machine.

Responsibilities

PSMFC Field Maintenance personnel are responsible for investigating trouble lights and monitoring the performance of the anti-slam slide gate logic.

Procedure

Establish a PCA connection

Using Aventail or a working VPN, establish a PCA connection with the utility machine of the site you are interested in.
If you are unable to establish a connection you may have to call the site to see if they can re-boot the utility machine for you or you may have to drive to the site.

Open the RSLogix500 PLC program

Click on Start, Documents and look for the program there. The program name will be the site acronym. For example Lower Monumental will be lmj.

If you do not find it as a recent document, it is located under C:\Program Files\rwsw

Once the program is up maximize the window.

Go Online

Click on the pull down in the upper left corner and select Go Online. (See below graphics)

RSLinx should start on its own.

You will know you are online when the RSLinx icon shows up in the system tray and the Online/Offline box reads REMOTE RUN and has a green back ground. (See below graphic)

Checking the Counters

Custom Data Monitors have been built for easy access to pertinent sensor logic counters. Scroll down to the Custom Data Monitors and double click on the gate of interest.

Interpreting the Counters

The following graphic shows a CMD for a gate.

Missed or Stuck On counts will cause gate trouble lights if the count is higher than the set threshold (This varies from site to site but was originally set to 3 counts = alarm).
- These cannot be re-set to 0 by sight personnel.
- If you need to clear the alarm you should visit the site to clear it from the PV300.
- You should note the missed or stuck on counts in a pit-event prior to clearing.
Stuck Open or Closed counts can be re-set to 0 by site personnel.
Time Used counts is a indicator as to how many times potential 'double-slam' instances were avoided due to the sensor logic being in place.

Typical causes for Gate Trouble alarms

If a sensor is being missed it most likely needs to be re-aligned.
- Sometimes the vibration of the gate slamming can cause the sensor to flicker which could register as a 'sensor missed' count.
If the sensor 1 stuck on count is high or the gate stuck open count is high it is most likely due either too short of a travel close time or the gate is having trouble closing due to alignment issues or the soft close regulator is too tight.
- A site visit is generally required as this phenomena can cause gate trouble lights.

Going Offline

When you are done checking the counters for the gates you are interested in, click on the pull down box in the upper left corner and select Go Offline. (See below graphic)

Once you are off line close the RSLogix500 program.

Shut down RSLinx

Right click on the RSLinx icon in the system tray and select Shutdown RSLinx.

End your PCA session

Once you have completed checking the gate and sensor counters end your PCA session ensuring that the 'Host Accepts Another Call' box is checked.

References

Refer to the following SOPs for question regarding the set up of slide gates and slide gate sensors.

SOP Slide Gate Timing and Pneumatic Setup
SOP Slide Gate Sensor Install and Timing Setup