Connectivity

This page covers how to reach the controller, and how to integrate it into a building management system.

Ports and interfaces at a glanceCopy Anchor Link

EthernetCopy Anchor Link

Connect an Ethernet cable to J4. The connector has a green and a yellow LED:

• Yellow — the link is up; it blinks when there is traffic.
• Green — the link runs at 100 Mbit/s.

Setting the addressCopy Anchor Link

The controller boots with a fixed address of 192.168.1.195, subnet 24, gateway 192.168.1.1, and DHCP switched off.

By DHCP

1. Open the Configuration tab in the web interface, or Settings → Network on the screen.
2. Tick Enable DHCP (web interface) or Enable DHCP (screen).
3. Save.

The controller then asks the network for an address. Read the address it was given back from SYSTEM INFORMATION → NETWORK on the screen, or from the System card in the web interface.

With a fixed address

1. Clear Enable DHCP.
2. Fill in IP ADDRESS, SUBNET MASK and GATEWAY.
3. Save.

The screen's SUBNET MASK field takes a dotted mask such as 255.255.255.0. The web interface's Subnet prefix field takes a prefix length such as 24 and shows the matching mask next to it; it also accepts a dotted mask, as long as it is contiguous.

The new address takes effect without restarting the unit. After changing the address, reopen the web interface at the new address.

The controller has no IP addressCopy Anchor Link

If the screen shows no address, or the network does not answer for the controller:

1. Check the yellow link LED on J4. If it is dark, the cable or the switch port is the problem.
2. Open the screen's SYSTEM INFORMATION → NETWORK panel. It shows the address, the DHCP setting, the subnet and the gateway.
3. If the unit has a fixed address that does not match your network, connect a computer directly to the controller with a fixed address in the same subnet, or set the address from the screen.
4. If the unit is set to DHCP and the network has no DHCP server, switch it back to a fixed address on the screen.

Networks that need 802.1XCopy Anchor Link

On a network where the switch authenticates ports with MAC Authentication Bypass, the controller announces itself on the network with a broadcast ARP announcement, once after the link comes up and then periodically. This lets the switch learn its MAC address and open the port. It happens in both DHCP and fixed-address mode.

The web interfaceCopy Anchor Link

Open http://<address> in a browser. Two pages are served:

The web interface has no login, no password and no encryption. The controller is normally on the client's own isolated network, and access to port 80 can be restricted at the switch or firewall if that is not the case.

RS-485 fieldbusCopy Anchor Link

The fieldbus terminal J6 has three terminals:

The bus can carry either Modbus RTU or BACnet MS/TP. Choose which one with the RS485 protocol setting (screen: Settings → Modbus; web interface: the Fieldbus card).

WiringCopy Anchor Link

• The board fits 560 Ω bias resistors across the bus, so a single unit on a bus holds the line in the idle state correctly.
• The board does not fit a termination resistor. Fit a 120 Ω resistor across the bus (Mod+ to Mod-) at each end of the bus — at the controller and at the last device. With only one device on the bus, fit it at the controller.
• Keep the common wire (J6 pin 1) connected at every device, and use a twisted pair.
• Do not connect the fieldbus to the screen connector J5. They are separate buses with separate transceivers.

SettingsCopy Anchor Link

The baud rate is read when the bus starts.

Modbus over RS-485Copy Anchor Link

The controller answers at the Modbus ID. Every setting and every measured value is in the register map. From the web interface you can see the whole map; the addresses are listed in the Settings reference and in the BACnet object list.

BACnet MS/TP over RS-485Copy Anchor Link

Set RS485 protocol to BACnet MS/TP. The controller then answers as a BACnet MS/TP node with the MAC address from BACnet MS/TP MAC and the BACnet device ID as its object instance number.

BACnet/IPCopy Anchor Link

BACnet/IP is always available on the Ethernet port, whatever the RS-485 protocol is set to.

The device ID must be unique on the BACnet network. The same instance number is used for BACnet/IP and for BACnet MS/TP.

The BACnet object list mirrors the register map: each register appears as an object whose name is the register name (MODE, ALARMS, CONDUCTIVITY, and so on). Objects that hold a value can be written to, with the same rules as the fieldbus.

Modbus/TCPCopy Anchor Link

Modbus/TCP runs on the Ethernet port, on the port given by Modbus port (502 by default). The controller answers at the Modbus ID.

USB service portCopy Anchor Link

The USB-C port J32 gives you a serial connection to the controller, independent of the network.

Over USB the controller behaves as a Modbus RTU server at 115200 baud and answers at Modbus ID 1. Unlike the fieldbus, the USB link can write every register, including the ones the fieldbus leaves read-only. Use it for commissioning and diagnostics.

The same port carries the firmware update protocol. Firmware updates are applied by DSH Belgium.

The USB device identifies itself as manufacturer DSH Belgium, product AdiaPure, with the unit's serial number.

The screen linkCopy Anchor Link

The screen is connected to J5, an 8-pin connector that carries the 5 V supply, the 0 V return and an RS-485 pair (Scr- and Scr+).

This is a point-to-point link. Do not put other devices on it.

The screen polls the controller over Modbus and writes its settings back, including a request to save the configuration. The screen and the web interface therefore write the same settings, so a change made on one is seen by the other.

Which interface should I use?Copy Anchor Link

Next stepsCopy Anchor Link

• Settings reference — the register names and their defaults.
• Maintenance and updates — routine care, backups and a factory reset.
• Troubleshooting — connectivity problems.