EsserSEI

Integration Manual
ESSERSEI – INTEGRATION MANUAL

Device Category
ACS IAS  FPS CCTV DVR Perimetry Building External Other

Supported Functionality
 Import From File  Combined Credentials
 Lift  Encrypted Communication
 Device Auto Import  Time Synchronization
 Time Zone Support  Live Video Streaming
 Recorded Video Streaming  Video Records Downloading
 Voice Transmitting  Audio Streaming
 PTZ  Presets
 Motion Detection  Live Stream Snapshot
 Recorded Stream Snapshot  Multiple Stream Types
 Fire Panel Networking Mode  Card Learning
 Dynamic Upload  Access Time Restriction
 Holidays Support  Pin Management
 Card Management  Fingerprint Management
 Reserved Memory Zones  Antipassback Forgiveness
 Handicapped Flag  Alarm Suppression
 Fire Alarm Counter  Device Audit Log Retrieval
 Remote Device Control  Dynamic Command State
 Wiegand Biometric Support
Legend:
 – Fully supported functionality.
 – Partially supported functionality, see results of integrations tests for more details.

Licensed Unit
Central Unit

Default Credentials
Key Value
empty

How to Connect Device to C4

Communication is made through the RS485 panel port 1 in connection with the RS485 to Ethernet converter.
When Events in Esser configuration are set as "technical event" in Column "Group Type", Esser is not propagating
these events to C4 driver.

2 / 38
ESSERSEI – INTEGRATION MANUAL

When you have more CUs connected, you have to send reset command on the CU that had the alarm, not any
CU.

Connecting Single IQ8 Control Through The Serial Essernet Interface (SEI)

The fire panel has to have a correctly configured extension communication module 784840 (EO 2). If the module
is on the panel mainboard, than the connection is as follows:
SEI essernet L1+ › IQ8 Micromodule 3
SEI essernet L1- › IQ8 Micromodule 4
SEI essernet L2+ › IQ8 Micromodule 1
SEI essernet L2- › IQ8 Micromodule 2
Also the power wires has to be connected:
IQ8 X2 +UBext › SEI UB+
IQ8 X2 GND › SEI GND
The SEI module is than connected to Ethernet converter:
SEI SIO2 TxD+ › converter RxD
SEI SIO2 RxD+ › converter TxD
SEI SIO2 GND › converter GND
When single panel is connected to SEI module the EMC jumpers are set:
SEI J3 EMC, J4 EMC, J5 no EMC, J6 no EMC
IQ8 X27 with filter, X28 with filter, X29 without filter, X30 without filter

Connecting Multiple IQ8 Control Throught The Serial Essernet Interface (SEI)

If the modules 784840 are on the panel mainboard, than the connection is as follows. If they are connected and
configured on extension board, the communication port on extension board has to be used according to the panel
manual.
SEI and panel are connected in circle (examle for two panels):
SEI essernet L1+ › 1.panel IQ8 Micromodule 3
SEI essernet L1- › 1.panel IQ8 Micromodule 4
1.panel IQ8 Micromodule 1 › 2.panel IQ8 Micromodule 3
1.panel IQ8 Micromodule 2 › 2.panel IQ8 Micromodule 4
2.panel IQ8 Micromodule 1 › SEI essernet L2+
2.panel IQ8 Micromodule 2 › SEI essernet L2-

Connecting Esser FlexES Panel

3 / 38
ESSERSEI – INTEGRATION MANUAL

Converter Serial Settings

communication type RS485 for Direct connection with FlexES

RS232 for Connection through external SEI module

speed 19200Bd

parity None

Worldlength 8

Stopbits 1

Device RS485 interface have to be configured to communicate with the external software: in the controller
module setting of the Tools 8000 application in Serial interface 1 set the 'Device to use' to 'Winmag'. When tools
are in Slovak language, set the 'Device to use' to 'Grafická nadstavba' and when in Czech language, set it to 'EDP
protokol' instead of 'Winmag'.

4 / 38
ESSERSEI – INTEGRATION MANUAL

Supported Configurations For Esser SEI + Flex

An example of supported configuration with single IQ8 Control panel:

The communication module SEI is connected to the panel and to an ethernet convertor Lantronix UDS 10.
The loop module 784382.10 B0.1 is connected to the module. Fire button (address 1, in area 1) and optical
detector (address 1, in area 2) are wired on the circular loop.

5 / 38
ESSERSEI – INTEGRATION MANUAL

An example of supported configuration with single FlexES Control panel: The panel is connected to an ethernet
convertor Lantronix UDS 10.
The loop module 784382.10 B0.1 is connected to the module. Fire button (address 1, in area 1) and optical
detector (address 1, in area 2) are wired on the circular loop.

An example of supported configuration with two IQ8 Control panels:

6 / 38
ESSERSEI – INTEGRATION MANUAL

Fire panels with address 2 and address 3 are connected to the SEI communication module and to each other. SEI
module is connected to the ethernet convertor Lantronix UDS 10.
Panel no. 2 has loop module 784382.10 B0.1 connected. To the circular loop are wired fire button (address 1, in
area 1) and optical detector (address 1, in area 2).
Panel no. 3 has loop module 784382.10 B0.1 connected too. To the circular loop are wired fire button (address 1,
in area 302) and optical detector (address 1, in area 301).
The delay time on panels is set to 10s, confirm time to 30s, prealarm to memory time on detector area is set to
10s .

Hardware Elements And Communication

Communication
Communication between C4 server and panels follows the Esser data protocol, revision 1.7.
After the expiration of a 5-second packet confirmation period, the packet is sent again. After 3 unsuccessful
attempts, a connection initialization attempt is repeated. Every packet that is successfully received is confirmed
by sending a confirmation packet (ACK).
Hardware configuratiom
To receive the prealarm events, the panels has to be configured to send prealarms to external software (in

7 / 38
ESSERSEI – INTEGRATION MANUAL

panel settings, functionality tab). To configure the prealarm on the detector, the detector area has to have
the working mode to alarm memory and set the prealarm time (detector area settings, properties tab).
To be able to switch the panel to T2 time, you have to set the times for alarm confirmation and delay (in
panel settings, times tab) and the detector area has to be set to delayed reaction (detector area settings,
activations tab)
To configure the area to activate alarm after multiple detectors are activated, the area has to be set to
MMA group mode and set the number of detectors that should be activated (detector area settings,
properties tab).

Supported Connected Devices

Device name Description Firmware

IQ8 Control-C Fire alarm panel 3.10.2

FlexES Control Fire alarm panel 1.03R002-EU

O-802371 optical smoke detector

804905 fire button

(EN 54-11 Type B)

8 / 38
ESSERSEI – INTEGRATION MANUAL

Configuration
BUS CONTROLLER
PROPERTY RANGE DEFAULT
Enabled Yes
Defines whether controller usage is enabled
Time zone System Time Zone
Device time zone
IP address
Device IP address
Port 1 - 65535 10001
Port defined on a device
Timeout for response from the device 00:00:05
Waiting time for a device response to the sent packet. After this time, the packet is sent again to the central
unit
Time Synchronization interval 01:00:00
Interval for synchronizing time between the server and central unit.
Network Monitoring Enabled Yes
Determines, whether the network monitoring is enabled.
SEIModule 1-2 1
The version of the used SEI module.

PANEL
PROPERTY RANGE DEFAULT
Address 1 - 32
Device address

SEI
PROPERTY RANGE DEFAULT
Address 1 - 32
Device address

FIRE GROUP
PROPERTY RANGE DEFAULT
Address 1 - 9999
Device address

OUTPUT
PROPERTY RANGE DEFAULT
Address 1 - 9999
Device address

9 / 38
ESSERSEI – INTEGRATION MANUAL

FIRE DETECTOR
PROPERTY RANGE DEFAULT
Address 1 - 32
Device address

Import From File

Driver supports the import of a device tree from a device configuration file in WINMAG format.
File extension - .txt
File data format - WINMAG

NOTE 1 - Bus Controller and Fire Alarm Panel nodes

Since the device configuration file does not contain any information about IP settings or unique fire alarm panel
identifier, the result of import is always 1 Bus Controller with 1 Fire Alarm Panel including all sub-devices
imported from the file.

NOTE 2 - Rewriting default values of device properties

Bus Controller is always imported with IP Address set to the default value 0.0.0.0. Please, re-write this value
using the real IP address after import.
Fire Alarm Panel is always imported with Address set to the default value 0. Please, re-write this value using the
real panel address after import.

NOTE 3 - Unique name of the device configuration file

To get file import working correctly, it is required to use the device configuration file with the unique name. This
provides, that two configurations of two different fire panels will be imported as two separate device trees.

NOTE 4 - Several fire panels under the one Bus Controller node
To get several fire panels under the one Bus Controller node, e.g. 2 fire panels, follow these steps:
1. Import the fire panel 1 configuration using the configuration file FirePanel_1.txt. The Bus Controller and
Fire Alarm Panel nodes are imported with FirePanel_1 name.
2. Set the real IP address on the Bus Controller node and the real address of fire panel 1 on the Fire Alarm
Panel node, e.g. 1.
3. Import the fire panel 2 configuration using the configuration file FirePanel_2.txt. The Bus Controller and
Fire Alarm Panel nodes are imported with FirePanel_2 name.
4. Set the real address of fire panel 2 on the Fire Alarm Panel node, e.g. 2.
5. Move Fire Alarm Panel node with FirePanel_2 name including all sub-devices under the Bus Controller node
with FirePanel_1 name. Change the Bus Controller's name to something more general, e.g. Lantronix UDS
10.
6. Delete the Bus Controller node with FirePanel_2 name.
7. The final device tree should know look like this:
Lantronix UDS 10 (Bus Controller)
FirePanel_1 (Fire Alarm Panel with Address 1)
All sub-devices

10 / 38
ESSERSEI – INTEGRATION MANUAL

FirePanel_2 (Fire Alarm Panel with Address 2)

All sub-devices

11 / 38
ESSERSEI – INTEGRATION MANUAL

Integration Tests
Test Name Result
Supported Functionality > Time Synchronization
T0FAFL Unified Time Management - Time Synchronization When Changed  Not supported
on Device
Comment: Not supported by communication protocol
T0FWIK Unified Time Management - Time Synchronization on Driver  Passed
Startup
T0FYDS Unified Time Management - Periodical Synchronization  Passed
Supported Functionality > Fire Panel Networking Mode
T04HHM Fire Panel - Networking Mode  Passed
Supported Functionality > Alarm Suppression
T03MTG Alarm Suppression - Intrusion  Not supported
Comment: Test not relevant for FPS driver category
T04BUV Alarm Suppression - Fire  Passed
Supported Functionality > Remote Device Control
T04XSI Output Inhibit and Uninhibit Remotely From C4  Passed
T08ARF Door Lock and Unlock  Not supported
Comment: Test not relevant for FPS driver category
T08LON Door Remote Open  Not supported
Comment: Test not relevant for FPS driver category
Device Category > FPS
T04AAR Fire Prealarm  Passed
T04DWS Fire Alarm  Passed
T04FIP Fire Panel - Mute Sounder  Passed
T04HRA Output Inhibit and Uninhibit from Device  Passed
T04JQW Fire Alarm Counter  Not supported
Comment: Not supported by communication protocol
T04NLX Fire Panel - Mute Buzzer  Passed
T04TFK Fire Panel - Controlling Key Events  Passed
T07BGC Detector Inhibit and Uninhibit Remotely from C4  Passed
T07QHA Detector Inhibit and Uninhibit from Device  Passed
T07XJB Failure While in Test on Detector  Passed
T07ZJY Alarm While in Test on Detector  Passed
T07ZOS Detector Failure  Passed
T08AGY Import the device tree for Fire Panel  Supported, cannot verify
T08FPR Fire Panel Reset from Device  Passed
T08FRR Fire Panel Reset Remotely From C4  Passed
T0FCVB Contact Monitoring from Device  Not supported
Comment: Not supported by communication protocol
T0FLFU Activating Test Mode on Detector from Device  Passed
T0FQCA Mains Failure  Passed
T0FVUH Activating Test Mode on Detector Remotely from C4  Passed
T0FYGI Battery Failure  Passed
T2FESO Device Audit Log Retrieval  Not supported
Comment: Not supported by communication protocol
T3FIGI Output Activation and Deactivation  Not supported
Comment: Not supported by device
T7FHSW Missing HW Item  Passed
12 / 38
ESSERSEI – INTEGRATION MANUAL

Appendix A
Integration Tests

13 / 38
ESSERSEI – INTEGRATION MANUAL

T04AAR - Fire Prealarm

This test verifies behavior of the driver when processing events about the fire prealarms in Fire alarm
systems or other systems with similar functionality.

Test Steps
Prepare the panel to support the prealarms
Activate first detector
Wait until prealarm is signaled in C4
After silencing the detector, but before expiration of T1 time, execute command “Reset” on the panel
Reactivate detector
When the prealarm is signaled, execute the command to switch to T2 time
After T2 time expiration the fire alarm is issued
Execute command "Reset" on the panel

Expected Results
Activated detector has status set to “Alarm”

Following events are stored in audit log:

Fire precondition 'DEVICE'.
'DEVICE' fire precondition ended.
'DEVICE1' reversed settings.
Fire precondition 'DEVICE'.
'DEVICE1' - switch to T2.
Fire alarm on 'DEVICE'.
Fire alarm on 'DEVICE' finished.
'DEVICE1' reversed settings.

Where

DEVICE represents the name of detector where fire prealarm or alarm is detected
DEVICE1 represents the name of fire panel.

Notes:
This test shows how the driver handles prealarms, therefore even when the steps to activate prealarms on
the device might differ, the test is considered as passed as long as it can distinguish between Fire alarm
event and Fire precondition event and log them in correct situations. When test steps are different than
these presented here, they must be described in test notes.

14 / 38
ESSERSEI – INTEGRATION MANUAL

15 / 38
ESSERSEI – INTEGRATION MANUAL

T04BUV - Alarm Suppression - Fire

To simplify alarm management procedures, driver can be notified about the client alarm handling procedure and
take respective actions, related to the current state of the alarm handling.

Test Steps
Issue an alarm on detector
In Monitor Panel, Accept the alarm
Restore the alarm on detector
In Monitor Panel, Resolve the alarm

Expected Results
After accepting of the alarm from the Monitor panel, device buzzer is silenced. Device and the group
where the device is linked have alarm status. Output/outputs have open status.
After alarm is resolved the panel is reseted. Device and the group where the device is linked have
equal status to real status of device. Output/outputs have equal status to real status of devices.

Following events are stored in audit log:

Fire alarm on 'DEVICE'
Buzzer on 'DEVICE1' muted.
Alarm restored on 'DEVICE'
'DEVICE1' reversed settings.

Where

DEVICE represents the name of device where fire alarm occurred

DEVICE1 represents the name of Fire panel

16 / 38
ESSERSEI – INTEGRATION MANUAL

T04DWS - Fire Alarm

This test verifies behavior of the driver for Fire alarm devices, or devices with similar functionality.

Test Steps
Issue an alarm on detector.
Restore the alarm on detector.

Expected Results
The detector status and possibly the states of areas or zones is set to Alarm.
After the alarm confirmation the Alarm state is finished.

Following events are stored in audit log:

Fire alarm on 'DEVICE'.
Alarm restored on 'DEVICE'.

Where

DEVICE represents a name of detector where the alarm was generated

PERSON represents a name of person who confirmed the alarm

Notes:
Preferred way to confirm an alarm is to handle it through the Alarm Window in the monitor panel.
When the Alarm module is not available, then user shall use Reset command on the detector in alarm.
On some devices this is not possible and it is necessary to issue another sequence of commands to
confirm the alarm (for instance disarming the area on Alarm systems). If the sequence can be issued
from the C4 UI and resembles the sequence of operations done on the device keypad, this test is
considered as passed.
In C4 alarm events are stored always for device that is “nearest” to the real alarm source. This is
usually detector. In case the device or its protocol doesn’t provide the information with that precision,
for example provides only information about the alarmed area, the test can be considered as passed
with remark in test notes.​

17 / 38
ESSERSEI – INTEGRATION MANUAL

T04FIP - Fire Panel - Mute Sounder

This test verifies behavior of the sounder controlling on Fire alarm panels. This test applies to Fire Alarm
Systems or systems with similar functionality.

Test Steps
Execute command “Mute Sounder” on panel

Expected Results
Sounder on panel is muted.

Following events are stored in audit log:

'PERSON' sent command 'Mute Sounder' to 'DEVICE'.
Sounder on 'DEVICE' muted.

Where

DEVICE represents the fire panel name

PERSON represents a name of person who executed the command

Notes:
Devices that doesn’t support independent mute for buzzer and sounder the test is passed if one of
the commands is supported.

18 / 38
ESSERSEI – INTEGRATION MANUAL

T04HHM - Fire Panel - Networking Mode

This test verifies behavior of the driver when device has a networking mode, when there are multiple panels
connected to the endpoint. They usually share a single networking (in an IP sense) node.

Test Steps
This test is considered as passed, when you can reproduce all other relevant tests in a networking mode. All
deviations in network mode must be specified directly in integration manual’s test notes. (For instance, when
the time setting doesn’t work in networking mode, it is expected that the time setting test notes mention this
limit and the same note appears in this test notes for easier reference).

Notes:
Typical example is a set of fire alarms with connected annunciators

19 / 38
ESSERSEI – INTEGRATION MANUAL

T04HRA - Output Inhibit and Uninhibit from

Device
This test verifies behavior of the driver implementation for output contact inhibit support. This test is applied to
Fire alarm systems or systems with similar functionality.

Test Steps
Inhibit output using keypad or device panel
Cancel the inhibit using keypad or device panel

Expected Results
State of the output is Idle when not inhibited and Inhibit when output is inhibited

Following events are stored in audit log:

Inhibit 'DEVICE' by user 'PERSON'.
Uninhibit 'DEVICE' by user 'PERSON'.

Where

DEVICE represents the output name

PERSON represents the name of person who executed the commands on device

Notes:
For systems where input and output contact functionality is separated, the test is repeated for both of
them to pass.

20 / 38
ESSERSEI – INTEGRATION MANUAL

T04NLX - Fire Panel - Mute Buzzer

This test verifies behavior of the buzzer controlling on Fire alarm panels. This test applies to Fire Alarm
Systems or systems with similar functionality.

Test Steps
Execute command “Mute Buzzer” on panel

Expected Results
Buzzer on panel is muted.

Following events are stored in audit log:

'PERSON' sent command 'Mute Buzzer' to 'DEVICE'.
Buzzer on 'DEVICE' muted.

Where

DEVICE represents the fire panel name

PERSON represents a name of person who executed the command

Notes:
Devices that doesn’t support independent mute for buzzer and sounder the test is passed if one of
the commands is supported.

21 / 38
ESSERSEI – INTEGRATION MANUAL

T04TFK - Fire Panel - Controlling Key Events

This test verifies behavior of the controlling key events handling. This test applies to Fire Alarm Systems or
systems with similar functionality.

Test Steps
Insert controlling key to the panels slot and turn it.
When there are more possible positions, go through all of them
Return the controlling key back to the locked position and remove it

Expected Results

Following events are stored in audit log:

Key turned to On position on 'DEVICE'.
Key turned on 'DEVICE'.
Key turned to Off position on 'DEVICE'.

Where

DEVICE represents the fire panel name

Notes:
When device has only two possible key positions, events are logged only for turning the key to On,
Off position. If the device has more that two positions events are logged according to that positions of
key.

22 / 38
ESSERSEI – INTEGRATION MANUAL

T04XSI - Output Inhibit and Uninhibit Remotely

From C4
This test verifies behavior of the driver implementation for output contact inhibit support. This test is applied to
Fire alarm systems or systems with similar functionality.

Test Steps
Execute command “Inhibit” on output.
Execute command “Uninhibit” on output.

Expected Results
State of the output is Idle when not inhibited and Inhibit when output is inhibited

Following events are stored in audit log:

'PERSON' send command 'Inhibit' to 'DEVICE'.
Inhibit 'DEVICE' by user 'PERSON'.
'PERSON' send command 'Uninhibit' to 'DEVICE'.
Uninhibit 'DEVICE' by user 'PERSON'.

Where

DEVICE represents the output name

PERSON represents the name of person who executed the commands in C4

23 / 38
ESSERSEI – INTEGRATION MANUAL

T07BGC - Detector Inhibit and Uninhibit

Remotely from C4
This test verifies behavior of the driver implementation for detector inhibit support. This test is applied to Alarm
systems and Fire alarm systems or systems with similar functionality. In Fire alarm systems it is usually
known as detector disable.

Test Steps
Execute command “Inhibit” on detector.
Execute command “Uninhibit” on detector

Expected Results
1.State of the detector is Idle when not inhibited and Inhibit when detector is inhibited

Following events are stored in audit log:

'PERSON' send command 'Inhibit' to 'DEVICE'.
Inhibit 'DEVICE' by user 'PERSON'.
'PERSON' send command 'Uninhibit' to 'DEVICE'.
Uninhibit 'DEVICE' by user 'PERSON'.

Where

DEVICE represents the detector name

PERSON represents the name of person who executed the command from C4

Notes:
For Fire alarm systems it is considered as acceptable when the zone/area is automatically inhibited
when all detectors in the zone/area are inhibited.

24 / 38
ESSERSEI – INTEGRATION MANUAL

T07QHA - Detector Inhibit and Uninhibit from

Device
This test verifies behavior of the driver implementation for detector inhibit support. This test is applied to Alarm
systems and Fire alarm systems or systems with similar functionality. In Fire alarm systems it is usually
considered as detector disable.

Test Steps
Inhibit the detector using keypad or device panel.
Cancel the inhibit using keypad or device panel

Expected Results
1.State of the detector is Idle when not inhibited and Inhibit when detector is inhibited

Following events are stored in audit log:

Inhibit 'DEVICE' by user 'PERSON'.
Uninhibit 'DEVICE' by user 'PERSON'.

Where

DEVICE represents the detector name

PERSON represents the name of person who executed the command from device

Notes:
For Fire alarm systems it is considered as acceptable when the zone/area is automatically inhibited
when all detectors in the zone/area are inhibited.

25 / 38
ESSERSEI – INTEGRATION MANUAL

T07XJB - Failure While in Test on Detector

This test verifies behavior of the driver implementation for test mode support. This test is focused specifically to
check the handling failure on detector while in test.

This test applies to Alarm systems, Access systems and Fire systems with support of Test mode on detectors
or areas.

Test Steps
Start the Test mode on detector
Connect broken detector to the system, or by other way force the system to report the detector failure
Recover the failure

Expected Results
Detector status is set to Test when the test mode is activated.
Detector status is set to Test + Failure when system reports the detector failure.
After finishing the failure on detector, its status is returned to the real status.

Following events are stored in audit log:

Failure on 'DEVICE' in test mode.
Recovery of normal state on 'DEVICE' in test mode.

Where

DEVICE represents the detector/area name where the failure happened

26 / 38
ESSERSEI – INTEGRATION MANUAL

T07ZJY - Alarm While in Test on Detector

This test verifies behavior of the driver implementation for test mode support. This test is focused specifically to
check the handling of alarm on detector while in test.

This test applies to Alarm systems, Access systems and Fire systems with support of Test mode on detectors
or areas.

Test Steps
Start the Test mode on detector
Issue an alarm on detector

Expected Results
Detector status is set to Test when the test mode is activated
Detector status is set to Test + Alarm when Alarm is activated

Following events are stored in audit log:

Alarm on 'DEVICE' in test mode.

Where

DEVICE represents the detector/area name

27 / 38
ESSERSEI – INTEGRATION MANUAL

T07ZOS - Detector Failure

This test verifies behavior of the driver and handling of the events from device in case of detector failure.

Test Steps
Connect broken detector to the system, or by other way force the system to report the detector failure
Recover the failure

Expected Results
1.Detector status is Failure

Following events are stored in audit log:

'DEVICE' failure.
Failure on 'DEVICE' restored. Description: 'DESCR'.
Where
DEVICE represents the detector where the failure occurred.
DESCR is optional, untranslated, failure description.

Notes:
This test applies for technologies with fire detection features only.

28 / 38
ESSERSEI – INTEGRATION MANUAL

T08AGY - Import the device tree for Fire Panel

This test verifies behavior of the driver when importing device tree from supported file type for Fire devices.

Test Steps
Open the import wizard.
Find the file you want to import.
Import Device tree from file.

Expected Results
When you are looking for file you want to import in file types you can see supported file types for
import.
Device tree is successfully imported from file.

29 / 38
ESSERSEI – INTEGRATION MANUAL

T08FPR - Fire Panel Reset from Device

This test verifies behavior of the driver implementation of Reset command from Fire panels.

This test applies to Fire alarm systems.

Test Steps
Issue an alarm on detector.
Restore the alarm on detector.
Use Reset button on fire panel.

Expected Results
The detector status and possibly the states of area or zone is set to Alarm.
After using Reset button alarm state on detector and possibly on area is restored.

Following events are stored in audit log:

'DEVICE' reversed settings.

Where

DEVICE represents the fire panel name.

30 / 38
ESSERSEI – INTEGRATION MANUAL

T08FRR - Fire Panel Reset Remotely From C4

This test verifies behavior of the driver implementation of Reset command for Fire panels remotely from
C4.
This test applies to Fire alarm systems.

Test Steps
Issue an alarm on detector.
Restore the alarm on detector.
Execute command 'Reset' on fire panel.

Expected Results
The detector status and possibly the states of area or zone is set to Alarm.
After executing Reset command alarm state on detector and possibly on area is restored.

Following events are stored in audit log:

'PERSON' sent command 'Reset' to 'DEVICE'.
'DEVICE' reversed settings.

Where

DEVICE represents the fire panel name

PERSON represents the name of person who executed the command from C4

31 / 38
ESSERSEI – INTEGRATION MANUAL

T0FLFU - Activating Test Mode on Detector from

Device
This test verifies behavior of the driver implementation for test mode support. This requires to correctly logging
appropriate events, setting the devices to correct state. This test applies to Alarm systems, Access systems
and Fire systems with support of Test mode on detectors or areas.

Test Steps
Start the test mode on detector using the device keypad or panel
Finish the test mode on detector using the device keypad or panel

Expected Results
1.Detector status is set to Test when the test mode is activated.

2.Detector status is set to Normal when the test mode is finished.

Following events are stored in audit log:

'DEVICE' is Tested.
Test finished on 'DEVICE'.

Where

DEVICE represents the detector name

Notes:
For Fire alarm systems it is considered as acceptable when the detector is automatically set to test
mode when all detectors in the detector are in test mode.

32 / 38
ESSERSEI – INTEGRATION MANUAL

T0FQCA - Mains Failure

This test verifies behavior of the driver in case of mains failure of the device that is backed up by battery or other
additional power source.

Test Steps
Disconnect the mains power
Wait until the disconnection is signalled
Reconnect mains power
Wait until the reconnection is signalled.

Expected Results
When mains power is disconnected device status is set to Fault state
After mains power is reconnected device status is set to real status of device.

Following events are stored in audit log:

'DEVICE' mains failed.
Restore 'DEVICE' after a mains failure.

Where

DEVICE represents the device where the power failure was detected.

Notes:
Test must be replicable on all types of devices that have independent powering and are backed up by
battery or another power source

33 / 38
ESSERSEI – INTEGRATION MANUAL

T0FVUH - Activating Test Mode on Detector

Remotely from C4
This test verifies behavior of the driver implementation for test mode support. This requires to correctly logging
appropriate events, setting the devices to correct state and possibility to set the state from starting the Test
mode from C4 UI. This test applies to Alarm systems, Access systems and Fire systems with support of Test
mode on detectors or areas.

Test Steps
Execute command “Test” on detector.
Execute command “Test Finish” on detector.

Expected Results
1.Detector status is set to Test when the test mode is activated.

2.Detector status is set to Normal when the test mode is finished.

Following events are stored in audit log:

'PERSON' send command 'Test' to 'DEVICE'.
'DEVICE' is tested.
'PERSON' send command 'Finish Test' to 'DEVICE'.
Testing of 'DEVICE' finished.

Where

DEVICE represents the detector name

PERSON represents the name of person who executed the commands

Notes:
For Fire alarm systems it is considered as acceptable when the detector is automatically set to test
mode when all detectors in the detector are in test mode.

34 / 38
ESSERSEI – INTEGRATION MANUAL

T0FWIK - Unified Time Management - Time

Synchronization on Driver Startup
This test verifies correct implementation of the unified time management in driver. Driver is required to set up
the time on the device after the communication is established.

Test Steps
Set the device time 60 min back.
Start the endpoint
Wait until driver is fully started
Check the time on device

Expected Results
Device time is synchronized with C4 server current time.

Following events are stored in audit log:

Time set to 'DEVICE'. Offset with real time was '60' minutes
Where
DEVICE represents the name of the device
OFFSET is an absolute value of the time difference in minutes. Here it is expected to have value 59-
61,depending on the exact timing and measurement precision

Notes:
Event is stored only when the time difference is greater than 5 minutes
When the device has its own NTP server (or similar facility) and the driver itself does not set the time on the
device, this test is considered not supported. Option of using NTP server to synchronize time should be stated in
the integration manual
Test is considered as passed also in case the event is not logged due to impossibility to retrieve device time

35 / 38
ESSERSEI – INTEGRATION MANUAL

T0FYDS - Unified Time Management - Periodical

Synchronization
This test verifies correct implementation of the unified time management in driver. Driver is required to keep the
device time synchronous with C4 server time.
This test can be executed only on the devices that do not support the time change notification, as this feature
collides with test execution.

Test Steps
Set the value of property Time Synchronization Interval to 5 minutes.
Start the endpoint
Set the device time 60 min back
Wait 5 minutes
Check the time on device

Expected Results
Device time is synchronized with C4 server current time

Following events are stored in audit log:

Time set to 'DEVICE'. Offset with real time was 'OFFSET' minutes
Where
DEVICE represents the name of the device
OFFSET is an absolute value of the time difference in minutes. Here it is expected to have value 59-
61,depending on the exact timing and measurement precision

Notes:
Event is stored only when the time difference is greater than 5 minutes
Test is considered as passed also in case the event is not logged due to impossibility to retrieve device time

36 / 38
ESSERSEI – INTEGRATION MANUAL

T0FYGI - Battery Failure

This test verifies behavior of the driver event handling in case of battery or other backup power fault.

Test Steps
Disconnect the backup power
Wait until the disconnection is signalled
Reconnect the backup power
Wait until the reconnection is signalled

Expected Results
When backup power is disconnected device status is set to Fault state
After backup power is reconnected device status is set to real status of device.

Following events are stored in audit log:

'DEVICE' – low battery.
'DEVICE' – low battery restored.

Where

DEVICE represents the device where the power failure was detected.

Notes:
Test must be replicable on all types of devices that have independent power and are backed up by
battery or another power source.

37 / 38
ESSERSEI – INTEGRATION MANUAL

T7FHSW - Missing HW Item

This test verifies behaviour of the driver in case the device configuration tree is incomplete. In that situation the
driver must, whenever it receives an event from device, log the missing Device event on the nearest parent node
of the device configuration or the driver node itself.

Test Steps
Stop the endpoint
Create an incomplete configuration tree with missing device.
Start the endpoint.
Generate some activity on the missing device.

Expected Results
Endpoint continues to work.

Following events are stored in audit log:

Configuration failure 'PARENTDEVICE': Missing device of category 'DEVICETYPE' with addre
ss: 'ADDRESS'. Detail: 'EVENT_DESCRIPTION'

Where

PARENTDEVICE represents the expected nearest parent device or the highest driver node.
DEVICETYPE represents the probable type of missing device.
ADDRESS represents the address/identifier of the missing device.
EVENT_DESCRIPTION represents untranslated text from the driver that should describe the event
that appear in the audit log in case of correct device tree configuration - for example "AC -
AreaAccessedEvent".

Notes:
Test must be repeatable on each node type that can be created in a tree and that can be removed
from device tree configuration without harming the core functionality (e.g. it doesn’t make sense to
remove the driver node itself or panel node when only one panel is allowed in configuration, but it’s
perfectly valid for detectors, contacts etc).

38 / 38