Verex/SNAPP: Integration Manual

Verex/SNAPP
Integration Manual
VEREX/SNAPP – 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.
Supported Card Segments

Facility Issue  Number
Supported Pin Lengths

 4 5 6 7 8
Licensed Unit
ACCESS PANEL
DOOR MODULE
POINT EXPANSION MODULE
2 / 37
Default Credentials
Key Value
MANAGER (001) 7793
How to Connect Device to C4
Before programming the IP interface module, obtain the following information from the Network Administrator:
The static IP address for the IP interface module (only if static IP address is going to be used)
The subnet mask for the IP interface module (only if static IP address is going to be used)
The gateway IP address
Step 1 - Configure the central unit to allow 3rd party connections

Activate the control unit's tamper to allow system programming for the service user.
Logon to the system as a service user. Default ID: 00 or 000. Service user PIN: 2482 or 7378 if the panel
has communicated with the Director software. Confirm logon with second user password (master user) if
requested. If the feature set is 5 or greater, keypad programming cannot be done.
Using the left and right keys on the keypad scroll the menus until Config is displayed.
Press OK. Config method will display.
Select Advanced option and press OK.
Go to program section S001 and subsection 02.
Set the panel unique ID (needed for communication with Director software)
Set the 3rd party password needed for communication with Director software and also with C4 system.
3 / 37
Write down the Main control board address as it will be needed when adding central unit into C4 Devices
tree.
Step 2 - Connect the IP interface to the Control Panel

Assemble the IP receiver module to the cabinet
With both AC and battery disconnected from the control panel, wire the IP receiver to the panel using the
supplied cable
COLOR OF THE WIRE FROM IP INTERFACE TERMINAL PIN ON THE CONTROL PANEL
Black 0V
Red 12 V
Green A485
Yellow B485
Other wires Not used
Step 3 - Programming the IP receiver (only SNAPP protocol)

Power up the central unit with the IP receiver
Using the IP Interface module configuration program (available on Verex Director installation media) set
the IP receiver's IP address, subnet mask and gateway. Follow the instructions described in the IP
connectivity guide provided with the IP receiver module.
In the configuration program go to the ISM tab and check the Local Port value. This value has to be entered
in C4 Devices tree on Bus controller.
Disconnect the configuration program from the central unit.
The device is now ready to accept 3rd party connections via IP receiver.
Step 4 - Programming the IP receiver (encrypted communication -

SABER protocol)
Power up the central unit with the IP receiver
Using the SABER2 Module Configuration (IP Module v4) program (available on Verex Director installation
media) set the IP receiver's IP address, subnet mask and gateway. Follow the instructions described in the
IP connectivity guide provided with the IP receiver module.
In the configuration program go to Director tab and set Listen and Director Port to 443. Director URL to IP
address of C4 server. Check Ignore validation certificate.
Send settings to central unit.
Disconnect the configuration program from the central unit.
The device is now ready to accept 3rd party connections via IP receiver.
Explicit User positions assignment

For assign explicit position to desired user, follow this steps and prerequisites:
4 / 37
Create special Credential type as 'Positional card' by enabling just Card number segment with length of 20
bits.
Set Manual User Starting Position to value between Minimum Allowed User Number and Maximum
Allowed User Number.
Assign 'Positional card' with Card number between Manual User Starting Position and Maximum
Allowed User Number to person, which you want explicit define position.
This 'Positional card' code determines user ID for arming. PIN credential and/or Access Card credential
must be create separately.
Extended PIN is not supported credential at all.
At this version driver supports one PIN credential, one Access Card and one 'Positional Card' per
person.
Upload changes to device.
For disable explicit positions assignment set Manual User Starting Position to value of Maximum Allowed
User Number.
5 / 37
Configuration
BUS CONTROLLER
PROPERTY RANGE DEFAULT
Network Monitoring Enabled YES/NO YES
Determines, whether the network monitoring is enabled.
Encryption Enabled YES/NO NO
Determines, whether the Saber encrypted communication is enabled.
IP Address
IP address of supported Verex/SNAPP IP Module.
Port 1 - 65535 24822
Defines a UDP (or TCP when encrypted communication is enabled) port for receiving data from Verex/SNAPP.
Receiving Port 1 - 65535
Defines port that receives data from <% txtApplicationName %> server. Property is used, when encrypted
communication is disabled.
Different Receiving Port YES/NO NO
Enables receiving information from another port, apart from the preset port. Property is used, when encrypted
communication is disabled.
CENTRAL UNIT
6 / 37

Address 0 - 65535
Central unit serial number.
Persons Management ENABLED/DISABLED ENABLED
Determines, whether the credential management is enabled.
Setting Time Interval 01:00:00
Interval for time synchronization between <% txtApplicationName %> server and the panel.
Password 9-DIGIT DECIMAL
Communication password (3rd party password).
Timeout for Response From The Device 00:00:05
Defines time, the <% txtApplicationName %> server waits for response from device.
Manual User Starting Position 2
Defines, at which position starts manual user positions management. Positions between this property and
Maximum Allowed User Number value are managed explicitly by assigning 'Positional card' to Person in <%
txtApplicationName %>. Value of this property, same as Maximum Allowed User Number, means full range of
device memory is managed automatically.
Minimum Allowed User Number 2
Minimum 'User' position in managed device memory. Property is used, when Full Memory Management is
disabled.
Maximum Allowed User Number 64000
Maximum 'User' position in managed device memory. Property is used, when Full Memory Management is
disabled.
Minimum Allowed Access Level Number 2
Minimum 'Access Level' position in managed device memory. Property is used, when Full Memory
Management is disabled.
Maximum Allowed Access Level Number 1000
Maximum 'Access Level' position in managed device memory. Property is used, when Full Memory
Management is disabled.
Minimum Allowed Profile Number 2
Minimum 'Profile' position in managed device memory. Property is used, when Full Memory Management is
disabled.
Maximum Allowed Profile Number 1000
Maximum 'Profile' position in managed device memory. Property is used, when Full Memory Management is
disabled.
Minimum Allowed Time Restriction Number 1
Minimum 'Schedule' position in managed device memory. Property is used, when Full Memory Management is
disabled.
Maximum Allowed Time Restriction Number 250
Maximum 'Schedule' position in managed device memory. Property is used, when Full Memory Management is
disabled.
PARTITION
Address 1 - 16
Partition address.
DETECTOR
Address 1 - 256
Detector address.
7 / 37
INPUT
Address 1 - 256
Input address.
OUTPUT
Address 1 - 128
Output address.
DOOR MODULE
Address 0 - 65535
Door module serial number.
DOOR
Address 1 - 32
Door address.
CARD READER
Reader Direction MOVEMENT DIRECTION NONE
Movement direction of the reader
CARD READER WITH KEYPAD

Reader Direction MOVEMENT DIRECTION NONE
Movement direction of the reader.
POINT EXPANSION MODULE

Address 0 - 65535
Point expansion module serial number.
KEYPAD MODULE
Address 0 - 65535
Keypad module serial number.
8 / 37
SUITE CARD READER WITH KEYPAD

Address 0 - 65535
Suite serial number.
SUITE DETECTOR
Address 1-8
Suite detector address.
SUITE INPUT
Address 1-8
Suite input address.
SUITE OUTPUT
Address 1-2
Suite output address.
Extended Properties
9 / 37

User Level FLAGS SELECTION STANDARD USER
Defines, which set of functions for user are enabled.
Accept Duress PIN YES/NO NO
Defines if Access Duress PIN option is enabled.
Silence Alarm YES/NO NO
Defines if option Silence Alarm is enabled.
Status YES/NO NO
Defines if option Status is enabled
History YES/NO NO
Defines if option History is enabled
Service Test YES/NO NO
Defines if option Service Test is enabled
Test YES/NO NO
Defines if option Test is enabled
Function-Key Authorization YES/NO NO
Defines if Function-Key Authorization option is enabled
Work Late YES/NO NO
Defines if option Work Late is enabled
Bypass YES/NO NO
Defines if option Bypass is enabled
Auto-Remove Bypass YES/NO NO
Defines if Auto-Remove Bypass option is enabled
Suspend Schedule YES/NO NO
Defines if option Suspend Schedule is enabled.
Emergency Off YES/NO NO
Defines if option Emergency Off is enabled
Isolate a trouble point YES/NO NO
Defines if option Isolate a trouble point is enabled
Master Override YES/NO NO
Defines if option Master Override is enabled
Escort YES/NO NO
Defines if option Escort is enabled
Visitor YES/NO NO
Defines if option Visitor is enabled
Wandering patient YES/NO NO
Defines if option Wandering patient is enabled
Reset door alarm YES/NO NO
Defines if option Reset door alarm is enabled
Panic Token YES/NO NO
Defines if option Panic Token is enabled
Language LANGUAGE English
Defines, which language to use
Access On YES/NO YES
Defines, if option to allow a person into an area when it's fully armed is enabled
Access Off YES/NO YES
Defines if option to allow a person into an area when it's disarmed is enabled
Access Stay YES/NO YES
Defines if option to allow a person into an area when it's armed is enabled
10 / 37
Defined Enumerations
FLAGS SELECTION
Used by Extended Properties > User Level.
Value Description
Limited User Accept Duress PIN, Status, On
Standard User Limited User, Silence Alarm, Work Late, Off, Stay, Door Commands
Advanced User Standard User, History, Test Function Key, Bypass Points, Auto Remove
Bypass, Suspend Schedule, Emergency Off, Isolate, Escort, Reset Door
Alarm, Off Not Stay, Auto All Off
Register Only Limited User, History
Detailed Configuration User can select detailed options
LANGUAGE
Used by Extended Properties > Language.
Value Description
English English language
Dutch Dutch language
French French language
Spanish Spanish language
MOVEMENT DIRECTION
Used by CARD READER > Reader Direction.
Used by CARD READER WITH KEYPAD > Reader Direction.
Value Description
In Movement direction is from inside to outside.
Out Movement direction is from outside to inside.
None Movement direction is undefined.
Test Notes
TEST NOTE
T08ARF: Door Lock and Test is considerable as passed if master card/PIN opens the door during Door
Unlock lockout phase.
11 / 37
Integration Tests
Test Name Result
Supported Functionality > Device Auto Import
T7FKUJ Device Auto import  Passed
Comment: Not supported by design.
Supported Functionality > Time Synchronization
T0FAFL Unified Time Management - Time Synchronization When  Not supported
Changed on Device
Comment: Keypad does not have set time command.
T0FWIK Unified Time Management - Time Synchronization on Driver  Supported, cannot verify
Startup
T0FYDS Unified Time Management - Periodical Synchronization  Not supported
Comment: Keypad does not have set time command.
Supported Functionality > Card Learning
T09UVU Personal Management - Card Learning  Supported, cannot verify
Supported Functionality > Access Time Restriction
T09LQY Personal Management - Access Time Restriction  Supported, cannot verify
Supported Functionality > Holidays Support
T09XRR Personal Management - Holiday Support  Supported, cannot verify
Supported Functionality > Pin Management
T09VMN Personal Management - Pin Management  Supported, cannot verify
Supported Functionality > Card Management
T09IND Personal Management - Card Management  Supported, cannot verify
Supported Functionality > Antipassback Forgiveness
T09UPY Personal Management - Antipassback Forgiveness  Supported, cannot verify
Supported Functionality > Device Audit Log Retrieval
T2FESO Device Audit Log Retrieval  Supported, cannot verify
Supported Functionality > Remote Device Control
T04XSI Output Inhibit and Uninhibit Remotely From C4  Not supported
Comment: Not supported by protocol.
T08ARF Door Lock and Unlock  Supported, cannot verify
T08LON Door Remote Open  Supported, cannot verify
Device Category > ACS
T08FDN Door Open Permanently  Supported, cannot verify
T08ICK Door Forced Open  Supported, cannot verify
T08JRH Door Open Too Long  Supported, cannot verify
T08OCH Request to Exit Button  Not supported
Comment: Not supported by communication protocol.
T09CRN Personal Management - Handling Access Granted Event  Supported, cannot verify
T09EZJ Personal Management - Biometric - Fingerprint  Not supported
Comment: Not supported by device.
T0BBCP Duress Alarm  Supported, cannot verify
T0BHSL Tamper  Supported, cannot verify
T0FCVB Contact Monitoring from Device  Not supported
Comment: Device generate Alarm events for inputs only when Area is armed. Device does not
sent events for inputs when Area is in disarmed state.
T0FLFU Activating Test Mode on Detector from Device  Not supported
T0FQCA Mains Failure  Supported, cannot verify
12 / 37
T0FVUH Activating Test Mode on Detector Remotely from C4  Not supported

T0FYGI Battery Failure  Supported, cannot verify
T3FIGI Output Activation and Deactivation  Supported, cannot verify
T7FHSW Missing HW Item  Not supported
Comment: Not all devices generates Missing device event.
Device Category > IAS
T03MTG Alarm Suppression - Intrusion  Not supported
Comment: Device does not require reset after alarm.
T03XRL Intrusion Alarm  Supported, cannot verify
T07BGC Detector Inhibit and Uninhibit Remotely from C4  Supported, cannot verify
T07QHA Detector Inhibit and Uninhibit from Device  Supported, cannot verify
T07XJB Failure While in Test on Detector  Not supported
T07ZJY Alarm While in Test on Detector  Not supported
T07ZOS Detector Failure  Not supported
T09CRN Personal Management - Handling Access Granted Event  Supported, cannot verify
T09EZJ Personal Management - Biometric - Fingerprint  Not supported
T0BBCP Duress Alarm  Supported, cannot verify
T0BHSL Tamper  Supported, cannot verify
T0FCVB Contact Monitoring from Device  Not supported
Comment: Device generate Alarm events for inputs only when Area is armed. Device does not
sent events for inputs when Area is in disarmed state.
T0FLFU Activating Test Mode on Detector from Device  Not supported
T0FQCA Mains Failure  Supported, cannot verify
T0FVUH Activating Test Mode on Detector Remotely from C4  Not supported
T0FYGI Battery Failure  Supported, cannot verify
T3FIGI Output Activation and Deactivation  Supported, cannot verify
T7FHSW Missing HW Item  Not supported
Comment: Not all devices generates Missing device event.
13 / 37
Appendix A
Integration Tests
14 / 37
T03XRL - Intrusion Alarm

This test verifies behavior of the driver when handling the alarm events and taking respective actions related to
the current state of the alarm handling. This test applies for Alarm systems or systems with similar functionality.
Test Steps
Set the detector to the armed mode (e.g. arming the corresponding area)
Issue an alarm on detector
Restore the alarm on detector
Confirm the alarm from C4 UI
Expected Results
The detector state is set to the Alarm.
The corresponding areas states are set to the Alarm.
After the alarm confirmation the Alarm state is finished.
Following events are stored in audit log:

Alarm on 'DEVICE'.
Alarm restored on 'DEVICE'.
Where
DEVICE represents a name of detector where the alarm was generated.
Notes:
Preferred way to confirm an alarm is to handle it through the Alarm Handling 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
15 / 37
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

'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.
16 / 37
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

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.
17 / 37
T08ARF - Door Lock and Unlock

This test verifies behavior of the driver implementation for controlling of locked doors.
Locked doors doesn't allow to enter the person, even when it has valid credential with proper access rights.
Test Steps
Execute command “Lock” on door
Try to open the door using valid credential
Execute command “Unlock” on door
Expected Results
During door lockout door ignores any attempt to open it with valid credentials
Status of the door is Locked when locked

'PERSON' sent command 'Lock' to 'DEVICE'.
'DEVICE' locked.
'PERSON' sent command 'Unlock' to 'DEVICE'.
'DEVICE' unlocked.
Where
DEVICE represents the door name

PERSON represents the name of person who executed the command
Notes:
If the device supports dynamic command state and device is Locked you can see only command
"Unlock".
18 / 37
T08FDN - Door Open Permanently

This test verifies behavior of the driver implementation for remote controlling of doors.
This test focuses on handling events and states when door is opened permanently.
Test Steps
Execute command “Open Permanently” on door
When door contact is present, simulate real door opening
Execute command “Close” on door
When door contact is present, simulate real door closing
Expected Results
After issuing the command "Open Permanently", the door status is set to Unblocked.
During real door opening, the door contact is activated and the door status is set to Open Indefinitely.
After issuing the command "Close", but door contact is still opened, door status remains Open Indefinitely.
After real door closing, the door contact is deactivated or the door relay timer expires, the door status returns to
Close (normal) state.

'PERSON' send command 'Open Permanently' to 'DEVICE'.
Door 'DEVICE' opened permanently.
'PERSON' send command 'Close' to 'DEVICE'.
Where
PERSON represents the name of person who executed the command.
Notes:
When door contact is not present or real door opening/closing is not simulated, after issuing both commands, the
door status is set to Open Indefinitely and then returns to Close (normal) state.
Test is considerabled as passed when you need to reverse step 4 and 3
19 / 37
T08ICK - Door Forced Open

This test verifies behavior of the driver implementation for remote controlling of doors
This test focuses on handling events and statuses during the unauthorized opening of the door in a protected
system.
Test Steps
Activate door contact
Expected Results
1.Door status is set to Forcibly open

Door 'DEVICE' forced open.
Where
20 / 37
T08JRH - Door Open Too Long

This test focuses on handling events and states during the held open alarm on the door.
Test Steps
Use the credential to access the access point
Activate door contact
Keep the contact activated longer than the predefined time
Expected Results
After successful credential authorization, the door status is set to Unblocked.
Door status is set to Open when the door contact is activated.
After predefined open time expiration, the door status is set to OpenTooLong.

'DEVICE' opened by 'PERSON'.
Door 'DEVICE' open too long.
Where

PERSON represents the name of person who used authorized credential
21 / 37
T08LON - Door Remote Open

Test Steps
Execute command “Open” on door
When door contact is present, simulate real door opening
When door contact is present, simulate real door closing
Expected Results
After issuing the command "Open", the door status is set to Unblocked.
During real door opening, the door contact is activated and the door status is set to Open.
After real door closing, the door contact is deactivated and the door status is set to Unblocked. If the
door relay timer also expires, the door status returns to Close (normal) state.

'PERSON' send command 'Open' to 'DEVICE'.
'DEVICE' opened by 'PERSON'.
Where

PERSON represents the name of person who executed the command
22 / 37
T09CRN - Personal Management - Handling

Access Granted Event
This test verifies behavior of the driver when receiving the access granted event from the device.
Test Steps
Create new person
Assign the person a valid credential
Grant the person access to the access point
Send credentials to the device
Expected Results
Person got access to specific access point
Access point status is set to Unblock

Access granted to 'PERSON' at 'DEVICE'
Where
PERSON represents the name of person who get access to device

23 / 37
T09IND - Personal Management - Card

Management
This test verifies behavior of the driver implementation for transferring the card credentials into the device
memory, allowing to define access permissions based on them.
Test Steps
Create new person
Assign valid Card to this person
Expected Results
Person has correctly defined permissions in a device

'PERSON' cleared access data on 'DEVICE'
Access granted to 'PERSON1' at 'DEVICE1'.
Where
PERSON represents a name of person who executed the command

PERSON1 represents a name of person who used credentials on access point
DEVICE represents the device where the credentials are sent into
DEVICE1 represents a name of access point
24 / 37
T09LQY - Personal Management - Access Time

Restriction
This test verifies behavior of the driver implementation for time limited access scenarios, allowing to update the
device configuration in that a way, that the access can be limited to some specific hours and/or days of the
week.
Test Steps
Create new person
Restrict the access permission with time restriction
Check whether the restriction is applied correctly
Expected Results
The assigned time restriction is correctly applied
When person has no limitation in access it gets access granted event. When person has limited
access by time restriction it gets access denied event.

Access granted to 'PERSON1' at 'DEVICE1'.
Access denied to 'PERSON1' at 'DEVICE1'. Reason: Active time restriction
Where

DEVICE represents the device where the credentials are sent into
DEVICE1 represents a name of access point
Notes:
Some devices might impose limits on the complexity and/or amount of available time
restrictions.These limits must be enumerated in test notes and validated during this test.
25 / 37
T09UPY - Personal Management - Antipassback

Forgiveness
This test verifies behavior of the driver when device provide antipassback functionality. Card holder's record will
be "forgiven" in order for normal card access to be achieved.
Test Steps
Activate antipassback functionality on device, when necessary
Create new person
Use credential again on same access point
Remove person from the region in C4
Expected Results
Person get access granted for first attempt
Person get denied access for second attempt
Person get granted access for third attempt

Access granted to 'PERSON' at 'DEVICE'.
Access denied to 'PERSON' at 'DEVICE'.
'PERSON' forcibly removed 'PERSON' from region 'REGION'.
Access granted to 'PERSON' at 'DEVICE'.
Where
PERSON represents a name of test person

DEVICE represents the device where the PERSON use credential
REGION represents a name of region
Notes:
Valid only on devices providing antipassback functionality. Credential holder's record will be "forgiven"
in order for normal credential access to be achieved.
26 / 37
T09UVU - Personal Management - Card Learning

This test verifies behavior of the driver when device provides enough information about the unknown card, that
card information can be constructed from these data and new card can be created in a system.
Test Steps
Create new person
Execute Learn Card feature on this person
Choose correct device for card learning
Slide the card on this device
Expected Results
A card of device supported type is created and assigned to the person

'PERSON' created Card 'CARDNAME' into 'DECK'.
'PERSON' activated 'CARDNAME' to 'PERSON1'.
Where:
PERSON represents a name of person who is executing the command
PERSON1 represents a name of person who got card assigned to
CARDNAME represents a name of card with it's card number
DECK represents a name of card deck
Notes:
Some devices might have some limitations in providing information abut the unknown card
Valid only on devices providing enough information about the unknown card, that the card information can be
constructed from these data and new card can be created in a system
27 / 37
T09VMN - Personal Management - Pin

Management
This test verifies behavior of the driver implementation for transferring the PIN credentials into the device
memory, allowing to define access permissions based on them.
Test Steps
Create new person.
Assign valid PIN to this person
Check, whether the definitions were transferred correctly – either by reading the device memory
directly or by proving operation on the device
Expected Results
Person has correctly defined permissions in a device.

'AREA' was armed by 'PERSON1'.
Where

DEVICE represents the device where the credentials are uploaded into
AREA represents the name of area
Notes:
Some devices might have some limitations in PIN length or some rules to define valid PIN.
28 / 37
T09XRR - Personal Management - Holiday

Support
This test verifies behavior of the driver implementation for manipulation with a list of holidays in the device,
allowing to define the different rules for holidays than for normal working days or weekends.
Test Steps
Create new person
Create holiday set, containing the todays date
Modify holiday set that it doesn't contain todays date
Expected Results
1.The assigned time restriction is correctly applied

'PERSON' cleared access data on 'DEVICE'.
Where

DEVICE represents the device where the credentials are uploaded into
Notes:
Some devices might impose limits on the complexity and/or amount of available time
restrictions.These limits must be enumerated in test notes and validated during this test.
29 / 37
T0BBCP - Duress Alarm

This test verifies behavior of the driver when is notified about duress alarm on Alarm systems, Access systems
or other systems with similar functionality.
Test Steps
Issue a duress alarm
Confirm the duress alarm
Expected Results
A device where the duress alarm is reported has Alarm status.
After confirming the duress alarm, duress alarm is finished and the device where the duress alarm
was reported has normal status.

Duress signal from 'DEVICE' by person 'PERSON'
Where
DEVICE represents the name of device where the duress alarm occurred.
PERSON represents the name of person issuing the duress alarm
Notes:
Depending on the device, the Alarm state might be signalized on other devices like areas, panels etc.
It is acceptable when the alarm is confirmed by other sequence of commands issued from UI (typically
Disarm on area)
In C4 alarm events are stored always for device that is “nearest” to the real alarm source. This is
usually keypad. 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
30 / 37
T0BHSL - Tamper
This test verifies behavior of the driver when processing the events about the device tampers on Access
systems, Alarm systems or devices with similar functionality.
Test Steps
Issue a tamper on detector, while detector is in disarmed state
Restore the tamper
Confirm the alarm from C4 UI.
Expected Results
Until the alarm confirmation, the detector has tamper status.

Tamper on 'DEVICE'.
Tamper completed on 'DEVICE'.
OR
Tamper 'DEVICE' restored by 'PERSON'.
Where
DEVICE represents a name of tampered detector.

PERSON represents a name of person who confirmed the alarm.
Notes:
Variation of this test is to confirm the tamper alarm from device keypad
Test must be reproducible on all devices that are capable of generating the tamper alarm
In case the device ends the tamper state automatically, there is no need to confirm the tamper from
C4 UI and the test is also considered as passed.
31 / 37
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.

'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
32 / 37
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.

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
33 / 37
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.

'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.
34 / 37
T2FESO - Device Audit Log Retrieval

This test verifies behavior of the driver when transferring events from the device audit log after establishing
communication. Standard behavior is that the driver reads all events from the device audit log, even events that
happened during periods of disconnection.
Test Steps
Stop the endpoint
Wait for 1 minute
Execute operation on device that leads to the entry in the device audit log
Wait for 1 minute
Start the endpoint.
Expected Results
All events from the device that happened during disconnection are stored in audit log with original
time of the events on device, not with the time when they were read out from the device.

'DEVICE' started.
Where
DEVICE is a name of driver that was started
35 / 37
T3FIGI - Output Activation and Deactivation

This test verifies behavior of the driver implementation for output contact monitoring and controlling support.
Test Steps
Execute command “On” on output.
After the output is opened, execute command “Off” on it.
Expected Results
When output is activated, its status is Open.
When output is deactivated, its status is Normal.

'PERSON' sent command 'On' to 'DEVICE'.
'DEVICE' opened.
PERSON' sent command 'Off' to 'DEVICE'.
'DEVICE' closed.
Where
PERSON represents the name of person who executed the commands

DEVICE represents the output name
36 / 37
T7FKUJ - Device Auto import

This test verifies behavior of the driver when retrieving the configuration of the device and building the device tree
corresponding to the actual device configuration.
Standard behavior is that the driver retrieves all nodes and properties on the device.
Test Steps
Use add wizard and choose corresponding device type
Fill required properties
Wait until the driver loads configuration from device
Confirm the changes
Expected Results
Window where you can fill required properties is shown.
'DEVICE' tree was successfully imported.

'DEVICE' import successfully finished on 'INSTALLATION'.
Where
DEVICE is a name of a driver that you want to import.

INSTALLATION is a name of installation under which the device is created.
Notes:
Variation of this test is to execute the command "Load Configuration from Device" on incomplete
device tree configuration. When this functionality is supported, the test is considered as passed only
when both ways work correctly
Some devices do not provide all properties
37 / 37

Verex/SNAPP: Integration Manual

Uploaded by

Copyright:

Available Formats

You might also like

Verex/SNAPP: Integration Manual

Uploaded by

Document Information

Original Description:

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Verex/SNAPP: Integration Manual

Uploaded by

Copyright:

Available Formats

Verex/SNAPP

Supported Card Segments

Supported Pin Lengths

How to Connect Device to C4

Step 1 - Configure the central unit to allow 3rd party connections

Step 2 - Connect the IP interface to the Control Panel

Step 3 - Programming the IP receiver (only SNAPP protocol)

Step 4 - Programming the IP receiver (encrypted communication -

Explicit User positions assignment

PROPERTY RANGE DEFAULT

CARD READER WITH KEYPAD

POINT EXPANSION MODULE

SUITE CARD READER WITH KEYPAD

PROPERTY RANGE DEFAULT

T0FVUH Activating Test Mode on Detector Remotely from C4  Not supported

T03XRL - Intrusion Alarm

Following events are stored in audit log:

T07BGC - Detector Inhibit and Uninhibit

Following events are stored in audit log:

DEVICE represents the detector name

T07QHA - Detector Inhibit and Uninhibit from

Following events are stored in audit log:

DEVICE represents the detector name

T08ARF - Door Lock and Unlock

Following events are stored in audit log:

DEVICE represents the door name

T08FDN - Door Open Permanently

Following events are stored in audit log:

T08ICK - Door Forced Open

Following events are stored in audit log:

DEVICE represents the door name

T08JRH - Door Open Too Long

Following events are stored in audit log:

DEVICE represents the door name

T08LON - Door Remote Open

Following events are stored in audit log:

DEVICE represents the door name

T09CRN - Personal Management - Handling

Following events are stored in audit log:

PERSON represents the name of person who get access to device

T09IND - Personal Management - Card

Following events are stored in audit log:

PERSON represents a name of person who executed the command

T09LQY - Personal Management - Access Time

Following events are stored in audit log:

PERSON represents a name of person who executed the command

T09UPY - Personal Management - Antipassback

Following events are stored in audit log:

PERSON represents a name of test person

T09UVU - Personal Management - Card Learning

Following events are stored in audit log:

T09VMN - Personal Management - Pin

Following events are stored in audit log:

PERSON represents a name of person who executed the command

T09XRR - Personal Management - Holiday

Following events are stored in audit log:

PERSON represents a name of person who executed the command