76 S&C Instruction Sheet 1043-550
Historic Event Log
IntelliLINK Historic Event View screens can show only a small portion of all historic events
stored in the control memory. To view the 4,096 events stored in control memory, use the
IntelliLINK HTML log feature. To access the IntelliLINK HTML Log:
1. Go to the Data > Event/Data logs menu in IntelliLINK to open the “Select Log
Dialog. Expand the item in the dialog and choose the “Historic Event Log”
option.
2. Click OK. You may check the “Save To File” checkbox to generate an HTML file
on your disk.
3. Wait several minutes while event data is downloaded from the control.
4, The log containing all historic events in the control memory will be displayed
in an Internet Explorer window (unless the “Save To File” checkbox was
checked).
The resulting log is sorted chronologically and contains up to 4,096 of the newest historic
events that have been logged.
The columns in the HTML log table are identical to those on the Historic Event View
screens. The HTML file can be opened with Microsoft Excel, or copied and pasted into
Excel, where it can be re-arranged in any way that the spreadsheets will allow.
Compact Flash Log
Compact flash logging requires a 1GB, or larger capacity, compact flash card. S&C sup-
plies and recommends the SanDisk Extreme® III CompactFlash® 1GB card.
The CF
card must be formatted as FAT, rather than FAT32
(all cards shipped by S&C have
been correctly formatted).
When compact flash logging is enabled (from the
Logging Setup
screen or the keypad),
every historic event generated by the UIM application is written to the Compact Flash,
even if historic event logging has been stopped for the in-memory event log, or the event
does not satisfy logging criteria.
The UIM uses 100 pre-allocated fixed-size files to store historic event data in the compact
flash, holding a total of over 1,000,000 events. The files are named LOG00.VM, LOG01.
VM…LOG98.VM, LOG99.VM and are of very similar size. The files are continuously reused:
once Data Logging fills all 100 files, LOG00.VM will be opened again, and new events writ-
ten, starting from the file’s beginning, and replacing the oldest events. This means that
after all 100 files have been used, at any given moment, one of the files is circular, without
a fixed beginning.
NOTE: the number of event entries in a full file is around 14,000 entries, but this is not a
precise count, and varies slightly for each file. This means that a reused file is likely to
contain a small amount of very old data at the end. The older events are obvious because
they are timestamped.
Sometimes data being stored to a file is interrupted, normally by a power loss or CF removal.
In this case Data Logging assumes that the file is corrupted, saves it under a unique name
such as “AABBCCDD.err”, and creates a new file for future use. A corrupted file like this
can still be useful, because usually only a small amount of data is lost. There is a Special
Event Counter associated with the saving of a corrupted file, called “CF Data Likely Lost
on Error,” that can be viewed on the Special Events screen.
CAUTION: do not remove the Compact Flash card when Compact Flash logging
is active
(which can be seen on the “Logging Setup” IntelliLINK screen or on the LCD).
Doing so may corrupt the card and cause loss of data. Disable compact flash logging first,
either with IntelliLINK, or with the keypad.
Data Logging
