---
documentId: "JABLOTRON_JA-100_INTEGRATION_MANUAL_EN"
title: "JABLOTRON JA-100 Integration Manual"
version: "v01"
publisher: "Gamanet"
author: "Marian Gal"
datePublished: "2026-11-22"
dateModified: "2026-11-22"
effectiveFrom: "2026-10-15"
effectiveTo: ""
applicableProduct: "system-c4"
applicableProductModule: "driver"
applicableProductVersions: ["2026 SP4"]
documentType: "INT"
audience: ["system-administrator","installer","system-integrator","support-engineer"]
language: "en"
confidentiality: "public"
abstract: "Describes the integration of the JABLOTRON JA-100 alarm system with System C4 through the JA-121T communication module and an RS485-to-TCP/IP converter. Covers supported functions and limitations, connection and device configuration, PIN and card management, remote control commands, device status mappings, and integration-test procedures."
keywords: ["C4","JABLOTRON","JA-100","JA-121T","intrusion alarm","control panel","RS485","TCP/IP","serial converter","Terminal mode","F-Link","BUS Controller","Central Unit","Section","Detector","Fire Detector","Relay","PG output","PIN management","card management","EM Marine","reserved user positions","Load Configuration","credential upload","integration tests"]
licenseOrUsageTerms: ""
canonicalUrl: "https://my.c4portal.com/atlas/docs/jablotron_ja-100_integration_manual_en/latest/index.html"
downloadFormats: ["HTML","PDF","Markdown"]
fileChecksum: "8TFlQUNQhQCtLvxC1DJtMnb65fxi1u/IG1XDgA3/bU8=                    "
citationText: ""
---

Varnet

C4 DRIVER DOCUMENTATION

JABLOTRON JA-100 Integration Manual

Intrusion alarm monitoring and control through JA-121T

JABLOTRON JA-100 | JA-121T | RS485-to-TCP/IP

| Field | Content |
| :--- | :--- |
| Prepared by | Varnet |
| Issue date | 11-22-2026 |
| Applies to | JABLOTRON JA-100 integration with C4 through JA-121T and an external RS485-to-TCP/IP converter |
| Language | English |

# Contents

- [Integration Overview and Supported Functionality](#integration-overview-and-supported-functionality)
- [Compatibility, Dependencies and Licensed Devices](#compatibility-dependencies-and-licensed-devices)
- [Restrictions and Important Notes](#restrictions-and-important-notes)
- [How to Connect Device to C4](#how-to-connect-device-to-c4)
- [Device Configuration](#device-configuration)
- [Configuration Transfer and Device Discovery](#configuration-transfer-and-device-discovery)
- [Supported Identifiers](#supported-identifiers)
- [Credentials Synchronization](#credentials-synchronization)
- [Technology-Specific Functionality](#technology-specific-functionality)
- [Remote Device Control](#remote-device-control)
- [Status Information Display](#status-information-display)
- [Events and Audit Log](#events-and-audit-log)
- [Operation, Recovery and Maintenance](#operation-recovery-and-maintenance)
- [Troubleshooting and Support](#troubleshooting-and-support)
- [Integration Tests](#integration-tests)

The scope and restrictions in this manual apply to the integration described below. Test procedures define expected behavior and are not records of test execution.

# Integration Overview and Supported Functionality

## Purpose and scope

This manual describes the integration of the JABLOTRON JA-100 alarm system with C4 through a JA-121T communication module and an external RS485-to-TCP/IP converter. It covers connection, device configuration, credentials, remote commands, status monitoring and integration tests.

It is intended for system integrators, commissioning engineers and C4 administrators. The C4 Server communicates with the converter over TCP; the converter provides the serial connection to JA-121T.

## Device category

| Category | Source selection |
| :--- | :--- |
| IAS | Selected — intrusion alarm system |
| ACS, FPS, CCTV, DVR, Perimetry, Building, Other | Not selected |

## Supported functionality

S identifies a function selected as supported in the source manual. A dash means no support declaration was selected; it does not establish an additional supported capability. Restrictions below take precedence for the stated cases.

| ID | Functionality | State | Coverage |
| :--- | :--- | :--- | :--- |
| F01 | Import From File | — |  |
| F02 | Combined Credentials | — |  |
| F03 | Lift | — |  |
| F04 | Encrypted Communication | — |  |
| F05 | Load Configuration | S | T-CFG-01 |
| F06 | Time Synchronization | — |  |
| F07 | Time Zone Support | — |  |
| F08 | Live Video Streaming | — |  |
| F09 | Recorded Video Streaming | — |  |
| F10 | Video Records Downloading | — |  |
| F11 | Voice Transmitting | — |  |
| F12 | Audio Streaming | — |  |
| F13 | PTZ | — |  |
| F14 | Presets | — |  |
| F15 | Motion Detection | — |  |
| F16 | Live Stream Snapshot | — |  |
| F17 | Record Stream Snapshot | — |  |
| F18 | Multiple Stream Types | — |  |
| F19 | Person Data Read | — |  |
| F20 | Fire Panel Networking Mode | — |  |
| F21 | Card Learning | — |  |
| F22 | Dynamic Upload | S | Related upload procedures: T-UPL-01, T-UPL-02; dynamic trigger not specified |
| F23 | Access Time Restrictions | — |  |
| F24 | Holidays Support | — |  |
| F25 | PIN Management | S | T-ID-01, T-SEC-01 |
| F26 | Card Management | S | T-ID-02 |
| F27 | Fingerprint Management | — |  |
| F28 | Reserved Memory Zones | S | Reserved memory positions and user range |
| F29 | Anti-passback Forgiveness | — |  |
| F30 | Handicapped Flag | — |  |
| F31 | Alarm Suppression | — |  |
| F32 | Fire Alarm Counter | — |  |
| F33 | Device Audit Log Retrieval | — |  |
| F34 | Remote Device Control | S | T-IO-01, T-ALM-01, T-ALM-03 |
| F35 | Wiegand Biometric Support | — |  |
| F36 | Discovery | — |  |
| F37 | Sending Configuration | — |  |

## Terminology

A Section is an area, partition or group in the JA-100 system. A Detector represents an input or zone; a Fire Detector represents a supported smoke or CO input. A Relay represents a programmable PG output. The BUS Controller is the C4 connection endpoint, and its Central Unit represents the control panel.

# Compatibility, Dependencies and Licensed Devices

## Integration components

The following components are required:

- JABLOTRON JA-100 control panel – a supported control panel from the JA-100 series.
- JA-121T communication module – connected to the control panel bus and enrolled using F-Link.
- RS485-to-TCP/IP converter – for example, Papouch GNOME485, Lantronix, or another compatible converter supporting transparent serial communication over TCP/IP.
- Gamanet C4 – with the appropriate JABLOTRON driver installed and licensed.

The source identifies older JA-100K, JA-101K and JA-106K control panels in the multi-input-module restriction. That restriction does not establish a complete list of validated model, firmware, driver and C4 combinations.

## Licensed device

Control Panel

The License Attribute test checks that one licensed device node consumes one license. When the driver starts, C4 counts the instances marked with the Licensed attribute and requests that count from the installed license. See T-LIC-01.

# Restrictions and Important Notes

- Load Configuration: The driver automatically imports all sections and supported detectors. PG outputs must be added manually.
- Missing detectors: On older control panels (JA-100K, JA-101K and JA-106K), inputs 2 and higher on multi-input modules (e.g. JA-116H) may not be correctly identified during Load Configuration due to protocol limitations.
- Detector bypass: Remote bypass control from C4 is not supported.
- Partial arming: Partial arming of sections is not supported.
- Silent panic alarm: Only the alarm of the corresponding section is reported to C4, without detector identification.
- Selective Upload: Selective upload of individual users is not supported.

Full Upload clears the managed user positions before uploading the users and credentials assigned to the control panel in C4. Keep the reserved Service and Master positions outside the managed range.

The driver provides no configurable profiles. No upgrade or migration procedure is documented in the source manual.

# How to Connect Device to C4

## Topology and communication flows

The JABLOTRON JA-100 alarm system is connected to C4 using the JA-121T communication module and an external RS485-to-TCP/IP converter.

![JABLOTRON JA-100 topology: the control panel connects over the four-wire Jablotron Bus to JA-121T. A 12 V DC supply powers JA-121T. The JA-121T A/B pair connects to an RS485 to TCP/IP converter, which connects over LAN to the C4 server.](media/image1.png)

Figure 1 — Connection between C4 and the JABLOTRON JA-100 system.

## Device preparation and secure access

**Important:** The RS485 interface of the JA-121T module requires a separate 12 V DC power supply connected to the +U and GND terminals.

Configure the RS485-to-TCP/IP converter with the following communication parameters:

| Parameter | Value |
| :--- | :--- |
| Baud rate | 9600 |
| Data bits | 8 |
| Parity | None |
| Stop bits | 1 |
| Flow control | None |
| Network protocol | TCP |
| Operating mode | TCP Server |
| TCP port | Configurable, e.g. 10001 |

Configure the JA-121T module in F-Link for **Terminal mode**, with **Passive Mode disabled**.

To connect C4 to the JABLOTRON JA-100 control panel, configure the network connection between the C4 Server and the RS485-to-TCP/IP converter:

- Connect the C4 Server and the converter to the same network, or ensure IP connectivity between them.
- Configure a static IP address for the converter.
- If both devices are on the same local subnet, ensure their IP addresses and subnet masks are configured correctly.
- Ensure that the converter's TCP port is accessible from the C4 Server.

# Device Configuration

## Initial device tree

In C4 Client, open **Professional → Devices**. Right-click **Root** and select **Add → Jablotron** to create a new BUS Controller.

Configure the BUS Controller properties listed below, then save the configuration.

Right-click the newly created **Jablotron** BUS Controller and select **Add → Central Unit**.

Configure the Central Unit properties listed below. Keep Credential Upload Enabled disabled until user management is ready.

User positions **0 (Service)** and **1 (Master)** are reserved and must not be included in the range managed by C4.

Save the configuration.

Each Jablotron BUS Controller must contain exactly one Central Unit.

## BUS Controller

| Parameter | Description |
| :--- | :--- |
| Name | Name of the BUS Controller displayed in the C4 device tree. |
| IP Address | IP address of the RS485-to-TCP/IP converter. |
| Port | TCP port configured on the converter, e.g. 10001. |

## Central Unit

| Parameter | Description |
| :--- | :--- |
| Name | Name of the control panel displayed in the C4 device tree. |
| Pin | JABLOTRON user PIN configured for credential uploads. Typically, the Master PIN (user position 1) is used. An invalid PIN does not prevent communication, but it causes Full Upload or Incremental Upload to fail. |
| Credential Upload Enabled | Enables uploading users and credentials from C4 to the control panel. Keep disabled during initial configuration and enable when user management is ready. |
| Minimum Allowed User Number | First user position managed by C4. Must be at least 2 to prevent overwriting the reserved Service (0) and Master (1) users. |
| Maximum Allowed User Number | Last user position managed by C4, according to the capacity of the control panel. |

## Detector

Represents an input device in the JA-100 system, equivalent to a loop, input, or zone in other systems. It triggers an AlarmEvent in C4.

| Parameter | Range |
| :--- | :--- |
| Address | 1–230 |

## Fire Detector

Represents an input device in the JA-100 system. During Load Configuration, C4 uses the device type to import smoke and CO detectors as Fire Detectors. A Fire Detector generates a FireAlarmEvent in C4.

| Parameter | Range |
| :--- | :--- |
| Address | 1–230 |

## Section

Represents a section in the JA-100 system, equivalent to an area, partition, or group in other systems.

| Parameter | Range |
| :--- | :--- |
| Address | 1–15 |

## Relay

Represents a programmable output (PG) in the JA-100 system.

| Parameter | Description |
| :--- | :--- |
| Address | PG output number in the JA-100 system. |

## Profiles

The driver provides no configurable profiles.

# Configuration Transfer and Device Discovery

## Load Configuration

After configuring the BUS Controller and Central Unit, start communication and load the control panel configuration into C4.

| Step | Action |
| :--- | :--- |
| 1 | Right-click the Jablotron BUS Controller and select Commands → Start. |
| 2 | Wait until communication with the control panel is established. |
| 3 | Right-click the BUS Controller and select Commands → Load Configuration. |
| 4 | In the Add devices connection wizard, verify the IP address and TCP port and click Next. |
| 5 | Select the controller and click Load Configuration. |
| 6 | Wait for the Configuration In Progress operation to complete. |
| 7 | Verify the imported devices in the C4 device tree. |
| 8 | Restart the communication driver using Commands → Restart. |

Load Configuration automatically creates:

- Sections – all sections supported by the control panel, including unused sections.
- Detectors – supported security detectors, created as Detector objects.
- Fire Detectors – supported fire and CO detectors, created as Fire Detector objects.

PG outputs are not imported automatically. To add a PG output, right-click **Central Unit**, select **Add → Relay**, and configure its name and PG output address.

## Important Notes

- Section names can be configured manually in C4. Detector names are imported from the control panel when nodes are first created. Existing custom names in C4 are preserved during repeated Load Configuration.
- Only supported detector types are imported. Other peripherals, such as sirens, are not automatically added.
- Check the classification of detectors connected through input expansion modules. A manually created Fire Detector may be required.
- After every Load Configuration operation, restart the communication driver.
- Load Configuration can be repeated after changes to the control panel configuration. Newly added devices are imported, removed devices are archived, and existing custom device names are preserved.
- The addresses of manually added devices must correspond to the supported range of the particular control panel model.

# Supported Identifiers

## Supported PIN Lengths

4, 6, 8 digits

## Supported Cards

- EM Marine cards with 5-byte UID
- JABLOTRON JA-100 cards and keyfobs

## Credentials per person

Each person may have one PIN and zero, one or two cards or keyfobs. A person must have at least one valid credential and permission to control at least one section to be uploaded. Using a card or keyfob on a JA-100 keypad provides the same authorization as entering the person’s PIN.

Use a PIN length supported by the control panel configuration. If multiple PINs are assigned, the person is not uploaded during Full Upload and may be removed during Incremental Upload. If more than two cards or keyfobs are assigned, the person is not uploaded during Full Upload. Invalid credentials are reported in the audit log. See T-ID-01 and T-ID-02.

# Credentials Synchronization

## Managed user range and reserved positions

| Memory Position | Name |
| :--- | :--- |
| 0 | Service (Servis) |
| 1 | Master (Správce) |

Minimum Allowed User Number must be at least 2. Maximum Allowed User Number is limited by the connected control panel’s capacity. Positions 0 (Service) and 1 (Master) must not be included in the range managed by C4.

## Upload behavior

| Operation | Documented behavior |
| :--- | :--- |
| Full Upload | Clears the managed user positions and uploads all users and credentials assigned to the control panel in C4. |
| Incremental Upload | Uploads changes to users, credentials and section permissions. |
| Selective Upload | Selective upload of individual users is not supported. |
| Removal | A person is removed during upload if they have no valid PIN, card or keyfob, or no permission to control any section. |
| Interrupted upload | An upload interrupted by loss of communication is reported as failed. |

Enable Credential Upload Enabled when user management is ready. Confirm uploaded credentials and section permissions in F-Link or at a JA-100 keypad. A successful upload message must be distinguished from the physical authorization checks in T-ID-01, T-ID-02 and T-UPL-01.

# Technology-Specific Functionality

## Intrusion and tamper alarms

An intrusion alarm is reported on the Detector and its Section. Restore the input and use Disarm on the Section to clear the alarm, even if the section is already disarmed. For a Silent Panic reaction, the alarm is reported on the Section without identifying the detector. See T-ALM-01.

A detector tamper alarm is reported on the Detector and Section. Restore the tamper contact and use Disarm to clear the alarm. See T-ALM-03.

## Detector bypass

Input bypass (BLK in F-Link) and Device bypass (Disabled in F-Link) are reported as Bypass in C4 and logged as automatic operations without user attribution. Tamper bypass is not reported to C4. Remote bypass control from C4 is not supported. See T-ALM-02.

## Fire and CO detectors

Supported smoke and CO detectors are imported as Fire Detector nodes and generate FireAlarmEvent. Check input expansion modules carefully: a fire input may be imported as a Detector and require manual reclassification. The relevant address and import rules are given under Device Configuration and T-CFG-01.

## PG output behavior

PG outputs are represented by manually added Relay nodes. In F-Link, set Function to ON/OFF for permanent On and Off control. For timed activation, set Function to Impulse and specify the activation duration in Time. See T-IO-01.

# Remote Device Control

| Device | Command | Description |
| :--- | :--- | :--- |
| BUS Controller | Start | Starts communication with the control panel. |
| Stop | Stops communication with the control panel. |  |
| Restart | Restarts communication with the control panel. |  |
| Load Configuration | Reads the control panel configuration and updates the C4 device tree. |  |
| Central Unit | Incremental Upload | Uploads changes to users and credentials. |
| Full Upload | Clears the managed user positions and uploads all users and credentials assigned to the control panel in C4. |  |
| Section | Arm | Arms the section. |
| Disarm | Disarms the section. |  |
| Detector | — | No remote control commands are available. |
| Fire Detector | — | No remote control commands are available. |
| Relay | On | Activates the PG output. |
| Off | Deactivates the PG output. |  |

The command audit messages distinguish an operator’s request, command delivery and the reported output state. Verify actual PG output activation and deactivation independently as described in T-IO-01.

# Status Information Display

## BUS Controller

| Icon | Status | Description |
| :---: | :--- | :--- |
| ![BUS Controller: Unknown status icon.](media/image2.png) | Unknown | Communication is stopped. All subordinate devices have Unknown status. |
| ![BUS Controller: Idle status icon.](media/image3.png) | Idle | Communication is established and running normally. |
| ![BUS Controller: Starting status icon.](media/image4.png) | Starting | The driver is starting communication. |
| ![BUS Controller: Reading Device Configuration status icon.](media/image5.png) | Reading Device Configuration | Load Configuration is reading the control panel configuration. |
| ![BUS Controller: Disconnected status icon.](media/image6.png) | Disconnected | Communication with the converter or over RS485 has been lost. All subordinate devices have Unknown status. |
| ![BUS Controller: Configuration Failure status icon.](media/image7.png) | Configuration Failure | The driver configuration is invalid. |

## Central Unit

| Icon | Status | Description |
| :---: | :--- | :--- |
| ![Central Unit: Unknown status icon.](media/image8.png) | Unknown | The control panel status is unknown. |
| ![Central Unit: Idle status icon.](media/image9.png) | Idle | The control panel is operating normally. |
| ![Central Unit: Uploading Credentials status icon.](media/image10.png) | Uploading Credentials | Users and credentials are being uploaded to the control panel. |
| ![Central Unit: Tamper status icon.](media/image11.png) | Tamper | A control panel tamper alarm is reported. |
| ![Central Unit: Configuration Failure status icon.](media/image12.png) | Configuration Failure | The configured user range exceeds the detected control panel limits. |

## Section

| Icon | Status | Description |
| :---: | :--- | :--- |
| ![Section: Unknown status icon.](media/image13.png) | Unknown | The section status is unknown. |
| ![Section: Disarmed status icon.](media/image14.png) | Disarmed | The section is disarmed. |
| ![Section: Armed status icon.](media/image15.png) | Armed | The section is armed. |
| ![Section: Alarm status icon.](media/image16.png) | Alarm | An alarm is reported in the section. |
| ![Section: Tamper status icon.](media/image17.png) | Tamper | A tamper alarm is reported in the section. |
| ![Section: Configuration Failure status icon.](media/image18.png) | Configuration Failure | The section address is outside the supported range. |

## Detector

| Icon | Status | Description |
| :---: | :--- | :--- |
| ![Detector: Unknown status icon.](media/image19.png) | Unknown | The detector status is unknown. |
| ![Detector: Idle status icon.](media/image20.png) | Idle | The detector input is inactive. |
| ![Detector: Activated status icon.](media/image21.png) | Activated | The detector input is active without an alarm (the section is disarmed). |
| ![Detector: Alarm status icon.](media/image22.png) | Alarm | An alarm is reported by the detector. |
| ![Detector: Tamper status icon.](media/image23.png) | Tamper | A detector tamper alarm is reported. |
| ![Detector: Bypass status icon.](media/image24.png) | Bypass | The detector is bypassed. |
| ![Detector: Configuration Failure status icon.](media/image25.png) | Configuration Failure | The detector address is outside the supported range. |

## Fire Detector

| Icon | Status | Description |
| :---: | :--- | :--- |
| ![Fire Detector: Unknown status icon.](media/image26.png) | Unknown | The fire detector status is unknown. |
| ![Fire Detector: Idle status icon.](media/image27.png) | Idle | The fire detector input is inactive. |
| ![Fire Detector: Fire Alarm status icon.](media/image28.png) | Fire Alarm | A fire alarm is reported by the detector. |
| ![Fire Detector: Tamper status icon.](media/image29.png) | Tamper | A fire detector tamper alarm is reported. |
| ![Fire Detector: Bypass status icon.](media/image30.png) | Bypass | The fire detector is bypassed. |
| ![Fire Detector: Configuration Failure status icon.](media/image31.png) | Configuration Failure | The fire detector address is outside the supported range. |

## Relay

| Icon | Status | Description |
| :---: | :--- | :--- |
| ![Relay: Unknown status icon.](media/image32.png) | Unknown | The PG output status is unknown. |
| ![Relay: Idle status icon.](media/image33.png) | Idle | The PG output is off. |
| ![Relay: Activated status icon.](media/image34.png) | Activated | The PG output is on. |
| ![Relay: Configuration Failure status icon.](media/image35.png) | Configuration Failure | The PG output address is outside the supported range. |

# Events and Audit Log

The integration reports connection and configuration events, command activity, credential upload results, alarms, bypass changes and control-panel power events. Exact source message text and variable meanings are preserved with the corresponding test procedures.

| Event group | Reported context | Procedure |
| :--- | :--- | :--- |
| Configuration and connection | BUS Controller; invalid configuration can also identify the affected device node. | T-CFG-01 to T-CFG-05; T-CON-01 and T-CON-02 |
| Intrusion and tamper | Detector and Section; Silent Panic identifies the Section only. | T-ALM-01 and T-ALM-03 |
| Input and Device bypass | Detector; both changes are logged as automatic bypass events without user identification. | T-ALM-02 |
| PG output control | Relay; request, delivery and actual state messages are distinct. | T-IO-01 |
| Credential upload | Central Unit; failed people and warning or failure outcomes are reported. | T-ID-01, T-ID-02, T-UPL-02 and T-SEC-01 |
| Mains and backup battery | Central Unit audit log; these events do not set the node to a fault state. | T-HEA-01 and T-HEA-02 |

# Operation, Recovery and Maintenance

## Connection and driver state

When communication is stopped, the BUS Controller and its subordinate devices have Unknown status. Loss of communication sets the BUS Controller to Disconnected and its children to Unknown. After communication is reestablished, device nodes return to their actual states.

Restart the communication driver after every Load Configuration operation. Correct invalid addresses, duplicate devices and nonexistent bus devices before starting communication. T-CON-02 and the configuration tests describe the expected states and audit evidence.

## Uploads and operational restoration

Full Upload replaces data in the managed user range. Keep the reserved Service and Master positions excluded. An interrupted upload is reported as failed; check the resulting users and permissions before considering the operation complete.

After an authorized alarm, bypass, PG output or power test, restore the original configuration and physical condition. The individual test cleanup instructions identify the relevant restoration steps; their successful execution must be recorded separately.

# Troubleshooting and Support

| Symptom | Checks | Action / evidence |
| :--- | :--- | :--- |
| No communication | Converter address/port; IP connectivity; 9600 baud, 8 data bits, no parity, 1 stop bit; TCP Server mode; JA-121T Terminal mode and separate 12 V DC supply. | Check the connection setup, then Start. Verify connection events and device states. |
| Configuration Failure at startup | Duplicate addresses, an address beyond the detected panel limit, or a Detector node absent from the bus. | Correct the configuration and restart communication. Inspect both the device and BUS Controller audit messages. |
| PG output missing after Load Configuration | PG outputs are not imported automatically. | Add a Relay under Central Unit and set its PG output address. |
| Fire input classified as Detector | Input expansion modules may not supply the expected classification. | Create the Fire Detector with the same address, remove the incorrect Detector node and restart. |
| Inputs missing on an older panel | JA-100K, JA-101K or JA-106K; input 2 or higher on a multi-input module such as JA-116H. | Apply the documented protocol limitation; verify the supported input mapping before relying on it. |
| Credential upload fails | Central Unit Pin, upload enablement, managed range, supported credentials and section permissions. | Review T-ID-01, T-ID-02 and T-SEC-01 and the recorded upload error. |
| Mains or battery event without a fault status | Power events are logged on Central Unit without setting a fault state. | Use the audit log and physical condition; see T-HEA-01 and T-HEA-02. |

## Diagnostic information

For investigation, record the installed C4 and driver versions, control-panel model and firmware, converter settings, affected device address, reproduction steps and relevant audit messages. Record configured limits and measured delays from the test environment. Keep actual PIN values out of the diagnostic record.

# Integration Tests

## Scope and execution conditions

These procedures cover the integration behavior described in this manual. Run them on an authorized test installation with the appropriate C4 and JABLOTRON permissions. Alarm, bypass, output, credential and power tests change the installation state; prepare the relevant isolation and restoration before execution.

Record the actual model, firmware, C4 version, driver version and configured limits for the tested combination. The procedures describe expected results; no execution PASS is implied. Detection, reconnection and delivery limits must be approved for the test environment before timing is used as an acceptance criterion.

## Procedure index

| ID | Procedure |
| :--- | :--- |
| T-LIC-01 | License Attribute |
| T-GEN-01 | Driver Copyright |
| T-CFG-01 | Download Configuration |
| T-CON-01 | DNS Name Resolving |
| T-CFG-02 | Duplicated Addresses |
| T-CFG-03 | Missing HW Item |
| T-CON-02 | Network Connection Lost |
| T-CFG-04 | Property Value Validation |
| T-IO-01 | Output Activation and Deactivation |
| T-ALM-01 | Intrusion Alarm |
| T-ALM-02 | Detector Bypass On and Bypass Off from Device |
| T-ID-01 | Personal Management - PIN Management |
| T-ID-02 | Personal Management - Card Management |
| T-UPL-01 | Upload Scenarios |
| T-UPL-02 | Disconnection During Sending Credentials to Device |
| T-ALM-03 | Tamper |
| T-CFG-05 | Device Tree Configuration Validation |
| T-SEC-01 | Attempt to Connect with Invalid Connection Credentials |
| T-HEA-01 | Mains Failure |
| T-HEA-02 | Battery Failure |

## T-LIC-01 | License Attribute

**Description:** This test verifies the correct implementation of the Licensed attribute in the driver.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a valid device tree with one licensed device node and an installed license from which the required count can be requested.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Create a device tree with one licensed device node. | The device tree contains one licensed device node. |
| 2 | Start the endpoint and check the BUS Controller license. | When one licensed device node is present, one license is consumed for this driver. |

**Notes:**

- When the driver is started, the system calculates the number of instances marked with the Licensed attribute and requests that amount from the currently installed license.

**Cleanup:** Restore the original device tree and driver operating state if temporary nodes or state changes were introduced for the test.

## T-GEN-01 | Driver Copyright

**Description:** This test verifies whether the driver copyright information is defined correctly.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Make the installed driver’s copyright information available for inspection. The expected copyright value is not supplied by the source.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Check the driver copyright information. | None |

**Cleanup:** None. This test only inspects driver information.

## T-CFG-01 | Download Configuration

**Description:** This test verifies the correct implementation of configuration retrieval from the device. The plugin retrieves supported device nodes and properties according to the current control panel configuration.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Configure the BUS Controller connection settings and add one Central Unit manually before executing Load Configuration.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Start the endpoint. | The endpoint is running before Load Configuration is executed. |
| 2 | Execute the “Load Configuration” wizard. | Configuration retrieval starts. |
| 3 | Wait until the configuration is downloaded from the device. | The device tree and supported properties are successfully imported. |

**Expected audit / evidence:**

'PERSON' sent command 'Load Configuration' to 'DEVICE'.

Configuration retrieval from 'DEVICE' started.

Configuration succesfully retrieved from 'DEVICE'.

**Where:**

- DEVICE represents the name of the BUS Controller.
- PERSON represents the name of the person who executed the command.

**Notes:**

- A Central Unit must be added manually before executing Load Configuration. The BUS Controller must be running.
- Supported input devices are imported as Detector nodes. Supported smoke and CO detectors are imported as Fire Detector nodes.
- Fire detectors connected through input expansion modules are imported as Detector nodes. Manually create a Fire Detector node with the same address and delete the incorrectly classified Detector node.
- All Section nodes supported by the detected control panel model are imported, including unused sections. The protocol does not identify which sections are actually used. Unused sections can be deleted manually.
- Relay nodes are not imported and must be added manually.
- Detector names are imported from the control panel when the nodes are first created. Repeating Load Configuration preserves their existing names in C4.
- Other peripherals, such as sirens, are not imported automatically. They can be added manually if they support input functionality.
- Restart the communication driver after Load Configuration.

**Cleanup:** Complete any required node corrections described in the source notes and restart the communication driver after Load Configuration.

## T-CON-01 | DNS Name Resolving

**Description:** This test verifies the behavior of the driver when a DNS name is entered in the IP Address field.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use the DNS name of the RS485-to-TCP/IP converter and otherwise valid communication settings.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Enter the DNS name of the converter in the IP Address field. | The converter DNS name is entered in the IP Address field. |
| 2 | Start the endpoint. | The endpoint successfully connects to the device. All device nodes under the endpoint are set to their actual states. |

**Expected audit / evidence:**

'DEVICE' started.

'DEVICE' successfully connected to the device.

**Where:**

- DEVICE represents the driver name.

**Cleanup:** Restore the original IP Address value if it was changed for this test, then restore normal communication.

## T-CFG-02 | Duplicated Addresses

**Description:** This test checks whether the driver detects duplicate addresses for each device type. Its purpose is to ensure that the device configuration tree does not contain multiple nodes representing the same device.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a working baseline configuration. Repeat the test independently for each addressable device type that can be created in the device tree.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Stop the endpoint. | The endpoint is stopped. |
| 2 | Create two devices of the same type identified by an address in the device configuration tree. | Two devices of the same addressable type exist in the device configuration tree. |
| 3 | Set the same address for both devices. | Both devices have the same configured address. |
| 4 | Start the endpoint. | Both devices with the same address and the BUS Controller are set to Configuration Failure. All other subordinate devices are set to Unknown. The endpoint does not complete initialization and stops. |

**Expected audit / evidence:**

Invalid configuration detected on device 'DEVICE1'. More details: 'Duplicate detector with hardware address ADDRESS'

Invalid configuration detected on device 'DEVICE2'. More details: 'Duplicate detector with hardware address ADDRESS'

Invalid configuration detected on device 'BUS\_CONTROLLER'. More details: 'Configuration has errors'

**Where:**

- DEVICE1 and DEVICE2 represent the names of the detectors sharing the same address.
- ADDRESS represents the duplicate hardware address.
- BUS\_CONTROLLER represents the name of the BUS Controller.

**Notes:**

- Repeat this test for each addressable device type that can be created in the device tree.
- The messages above show an example for duplicate Detector addresses. The first two messages are logged on the respective Detector nodes. The last message is logged on the BUS Controller.
- The BUS Controller and both devices sharing the same address are set to the Configuration Failure state. All other subordinate devices are set to the Unknown state.

**Cleanup:** Stop the endpoint, remove the duplicate test node or restore unique valid addresses, and start the endpoint with the valid baseline configuration.

## T-CFG-03 | Missing HW Item

**Description:** This test verifies the behavior of the driver when a device is present in the JA-100 system but its node is missing from the C4 device tree.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Choose a node that can be removed without affecting basic communication. Keep the BUS Controller and Central Unit nodes.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Stop the endpoint. | The endpoint is stopped. |
| 2 | Remove a device node from the C4 device tree while keeping the physical device in the JA-100 system. | The selected node is absent from the C4 device tree while its physical device remains in the JA-100 system. The BUS Controller and Central Unit nodes remain present. |
| 3 | Start the endpoint. | The endpoint starts and continues to operate. No missing-device warning is recorded in the audit log. |
| 4 | Generate activity on the device whose node is missing. | Related events are reported on existing nodes where applicable. For example, an alarm triggered by a detector whose node is missing is reported on its Section node. No missing-device warning is recorded in the audit log. |

**Notes:**

- During startup, only devices defined in the C4 device tree can be validated.
- Repeat this test for device types whose nodes can be removed without affecting basic communication. Keep the BUS Controller and Central Unit nodes.

**Cleanup:** Restore the removed C4 node and its original settings, and restore any input or Section state changed to generate test activity.

## T-CON-02 | Network Connection Lost

**Description:** This test verifies the behavior of the driver when the connection between the C4 Server and the RS485-to-TCP/IP converter is lost.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a working connection between C4 Server and the RS485-to-TCP/IP converter. Interrupt it at a switch or router while keeping the C4 Server’s Ethernet link active.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Start the endpoint. | The endpoint starts communication. |
| 2 | Wait until communication is established. | Communication is established before the connection is interrupted. |
| 3 | Interrupt the connection on the switch or router while keeping the C4 Server’s Ethernet link active. | The network connection is interrupted while the C4 Server’s Ethernet link remains active. |
| 4 | Wait until the disconnection is indicated. | The BUS Controller is set to Disconnected. All subordinate devices are set to Unknown. |
| 5 | Keep the connection interrupted for two minutes. | For the two-minute interruption, the BUS Controller remains Disconnected and subordinate devices remain Unknown. No additional audit log message indicates a reconnection attempt. |
| 6 | Restore the connection. | The network connection is restored. |
| 7 | Wait until communication is reestablished. | Communication is reestablished and all device nodes return to their actual states. |

**Expected audit / evidence:**

Network connection interrupted to 'DEVICE'.

'DEVICE' successfully connected to the device.

**Where:**

- DEVICE represents the name of the BUS Controller.

**Notes:**

- During the interruption, the BUS Controller remains in the Disconnected state and subordinate devices remain in the Unknown state. No additional audit log message indicates a reconnection attempt.

**Cleanup:** Confirm the network connection is restored, communication is reestablished, and device nodes have returned to their actual states.

## T-CFG-04 | Property Value Validation

**Description:** This test verifies the behavior of the driver when a configuration value is outside the allowed range or has an invalid format. It also verifies that the driver detects invalid values during startup.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Begin each invalid-property case with an otherwise valid configuration; apply the coverage and address-validation rules in Notes.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Stop the endpoint. | The endpoint is stopped. |
| 2 | Set a property value outside the allowed range or enter an invalid format. | A property with an invalid value is highlighted with a red border if regular expression validation is implemented for that property. |
| 3 | Start the endpoint. | For an address that passes regular expression validation but exceeds the connected control panel’s limit, startup detects the error and logs it on the affected device node and on the BUS Controller. |

**Notes:**

- Repeat this test for every validated property of each device type.
- Test values outside the allowed range and values in an invalid format.
- For newly created devices, also try leaving the value empty.
- Address validation for Section, Relay, Detector, and Fire Detector uses the maximum supported range across JA-100 control panel models.
- An address may pass regular expression validation but exceed the limit of the connected control panel model. The driver detects this during startup. An error is logged on the affected device node and on the BUS Controller.

Invalid configuration detected on device 'DEVICE'. More details: 'DEVICE\_TYPE hardware address ADDRESS exceeds maximum MAX\_ADDRESS'

Invalid configuration detected on device 'BUS\_CONTROLLER'. More details: 'Configuration has errors'

**Where:**

- DEVICE represents the name of the device with an invalid address.
- DEVICE\_TYPE represents the device type, such as Section.
- ADDRESS represents the configured hardware address.
- MAX\_ADDRESS represents the maximum address supported by the connected control panel.
- BUS\_CONTROLLER represents the name of the BUS Controller.

**Cleanup:** Restore the valid property value and baseline configuration before the next case. Start the endpoint with valid configuration after testing.

## T-IO-01 | Output Activation and Deactivation

**Description:** This test verifies monitoring and control of PG outputs represented by Relay nodes in C4.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a manually configured Relay node for the corresponding PG output. Set the PG output’s Function to ON/OFF in F-Link for this permanent activation/deactivation test.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Execute the “On” command on a Relay node. | The corresponding PG output activates and the Relay node is set to Activated. |
| 2 | Verify that the corresponding PG output is activated. | The PG output is active and the Relay node is set to Activated. |
| 3 | Execute the “Off” command on the Relay node. | The corresponding PG output deactivates and the Relay node is set to Idle. |
| 4 | Verify that the corresponding PG output is deactivated. | The PG output is inactive and the Relay node is set to Idle. |

**Expected audit / evidence:**

Command 'On' from 'PERSON' was delivered to 'DEVICE'.

'PERSON' sent command 'On' to 'DEVICE'.

'DEVICE' turned on.

'PERSON' sent command 'Off' to 'DEVICE'.

Command 'Off' from 'PERSON' was delivered to 'DEVICE'.

'DEVICE' turned off.

**Where:**

- PERSON represents the name of the person who executed the command.
- DEVICE represents the name of the Relay node.

**Notes:**

- For permanent activation and deactivation using the C4 On and Off commands, set the PG output’s Function to ON/OFF in F-Link.
- For timed activation, set Function to Impulse and specify the activation duration in Time.

**Cleanup:** Leave the PG output deactivated as in the final test step. Restore any PG Function or Time settings changed solely for testing.

## T-ALM-01 | Intrusion Alarm

**Description:** This test verifies the behavior of the driver when an intrusion alarm is triggered and cleared.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a configured Detector and its corresponding Section. Distinguish the Silent Panic reaction, which reports the alarm on the Section without identifying the detector.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Arm the section containing the detector. | The section containing the detector is armed. |
| 2 | Trigger an alarm on the detector. | For an ordinary detector alarm, the Detector and its Section are set to Alarm. For the Silent Panic reaction, the alarm is reported on the corresponding Section node without identifying the detector. |
| 3 | Check the states of the Detector and its Section in C4. | For an ordinary detector alarm, the Detector and its Section show Alarm. For Silent Panic, the Section reports the alarm without identifying the detector. |
| 4 | Restore the detector input to its inactive state. | The detector input is inactive. Use Disarm in the following step to clear the alarm. |
| 5 | Execute the Disarm command on the corresponding Section node. | After the alarm is cleared using Disarm, the Detector returns to Idle and the Section is set to Disarmed. |

**Expected audit / evidence:**

Alarm on 'DETECTOR'.

Alarm on 'SECTION'.

Alarm on 'DETECTOR' restored.

Alarm on 'SECTION' restored.

**Where:**

- DETECTOR represents the name of the detector that triggered the alarm.
- SECTION represents the name of the corresponding section.

**Notes:**

- Use the Disarm command on the corresponding Section node to clear the alarm, even if the section is already disarmed.
- For a device configured with the Silent Panic reaction, the alarm is reported on the corresponding Section node without identifying the detector.

**Cleanup:** Confirm the detector input is inactive, use Disarm to clear the test alarm, and confirm the Detector is Idle and the Section is Disarmed.

## T-ALM-02 | Detector Bypass On and Bypass Off from Device

**Description:** This test verifies that C4 reports Input and Device bypass changes performed directly in the JA-100 system.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a Detector whose Input bypass and Device bypass can be changed in F-Link. The detector input must be inactive when checking the Idle state after cancelling bypass.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Apply Input bypass (BLK in F-Link) to a detector. | The Detector node is set to Bypass. |
| 2 | Check the Detector state in C4. | The Detector node shows Bypass. |
| 3 | Cancel Input bypass and check the Detector state in C4. | After bypass is cancelled and the detector input is inactive, the Detector node is set to Idle. |
| 4 | Repeat the test using Device bypass (Disabled in F-Link). | Device bypass sets the Detector to Bypass. Cancelling it returns the Detector to Idle when the input is inactive. The same audit log messages are recorded for Input and Device bypass. |

**Expected audit / evidence:**

'DEVICE' was bypassed automatically.

'DEVICE' bypass was cancelled automatically.

**Where:**

- DEVICE represents the name of the detector.

**Notes:**

- Tamper bypass blocks only tamper detection and has no separate status indication in F-Link. Its bypass status is not reported to C4 and cannot be evaluated by the driver.
- Bypass events do not identify the user who performed the operation. Input and Device bypass are both logged as automatic bypass events.

**Cleanup:** Cancel both Input bypass and Device bypass applied during the test. With the detector input inactive, confirm the Detector returns to Idle.

## T-ID-01 | Personal Management - PIN Management

**Description:** This test verifies that PIN credentials and section permissions are correctly transferred to the JA-100 control panel.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Enable Credential Upload Enabled when user management is ready, use a valid Central Unit PIN and a managed user range from position 2 up to the actual panel capacity, and use one PIN of a supported length per person.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Create a new person in C4. | The new person exists in C4. |
| 2 | Grant the person permission to control the required sections. | The person has permission to control the required sections in C4. |
| 3 | Assign a valid PIN to the person. | One valid PIN of a length supported by the control panel configuration is assigned to the person. |
| 4 | Upload the credentials to the control panel. | The person’s PIN and section permissions are correctly configured in the control panel. |
| 5 | Verify the transferred PIN and section permissions in F-Link or by using the PIN on a JA-100 keypad. | The transferred PIN and section permissions match the person’s C4 configuration, and the PIN allows the person to control the assigned sections. |

**Notes:**

- Use a PIN with a length supported by the control panel configuration.
- Each person may have only one PIN. If multiple PINs are assigned in C4, the person is not uploaded during Full Upload and may be removed from the control panel during Incremental Upload.
- Invalid credentials are reported in the audit log. The following messages show the person-level error and the Full Upload result:

'PERSON' failed to upload to 'DEVICE' due to invalid credential

'Full' upload to 'DEVICE' successfully completed with warning

- PERSON represents the name of the affected person.
- DEVICE represents the name of the Central Unit.

**Cleanup:** Remove section permissions from the temporary test person and upload that change so the person is removed from the control panel. Restore any pre-test settings changed for the case.

## T-ID-02 | Personal Management - Card Management

**Description:** This test verifies that card credentials and section permissions are correctly transferred to the JA-100 control panel.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Enable Credential Upload Enabled when user management is ready, use a valid Central Unit PIN and a managed user range from position 2 up to the actual panel capacity, and use valid cards or keyfobs. A person must have at least one valid credential.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Create a new person in C4. | The new person exists in C4. |
| 2 | Grant the person permission to control the required sections. | The person has permission to control the required sections in C4. |
| 3 | Assign a valid card or keyfob to the person. | One valid card or keyfob is assigned to the person. |
| 4 | Upload the credentials to the control panel. | The person’s assigned card and section permissions are correctly configured in the control panel. |
| 5 | Verify the transferred card and section permissions in F-Link or by using the card on a JA-100 keypad. | The transferred card and section permissions match the person’s C4 configuration. The card provides authorization to control the assigned sections. |
| 6 | Assign a second valid card or keyfob to the same person, repeat the upload, and verify that both credentials work. | Both cards or keyfobs and the section permissions are correctly configured in the control panel. Both credentials allow the person to control the assigned sections. |

**Expected audit / evidence:**

'UPLOAD\_TYPE' upload to 'DEVICE' started.

'UPLOAD\_TYPE' upload to 'DEVICE' successfully completed (duration 'UPLOAD\_DURATION').

**Where:**

- UPLOAD\_TYPE represents the upload type, such as Full or Incremental.
- DEVICE represents the name of the Central Unit.
- UPLOAD\_DURATION represents the upload duration.

### T-ID-02 | Card Management — continued

**Notes:**

- Each person may have zero, one, or two cards or keyfobs.
- Using a card or keyfob on a JA-100 keypad provides the same authorization as entering the person’s PIN.
- A person must have at least one valid credential to be uploaded to the control panel.
- If more than two cards or keyfobs are assigned to a person, that person is not uploaded during Full Upload. The following messages are recorded:

'PERSON' failed to upload to 'DEVICE' due to invalid credential.

'UPLOAD\_TYPE' upload to 'DEVICE' successfully completed with warning (duration'UPLOAD\_DURATION').

- PERSON represents the name of the affected person.

**Cleanup:** Remove section permissions from the temporary test person and upload that change so the person is removed from the control panel. Restore any pre-test settings changed for the case.

## T-UPL-01 | Upload Scenarios

**Description:** This test verifies that Full Upload and Incremental Upload correctly apply changes to users and section permissions.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use two configured Sections, A and B, and a valid credential. Enable credential upload with a valid Central Unit PIN and a valid managed user range.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Create a person with at least one valid PIN, card, or keyfob and permission to control Section A only. | The person has at least one valid credential and permission to control Section A only in C4. |
| 2 | Perform Full Upload and verify that the person can control Section A but cannot control Section B. | Full Upload transfers the person’s credential and section permissions correctly. The person can control Section A but cannot control Section B. |
| 3 | Change the person’s permissions to Section B only. | The person’s C4 permissions are changed to Section B only. |
| 4 | Perform Incremental Upload and verify that the person can control Section B but cannot control Section A. | Incremental Upload applies the permission change correctly. The person can control Section B but cannot control Section A. |
| 5 | Remove all section permissions from the person. | The person has no section permissions in C4. |
| 6 | Perform Incremental Upload and verify that the person can no longer control either section. | After Incremental Upload, the credential no longer authorizes control of either section. The person is removed from the control panel because no section permission remains. |

**Notes:**

- A person is removed from the control panel during upload if they have no valid PIN, card, or keyfob, or no permission to control any section.

**Cleanup:** Confirm the final Incremental Upload has removed the test person’s authorization for both Sections. The source states that a person without any Section permission is removed from the control panel during upload.

## T-UPL-02 | Disconnection During Sending Credentials to Device

**Description:** This test verifies the behavior of the driver when communication is interrupted during a credential upload.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use an otherwise working credential-upload configuration and an upload long enough to interrupt while it is in progress.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Start a credential upload to the control panel. | The credential upload starts and is in progress before the interruption. |
| 2 | Interrupt the connection while the upload is in progress. | The upload fails due to the communication interruption. |

**Expected audit / evidence:**

'PERSON' sent command 'UPLOAD\_TYPE' to 'DEVICE'.

Command 'UPLOAD\_TYPE' from 'PERSON' was delivered to 'DEVICE'.

'UPLOAD\_TYPE' upload to 'DEVICE' started.

'UPLOAD\_TYPE' upload failed in 'DEVICE' (duration'UPLOAD\_DURATION').

**Where:**

- PERSON represents the name of the person who started the upload.
- UPLOAD\_TYPE represents the upload type, such as Full or Incremental.
- DEVICE represents the name of the Central Unit.
- UPLOAD\_DURATION represents the elapsed time from the start of the upload until its interruption.

**Cleanup:** Restore the interrupted connection and wait until normal communication is reestablished. Reapply the intended user and credential configuration using the documented upload commands and verify it before subsequent tests. The source does not define automatic resume, rollback, or retry behavior after an interrupted upload.

## T-ALM-03 | Tamper

**Description:** This test verifies the behavior of the driver when a tamper alarm is triggered and cleared.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use a detector that reports a tamper alarm and its corresponding Section. Begin with the Section disarmed and repeat for all supported device types that report tamper alarms.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Trigger a tamper alarm on a detector while its section is disarmed. | The Detector and its Section are set to Tamper. |
| 2 | Check the Detector and Section states in C4. | The Detector and its Section show Tamper. |
| 3 | Restore the detector’s tamper contact. | The detector’s tamper contact is restored. Use Disarm in the following step to clear the tamper alarm. |
| 4 | Execute the Disarm command on the corresponding Section node. | After the tamper contact is restored and the alarm is cleared using Disarm, the Detector returns to Idle and the Section returns to Disarmed. |
| 5 | Check the Detector and Section states in C4. | The Detector shows Idle and the Section shows Disarmed. |

**Expected audit / evidence:**

Tamper on 'DETECTOR'.

Tamper on 'SECTION'.

Tamper completed on 'DETECTOR'.

Tamper completed on 'SECTION'.

**Where:**

- DETECTOR represents the name of the detector reporting the tamper alarm.
- SECTION represents the name of the corresponding section.

**Notes:**

- Use the Disarm command on the corresponding Section node to clear the tamper alarm, even if the section is already disarmed.
- Repeat this test for all supported device types that report tamper alarms.

**Cleanup:** Restore the tamper contact, use Disarm to clear the test alarm, and confirm the Detector is Idle and the Section is Disarmed.

## T-CFG-05 | Device Tree Configuration Validation

**Description:** This test verifies the behavior of the driver when the C4 device tree contains a device that is not present on the JA-100 bus.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use an otherwise valid device tree and a Detector address inside the supported range that is not assigned to a physical device on the JA-100 bus.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Stop the endpoint. | The endpoint is stopped. |
| 2 | Add a Detector node with an address that is within the supported range but does not correspond to a device on the bus. | The added Detector node uses an address within the supported range that does not correspond to a physical device on the JA-100 bus. |
| 3 | Start the endpoint. | The nonexistent Detector node and the BUS Controller are set to Configuration Failure. All other subordinate devices are set to Unknown. The driver does not start; the configuration error must be corrected before communication can start. |
| 4 | Check the device states and audit log in C4. | The failure states remain visible. The Detector audit message reports that it was not found on the bus, and the BUS Controller audit message reports that the configuration has errors. |

**Expected audit / evidence:**

Invalid configuration detected on device 'DEVICE'. More details: 'Detector not found on the bus'

Invalid configuration detected on device 'BUS\_CONTROLLER'. More details: 'Configuration has errors'

**Where:**

- DEVICE represents the name of the Detector node whose address does not correspond to a device on the bus.
- BUS\_CONTROLLER represents the name of the BUS Controller.

**Notes:**

- The first message is logged on the Detector node. The second message is logged on the BUS Controller.

**Cleanup:** Remove the nonexistent Detector test node or correct its configuration to the valid baseline before starting communication again.

## T-SEC-01 | Attempt to Connect with Invalid Connection Credentials

**Description:** This test verifies the behavior of the driver when an invalid PIN is configured on the Central Unit and a credential upload is attempted.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Use otherwise valid communication and credential-upload settings; change only the Central Unit’s Pin property to an invalid value for this case.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Stop the endpoint. | The endpoint is stopped. |
| 2 | Set an invalid PIN in the Central Unit’s Pin property. | An invalid PIN is set in the Central Unit’s Pin property. |
| 3 | Start the endpoint and wait until communication is established. | Communication is established despite the invalid PIN. |
| 4 | Execute Full Upload or Incremental Upload. | The credential upload fails. |
| 5 | Check the upload result in the audit log. | The audit log records the failed credential upload. |

**Expected audit / evidence:**

'UPLOAD\_TYPE' upload failed in 'DEVICE' (duration'UPLOAD\_DURATION').

**Where:**

- UPLOAD\_TYPE represents the upload type, Full or Incremental.
- DEVICE represents the name of the Central Unit.
- UPLOAD\_DURATION represents the elapsed time from the start of the upload until its failure.

**Notes:**

Communication is established without using the PIN. This test verifies that an invalid PIN causes Full Upload or Incremental Upload to fail.

**Cleanup:** Restore the valid Central Unit Pin value and the normal credential-upload configuration before subsequent tests.

## T-HEA-01 | Mains Failure

**Description:** This test verifies that a control panel mains power failure and its restoration are reported in C4.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Keep the control panel’s backup battery connected while disconnecting the mains supply.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Disconnect the control panel’s mains supply while keeping its backup battery connected. | The mains supply is disconnected and the backup battery remains connected. |
| 2 | Wait until the mains failure event is recorded in C4. | The mains failure event is recorded in the audit log on the Central Unit node. This event does not set the Central Unit to a fault state. |
| 3 | Restore the mains supply. | The mains supply is restored. |
| 4 | Wait until the mains restoration event is recorded in C4. | The mains restoration event is recorded in the audit log on the Central Unit node. This event does not set the Central Unit to a fault state. |

**Expected audit / evidence:**

'DEVICE' mains failed.

Restore 'DEVICE' after a mains failure.

**Where:**

- DEVICE represents the name of the Central Unit.

**Notes:**

- Mains failure reporting has no configured delay to filter out short outages.
- Mains failure and restoration events may take several seconds to appear in C4.

**Cleanup:** Confirm the mains supply is restored and the Central Unit audit log records restoration, with the backup battery still connected.

## T-HEA-02 | Battery Failure

**Description:** This test verifies that a control panel backup battery failure and its restoration are reported in C4.

Applicability: Configured JA-100 test installation and the device types named below.

**Prerequisites:** Keep the control panel’s mains supply connected while disconnecting the backup battery.

| Step | Test Steps | Expected Results |
| :---: | :--- | :--- |
| 1 | Disconnect the control panel’s backup battery while keeping its mains supply connected. | The backup battery is disconnected and the mains supply remains connected. |
| 2 | Wait until the battery failure event is recorded in C4. | The Central Unit audit log records the low battery and battery missing events separately. These events do not set the Central Unit to a fault state. |
| 3 | Reconnect the backup battery. | The backup battery is reconnected. |
| 4 | Wait until the battery restoration event is recorded in C4. | The Central Unit audit log records the battery missing restored and low battery restored events separately. These events do not set the Central Unit to a fault state. The low battery condition may clear later than the battery missing condition. |

**Expected audit / evidence:**

'DEVICE' - low battery.

'DEVICE' - battery missing.

'DEVICE' - battery missing restored.

'DEVICE' - low battery restored.

**Where:**

- DEVICE represents the name of the Central Unit.

**Notes:**

- The control panel reports low battery voltage and a missing battery separately. Disconnecting the battery triggers both events.
- Battery restoration may be reported several tens of seconds after the battery is reconnected. The low battery condition may clear later than the battery missing condition. These delays are normal.

**Cleanup:** Confirm the backup battery is reconnected and both battery missing and low battery restoration events have been recorded, allowing for the distinct delays described in the source.