SOP PRO General Maintenance Check
From PTAGISWiki
Standard Operating Procedure
| |
Subject:
| SOP PRO General Maintenance Check
|
Author:
| Alan Brower
|
Approved by:
| Don Warf
|
Contents |
Objective
This procedure describes the activities required to perform a General Maintenance Check (GMC) at the Chandler diversion dam and juvenile fish facility in Prosser, Wa.
Scope
This procedure is to be used as necessary to verify and/or restore peak system performance at the interrogation site itself. During the execution of this procedure, problems may be discovered that are outside the realm of this procedure. Remedies to problems found during the execution of this procedure could possibly be found in the SOP Troubleshooting Sub-Group. The GMC is intended to provide periodic optimization of system performance from the antennas to the ISP.
Responsibilities
This procedure is to be performed by or under the supervision of qualified PTAGIS staff. The scheduling of GMCs is determined by the PTAGIS Field Engineering Supervisor.
Procedure
1) Preparation
Obtain information about site status prior to arrival.
- Check (or have someone check for you while you are en-route) the most recent operation status reports generated by PTAGIS on three hour intervals
- Information gleaned from the reports can give indications of work that needs to be done
- http://www.ptagis.org/cgi-bin/linkcheck.pl?max=8&site=PRO - Take special note of this report to verify radio modem functionality.
- Check (or have someone check for you while you are en-route) the event log for problems that have arisen since the last GMC
2) Initial Actions
Upon arrival:
- Communicate with the facility point of contact (usually the site biologist) to learn of unknown issues (if any) about the site
- Address any substantial problems that were discovered prior to arrival (such as transceiver failures, timer tag failures, locked up interrogation computers, etc.)
3) Verify Data Collection Platform Status
- Power on the video monitors
- PC1 & PC2
- Verify proper Windows OS functionality
- Observe keyboard/mouse operation, video updating, clock operation, etc.
- Verify Minimon functionality and transceiver communications
- Check in the "Device Status" tab that the proper file is being created as per SOP Minimon Site Configuration for each PC
- Observe live information from the transceivers in the "Logging Data" tabs
OR
send a command such as "DTS" (single test tag) or "DRS" (status report request) using the "Command" button on PC2 to a transceiver and observe the live information from the transceiver in the "Logging Data" tabs
- On PC1, verify that the files prior to the current file have been sent to PTAGIS and then archived
- Archive the data files on PC2 as per SOP Site Platform Manual File Submission
- Verify proper Windows OS functionality
- Perform SOP Site Platform System Clock Adjustment
- Check the six radio modems for "Link" lights to verify transceiver communications
4) Tune Transceivers
In no specific order:
- Tune the JFF separator transceivers (IDs A1-A3) and sample transceivers (IDs 51-52) as per SOP FS1001 Tuning
- Tune the left ladder transceivers (IDs 01-02), center ladder transceivers (IDs 03-04) and right ladder transceivers (IDs 05-06) as per SOP FS1001A Tuning
5) Verify JFF monitor detection with test sticks
This test can be accomplished alone, but is easier with someone to retrieve the test sticks.
- Insert 20 test sticks into the entrance of the separator monitor
- Insert the test sticks no faster than one every five seconds to avoid grouping in the monitor
- Retrieve (or have someone else retrieve) the sticks as they exit the monitor
- Insert 20 test sticks into the entrance of the sample monitor
- Insert the test sticks no faster than one every five seconds to avoid grouping in the monitor
- Retrieve (or have someone else retrieve) the sticks as they exit the monitor
- Use the "Report" function in Minimon (see SOP Minimon Operators Manual) to verify that the sticks were detected.
6) Best Practices
- Archive outstanding files on PC2
- Turn off the video monitors when leaving
- Check to see that the temperature in the PIT Tag Room is conducive to PC performance
- In the fall, set the heater to ~68F
- In the spring, set the air conditioner to ~72F
- Observe the surroundings while on-site, looking for possible problems such as:
- Loose conduit in the ladder
- Self-ballasting fluorescent bulbs (possible noise source)
- Near-by activities such as construction or other agencies projects that could impact system performance
7) Send a PIT Event
Submit a PIT Event to the event log describing the actions taken during the GMC (transceivers tuned, date, clocks set, files submitted, sticktest results, notes, etc.).
References
Event Log - a journal of events pertaining to site status located at ftp://ftp.ptagis.org/Reports/event_log/PRO
General Maintenance Check - a.k.a. GMC, a group of activities routinely performed to optimize and verify equipment at an interrogation site.
Operation Status Reports - The following reports are available on the internet:
- File Load Status and Gaps - http://www.psmfc.org/cgi-bin/pittag/fd_fileStat.cgix
- PRO Radio Check - http://www.ptagis.org/cgi-bin/linkcheck.pl?max=8&site=PRO
SOP FS1001 Tuning - PTAGIS SOP
SOP FS1001A Tuning - PTAGIS SOP
SOP Minimon Operators Manual - PTAGIS SOP
SOP Minimon Site Configuration - PTAGIS SOP
SOP Site Platform Manual File Submission - PTAGIS SOP
SOP Site Platform System Clock Adjustment - PTAGIS SOP
SOP Troubleshooting Sub-Group - A sub-group of the PTAGIS SOP library
Submit a PIT Event - This can be accomplished using the web based form at http://www.psmfc.org/cgi-bin/pittag/send_2_event_log.cgi or by sending an email to pitevent@psmfc.org with the subject of PRO.
Test Stick - typically a 9" piece of 3/4" yardstick with a PIT Tag sealed into one end


