Riedel hiContact
Production
Recommended for normal production use.
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.
The integration uses fixed TCP Ports on the hiContact.
Minimum hi Version: v1.1.0
Overview
Riedel hiContact connects physical GPIO signals to hi. By default, the integration creates 16 GPI Ports and 16 GPO Ports.
Information
hiContact Hardware Information in Hardware. Use the current Riedel product datasheet as the authoritative source for physical, electrical, and ordering specifications.
Network Requirements
-
Connection Model: hi opens both TCP connections; GPIO data flows in both directions across the pair.
-
Multicast / Unicast: Unicast only.
-
Bandwidth: GPIO control data only.
-
IP Version: IPv4.
-
Firewall: Allow the hi system to connect to the hiContact on TCP Ports
10001and10002.
Standards Conformance
|
Standard |
Conformance |
Notes |
|---|---|---|
|
hi GPIO Protocol |
GPI/GPO state monitoring and output control |
Riedel vendor protocol. |
Operator Workflow
-
Inventory > Nodes: On the Ports tab of the hiContact Node, view the live GPI and GPO state, enable test mode per Port, and force test states on outputs.
-
Functions > Rules: Use a GPI's active or inactive state as a trigger, and switch a GPO with Set GPO on, Set GPO off, GPO follows the Trigger, or Impulse.
Connection Details
|
Property |
Value |
|---|---|
|
Protocol |
hi GPIO Protocol |
|
Transport |
TCP |
|
Default Port |
|
|
Authentication |
None |
|
Encryption in Transit |
None; both connections are plaintext TCP. |
|
Connection Model |
Two persistent connections initiated by hi |
|
Required License |
hiGlue |
|
Traffic Flow |
Bidirectional across the connection pair |
Required Configuration
|
Parameter |
Description |
Default |
|---|---|---|
|
Host / IP Address |
Hostname or IP address of the hiContact |
- |
|
Input Count |
Number of GPI Ports created in hi, in the Port Settings group. Set when you create the Node. |
16 |
|
Output Count |
Number of GPO Ports created in hi, in the Port Settings group. Set when you create the Node. |
16 |
The TCP Ports are fixed and not configurable: hi connects to 10001 on hiContact for control/output traffic and to 10002 on hiContact for input/status traffic. Status returns over the second connection; it does not require hiContact to open a connection to a listener on hi.
Device-Side Setup
Follow Riedel hiContact Integration Configuration for the device-side and hi-side configuration steps.
Supported Features
|
Feature |
Access |
Exposed Operation and Scope |
|---|---|---|
|
GPI State Monitoring |
Read-only |
Receive and display opto-isolated input state changes; the inputs share a common ground. |
|
GPI Active/Inactive Triggers |
Read-only input events |
Trigger configured hi Rules when an input becomes active or inactive; the integration does not drive the inputs. |
|
GPO Output State |
Read/write |
Set relay-contact output states and read their reported state. |
|
GPO Actions |
Write-only output actions |
Set on, off, follow-trigger, or impulse behavior. With GPO follows the Trigger, hi sends the expected state again when the hiContact reports a different one. |
|
Port Testing |
Read/write test action |
View live state and force test states on outputs on the Ports tab of the Node in Inventory > Nodes. |
Device Coverage
The integration creates 16 GPI and 16 GPO Ports by default; both counts are configurable when you create the Node. hi identifies the hiContact Mark 1 (hi-IO1616) and hiContact Mark 3 (hi-IO1616B-PoE) automatically after it connects.
This integration supports the Riedel hiContact range.
Tested With identifies devices that have been tested with hi.
Tested With
-
Riedel hiContact
Supported Product Range
-
Riedel hiContact Mark 1 (hi-IO1616)
-
Riedel hiContact Mark 3 (hi-IO1616B-PoE)
Known Limitations
-
GPI and GPO are separate, fixed port types. Port direction cannot be changed at runtime.
-
Ports are numbered from 1, as
GPI 1,GPI 2, and so on, andGPO 1,GPO 2, and so on. -
The Impulse action switches the GPO for a fixed 1000 ms, then switches it back. The duration cannot be edited.
-
If hi receives no status data from the hiContact for more than 2 seconds, it closes both connections and reconnects.
What's Not Supported
-
Physical wiring, contact-closure electrical commissioning, firmware updates, and hardware diagnostics are outside this integration.
Trademarks
Note
hi human interface and hiContact are trademarks of RIEDEL Communications GmbH.