VAF instruments Shapoli 620 - Alarms

21
Besides the Power limitation event there are five more events that are logged in the Event Log menu:
Event type:
Causes:
Verification needed:
Power above limit
Shaft power exceeds the EEXI power limit
YES
SDB-3 was turned off
The power of the SDB-3 was turned off
NO
Missing settings
The settings-file with EEXI limit is missing
One of the two power-sensors have not
been enabled
NO
No sensor
communication
No power signal available of T-/TT-sense
(Modbus) or 4-20mA of 3
rd
Party Torque
meter
NO
No NMEA data
No NMEA signal available via RS485 or
TCP/IP
NO
No IO communication
No communication with IO-modules (4-
20mA inputs)
NO
7.5.3 Alarms
At the top of the screen you will find a tab Alarms representing the internal Sensor Alarm functions. In
case the Bridge Panel PC detects an alarm the ShaPoLi and Alarms tab blink red. An Alarm Message
will appear on the Current Alarm screen.
The Alarms menu is divided in 2 submenus:
• Current Alarms
• Alarm log
Current Alarms:
In the situation of an alarm due to an error in the system, an alarm message will pop-up in the Current
Alarms submenu. All active (current) alarms are shown in this overview and can be Silenced and
Accepted by touching the Silence and/or Accept button behind the specific alarm, in order to Silence
and/or accept the internal alarms.
An alarm can be triggered for one of the following reasons:
- Power is above the EEXI Shaft Power Limit
- T-Sense
®
/TT-sense
®
(over MODBUS) communication failure
- NMEA communication failure
- Some of the expected power sensors have not been enabled
- Individual sensor (Torque, Speed, Power) communication failure if using an analogue power
sensor
- Missing encrypted ShaPoLi settings
- IO communication failure
Figure 24 – Alarms menu - Current Alarms
Figure 25 – Alarms menu – Current Alarm can be Silenced
and Accepted