Burkert Type 8620 - Manual (Page 40)

mxCONTROL Type 8620
Page 40
The layout of the data logging file, the abbreviations and the coding used in the header are shown
in an example in appendix 21.6.
Automatic log file size limitation (FSizeLimit = Yes)
A new log file is started automatically by increasing the log file index,
if data logging was active and the current log file size exceeded the maximum log file size FSizeMax.
Event Triggered Data Logging Function
An integrated Event Triggered Data Logging Function logs a complete set of process data with
max. 10 s delay, after a specific event was triggered.
Such specific events are:
• Occurrence / Disappearance of an alarm.
• Occurrence of important error messages
- Battery Failed / RTC Failed / Check Clock!
- Eeprom Fault XXY
- Error ISR timing!
- Calibdata Fault 4-20mA In / Pt100 in / 4-20 mA Out
- 4-20mA Out X failed
• Changing operational mode (Automatic / Manual)
• Switching on/off of an output, which is configured as an On/Off output
• Communication events and errors (devices with Ethernet Option only)
- Start / end of incoming / outgoing connection
- Changes of net link status
- Important communication error messages
• Miscellaneous events
- Totalizer reset
- Start / end of user calibration of 4-20mA inputs / outputs
The event triggered data logging function can be enabled / disabled and configured by means of
configuration. For details refer to section “Configuration”.
Datalog failed alarm
If data logging failed (e.g. in case of writing error or full/missing SD Card), a special datalog alarm is
raised and the common alarm is actuated, too.
This special datalog alarm needs to be reset in the data logging menu by the operator.
Log files are stored in the root directory of the SD card. The root directory can contain
approximately max. 100 entries (files and folders; each file / folder name has max. 31
characters).
Back up older log files in time from SD card on PC. If permitted, delete them afterwards on SD
card.