When diagnosing issues with faults and relays in a GLOBALCOM system, it can be useful to query the System Supervisor service and/or the LIR service for what they think the current state of things is.  This article provides information on the built in diagnostics which are available. 

System Supervisor

There are two queries that can be done to the System Supervisor, one for current faults and one for current relays.  This is done by typing the below URLs into a browser address bar.  What you will see in the browser window is the XML representation of faults or relays (see attached example of faults).  If there are no faults or relays, what is displayed may simply be "<faults />" or "<relays />".  If running on the GLOBALCOM 1100/1200ACS, you can use the following URL addresses:

      http://localhost:8088/SystemSupervision/Legacy/faults

      http://localhost:8088/SystemSupervision/Legacy/relays  

Notice the :8088 in the URL.  This is the port number since this query is not done to the standard HTTP port of 80.  If one is not on the GLOBALCOM box,  then the URLs are modified to put the IP address in place of "localhost", e.g,.
       http://10.2.23.4:8088/SystemSupervision/Legacy/faults

LIR Service

There are two ways to query the LIR service:  via IEDnet or via Web URL.  The IEDnet method is to use NetMon32 to send a message with Object ID 0x1000, Message ID 0x0026.  Add one data field and type the relay number into the data field (1 ... 8).  Enter the 1200ACS IP address (or 127.0.0.1 if on the box).  Then click on the Send Fields button.  The return starting at byte 09 should be 00 (ACK), then the relay number sent, and then a Word (two bytes) that is zero (00 00)  if the relay is de-activated and non-zero if active.  (The number is an Action ID, which is like an announcement ID except for this type activity.)

The Web method is to enter the following URL into a browser address bar.  The browser will prompt you to save a text file, which is the JSON representation of all the relay states (see attached example).  Note, if reverse polarity is used, the LIR will show that the relay is activated in the normal non-faulted condition.  Entries in the JSON file will be a list of relay number followed by Tag.  The Tag is the Action ID described above for IEDnet response;  zero means de-activated. 

          http://localhost/lir/debug/relays

Again, if running remotely, replace "localhost" with the IP address of the 1200ACS.  Also available is a way to query the logic inputs via the URL:

         http://localhost/lir/debug/inputs

Bonus Information

If one wants to test the relays, one can send IEDnet commands to the LIR service to turn relays on and off.  One diagnostic trick to try in cases where the hardware is suspected of not working is to toggle relay #8.  This is done by the IED software at start up to "unlock" the other relays.  To turn a relay on or off, one sends an IEDnet message to Object ID 0x1000, Message ID 0x0025 with the following field values:

Field 1 (byte):  1
Field 2 (byte):  1 to energize or 0 to de-energize the relay.
Field 3 (word): Action ID (any value, perhaps by convention use relay number here too)
Field 4 (byte):  FF
Field 5 (32 bytes):  all zeroes or define as string of length 32 ("123455678901234567890123456789012")
Field 6 (byte): relay number
Field 7 (Word): zero