Evertz EQX/EQT Quartz Router Controller
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.
Minimum hi Version: v2.1.0
Overview
The Evertz® Quartz integration reads Source and Destination names, monitors Crosspoint state, and sets Crosspoints over TCP.
Network Requirements
-
Allow outbound TCP from hi to the Quartz controller. The integration defaults to Port
4000; use the Port commissioned on the controller when it differs. -
No callback or inbound connection to hi is used.
-
Keep the plaintext control connection on a trusted management network.
Standards Conformance
|
Standard |
Conformance |
Notes |
|---|---|---|
|
Evertz Quartz |
Source and Destination names
|
Vendor protocol
|
Operator Workflow
-
UI Surface in hi: Routing Matrix, Inventory, and Hardware Panel workflows
-
Capabilities: Source/Destination names, Crosspoint reads, Destination interrogation, and Crosspoint setting
-
Routing Semantics: The configured router Sources and Destinations appear in hi routing workflows.
-
Notes for Operators Familiar with the Vendor's Own Tooling: Use vendor tooling for salvos, locks, protection, engineering configuration, and firmware management.
Connection Details
|
Property |
Value |
|---|---|
|
Protocol |
Evertz Quartz |
|
Transport |
TCP |
|
Default Port |
4000 (integration default
|
|
Authentication |
No credentials are configured in hi for this connection |
|
Encryption in Transit |
Not provided by the configured TCP connection |
|
Connection Model |
Persistent TCP command/response with state reads |
|
Required License |
hiBase |
|
Traffic Flow |
Outbound from hi |
Required Configuration
|
Parameter |
Description |
Default |
|---|---|---|
|
Host / IP Address |
IP address of the Evertz router controller |
- |
|
Port |
Quartz TCP control port |
4000 |
Device-Side Setup
Follow Evertz EQX/EQT Quartz Router Controller Integration Configuration for the device-side and hi-side configuration steps.
Supported Features
|
Feature |
Access |
Exposed Operation and Scope |
|---|---|---|
|
Source and Destination Names |
Read-only |
Read configured names. |
|
Crosspoint State |
Read-only |
Read all Crosspoints or interrogate a Destination. |
|
Crosspoint Set |
Write-only |
Route a Source to a Destination on a supported level. |
Device Coverage
Tested With identifies devices that have been tested with hi. Potentially Compatible (Not Yet Verified) identifies compatibility candidates that use the same protocol or connection method. Device-specific configuration, firmware, and feature support can affect results.
This integration supports the Evertz Quartz range.
Tested With
-
Evertz EQX
-
Evertz MAGNUM
Supported Product Range
These Evertz routers and controllers support the Quartz protocol:
-
Evertz EQT
-
Evertz Xenon
-
Evertz Q256
-
Evertz Topaz
-
Evertz SC-1000
Potentially Compatible (Not Yet Verified)
-
Other router controllers that expose the same Quartz Source, Destination, and Crosspoint commands.
Known Limitations
-
Validate the matrix dimensions and the level mapping with the installed firmware during commissioning.
-
The controller ends all connections when a new configuration is downloaded to it. Expect the connection to drop and reconnect after an engineering configuration change.
-
A frame with redundant controllers has one IP address per controller, and only the active controller accepts a connection. Use the address of the active controller when you commission hi. hi connects to one controller address and does not fail over. After a changeover, the Node stays disconnected until you change its address to the newly active controller.
-
Quartz command support differs by product and software version. Validate Source and Destination names and Crosspoint reads against your controller during commissioning.
-
The Quartz protocol addresses router levels with letters. Systems use 8 or 16 levels, and MAGNUM-based control systems use up to 26 levels, so check the level mapping against the controller database.
What's Not Supported
-
Salvo execution, Destination locks, and protection operations.
-
Firmware updates and engineering-level configuration remain in the vendor tooling.
-
Failing over between the two controllers of a redundant frame.
Trademarks
Note
Evertz, EQX, and EQT are trademarks or registered trademarks of Evertz Microsystems Ltd.
RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Evertz unless explicitly stated.