Skip to main content
Skip table of contents

Alarm/state configuration

Last modified:

You can configure alarms to alert you to technical issues with your blue'Log and its connected devices.

  • View alarms under Cockpit > Alarms/State.

  • Alarms can be sent via email as an additional option.

  • VCOM USERS Enabling an alarm type toggle (such as Device alarm) allows the blue'Log to automatically transmit alarms to VCOM.

Activate alarms and notification period

Prerequisites
  • Device state alarms: from Firmware 22.0.0 on.

  • Power control alarms: from Firmware 27.07 on. For firmware below 27.0.7, you can find the power control alarms under Device alarm.

  • All other alarms are available with all firmware versions.

Steps
  1. Go to Plant > Alarms/state configuration > Alarm/state configuration.

  2. Activate the toggles for the required alarm types.

  3. Under Active time of notification, select the desired notification period.

    • Default: 24 hours

    • Sunrise to sunset: Enter the site's latitude and longitude and the desired time offset. Example: If the time is set to 6:00 AM - 6:00 PM with an offset of 10, notifications will be sent from 6:10 AM - 5:50 PM.

Activate an alarm and configure email notifications

Activate an alarm and configure email notifications

Set up email notifications

  1. Go to Receive alarms additionally via email.

  2. Enter email recipients, separating multiple recipients with a comma.

    • VCOM USERS Alarms will be transmitted and displayed in the VCOM alarm portlets.

    • Non-VCOM users: You can choose to receive alarms via email.

  3. Select the language for alarm notifications. 

    • Default: English (if the alarms are not available in all languages)

    • VCOM USERS The language in which alarms are sent depends on your VCOM language settings.

Filter undesired notifications

The image-20241121-122248.png Filter allows you to exclude specific error/event codes from notifications. This is useful if you want to avoid notifications for certain issues (for example communication failures).

Prerequisites

  • Device state alarms: from Firmware 22.0.0 on.

  • Power control alarms: from Firmware 27.07 on. For firmware below 27.0.7, power control alarms are listed under Device alarm.

  • All other alarms are available in all firmware versions.

Steps

  1. Go to Plant > Alarms/state configuration.

  2. Select the image-20241121-122248.png Filter next to the alarm type you want to filter.

  3. A window will appear. Enter the error or event code for the alarms you want to exclude. The relevant error or event codes can be found under Cockpit > Alarms/state > Error code.

Example of an undesired notification

Example of an undesired notification

Activate a filter for undesired notifications

Activate a filter for undesired notifications

Alarms and state types

Name

Details

Device communication

Activate the toggle to receive notifications about RS485 or TCP/Ethernet communication failures. 

Troubleshooting: Ensure that the device is working, there is a cable connection, and that the device’s communication interface is correctly configured and activated.

Device alarm

Activate the toggle to receive notifications of devices connected to the blue'Log, such as inverters and meters. 

Example (Sunspec alliance compatible inverter):

  • Event code: Inverter-Evt1-1 

  • Notification: DC over-voltage

Device state

Activate the toggle to receive notifications of states of devices connected to the blue'Log, for example inverters and meters. 

Example (Sunspec alliance compatible inverter):

  • Event code: Inverter-St-3

  • Notification: The device is starting up

Power control alarm

Activate the toggle to receive notifications of power control issues. Here is a list of power control alarms:

Power control alarms (select to exapand)
  • Setpoint value cannot be determined as cable breakage was detected

  • Actual value for measured value feedback is missing

  • Automatic grid disconnection tripped

  • Limited frequency sensitive mode - overfrequency (LFSM-O) activated because the actual system frequency is above the configured frequency threshold

  • Limited frequency sensitive mode - overfrequency (LFSM-U) activated because the actual system frequency is under the configured frequency threshold

  • At least one slave has failed to connect to master

  • At least one slave has lost the connection to master

  • Power control not supported

  • Start/Stop not supported

  • Setpoint value for active power control is missing

  • Setpoint value for reactive power control is missing

  • Fail-safe operation was activated, and a system fallback value is used as setpoint until a valid setpoint is received

  • Setpoint value cannot be determined as transmitter fault (overcurrent) was detected.

Note

To configure alarms/state for digital inputs, see Status DI internal and Status DI external.

Note

If a connected device sends excessive alarms or states, the system will automatically disable alarm and/or state notifications. You will receive one of the following notifications:

  • ALARM_DB_FULL: alarm database is full / the device alarming was deactivated

  • STATE_DB_FULL: state database is full / the device alarming was deactivated

  • POWER_CONTROL_ALARM_DB_FULL: database for power control alarms is full

VCOM USERS The Smart alarms feature in VCOM is an efficient means of handling unwanted alarms.

JavaScript errors detected

Please note, these errors can depend on your browser setup.

If this problem persists, please contact our support.