Purpose and scope

This manual describes the integration of Advisor Advanced with C4 through the Advisor Advanced driver using FWK4. It covers supported functionality, communication, configuration, credentials, profiles, operating behavior, restrictions and integration tests.

The manual is intended for system integrators, commissioning engineers, C4 administrators, technical support and integration testers. Device installation, electrical work and manufacturer-specific safety procedures remain governed by the applicable manufacturer documentation and site procedures.

Document control

Revision history

Terminology and conventions

C4 labels, device types, property names, commands, statuses and event identifiers are written exactly as shown in the applicable software. A device is the integrated equipment or external system; a driver is the C4 software component that implements the integration. An endpoint or circuit is identified using the terminology of the applicable C4 release.

Device Category

Integration boundary and operating modes

C4 connects to the Advisor Advanced panel over Ethernet. Associated expanders, keypads and readers are represented in the C4 device tree. A CDC4 in extended mode communicates both through the internal ATS bus and directly over the LAN; it keeps a separate database of users and door groups.

For the two connection topologies and their original diagrams, see How to Connect Device to C4. For CDC4 in standard mode, use the Expander device type.

Supported Functionality

S = marked as supported. N = not marked as supported in the integration scope. The detailed chapters qualify the supported functions; a support indication is not an executed test result.

Compatibility and dependencies

• Supported firmware versions: MR_4.7 … MR_4.13

Licensed Device

Alarm Panel

Capacity and functional restrictions

• The maximum number of credentials per user is one PIN code and one Card. If a person in C4 has multiple credentials assigned, multiple user entries are created in the device so that all credentials can be added.

Important notes

• PIN code is mandatory for every user on X500 panels with MR1 and MR2 firmware

• While communicating with the panel from C4, Installer account is locked out (Installer cannot login to keypad or to ATS8500 Standalone Downloader). This is valid also vice versa.

• Advisor Advanced X500 (MR1, MR2, MR3, MR4) : All areas, DGPs an DGPs ATS 125x Access Controller couldn’t have any of alarms (e.g. Alarm, Fire alarm or Tamper) during credentials upload. Otherwise, upload will fail.

• Advisor Advanced X500 (MR4.1 and higher) : Panel accepts credentials upload in states like: unset, alarm, exit time, set, set alarm, entry time, entry alarm, tamper zone, tamper RAS, tamper DGP, partset1, partset2.

• During user upload, users can be denied their rightful access.

• Maximum / minimum number of allowed users and user groups may be set in Alarm Panel’s general setting tab. It’s extremely important to remember about not exceeding the available number, keeping in mind that 2 first users are already saved for Installer and Supervisor (done automatically).

• The maximum acceptable user number on the old panels (MR1, MR2) varies (50, 200, 1000) and depends on panel model and protocol version. The current panels (MR4) support 2000 users itself, which increase to the max (65532) only when a door controller is added. Without door controller these additional users will not be usable.

Operational warnings

Full Upload clears managed device memory positions before uploading credentials. Coordinate access, protection and monitoring impacts before uploads, resets or integration tests. Use an authorized test installation or controlled work window.

Security and safety boundaries

The retained factory-reset procedure specifies Non EN50131 mode, Duress mode and Forced Set. Confirm these settings against approved site requirements before changing an operational installation. Encryption settings are listed under Device Configuration.

Topology and communication flows

The ATS Advanced system is connected through an Ethernet interface.

ATS in the diagram means ATSx500A(IP) Advisor Advanced device - Main Control Panel (e.g. ATS3500AIP) and some other DGP expanders (DGP – Data Gathering Panel, e.g. four door expander ATS1250), Keypads (RAS-es) and Readers.

To connect C4 to Advisor Advanced device, configure network connection between your machine and the panel:

• Put the machine and the panel in the same network,

• Configure static IP for the panel,

• Make sure the machine and the panel are in the same subnet (subnet mask)

Connection and initial commissioning procedure

After the physical network is configured, in C4, under device manager, add Advisor Advanced Bus Controller device, under which ATS Alarm Panel. Fields that must be configured:

Bus Controller:

• IP Address,

• Destination port (default 32000),

• Timeout (default 30 seconds)

• Type Encryption Key in Encryption Key field

• Type Encryption Key 2 in Encryption Key 2 field

ATS Alarm Panel options:

• Password (Installer’s PIN code).

Connection and communication with CDC4 door controllers in extended mode

The CDC4 is an eight-door controller (In Standard mode only the four-door) and can operate in extended mode, which means that it is connected directly to the LAN in addition to the internal ATS bus. In the C4, the “CDC4 Door Controller” device is used for this type of connection. Each door slot can be configured as a Lift (Door type: CDC4 Lift).

The CDC4 door controllers in extended mode communicates with the C4 system via the Advanced panel (via the internal ATS bus) and also directly via the LAN. Access events are sent directly via IP to C4, while intrusion alarms are sent to the Advisor Advanced panel. The CDC4 retains its own database of users, door groups etc. separate from the Advisor Advanced panel.

Device preparation and secure access

Set the panel network address and subnet before starting the circuit. The panel Password is the Installer PIN. Provision Encryption Key and Encryption Key 2 to match the panel. The factory-reset and initial-menu sequence is retained under Operation, Recovery and Maintenance.

After Load Configuration, complete the CDC4 IP Address, Port, Password and encryption properties manually. The C4 and local Installer sessions cannot be used concurrently, as described under Restrictions and Important Notes.

Device tree and addressing

Add the ATS Alarm Panel below the Advisor Advanced Bus Controller. Each record below defines the represented object, allowed parent, properties and address range.

Advisor Advanced Bus Controller

• This is the root device in the device tree.

NOTE:

• The time zone property must match the time zone (UTC offset) in the panel settings, otherwise time of events or time synchronization may not work properly!
  If panel’s time zone differs from the C4 time zone, the event “Invalid format of property value 'TimeZone' on device 'DEVICE'.” is stored when the driver is started.

ATS Alarm Panel

• Represents the main panel (Central unit)

• This device can be added under the Bus Controller

NOTES:

• The Filters have been implemented (as time restrictions for User Groups) in driver version 2020.0.0.138

Area

• Represents Area (Partition) on the ATS device

• This device can be added under the Alarm Panel

Detector

• Represents a Zone on the ATS device

• This device can be added under the Alarm Panel.
  Link to Detector can be added under the Area

Virtual Door

• Used as a parent device for RAS devices (Keypad, Card Reader or Keypad And Card Reader) not associated with a physical CU Door.

• This device can be added under the Alarm Panel

CU Door

• Represents a Door on the ATS Panel (Door type: Standard)

• This device can be added under the Alarm Panel

Keypad

• Represents an LCD Keypad on the RAS bus (RAS - Remote Arming Station)

• This device can be added under the: CU Door; Virtual Door.

Keypad And Card Reader

• Represents a Card reader device with numeric keypad (on the RAS bus)

• This device can be added under the: CU Door; Virtual Door.

Card Reader

• Represents a Card reader device (on the RAS bus)

• This device can be added under the: CU Door; Virtual Door.

Input

• Represents a Zone on the ATS device (typically expander)

• This device can be added under the: Alarm Panel; Expander; DGP Door; CDC4 Door Controller.

Relay (Output)

• Represents the Relay / Output on the device

• This device can be added under the: ATS Alarm panel; Card Reader; Keypad; Keypad And Card Reader; DGP Keypad And Card Reader; Expander; CU Door; DGP Door; CDC4 Door Controller.

Expander

• Represents the DGP (Data Gathering Panel) device

• This device can be added under the Alarm Panel.

NOTE: Maximum address for the devices ATS125x Access Controller and CDC4 (4-door controller in standard mode) is 12

DGP Door

• Represents a Door on the Expander (DGP device – e.g. ATS1250 controller)

• This device can be added under the Expander

DGP Lift Unit

• Represents a Lift (Lift car) on the Expander (CDC4 controller in Standard mode)

• This device can be added under the Expander

DGP Lift Door

• Represents a Floor

• This device can be added under the DGP Lift Unit

DGP Keypad

• Represents an LCD Keypad

• This device can be added under the DGP Door or DGP Lift Unit

DGP Keypad And Card Reader

• Represents a Card reader device with numeric keypad

• This device can be added under the DGP Door or DGP Lift Unit

DGP Card Reader

• Represents a Card reader device (on the RAS bus)

• This device can be added under the DGP Door or DGP Lift Unit

CDC4 Door Controller

• The CDC4 door / lift controller in extended mode

• This device can be added under the ATS Alarm Panel

NOTES:

• for CDC4 in standard mode use Expander device type instead of CDC4 Door Controller

• The minimum and maximum allowed memory position for user records is the same as for the ATS alarm panel. Also, the memory positions for the same person are the same on the panel and CDC4

• Time synchronization is performed via the internal ATS BUS from the Advanced panel

CDC4 Door

• Represents a Door on the CDC4 door controller in extended mode

• This device can be added under the CDC4 door controller

CDC4 Lift Unit

• Represents a Lift (Lift car) on the CDC4 controller in extended mode (door slot configured as Lift)

• This device can be added under the CDC4 door controller

CDC4 Lift Door

• Represents a Floor on the CDC4 Lift Unit

• This device can be added under the CDC4 Lift Unit

CDC4 Keypad

• Represents a credential device on the CDC4 door controller in extended mode

• This device can be added under: CDC4 Door; CDC4 Lift Unit.

CDC4 Card Reader and CDC4 Keypad with Card Reader

• Represents a credential devices on the CDC4 door controller in extended mode

• This device can be added under: CDC4 Door; CDC4 Lift Unit.

Load Configuration

During the Load Configuration process, CDC4 door controllers in extended mode are automatically imported into the device tree, but some properties (IP address, Port, Password, encryption settings) must be configured manually for successful communication.

Configuration-transfer acceptance checks

Check the resulting tree and properties, complete the manual CDC4 settings and validate the addresses before starting the endpoint. Expected audit messages are retained in T-CFG-03.

Supported PIN Lengths

4 - 10

PIN

Each user can be authenticated with a PIN. PIN can be an n digit number string within a range defined by the central unit. Central unit must have the PIN mode property set to Custom.

Important: PIN is compulsory for X500 MR1, MR2. A person without a PIN couldn’t be send to the panel.

Card

Apart from the PIN, each user can have a card, as well. Card is not required to send credentials (this option is non-obligatory). Supported card type is for example ATS IUM.

Card + PIN (Merged)

If a person has multiple cards or PINs, the merged credentials ensures that they are stored in the same memory position on the device.

Person and identifier mapping

The device supports one PIN and one Card per user entry. Multiple credentials assigned to one person in C4 can require multiple device user entries. Review the merged-credential statement above together with this per-entry limit, and validate reassignment using T-UPL-01.

Default credentials and commissioning accounts

Ownership and object mapping

Upload modes and triggers

Lifecycle, access rights and exceptional conditions

T-UPL-01 preserves the access-right and credential-reassignment scenarios, including persons placed under the root, companies and departments, and access assigned to doors absent from the physical device. Check permissions on the device and verify the correct person in the C4 access event after each upload.

The panel Holiday Set and schedule/filter ranges are listed in Device Configuration. T-ACL-01 verifies access-time restrictions and T-ACL-02 verifies holiday behavior. Filters for user-group time restrictions were introduced in driver version 2020.0.0.138.

Reserved memory positions

Verification and recovery

Observe the Uploading Credentials status and the completion or failure audit messages. A reported communication failure during upload can also mean that the central unit refused a user or user group. Validate actual permissions and person attribution rather than relying only on transport completion.

T-UPL-02 covers interruption during credential transfer. After the namespace-changing upgrade to driver version 2020.0.0.581 or later, perform Full Upload before any other upload type; see Upgrade and Migration.

Profiles on ATS Alarm Panel

These profiles are mapped to users in device’s memory

Area profiles

Area profiles are mapped to user groups in device’s memory.
It is possible to set special user settings for each user group (access level).

Be careful while setting different settings for many Profiles. Modifications in Profiles for separate users may cause creation of new user group at the panel and in result cause overrun of maximum allowed alarm group number.

CDC4 profiles

CDC4 profiles are mapped to users in device’s memory (on the CDC4 door controller).

Time source and synchronization

Time zone and event-time interpretation

The Bus Controller Time zone property must match the panel time zone (UTC offset). Otherwise event timestamps or time synchronization may be incorrect.

Verification

Execute the startup and periodic tests only under their documented conditions. The periodic test is restricted to devices that do not notify time changes. The startup test retains the special applicability note for devices whose time is controlled by their own NTP server or equivalent facility.

ACS - doors, access and lifts

CU Door represents a standard panel door. DGP Door represents a door on an expander; CDC4 Door represents a local door on an extended-mode CDC4. Their command and status mappings are defined in the following two chapters.

DGP Lift Unit and CDC4 Lift Unit represent lift cars; their Lift Door children represent floors. Lift-unit Arm secures all floors and Disarm provides access to all floors. Lift Door Lock and Unlock secure or allow access to the individual floor. DGP Lift Unit additionally exposes Bypass On and Bypass Off.

Door tests cover manual override, permanent unlock, forced opening, held-open alarms, remote unlock, exit-button use and access decisions. Open/closed/locked events depend on the door type and settings; the held-open event depends on Report DOTL.

IAS - alarm, bypass and walk test

Area commands include Arm, Disarm, Reset alarm, Forced arm, Rearm, Test and Finish Test. Rearm issues Disarm, waits for Rearm delay and then issues Forced Arm. All commands are disabled during area testing except Finish Test.

Alarm and bypass behavior, including the extended-mode expander Rearm restriction and device-side bypass events identifying the actor as Unknown, is preserved in T-ALM-01, T-ALM-02A and T-ALM-02B.

Inputs, outputs and equipment health

Output has to be configured in ATS downloader through Filter where you select trigger and event. Then on output you select filter you created.

Input and Relay (Output) addressing and trigger properties are listed in Device Configuration. Output activation/deactivation, tamper, mains failure and backup-power failure are covered by T-IO-01, T-ALM-03 and T-HLT-01/02.

Supported commands

The C4 system makes it possible to perform the following operations above individual elements:

Door, input and lift commands

NOTES:

• All commands are disabled while the area(s) are being tested, except the Finish Test command

Bus Controller

Alarm Panel

NOTES:

• The device reports a Fault status under certain circumstances even when everything is functional.

Area

Detector

CU Door

Virtual Door

Keypad, Keypad And Card Reader, Card Reader

DGP Door

DGP Keypad, DGP Keypad And Card Reader, DGP Card Reader

DGP Lift Unit

DGP Lift Door

Expander

Input

Output

CDC4 Door controller

CDC4 Door

CDC4 Lift Unit

CDC4 Lift Door

CDC4 Keypad,
CDC4 Card Reader,
CDC4 Keypad with Card Reader

Initialization, connection and restoration

On a successful connection, the endpoint children are set to their real states. The Network Connection Lost test expects all nodes below the endpoint to become Disconnected during the interruption and to return to their real states after reconnection. Missing, duplicate or additional nodes are addressed by T-CFG-01, T-CFG-02 and T-CFG-08.

The Alarm Panel may report Fault even when all equipment appears functional. State labels used by some test cases differ from the reference tables; retain those differences during review as described under Technical confirmation notes.

Event mapping

The integration tests retain the exact expected audit-message text for each operation. Use the related case below for complete messages, placeholder definitions and conditional logging notes.

Event context and interpretation

Audit messages use the device, person, credential and reader identifiers defined in each test. Missing-device events are attributed to the nearest parent or driver; alarms use the nearest identifiable source. Device-side PIN bypass may identify the actor as Unknown.

Device Audit Log Retrieval

After communication is established again, C4 retrieves events recorded while the device was disconnected. T-EVT-02 requires those events to be stored with their original device timestamps, not the time at which C4 read them. Alarm Panel and CDC4 Door Controller expose Downloading History status.

Diagnostics and evidence

The namespace-change issue described under Upgrade and Migration is recorded in the Exceptions trace log. Retain the actual event and trace evidence with the test report; protect deployment secrets and personal identifiers when distributing diagnostic material.

Normal operation and connection ownership

Use the Bus Controller Start, Stop and Restart commands for circuit operation. The normal Bus Controller state is Idle. Panel status/event polling defaults to 00:00:10; CDC4 regular queries default to 00:00:05.

While C4 communicates with the panel, the Installer cannot log in through the keypad or ATS8500 Standalone Downloader. The restriction also applies in the reverse direction.

Failure and recovery behavior

Factory reset

1.Press MENU - Installer PIN - # - # - 1 - 6 - UP ARROW - #

2. How to log in using default credentials?

Press MENU - PIN - #

To reset changed Installer PIN code to default, short jumper T1 (see image) and power on the panel and wait for System failure message on the LCD keypad. Then remove jumper.

3. Configuration steps to ensure basic operation of the device

Configuration is automatically started after the panel is defaulted, this is only a list of important changes in regards to C4:

option 2 - select Non EN50131 mode

option 3 - Duress mode set to Inc Last Digit

option 6 - select Install - OK - # - # - # / Installation starts.

When installation ends and panel loads, it will ask for Auto Config - confirm Yes with # key

In Installers Menu, navigate to 8 - 4 - 3 and set Forced Set option to On.

In Installers Menu, navigate to 8 - 7 - 5 and set PIN chg mode to Custom

In Installers Menu, navigate to 9 - 3 - 4 - 4 - 1 - change IP config from Dynamic to Static

In Installers Menu, navigate to 9 - 3 - 4 - 4 - 2 - set IP address and confirm with #

In Installers Menu, navigate to 9 - 3 - 4 - 4 - 3 - set subnet mask, if non default

In Installers Menu, navigate to 9 - 3 - 4 - 4 - 4 - set IP of the gateway

Exit the menu with Clear key, until message Goodbye ? appears, then choose Yes and # key.

Person names are not resolved after upgrade to version 2020.0.0.581 due to a JSON serialization exception

When updating the driver to version 2020.0.0.581 or later, the driver does not determine the names of persons in access events until a full upload has been performed. After this update, a full upload must be performed before any other type of upload. This happens because from this version driver change namespaces in Device Model.

The following error is stored in the Exceptions trace log file:

Troubleshooting

Support and reference material

Test scope, environment and safety

The test set validates the documented integration scope. Record the exact environment and approved expected results before execution. Use an authorized test installation or controlled commissioning window, synthetic identities and safe stimuli. Alarm, access, output, reset, power and time-change tests require an approved method, affected-party notification and a recovery plan.

The following 35 cases are test procedures, not recorded execution results. Retain the firmware-specific conditions and notes within each case. Use an authorized installation and restore temporary settings, credentials, door states and power/alarm conditions after the run.

Measurable acceptance limits

Coverage and selection rules

Run each applicable procedure for the relevant device types and supported modes. Repeat the stated address, property, tamper and power variants. A capability without a dedicated procedure here, such as Card Learning, is not automatically considered validated. Record any additional qualification coverage separately.

Test result and execution record

Each case uses a description, prerequisites, paired Test Steps and Expected Results, expected audit evidence and cleanup. Complete the execution record with actual results and evidence. PASS means every applicable expected result met its limit; FAIL means at least one did not; BLOCKED means a prerequisite or dependency prevented execution; NOT RUN means no execution; NA means an approved, documented non-applicability decision. A waiver or known defect does not turn a failed test into a pass.

Record test ID and variant, requirement, purpose, risk authorization, tester/date, actual results, result, evidence, defect/deviation reference and cleanup confirmation in a separate versioned test report. A dash in a test table means no separate intermediate result is stated for that step; use the later expected result and audit evidence.

Test catalog