KROHNE ALTOSONIC V Modbus EN - Manual (Page 55)

ALTOSONIC V
ModBus Manual 0300 rev07 E 7.30855.35.00 Page 55 of 64
8.11 The System Messages
The system messages contains the system runtime warnings and alarms. They are stored as bits into
the integer data. Each system message is packed as one message per bit of the integer. The message
is active if the accompanying bit is one. The messages are numbered from the least significant bit to
the most significant bit.
The status of the system is divided into:
•
System Runtime Warnings. These are caused by system failures. These failures will not influence
the flow measurement.
•
System Runtime Alarms. These are caused by system failures. These failures might influence the
flow measurement.
Identified System Runtime Errors are numbered 1 to 60 are:
Identified System Runtime Errors are numbered 1 to 60, A = alarm, W = warning:
Error no. In function Problem Consequence
A : 1 Get RS485 data from
converters
Overrun, missed data Missed data, message
A : 2 Self test Error in self-test Non-reliable memory
A : 3 Batch start / stop Error during saving files of start or stop File lost but ticket is made
A : 4 Profile correction (REAL) Error in state_correction Attempt divide to by zero
W: 5 Read Backup all files Error in reading backup file Possible loss of backup file
W: 6 Switching disk Error in finding a drive Message
W: 7 System time A notice that the system time was adjusted
manually or by Modbus.
No consequence for totalisers or
proces time, only on ticket time
A: 8 CRC checksum
Executable Executable is corrupted or not certified
version 03.00.50.00 and higher Load new executable. Contact
Krohne service department
A: 9 Batch status backup Status file corrupt Possible loss of batch status
W: 10 Override values files Error in opening/closing override value file Override values not stored but
still in use
A: 11 Batch totaliser backup Totaliser backup-file corrupt File lost , message
A: 12 Batch average backup Average backup-file corrupt File lost, message
A: 13 Batch ticket create Error in creating batch ticket file Ticket itself is made for printing
but lost during saving
W: 14 Opening file (for update) Error in opening REAL file File lost, message
W: 15 Closing file (for update) Error in closing REAL file File lost, message
W: 16 API settings Error in file, defaults are loaded and saved Old settings lost
W: 17 Batch 2 A alarm on batch 2 file (Batch 2 is only
used through Modbus with a Scada
system)
File lost, message
W: 18 Check free disk-space Error dos_getdiskfree() call Time-out function 30 s
W: 19 Check free disk-space Low on disk-space Time-out function 30 s
W: 20 Ad card overrun The requested AD card is not noticed Solve the problem
W: 21 Opening file (for update) Error opening API table file File lost, message
W: 22 Value check 1 or more API values defaulted Check the installed parameters
W: 23 Opening file (for update) Error opening external flow meter file File lost, message
W: 24 Value check Default external flow meter K-factor Check the installed K-factor
W: 25 Counter input Unable to read Counter value Read on next entry
A : 26 Calibration MP103 card MPCA File corrupt Install backup
A : 27 Calibration AD card File corrupt Install backup
A : 28 Calibration data Densito
Cells
File corrupt Automatic install of default values
Set the correct values on-line
A : 29 Batch ticket currently
saved A Requested batch ticket not available for
printing A ticket by that name was not
saved or had a previous save
error
A : 30 Batch ticket CRC error in a Batch ticket A ticket was not saved correctly
or was changed manually
W: 31 Read batch ticket
previously saved A Requested batch ticket not available for
printing A ticket by that name was not
saved or had a previous save
error
W : 32 Batch ticket close file Error in closing a ticket file Ticket file not closed , probably
because it could not be opened