Riedel hiContact Integration Configuration

Caution

Compatibility Note: This information is a general guide and may be incomplete, may not match a specific project implementation, and is subject to change as supported products and versions evolve. Confirm the exact implementation and requirements for each project with Riedel and the relevant equipment vendor, then validate the required functions end to end in the target environment before deployment.

Configuration Overview

A hiContact connects to hi as one GPIO Node. hi opens both TCP connections to the hiContact, so the hiContact needs only a reachable IP address. The GPI and GPO counts that you enter when you create the Node set the Ports that hi creates.

Caution

hi applies Input Count and Output Count only when it creates the Node. To change them, create the Node again.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the hiGlue license and the minimum hi version in Required Configuration.
Identify the hiContact generation from the model label. See hiContact Hardware Information.
Confirm the network access in Network Requirements.
The hiContact connection has no authentication. Keep the hiContact on a control network.

Configure hiContact GPIO

Use this configuration to monitor GPI contacts and switch GPO relays from hi.

Device Configuration

Install and power the hiContact as described in Hardware Installation and Commissioning, and connect it to the control network.
For hiContact Mark 3, set a unique production IP address with the procedure in Hardware Network Configuration. The factory default address is listed on that page. Commission one unconfigured unit at a time, because units can share the default address.
hiContact Mark 1 uses a fixed default address, given in Hardware Network Configuration, and has no self-service procedure to change it. Contact Riedel Customer Success to change the address.
Record the IP address of the hiContact.

hi Configuration

Add the hiContact integration (manufacturer hi human interface) in Inventory.
Enter the IP address of the hiContact.
In the Port Settings group, set Input Count and Output Count. The template defaults are 16 and 16.
Create the Node. hi creates the Ports GPI 1 onward and GPO 1 onward, and connects to TCP Ports 10001 and 10002 on the hiContact.

Settings Summary

Setting	Device Side	hi Side
Address	IP address of the hiContact	IP address of the Node
TCP Ports	`10001` and `10002`	Fixed no setting
GPI and GPO counts	16 inputs and 16 relay outputs on the hardware	Input Count and Output Count default `16` each

Common Checks

Symptom	Check
The Node does not connect.	Confirm the IP address of the hiContact, and confirm that the hi system can reach TCP Ports `10001` and `10002`.
The Node reconnects repeatedly.	hi reconnects when it receives no status data for more than 2 seconds. Check the network path between hi and the hiContact.
A GPI or GPO is missing in hi.	Confirm Input Count and Output Count on the Node. To change them, create the Node again.

Verify the Configuration

Close a contact on one GPI and confirm that the matching GPI Port changes state in the Live Status column of the Ports tab in Inventory > Nodes. Then select one GPO that drives no live circuit, select Enable Test Mode from the three-dot menu, switch its Live Status, and confirm that the relay switches and that hi shows the reported state.