Datasheet

User’s guide · RCM 310
- 14 - RCM 310 version_en_1.0 FTE maximal
Chapter 4. Alarms and actions
One of the main features of RCM 3140 is the capacity of continually monitoring the status and output level of the devices
that are connected to the DVBUS, as well as the level of the external RF signals.
The system allows setting alarm status, which once activated will generate several actions, and once deactivated will
generate other different actions.
An alarm can be created by configuring a series of events that must take place in order to get the alarm activated. When
the configured requirements take place, the alarm gets activated. The actions that have to happen so the alarm gets
activated are defined in the alarm configuration. Once the necessary events in order to get the alarm activated disappear,
the alarm is deactivated. The actions that should take place when the alarm gets deactivated are defined in the alarm
configuration too.
Note: The alarm status does not get stored, therefore when the system is rebooted, if there was any active
alarm it will be removed.
4.1. Definition of system monitoring cycle
The RCM 310 is checking the status of the devices that are connected to the DVBUS all the time. This monitoring is
made in a sequential way. The more modules are connected to the DVBUS, the more time the cycle will take. The cycle
can last around one second for less than 6 connected devices, and several seconds when the total of 72 devices are
connected.
In the monitoring cycle are included the external RF signals and SMS reception too.
The digital inputs are asynchronously monitored (they are treated immediately instead of waiting until the end of the
monitoring cycle).
Alarm list
In order to move to the alarm list you have to go to the “Alarm” page situated in the upper tabs of any page of the
RCM310.
In the system you can define as many alarms as you wish. The alarms are treated depending on priorities; the most urgent
one is placed at the top of the list and the less one at the bottom.