Fault
codes
Name/text
Description
Cause
Remedy
4
Database
checksum
Corrupted data in ee‐
prom detected by
checksum test made
during power-up
● Power failure during
Eeprom write
1. Reset checksum repair alarm via
parameter 560 and check data.
– All data is checked after operation
(e.g., new flow calculation, writing
to the EEprom, etc.) with a
checksum control. If the checksum
result fails, data will not be
considered as valid and repair data
must be made.
2. If data is wrong or checksum error
reoccurs, replace the PCB board.
The alarm is active until the fault condition
is corrected.
5
Low Power
Alarm
Battery capacity is be‐
low preset threshold
(default 10%).
Power up (temporary
warning – will disappear
after 4 hours)
● Battery capacity low
● Meter has been
powered up
Check calculated battery capacity (param‐
eter 510) versus battery alarm limit (param‐
eter 206) and replace batteries if necessary
Flow measurement and communication
stop, but display remains active as long as
power is available.
The alarm remains active until the fault con‐
dition is resolved.
6
Flow Overload Flow rate has exceeded
125% of Q3
● Wrong sizing – flow
sensor too small
Check meter sizing for actual installation
Alarm remains active until fault condition is
resolved.
7
PulseA over‐
load
Duty cycle of output A
has exceeded maxi‐
mum possible of 50
● Wrong settings for
output A
Change volume per pulse to a higher value
- see Technical data (Page 96) for pulse
selection.
Reminder: basic version is limited to 50 Hz
maximum; advanced version to 100 Hz
maximum.
The alarm remains active until output pulse
rate drops below maximum pulse rate.
8
PulseB over‐
load
Duty cycle of output B
has exceed maximum
possible of 50
● Wrong settings for
output B
Change volume per pulse to a higher value
- see Technical data (Page 96) for pulse
selection.
Reminder: basic version is limited to 50 Hz
maximum; advanced version to 100 Hz
maximum.
The alarm remains active until output pulse
rate drops below maximum pulse rate.
9
Consumption
Interval
Accumulated volume
on totalizer 1 during da‐
ta log period has excee‐
ded the too low or too
high consumption limit
● Flowrate higher or
lower than expected
● Wrong parameter setup
Check data logger values and consump‐
tion limit.
Alarm remains active until it is manually re‐
set via parameter 209.
Troubleshooting/FAQs
9.1 Fault codes
SITRANS MAG 8000
86
Operating Instructions, 11/2018, A5E03071515-AE