Evertz EQX/EQT Quartz Router Controller 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

An Evertz Quartz controller connects to hi as one router Node. The Node has two level groups, one for video and one for audio. Each group has its own level letter and its own Source and Destination counts. Quartz does not report its matrix size, so every count that you enter in hi must come from the router configuration.

Configuration	What hi Sees	Use When
Video Level	One matrix of Sources and Destinations on the video level.	hi must route video only.
Video and Audio Levels	One matrix on the video level and one on an audio level.	hi must route video and audio on the same controller.

Caution

The controller does not report its dimensions. It does not answer an interrogation for an unknown level or Destination, and hi discards the error replies to other commands. A wrong Level or count therefore shows up as missing names or missing Crosspoints, and not as an error message.

Before You Begin

Use Node admin and open Inventory > Nodes. See Manage Nodes.
Confirm the license and minimum hi version in Required Configuration.
Use the Evertz router configuration software, WinSetup, to read the levels, the Port, and the Source and Destination counts.
Confirm the network access in Network Requirements.
Quartz has no authentication. Anyone who can reach the Port can route. Keep the controller on a routing-control network.

Configure Quartz Levels

Device Configuration

Enable the Quartz control interface on the router controller.
Confirm the TCP Port. On an EQX, add a TCP Port for Quartz control on the Port Setup tab in WinSetup. The EQX offers the TCP Ports 4000, 4001, 4002, and 4003, and Port 4000 matches the integration default. Other Quartz controllers, such as Xenon, Q256, and Topaz, accept a connection on the telnet Port 23. On an SC-1000, add a TCP/IP port that uses the Quartz protocol in WinSetup under System > SC-1000 Configuration > Options, select the server option, and use a Port number above 1024. On an EQT, add an Ethernet interface for Quartz control on the Port Setup tab of the Edit Frame dialog in WinSetup. The EQT provides up to four Quartz control Ports: 3737, 3738, 3739, and 3740. Port 4000 on the EQT serves the Telnet configuration and monitoring menu, and Port 2500 carries configuration downloads, so enter the EQT Quartz control Port in hi instead of the integration default.
When the frame has two controllers, record the address of each. Each controller has its own IP address. Only the active controller accepts a connection, so enter the address of the active one. hi connects to one address and does not fail over. After a controller changeover, change the address of the Node to the newly active controller.
Record each level that hi must route, with its Source count and its Destination count. Quartz identifies a level by a letter. In typical systems, V is video, and A, B, C, and onward carry audio, data, or control levels. Confirm the assignment in the router configuration. Quartz numbers Sources and Destinations from 1, and hi also shows a Source 0 named Clear.

hi Configuration

Add the Quartz Compatible Router integration (manufacturer Evertz Microsystems) in Inventory.
Enter the controller address and the Port.
Open Level 1. Its Signal Type defaults to Video and its Level to V. Enter Input Count and Output Count. The template defaults are 16 and 16.
To route a second level, set Enabled to True in Level 2. Its Signal Type defaults to Audio and its Level to A. Enter its counts.
Create the Node. hi reads all names on the first connection.
To read the names again on every later connection, open the Node and set Read labels on startup to Yes in the Startup group.

For example, a router with 64 video Sources, 64 video Destinations, and a matching set of audio signals on level A uses V with 64 and 64 in Level 1, and A with the audio counts in Level 2.

Settings Summary

Setting	Device Side	hi Side
Control Port	Port `4000` `4001` `4002` or `4003` on an EQX. Port `3737` `3738` `3739` or `3740` on an EQT. A Port above `1024` on an SC-1000. The telnet Port `23` on other Quartz controllers.	Port default `4000`
Level	Level letter such as `V` or `A`	Level in the matching level group
Sources and Destinations	Counts from the router configuration	Input Count and Output Count
Active controller	The address of the active controller in a redundant pair	Controller address

Information

The integration default Port is 4000, which is an EQX Quartz control Port. Other controllers use other Ports. Always enter the Port that the controller commissioning record lists.

Common Checks

Symptom	Check
The Node does not connect.	Confirm the Port, and confirm that the address belongs to the active controller.
The Node disconnects after the router configuration changes.	The controller closes every connection when it loads a new configuration. Wait for hi to reconnect. hi reloads the Crosspoints. To reload the names, select Refresh Labels or set Read labels on startup to `Yes`.
Names are missing.	Select Refresh Labels in the Operations group, or set Read labels on startup to `Yes`. Confirm that the counts match the router.
A level shows no Crosspoints.	Confirm that Enabled is `True` for that group and that the level letter exists on the controller. The controller does not answer an interrogation for an unknown level.
A route from hi does not appear on a panel.	Confirm the Source and Destination numbers against the router configuration. Quartz numbers start at `1`.

Verify the Configuration

Wait for the Node to report a connected state. When Read labels on startup is off and the names are not loaded, select Refresh Labels in the Operations group. Compare the Source names, the Destination names, and several Crosspoints with the controller. If names or Crosspoints are incomplete, verify the level mapping, the Source and Destination counts, the Port, and that the hi server can reach the controller. hi opens the connection, and the controller makes no connection to hi. Route a noncritical Destination from hi, and confirm that the change returns to hi. Then change a Crosspoint from a router panel and confirm that hi shows it without a restart, because the controller reports changes made on other panels.