Grass Valley Sirius / Vega 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.
Minimum hi Version: v2.0.0
Overview
The Grass Valley® Sirius™ and Vega™ integration uses Pro-Bel SW-P-08 for routing. A separate RollCall surface provides Parameter Control.
Network Requirements
-
Allow outbound TCP from hi to the SW-P-08 controller on Port
2008by default. -
Allow outbound TCP from hi to the RollCall interface on Port
2050by default. -
No callback or inbound connection to hi is used.
-
Keep both plaintext control connections on a trusted management network.
Standards Conformance
|
Standard |
Conformance |
Notes |
|---|---|---|
|
Pro-Bel SW-P-08 |
Crosspoint routing
|
De facto broadcast-router control protocol |
|
Grass Valley RollCall |
Parameter reads
|
Vendor protocol
|
Operator Workflow
-
UI Surface in hi: Routing Matrix, Inventory, and Parameter Control
-
Control Scope: Router levels exposed through SW-P-08 and parameters exposed through RollCall
-
Routing Semantics: hi uses SW-P-08 for Sources, Destinations, labels, and Crosspoints.
-
Notes for Operators Familiar with the Vendor's Own Tooling: Use vendor tooling for protection, UMD, tie-line, salvo, engineering, and firmware operations.
Connection Methods
Connection: Pro-Bel SW-P-08
|
Property |
Value |
|---|---|
|
Purpose |
Router labels
|
|
Transport |
TCP |
|
Default Port |
2008 |
|
Authentication |
None at the protocol layer |
|
Encryption in Transit |
Not supported by the protocol |
|
Connection Model |
Persistent TCP with asynchronous routing-state updates |
|
Required License |
hiBase |
|
Traffic Flow |
Outbound from hi |
Connection: Grass Valley RollCall
|
Property |
Value |
|---|---|
|
Purpose |
Parameter discovery
|
|
Transport |
TCP |
|
Default Port |
2050 |
|
Authentication |
None at the protocol layer |
|
Encryption in Transit |
Not supported by the protocol |
|
Connection Model |
Persistent TCP with parameter subscriptions |
|
Required License |
hiBase |
|
Traffic Flow |
Outbound from hi |
Required Configuration
|
Parameter |
Description |
Default |
|---|---|---|
|
Host / IP Address |
IP address of the Sirius/Vega system controller. The template has two SW-P-08 connections, one for each controller. |
- |
|
SW-P-08 Port |
TCP port for SW-P-08 communication |
2008 |
|
Signal Type |
Signal type of the controlled matrix |
Video |
|
Level |
Level of the matrix
|
0 |
|
Matrix |
Matrix of the level
|
0 |
|
Input Count |
Number of router inputs
|
24 |
|
Output Count |
Number of router outputs
|
24 |
|
Dummy Crosspoints |
Create dummy Crosspoints until the device connects |
No |
|
RollCall Port |
TCP port for RollCall Parameter Control |
2050 |
Device-Side Setup
Follow Grass Valley Sirius / Vega Series Integration Configuration for the device-side and hi-side configuration steps.
Supported Features
|
Feature |
Access |
Exposed Operation and Scope |
|---|---|---|
|
SW-P-08 Crosspoints |
Read/write |
Route and monitor Crosspoints. |
|
SW-P-08 Labels |
Read-only |
Read Source and Destination names when the Node first initializes, at each connection when Read labels on startup is |
|
SW-P-08 Extended Addressing |
Protocol capability |
Address large matrices when the controller supports the extension. |
|
SW-P-08 Controller Status |
Read-only |
Monitor the active controller in redundant deployments. |
|
RollCall Parameters |
Per-parameter access |
Discover/read exposed Parameters, receive subscriptions, and write only Parameters whose RollCall access mode permits writing. |
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 Grass Valley Sirius and Vega range.
Tested With
-
Grass Valley Sirius Series
-
Grass Valley Vega Series
Supported Product Range
-
Grass Valley Sirius 830
-
Grass Valley Sirius 840
-
Grass Valley Sirius 850
-
Grass Valley Vega 30
Known Limitations
-
RollCall parameters vary by model, firmware, and controller configuration.
-
Validate the required routing and parameter operations with the installed firmware during commissioning.
-
On the Sirius 800, the Nucleus2 2463 controller supports SW-P-08 over IP. The earlier Nucleus 2450 controller supports SW-P-08 on serial ports only. hi connects over TCP, so a Sirius 800 with Nucleus 2450 controllers does not accept the hi SW-P-08 connection.
-
The 96-port and 192-port Vega Video Routers provide the General Switcher (SW-P-02) protocol for external control. The Vega 30 accepts SW-P-08 over Ethernet.
-
The Sirius 600 provides SW-P-08 on its serial ports only, and its Ethernet port uses the General Switcher (SW-P-02) protocol. hi connects over TCP, so a Sirius 600 does not accept the hi SW-P-08 connection.
What's Not Supported
-
Engineering-level configuration (level naming, port labels, redundancy setup) - use the vendor's native router-control tool.
-
Firmware updates - use the vendor's native update utility.
-
Hardware diagnostics and SFP-level health - surfaced by the device's own management plane, not this integration.
Trademarks
Note
Grass Valley and Rollcall are trademarks or registered trademarks of Grass Valley USA, LLC or its affiliated companies.
RIEDEL Communications is not affiliated with, endorsed by, or officially partnered with Grass Valley unless explicitly stated.