Rockwell Automation FactoryTalk View Site Edition Users Guide - Manual (Page 239)

11 • S ETTING UP HMI TAG ALARMS
11–27
•
•
•
• •
11
•
Pla
ceho
lde
r
Example: Exporting alarm log files to ODBC format on demand
To export the contents of the alarm log files to an ODBC-compliant database on demand,
create a graphic display containing a button that uses the AlarmLogSendToODBC
command as its press action.
When the operator presses the button at run time, the contents of the alarm log file will be
exported to the ODBC database.
The AlarmLogSendToODBC command exports only the records added to the alarm log
files since the last export.
ODBC database schemas for HMI alarm logging
FactoryTalk View generates HMI tag alarm and data log information that can be stored in
ODBC-compliant databases.
HMI tag alarm data stored in ODBC format uses the following table. For information
about how alarm log files are named, see page 11-30.
This column Contains SQL data type Length
TimeStmp The time and date data was logged, in UTC
(Coordinated Universal Time) format.
TIP : If the ODBC database does not support
SQL_TIMESTAMP, the data might be truncated.
If you are using the Oracle ODBC driver, for
example, to avoid truncating date and time data, use
SQL_DATE instead of SQL_TIMESTAMP.
SQL_TIMESTAMP Driver
dependent
MilliTime Millisecond time when data was logged. SQL_INTEGER 3
TransType The type of alarm that was generated. The
transaction type is one of:
SysAk (System Acknowledged)
InAlm (In Alarm)
OutAlm (Out of Alarm)
InFlt (In Fault)
OutFt (Out of Fault)
Ack (Acknowledged)
RmAck (Remote Acknowledged)
SupOn (Suppress On)
SupOf (Suppress Off)
Remar (Remark)
SQL_VARCHAR, or
SQL_CHAR 6