NVision NV9000 Protocol implementation notes

NV9000 protocol for router control is supported in Helm, RouteMaster and RouteMaster VR. RouteMaster uses the protocol for both outgoing and incoming connections, allowing third-party systems using NV9000 to control RouteMaster.  Helm uses it for outgoing connections...

Quartz Protocol implementation notes

Evertz-Quartz protocol for router control is supported in Helm, RouteMaster and RouteMaster VR. RouteMaster uses the protocol for both outgoing and incoming connections, allowing third-party systems using Quartz to control RouteMaster.  Helm uses it for outgoing...

Utah RCP-3A Implementation notes

Utah RCP-3A protocol for router control is supported in Helm, RouteMaster and RouteMaster VR. RouteMaster uses the protocol for both outgoing and incoming connections, allowing third-party systems using RCP-3A to control RouteMaster.  Helm uses it for outgoing...

Control of AJA Kumo routers

AJA Kumo routers can be controlled using Grass Valley Native protocol over TCP/IP from Helm, RouteMaster and RouteMaster-VR. Kumo routers only support a subset of GVG native commands. RouteMaster and Helm automatically detect Kumo routers, and adapt to only use the...

Using REST APIs with Helm

Helm has built-in support for both creating and accessing JSON REST APIs. This replaces the older “WebActive” property of the Root Panel, which is now deprecated. Accessing REST APIs To start, add a REST API Device to your panel. You’ll find this in...

Using GPI/O devices in Helm

Helm supports various GPI/O devices, allowing panels to control external legacy equipment, and to receive status and tallies from external equipment. Output Controls Control of GPI/O Outputs is straightfoward. Each GPI device provides commands to turn outputs on and...