Vanderbilt SPC alarm and KNX integration with Link’nX
Link’nX connects a Vanderbilt (ACRE) SPC intrusion panel to the KNX bus and to scenarios through a Lundix SPC Bridge, a box plugged into the local network next to the panel. A KNX button or a scenario can arm or disarm the panel or an area, inhibit a zone, drive an output or a door; the bus and the scenarios receive the arm mode, the alarms and the state of the zones. This page tells you what to enter, where to find it in the bridge and in which order to commission the integration.
What the Vanderbilt SPC integration does
Section titled “What the Vanderbilt SPC integration does”| Need | Where to configure it | Guide |
|---|---|---|
| Declare the SPC Bridge and read the areas, zones, outputs and doors | Devices → Security & Access → Vanderbilt SPC | Declare the SPC Bridge |
| Arm, disarm or clear the alerts from a KNX button | Vanderbilt SPC gateway table, Actions tab | Vanderbilt SPC and KNX |
| Receive the arm mode, the alarms and the zone openings on the bus | Gateway table, second tab | Vanderbilt SPC and KNX |
| Arm, disarm, inhibit a zone or drive a door in a scenario | Vanderbilt SPC actions | Vanderbilt SPC actions and triggers |
| Start a scenario on an arming, an alarm, an open zone or a door passage | Vanderbilt SPC triggers | Vanderbilt SPC actions and triggers |
| Let a scenario start only if the alarm is armed or disarmed | Vanderbilt SPC — alarm armed / disarmed conditions | Vanderbilt SPC alarm condition |
What to enter and where to find it
Section titled “What to enter and where to find it”| To enter in Link’nX | Where to find it |
|---|---|
| Bridge IP address | Bridge web interface, System → Network. Give it a fixed address. |
| Port | Services → Bridge API → API Server, TCP Port field: 8088 by default. |
| SSL/TLS encryption is enabled in the bridge (recommended) | Same page, Enable SSL/TLS Encryption box. |
| Queries, Commands and Events accounts | Services → Bridge API → API Credentials: user and password of each account, once the factory accounts are replaced. |
| Panel user and its web password, otherwise its PIN | Users of the SPC panel. Its profile must allow Web Access. Only needed to send commands. |
Step-by-step commissioning
Section titled “Step-by-step commissioning”- Link the SPC Bridge to the panel as described in the Lundix manual, then give it a fixed IP address.
- Declare the bridge in Link’nX in four steps: Where the bridge is, Bridge accounts, Control the panel, What the panel holds. Save, reopen the record, click Read from the panel, then save again.
- Map the commands and the feedback to KNX group addresses.
- Prepare the actions and the triggers, then add them to the relevant scenario.
Good to know
Section titled “Good to know”- Hardware: a Vanderbilt or ACRE SPC 4000, 5000 or 6000 panel, with firmware 3.8.5 or later, behind a Lundix SPC Bridge Generic or Generic Lite. The Lite is recommended for up to 32 zones and 4 areas. The “SPC Web Gateway” module is not supported.
- Link’nX talks to the bridge, never directly to the panel. The bridge and the gateway are on the same local network.
- The Vanderbilt SPC card still carries the Soon badge: the integration is being validated. Test every command and every feedback on the installation.
- The commands are sent on behalf of a panel user, and the panel only carries out what that user’s profile allows. Create a user reserved for Link’nX, limited to what you want to control.
- A refusal by the panel does not appear in Link’nX. Check the effect of a command on the panel or on the arm mode feedback.
- On the bus, each command is sent on a 1 in DPT 1.017; a 0 does nothing. Only an output is driven on and off, in DPT 1.001.
- The arm mode, in DPT 5.010, is 0 disarmed, 1 part set A, 2 part set B, 3 full set. For the panel, 97, 98 and 99 indicate areas in different modes; these values are only reported after 2 seconds.
- In a trigger, the SPC user (optional) filter only applies to mode changes and door passages.
For cameras and intercoms, see Security and video surveillance. For intercoms, locks and access codes, see Access control.