85-3 Callout Box

We now have a callout box connected to the 85-3 system. Actually, as you know, it has been hooked up for a while so we could test it and get the bugs out of it. The callout box sits on the desk in front of osiris' monitor in the USNO control room. It is connected to a normally open (#3) contact on sensaphone number 2336 on the desk to the right of the monitors. In order for the callout system to work, a cleo application has to be launched on osiris. That application monitors the system status and communicates with the callout box. This communication is indicated by a red light on the mid right hand side of the callout box blinking approximately every 10 seconds.

Info

There are two events which can trigger a callout:

1. Loss of communication between the watchdog program and the callout box (indicated by the red light #1 on the callout box).

2. Any system status message that we have programmed into the cleo application to trigger a callout (indicated by red light #2 on the callout box).

Note that the callout message you will receive from the sensaphone for either event will tell you that an "alert condition 3 exist". All alarms except for the deadman timer will also write a message to the 85-3 message window on the 85-3 control PC (Amanda), and on any other 85-3 message window that might be up and running. (I currently have one running on osiris as well and recommend that you keep it running.)

The sensaphone is currently programmed to call the following phones in order:

2341 GBT control room primary
2346 GBT control room secondary
2187 Warehouse
456-4457 Pete's home phone

RESPONSE TO A CALLOUT:

STEP		ACTION
1	Acknowledge the alert by entering 555 on the phone as is the case for all other sensaphones around the site.
2	Go to the USNO control room and look at the callout box to see whichred light is on. A. IF #1 is on, the problem will be something disrupting the communication between the cleo application and the callout box. B. If #2 is on, look at the cleo message window to see the problem.
3	Flip the callout box switch up to "CALLOUT DISABLED".
4	Take appropriate steps to correct the problem that caused the callout. (Call Pete if necessary).
5	Clear the message and reset the callout box. A. Go to a terminal or console window on osiris and enter: msg853 clrNote that this will in itself trigger an alarm. This is why you should disable the box first. After entering this command, you will see "Message Cleared" in the Cleo message window. B. Go to the cleo "Call Out Box" window and click on the "port 2" button under Acknowledge to reset the callout box (You can also click on the "Acknowledge All".)
6	Flip the callout box switch to the down (enable) position.
7	Press the "Run/Standby" button on the sensaphone until it says "Hello, this is sensaphone 1104".
8	Fill out the 85-3 Operating & Maintenance log describing the problem, when it occured, and how much time was lost. Note that the deadman timer alarm may or may not be a cause for lost time.

DISABLING CALLOUTS:

Do this if you wish to prevent the callout box from triggering a sensaphone callout. You should do this anytime you will be halting for maintenance, halting Backer's pc or changing over Backer's pc to "gogbt" for GBT observations, and if you need to logout gbiop on osiris for whatever reason, or any other activity you know will trigger an alarm.

STEP		ACTION
1	Flip the switch on the box up to "CALLOUT DISABLED"
2	Flip the switch on the box down to enable it again when finished and observing has resumed
3	If you accidently trigger an alarm, you can stop the sensaphone callout by pressing the Run/Standby button on the sensaphone
4	To put the sensaphone back in a ready state, push that button once or twice more until it says "Hello, this is sensaphone 1104"
5	Update the Callout enabled/disabled status on white board in the GBT control room to reflect the current status.

STARTING THE CLEO MESSAGE WINDOW ON OSIRIS:

STEP	ACTION
1	Login to osiris as "gbiop" if not already logged in.
2	Open up or go to a terminal or console window (preferably on the right hand monitor).
3	Enter: cleo
4	Launch the "Messages" application.

STARTING THE CLEO CALLOUT BOX APPLICATION:

STEP	ACTION
1	Login to osiris as "gbiop" if not already logged in.
2	Open up or go to a terminal or console window (preferably on the right hand monitor).
3	Enter: cleo -gbi calloutbox

Reasons for getting a call:

Deadman timer: This is a timeout circuit in the callout box. It requires that "gbiop" be logged in on osiris and the "Call Out Box" application be up and running. This application sends a signal to the the callout box approx. every 10 seconds. If that communication is lost, an alarm will be triggered after approx. 30 seconds. This alarm will not produce a message in the message window.

Telescope limits: Any one of the telescope limits will trigger a callout. You will see a message in the 85-3 cleo message window as to which limit triggered the callout. The message will say "85-3 Telescope Limit" along with another message telling you which limit it was. Note that computer limits will not trigger a callout since the program can move the antenna out of these limits to track as the source rises, or to move to the next source when the time comes.

Don Backer's program not updating the bcpm file: This file is checked approx. once per hour to see if it has been updated. If not, it triggers a callout. This could be the result of his PC program not running or being in a hung state due to things such as losing the network connection to osiris. The message will say "GBPP LOG NOT UPDATING". You can look at the bottom line of the text in the yellow box at the upper right hand corner of the osiris screen. That last line should normally have a time less than an hour old (normally updates approx. every 1 to 10 minutes). In this case, the callout tends to occur approx. 1 1/2 hrs after the file was last updated.

GBT OPERATIONS PROCEDURES	Number: 853-01
Title: 85-3 Callout System	Last Revision: 28 MAR 03