MODCOMP Data Receiver

This application (named moData) is designed to receive scan and limit changes from the MODCOMP (using TCP over the MRN-250). An EVI application runs on the MODCOMP each time a scan or limit change is made that queues the change to moData. Every [time period] moData and the MODCOMP app communicate to determine which changes have been applied and which must be (re)sent.

moData handles one particular type of change in a special way:  When all of the SMOKE (PG) points in a unit are taken on or off scan (made ACTIVE or INACTIVE on the MODCOMP), moData instead marks the unit as running a smoke test. This allows the MUXCTL application to remove (or restore) all alarms for the smoke points without requiring a huge number of database updates.

Specifically, moData processes the following commands from the MODCOMP:

Alarm Limits

• CHGDS
• CHGASS
• CHGLMN (except for PG points)

Scan Status and Alarming

• CHGSMN

Unit Computer Control

• UPON
• UPOFF
• LOADON
• SNDUDB
• UPHALT
• IPLODT
• UPLOAD
• USTLOD
• XSTLOD
• SNDBON

Most (if not all) of these commands are now implemented in the PICS application named sdBatch. This was done in an attempt to flatten the learning curve for the transition from the MODCOMPs to PICS.

Logging

moData logs all activity to a file in the PICS logs folder (typically C:\PICS\log). The logs serve two purposes:  first, they provide an audit trail of commands received from the MODCOMP; second, they provide diagnostic information in the event that anything should go wrong while processing a command.