---
title: "Vanderbilt SPC in Link’nX: declare the Lundix SPC Bridge"
description: "Declare a Vanderbilt SPC intrusion panel in Link’nX through its Lundix SPC Bridge: IP address, port 8088, bridge accounts and the panel user for commands."
canonical: https://wiki.can-nx.com/en/guides/link-vanderbilt-device/
language: en
product: Link’nX
audience:
  - administrateur
  - installateur
context: "Link’nX web: Security & Access devices, Vanderbilt SPC record and reading of the panel"
---

# Vanderbilt SPC in Link’nX: declare the Lundix SPC Bridge

Context: Link’nX web: Security & Access devices, Vanderbilt SPC record and reading of the panel

Link’nX controls a Vanderbilt (ACRE) SPC intrusion panel through a Lundix SPC Bridge, a box plugged into the local network next to the panel. The declaration gathers the bridge address, its three accounts and, to send commands, a panel user. Link’nX then reads the panel’s areas, zones, outputs and doors, which feed the KNX table and the scenarios.

Intended for the alarm installer or the authorized administrator. The **Vanderbilt SPC** card still carries the **Soon** badge in Link’nX: the integration is being validated. Test every command and every feedback on the installation before relying on it.

## Before you start

- A Vanderbilt or ACRE SPC 4000, 5000 or 6000 panel, with firmware 3.8.5 or later.
- A Lundix SPC Bridge Generic or Generic Lite, already linked to the panel as described in the Lundix manual. The Lite model is recommended for up to 32 zones and 4 areas. The “SPC Web Gateway” software module is not supported.
- The bridge on the same local network as the gateway: Link’nX talks to the bridge, never directly to the panel.
- A fixed IP address for the bridge: in its web interface, open **System → Network** and uncheck **Enable DHCP**.
- A bridge that communicates with the panel: in its web interface, **Services → SPC → SPC Areas** displays the status of the areas.

## Note the settings in the bridge

1. In the bridge web interface, open **Services → Bridge API → API Server**. Note **TCP Port**, 8088 by default, and the state of the **Enable SSL/TLS Encryption** box, which the Lundix manual recommends checking.
2. Open **Services → Bridge API → API Credentials**. The bridge has three accounts: **Queries** to read the states, **Commands** to send the commands, **Events** to receive the real-time events.
3. Replace the factory accounts with your own, as the Lundix manual requires, then note the user and the password of each one. The bridge never shows a saved password again: note it when you set it.

## Prepare the panel user

To arm, disarm, or drive a door or an output, the panel asks for one of its users and only carries out what that user’s profile allows. This user is not needed if Link’nX only reads states.

- Create a panel user reserved for Link’nX.
- In its profile, allow the **Web Access** right, under **User Rights - System**, and nothing beyond what you want to control: for example, neither disarming nor door unlocking if Link’nX must not command them.
- Note its exact name, then its web password if it has one, otherwise its PIN.

## Declare the bridge in Link’nX

1. In Link’nX, check the project and the gateway. Open **Devices → Security & Access → Vanderbilt SPC**, or search for **Vanderbilt** in **Search a device...**. On mobile, first open the three-line menu. For a padlock or a missing card, follow the [navigation guide](https://wiki.can-nx.com/en/guides/link-navigation/).
2. Click **Add**. **Vanderbilt SPC bridge declaration** presents four numbered steps. The required fields bear an asterisk.
3. Step 1, **Where the bridge is**: fill in **Name in Link'nX**, limited to 64 characters, for example “Reception alarm”, then **Bridge IP address** and **Port**. Keep 8088, unless you changed it in the bridge.
4. Step 2, **Bridge accounts**: check **SSL/TLS encryption is enabled in the bridge (recommended)** if the bridge’s **Enable SSL/TLS Encryption** box is checked. Then fill in **User** and **Password** for the three accounts, **Queries — read the states**, **Commands — send the commands** and **Events — receive the events**, as they are set in the bridge. With the box unchecked, the form displays **Without encryption, Link'nX sends no account to the bridge: nothing to enter here.**
5. Step 3, **Control the panel**: check **Link'nX sends commands to the panel**, then fill in **Panel user**, with its exact name, and **Web password, otherwise PIN**. Only uncheck it if this bridge is used solely to read states and start scenarios. The form then displays **No user is sent to the panel. Use this bridge only to read states and trigger scenarios: a command would go out without a user, and the panel may refuse it.** The scenario actions and the KNX command rows are still offered for this bridge.
6. Step 4, **What the panel holds**: on creation, the form displays **Save the bridge first, then reopen it to read its areas, zones, outputs and doors.**
7. Click the **floppy disk at the bottom right**. Wait for **Success!** and the return to the list, which presents **Name**, **Bridge IP address**, **Areas** and **Zones**.

## Read what the panel holds

The reading only works on a bridge that is already saved, with the saved settings: save any change to the address or the accounts first.

1. In the list, click the bridge’s **Edit** pencil. **Vanderbilt SPC bridge modification** opens.
2. At the **What the panel holds** step, click **Read from the panel**.
3. Reread the **Areas**, **Zones**, **Outputs** and **Doors** lists. Each element bears its number and its name in the panel; each zone shows its area. The outputs are the panel’s “mapping gates”.
4. When **List updated: save to apply it to the KNX table and the scenarios.** appears, click the floppy disk and wait for **Updated!**. Without this save, the list that was read is not kept.

As long as nothing has been read, the form displays **Nothing read from the panel yet: only the panel lines will appear in the KNX table.** Run the reading again, then save, after any addition or change of an area, a zone, an output or a door in the panel.

## Edit or delete the declaration

- To edit, use the pencil, then the floppy disk. When editing, a saved password is not displayed and the length shown does not match its own: do not replace it for this reason alone.
- To abandon an entry, leave the record; in **Unsaved changes**, **Cancel** stays on the form and **Don't save** discards the changes.
- Before deleting the declaration with the **Delete** bin, check the scenarios and the KNX group addresses that use it. If the consequences are not established, contact support before the operation.

## Check the result

- The list displays the bridge with the right address, its port and the expected number of **Areas** and **Zones**.
- A reading without an error message confirms that the gateway reaches the bridge and that the bridge returns what the panel holds.
- Then map the **Panel: bridge connected** feedback in the [Vanderbilt SPC KNX table](https://wiki.can-nx.com/en/guides/link-vanderbilt-gateway/), or prepare [a scenario action or trigger](https://wiki.can-nx.com/en/guides/link-vanderbilt-automation/), then test on the panel.

## Troubleshooting

| Message or symptom | Check and action |
| --- | --- |
| **The gateway did not answer. Check that it is online, then try again.** | The project’s gateway did not answer Link’nX. Check that it is online, then run **Read from the panel** again. |
| **The gateway does not know this bridge yet: wait a few seconds after saving, then try again.** | The bridge has just been saved. Wait a few seconds, then run the reading again. |
| **The bridge did not answer in time. Check that it is powered on and reachable from the gateway.** | Check the bridge’s power supply, its network cable and its presence on the same local network as the gateway. |
| **The bridge cannot be reached from the gateway. Check its IP address and port.** | Compare the address and the port with the bridge’s **System → Network** and **TCP Port**. Also check that the Link’nX encryption box matches **Enable SSL/TLS Encryption**, and that the bridge’s **Access Control** setting allows the gateway. |
| **The bridge refused the Queries account. Check its user and password in step 2.** | At the **Bridge accounts** step, correct the user and the password of the **Queries** account, save, then run the reading again. |
| **The bridge answered with an error**, followed by an HTTP code | Note the code displayed and check in the bridge that **Services → SPC → SPC Areas** displays the areas. |
| **The panel returned nothing — the saved list is kept. Check the bridge, then try again.** | Check in the bridge interface that it communicates with the panel, then run the reading again. The list already saved stays in place. |
| The floppy disk is greyed out | The form displays at the bottom **To save, fill in every field marked with an asterisk (\*).** With the encryption box checked, the user and the password of the three accounts are required; with the **Link'nX sends commands to the panel** box checked, so are the panel user and its web password or PIN. The port is between 1 and 65535 (**Enter a port between 1 and 65535**). |
| A command has no effect | A refusal by the panel does not appear in Link’nX. Check that **Link'nX sends commands to the panel** is checked: without it, the command goes out without a user. Then check the panel user’s name, its web password or PIN, the **Web Access** right and the rights of its profile. |

If the blockage persists, contact support@can-nx.com with the model of the panel and of the bridge, the message displayed and the attempts made, without a password or PIN.

French labels: **Vanderbilt SPC → Ajouter → Déclaration d'un SPC Bridge Vanderbilt**, **Où est le bridge**, **Nom dans Link'nX**, **Adresse IP du bridge**, **Port**, **Comptes du bridge**, **Le chiffrement SSL/TLS est activé dans le bridge (recommandé)**, **Queries — lire les états**, **Commands — envoyer les commandes**, **Events — recevoir les événements**, **Piloter la centrale**, **Link'nX envoie des commandes à la centrale**, **Utilisateur de la centrale**, **Mot de passe web, sinon code PIN**, **Contenu de la centrale**, **Lire la centrale**, **Secteurs**, **Zones**, **Sorties**, **Portes**. Saving displays **Succès !** or **Mis à jour !**.