|
|
|
|
This application (named upData) was created to help the MODCOMP limp along, ahem, continue running during the conversion to PICS. Its purpose is to send data (via TCP using the MRN-250) to another EVI application that runs on the MODCOMP. The EVI MODCOMP application takes the data (both alarms and scans) and provides it to the pre-existing MODCOMP rpograms as if it were coming from a unit computer (which was also a MODCOMP).
upData may be configured to consider any 8800 (pair) as being active (in control) or passive. Data for passive 8800s is NOT provided to the MODCOMP (it is assumed that those unit computers are still functioning). In order to emulate the way the MODCOMP programs functioned, upData will set a point OFF SCAN (or INACTIVE in MODCOMP terms) when it sees a hardware error for a scanned point. This will trigger an SDB update for the point which will propigate down to the 8800 to stop scanning for the point. However, a few more records may still be received for the point before the sequence is completed.
The image above shows upData's main window immediately after the program started. During startup, upData logs the configuration it loaded, the program version info, and the current state of the PICS node (primary, backup or standby). From this point onward, upData will continue to log various events as they occur. When the user changes which 8800s are in control , the Unit Control Status table will be logged. If the user has activated one of the monitoring functions (described in the monitoring section below), the selected events will be logged. Lastly, if the user chooses to dump some types of information (described in the dumping status section, below), that will also be logged.
The panel shown above allows the user to specify which 8800s are controlling (active) or not controlling (passive) their respective unit's scanning hardware. The units showing a check mark in the checkbox are controlling units. All others are passing.
During the testing phases of the change from MODCOMP II unit computers to the 8800s, it might be helpful to see the actual data being sent from PICS to the MODCOMP. The monitoring options above allow specification of various items to be monitored. Because of the volume of data that monitoring may generate, you'll notice that only one item may be selected at any given time.
The Alarm Queue may be monitored in 'raw' (just shown as hexadecimal values) or 'cooked' (shown translated to be more human-readable) format. upData sends health messages periodically to help the application on the MODCOMP side detect a loss of connection. Checking the 'Include Health Msgs' box will include those in the log.
The Live Data from a particular unit may also be monitored, however, only one type of data may be monitored at a time. Each unit may send up analog data, analog statuses, digital statuses and PG statuses.
The final option, Monitor Nothing, turns all monitoring off and is the default setting for upData.
Because of the hardware and software differences between the MODCOMP and the PICS packages, there is often a dispute over whether or not data is being transmitted correctly between the two. The status menu allows the user to dump a complete status block for any unit at any time (regarless of the current monitor setting, see above). The Dump Everything option does just what it says and should be used sparingly (because upData is not performing its primary task while it is logging all that data). The swap byte order option affects the actual data being sent to the MODCOMP, so DO NOT select that menu option unless you are certain it is necessary!
|
|
|
|