Data Logging and Display When saving the alarm history in the proprietary format, each alarm event is saved in a new line, using the pipe character ( | ) to delimiter the different fields, as illustrated below: P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19|P20|P21 P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19|P20|P21 . . P1|P2|P3|P4|P5|P6|P7|P8|P9|P10|P11|P12|P13|P14|P15|P16|P17|P18|P19|P20|P21 The format of the history both in proprietary format and in the SQL Relational Database format is described in the following table: Page 224 InduSoft Web Studio Proprietary SQL Relational Database Remarks File Vers. Field No.
Field Name Field Type P1 — — File version (Current = 003) 001 P2 Al Start Time _ _ Date/Time Start Date (MM/DD/YYYY) 001 P3 Start Time (HH:MM:SS) 001 P4 Al Tag _ Text Tag Name 001 P5 Al Message _ Text Alarm Message 001 P6 Al Ack _ Number Ack, where: • 0: Alarm was acknowledged or does not require acknowledgment • 1: Alarm was not acknowledged 001 P7 Al Active _ Number Active, where: • 0: Alarm is not active • 1: Alarm is active 001 P8 Al Tag Value _ _ Number Tag Value when the event occurred 001 P9 Al Group _ Number Alarm Group Number 001 P10 Al Priority _ Number Priority Number 001 P11 Al Selection _ Text Selection 001 P12 Al Type _ Number Type, where:
• 1 is HiHi • 2 is Hi(On) • 4 is Lo(Off) • 8 is LoLo • 16 is Rate(Change) • 32 is Deviation+ • 64 is Deviation- 001 P13 Al Ack Req _ _ Number Ack required, where: • 0: Alarm requires acknowledge • 1: Alarm does not require acknowldge 001 P14 Al Norm Time _ _ Date/Time Normalization Date (MM/DD/YYYY) 001 P15 Normalization Time (HH:MM:SS) 001 P16 Al Ack Time _ _ Date/Time Ack Date (MM/DD/YYYY) 001 P17 Ack Time (HH:MM:SS) 001 P18 Al User _ User Name 002 P19 Al User Comment _ _ Comment 002 P20 Al User Full _ _ User Full Name 003 P21 Al Station _ Station 003