Riedel hiPush Series
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.
Available controls vary by product and hardware generation.
Minimum hi Version: v1.1.0
Overview
The Riedel hiPush™ family uses the proprietary hi Hardware Panel protocol. The panel initiates a persistent connection to the hi system, and control data then flows in both directions.
Supported products are hiPush18, hiPush20, hiPush32-D, hiPush32-S, hiPush36, and hiPush54.
The Hardware User Manual summarizes the product range. Use the current Riedel product datasheet as the authoritative source for hardware specifications.
Network Requirements
-
Connection Model: Inbound to hi from the panel; bidirectional after connection.
-
Multicast / Unicast: Unicast only.
-
Bandwidth: Control data only.
-
IP Version: IPv4.
-
Firewall: Allow the panel to reach the configured hi Hardware Panel service.
Operator Workflow
hiPush panels use the Hardware Panel editor, Router Panel Preset delegation, Static Preset layouts, and the Hardware Panel simulator where supported by the selected product. Operators can assign buttons and rotaries to routing, disconnect, Parameters, Triggers, Presets, and Destination locks.
Connection Details
|
Property |
Value |
|---|---|
|
Protocol |
hi Hardware Panel protocol (proprietary) |
|
Transport |
TCP / WebSocket |
|
Default Port |
Not specified (device-dependent) |
|
Authentication |
Not specified (device-dependent) |
|
Encryption in Transit |
Not specified (device-dependent) |
|
Connection Model |
Persistent connection initiated by the panel |
|
Required License |
hiGlue |
|
Traffic Flow |
Bidirectional |
Required Configuration
The integration requires hiGlue. Each connected panel also consumes one hiUser session. Confirm available capacity using hiUser before connecting panels.
The panel must be configured to reach the assigned hi Hardware Panel service. On connection, the panel registers its identity and hardware description with hi.
Device-Side Setup
Follow Riedel hiPush Series Integration Configuration for the device-side and hi-side configuration steps.
Supported Features
|
Feature |
Access |
Exposed Operation and Scope |
|---|---|---|
|
Button and Rotary Input |
Read-only input |
Receive actuation, rotary movement, and rotary push where the selected product provides them. |
|
Presets and Layouts |
hi-side configuration and write actions |
Delegate Presets and configure supported panel layouts. |
|
Routing |
Read/write actions |
Route, take, disconnect, and select entries from Port Containers. |
|
Parameters |
Per-parameter access |
Read and write only Parameters whose hi access mode permits the requested operation. |
|
Triggers |
Write-only actions |
Execute configured triggers. |
|
Destination Locking |
Read/write |
Apply and display Destination lock state. |
|
Displays and Indicators |
Write-only panel output |
Update button/display content, LEDs, and meters where provided by the selected product. |
|
Panel Operation |
Read/write and read-only status |
Register the panel, synchronize initial data, and control standby state. |
Device Coverage
The following product layouts and controls are available.
This integration supports the Riedel hiPush range.
Tested With identifies devices that have been tested with hi.
Tested With
-
Riedel hiPush36
-
Riedel hiPush54
Supported Product Range
|
Product |
Implemented Controls |
|---|---|
|
hiPush18 |
18 buttons and 2 rotaries
|
|
hiPush20 |
20 buttons |
|
hiPush32-D |
32 buttons
|
|
hiPush32-S |
32 buttons
|
|
hiPush36 |
36 buttons
|
|
hiPush54 |
54 buttons and 2 rotaries
|
Known Limitations
-
Available indicators and meters depend on the selected hiPush product.
-
Static Presets are not available on hiPush32-D or hiPush32-S.
-
hi identifies a connecting panel by its source IP address. The address entered on the Node must match the panel's own IP address. hi does not register a panel whose address matches no enabled Node.
-
When two enabled Nodes use the same panel IP address, hi uses only the first match.
-
After registration, hi records the MAC address and firmware version that the panel reports.
What's Not Supported
-
Firmware updates, physical commissioning, and hardware diagnostics are outside this integration.
-
Standalone offline operation is outside the hi Hardware Panel workflow.
Trademarks
Note
hi human interface and hiPush are trademarks of RIEDEL Communications GmbH.