FAQ
– CMC III
Page
11
of
24
appear there. To log on, first close the window. Then right-click on the list of messages at the
bottom of the Web interface or on the list of sensors on the left, and select the action
"Acknowledge Devices" or "Acknowledge All Devices". Alternatively, keep the "C" button on
the front of the CMC III PU held down for 3 seconds. The sensor will then be logged on and
alarm configuration can be carried out.
What is the difference between a "virtual device" and a "task"?
A "virtual device" is a virtual sensor that performs a specific action depending on its category.
For example, whereas a "two-level controller" switches an output depending on an input
value, an "access controller" switches an output that will then be recognised as a handle so it
can be triggered with a reader system. A virtual device can also be queried using SNMP and
OPC-UA. A virtual device, however, only performs one fixed action and there is only a single
input variable used for control. This is also independent of the status
("OK"/"warning"/"alarm") of the associated sensor.
In contrast, many different input values can be linked with a task that can also perform
various actions. This means defined states can use logical links to trigger an action over
several sensors. A task then regulates the sensors ("OK"/"warning"/"alarm") depending on
the associated states and can also be linked with a time period. Not only the switching of an
output, but also other actions, such as the sending of an e-mail or the suppression of an
alarm, can be triggered as action. Consequently, although a task is much more flexible than
a virtual device, it cannot be queried by SNMP and the system is limited to 16 tasks.
How many messages can the CMC III store in the logging?
A permanently defined area in the system memory of 1 MB is reserved for logging
messages. This area consists of two blocks each of 500 kB. The system first writes one such
block full and then begins with the second block. If the second block becomes full with
messages, the first (and oldest block) will be deleted. The number of messages depends on
the length of the individual logging lines. As a guideline, you can expect at least 5,000
logging entries to be accommodated.
If you want these logging entries to be permanently saved, they must be copied at regular
intervals onto an external server via FTP or SFTP. Alternatively, the CMC III also supports
the Syslog protocol, whereby logging messages can be sent automatically to an external
Syslog server as soon as they occur.
Can the logging messages be deleted?
No, the complete deletion of the logging messages is not possible. Although, on the website,
the list of the messages can be filtered and the current display deleted, the messages
themselves are retained on the system. The log files can also only be downloaded but not
deleted by FTP or SFTP.
Can a system configuration be saved and recreated on another device?
From software version V3.11.00 and above, both the configuration of the sensors and the
general configuration of a CMC III system may be saved and recreated. However, please
note that the sensor configuration in both the original system and the new system into which
the configuration is being copied must have exactly the same sequence (same index for a
sensor type in the sensor list on the left-hand side of the Web interface). If not, the system
