CPI 8800 (passive)

8800cpi

The CPI 8800 display (when attached) looks similar to the sample shown below. There is also a table of memory usage statistics, followed by a log of significant events that have occurred since the 8800av has booted.

 
  
>= ddddd mm:ss.sss             Version 5.11 CPI            (dd) ddd.ddd.ddd.ddd
|  Status  sssss   Time  sssssss     Network       SysLog Debug sss   FollowMux
State  ssssssssssRecv ddddddddRecv ddddddddssssss  ddd.ddd.ddd.ddd sss
Ctrl   ssssssssssBad     dddddBadRecv dddddBit masks...   87654321
Watchdog ssssssssAdjust  dddddSend dddddddd...for Screen xxxxxxxx  ◄-
  ssss mmm:ss.sssTickAdj  sdddBadSend ddddd...for Network xxxxxxxx  ◄-
Bytes In dddddddddd   Analog Converted ddddd  Refresh ddddd  Fail ddddd
  Tossed dddddddddd  Digital Converted ddddd  Refresh ddddd  Fail ddddd
Cmd Meaning                      Cmd Meaning
 S  toggle Syslog open/close      B  toggle syslog deBug
 Y  exit to DOS                   F  cycle Filter mask selections
 X  eXit and reboot           Alt200-231 toggle bit 0-31 of selected bit mask
 D  Disable watchdog              L  reLoad '8800.ini'
 E  Enable watchdog


  
 

The passive CPI 8800 monitors a serial data stream between the USEC/PGDP C-310 unit computer and CPI data collection system. The 8800cpi uses both the outgoing scan commands, CPI scan tables and CPI responses to identify data points being scanned. The database containing the point addresses, conversion types, and related information is downloaded from PICS through the MUXSDB application, which acts as a static data server for all 8800s. The MUXClock application provides a time synchronization pulse via a UDP broadcast once per second. The time pulse message also contains the current plant operating mode and a change counter for each 8800. The 8800s use the mode to determine which set of alarms (if any) to use when determining if a point is in alarm. They use their change counter to determine if they need to request a static data update from MUXSDB. When data values are scanned (or in this case, received on the serial line), the 8800 converts the raw value to engineering units and checks to see if the current alarm level has changed. If the point status has changed, OR if the EU value has changed more than the amount specified in the database (sig change threshold), OR the refresh interval (also specified in the database) has expired, then the value is reported to PICS through the MUXControl application. In order to lower the network overhead, the 8800s collect changes until either a ~500 byte packet is filled, OR 200ms have elapsed since the last report.

The information on the CPI 8800 display is broken into six distinct areas:

Header Line

The header line shows, from right to left, the following information:

Status

The status section shows information about the various states that the 8800 software uses to regulate its internal operation. It also shows the currently configured watchdog hardware type.

Time

The time section shows information about how well the 8800 is maintaining time synch with PICS.

Network

The network section shows how many packets have been sent and received and also how many send/recv attempts failed.

Syslog

Shows the settings for the syslog option, including the current IP address of the syslog server targeted to receive the 8800's messages and the current display and transmit bit flags. The bit flags determine which messages are displayed and/or transmitted to the syslog host.

Bytes In

The two 'bytes in' lines show how many bytes of serial data have been processed. One line shows stats for the analog port, the other shows the digital port. The Tossed count indicates how many malformed messages were discarded. The Converted count shows how many analog (or digital) points have been successfully converted from the input data. The Refresh count show how many analog (or digital) refresh records have been transmitted and the Fail count shows how many analog (or digital) points failed in the EU conversion routine. The EU conversions may fail for a number of reasons, the most common of which is a garbled address field in the serial data stream, which causes the 8800 to be unable to find a match for the point.