vega-30 user manual - grass valley

www.s-a-m.com

User Manual

Vega 30 SDI Router with Audio Routing

Vega 30 Router User Manual Top Level Contents

Issue1 Revision 1 © 2017 SAM

Top Level Contents

1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

2 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8

3 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14

4 Chassis and Connectors etc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31

5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

6 Vega 30 Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45

7 Vega 30 RollCall Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .100

8 Output Video Timing - Line Sync and Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . .154

9 Sources and Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

10 Routing Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .171

11 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .194

12 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .220

Appendix A Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

Appendix B Source and Destination Port Numbering . . . . . . . . . . . . . . . . . . . . . . .246

Appendix C Audio Channel Source and Destination Names and Numbers . . . . . .248

Appendix D SNMP MIB Files for the Vega 30 Router . . . . . . . . . . . . . . . . . . . . . . . .257

Appendix E Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Appendix F Persistence File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Appendix G Source and Destination Names File (Import and Export) . . . . . . . . . .276

Vega 30 Router User Manual Contents

Contents

1 About this Manual . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.1 Contact Details . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.2 Copyright and Disclaimer . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .71.3 Trademarks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .7

2 Safety . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.1 Explanation of Safety Symbols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.2 Safety Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.3 Mains Power Supplies. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

2.3.1 Supplied Power Cords . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122.4 Rack Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122.5 Compliance Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .122.6 EMC Standards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12

2.6.1 EMC Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.6.2 EMC Performance of Cables and Connectors . . . . . . . . . . . . . . . . . . . . . . .13

3 Product Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143.1 Vega 30 Features and Benefits. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153.2 Order Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.3 Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .163.4 Architecture and Signal Flow . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

3.4.1 Vega 30 Inputs and Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .173.4.2 Functional Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .183.4.3 Video Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193.4.4 Timed Video Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .193.4.5 Line Synchronizing and Offset from Reference . . . . . . . . . . . . . . . . . . . . . .19

3.5 Routing Architecture . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .203.5.1 Operational Routing and Direct Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.5.2 Video Crosspoint (34 x 34) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223.5.3 Audio Crosspoint. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233.5.4 Source and destination numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243.5.5 ‘Follow Video’ Audio Channel Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253.5.6 Lock Route 1:1 Feature . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253.5.7 Internal Test Tone Audio Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

3.6 Router Configuration and Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273.6.1 Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .273.6.2 Protocols . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28

3.7 Terminology. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

4 Chassis and Connectors etc. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.1 Unpacking . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.2 Chassis Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324.3 Chassis Front . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324.4 Front Panel Status Indicators . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334.5 Rear Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

4.5.1 Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374.5.2 Ethernet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384.5.3 Vega 30 Unit Resets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394.5.4 DC Power Inlets . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

4.6 Fuses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .40

5 Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415.1 Environmental Considerations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415.2 Chassis Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .415.3 Chassis Ventilation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42

5.3.1 Location in Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .425.4 Rack Mounting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43

5.4.1 Location in Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .43



5.4.2 Mounting the Vega 30 Router into a Rack . . . . . . . . . . . . . . . . . . . . . . . . . .435.4.3 Cabling Up in a Rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435.4.4 Connecting Power to Vega 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .445.4.5 Disconnecting Power to Vega 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

5.5 Initial Vega 30 Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

6 Vega 30 Web Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .456.1 Vega 30 Web Pages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .466.2 Home Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496.3 Source Names Page. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .51

6.3.1 Source Names Web Page - Apply Button. . . . . . . . . . . . . . . . . . . . . . . . . . .526.3.2 Source Names Web Page - Input Ports Table . . . . . . . . . . . . . . . . . . . . . . .536.3.3 Source Names Web Page - Source Names Table . . . . . . . . . . . . . . . . . . . .57

6.4 Renaming Pre-defined Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .636.5 Defining User-defined Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .64

6.5.1 User-defined Source - Defining a Source Name. . . . . . . . . . . . . . . . . . . . . .646.5.2 User-defined Source - Defining an Associated Video Source . . . . . . . . . . .656.5.3 User-defined Source - Entering Audio Channel Source Names . . . . . . . . . .686.5.4 Importing and Exporting Source and Destination Names . . . . . . . . . . . . . . .74

6.6 Destination Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .766.6.1 Import and Export Destination Names . . . . . . . . . . . . . . . . . . . . . . . . . . . . .79

6.7 Set Routes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .806.7.1 Cursors on the Set Routes Web Page . . . . . . . . . . . . . . . . . . . . . . . . . . . . .846.7.2 Simple Routing Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .856.7.3 4K Routing Example . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .876.7.4 Destination Protect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .89

6.8 Processing Control . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .916.9 Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .95

7 Vega 30 RollCall Templates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1007.1 Connecting RollCall Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .101

7.1.1 Connecting to the Vega 30 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1027.1.2 Connecting to the Vega 30 Routing Templates. . . . . . . . . . . . . . . . . . . . . .1057.1.3 Routing Matrix Levels . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .105

7.2 Unit Information Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1077.3 System Information Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1117.4 Source Configuration Template. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .113

7.4.1 Navigating the Source Configuration Screen . . . . . . . . . . . . . . . . . . . . . . .1157.4.2 Columns of the Source Configuration Template . . . . . . . . . . . . . . . . . . . . .1187.4.3 Defining User-defined Sources on the Source Configuration Template . . .119

7.5 Port Configuration Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1207.5.1 Port Configuration - Top Section of Template . . . . . . . . . . . . . . . . . . . . . . .1217.5.2 Port Configuration - Input Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1227.5.3 Port Configuration - Output Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .124

7.6 Comms Setup Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1277.6.1 Comms Setup - IP Address Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1287.6.2 Comms Setup - RollCall Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1297.6.3 Comms Setup - RollCall+ . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1307.6.4 Comms Setup - SNMP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1317.6.5 Comms Setup - General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1327.6.6 Comms Setup - Syslog (Logging) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1337.6.7 Comms Setup - Restart Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .133

7.7 Log Fields Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1347.8 Assoc Routing - XY Panel Control Template. . . . . . . . . . . . . . . . . . . . . . . . . . . .135

7.8.1 Routing Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1367.8.2 Edit Names Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1417.8.3 Edit Protect Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1427.8.4 Options Tab. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .143

7.9 Assoc Routing - Routing Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1487.10 Direct Video - XY Panel Control Template . . . . . . . . . . . . . . . . . . . . . . . . . . . .150



7.11 Direct Video - Routing Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1517.12 Direct Audio - XY Panel Control Template . . . . . . . . . . . . . . . . . . . . . . . . . . . .1527.13 Direct Audio - Routing Template . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .153

8 Output Video Timing - Line Sync and Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1548.1 Line Synchronizer and Offset from Reference . . . . . . . . . . . . . . . . . . . . . . . . . .154

8.1.1 Buffer Storage Capacity . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1548.2 User Controls . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1558.3 Input Signal Timing Use Cases. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .156

8.3.1 Timing Case 1) Input Arriving some Pixels Earlier than Reference . . . . .1578.3.2 Timing Case 2) Input Arriving Co-timed with Reference . . . . . . . . . . . . .1588.3.3 Timing Case 3) Input Arriving some Pixels Later than Reference . . . . . .159

8.4 Setting Up Router Offset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .160

9 Sources and Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1629.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162

9.1.1 Destinations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1629.1.2 Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1629.1.3 Defining User-defined Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1639.1.4 Source and Destination Port Numbering . . . . . . . . . . . . . . . . . . . . . . . . . .163

9.2 Source Types . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1639.3 User-defined Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .164

9.3.1 Video Source Numbers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1649.3.2 Audio Channel Source Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1649.3.3 ‘Follow Video’ Audio Channel Sources (DestThru) . . . . . . . . . . . . . . . . . . .1659.3.4 ‘Follow Video’ versus ‘Fixed’ Audio Channel Sources . . . . . . . . . . . . . . . .1659.3.5 Silence Audio Channel Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1689.3.6 Null Source . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1689.3.7 Partial Sources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .168

9.4 Making User-defined Sources. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .170

10 Routing Use Cases . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17110.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17210.2 Video-only Router Use Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17310.3 MADI-only Router Use Case. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17410.4 Video and MADI only router . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17510.5 Monitoring a Router Input and Output. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .176

10.5.1 Monitor a Video Input . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17610.5.2 Monitor Audio in a Router Video Output . . . . . . . . . . . . . . . . . . . . . . . . . .17710.5.3 Monitor a Router Video Output . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .179

10.6 Inserting Audio Channels into Router Inputs and Outputs . . . . . . . . . . . . . . . .18010.6.1 Inserting MADI Audio into a Video Input . . . . . . . . . . . . . . . . . . . . . . . . . .18010.6.2 Inserting MADI Audio into a Video Output . . . . . . . . . . . . . . . . . . . . . . . .18110.6.3 Inserting Embedded Audio into a Video Output . . . . . . . . . . . . . . . . . . . .18210.6.4 Inserting MADI audio channels into a MADI Output . . . . . . . . . . . . . . . . .184

10.7 Audio Channel-Swap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18610.7.1 Audio Channel-Swap in a Video Output . . . . . . . . . . . . . . . . . . . . . . . . . .18610.7.2 Embedded Audio Channel-Swap in a Video Input . . . . . . . . . . . . . . . . . .187

10.8 System Application Example. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18910.8.1 Target System Diagram . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .18910.8.2 System Implementation with Vega 30 Router . . . . . . . . . . . . . . . . . . . . . .191

11 Getting Started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19411.1 Vega 30 Rear Connections Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19411.2 Initial Powering and Starting Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .195

11.2.1 Disconnecting Power to Vega 30 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19611.3 Preliminary Vega 30 Router Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . .19711.4 Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19911.5 Initial Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19911.6 Basic Video Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .202



11.7 Basic MADI Audio Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20511.8 MADI Stereo Pair Audio Routing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20911.9 Embed a MADI Stereo Audio Pair into a Video Output . . . . . . . . . . . . . . . . . . .21511.10 Output Video Signal Timing. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .219

12 Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22012.1 Power Supply Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .22012.2 Airflow Cooling Fan Assembly Replacement . . . . . . . . . . . . . . . . . . . . . . . . . .22112.3 Software Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223

12.3.1 Checking Software Version on a Vega 30 Unit . . . . . . . . . . . . . . . . . . . . .22312.3.2 Software Upgrade Procedure (with SAM RollCall Control Panel). . . . . . .224

12.4 Installing a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23412.4.1 To View License Status on a Vega 30 Unit . . . . . . . . . . . . . . . . . . . . . . . .23412.4.2 To Obtain a License . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23612.4.3 Installing a License via the Vega 30 Web Page . . . . . . . . . . . . . . . . . . . .23712.4.4 Installing a License via RollCall Control Panel . . . . . . . . . . . . . . . . . . . . .238

Appendix A Specifications . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241A.1 Physical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241A.2 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241A.3 Compliance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241A.4 Electrical . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241

A.4.1 Vega 30 Unit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .241A.4.2 Vega 30 Power Supply Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242

A.5 Signal Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242A.6 Signal Outputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .242A.7 Reference Inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243A.8 Timed Switching . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243A.9 Audio V-Fade Rates . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244A.10 Built-in Audio Test Tone Generator . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244A.11 Router Ports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244A.12 Control and Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244A.13 Default IP Address . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244A.14 RollCall ID Numbers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .244A.15 Software Compatibility . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .245

Appendix B Source and Destination Port Numbering . . . . . . . . . . . . . . . . . . . . . . .246

Appendix C Audio Channel Source and Destination Names and Numbers . . . . . .248C.1 Audio Crosspoint - Overview of Source and Destination Numbers . . . . . . . . . .249C.2 Table of Audio Source and Destination Names and Numbers . . . . . . . . . . . . . .250C.3 Audio Channel Source Names Diagram. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .256

Appendix D SNMP MIB Files for the Vega 30 Router . . . . . . . . . . . . . . . . . . . . . . . .257D.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257D.2 MIB Support . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .257D.3 File listing: PROBEL-COMMON.mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .259D.4 File listing: Vega30Router.mib . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .260

Appendix E Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272E.1 Introduction. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .272E.2 Example Vega 30 Router Configuration File . . . . . . . . . . . . . . . . . . . . . . . . . . .272

Appendix F Persistence File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274F.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274F.2 Example Vega 30 Router Persistence File . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274

Appendix G Source and Destination Names File (Import and Export) . . . . . . . . . .276G.1 Example Default Names File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .276G.2 Example Real-world File Contents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .278


Vega 30 Router User Manual Contact Details About this Manual 1.1


1 About this Manual

Thank you for purchasing your new Vega 30 Router.

This Vega 30 Router User Manual describes and provides relevant safety information and instructions on how to install, configure and operate the Vega 30 router.

If you have any questions regarding the installation and setup of your product, please contact SAM Customer Support.

1.1 Contact Details

Customer Support

For details of our Regional Customer Support Offices and contact details please visit the SAM web site and navigate to:

https://s-a-m.com/support/247-support-contact-details/

Customers with a support contract should call their personalized number, which can be found in their contract, and be ready to provide their contract number and details.

1.2 Copyright and Disclaimer

Copyright protection claimed includes all forms and matters of copyrightable material and information now allowed by statutory or judicial law or hereinafter granted, including without limitation, material generated from the software programs which are displayed on the screen such as icons, screen display looks etc.

Information in this manual and any software are subject to change without notice and does not represent a commitment on the part of SAM. Any software described in this manual is furnished under a license agreement and can not be reproduced or copied in any manner without prior agreement with SAM or their authorized agents.

Reproduction or disassembly of embedded computer programs or algorithms is prohibited.

No part of this publication can be transmitted or reproduced in any form or by any means, electronic or mechanical, including photocopy, recording or any information storage and retrieval system, without permission being granted, in writing, by the publishers or their authorized agents.

SAM operates a policy of continuous improvement and development. SAM reserves the right to make changes and improvements to any of the products described in this document without prior notice.

1.3 Trademarks

Microsoft, Microsoft Windows and Windows are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks or registered trademarks are the property of their respective owners.


Vega 30 Router User Manual Safety

2 Safety

Erklärung der Sicherheitssymbole

Dieses Symbol weist denBenutzer auf wichtige Informationenhin, die in der begleitenden Dokumentation enthaltensind.

Dieses Symbol zeigt an, dass gefährliche Spannungvorhanden ist.Es befindensichkeine vomBenutzer zu wartendenTeile imGeräteinneren.Dieses Gerät solltenur vongeschultemPersonal gewartet werden

· Um das Risiko einesElektroschockszu reduzieren, setzen Sie dasGerät weder Regen nochFeuchtigkeit aus.

· Stellen Sie immer sicher, dass dasGerät ordnungsgemäßgeerdetund verkabelt ist.

· Dieses Equipment muss aneine Netzsteckdose mit SchutzleiterangeschlossenwerdenundeinenzuverlässigidentifizierbarenNullleiterhaben.

· Die Netzsteckdose solltenahe beim Gerät und einfachzugänglich sein.

Sicherheits-Warnhinweise

D

!

Die angeführten Service-/Reparatur-Anweisungen sindausschließlichvon qualifiziertemService-Personalauszuführen. Um das Risiko eines lektroschocks zureduzieren, führenSieausschließlich die imBenutzerhandbucheschriebenenAnweisungenaus,es sei denn, Sie haben die entsprechendeQualifikation.WendenSiesichinallenService-FragenanqualifiziertesPersonal.

! ACHTUNG

Gefahr vonElektroschocks.Abdeckungen nichtentfernen

Keine vomBenutzer zuwartendeTeileWendenSiesichausschließlich

anqualifiziertesPersonal

Explicación de los Símbolos de Seguridad

Éste símbolo refiere al usuario información importante contenida en la literatura incluida. Referirse al manual.

Éste símbolo indica que voltajes peligrosos están presentes en el interior. No hay elementos accesibles al usuario dentro.Esta unidad sólo debería ser tratada por personal cualificado.

Las instrucciones de servicio cuando sean dadas, son sólo para uso de personal cualificado. Para reducir el riesgo de choque eléctrico no llevar a cabo ninguna operación de servicio aparte de las contenidas en las instrucciones de operación, a menos que se esté cualificado para realizarlas. Referir todo el trabajo de servicio a personal cualificado.

· Para reducir el riesgo de choque eléctrico, no exponer este equipo a la lluvia o humedad.

· Siempre asegurarse de que la unidad está propiamente conectada a tierra y que las conexiones de alimentación están hechas correctamente.

· Este equipo debe ser alimentado desde un sistema de alimentación con conexión a TIERRA y teniendo una conexión neutra fácilmente identificable.

· La toma de alimentación para la unidad debe ser cercana y fácilmente accesible.

ESP

!

Advertencias de Seguridad

RIESGO DE CHOQUE ELECTRICONO QUITAR LAS PROTECCIONNESELEMENTOS NO ACCESIBLES ALUSUARIO.SERVICIO SOLAMENTE A PERSONALCUALIFICADO



Simboli di sicurezza:Questo simbolo indica l'informazione importante contenuta nei manuali appartenenti all'apparecchiatura. Consultare il manuale.

Questo simbolo indica che all'interno dell'apparato sono presenti tensioni pericolose. Non cercare di smontare l'unità. Per qualsiasi tipo di intervento rivolgersi al personale qualificato.

Le istruzioni relative alla manutenzione sono ad uso esclusivo del personale qualificato. E' proibito all'utente eseguire qualsiasi operazione non esplicitamente consentita nelle istruzioni. Per qualsiasi informazione rivolgersi al personale qualificato.

· Per prevenire il pericolo di scosse elettriche è necessario non esporre mai l'apparecchiatura alla pioggia o a qualsiasi tipo di umidità.

· Assicurarsi sempre, che l'unità sia propriamente messa a terra e che le connessioni elettriche siano eseguite correttamente.

· Questo dispositivo deve essere collegato ad un impianto elettrico dotato di un sistema di messa a terra efficace.

· La presa di corrente deve essere vicina all'apparecchio e facilmente accessibile.

I

!

Attenzione:

! ATTENZIONERISCHIO DI SHOCK ELETTRICONON CERCARE DI SMONTARE

L'UNITA PER QUALSIASI TIPO DI INTERVENTO RIVOLGERSI AL

PERSONALE QUALIFICATO

Forklaring på sikkerhedssymbolerDette symbol gør brugeren opmærksom på vigtig information i den medfølgende manual.

Dette symbol indikerer farlig spænding inden i apparatet. Ingen bruger servicerbare dele i apparatet på brugerniveau. Dette apparat må kun serviceres af faglærte personer..

Serviceinstruktioner er kun til brug for faglærte servicefolk. For at reducere risikoen for elektrisk stød må bruger kun udføre anvisninger i betjeningsmanualen. Al service skal udføres af faglærte personer.

· For at reducere risikoen for elektrisk stød må apparatet ikke udsættes for regn eller fugt.

· Sørg altid for at apparatet er korrekt tilsluttet og jordet.

· Dette apparat skal forbindes til en nettilslutning, der yder BESKYTTENDE JORD og 0 forbindelse skal være tydeligt markeret.

· Stikkontakten, som forsyner apparatet, skal være tæt på apparatet og let tilgængelig.

DK

!

!

Sikkerhedsadvarsler

! FORSIGTIGRISIKO FOR ELEKTRISK STØD

DÆKPLADER MÅ IKKE FJERNESINGEN BRUGER SERVICERBARE

DELE SERVICE MÅ KUN UDFØRESAF FAGLÆRTE PERSONER

Förklaring av SäkerhetssymbolerDenna symbol hänvisar användaren till viktig information som återfinns i litteraturen som medföljer. Se manualen.

Denna symbol indikerar att livsfarlig spänning finns på insidan.Det finns inga servicevänliga delar inne i apparaten. Denna apparat få endast repareras av utbildad personal.

Serviceinstruktioner som anges avser endast kvalificerad och utbildad servicepersonal. För att minska risken för elektrisk stöt, utför ingen annan service än den som återfinns i medföljande driftinstruktionerna, om du ej är behörig. Överlåt all service till kvalificerad personal.

· För att reducera risken för elektrisk stöt, utsätt inte apparaten för regn eller fukt.

· Se alltid till att apparaten är ordentligt jordad samt att strömtillförseln är korrekt utförd.

· Denna apparat måste bli försörjd från ett strömsystem som är försedd med jordadanslutning samt ha en neutral anslutning som lätt identifierbar.

· Vägguttaget som strömförsörjer apparaten bör finnas i närheten samt vara lätttillgänglig.

S

! CAUTIONRISK OF ELECTRIC SHOCKDO NOT REMOVE COVERS

NO USER SERVICEABLE PARTSREFER SERVICING TO QUALIFIED

PERSONNEL ONLY

!

Säkerhetsvarningar

Turvamerkkien selitysTämä merkki tarkoittaa, että laitteen mukana toimitettu kirjallinen materiaali sisältää tärkeitä tietoja. Lue käyttöohje.

Tämä merkki ilmoittaa, että laitteen sisällä on vaarallisen voimakas jännite. Sisäpuolella ei ole mitään osia, joita käyttäjä voisi itse huoltaa. Huollon saa suorittaa vain alan ammattilainen.

Huolto-ohjeet on tarkoitettu ainoastaan alan ammattilaisille. Älä suorita laitteelle muita toimenpiteitä, kuin mitä käyttöohjeissa on neuvottu, ellet ole asiantuntija. Voit saada sähköiskun. Jätä kaikki huoltotoimet ammattilaiselle.

· Sähköiskujen välttämiseksi suojaa laite sateelta ja kosteudelta.

· Varmistu, että laite on asianmukaisesti maadoitettu ja että sähkökytkennät on tehty oikein.

· Laitteelle tehoa syöttävässä järjestelmässä tulee olla SUOJAMAALIITÄNTÄ ja nollaliitännän on oltava luotettavasti tunnistettavissa.

· Sähköpistorasian tulee olla laitteen lähellä ja helposti tavoitettavissa.

FI

!

Turvaohjeita

!SÄHKÖISKUN VAARA ÄLÄ AVAA

LAITTEEN KANSIA EI SISÄLLÄKÄYTTÄJÄLLE HUOLLETTAVIAOSIA HUOLTO AINOASTAAN

AMMATTILAISEN SUORITTAMANA

VAROITUS



Símbolos de SegurançaO símbolo triangular adverte para a necessidade de consultar o manual antes de utilizar o equipamento ou efectuar qualquer ajuste.

Este símbolo indica a presença de voltagens perigosas no interior do equipamento. As peças ou partes existentes no interior do equipamento não necessitam de intervenção, manutenção ou manuseamento por parte do utilizador. Reparações ou outras intervenções devem ser efectuadas apenas por técnicos devidamente habilitados.

As instruções de manutenção fornecidas são para utilização de técnicos qualificados. Para reduzir o risco de choque eléctrico, não devem ser realizadas intervenções no equipamento não especificadas no manual de instalações a menos que seja efectuadas por técnicos habilitados.

· Para reduzir o risco de choque eléctrico, não expor este equipamento à chuva ou humidade.

· Assegurar que a unidade está sempre devidamente ligada à terra e que as ligações à alimentação estão correctas.

· O sistema de alimentação do equipamento deve, por razões de segurança, possuir ligação a terra de protecção e ligação ao NEUTRO devidamente identificada.

· A tomada de energia à qual a unidade está ligada deve situar-se na sua proximidade e facilmente acessível.

P

!

Avisos de Segurança


Vega 30 Router User Manual Explanation of Safety Symbols Safety 2.1

2.1 Explanation of Safety Symbols

2.2 Safety Warnings

CAUTION: These servicing instructions are for use by qualified personnel only. To reduce the risk of electric shock, do not perform any servicing other than that contained in the Operating Instructions unless you are qualified to do so. Refer all servicing to qualified service personnel.

2.3 Mains Power Supplies

The Vega 30 Router chassis has two DC power connectors, for up to two separate external Vega 30 power supply modules; these modules each have an IEC mains power socket.

The mains supply voltage will be auto-detected by the external power supply modules, provided it is in the range 100 - 240 Vac and 50 / 60 Hz.

Always ensure that the unit is properly earthed and power connections are correctly made.

This Vega 30 equipment with its separate external power supply modules must be supplied from a power supply system providing a PROTECTIVE EARTH connection and having a neutral connection which can be reliably identified.

The power circuit breakers or switches supplying power to the unit should be close to the unit and easily accessible.

This symbol refers the user to important information contained in the accompanying literature.

This symbol indicates that hazardous voltages are present inside. No user serviceable parts are inside. This system should only be serviced by trained personnel.

To reduce the risk of electric shock, do not expose this appliance to rain or moisture.

The installation and maintenance of the Vega 10 Series router(s) and any associated equipment must be carried out by persons qualified to work with equipment which may be connected to a mains electric supply.

CAUTIONRISK OF ELECTRIC SHOCK DO NOT REMOVE COVERS

NO USER SERVICABLE PARTS REFER SERVICING TO QUALIFIED

PERSONNEL ONLY


Vega 30 Router User Manual Rack Mounting Safety 2.4

2.3.1 Supplied Power Cords

The external Vega 30 power supply modules are each shipped with a power cord with a standard molded IEC female socket on one end and a standard mains plug on the other.

2.4 Rack Mounting

When rack-mounting the Vega 30 Router, a rack shelf is not required. Secure the Vega router to the rack using the front ears. See Section 5 “Installation” on page 41 for details.

2.5 Compliance Standards

This equipment complies with the following standards:

EN60950-1: 2006Safety of information Technology Equipment Including Electrical Business Equipment.

UL1419 (4th Edition) - UL File E193966 Standard for Safety - Professional Video and Audio equipment

2.6 EMC Standards

This unit conforms to the following standards:

EN 55032:2012 (Class A)

EN 55103-2:2009 (Environment E2)

EN 61000-3-2:2014 (Class A)

EN 61000-3-3:2013

Federal Communications Commission Rules, 47 CFR: Part 15, Subpart B (Class A)

• The Vega 30 with its external power supply modules has more than one power supply cord. To reduce the risk of electrical shock, disconnect all the power supply cords before servicing.

• Isolate the unit from the outputs of other products before servicing.

• The DC power inlets on the Vega 30 Router are the DC power disconnection devices for the Vega 30 Router unit.

• The IEC power inlets on the Vega 30 external power supply modules are the AC mains power disconnection devices for the Vega 30 Router and its external DC power supply unit modules.

• To reduce the risk of electric shock, plug each power supply cord into separate branch circuits employing separate service grounds.

Warning:

This equipment is compliant with Class A of CISPR 32. In a residential environment this equipment may cause radio interference.


Vega 30 Router User Manual EMC Standards Safety 2.6

2.6.1 EMC Environment

The product(s) described in this manual conform to the EMC requirements for, and are intended for use in:

The controlled EMC environment (for example purpose-built broadcasting or recording studios), and the rural outdoor environment (far away from railways, transmitters, overhead power lines, etc.) E4.

2.6.2 EMC Performance of Cables and Connectors

SAM products are designed to meet or exceed the requirements of the appropriate European EMC standards. In order to achieve this performance in real installations it is essential to use cables and connectors with good EMC characteristics.

All signal connections (including remote control connections) shall be made with screened cables terminated in connectors having a metal shell. The cable screen shall have a large-area contact with the metal shell.

Coaxial Cables:

Coaxial cable connections (particularly serial digital video connections) shall be made with high-quality double-screened coaxial cables such as Belden 1694.


Vega 30 Router User Manual Product Overview

3 Product Overview

The Vega 30 is part of the Vega 10 Series; it offers compact, powerful video and audio routing with simple installation and switching. Line-synchronized and clean-quiet-switching outputs give smooth program transitions. It suits simple video-only applications through to complex live TV production.

The Vega 30 is a fixed 34x34 video router with audio routing capability. It is a non-modular, shallow 3RU unit which can be simply configured on-line via its web interface. It may be controlled via a browser control panel, with SAM Luna hardware control panels, over ethernet with remote protocols, and via SNMP. It has optional redundant power supplies.

Figure 1 Vega 30 Router


Vega 30 Router User Manual Vega 30 Features and Benefits Product Overview 3.1

3.1 Vega 30 Features and Benefits

• 3RU, shallow-depth.

• Light-weight.

• Dual Redundant PSU.

• Simple Video and Audio Routing:

• Up to 34 x 34, fixed video routing.

• Up to 736 x 928 fixed audio routing.

• Hybrid video and audio routing.

• Supports quad-link co-timed switching.

• Timed switching.

• Video:

• HD-BNC connectors.

• 4K, 3G, HD, SD.

• Audio:

• Audio embedding and de-embedding.

• Hybrid audio routing.

• MADI I/O interfaces:3 inputs, 6 outputs.

• Passes Dolby data.

• Fast, simple Web configuration.

• Powerful processing:

• Audio input de-embedding.

• Output embedding from MADI or embedded audio channel sources.

• Output Line Synchronizing.

• Clean and Quiet switching.

• Comprehensive Control and monitoring:

• Web browser control panel routing and processing.

• RollCall Control Panel interface.

• Soft panel applications.

• Hardware panels, Luna panels.

• Remote control with standard protocols over ethernet.:General Switcher (SW-P-02)General Remote (SW-P-08)

• SNMP control and monitoring.


Vega 30 Router User Manual Order Codes Product Overview 3.2

3.2 Order Codes

3.3 Options

The basic Vega 30 Router is a 34x34 SDI video-only router with timed-switching. It routes video and embedded audio. Licensable options are available to add audio routing and add processing on outputs. See Table 2.

Order Code Description

Vega 30 Router:

VG30 Vega 30 Router (34x34 video) with single PSU.

VG30-PSU Vega 30 Power Supply Unit (Second, redundant)

VG30-P2 Router package: Vega 30 Router (34x34 video) with single PSU + 12 Clean & Quiet Switching outputs. (VG30 + VG10-CSA + VG10-AR)

License Options:

VG10-CSA Enable Line Sync and Clean Switching on outputs 1-12 (and Quiet Switching with option VG10-AR)

VG10-CSB Enable Line Sync and Clean Switching on outputs 13-24 (and Quiet Switching with option VG10-AR)

VG10-CSC Enable Line Sync and Clean Switching on outputs 25-34 (and Quiet Switching with option VG10-AR)

VG10-AR Enable Audio Routing, Audio embed/de-embed, and MADI inputs and outputs. Quiet switching at outputs (with a VG10-CSx license).

Spares:

VG30-PSU Vega 30 Power Supply Unit (Main or redundant)

VG30-FAN Vega 30 Replacement Fan Assembly

Table 1 Vega 30 Router Order Codes

OptionSDI Video

34x34Router

Number of PSUs

Video SDI Outputs MADI Inputs and

Outputs

Audio Routing

Audio Embed/

De-embed1 to 12 13 to 24 25 to 34

Basic Router:

VG30 Yes 1 TS TS TS No No No

Options:

VG30-PSU 1 - - - - - -

VG10-CSA - LS, CS - - - - -

VG10-CSB - - LS, CS - - - -

VG10-CSC - - - LS, CS - - -

VG10-AR - QSSee Note 1 QSSee Note 1 QSSee Note 1 Yes Yes Yes

Where: TS - Timed switching; LS - Line Sync on output; CS - Clean switching at output; QS - Quiet switching at output.

Note 1: Quiet switching at outputs requires VG10-AR option and one or more VG10-CSx options.

Table 2 Features of the Vega 30 Router Options


Vega 30 Router User Manual Architecture and Signal Flow Product Overview 3.4

3.4 Architecture and Signal Flow

3.4.1 Vega 30 Inputs and Outputs

The Vega 30 Router is powered by one or two separate Vega 30 power supply modules.The router simply requires:

• An analog reference signal for SMPTE RP-168-2009 compliant switching.

• An ethernet connection for control.

Video inputs and MADI audio inputs are routed to video outputs and MADI audio outputs. (Note: Audio routing requires option VG10-AR.)

The inputs and outputs are shown in Figure 2 and are listed below:

• Signal Inputs:

• Video inputs - 34-off HD-BNC.

• MADI Audio inputs - 3-off HD-BNC. (64 audio channels per input.)

• Signal Outputs:

• Video outputs - 34-off HD-BNC.

• MADI Audio outputs - 6-off HD-BNC. (64 audio channels per output.)

• Reference: Includes a switchable 75R termination.

• Reference input - 1-off HD-BNC for analogue reference signal.

• Reference output - 1-off HD-BNC, loops through the Reference input.

• Ethernet LAN port - RJ45 connector.

• Power: DC power inputs:

• PSU1- Connect the supplied Vega 30 Power Supply Module.

• PSU2 -Connect optional Vega 30 Power Supply Module. (Purchased separately.)

Figure 2 Vega 30 Router Inputs and Outputs



3.4.2 Functional Description

Figure 3 shows a block diagram of the Vega 30.

Video Crosspoint Switch - Fixed-size routing matrix. Routes video inputs to one or more outputs of the Video Crosspoint Switch,.

Timed Switching - Controls route switch timing compliant to SMPTE RP-168-2009.

Line Sync - Adjusts input line timing to synchronize video outputs and, if required, adds in delay to output.

De-Embed - De-embeds embedded audio coming from the video crosspoint and passes it to the Audio Crosspoint Switch.

Audio Crosspoint Switch - Optional audio routing allows additional, separate routing of audio, including MADI audio.

Embed - Embeds audio from the audio crosspoint back into output video. This can simplify system installation by removing a need for external audio embedders.

Clean Quiet Switch (CQS) - Gives smooth non-visible transitions and removes any audio clicks and pops associated with a switched transition.

Timing and Control - Provides timing and control to the router’s functional blocks.

Dual Redundant Power - Allows the unit to operate from separate mains power supplies via Vega 30 DC Power Supply Modules.

Figure 3 Vega 30 Router Functional Block Diagram



3.4.3 Video Reference

The Vega 30 Router auto-detects a bi-level or tri-level analogue reference sync signal and reports the video standard. The Vega 30 Router has one video reference input. There is a reference loop-through output and a selectable termination to 75R.

The video reference signal is used as the timing basis for video line switching. Switching is then done independently for each router input (to SMPTE RP-168-2009).

The video standards for the Vega 30 reference input signal and for route switching are defined as part of the unit configuration.

3.4.4 Timed Video Switching

The Vega 30 does timed switching to SMPTE RP-168-2009 for video input signals which are compliant with SMPTE RP-168-2009 and which share the same frame rate. The router will switch between inputs on the switching line according to the video switching standard of the signal being switched to.

Using one video reference signal, the video switching standard can be configured separately for each input. For example, with a 1080i50 analogue reference signal, 1080i50, 1080p50 and 625i25 signals can be timed-switched.

3.4.5 Line Synchronizing and Offset from Reference

Each switched video output can be independently line-synchronized and, if required, can be further delayed from the reference timing.

• Line Synchronizing - synchronizes the router output to the video reference according to the routed input’s timing switching standard.

• Delay - if required, delay can be added into each router output to offset the output signal timing from the reference signal timing.

See Section 6 "Output Video Timing - Line Sync and Offset" on page 45 for more information.

Note: The Vega 30 Router carries out timed-switching which is only supported for a single frame rate at any one time. For example, with a 50Hz reference, 59.94Hz and 60Hz frame rate signals cannot be timed-switched.

Important: If there is no reference input signal, the router will crash-switch upon receiving a routing switch command.

If a video input signal is inconsistent with the configured video switching standard set up for that input, then the signal will be crash-switched.

When using an interlaced reference signal, progressive video sources are only switched on the first field of the reference signal.


Vega 30 Router User Manual Routing Architecture Product Overview 3.5

3.5 Routing Architecture

The Vega 30 Router basically routes sources to destinations. The Vega 30 Router contains a video crosspoint switch and an audio crosspoint switch, as shown in Figure 4.

The routing is carried out in a video crosspoint switch and an audio crosspoint switch.

The video crosspoint essentially routes Vega 30 video inputs to video outputs.

The audio crosspoint is located after the video crosspoint. The audio crosspoint routes external MADI input audio and internal de-multiplexed audio channels to external MADI outputs and internal audio ‘re-multiplex’ streams (for embedding into video outputs).

Router use cases are considered for the Vega 30 routing architecture in Section 10 "Routing Use Cases" on page 171.

Sources and destinations are allocated numbers and names. There are 8-character and 32-character names, and default names are allocated. The names are editable via the unit’s Web interface or via a RollCall template.

Figure 4 Vega 30 Routing Architecture



3.5.1 Operational Routing and Direct Routing

The router switches sources to destinations. The router has pre-defined and user-defined sources. A video channel (selected from video inputs) and audio input channels (selected from embedded audio inputs or from MADI audio inputs) are grouped together (associated) to form defined sources. These source associations are used when normally operating the router. This operational routing is sometimes called ‘routing by association’; it controls both the video and audio crosspoints together in unison.

Operational routing can be done via the Vega 30 unit’s Web interface, from RollCall Control Panel and via other control interfaces.

Control of the routing can also be done directly on each video or audio crosspoint switch separately; this is direct routing. There is ‘direct video’ routing and ‘direct audio’ routing.Direct routing is not available on the unit’s Web interface.

Figure 5 shows the levels of control over the router for operational routing and for direct routing.

Figure 5 Router Control:a) Operational Routing, with defined Source Associations,

controlling both Crosspoints together in unison.b) Direct Video Routing of the Video Crosspoint.c) Direct Audio Routing of the Audio Crosspoint.

a) Operational Routing controlling both crosspoints in unison (via source ‘associations’)

b) Direct video routing

c) Direct audio routing



3.5.2 Video Crosspoint (34 x 34)

The video crosspoint switch routes video and embedded audio together. A video source or destination comprises one video with up to 16 embedded audio channels.

Sources 1 to 34:

• Vega 30 Router’s video inputs. These inputs each carry video + up to 16 channels of embedded audio.

Destinations 1 to 34:

• Video crosspoint outputs (Video Xpt Outputs 1 to 34), internal nodes within the unit.These each comprise video + up to 16 channels of embedded audio.

Figure 6 shows the video crosspoint switch video source and destination numbering.

Destinations 1 to 34 form the router video outputs 1 to 34 after audio de-multiplexing and re-multiplexing stages involving the audio crosspoint.

Figure 6 Video Crosspoint Source and Destination Numbering

Routed video signals, at Video Crosspoint outputs (internal nodes)

Router’s Video Inputs Router’s Video Outputs

Video Sources1 to 34



3.5.3 Audio Crosspoint

The audio crosspoint is located after the video crosspoint. The audio crosspoint routes individual audio channels from external MADI inputs and from internal de-multiplexed audio channels to external MADI outputs and to internal audio embedders on the video outputs.

The audio crosspoint is 736 x 928.

Sources of audio signals:

• Vega 30 Router’s MADI audio inputs 1 to 3. These inputs each contain up to 64 channels of audio.

• Internal ‘Audio De-muxes’:These are de-embedded audio channels from each internal routed video signal. (16 channels of audio per routed video signal.)

• Internal audio silence and test tones (not shown in figure).

Destinations for audio signals:

• Vega 30 Router’s MADI audio outputs 1 to 6: These outputs each contain 64 channels of audio.

• Audio re-mux channels:These are audio channels to be re-embedded into the routed video signals to form the Vega 30 Video output. Each output has 16 embedded audio channels.

Figure 8 shows the routing architecture with audio channel source and destination numbers annotated onto the audio crosspoint.

Figure 7 Vega 30 Routing Architecture (re-cap)



3.5.4 Source and destination numbers

The audio source and destination numbers in Figure 8 are fixed and refer to precise ports on the audio crosspoint.

(See Appendix C “Audio Channel Source and Destination Names and Numbers” on page 248 for a table of audio crosspoint audio channel source and destination numbers.)

Figure 8 Vega 30 Audio Routing Diagram

Audio channel source numbers

Routed video signals (Xpt.Out) Audio embedded into Video Outputs

Audio de-embedded from routed video(at Video Crosspoint Outputs)

Embedded Audio to Audio Crosspoint

Audio Sources1 to 741

Audio Destinations1 to 928

Note: Fixed Audio Sources.

The audio sources and destinations are fixed. They refer to precise ports on the audio crosspoint.



3.5.5 ‘Follow Video’ Audio Channel Sources

In the compact Vega 30 Router architecture, the audio crosspoint is located after the video crosspoint. The result of this is that the audio signals present in the de-muxed audio channels (i.e. embedded audio from the video crosspoint) depend on the routing in the video crosspoint itself.

Extra, special ‘follow video’ audio channel sources actively take the video crosspoint routing into account. They may be used to easily specify an embedded audio channel source relative to an associated video source signal.

‘Follow video’ audio channel sources are used in many use cases when defining one or more user-defined sources for Vega 30.

3.5.6 Lock Route 1:1 Feature

The internal ‘Audio De-mux’ audio sources give the audio crosspoint access to embedded audio after the video crosspoint. In order to be able to access embedded audio directly from before the video crosspoint regardless of any video routing, a ‘Lock Route 1:1’ configuration feature is available on each video crosspoint destination.

‘Lock Route 1:1’ routes the input source video with its embedded audio across the video crosspoint and to the corresponding video crosspoint destination. (For example, video source 31 to destination 31 on the video crosspoint). All other video crosspoint routing to that destination is prevented when the ‘Lock Route 1:1’ is enabled. Audio routing, however, is still permitted to the destination.

Thus, ‘Lock Route 1:1’ makes a ‘1:1’ route and locks the video crosspoint destination. The audio crosspoint can then always directly access input embedded audio on the video input. See Figure 9.

Note: ‘Follow Video’:

There are just 16 ‘Follow Video’ audio source channels. They correspond to the 16 embedded audio channels of a user-defined source’s associated video source.

Note: ‘Lock Route 1:1’ affects the video crosspoint. It does not affect the audio crosspoint.

‘Lock Route 1:1’ is a configuration setting and not an operational control.



3.5.7 Internal Test Tone Audio Sources

Audio test tones are available to the audio crosspoint switch as internal, pre-defined audio channel sources, these include:

• Audio Test tones.

• Left- and Right-channel ID signals.

• Audio Silence.

(See A.10 “Built-in Audio Test Tone Generator” on page 244 for more information.)

Figure 9 Video Crosspoint Lock Route 1:1

Note: When ‘Lock Route 1:1’ is enabled, it locks a video crosspoint source-destination routing.However, ‘Lock Route 1:1’ does not affect any audio crosspoint routing.

Note: When ‘Lock Route 1:1’ is enabled for a video crosspoint source-destination, the effective size of the video router is reduced. The benefit is, however, that input audio is always directly available to the audio crosspoint.

Internal Audio De-mux sources

Input embedded audio from the ‘Lock Route’ video input is always directly available to the audio crosspoint.

Locked Route


Vega 30 Router User Manual Router Configuration and Control Product Overview 3.6

3.6 Router Configuration and Control

3.6.1 Overview

Vega 30 unit configuration may be done in either of the following ways:

• Web browser. (See Section 6 "Vega 30 Web Interface" on page 45.)

• RollCall. (See Section 8 "Configuration with RolllCall" on page 117.)

A user can thus configure a unit and backup/restore configuration and persistent data (route settings and adjustable CQS parameters).

The following router control methods are available:

• Vega 30 Web browser control panel for routing and processing.

• RollCall interface.

• SAM Luna hardware control panels.

• Protocols:

• General Switcher (SW-P-02) protocol on ethernet.

• General Remote (SW-P-08) protocol on ethernet.

• SNMP.

Figure 10 Example Vega 30 Router System Layout

Local Area Network

PC Mac

PC

SAM HardwareControl Panel

SAM HardwareControl Panel

RollCall Control Panel installed on

a Windows PC

Vega 30 Web Interface browsed on an Apple Mac

Vega 30 Web Interface browsed on a Windows PC

Vega 30 Router


Vega 30 Router User Manual Router Configuration and Control Product Overview 3.6

3.6.2 Protocols

3.6.2.1 SW-P-02 General Switcher Protocol

Supported commands:

• Connect.

• Interrogate.

• Connect on Go Group Salvo - New command now supported including Extended Command.

• Go Group Salvo - New command now supported.

• Extended Protect Interrogate - New command now supported.

• Extended Protect Tally Dump Request - New command now supported.

• Protected Device Name Request - New command now supported.

Eight simultaneous clients.

3.6.2.2 SW-P-08 General Remote Protocol

Supported commands:

• Connect - Now supports Extended command.

• Interrogate - now supports Extended command.

• Protect Connect - Now supports Extended Commands..

• Protect Interrogate - Now supports Extended command.

• Protect Disconnect - Now supports Extended Commands.

• Protect Tally Dump.

• Device Name Request.

• Tally Dump Request.

• Connect on Go Group Salvo - Now supports Extended Commands.

• Go Group Salvo.

• Enquire Connect - Now supports Extended Commands.

• Protect Tally Dump Request - Now supports Extended Commands.

• Tally Dump Request - Now Supports Extended commands.

• All Source Names Request - New command supported includes Extended Command option.

• All Destination Association Names Request - New command supported includes Extended Command option.

• All Source Association Names Request - New command now supported.

Eight simultaneous clients.

3.6.2.3 SNMP

• Traps with support for 10 servers.

• MIB Browse/Walk.

• Route Setting.

• PSU fail, Fan fail.

Mib files are outlined in Appendix D “SNMP MIB Files for the Vega 30 Router” on page 257.


Vega 30 Router User Manual Terminology Product Overview 3.7

3.7 Terminology

Terms used in this Vega 30 Router User Manual are listed and defined in the table below:

Term Definition

Association A logical grouping of sources, or of destinations, which allows several signals to be routed together. These are normally of different signal types e.g. audio channels associated with a video source.

Association Routing Routing using associations, i.e. associated sources and associated destinations.

Audio Channel Source Sources for each audio channel in a source association.

Audio De-mux Point Internal node within a Vega 30 router. Provides access to the embedded audio in the video crosspoint outputs.

Channel A signal may be a composite of several signals or channels. For example, the 16 embedded audio channels in a video signal.

Clean switch A switch transition resulting in a signal waveform with no or minimal disturbance in the switched signal waveform.

Crosspoint Switch (Crosspoint)The switching component of a router. There can be more than one crosspoint switch. For example, video crosspoint and audio crosspoint.

Destination An output of a crosspoint.

Direct Audio Routing Routing the audio crosspoint, using source and destination port names or fixed numbers, not using associated sources and destinations.

Direct Video Routing Routing the video crosspoint, using source and destination port names and fixed numbers, not using associated sources and destinations.

Follow Video A type of audio channel source which gives automatic access to the embedded audio in a routed video signal.

Input Router input connection.

Line Sync (Line Synchronizer)A feature which aligns the timing of video signals.

Lock Route 1:1 Setting Lock Route 1:1 guarantees the presence of input video at the corresponding output of the video crosspoint. Used to give audio routing direct access to the input embedded audio.

MADI Multichannel Audio Digital Interface

Null Source A video or an audio channel source of ‘null source’ has no effect when routed.

Output Router output connection.

Table 3 Vega 30 Router Terminology


Vega 30 Router User Manual Terminology Product Overview 3.7

Partial Source A user-defined source which contains one or more ‘null sources’.

Pre-defined Source A source inherently defined in a router. These are not editable by the user. In Vega 30, these are associated sources.

Port Input or output signal connection to the router.

Port Name Name given to a router port. Typically, the name can be edited.

Port Number Number assigned to a router crosspoint port. The number is fixed.

Protect destination A feature of a destination. Set ‘Protect Destination’ on a destination to prevent a route being made to it.

‘Protect’ is an operational control.

Quiet switch A switch transition with no audible disturbance.

Route The connection made within a router in a crosspoint, connecting an input to an output.

Router A Vega 30 unit with physical signal input and output connections, where the inputs can be routed to any output. A router may be able to route more than one type of signal.

Signal Information carried by a connection between equipment in a facility. For example video or audio data.

Source A set of one or more crosspoint inputs which can be routed at the same time. For example, video together with embedded audio channels.

Source port name Name assigned to a source. For example, “BBC News”.

Tally Message sent out of a comms port by a router to confirm that a command to set a route has been received. It does not mean that a route has been set.

Timed switch Switching between two signals in a crosspoint switch at a time consistent with SMPTE RP-168-2009. The timing of the switching is governed by the signal being switched to.

User-defined source A source which can be defined by the user. In Vega 30, these are associated sources.

Term Definition

Table 3 Vega 30 Router Terminology (Continued)


Vega 30 Router User Manual Unpacking Chassis and Connectors etc. 4.1

4 Chassis and Connectors etc.

This section describes the Vega 30 Router from the outside and contains information on:

4.1 Unpacking

The Vega 30 Router is supplied in dedicated packaging provided by the manufacturer and should not be accepted if delivered in inferior or unauthorized materials.

1. Carefully unpack the system components and check them against the listed items here:

• Vega 30 Router main unit.

• One Vega 30 Power Supply Module.

• AC mains cord.

If there is anything incorrect notify your SAM Partner, or SAM, at once.(https://s-a-m.com/support/247-support-contact-details/)

2. Check that the equipment has not been damaged in transit. If any damage has occurred notify your SAM Partner (or SAM directly) and the carrier immediately.

3. Always retain the original packing materials if possible, they could prove useful should it ever be necessary to transport or ship the equipment.

4. Always read the installation and user instructions carefully, it will provide you with helpful hints and tips about care and maintenance and help you get the most out of your Vega 30 Router. (SAM manuals may be downloaded from https://s-a-m.com/support/routers/)

5. Place the unit on a suitable surface for preliminary inspection.

4.1 “Unpacking” page 31

4.2 “Chassis Overview” page 32

4.3 “Chassis Front” page 32

4.4 “Front Panel Status Indicators” page 33

4.5 “Rear Panel” page 35

4.6 “Fuses” page 40


https://s-a-m.com/support/routers/




Vega 30 Router User Manual Chassis Overview Chassis and Connectors etc. 4.2

4.2 Chassis Overview

The Vega 30 Router is a shallow 3RU 19” rack-mount chassis (approximately 65 mm deep) with connectors at the rear, see Figure 11. It has a grille at the front and an integral cooling fan at the rear. On the rear, there are two DC power inlets and an array of video, audio, control and data signal connectors.

There are up to two dual-redundant power supply unit (PSU) modules external to the chassis, which supply DC power to the Vega 30 Router unit.

The router chassis is air-cooled and the airflow is front-to-back and side-to-side.

For chassis dimensions, see 5.2 “Chassis Dimensions” on page 41

4.3 Chassis Front

The front of the Vega 30 Router unit chassis has an air inlet grille and some status indicator lights. See Figure 12.

Figure 11 Vega 30 Router front and rear views

Vega-30 (Front view)

Vega-30 (Rear view)

Figure 12 Vega 30 Router Front View

Airflow inlet grille Indicators


Vega 30 Router User Manual Front Panel Status Indicators Chassis and Connectors etc. 4.4

4.4 Front Panel Status Indicators

The front indicators are shown in Figure 13. The operational states of these LED indicators is

described in Table 4 and Table 5.

Figure 13 Vega 30 Router Front Indicators

LED Color LED Status Description

PSU 1 Indicates status of power supplied at PSU 1 DC power rear inlet:

Green DC power present on the rear PSU 1 DC power inlet.

Red No DC power present at rear PSU 1 DC power inlet.

OffVega 30 is configured for one DC power inlet (PSU 2 rear inlet) and there is no DC power present at the PSU 1 inlet.

PSU 2 Indicates status of power supplied at PSU 2 DC power rear inlet:

Green DC power present on the rear PSU 2 DC power inlet.

Red No DC power present at rear PSU 2 DC power inlet.

OffVega 30 is configured for one DC power inlet (PSU 1 rear inlet) and there is no DC power present at the PSU 2 inlet.

FAN Indicates fan status:

Green Fan OK.

AmberIndicates a fan problem condition. For example, a slow-running fan.

Red Fan Failure or Over Temperature condition.

Table 4 Vega 30 Router Front - PSU and Fan LED Operational Information

Note: A Vega 30 Router’s PSU configuration is set up via the unit’s web interface, see Table 29 on page 98 in Section 6.9 "Configuration".


Vega 30 Router User Manual Front Panel Status Indicators Chassis and Connectors etc. 4.4

LED Color LED Status Description

SYSTEM Indicates Vega 30 system status:

FlashingGreen

Slow flashing, 0.5 Hz. System OK.

Quick FlashingGreen

Quick flashing, 2 Hz. System is loading and reverting to a previous configuration file and persistence file.

additionalPulse Yellow

Pulse: 0.1 sec on, 0.3 sec off. A remote command received. E.g. to set a route.

additionalPulse Red

Pulse: 0.1 sec on, 0.3 sec off. A corrupted IP message received.

additionalDbl Pulse Red

Double pulse: 0.1s on, 0.1s off, 0.1s on, 0.3s off. Unrecognized IP message received.

Pulsing RedPulsing once every 2s. System error, no network connection.

2 Pulsing RedPulsing twice every 2s. System upgrade error.

3 Pulsing RedPulsing three times every 2s. Invalid license file.

Blue System starting up.

Flashing BlueQuick flashing, 2Hz. System is upgrading (via RollCall or with a Factory Reset).

Blue Flashing Red

System start up error.

FlashingMagenta

Quick flash, 2Hz. A system Factory Reset has started.

Table 5 Vega 30 Router Front - System LED Operational Information

Note: Factory LED states:

The front LED indicators are also in use when manufacturing and testing the unit. These are not operational states and should not be seen by the user.


Vega 30 Router User Manual Rear Panel Chassis and Connectors etc. 4.5

4.5 Rear Panel

The Vega 30 Router rear panel is shown in Figure 14 and Figure 15. The rear panel houses a cooling fan, a chassis ground point and various connectors. The cooling fan is a replaceable item. See 12.2 “Airflow Cooling Fan Assembly Replacement” on page 221. The Vega 30 Router chassis may be earthed with an earthing wire at the Chassis Ground Point.

Figure 14 Vega 30 Router Rear Panel

Figure 15 Vega 30 Router Rear Panel (Annotated)

Cooling Fan Housing

MADI Outputs(HD-BNC)

Reference(HD-BNC)

“PSU”DC Power Inlets

Ethernet

Unit Resets

Video Inputs1-34

(HD-BNC)

Chassis Ground Point

MADI Inputs 1 to 3(HD-BNC)

Video Outputs1-34

(HD-BNC)

13

57

24

68 . . . . . . . . . . . . 32

34

. . . . . . . . . . . . . . . 3133 1

35

7 . . . . . . . . . . . . . . . . 3133

24

68 . . . . . . . . . . . . . . . 32

34

1 2 3

3546

21



Connection Rear Marking Description

Video Inputs INPUTS 1 to 34 34-off HD-BNC SDI video inputs.

Four staggered rows. Odd numbered inputs below. Even-numbered inputs above. See Figure 15.

Video Outputs OUTPUTS 1 to 34 34-off HD-BNC SDI video outputs.

Four staggered rows. Odd numbered inputs below. Even-numbered inputs above. See Figure 15.

MADI Inputs MADI IN 1 to 3 3-off HD-BNC MADI audio inputs.

MADI Outputs MADI OUT1 to 6 6-off HD-BNC MADI audio outputs.

Table 6 Vega 30 Video and Audio Rear Connections

Note: MADI inputs and outputs:

MADI audio input and output connectors are located among the video outputs and are clearly marked “MADI”.



4.5.1 Reference

The Vega 30 unit detects any analogue reference signal and switches video synchronized to the reference. Timed switching of video signals can be achieved for video signals with the same frame rate as the reference signal.

Figure 16 Vega 30 Router Rear - Reference Connection:a) Reference Connections.b) 75R Termination Slide Switch Operation.

Connection Rear Marking Description

Ref In REF 1-off HD-BNC

Analog reference.

Ref Loop Out REF 1-off HD-BNC

Analog reference, passively looped-through from the Ref In connection.

Termination Slide-Switch

TERM Slide-switch to add a 75R termination to the reference input.

See Figure 16b for switch operation.

Table 7 Vega 30 Reference Connections

Note: Reference Input and Loop Output:

Either of the two REF HD-BNC connectors may actually be used for reference input. The other connector may then be used as the loop output.

75R termination slide-switch:

75R Terminated

Reference Input

Reference Loop Output

UNterminated

a) b)



4.5.2 Ethernet

There is an RJ-45 ethernet connector on the unit rear, providing the unit with a 1 Gbps ethernet port.

Figure 17 Vega 30 Router - Ethernet Connection

Ethernet Link LEDs Description

Off Off No network connection.

Off Flashing GREEN

10M link.

Flashing YELLOW

Flashing GREEN

100M link.

Flashing YELLOW

Off1G link.

Table 8 Vega 30 Ethernet LEDs

Ethernet connector

Ethernet Link LEDs



4.5.3 Vega 30 Unit Resets

4.5.3.1 Factory Reset

To initiated a Factory Reset:

1. Either:

• Push and hold the Factory Reset push button and power cycle the Vega 30 Router. Release the push button after 10 seconds.

Or

• Push and hold the Factory Reset push button and push the Reset push button for 5 seconds. Release the Factory Reset push button after 10 seconds.

A Factory Reset process starts.

2. During the Factory Reset, the front System LED flashes magenta; then the System LED flashes blue.

3. The unit is ready when the System LED is flashing green.

The unit has been Factory Reset. The unit will need to be re-configured to the required settings.

Figure 18 Vega 30 Router - Unit Resets

Unit ResetFactory Reset

Control Rear Marking Description

Factory Reset FACTORY RESET Recessed push button.

Initiates a Factory Reset process to return the Vega 30 Router to its factory-set state.

Unit Reset RESET Recessed push button.

Push for 5 seconds to reset the Vega 30 Router unit.

A unit reset and can take 2 to 3 minutes to complete its reset. The previous state of the router is restored.

The unit is ready for use when the front System LED is flashing green.

Table 9 Vega 30 Rear - Reset Push Buttons

Note: After a Factory Reset:

All Vega 30 Router software, configuration settings and unit state are returned to their factory-set, default states. This includes the software version and the IP address etc.


Vega 30 Router User Manual Fuses Chassis and Connectors etc. 4.6

4.5.4 DC Power Inlets

The Vega 30 Router may be DC powered from one or two external power supply unit (PSU) modules. There are two DC power inlets on the rear of the Vega 30: Either DC power inlet may be used as the primary power supply inlet.

Powering the Vega 30 Router from two Vega 30 PSU’s, with each PSU connected to separate mains supplies, provides full power supply redundancy.

4.6 Fuses

The Vega 30 Router chassis has internal fuses which are not user-serviceable.

The external Vega 30 PSU modules do not have user-serviceable fuses.

Figure 19 Vega 30 Router Rear - DC Power Inlets

WARNING:

The DC Power connectors on the rear of the Vega 30 Router are DC power inlets. They are NOT AC mains power inlets.

Rear Marking Description

PSU 1 DC power inlet 1.4-way DIN connector for an external Vega 30 PSU.

PSU 2 DC power inlet 2.4-way DIN connector for an external Vega 30 PSU.

Table 10 Vega 30 Rear - DC Power Inlets

Note: The Vega 30 external power supply unit is SAM Order Code: VG30-PSU

Two are required for redundancy.

PSU 2 Inlet

PSU 1 Inlet

WARNING: PSU 1 and PSU 2 connectors are DC power inlets.They are NOT AC mains inlets.


Vega 30 Router User Manual Environmental Considerations Installation 5.1

5 Installation

5.1 Environmental Considerations

The ambient temperature for all the supplied equipment should not exceed the limits specified in Appendix A “Physical” on page 241.

Installing the equipment in a clean environment with moderate temperature and humidity will promote a long and trouble-free equipment life.

5.2 Chassis Dimensions

The chassis is a shallow 3RU unit. Dimensions are shown in Figure 20:

• Refer to safety information in Section 2 “Safety” on page 8 Section 2 “Safety” on page 8

• The installation and maintenance of the Vega 10 Series router(s) and any associated equipment must be carried out by persons qualified to work with equipment which may be connected to a mains electric supply.

• The mounting and installation of the equipment must be arranged by the user to comply with all safety regulations of the indigenous authority.

Figure 20 Vega 30 Dimensions

Dimensions are in millimeters [inches]


Vega 30 Router User Manual Chassis Ventilation Installation 5.3

5.3 Chassis Ventilation

The Vega 30 Router is a shallow 3RU 19” rack-mount chassis with front-to-back air cooling. A cooling fan is mounted on the chassis rear which pulls air through the front of the unit and exhausts it out of the rear, see Figure 21. Figure 21 shows the external chassis air flow and air intake and exhaust holes.

5.3.1 Location in Rack

The following precautions should be observed:

1. Do not obstruct the front air intake holes nor the rear air exhaust holes. These are to allow the inlet of cooling air and air exhaust at the rear of the unit.

2. Ensure that there is a minimum 50mm (2 inches) clearance at the rear of the unit. This is ESSENTIAL.

Figure 21 Vega 30 Router Chassis Air Flow and Air Intake/Exhaust Holes

Air Flow In

Air Flow Out

Front Air Intake holes

a) Chassis air flow

Rear Cooling Fan

b) Top View

Do not obstruct the front air inlet holes and the rear air exhaust holes.

Ensure a minimum clearance at the rear of the chassis frame of 50mm (2 inches).


Vega 30 Router User Manual Rack Mounting Installation 5.4

5.4 Rack Mounting

5.4.1 Location in Rack

The Vega 30 Router is designed to be installed in a standard 483mm (19 inch) equipment rack for use. The unit requires a “shallow” 3RU high space within a rack. (See Section 5.2 “Chassis Dimensions” on page 41 for the unit’s depth dimensions.)

5.4.2 Mounting the Vega 30 Router into a Rack

Preliminaries:

1. Check that the rack is rigid enough for the Vega 30 Router chassis.

Fitting the unit:

2. Position the Vega 30 Router in the rack.

3. Secure the Vega 30 Router chassis in the rack at each mounting hole using 4-off M6 screws. See Figure 22.

Unit removal is the reverse of fitting.

5.4.3 Cabling Up in a Rack

When connecting cables to the Vega 30 Router, it is recommended that cable supports are used (clamps and bars) to relieve the strain on rear connectors.

Bond the Vega 30 chassis to a house ground at the Chassis Ground Point, see Figure 15 “Vega 30 Router Rear Panel (Annotated)” on page 35 and Section A.4.1 “Vega 30 Unit” on page 241 for details about the Chassis Ground Point.

Note: The chassis rear will become heavier when cables are connected

Figure 22 Rack Mounting Vega 30 Router.

Chassis Rack Mounting Holes

4-off M6 (1/4 inch) Screws


Vega 30 Router User Manual Initial Vega 30 Router Configuration Installation 5.5

5.4.4 Connecting Power to Vega 30

The Vega 30 Router may be powered from one or two Vega 30 PSU module(s).

1. Connect DC power cable(s) from the external Vega 30 PSU module(s) to the Vega 30 Router unit.

2. Connect the external Vega 30 PSU module(s) to an AC mains supply.

3. Turn on mains to Vega 30 PSU modules.No voltage adjustment procedure is required.

Power consumption is listed in Appendix A.4.1 “Vega 30 Unit” on page 241.

5.4.5 Disconnecting Power to Vega 30

To disconnect power from a Vega 30 Router:

1. Disconnect both external Vega 30 PSU’s from AC mains supplies.

2. Disconnect both DC power cables from the rear of the Vega 30 Router.

5.5 Initial Vega 30 Router Configuration

The Vega 30 Router unit requires some network settings to be set up before the unit can be fully configured and other settings can be changed. Network settings may be set up via the following unit interfaces:

• Web Interface - see Section 6 “Vega 30 Web Interface” on page 45.

or

• RollCall Control Panel - see Section 7 “Vega 30 RollCall Templates” on page 100.

In both cases:

1. Connect to the unit via the selected interface. (The unit’s default IP address is 192.168.0.101)

2. Make network settings changes.(In the Configuration Web page or Comms Setup RollCall template screen.)

3. Restart the unit to make the network settings changes take effect.

4. Connect to the unit again using its new IP address.

The unit is ready to be configured.

Refer to safety information in Section 2 “Safety” on page 8.

To reduce the risk of electric shock, plug each external Vega 30 PSU module’s cord into separate branch AC circuits employing separate service grounds.

Note: Output disruption and Vega 30 Router starting:

While the Vega 30 Router unit starts up or restarts, there may be disruption to the video outputs. This is normal: The unit starts by routing ‘1 to 1’ inputs to outputs and only adopts the last know routing settings once the control software has successfully started up.


Vega 30 Router User Manual Vega 30 Web Interface

6 Vega 30 Web Interface

This section describes the Vega 30 Router Web pages:

The Vega 30 Router has a web browser interface for configuration, status monitoring and unit operation. To access the web page, enter the unit’s IP address into a web browser. Supported web browsers include:

• Windows® Internet Explorer®, Edge®.

• ChromeTM.

• Safari®.

• FirefoxTM.

• OperaTM.

6.1 Vega 30 Web Pages page 46

6.2 Home Page page 49

6.3 Source Names Page page 51

6.3.1 Source Names Web Page - Apply Button page 52

6.3.2 Source Names Web Page - Input Ports Table page 53

6.3.3 Source Names Web Page - Source Names Table page 57

6.4 Renaming Pre-defined Sources page 63

6.5 Defining User-defined Sources page 64

6.5.1 User-defined Source - Defining a Source Name page 64

6.5.2 User-defined Source - Defining an Associated Video Source page 65

6.5.3 User-defined Source - Entering Audio Channel Source Names page 68

6.5.4 Importing and Exporting Source and Destination Names page 74

6.6 Destination Names page 76

6.7 Set Routes page 80

6.8 Processing Control page 91

6.9 Configuration page 95

Note: The Web interface’s appearance, including pop-up message windows and dialogs, may vary from web browser to web browser. Screenshots in this user manual section were captured from a FireFoxM web browser.


Vega 30 Router User Manual Vega 30 Web Pages Vega 30 Web Interface 6.1

6.1 Vega 30 Web Pages

When a connection to the unit is made, the Vega 30 Home Page is shown, see Figure 23.

Other Vega 30 web pages may be navigated to using the navigation side bar, in Figure 23. Click on a web page name in the side bar to navigate to that page.The available web pages are shown in Figure 24 and are listed in Table 11.

Figure 23 Vega 30 Home Page and Navigation Side Bar



Figure 24 Vega 30 Web Pages

Destination Names, see page 76

Set Routes, see page 80

Processing Control, see page 91

Source Names, see page 51

Configuration, see page 95

Home Page, see page 49

Web Page Description

Home Page Home page, showing system status. See page 49

Source Names Define the router’s sources. See page 51

Destination Names Define the router’s destinations. See page 76

Set Routes Control the routing. See page 80

Processing Control Control the processing functions. See page 91

Configuration Configure the unit. See page 95Table 11 Vega 30 Web Pages



Table 12 cross-references Vega 30 Web pages and Vega 30 RollCall templates.

Function Vega 30 Web Page Vega 30 RollCall Template

Status:

Section 6.2 “Home Page” on page 49

Section 7.2 “Unit Information Template” on page 107

Section 7.3 “System Information Template” on page 111

Input Ports:Section 6.3.1 “Source Names Web Page - Apply Button” on page 52

Section 7.5.2 “Port Configuration - Input Ports” on page 122

Source Names:Section 6.3.3 “Source Names Web Page - Source Names Table” on page 57

Section 7.4 “Source Configuration Template” on page 113

Destination Names:

Section 6.6 “Destination Names” on page 76Section 7.5.2 “Port Configuration - Input Ports” on page 122

Set Routes:

Section 6.7 “Set Routes” on page 80

Section 7.8 “Assoc Routing - XY Panel Control Template” on page 135

Section 7.10 “Direct Video - XY Panel Control Template” on page 150,

Section 7.12 “Direct Audio - XY Panel Control Template” on page 152

Processing Control:

Section 6.8 “Processing Control” on page 91Section 7.5.3 “Port Configuration - Output Ports” on page 124

Configuration:

Section 6.9 “Configuration” on page 95

Section 7.6 “Comms Setup Template” on page 127

Section 7.7 “Log Fields Template” on page 134

Table 12 Comparing Vega 30 Web Interface Pages and Vega 30 RollCall Templates


Vega 30 Router User Manual Home Page Vega 30 Web Interface 6.2

6.2 Home Page

The Vega 30 Web Home Page is shown in Figure 25; information presented is read-only.

The information on the web page is described in Table 13.

Figure 25 Vega 30 Home Page

Item Description

License Status:

VG10_CSA Yes/No: Licensed for video inputs/outputs 1 to 12.

VG10_CSB Yes/No: Licensed for video inputs/outputs 13 to 24.

VG10_CSC Yes/No: Licensed for video inputs/outputs 25 to 34.

VG10_AR Yes/No: Licensed for discrete audio routing.

System Information:

Local IP Address IP address of the Vega 30 unit.

MAC Address MAC address of the Vega 30 unit.

Serial Number Factory serial number of the Vega 30 unit.

Controller Name Name of the Vega 30 unit in a RollCall system.

Table 13 Vega 30 Home Web Page Items


Vega 30 Router User Manual Home Page Vega 30 Web Interface 6.2

System Contact Shows the system contact details. For example, “A.N.Other”

Location Shows the location of the Vega 30 unit. For example, “MCR 1”

System Status:

PSU 1 Status Status of the external PSU connected to DC power inlet PSU 1.

PSU 2 Status Status of the external PSU connected to DC power inlet PSU 2.

Fan Speed Speed of the internal cooling fan.

Fan Status Status of internal cooling fan.

Temperature (oC) Internal temperature of the Vega 30 unit

Reference Standard Video standard of the video reference signal connected to the Vega 30 unit ‘REF’ input. For example, “SD525”

(Vega 30 IC device firmware versions:)

FPGA A for video outputs 1 to 12 and MADI outputs 1 to 2, FPGA B for video outputs 13 to 24 and MADI outputs 3 to 4, and FPGA C for video outputs 25 to 34 and MADI outputs 5 to 6.

FPGA A Firmware Version

Version of the firmware running in FPGA IC device A, which handles video inputs and outputs 1 to 12 and MADI out 1 to 2.

FPGA A PA Number Identifier of firmware running in FPGA IC device A.

FPGA B Firmware Version

Version of the firmware running in FPGA IC device B, which handles video inputs and outputs 13 to 24 and MADI out 3 to 4.

FPGA B PA Number Identifier of firmware running in FPGA IC device B.

FPGA C Firmware Version

Version of the firmware running in FPGA IC device C, which handles video inputs and outputs 25 to 34 and MADI out 5 to 6.

FPGA C PA Number Identifier of firmware running in FPGA IC device C.

(Vega 30 controller firmware/software versions:)

Controller FPGA Firmware Version

Firmware version running in the Vega 30 unit’s controller FPGA IC device. This device handles part of the router controller function.

Controller FPGA PA Number

Identifier of firmware running in the controller FPGA IC device.

Controller Software Version

Software version running on the Vega 30 unit’s controller CPU device. This CPU device handles the main router controller function.

Item Description

Table 13 Vega 30 Home Web Page Items (Continued)


Vega 30 Router User Manual Source Names Page Vega 30 Web Interface 6.3

6.3 Source Names Page

The Source Names web page lists video/audio input ports and all of the source names. The web page contains two tables: Input Ports and Source Names tables. These are shown in the zoomed-out screen-shot of Figure 26.

• Input Ports table is described in:Section 6.3.2 “Source Names Web Page - Input Ports Table” on page 53.

• Source Names table is described in: Section 6.3.3 “Source Names Web Page - Source Names Table” on page 57.

Remember to click Apply at the top of the Source Names web page to apply any changes made in these tables.

Figure 26 Source Names Web Page (Zoomed Out)

Input Ports table (See Figure 27)Section 6.3.2 “Source Names Web Page - Input Ports Table” on page 53.

Source Names table, (See Figure 30)See Section 6.3.3 “Source Names Web Page - Source Names Table” on page 57.

Note: User-defined sources are specified in this Source Names table.See Section 6.5 “Defining User-defined Sources” on page 64.

Apply button: Click Apply to save any changes made in either table on this web page.See Section 6.3.1 “Source Names Web Page - Apply Button” on page 52.



6.3.1 Source Names Web Page - Apply Button

Click Apply at the top of the Source Names web page to apply any changes made in this table.

Item Description

Apply Button. (At the top of the Source Names Web page.)

Click to apply settings changes made on the Source Names page. (Changes may be in either the Input Ports table or in the extensive Source Names table.)

• After changed settings have been applied, a message is briefly displayed on the web page adjacent to the Apply button. See below:

• If another web page is selected before any settings changes are applied, a browser-dependent dialog message is displayed. An example is shown below:

The user may leave the current page, but any changes will not be applied (and will be lost.)

Table 14 Source Names Web Page ‘Apply’ Button



6.3.2 Source Names Web Page - Input Ports Table

The Input Ports table (see Figure 27) comprises a list of 34 input video port configuration settings. There is one row per router video input. Up to 34 video input ports can be configured. Configuration items for each input port include:

• Video standard to use for switching to the input port.

• 4K source quad-link source groups.

Each configuration item has a column and is described in Table 15.

Figure 27 Vega 30 - Input Ports Table



Item Description

Port Number: (Rows of the table:)

All Settings in this row apply to all video inputs.

Input 1...Input 34

One row per video input port.

Standard Drop-down box.Select the video standard to use for switching to the corresponding video input. The SMPTE RP-168 -2009 switching standard is used.

Note: If the applied input signal is of a different standard, then any routing of that input will effectively ‘crash-switch’.

4K Source Check box.Click to toggle on/off selecting the first input of a sequence of four consecutive inputs to be grouped and associated with a 4K input source. See Figure 28 screen-shot.

“All” row: Clicking the check box in the “All” row will group the first 32 video inputs into groups of four. See Figure 29.

Table 15 Input Port Configuration Items



Figure 28 Four Input Ports Grouped for a 4K Quad-link Input

Clicked 4K Source check box

Four Input Ports grouped



Remember to click Apply at the top of the web page to apply any changes made on this page.

Figure 29 “All” 4K Quad-Link Source Groups:a) Ports 1 to 32 Grouped to be 4K Source-Groups. (Ungrouped: 33 and 34.)And different end-groupings can be selected:b) Ports 1 to 28, 30 to 33 grouped. (Ungrouped: 29 and 34.) c) Ports 1 to 28, 31 to 34 grouped. (Ungrouped: 29 and 30.)

b) 4K Grouped Ports 1 to 28 and 30 to 33.

c) 4K Grouped Ports 1 to 28 and 31 to 34.

a) “All” 4K Source check box ticked.

• Ports 1 to 32 grouped together to be 4K Quad-link Source-Groups.

• Ports 33 and 34 are ungrouped.

Clicked 4K Source check box in “All” row

Inputs 1 to 32 used for quad-link 4K sources.



6.3.3 Source Names Web Page - Source Names Table

The Source Names table is a large table with 500 rows; only 50 rows are shown at any one time, as shown in overview in Figure 30. Once a source is defined, it can be routed by the router.

Up to 500 sources for the router can be defined. The first 50 rows of the table are initially shown, as shown in Figure 30. Other rows are accessed via navigation tabs.

The listed sources in this table include:

• Pre-defined sources that use router video inputs.

• Pre-defined sources that use router MADI inputs.

• User-defined sources that use any combination of router inputs. (Source associations.)

The Source Names table is described in detail in the following sub-sections.

Note: Associated Sources:

Sources defined in the Source Names table are formed by associating up to one video source and up to 16 audio channel sources. These user-defined sources are called ‘Associated Sources’ or ‘Source Associations’.

Figure 30 (Wide) Source Names Table (Overview)

Navigation tabs: Click on tabs to select Sources 1-50, 51-100, 101-150, ... , and 451-500. See Figure 31

Sources Import and Export controls

Source Names

(8- and 32-character)

Source Number

Audio channel sources (Number or Names):

Rows 1 to 34: Embedded audio channels.

Rows 35 to 46: MADI audio channels.

Rows 47 onwards: Any audio channel source numbers.

Video Input source or

MADI Input (32- and 8- character

name)



6.3.3.1 Navigating Pages of the Source Names Table

Click the tabs along the top of the table to navigate to other pages of sources. See Figure 31.

6.3.3.2 Columns of the Source Names Table

The table’s column headings are shown in Figure 32 and are described in Table 16.

Remember to click Apply at the top of the Source Names web page to apply any changes made in this table.

Figure 31 Source Names Table - Navigation Tabs

Click tabs to display Source rows1-50, 51-100, 101-150, ... and 451-500.

Tabs

Figure 32 Source Names Table - Column Headings



Item Description

Logical NumberSource Number, identifies the Source and the table row. This is not editable.

32 Character Name

Enter a 32-character name for the pre-defined or for the user-defined source.

Note: Source names can also be imported, see Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.

8 Character Name

Enter an 8-character name for the pre-defined or for the user-defined source.

Source names on a new or factory-reset Vega 30 unit are set up to default source names, refer to Table 63 in Appendix C “Audio Channel Source and Destination Names and Numbers” on page 248.

Note: Source names can also be imported, see Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.

Input Source This column contains text or a button:

Physical Input text. This is not editable.

The row is for a pre-defined source which is tied to a physical router video input.

Physical Input text. This is not editable.

The row is for a pre-defined source which is tied to a physical router MADI input.

Button.

The button occurs in user-defined source rows.

Click Apply in this row to select the associated source video for the user-defined source.See Section 6.5 “Defining User-defined Sources” on page 64.

Associated Source 32 Character Name

Name of the video source associated with this source definition, 32-character name.

Table rows 1 to 46: Not editable. (The text background color is grey.)

Table rows 47 to 500: Not editable directly. Use Input Source column Apply button,see Section 6.5 “Defining User-defined Sources” on page 64.

Associated Source 8 Character Name

Name of the video source associated with this source definition, 8-character name

Table rows 1 to 46: Not editable. (The text background color is grey.)

Table rows 47 to 500: Not editable directly.Use Input Source column Apply button, see Section 6.5 “Defining User-defined Sources” on page 64.

Table 16 Sources Names Table - Column Headings



Remember to click Apply at the top of the Source Names web page to apply any changes made in this table.

Audio 1, Audio 2, ... Audio 16

A column for each of the 16 audio channel sources associated with the defined source:

Table rows 1 to 46:

This is not editable. (The text background color is grey.)

Table rows 47 to 500:

Enter the audio channel source name. Then press enter to finish entering characters.

As you begin to type, an auto-complete list appears. This lists 10 possible names, based on the characters entered so far.

To enter a ‘null source’, just press enter. (I.e. a blank entry in table)

See Section 6.5 “Defining User-defined Sources” on page 64.

Item Description

Table 16 Sources Names Table - Column Headings (Continued)



6.3.3.3 Rows of the Source Names Table

The rows of the Source Names screen show some pre-defined sources and enable user-defined sources to be entered. The appearance of rows depends on the type of source being shown:

• Pre-defined Video sources. (Rows 1 to 34)

• Pre-defined MADI audio sources. (Rows 35 to 46)

• User-defined video or audio sources. (Rows 47 to 500)

Table rows are shown respectively in Figure 33a, b and c.

The various source types are described in Table 17.

Figure 33 Source Names Table Rows:a) Example rows for Sources 1 to 34 (Pre-defined video sources).b) Example rows for Sources 35 to 46 (Pre-defined audio sources).c) Example rows for Sources 47 to 500 (User-defined sources).

a) Example rows for Sources 1 to 34: Pre-defined video sources.

b) Example rows for Sources 35 to 46: Pre-defined MADI audio sources.

c) Example rows for Sources 47 to 500: User-defined sources (Source associations)

Pre-defined video sources

Pre-defined MADI audio sources

User-defined sources



Table rows

Source Numbers

Source Type and Description

1 to 34 1 to 34 Pre-defined video sources:

The first 34 table rows contain pre-defined video sources which correspond to the physical video inputs of the router. (I.e. a video with 16-off embedded audio channels.)

Routing these sources routes video and its embedded audio to the router destination and to the router output.

The 32- and 8-character Source Names columns are editable on these rows. Remaining columns in the rows are not editable.

See Note 1.

35 to 46 35 to 46 MADI audio sources:

The table rows contain pre-defined sources which correspond to each of the three physical MADI inputs to the router.

Each MADI 64-channel input is divided into four groups of 16 channels:Each table row is predefined for 16 audio channels. One row represents one quarter of a MADI port. Four rows represent one physical MADI port of the router.

A row may correspond to MADI channels:

• A) MADI audio channels 1 to 16.

• B) MADI audio channels 17 to 32.

• C) MADI audio channels 33 to 48.

• D) MADI audio channels 49 to 64.

(Labelled MADI 1A-x, MADI 1B-x, MADI 1C-x, MADI 1D-x respectively).

The 32- and 8-character source names are editable on rows 35, 39 and 43. Remaining rows are not editable.

See Note 1.

47 to 500 47 to 500 User-defined Sources:

The remaining table rows permit the user to define further sources, which can be combinations of physical router inputs and internal audio silence and test tone signals.

User-defined Sources may be fully-defined (i.e. all columns of the row filled out) or partially defined (i.e. not all columns of the row filled out).

The 32- and 8-character source names and the audio channel source names are editable on these rows. Remaining columns are not editable.

See Section 6.5 “Defining User-defined Sources” on page 64.

See Note 1.

Note 1: Source names can also be imported, along with destination names, see Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.

Table 17 Source Names - Table Rows, Source Types


Vega 30 Router User Manual Renaming Pre-defined Sources Vega 30 Web Interface 6.4

6.4 Renaming Pre-defined Sources

Pre-defined sources are defined in the Source Names table of the Source Names web page.

Sources 1 to 46: (Table rows 1 to 46, pre-defined sources.)

These are pre-defined sources. Routing these sources means that the entire router input source (video or 16 channels of a MADI input) is routed to a destination. These sources are pre-defined for this purpose.

To define a user name for a pre-defined source:

1. Enter a 32-character name and an 8 character name in the respective columns for the source row.

2. Click Apply at the top of the Source Names Web page to apply changes.

This simply renames the pre-defined source with a user-defined name. Any video and audio channels associated with this source are unaffected and cannot be modified.

Note: Editing Source Names:

Source names can be edited either:

• in the Vega 30 Web page,

• or in the RollCall template screen,

• or in the RollCall XY Panel.

• or the entire set of source and destination names can be imported. (See Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.)


Vega 30 Router User Manual Defining User-defined Sources Vega 30 Web Interface 6.5

6.5 Defining User-defined Sources

User-defined sources are defined in the Source Names table of the Source Names web page.

Sources 47 to 500: (Table rows 47 to 500, user-defined sources.)

These are user-defined sources. The user can determine which video and audio input channels are used together as a source and can be routed together to a destination.

A user-defined source is defined in a row of the table. Names of each video and audio channel of the user-defined source are entered.

6.5.1 User-defined Source - Defining a Source Name

User-defined sources are in rows 47 to 500.

To define a user name for a user-defined source:

1. Enter a 32-character name and an 8 character name in the respective columns for the source row.

2. Click Apply at the top of the Source Names Web page to apply changes.

This simply renames the user-defined source with a user-defined name.

Alternatively, source names can be imported via a spreadsheet. See Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.

Note: The video and audio channels associated with this source also require defining. (See “User-defined Source - Defining an Associated Video Source” on page 65 and “User-defined Source - Entering Audio Channel Source Names” on page 68.)


Source names can be edited either:


• or in the RollCall template screen,

• or in the RollCall XY Panel.

• or the entire set of source and destination names can be imported. (See Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.)



6.5.2 User-defined Source - Defining an Associated Video Source

When specifying a user-defined source in the Source Names table, the aim is to fill out:

• Columns ‘Associated Source 32 character name’ and ‘8 character name’: This is described in this sub-section.

• Columns ‘Audio 1’, ‘Audio 2’, .. ‘Audio 16’: Enter audio channel sources, see Section 6.5.3 “User-defined Source - Entering Audio Channel Source Names” on page 68.

User-defined sources are in rows 47 onwards.

The example below is for user-defined Source 51 (i.e. table row 51).

To enter Video input 13 as the video source for Source 51:

1. Click Apply in source row 51 of the Source Names table. See Figure 34.

A ‘Choose the video’ dialog is shown. See Figure 35.

Figure 34 Click Apply in Source Row 51



2. Click Apply at Source 13 in the dialog to choose video source 13. The chosen video source is shown at the top of the dialog. See Figure 36.

3. Click Apply at the bottom of the dialog. See Figure 37.

Figure 35 ‘Choose the video’ Dialog

Figure 36 Click the Apply Button for a Video Source

Click Apply for Source 13. Then Source 13 appears at top of dialog.



This accepts the chosen video source. It is now filled out in Source 51 row of the Source Names table. See Figure 37.

This has filled out the “Associated Source” (video source) columns for user-defined Source 51.

6.5.2.1 Null Video Source

If a ‘null source’ is required for the specified video source, then:

1. Click the Apply button in Source 51 row of the Source Names table.

2. Click Reset at the bottom of the ‘Choose the video’ dialog.

3. Click Apply at the bottom of the ‘Choose the video’ dialog.

The video source for Source 51 is now blank, indicating ‘null source’. See Figure 39.

Figure 37 Click the Apply Button at Bottom of Dialog

Figure 38 Video Source 13 Specified for Source 51

Figure 39 Video Source is ‘Null Source’ for Source 51



6.5.3 User-defined Source - Entering Audio Channel Source Names

When specifying a user-defined source in the Source Names table, the aim is to fill out:

• Columns ‘Associated Source 32 character name’ and ‘8 character name’: Enter video sources, see Section 6.5.2 “User-defined Source - Defining an Associated Video Source” on page 65.

• Columns ‘Audio 1’, ‘Audio 2’, .. ‘Audio 16’: This is described in this sub-section.

There are up to 16 Audio columns to be filled out for the associated audio channels of a user-defined source. The Source Names table columns are labelled “Audio 1”, “Audio 2”, .. “Audio 16”.

Audio channel source names must be entered into each column of a row for a source. Blank entries indicate a ‘null source’ for an audio channel.

After making changes, remember to click Apply at the top of the Source Names web page to apply any changes made in this table.

The example in the sub-sections below is for user-defined Source 51 and shows how to enter audio channel sources for Source 51 in the Source Names table row 51.

6.5.3.1 Enter MADI Audio Channel Sources

1. Click in the “Audio 1” column table cell and enter ‘A’. A sort of drop-down list appears to show some entry possibilities and assist name entry. See Figure 40.

Note: Source names in this example:

The factory names are used for video and audio channel sources in this example. (For example, “V.In 2-12”, “A.In 2D-14”.) These names would be seen on a new or on a factory-reset Vega 30 unit.

If user source names have been defined on a unit, then some or all of the factory source names will have been over-written.



2. Click on an item in the drop-down list to select it, or continue typing in the table cell.

The “Audio 1” table cell entry is complete. See Figure 41.

Continue to add a further MADI input audio channel source:

3. Click in the “Audio 2” column and enter ‘A.In 3D’. A drop-down list appears to assist entry. See Figure 42.

4. Continue to type the name, enter ‘-1’ and the drop-down list modifies. See Figure 43.

Figure 40 Drop-down ‘Auto-complete’ List

Some ‘auto-complete’ entry possibilities

Internal Test Tones and Silence audio sources

Figure 41 Audio Channel Source Entered

Figure 42 Drop-Down ‘Auto-complete’ List

Some possibilities




5. Continue to type, enter ‘6’ and the drop-down list modifies again. Select the ‘A.In 3D-16’ drop-down list entry. See Figure 44.

The “Audio 2” column entry is complete. See Figure 45

6. (Click Apply at the top of the Source Names Web page to apply settings changes when all settings changes are done.)

6.5.3.2 To enter a ‘Follow Video’ for an Audio Channel Source

7. Click in the “Audio 3” column and enter ‘De’. A drop-down list appears to assist entry. See Figure 46.

Figure 43 Modified Drop-Down ‘Auto-complete’ List

Figure 44 Modified Drop-Down ‘Auto-complete’ List

Figure 45 Audio 2 Column Entry Complete


Some ‘Auto-complete’ possibilities




8. Select ‘DestThru-3’ in the drop-down list.

This selects embedded audio channel 3 of the video input source specified for this user-defined source.

The ‘Audio 3’ column entry is done. See Figure 47.


6.5.3.3 To enter a De-embedded Audio Channel Source

To enter a de-embedded audio channel source, for example, from video crosspoint output 23:

10. Click in the “Audio 4” column and enter ‘V.In 23’. A drop-down list appears to assist entry. See Figure 48.

11. Select ‘V.In 23-4’ in the drop-down list. The ‘Audio 4’ column entry is done. See Figure 49.

The user-defined source’s audio channel 4 (i.e. the ‘Audio 4’ column) is now defined to be audio channel 4 from video output 23 of the video crosspoint.



Note: DestThru-N

‘DestThru-N’ specifies an embedded audio channel from the user-defined source’s associated video source.

In this example, “DestThru-3” means that embedded audio channel 3 of whichever video source is used



Some ‘Auto-complete’ possibilities




6.5.3.4 To enter Silence for an Audio Channel Source

13. Click in the “Audio 5” column and enter ‘S’. A drop-down list appears to assist entry. See Figure 50.

14. Select ‘Silence’ in the drop-down list.



6.5.3.5 To enter a Test Tone for an Audio Channel Source

16. Click in the “Audio 6” column and enter ‘T’. A drop-down list appears to assist entry. See Figure 50.

17. Select ‘979.6Hz’ in the drop-down list.



6.5.3.6 To Apply All Changes

19. Click Apply at the top of the Source Names Web page.

The changes are applied and a brief message appears on the web page, see Figure 53.




Figure 53 Changes Applied



If no message appears, then check the spellings of channel source names.

6.5.3.7 Defining ‘Null Source’ for a Channel Source

For each user-defined source, video and audio channels may be defined for a source. A blank entry in the Source Names web page means ‘null source’ for that channel source.

For ‘null source’, no routing is done on that channel, so there will be no change on that corresponding channel at the routed destination.

If no video or audio source is required in a source’s video or audio channel, then:

• Enter a blank in the Source Names table.

Remember to click Apply at the top of the Source Names Web page to apply changes made.

Figure 54 ‘Null Source’ Entries

Note: Partial Sources:

Sources with ‘null sources’ in them are called partial sources. When routing a partial source to a destination, the end result depends on what was routed there previously. Tallies will indicate the last source routed to the destination, whether it was partial or not.



6.5.4 Importing and Exporting Source and Destination Names

A whole set of source names and destination 8- and 32-character names can be exported or imported from the Source Names web page or from the Destinations web page. The Import and Export controls on these web pages are shown in Figure 55 and Figure 56.

Both source names and destination 8- and 32-character names are contained in one file and these names are imported or exported together. An exported file may be opened in a spreadsheet editor or viewed in a text editor.

The file contents of an exported names spreadsheet file are shown in Appendix G “Source and Destination Names File (Import and Export)” on page 276.

6.5.4.1 Recommended Procedure for Import/Export

• Always export a names spreadsheet before importing another. In this way, a record of all the earlier names may be kept.

• When setting source names via a spreadsheet, use a “read-modify-write” approach:

1. Export a names spreadsheet file.

2. Modify it.

3. Import the modified spreadsheet.

• In this way, any existing source names will be unchanged.

6.5.4.2 To Export

1. Click Export to export a list of source and destination names to a spreadsheet file.

2. At the ‘Opening Vega30names.csv’ dialog, select to either:

• Open the file to view the file and then save the file, under a new name if required.

• or Save the file.

Note: Import and Export do not work from the Vega 30 Web page in Internet Explorer®.

Figure 55 Source Names Web Page - Import and Export Controls

Figure 56 Destinations Web Page - Import and Export Controls

Note: All names are over-written when importing:

The entire set of source and destination 8- and 32-character names is over-written when importing a names spreadsheet file. Thus, every name must be uniquely defined in a names spreadsheet file before importing.

Import

Export

Browse control

Import Export

Browse control



6.5.4.3 To Import

1. Click Browse and browse to the required source and destination names file.Click Open to select the file.

2. Click Import to import the file.

A message appears at the top of the page when names have been imported. See Figure 57.

3. Click Apply to save the newly-imported settings.

Figure 57 Imported Successfully Messages

a) Destinations Web page “Imported Successfully” message

b) Source Names Web page “Imported Successfully” message


Vega 30 Router User Manual Destination Names Vega 30 Web Interface 6.6

6.6 Destination Names

The Destination web page is shown in Figure 58. The page comprises a table of configuration settings, with one row per video output. Up to 34 video outputs can be configured. Configuration items for each video output include:

• 4K source quad-link destination-groups.

• Output names, 32-character and 8-character names.

Each configuration item has a column and is described in Table 18. Table rows are described in Table 19.



Figure 58 Vega 30 - Destinations Web Page

Import and Export Controls



Remember to click Apply to apply any changes made on this web page.

Item Description

Apply Button.Click to apply settings changes made on the page.

(See Table 14 for more details about the Apply button operation.) The user may leave the current page, but any changes will not be applied (and will be lost.)

Logical Number: Destination number.

All Settings carried out in this row apply to all destinations.

1..34

One row per video destination. Total of 34 video outputs.

35..58

Four rows per MADI output. Total of 6 MADI outputs.

4K Dest Check box. (Rows 1 to 34 only)Click to select the first output of a sequence of four consecutive outputs to be associated with a 4K destination.

Clicking the check box in the “All” row will group the first 32 video outputs into groups of four, Destination-Groups.

Grouping operation is similar to Source-Groups, see Figure 29 on page 56.

32 Character Name

Enter a 32-character name for the destination.

8 Character Name

Enter an 8-character name for the destination.

Table 18 Vega 30 Destination Names Web Page Items



6.6.1 Import and Export Destination Names

A set of source and destination 8- and 32-character names can be exported from the Destination Names web page or from the Source Names web page. See Section 6.5.4 “Importing and Exporting Source and Destination Names” on page 74.

Table rows

Destination Numbers

Description

1 to 34 1 to 34 Pre-defined video destinations:

The first 34 table rows correspond to the physical video outputs from the router. (I.e. video with 16 channels of embedded audio.)

The 32- and 8-character source names are editable on these rows.

35 to 58 35 to 58 MADI audio destinations:

The next 24 table rows correspond to each of the six physical MADI outputs from the router.

Each row is predefined for 16 audio channels. Four rows represent one physical MADI output from the router, carrying MADI audio channels 1 to 16, 17 to 32, 33 to 48 and 49 to 64 respectively.

The 32- and 8-character destination names are editable on rows 35, 39, 43, 51, and 55. The suffices ‘A’, ‘B’, ‘C’ and ‘D’ are appended to the entered name for the three subsequent rows. See Figure 59.Remaining rows are not editable.

Table 19 Destination Names - Table Rows

Figure 59 MADI Destination Names

32-character and 8-character names auto-complete with A, B, C and D suffices for the four grouped audio destinations.


Vega 30 Router User Manual Set Routes Vega 30 Web Interface 6.7

6.7 Set Routes

The Set Routes web page is shown in Figure 60. The page houses push buttons and information about:

• Source selection.

• Destination selection.

• Take.

• Destination protect.

The page allows a user to make routes in the Vega 30 Router. The general operation sequence is:

1. Select a Destination.

2. Select a Source.

3. Press Take.

Figure 60 Vega 30 Set Routes Web Page

Take / Protect section

Destination Selection section

Source Selection section

Scroll Barsto access other selection buttons

Selection buttons



Figure 61 shows an annotated view of the page.

The page contains a:

• Sources Selection section: An array of source-selection push buttons. Button colors are described in Table 20.

• Destination Selection section: An array of destination-selection push buttons. Button colors are described in Table 21.

• Take push button with route information. See Table 22.

• Protect control push button with protect information. See Table 23.

When operating the Set Routes page, the cursor shape can change or pop-up information is displayed. See Section 6.7.1 “Cursors on the Set Routes Web Page” on page 84.

Figure 61 Vega 30 Set Routes Web Page - Sources, Destinations, Take and Protect Controls

Source Selection push button. See Table 20 for details.

Source Name

Destination Selection push button.See Table 21 for details.

Destination Name

Take push button.See Table 22 for details about the button and see Section 6.7.2 “Simple Routing Example” on page 85

Current Routed Source

Protect control. See Table 23 for details about the button and see Section 6.7.4 “Destination Protect” on page 89.



A simple operating example is given in Section 6.7.2 “Simple Routing Example” on page 85 and in Section 6.7.3 “4K Routing Example” on page 87.

Source Selection Item Description

Source selection button. Click to pre-select a source

Button showing Currently Selected Source.

Button showing Pre-Selected Source.

Button showing Source is part of a 4K source group.

Table 20 Source Selection - Button Colors

Dest Selection Item Description

Destination selection button.Click to select a destination.

Button showing Selected Destination.

Button showing Destination is the first of a 4K group.

Button showing Destination is part of a 4K group.

Button shows that a destination is protected.

Table 21 Destination Selection - Button Colors



Item Description

Destination: Shows selected Destination Name.

Current Source: Shows current Source Name routed to the selected Destination.

Preselected Source: Shows the Source Name of the new (pre-)selected Source.

Take push button.Click Take to make a new route in the Vega 30 Router.The Pre-selected Source is routed to the selected Destination.

Table 22 Take Section



6.7.1 Cursors on the Set Routes Web Page

The normal cursor shape is an arrow, see Figure 62a.

When the cursor is over a button, the cursor changes to be hand-shaped, See Figure 62b.

Hover the cursor over a Source selection or Destination selection button to see the 32 character long name of the Source or Destination. See Figure 62c.

If a button may not be clicked, for example it is one of a 4K group, then the cursor changes shape to reflect this, see See Figure 62d.

Figure 62 Cursors on Set Routes Web Page

c) Revealing 32 character long name

d) Cursor shape when button may not be clicked.

a) Normal “arrow” cursor.

b) Push button cursor.



6.7.2 Simple Routing Example

Figure 63 shows making a simple route:

1. Click a destination selection button to select a Destination.

2. The Selected Destination is highlighted in the Destinations section and is shown in the Take section.

3. The Currently-routed Source is highlighted in the Sources section and shown in the Take section.

4. Click a source selection button to pre-select a Source. This is the source to be switched to.

5. The Pre-Selected Source is highlighted in the Sources section and shown in the Take section.

6. Click Take to make the new route.

The new route is now made.

Figure 63 Making a Simple Route

1.

2.

3.

5.

4.

3.

6.

2.

5.



Once the new route is made:

7. The new route is highlighted in the Sources and Destinations section and shown in the Take section, see Figure 64.

Figure 64 Result of Making a Simple Route.

7. 7.

7.

7.



6.7.3 4K Routing Example

To make a 4K route:

Preliminaries:

• On the Video Input Names and Video Outputs Names pages, make 4K groups.

• Go to the Set Video Routes page.The page reflects the 4K grouping made. See Figure 65.

Now make the route:

1. Click a destination selection button to select a 4K Destination.

2. The Selected 4K Destination is highlighted in the Destinations section and is shown in the Take section.

3. The Currently-routed 4K Source is highlighted in the Sources section and shown in the Take section.

4. Click a source selection button to pre-select a 4K Source. This is the new source to switch to.

5. The Pre-Selected 4K Source is highlighted in the Sources section and shown in the Take section.

6. Click Take to make the new route.

The new 4K route is now made.

Figure 65 Making a 4K Route

1.

2.

3.

5.

4.

3.

6.

2.

5.



Once the new 4K route is made:

7. The new 4K route is highlighted in the Sources and Destinations section and shown in the Take section, see Figure 66.

Figure 66 Result of Making a 4K Route.

7.

7.

7.

7.

7.7.7.



6.7.4 Destination Protect

A destination may be protected, to prevent other routes being made to it. Protecting a destination is an operational control and is carried out by a user from a panel, from the Vega 30 Web interface, or from a RollCall routing template screen.

For example, to perform a 3 hour long recording, a destination can be protected to prevent anyone else from accidentally disturbing the recording.

In the Vega 30 Web interface, Destination Protect is carried out in the Set Routes page.

The various Protect button appearances, see Table 23, may be seen when destinations are selected; the Protect push button will show:

• “Protect” - if the destination can be protected.

• “Unprotect” - if the destination is protected by this local web interface.

• “Protected by others” - if the destination is protected by another panel and user.

To protect a destination:

1. Select an unprotected destination. The Protect button should show “Protect”.

2. Click the Protect button.

A small padlock icon appears on the destination button.

The selected destination is now protected.

To remove protection from this (now protected) destination:

3. Temporarily select any other destination, then select the protected destination again. The Protect button should show “Unprotect”.

4. Click the Protect button. The selected destination is now protected.

Item Description

Protect toggle push button.Click button to protect/unprotect the selected destination.

With a destination selected, the Protect button may show the following:

• Protect - Click to protect the selected destination.:

• Unprotect - Click to remove protection.

• Protected by others - The selected destination has been protected from some other control panel, by another user. Only the “protecting” panel can remove this protection.

Table 23 Destination Protect Control

Note: Destination protection can only be removed by the panel/screen that set the Protect or by a master panel.



If a route is attempted to a protected destination, then a warning message is shown on the web interface Set Routes screen after the route is attempted. See Figure 67.

Figure 67 Warning message when attempting to route to a protected destination.


Vega 30 Router User Manual Processing Control Vega 30 Web Interface 6.8

6.8 Processing Control

The Vega 30 Router contains some processing functionality, see the functional block diagram in Figure 3 on page 18. Processing functions include:

• Quiet Switching.

• Line Synchronizer and Delay.

Figure 68 shows the Processing Control screen. Table 25 and Table 25 list the screen’s controls and indicators.

Figure 68 Vega 30 Processing Control Web Page

‘Top’ section of screen, see Table 24 ‘Table’ section of screen,see Table 25.



Item Description

Apply Button.Click to apply settings changes made on the page. (See Table 14 for more details about the Apply button operation.)


VFade Outputs 1-12 Drop-down box.Select V-fade rate on outputs 1 to 12. Select the V-fade rate to reduce any audible disturbance during switching.

The setting is subjective and dependent on the audio media being switched.

• Fast. (Default)

• Medium.

• Slow.

For V-fade durations, see A.9 “Audio V-Fade Rates” on page 244.

See Note 1.

VFade Outputs 13-24 Drop-down box.Select V-fade rate on outputs 13 to 24.

See Note 1.

VFade Outputs 25-34 Drop-down box.Select V-fade rate on outputs 25 to 34.

See Note 1.

Note 1: The V-Fade function is enabled on an output-by-output basis. Use the:

• ‘Quiet Switch V-Fade enable’ controls in the Web interface ‘Processing Control’ page.

• ‘V-Fade enable’ in the RollCall interface ‘Port Configuration’ template.

Table 24 Processing Control Web Page - Items on top section of screen



Item Description

Destinations: Columns show destination names only and are not editable.

Destination Number

Destination’s physical router output number.

• Rows 1 to 34: One row per video output.

• Rows 35 to 58: Four rows per MADI output.

Video 8 Character Name

The assigned 8 character destination name:

• Rows 1 to 34: Video output name.

• Rows 35 to 58: Name for 16-channels of each MADI output.

Lock Route 1-1 Check box.Tick to connect the video crosspoint output port directly to the video input port with the same port number, regardless of any routing in place on the video crosspoint. This is done in a “1 to 1” manner. For example, video crosspoint output port 14 to input port 14.

Lock Route 1-1 is a router configuration setting.

Lock Route 1-1 guarantees the presence of a video input’s embedded audio at a video crosspoint output, useful for audio routing within the Vega 30 unit. (Audio routing is done in the audio crosspoint.)

Note: Lock Route 1-1 affects the video crosspoint. It does not prevent any audio routing being made to the same router destination output.

See Section 3.5 “Routing Architecture” on page 20 for information about Vega 30 routing.

Quiet Switching V-Fade:

Enable Check box.Tick to enable audio quiet switching on an output-by-output basis.

Line Synchroniser Enable and Offset from Reference:

See Section 6 “Output Video Timing - Line Sync and Offset” on page 45 for information on these controls. (Settings available with options VG10-CSx.) See Note 1.

Enable Check box.Tick to enable the line synchronizer and clean switching functions.

Lines Enter number of video lines of offset required with respect to video reference for the video output. Setting must be in the range 0 to 15 inclusive.

Total offset = Lines offset + Pixels offset.

Pixels Enter number of pixels offset required with respect to video reference for the video output. Setting must be in the range 0 to 4095 inclusive.

Table 25 Processing Control Web Page - Items in the ‘table section’



Output Reference Offset

Read-only.Displays the measured time between an output signal and the reference signal. The value is in pixels (video samples).

The output may be advanced or retarded by changing the Lines and Pixels offset controls.

The Output Reference Offset value:

• Positive integer: Input arrives ahead of the reference.

• Zero: Input arrives at the same time as the reference.

• Negative integer: Input arrives later the reference.

See Section 6 “Output Video Timing - Line Sync and Offset” on page 45 for more information about using these values.

Note 1: Line Sync Controls and 4K/UHD (Quad-link):For each 4K router output, the Line Sync controls must be manually configured to the same settings across each of the four router ports set up for 4K.

Item Description

Table 25 Processing Control Web Page - Items in the ‘table section’ (Continued)


Vega 30 Router User Manual Configuration Vega 30 Web Interface 6.9

6.9 Configuration

Various protocol, network, system and logging settings are configured on the Configuration page.

Figure 69 Vega 30 Configuration Web Page

System settings, see Table 29

System Files, see Table 30

Protocol Settings, see Table 27

Top section, see Table 26

System Network settings, see Table 28 (Restart unit after changes here)

Logging settings, see Table 31



Item Description

Apply Button.Click to apply any settings changes made on the page.

(See Table 14 for more details about the Apply button operation.)


Restart Unit Button.Click to restart the Vega 30 Router unit.

A message appears asking if you do wish to restart. An example is given below.

After clicking OK to the message, a further message is displayed saying the unit is restarting. See example below.

While the unit is restarting, the browser will lose connection to the Vega 30 Router web page.

When the unit is ready, the front System LED is flashing green.

Table 26 Configuration Web Page - Top Section



Item Description

RollCall

Enable Check box. Tick to enable the RollCall protocol interface.

Port Enter port number for RollCall interface.(Leave as default)

SW-P-02

Enable Check box. Tick to enable the SW-P-02 general switcher protocol interface.

Port Enter port number for SW-P-02 interface.(Leave as default)

SW-P-08

Enable Check box. Tick to enable the SW-P-08 general remote protocol interface.

Port Enter port number for SW-P-08 interface.(Leave as default)

SNMP

Enable Check box. Tick to enable the SNMP protocol interface.

Community Get Enter privacy setting for SNMP Community read-only string.Typically set to “public”.

Community Set Enter privacy setting for SNMP Community read-write string.Typically set to “Private”.

Community Trap Enter SNMP Community Trap string.

SNMP Trap (1 to 5) and (6 to 10):

IP Address 1 to 10 Enter IP Address to send trap message to.

Table 27 Configuration Web Page - Protocol Setting Items



Item Description (And see Note 1)

IP Address Enter IP address of the Vega 30 unit. See Note 1.

Subnet Mask Enter subnet mask for the Vega 30 unit. See Note 1.

Gateway Enter IP address of the IP gateway for the Vega 30 unit. See Note 1.

DNS Server 1 Enter IP address of DNS server for the Vega 30 unit.

Note: At least one DNS server must be specified if URLs are used in any other settings.

See Note 1.

DNS Server 2 Enter IP address of a second DNS server for the Vega 30 unit.

Note: At least one DNS server must be specified if URLs are used in any other settings.

See Note 1.

Note 1: Perform a unit restart to make any changes take effect.

Table 28 Configuration Web Page - System Network Items (Restart Unit after Changes Here)

Item Description

Controller Name Enter name of the Vega 30 unit.

PSU Fitted Drop-down box. Select external PSU arrangement.

Note: When this setting matches the Vega 30 unit’s external PSU arrangement, any front panel error display and any unit error condition relating to an unfitted PSU module are cleared.

System Contact Enter name or details of a system contact.

Location Enter location of the Vega 30 unit.

NTP Server Enter URL or IP Address of a NTP server.

The NTP server is used to synchronize logging messages to the time of day.

See Note 1.

Note 1: When a URL is used, at least one DNS server IP address must be set up.(This allows the URL to be resolved into an IP address.)

Table 29 Configuration Web Page - System Setting Items



Item Description

Import Configuration File:

Browse Click to browse to a configuration file.

(Text box) Shows file name to be imported.

Import Click to import a configuration file.

Export Configuration File:

Export Click to export configuration information to a file.

Note: The exported configuration file is called "Config". If a file of this name already exists in the browser’s download area, the exported file will typically have its file name appended with (n), where n is an incrementing number. For example, “Config(2)”.

Import Persistence File:

Browse Click to browse to a persistence file.


Import Click to import a configuration file.

Export Persistence File:

Export Click to export persistence data to a file.

Note: The exported persistence file is called "Persistence". If a file of this name already exists in the browser’s download area, the exported file will typically have its file name appended with (n), where n is an incrementing number. For example, “Persistence(4)”.

Import Licence File:

Browse Click to browse to a license file.


Import Click to import a license file.

Table 30 Configuration Web Page - Files Items

Item Description

Logging Settings:

Enable Check box. Tick to enable logging.

IP Address Enter IP address of logging server.

Format Drop-down box.Select logging format.

• RFC3164: BSD syslog protocol.

• RFC3164: BSD syslog protocol + milliseconds.

• RFC5424: Syslog protocol.

(RFC3164 and RFC5464 are IETF system logging protocols.)

Port Enter IP port number for the logging data.

Table 31 Configuration Web Page - Logging Settings Items


Vega 30 Router User Manual Vega 30 RollCall Templates

7 Vega 30 RollCall Templates

The Vega 30 Router may be configured and controlled via SAM’s RollCall. Using a computer which has a network connection to the router, the Vega 30 Router unit’s RollCall template screens can be accessed with SAM’s RollCall Control Panel application.

The Vega 30 RollCall templates include screens for:

• Control and Configuration.

• Operational Control - Association routing of video and audio:

• XY Panels.

• Routing of video and audio.

• Direct Routing:

• Direct video routing.

• Direct audio routing.

Destinations can be protected to prevent further routes being made to that destination.

Router configurations can be backed up and restored at a later date, allowing the router to be returned to a known state, if required.

This section describes the Vega 30 Router RollCall templates:

See the SAM ‘RollCall Control Panel User Manual’ for further information about RollCall Control Panel.

7.1 “Connecting RollCall Control Panel” page 101

7.2 “Unit Information Template” page 107

7.3 “System Information Template” page 111

7.4 “Source Configuration Template” page 113

7.5 “Port Configuration Template” page 120

7.6 “Comms Setup Template” page 127

7.7 “Log Fields Template” page 134

7.8 “Assoc Routing - XY Panel Control Template” page 135

7.9 “Assoc Routing - Routing Template” page 148

7.10 “Direct Video - XY Panel Control Template” page 150

7.11 “Direct Video - Routing Template” page 151

7.12 “Direct Audio - XY Panel Control Template” page 152

7.13 “Direct Audio - Routing Template” page 153


Vega 30 Router User Manual Connecting RollCall Control Panel Vega 30 RollCall Templates 7.1

7.1 Connecting RollCall Control Panel

A Vega 30 unit has the following RollCall views:

• Vega 30 Unit.

• Vega 30 Router Matrix:

• Assoc Routing.

• Direct Video.

• Direct Audio. (Only available on units with a VG10-AR audio license.)

Figure 70 RollCall Template Views of a Vega 30 Router



7.1.1 Connecting to the Vega 30 Unit

1. Start up the RollCall Control Panel application.The RollCall initial screen is shown. See Figure 71.

2. Enter the IP address of the unit into the RollCall > Network dialog. (The default IP address is given in Section A.13 “Default IP Address” on page 244.)Click OK.

Figure 71 RollCall Initial Screen

Figure 72 RollCall > Network Dialog



3. Right-click on the Vega unit name and select Connect, see Figure 73.Or double-click on the Vega unit item name.

RollCall Control Panel connects to the unit and the Vega 30 RollCall template is shown, see Figure 74.

Within the RollCall templates, some unit settings require explicit saving using the “P” or “S” buttons located adjacent to the settings.

Figure 73 Connecting to Vega 30 Unit

Figure 74 RollCall Vega 30 Initial Template

Screen Selection Box

“P” and “S” buttons



All Vega 30 template screens contain a Screen Selection Box, which lists the available template screens. Navigate between Vega 30 template screens by clicking on the screen name in the box. See Figure 75.

Note: “S” and “P” buttons - After entering information in each text box, always click on the adjacent “S” button or press “return” to locally save the new setting. Do this for each text box. (Note: Clicking on the “P” button will return the setting to its preset default value).

“S” - Locally save new setting value (or press “return”).

“P” - Locally save default setting value.

Figure 75 Screen Selection Box

See Section 7.2 “Unit Information Template” on page 107.

See Section 7.3 “System Information Template” on page 111.

See Section 7.4 “Source Configuration Template” on page 113.

See Section 7.5 “Port Configuration Template” on page 120.

See Section 7.6 “Comms Setup Template” on page 127.

See Section 7.7 “Log Fields Template” on page 134.



7.1.2 Connecting to the Vega 30 Routing Templates

Connecting to the Vega 30 Assoc Routing, Direct Video or Direct Audio template is similar to procedure in Section 7.1.1 “Connecting to the Vega 30 Unit” on page 102:

1. Right-click on the Router Matrix item and select Expand, see Figure 76a.Or double-click on the Router Matrix item name.

This expands the Router Matrix item to show routing items: Assoc Routing, Direct Video and Direct Audio.

To open a routing item:

2. Right-click on a routing item and select Connect, see Figure 76b.Or double-click on the routing item name.

RollCall Control Panel connects to the Routing unit and the Vega 30 Routing RollCall template is shown, for example, see Figure 77.

7.1.3 Routing Matrix Levels

The Assoc Routing, Direct Video or Direct Audio templates are control interfaces to each of the Vega 30’s routing matrix levels.

Figure 76 Connecting to Vega 30 Routing Items

a) Expand routing item b) Connect to Vega 30 Assoc Routing

LevelNumber of

CommentSources Destinations

Assoc Routing 500 58 Source Association Routes

Direct Video 34 34 Video Routes

Direct Audio 741 928 Audio Routes

Table 32 Vega 30’s Routing Matrix 1 Levels



,

Each Vega 30 routing template screen contains a similar Screen Selection Box, see Figure 77. This is used to navigate between the Vega 30 Routing Matrix template screens.

All the template screens are described in sections below.

Figure 77 Vega 30 Assoc Routing Template

Screen Selection Box

Figure 78 Vega 30 Routing Item Screen Selection Box

Assoc Routing: Section 7.9 “Assoc Routing - Routing Template” on page 148.

Direct Video: Section 7.11 “Direct Video - Routing Template” on page 151.

Direct Audio: Section 7.13 “Direct Audio - Routing Template” on page 153.

Assoc Routing: Section 7.8 “Assoc Routing - XY Panel Control Template” on page 135.

Direct Video: Section 7.10 “Direct Video - XY Panel Control Template” on page 150.

Direct Audio: Section 7.12 “Direct Audio - XY Panel Control Template” on page 152.


Vega 30 Router User Manual Unit Information Template Vega 30 RollCall Templates 7.2

7.2 Unit Information Template

The Vega 30 Unit Information RollCall template screen shows unit information. The screen contains some read-only information as well as read-write settings that can be set up in the screen.

Table 33 and Table 34 list the read-only information items and read-write settings, respectively.

Figure 79 Vega 30 Unit Information Screen

Item Description

Software Version Version of software running on the unit.

Software Build Date Date when the software was built.

IP Address Unit’s IP Address.

IP Share Port Unit’s IP Port used by RollCall comms.

Table 33 Vega 30 Unit Information Screen - Read-only information

Read-Write Information

Read-Only Information



FPGA Numbers: Identifiers for the firmware running in FPGA IC devices. These IC devices implement part of the unit’s video input/output and router controller functionality:

A Identifier for firmware in FPGA Device A. (Inputs/outputs 1 to 12)

B Identifier for firmware in FPGA Device B. (Inputs/outputs 13 to 24)

C Identifier for firmware in FPGA Device C. (Inputs/outputs 25 to 34)

Controller Identifier for firmware in the Controller FPGA Device.

FPGA Versions: Versions of the firmware running in FPGA IC devices:

A Version of firmware in FPGA Device A.

B Version of firmware in FPGA Device B.

C Version of firmware in FPGA Device C.

Controller Version of firmware in Controller FPGA Device.

OS Version Version of the router controller embedded Operating System, running within the Vega 30 Router unit.

Enclosure Type of frame that a router controller is mounted in.

For the Vega 30 Router, this is set to ‘Standalone’, indicating that the Vega 30 controller only fits into a standalone Vega 30 frame.

Item Description

Unit Name Text field. Enter a name for the Vega 30 Router unit. See Note 1.

Location Text field. Enter a name for the unit’s location. See Note 1.

System Contact Text field. Enter a name for the system contact. See Note 1.

PSU Fitted Drop-down box.Select which PSUs are fitted.

Table 34 Vega 30 Unit Information Screen - Read-Write Settings

Item Description

Table 33 Vega 30 Unit Information Screen - Read-only information (Continued)



Use Long Names (32 chars) Check box.Tick the box to use the long source and destination names on the RollCall routing template screens and on other routing control panel source/destination selection buttons.

Time Auto Set:

NTP Server Radio button.Select this to use an NTP server for setting the system time.

Text box.Enter the URL of the NTP server to be used. See Note 2 and Note 3.

RollCall Log Server Radio button.Select this to use a RollCall log server for setting the system time.

(The RollCall log server to use is defined on the Comms Setup screen.)

Item Description

Table 34 Vega 30 Unit Information Screen - Read-Write Settings (Continued)



TimeZone Text box.Enter a Posix-style string to define the timezone to be used by the unit’s time.

Example:

• EST5EDT- for North American Eastern Time.

• EST5EDT4,M3.2.0/02:00:00,M11.1.0/02:00:00- for the full, explicit specification of N.American Eastern Time. (The daylight saving time start and end dates/times are specified in the text string.)

• PST8PDT- for Pacific time.

• JST-9- for Japanese time.

Refer to first two timezone formats specified in the Posix TimeZone documentation at:http://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html

Note 1: “S” and “P” buttons - After entering information in each text box, always click on the adjacent “S” button or press “return” to locally save the new setting.

(Note: Clicking on the “P” button will return the setting to its preset default value).

Note 2: “S” button - After entering information in the text box, always click on the adjacent “S” button or press “return” to locally save the new setting.

Note 3: When a URL is used, at least one DNS server IP address must be set up.(This allows the URL to be resolved into an IP address.)

Item Description

Table 34 Vega 30 Unit Information Screen - Read-Write Settings (Continued)


http://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html

Vega 30 Router User Manual System Information Template Vega 30 RollCall Templates 7.3

7.3 System Information Template

The Vega 30 System Information RollCall template screen shows read-only system information. This is shown in Figure 80 and information items are listed in Table 35.

Figure 80 Vega 30 System Information Screen (Status Information, Read-Only)

Item Description

Licenses:

VG10-CSA: Line sync / clean switching / dests 1-12

Yes/No. Indicates license is present or not.

VG10-CSB: Line sync / clean switching / dests 13-24


VG10-CSC: Line sync / clean switching / dests 25-34


VG10-AR: Audio routing


MAC Address MAC address of unit.

Serial Number Unit factory serial number.

PSU 1 Status Status of power supply connected to PSU 1 DC power inlet.

PSU 2 Status Status of power supply connected to PSU 2 DC power inlet.

Table 35 Vega 30 System Information Screen (Read-only Information)


Vega 30 Router User Manual System Information Template Vega 30 RollCall Templates 7.3

Fan:

Status Status of the internal Vega 30 cooling fan.

RPM Fan speed (rpm).

Temperature Internal unit temperature (ºC).

Reference Standard Video standard of reference signal connected to the Vega 30 unit.

Item Description

Table 35 Vega 30 System Information Screen (Read-only Information) (Continued)


Vega 30 Router User Manual Source Configuration Template Vega 30 RollCall Templates 7.4

7.4 Source Configuration Template

The Vega 30 Source Configuration RollCall template is wide and shows only part of a large sources table at any one time. The sources table lists pre-defined and user-defined sources. The table has 500 rows for 500 possible sources. The user can navigate around pages of this large table.

Each source table row shows information about each source name and the different columns are:

• Source name.

• Name of up to one video source associated with the source name.

• Names of up to 16 audio channel sources associated with the source name.

The following types of sources are listed in the table rows:

• 34 video input sources, each with 16 embedded audio channels. These are pre-defined. They are physical video inputs of the Vega 30 unit. These are not editable.

• Three MADI audio inputs (64 audio channel per input). These are pre-defined. They are physical MADI inputs of the Vega 30 unit. These are not editable.

• 454 user-defined sources (initially blank). These are user-definable. Video and audio channel source associations can be made. (Up to one video source, up to 16 audio channels.)

The Source Configuration template comprises 50 pages and each page shows 10 rows of the source table. The screen is shown in overview in Figure 80 (four pages are shown) and is shown in detail in Figure 83.

Figure 81 Sample Source Configuration Template Page


Source Names are not editable in the Source Configuration page.

Source Names can be edited either:


• or in the RollCall template screens,

• or in the RollCall XY Panel screens.



Figure 82 Overview of Source Configuration Screen (Pages 1,4,5 and 50 shown)

Page 1

Page 4

Page 5

...Page 50



7.4.1 Navigating the Source Configuration Screen

Sources information is shown in a large Sources table: There are 500 rows and 19 columns in the table.

Depending on the width of the screen window, there are left-right scroll bars to enable the user to view table columns.

Move between pages of the table (10 rows per page) with the Source Page Slider, see Figure 84 and Table 36.

Figure 83 A Source Configuration (Wide) Screen Page

Video Source column Audio Channel Source columns

Template selection box

Source Configuration Page Selection Slider

Source Names

Source Names

Show channel source numbers or names in table.(Numbers are shown in this figure.)

Pre

-de

fined

an

d U

ser-

defin

ed S

ou

rce

Def

initi

on

s



)

Figure 84 Vega 30 Source Configuration Screen

Source Page Slider

Use slider to move between pages.Move up and down rows of the long table.

Use left-right scrolls bars to move across the (wide) table columns

Show as Names

Item Description

Source Page (1-50) Slider and Number.

Navigate around source table rows with the Source Page Slider.See Source Page Slider Note.

Show as Names Check box.Tick to show Source Names instead of Source Numbers in the table body.

Table 36 Vega 30 Source Configuration Screen Controls



Note: Source Page Slider:

A control to move between pages of sources:

• Click on the number adjacent to the slider to enter a page number directly. Press <return> to enter the number.

• Click on the slider to move in coarse jumps in row pages.

• Drag the slider knob to move around row pages.

• Click on the slider knob to select it select it. Use the left-/right-arrow keys (“<“, “>”) for fine moves.



7.4.2 Columns of the Source Configuration Template

Figure 85 Source Configuration Columns

Video source Audio channel sources

Column Heading Description

Video Text box.

Name of the video source associated with this source definition.

Table rows 1 to 46: Video source for the pre-defined source.Not editable. (The text color is grey.)

Table rows 47 to 500: Enter the video source name for the user-defined source. Then press enter to finish entering characters.

To enter a ‘null source’, just press ‘0’ and press enter. (This produces a blank entry in the table)

Ch 1,Ch 2,

...

Ch 16

A column for each of the 16 audio channel sources associated with the defined source:

Table rows 1 to 46: This is not editable. (The text color is grey.)

Table rows 47 to 500: Enter the audio channel source name for the user-defined source. Then press enter to finish entering characters.

To enter a ‘null source’, just press ‘0’ and press enter. (This produces a blank entry.)

To enter a ‘follow video’ audio channel source, enter the channel source number (742 to 757) or the name (“DestThru-1” to “DestThru-16”), see Table 63 in Appendix C.

Table 37 Source Configuration Columns



7.4.3 Defining User-defined Sources on the Source Configuration Template

The first 46 table rows show pre-defined Sources. These are for the physical video input ports and MADI input ports. (I.e. 34 pre-defined Sources for video inputs and 12 predefined Sources to cover the three MADI 64-channel inputs - four pre-defined sources per MADI input port.) These rows are not editable; the text in these rows is colored grey.

The remaining 454 rows are for user-defined sources. These comprise up to one video source and up to 16 audio channel sources and are editable. (The Source Name is not editable in this screen.)

To define a user-defined Source:

1. In the table row for the source to be defined,enter a video source name or number. (Enter ‘0’ for no video source in the user-defined Source.)

While text is being typed, the text color is blue. Press enter on the keyboard to enter the channel source name or number.

If the entered value is not a recognized channel source name or number, a warning dialog is displayed.

2. Enter an audio channel source name or number. (Enter ‘0’ for no audio channel.)

Press enter on the keyboard to enter the channel source name or number.

3. Fill out the audio channels as required.

In the RollCall screens, a zero (‘0’) or hyphens (‘---’) in the channel source column means ‘null source’. (In the Web interface screens ‘null source’ is a blank entry.)

When a Source is routed to a destination, any channel in the Source that is set to ‘null source’ does not change the corresponding channel at the destination.

See Section 9 “Sources and Destinations” on page 162 for more information about defining sources.


Vega 30 Router User Manual Port Configuration Template Vega 30 RollCall Templates 7.5

7.5 Port Configuration Template

On the Vega 30 Port Configuration RollCall template screen, the Vega 30 unit’s video input and output ports can be configured. (I.e. input and output ports 1 to 34.) The configuration screen is shown in Figure 86.

Figure 86 Vega 30 Port Configuration Screen

Input Ports sectionSee Section 7.5.2 on page 122

Top sectionSee Section 7.5.2 on page 122

Output Ports sectionSee Section 7.5.3 on page 124



7.5.1 Port Configuration - Top Section of Template

7.5.1.1 Reset All Persistence

Click the button to reset ‘persistence’ settings (including all port settings) to their factory default.

7.5.1.2 VFade

This comprises three VFade controls, VFadeA, VFadeB and VFadeC. These control the ‘V Fade’ settings for router outputs 1 to 12, 13 to 24, and 25 to 34 respectively.

Each control is a drop-down box.

Select the V-fade rate to reduce any audible disturbance during switching. The setting is subjective and dependent on the audio media being switched.

• Fast. (Default)

• Medium.

• Slow.

For V-fade durations, see A.9 “Audio V-Fade Rates” on page 244.

Figure 87 Port Configuration - Top Section

Reset All Persistence VFade

Note: Persistence Settings:

Persistence settings include:

• All port settings.

• Routing.

• Names.

• and other settings that change in normal router use.

And does NOT include:

• Unit Information screen settings.

• Comms Setup screen settings.

Note: V-Fade function is enabled on an output-by-output basis. Use the:

• ‘V-Fade enable’ in the RollCall interface ‘Port Configuration’ template.

• ‘Quiet Switch V-Fade enable’ in the Web interface ‘Processing Control’ page.



7.5.2 Port Configuration - Input Ports

Configuration items for each Vega 30 input port are shown.

Figure 88 Vega 30 - Input Ports Section



Item Description

Input Standard Drop-down box.Select the video standard to use for switching to the corresponding video input.

The SMPTE RP-168 -2009 switching standard is used.

Selection options:

• SD625

• SD525

• HD720P50, HD720P59, HD720P60

• HD1080I50, HD1080I59, HD1080I60

• HD1080P50, HD1080P59, HD1080P60

Note: If the input signal is of a different standard, then any routing of that input will ‘crash-switch’.

4K Check box.

• Tick to make a quad-link source group.

The selected input and the three subsequent inputs are ticked. They form a quad-link source-group, to support a 4K quad-link input.

• Unticking any input undoes the quad-link source group.

Note: For a quad-link source-group, the switching video standard of the first input of the source-group will be use as the switching video standard for all the four source-group inputs. (I.e. the switching video standard settings of the other three source-group inputs are over-ridden.)

Note: For a 4K quad-link source-group, the switching video standard must be a HD 1080P video standard.

Table 38 Input Ports Configuration



7.5.3 Port Configuration - Output Ports

Configuration items for each Vega 30 output port are shown. Output ports each have some processing, see the functional block diagram in Figure 3 on page 18.

The processing functions include:

• Video routing lock.

• Quiet Switching.

• Line Synchronizer and Delay.

Processing configuration is done on this screen, see Figure 89 and Table 39.

Figure 89 Output Ports



Item Description

Lock Route Check box.Tick to connect the video crosspoint output port directly to the video input port with the same port number, regardless of any routing in place on the video crosspoint. This is done in a “1 to 1” manner, for example, output port 14 to input port 14.

Lock Route guarantees the presence of a video input’s embedded audio for audio routing within the Vega 30 unit. (Audio routing is done in the audio crosspoint.)

Lock Route is a router configuration setting.

Note: Lock Route does not prevent any audio routing being made to the same router destination output.

See Section 3.5 “Routing Architecture” on page 20 for information about Vega 30 routing.

4K Check box.

Tick to make a quad-link destination group.

The ticked input and the three subsequent outputs are grouped together to support a 4K quad-link output.

Unticking any output undoes the quad-link grouping.

V Fade Enable Check box.Tick to enable V-fade quiet switching functionality on an output-by-output basis.

Line Sync Enable Check box.Tick to enable the line-synchronizing and output offset delay functions.

Note: Line synchronizing uses Line Offset and Pixel Offset settings.

See Note 1 and Note 2.

Line Offset Slider.Adjust the number of lines offset from the Vega 30’s internal video reference for the output.

This setting, with the Pixel offset setting, acts to delay the output overall. Total offset = Lines offset + Pixels offset. This overall delay sets when the video switching occurs with respect to video reference timing for the output to switch cleanly

Value adjustment range: 0 to 15 lines.

See Slider Control Note below for general slider usage.


Table 39 Output Ports Configuration



Pixel Offset Slider.Adjust number of extra pixels offset from the Vega 30’s internal video reference timing for the output.

The setting, with the Line offset setting, acts to delay the output overall. This overall delay sets when the video switching occurs with respect to video reference timing for the output to switch cleanly

Value adjustment range: 0 to 4095 pixels.

See Slider Control Note below for general slider usage.


Reference Offset

Read-only.Displays the measured time between an output signal and the reference signal. The value is in pixels (video samples).

The output may be advanced or retarded by changing the Lines and Pixels offset controls.

The OutputReferenceOffset value:

• Positive integer: Input arrives ahead of the reference.

• Zero: Input arrives at the same time as the reference.

• Negative integer: Input arrives later than the reference.

See Note 1.

Note 1: See Section 6 “Output Video Timing - Line Sync and Offset” on page 45 for more information on the Line Sync Enable, Line Offset, Pixel Offset and Reference Offset controls.

Note 2: Settings available with options VG10-CSx.

Note: Slider Control Note: General slider usage to adjust a value:

• Click on the number adjacent to the slider to enter a number directly. Press <return> to enter the value.

• Click on the slider for coarse jumps.

• Drag the slider knob to change the value.

• Click on the slider knob to select it select it. Use the left-/right-arrow keys (“<“, “>”) for fine changes.

Item Description

Table 39 Output Ports Configuration (Continued)


Vega 30 Router User Manual Comms Setup Template Vega 30 RollCall Templates 7.6

7.6 Comms Setup Template

Various Vega 30 router controller network and comms port settings are configured in the Comms Setup template screen, together with a unit restart control. Settings change on this screen only take effect on the unit after a unit restart.

The screen is shown in Figure 90.

Figure 90 Comms Setup Screen

IP Address Settings,see page 128

RollCall+,see page 130

RollCall,see page 129

SNMP,see page 131

General,see page 132

Syslog,see page 133

Restart Unit,see page 133



7.6.1 Comms Setup - IP Address Settings

Figure 91 Comms Setup Screen - IP Address

Item Description

Unit IP Address Text box.Enter IP address of the Vega 30 unit.See Note 1.

Subnet Mask Text box.Enter subnet mask for the Vega 30 unit.See Note 1.

Default Gateway Address

Text box.Enter IP address of the IP gateway for the Vega 30 unit.See Note 1.

Primary DNS Address

Text box.Enter IP address of DNS server for the Vega 30 unit.See Note 1.

Secondary DNS Address

Text box.Enter IP address of a second DNS server for the Vega 30 unit.See Note 1.

MAC Address Displays the MAC address of the Vega 30 unit.



Table 40 Comms Setup - IP Address Settings



7.6.2 Comms Setup - RollCall Items

Figure 92 Comms Setup - RollCall Items

Item Description

IP Share Port Text Box.Enter network port for use by RollCall. Default is 2050.See Note 1.

Any Log Server Check box.

Tick to use any log server.

Note: This takes effect regardless of whether a ‘Specific Log Server’ has been entered.

Untick to use the log sever specified.

Specific Log Server Text box.Enter the name of a specific log server to use. (The Log Server name is configured in the Log Server itself.)The name entered must be correct and match the name set up in the Log Server.

See Note 1.



Table 41 Comms Setup - RollCall Items



7.6.3 Comms Setup - RollCall+

Figure 93 Comms Setup - RollCall+ Items

Item Description

Enable Check box.Tick to enable RollCall+ on the Vega 30 unit.

Domain Text box.Enter a RollCall+ domain number for the Vega 30 unit.See Note 1:

Address Text box.Enter a RollCall+ address for the Vega 30 unit.See Note 1:

See RollCall Address note below.



Table 42 Comms Setup - RollCall+ Items

Note: RollCall Address:

A RollCall address is of the form:

NNNN:UU:PP

Where:

• NNNN - RollCall Network address.

• UU - RollCall Unit address. Address of unit of a RollCall network. Range: 0x10 to 0xFF.

• PP - RollCall port address. The port number within a unit. Range: 0x00 to 0xFF.



7.6.4 Comms Setup - SNMP

Figure 94 Comms Setup - SNMP Items

Item Description

Enable Check box.Tick to enable the SNMP protocol interface.

Communities: (SNMP name fields for Get, Set and Trap commands/messages.)

Get Text box.Enter privacy setting for SNMP Community read-only string.Typically set to “public”.See Note 1.

Set Text box.Enter privacy setting for SNMP Community read-write string.Typically set to “Private”.See Note 1.

Trap Text box.Enter SNMP Community Trap string.See Note 1.

Trap Addresses: Several entry items:

Text box.Enter IP Address to send trap message to.See Note 1.



Table 43 Comms Setup - SNMP Items



7.6.5 Comms Setup - General

Figure 95 Comms Setup - General Items

Item Description

General Switcher (SW-P-02):

EnableCheck box.Tick to enable the unit’s general switcher protocol interface.

IP Port

Text box.Enter IP port number for general switcher protocol. Default = 2002.See Note 1.

General Remote (SW-P-08):

Enable Check box.Tick to enable the unit’s general remote protocol interface.

IP Port Text box.Enter IP port number for general remote protocol. Default = 2008.See Note 1.



Table 44 Comms Setup - General Items



7.6.6 Comms Setup - Syslog (Logging)

7.6.7 Comms Setup - Restart Unit

Click Restart Unit after changes have been made to settings in the Comms Setup screen.

Figure 96 Comms Setup - Syslog Items

Item Description

Enable Check box.Tick to enable the unit’s logging interface.

(Logging Format:) Radio buttons:Select logging format.

RFC3164 RFC3164: BSD syslog protocol.

RFC3164+ms RFC3164: BSD syslog protocol + milliseconds.

RFC5424 RFC5424: Syslog protocol.

Address Text box.Enter IP address of logging server. See Note 1.

IP Port Text box.Enter IP port for logging data. See Note 1.



Table 45 Comms Setup - Syslog Items

Figure 97 Comms Setup - Restart Unit

Item Description

Restart Unit Button.Click to restart the Vega 30 unit.

Table 46 Comms Setup - Restart Unit


Vega 30 Router User Manual Log Fields Template Vega 30 RollCall Templates 7.7

7.7 Log Fields Template

The Vega 30 Log Fields RollCall template screen shows some read-only unit logging information. These are auto-generated parameters for sending messages to RollCall Log Servers.

Figure 98 Vega 30 Unit Log Fields Screen

Item Description

SYSTEM_ DESCRIPTION

Text field.Describes the Vega 30 unit.

UPTIME

Text field.Indicates the time elapsed since the last Vega 30 unit hardware or software restart, or power on.

Table 47 Vega 30 Logging Fields (Read-only information)


Vega 30 Router User Manual Assoc Routing - XY Panel Control Template Vega 30 RollCall Templates 7.8

7.8 Assoc Routing - XY Panel Control Template

The XY Panel is a RollCall Control Panel screen for setting up and changing routes on a connected router (or on a device with some router behavior).

Routing control uses pre-defined and user-defined sources (up to 500-off) and destinations (up to 58-off). These sources and destinations are sometimes referred to as “Associations”.

(See the SAM ‘RollCall Control Panel User Manual’, Appendix 1 ‘XY Panel’, for further information about RollCall Control Panel and XY Routing Panels.)

The Vega 30 Assoc Routing XY Panel template has four tabs. The Routing tab is shown in Figure 99.

Figure 99 (Assoc Routing) XY Panel - Routing Tab

Tabs: Routing, Edit Names, Edit Protect and Options

Sources

Up to 500 Pre-defined and User-defined Sources

Destinations

Up to 58 pre-defined Destinations

Panel Lock/Unlock

TAKE button

Destination Name

Currently routed Source Name

Note: Panel appearance:

The overall appearance of the routing panels may be customized, see the Section 7.8.4 “Options Tab” on page 143 for options regarding the appearance of buttons etc.



The tabs are:

• Routing - for making routes.

• Edit Names - for editing source and destination names.

• Edit Protect - for protecting a destination from having further sources routed to it.

• Options - set to customize the display of the XY panel.

7.8.1 Routing Tab


7.8.1.1 Making a Route

1. Click on a Destination button to select a destination.

The Source button for the source currently routed to the destination is highlighted and routing information is shown at the TAKE button. See Figure 100.

Figure 100 (Assoc Routing) XY Panel - Making a Route, Select a Destination

Select a Destination

Current Source

TAKE button

Current Source

Selected Destination

Destination Name

Currently routed Source Name



2. Click on a Source button to select a new source.

The selected Source name appears on the TAKE button. See Figure 101.

3. Click TAKE to make the route.

The selected source is routed to the selected destination.

Figure 101 (Assoc Routing) XY Panel - Making a Route, Select a Source

TAKE buttonSelected Source



4. Clicking on the selected Destination button toggles selection of it. Select the destination and the new source button is shown as the currently routed source, see Figure 102.

7.8.1.2 Protecting a Destination

Destination protect is an operational control.

1. Select a Destination.

A Destination Protect button appears. See Figure 103.

Figure 102 (Assoc Routing) XY Panel - Route Made

New route information now shown as the currently routed source.

Figure 103 (Assoc Routing) XY Panel - Destination Protect

Selected Destination

Destination Protect buttonOpen padlock symbol indicates Destination is not protected

(Closed padlock symbol indicates a Destination is protected)



2. Clicking the Destination Protect button toggles destination protection on and off.

To review and edit protected destinations, see Section 7.8.3 “Edit Protect Tab” on page 142. To protect multiple destinations, see Section 7.8.3 “Edit Protect Tab” on page 142.

See the Section 7.8.4 “Options Tab” on page 143 for options regarding the appearance of buttons.

Figure 104 Destination Protect Button

a) Destination is not protected.

Click to protect.

b) Destination is protected.

Click to unprotect.



7.8.1.3 Panel Lock

The XY panel can be locked to prevent further routing from the panel.

To lock the panel:

• Click the Panel Unlocked button.

To unlock the panel:

• Click the Panel Locked button.

See Figure 105.

Figure 105 Panel Lock Button

a) Panel is Unlocked.

Click button to Lock panel.

b) Panel is Locked.

Click button to Unlock panel.

Panel is Locked and “greyed out”



7.8.2 Edit Names Tab

The Edit Names Tab shows the selection buttons all router source and destinations. See Figure 106. The names on each button can be edited on this screen.

To change a name:

1. Click on a button to select it.

2. Enter a new name.

3. Press enter to enter the new name.


Figure 106 (Assoc Routing) XY Panel - Edit Names Tab

Figure 107 (Assoc Routing) XY Panel - Entering a Source or Destination Name



7.8.3 Edit Protect Tab

The Edit Protect Tab shows the destination selection buttons, see Figure 108. All protected destinations are shown with a padlock symbol on the button, see Figure 109.

To protect / unprotect a destination:

• Click on a button to toggle the destination protect feature on/off.

Outside of the Edit Protect tab, on the XY Panel Routing tab, when a destination is selected, the protected status is shown at the bottom of the tab. See Figure 110 and Section 7.8.1 “Routing Tab” on page 136.

Figure 108 (Assoc Routing) XY Panel - Edit Protect Tab

Figure 109 (Assoc Routing) XY Panel - Edit protect Tab (Protected Destination with Padlock Symbol)

Figure 110 Destination Protect Buttons Indicate Protect Status

a) Destination is not protected. b) Destination is protected.



See the Section 7.8.4 “Options Tab” on page 143 for options regarding the appearance of buttons.


7.8.4 Options Tab

The Options Tab provides settings for customizing the display of the XY panel. See the SAM ‘RollCall Control Panel User Manual’, Appendix 1 ‘XY Panel’, for further information about RollCall Control Panel, XY Routing Panels and the Options tab.

The Options Tab is shown in Figure 111.s

The Options tab has two modes: User Mode and Admin Mode, indicated by radio buttons on the screen. The XY Panel always starts in User Mode. The features in the Options Tab are only available when in Admin Mode. (If required, a password can be set up to secure this mode, see the SAM ‘RollCall Control Panel User Manual’ for more information.)

The Options tab contains buttons to access the various features controlled by the tab. The features in the Options tab are summarized in Table 48. See the SAM ‘RollCall Control Panel User Manual’ for more information.

Figure 111 (Assoc Routing) XY Panel - Option Tab

Options Tab Mode radio buttons

Click buttons to access features.



Feature

Router Functions Define Take and Undo buttons to be included in the Routing screen.

If no Take button is present, then routing takes place immediately.

An Undo button may be added with a time out.

Router Display Define additional information to be displayed on the source and destination buttons.

Table 48 (Assoc Routing) XY Panel - Option Tab Controls



Popout Display Customize the display of the XY panel when it is used as a pop-out screen.

Feature

Table 48 (Assoc Routing) XY Panel - Option Tab Controls (Continued)



Button Sizes The source and destination buttons can be resized and button text formatted.

Panel Sizes Adjust the number of rows and columns of source and destination buttons, and the spacing between them.

Feature




Button Maps Use button maps to define alternative mappings of the source and destination buttons.

Do this to:

• Limit the number of source and destination buttons visible on the router displays.

• Control the order in which the buttons are displayed.

Manage Options Save and load settings, restore defaults and set an admin password.

Feature



Vega 30 Router User Manual Assoc Routing - Routing Template Vega 30 RollCall Templates 7.9

7.9 Assoc Routing - Routing Template

The Routing template is a RollCall Control Panel screen for setting up and changing routes on a connected router (or on a device with some router behavior). It is an alternative screen to the XY Panel template for controlling routing and is shown in Figure 112.

The template presents a list of source and a list of destinations.

Routes can be made upon pressing the Take button, or made immediately the route is prepared, depending on the Take Mode.

Figure 112 Assoc Routing - Routing Panel

Take button

Control Description

Take Button.Click to make a prepared routing.

Cancel Button.Click to cancel a prepared routing.

Take Mode: Radio button.

Immediate TakeRoutes are made immediately with the source and destination selection.

Use Take Button Routes are made upon clicking the Take button.

Dest Protect: Check box.

Protected Tick to protect/unprotect the selected destination.

Table 49 Routing Screen Controls


Vega 30 Router User Manual Assoc Routing - Routing Template Vega 30 RollCall Templates 7.9

To make a route:

1. Click on a destination item in the destination list to select a Destination.The currently routed Source is highlighted in the list of sources. See Figure 113.

2. Click on a new Source to select the next Source to be routed, see Figure 113.

A route has been prepared.

3. Click the Take button to make the route.A new route is made and the new Source is highlighted when the Destination is selected, see Figure 113.

Figure 113 (Assoc Routing) Routing Screen - Select Destination

Figure 114 (Assoc Routing) Routing Screen - Source Selected.

Select Destination

Currently routed Currently routed Source

Select Source to be routed


Vega 30 Router User Manual Direct Video - XY Panel Control Template Vega 30 RollCall Templates 7.10

7.10 Direct Video - XY Panel Control Template

The Direct Video routing XP panel controls the Vega 30 Router’s video crosspoint.

Routing is controlled via the pre-defined video source (up to 34-off) and video destination (up to 34-off) names.

The Direct Video routing XP panel screen operation is similar to the one described in Section 7.8 “Assoc Routing - XY Panel Control Template” on page 135.

Figure 115 (Direct Video) XY Panel

Take button

Video Sources

Up to 34-off video sources

Video Destinations

Up to 34-off video destinations


Vega 30 Router User Manual Direct Video - Routing Template Vega 30 RollCall Templates 7.11

7.11 Direct Video - Routing Template

The Direct Video routing template controls the Vega 30 Router’s video crosspoint.

The Direct Video routing template screen operation is similar to the one described in Section 7.9 “Assoc Routing - Routing Template” on page 148.

Figure 116 (Direct Video) Routing Template

Take buttonVideo Sources Video Destinations


Vega 30 Router User Manual Direct Audio - XY Panel Control Template Vega 30 RollCall Templates 7.12

7.12 Direct Audio - XY Panel Control Template

The Direct Audio routing XP panel controls the Vega 30 Router’s audio crosspoint.

Routing is controlled via the audio channel source names and numbers. (See Table 63 in Section Appendix C on page 250.). There are 741 audio channel sources and 928 audio channel destinations.

The Direct Audio routing XP panel screen operation is similar to the one described in Section 7.8 “Assoc Routing - XY Panel Control Template” on page 135.

Figure 117 (Direct Audio) XY Panel

TAKE button

Audio Sources

741-off

Audio Destinations

928-off


Vega 30 Router User Manual Direct Audio - Routing Template Vega 30 RollCall Templates 7.13

7.13 Direct Audio - Routing Template

The Direct Audio routing template controls the Vega 30 Router’s audio crosspoint.

The Direct Audio routing template screen operation is similar to the one described in Section 7.9 “Assoc Routing - Routing Template” on page 148.

Figure 118 (Direct Audio) Routing Template

Take buttonAudio Sources Audio Destinations


Vega 30 Router User Manual Line Synchronizer and Offset from Reference Output Video Timing - Line Sync and Offset 8.1

8 Output Video Timing - Line Sync and Offset

8.1 Line Synchronizer and Offset from Reference

Each switched video output can be independently line-synchronized and, if required, delayed from the reference timing. The licensed options VG10-CSx are required for this feature. The functions licensed are:

• Line Synchronizing - synchronizes the router output to the video reference according to the routed input’s switching video standard.

• Delay - if required, delay can be added into each router output to offset the output signal timing from the reference signal timing.

These two functions are both implemented within the unit using video storage buffering on a per router output basis. They both share the video buffer storage on each output.

8.1.1 Buffer Storage Capacity

The buffer storage capability varies according to video standard. Table 50 lists the storage capability for the video buffer block for each supported video standard.

The amount of storage used for line-synchronizing depends on the relative timing relationship between each router input signal and the video reference. The remaining buffer storage capacity for each output can be used to offset (i.e. delay) each router output from the video reference.

If all router video input signal timings are co-timed with reference to ±½ line, then a router output can then typically be delayed by up to a further 14 lines regardless of standard.

Note: For each output, video buffer storage is used for:

Line-synchronizing and Output delay

Video Switching Standard

Pixels per line

Buffer Store Capacity

(Video Samples) Lines Pixels

SD525 858 38 163

SD625 864 37 799

HD1080i50 2640 12 1087

HD1080i59 2200 14 1966

HD1080i60 2200 14 1966

HD1080p50 2640 12 1087

HD1080p59 2200 14 1966

HD1080p60 2200 14 1966

HD720p50 1980 16 1087

HD720p59 1650 19 1417

HD720p60 1650 19 1417

Table 50 Video Buffer Block Storage Capability

Note: Buffer storage capacity =

Storage used for Line-sync + Storage used for delaying output.


Vega 30 Router User Manual User Controls Output Video Timing - Line Sync and Offset 8.2

8.2 User Controls

On each output, the line-synchronizer and offset-delay functions share the same user controls and status displays. Table 51 lists the controls that appear on the Vega 30 Web and the RollCall interfaces.

In practice, when setting up the router video output offset:

• Enable the control on each output.(Note: license options VG10-CSx are required for this feature.)

Then, there are two stages:

1. Adjust the offset so that the reference offset value is reported as a small, positive value for all the router video inputs.

2. Add more offset to delay the video output as required.

Controls Web interface RollCall template

Enable / disable: ‘Line Synchroniser Enable and Offset from Reference’enable check box

Line Sync Enablecheck box

Offset controls: Lines offset setting Lines Offset

Pixels offset setting Pixels Offset

Measured offset: Output Reference Offset(in units of pixels)

Reference Offset(in units of pixels)

Table 51 User Controls


Vega 30 Router User Manual Input Signal Timing Use Cases Output Video Timing - Line Sync and Offset 8.3

8.3 Input Signal Timing Use Cases

The following video input signal timing cases are considered:

• Timing Case 1) Input arriving some pixels earlier than reference.

See Figure 119 and Table 52 in Section 8.3.1 "Timing Case 1) Input Arriving some Pixels Earlier than Reference" on page 157.

• Timing Case 2) Input arriving co-timed with reference.

See Figure 120 and Table 53 in Section 8.3.2 "Timing Case 2) Input Arriving Co-timed with Reference" on page 158.

• Timing Case 3) Input arriving some pixels later than reference.

See Figure 121 and Table 54 in Section 8.3.3 "Timing Case 3) Input Arriving some Pixels Later than Reference" on page 159.

It is assumed that:

• License options VG10-CSx are active on the Vega 30 unit for an output.

• Line Sync feature is enabled on the output.

• Lines offset and Pixels offset controls are initially set to 0 in each case.

An output offset must be set up to cope with the timing of any input source routed to the output destination. It must be set up for the latest-arriving input signal.

Note: A change in the input signal timing or to the overall offset value (Lines Offset + Pixels Offset) is reflected in the reported Reference Offset value.

Increasing the Lines Offset value by 1 will produce an increase in the Reference Offset value by an amount equal to one line in the video standard for the signal. For example, 1 line in 1080i59 is 2200 pixels, so the Reference Offset value will change by that amount.



8.3.1 Timing Case 1) Input Arriving some Pixels Earlier than Reference

Figure 119 Vega 30 - Video Input Timing Cases and the Reference Offset Control:Timing Case 1) Input Earlier than Reference

Input early compared to Ref,Positive Reference Offset value

Output with added delay

Video Input Signal Timing

Offset Setting

Reference Offset

value shown(see Figure

119)

Comments

Reference Offset

Video Output Signal Timing

(with respect to reference)

Video Buffer Storage

(Pixels) (Pixels) (Pixels)

Case 1) Input Earlier than Reference

• Set Offset to 0.

0 A Reference Offset reported is a positive number.

Output is timed up with reference.

Storage used to buffer the input by A pixels.

Thus delaying the input

• Introduce an offset of B pixels:

+B (A+B) Output is late by B pixels.

Storage used to buffer signal by A+B pixels.

Table 52 Input Timing Case 1)



8.3.2 Timing Case 2) Input Arriving Co-timed with Reference

Figure 120 Vega 30 Video Input Timing Cases and the Reference Offset Control:Timing Case 2) Input Co-timed with Reference

Zero Reference Offset value



Offset Setting

Reference Offset


119)

Comments

Reference Offset





Case 2) Input Co-timed


0 0 Reference Offset reported as zero.

Output timed up with reference.

No storage consumed.

• Introduce an offset of B pixels:

+B B Output late by B pixels.

Storage used to delay output by B pixels.

Table 53 Timing Case 2)



8.3.3 Timing Case 3) Input Arriving some Pixels Later than Reference

Figure 121 Vega 30 Video Input Timing Cases and the Reference Offset Control:Timing Case 3) Input Later than Reference

Input late compared to ref,Negative Reference Offset value



Offset Setting

Reference Offset


119)

Comments

Reference Offset





Case 3) Input Later than Reference


0 minus A Reference Offset a negative number.

Need to add an Offset.

• Add an offset of +A pixels to account for late-arriving input:

+A (-A +A) = 0 Output is late by A pixels.

No storage consumed.

• Introduce a further offset of B pixels:

A+B B Output is late by (A+B) pixels.

Storage used to delay output by B pixels.

Table 54 Timing Case 3)


Vega 30 Router User Manual Setting Up Router Offset Output Video Timing - Line Sync and Offset 8.4

8.4 Setting Up Router Offset

It is important to know the input relative signal timing of all signals connected to a router. This should be checked using a suitable piece of video waveform analyzing equipment.

The Vega 30 Router offers some assistance to set up the router offset values. The procedure is:

1) Identify the latest-arriving input:

1. Set all Lines Offset and Pixel Offset values to zero.

2. Either:

• Set all routes to be “1 to 1”, i.e. ‘Source 1’ to ‘Destination 1’,

‘Source 2’ to ‘Destination 2’, ...

and ‘Source 34 to ‘Destination 34’.

Or

• Route each input in turn to just one destination.

To record the Reference Offset value for each input.

3. Inspect the recorded values and identify the latest-arriving input and its Reference Offset.

For outputs with a VG10-CSx license option:

4. Enable the Line Sync feature on each output with a VG10-CSx option.

5. Route the latest-arriving input to a destination.

2) Set the offset value:

The action required depends on whether the latest-arriving video input Reference Offset value is positive or negative:

Negative: If the latest arriving input’s Reference Offset value is negative, then:

6. Add an offset until the Reference Offset value is a small positive number (for example, 10 pixels).

This gives a timing margin of 10 pixels.

Positive: If the latest arriving input’s Reference Offset value is positive, then:

7. Increase the offset value for the destination by a small positive number (for example, increase by 10 pixels).The Reference Offset value increases by the same amount.

This gives a timing margin of 10 pixels.

Now:

8. Change other destinations to the same Reference Offset value.

Note:Smallest

Latest Arriving Input and Reference Offset:

If all input timings are earlier than reference, then the latest-arriving input’s Reference Offset value will have the smallest positive value.

If all inputs are co-timed with reference, then all input timings are the same and the Reference Offset value is zero.

If one or more input timings are later than reference, then the latest-arriving input’s Reference Offset value will have the most negative value.


Vega 30 Router User Manual Setting Up Router Offset Output Video Timing - Line Sync and Offset 8.4

This has set up the Vega 30 Router video output offset to be the earliest possible, for any of the inputs. Any input may then be routed to any output.

3) Setting up Router Output Delay:

Further delay can be added to each router output by increasing the offset value for each router destination.


Vega 30 Router User Manual Introduction Sources and Destinations 9.1

9 Sources and Destinations

This section describes the Vega 30 Router sources which are routable to destinations:

9.1 Introduction

Sources and destinations are routed by the router. Both comprise:

• Up to one Video channel.

• Up to 16 Audio channels.

9.1.1 Destinations

Destinations may have sources routed to them.

Destinations are numbered 1 to 58 and include:

• Video outputs (1 to 34).

• Six MADI outputs (35 to 58).

Destinations are pre-defined.

Destinations have an individual default destination name. The user may edit the destination name.

There are 8- and 32-character names.

A destination comprises up to one video signal and 16 audio channels.

• If a destination has a video channel, then it is assumed to be the corresponding physical video output port on the router (comprising video with 16 channels of embedded audio).

• If a destination does not have a video channel, then it is assumed to be part of a MADI output port (16 audio channels, one quarter of the 64 channels of a MADI port).

9.1.2 Sources

Some sources are pre-defined and others are user-defined.

Sources can be routed by the router to destinations.

Sources have an individual Source number.

There are up to 500 sources, including:

• Video inputs, pre-defined (Source numbers 1 to 34).

• Three MADI inputs, pre-defined (Source numbers 35 to 46).

• User-defined sources (Source numbers 47 to 500).

Each source has a default source name. The user may edit the source name.

There are 8- and 32-character names.

A source comprises up to one video signal and 16 audio channels.

9.1 “Introduction” page 162

9.2 “Source Types” page 163

9.3 “User-defined Sources” page 164

9.4 “Making User-defined Sources” page 170


Vega 30 Router User Manual Source Types Sources and Destinations 9.2

9.1.3 Defining User-defined Sources

Source definition is carried out in the rows of either of the following control screens:

• Vega 30 Source Names Web page.

• Vega 30 Rollcall Source Configuration template.

9.1.4 Source and Destination Port Numbering

Table 61 of Appendix B on page 247 lists:

• Video port source and destination numbers.

• MADI port source and destination numbers.

9.2 Source Types

Sources are presented in a tabular format on the Vega 30’s Web interface or in a RollCall template. Different source types are described in Table 55.

Source Numbers Description

1 to 34 Pre-defined video sources:

The first 34 table rows contain pre-defined video sources which correspond to the physical video inputs of the router. (I.e. video with 16 channels of embedded audio.)

The audio channel sources use ‘follow video’ audio channel sources.

Routing these sources routes video and its embedded audio to the router destination and router output.

35 to 46 Pre-defined MADI audio sources:

The table rows contain pre-defined sources which correspond to each of the three physical MADI inputs to the router.

Each MADI 64-channel input is divided into four groups of 16 channels (A, B, C and D):Each table row is predefined for 16 audio channels. Four rows (A, B, C, and D) represent one physical MADI input to the router, carrying 64 MADI audio channels in total.

47 to 500 User-defined Sources:

The remaining table rows permit the user to define further sources, which can be combinations of physical router inputs (video inputs, embedded audio channels, MADI audio input channels) and internal audio signals (silence and test tones).

User-defined Sources may be fully-defined (all channels defined) or partially defined (some channels not defined).

Table 55 Source Types in Table Rows


Vega 30 Router User Manual User-defined Sources Sources and Destinations 9.3

9.3 User-defined Sources

User-defined sources are the sources numbered 47 to 500. After a User-defined source is defined, it may be routed.

Each User-defined source can comprise:

• A video source with up to 16 audio channels.

• Up to 16 audio channels.

A User-defined source may be associated with physical router inputs or internal audio sources. ‘Follow video’ audio channel sources can be used.

User-defined sources are defined via the Vega 30 Web interface or RollCall interface using the following control interface pages:

• Vega 30 Source Names Web page.

• Vega 30 Rollcall Source Configuration template.

Remember to click Apply at the top of the Web page when changes are finished.

9.3.1 Video Source Numbers

The video sources are numbered 1 to 34, corresponding to the external Video Input ports, see Table 61 in Appendix B on page 247.

When using a 4K video source, the lowest video source number of the 4K quad-linked sources is used.

9.3.2 Audio Channel Source Numbers

The audio channel sources are numbered 1 to 757:

• 1 to 544 correspond to fixed, de-embedded audio channels from the video crosspoint outputs;

• 545 to 736 correspond and to the fixed, external MADI Input channels.

• 737 to 740 internal test signals.

• 741 internal audio silence.

• 742 to 757 ‘Follow Video’ internal sources.

See Table 63 in Appendix C on page 248 for more information.

Note: Web Interface:

In the Source Names Web page, enter a name, or a blank (i.e. clear the table entry and press enter). Press the enter key to finish.

Note: RollCall interface:

In the RollCall Source Configuration template, enter either a number, or a name, or a zero. Press the enter key to finish.



9.3.3 ‘Follow Video’ Audio Channel Sources (DestThru)

There are 16 ‘follow video’ audio channel sources which are internal, virtual sources.

These are numbered 742 to 757, see the latter part of Table 63 in Appendix C on page 248.

The ‘follow video’ audio channel sources represent the embedded audio of the video source specified in a pre-defined source or in a user-defined source. These sources are independent of video crosspoint routing. As a result, ‘Follow video’ audio channel sources are used instead of fixed source numbers in user-defined sources for many use cases. For example, where embedded audio channels are subject to routing through the video crosspoint.

There is one ‘follow video’ source for each of the 16 embedded audio channels of the corresponding video source signal, see Table 56.

9.3.4 ‘Follow Video’ versus ‘Fixed’ Audio Channel Sources

The behavior of the ‘follow video’ audio channel sources and the ‘fixed’ channel source numbers is outlined here with an example.

Some user-defined sources are shown in Figure 122.

‘Follow Video’ NameEmbedded audio channel

(of corresponding video source signal)

DestThru-1 1

DestThru-2 2

DestThru-3 3

DestThru-4 4

DestThru-5 5

DestThru-6 6

DestThru-7 7

DestThru-8 8

DestThru-9 9

DestThru-10 10

DestThru-11 11

DestThru-12 12

DestThru-13 13

DestThru-14 14

DestThru-15 15

DestThru-16 16

Table 56 ‘Follow Video’ Audio Channel Sources

Note: ‘Follow video’ audio channel sources represent the embedded audio of the video source specified in a pre-defined source, or in a user-defined source.



In Figure 122:

• Sources 101, 102 and 103:

• Each use a different video source.

• Each contain audio channel sources all set to ‘follow video’ sources.(Source numbers 742 to 757; “DestThru-N”)

• Sources 104, 105 and 106:

• Each use a different video source.

• Each contain audio channel sources all set to ‘fixed’ audio channel sources. (Source numbers 1,2,3, etc. Factory source names “V.In 1-1”, “V.In 1-2” etc.)

The fixed numbers are for the embedded audio channels on video crosspoint output 1. (All ‘Fixed’ audio numbers are found in Table 63 of Appendix C.)

Table 57 lists the resulting different video and embedded audio at router video destination outputs when the sources of Figure 122 are then routed to some destinations (Table 57 lists three destinations, Dest 1, Dest 13 and Dest 27).

Source Definition

Video Source

Audio Channel Sources

1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Source 101:1

DestThru

-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

Source 102:2

DestThru

-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

Source 103:3

DestThru

-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

Source 104:1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Source 105:2 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Source 106:3 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

Figure 122 User-defined Source Example



In Table 57, at each destination it can be seen that:

• For Sources 101, 102 and 103, the embedded audio is from the corresponding routed video input.

• For Sources 104, 105 and 106, the embedded audio is from a fixed source position, video crosspoint output 1. The same video crosspoint output, output 1, and this does not change. The actual audio presented depends on which input has been routed to that video crosspoint output.

Conclusion:

When making a route:

• Use ‘Follow Video’ audio channel sources to:

• Keep embedded audio channels with their input video.

• Use ‘Fixed’ audio channel sources when:

• Fixed embedded audio sources are required.

• Using (fixed) MADI input sources.

Routed Source

Sources Routed To Destinations:

Dest 1 Dest 13 Dest 27

Video from

Embedded Audio from

Video from

Embedded Audio fromVideo from

Embedded Audio from

Source 101 I/p 1 Video I/p 1 I/p 1 Video I/p 1 I/p 1 Video I/p 1



Source 104 I/p 1Vid Xpt O/p 1

(= from Video I/p 1)I/p 1

Vid Xpt O/p 1(= from last Video I/p

routed to Vid Xpt O/p 1)I/p 1


routed to Vid Xpt O/p 1)













Table 57 Routed User-defined Sources Example



9.3.5 Silence Audio Channel Source

If silence is required on an audio channel, then a source must be defined with silence on the required channel and a route then made.

Silence is an internal source available to the router.

9.3.6 Null Source

For each user-defined source, video and audio channels may be defined.

If no video source, nor audio channel source, nor silence is required in a particular user-defined source, a ‘null source’ must be entered into the source definition. To enter a ‘null source’:

• Enter a blank (in the Web interface)

or

• Enter a ‘0’ (in a RollCall template).

In this case, if this source is routed to a destination, then the destination channel will be unchanged by ‘null source’.

Initially, all user-defined sources are set to ‘null source’ for each user-definable channel source. (Web interface screen table entries are blank. RollCall template screen table entries show ‘0’ or ‘---’.)

9.3.7 Partial Sources

A user-defined source comprises video and 16 audio channels. If there are one or more null sources in the user-defined source, it is called a partial source.

When a partial source is routed to a destination, the channel source(s) with null source(s) in them do not change the corresponding destination channel(s) - these destination channels are unaffected by the route.

After the route is made, the routed source tally displayed on a routing panel will indicate the last source name to be routed to that destination, whether partial or not.

9.3.7.1 Partial Source Routing Example

The example illustrates how destination channels are unaffected when a partial source is routed. Figure 123 shows the following routing sequence and shows the resulting destination:

1. Select a destination.

2. Pre-select a partial source.

3. Take, i.e. make the route.



After the route is made, at the routed destination:

• The routed video source is unaffected, because of the ‘null source’ in the pre-selected source.

• Audio channels 1 to 4 have been replaced by audio channel sources 545 to 548 (i.e. MADI audio channels of MADI input 1).

• Audio channels 5 to 8 are not affected by the routing, because of the ‘null sources’ in the pre-selected source.

• Audio channels 9 &10 and 11 &12 have been pair-swapped.

• Audio channels 13 to 16 are not affected by the routing, because of the ‘null sources’ in the pre-selected source.

Routed Source

Tally

Source Definition

Video Source


1. Selected destination is:

Destination 1 SRC-1 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

2. Pre-selected source is:‘null

source’ ..‘null sources’.. pair-swapped ..‘null sources’..

User-defined Source 50

VSRC-50 0 545 546 547 548 0 0 0 0 11 12 9 10 0 0 0 0

Then:

3. After the route is made:

Destination 1 VSRC-50 1 545 546 547 548 5 6 7 8 11 12 9 10 13 14 15 16

unchanged unchanged pair-swapped unchanged

Figure 123 Partial Source Routing example


Vega 30 Router User Manual Making User-defined Sources Sources and Destinations 9.4

9.4 Making User-defined Sources

User-defined sources are made via the Vega 30 Web interface or RollCall interface using the following pages:

• Vega 30 Source Names Web page.See Section 7.4 “Source Configuration Template” on page 113.

• Vega 30 Rollcall Source Configuration template. See Section 6.3.3 “Source Names Web Page - Source Names Table” on page 57.

Only channel source names or numbers of the physical Vega 30 unit or of internal Vega 30 sources may be entered on the screens. Do not enter any User-defined source names nor numbers.

For the RollCall template, video sources and audio channel sources are displayed as either names or as numbers. Either a name or a number may be entered. If sources names are being shown, then an entered a source number will show as the corresponding name after pressing carriage return (<cr>). And vice versa.

Entering a zero (0) in the RollCall template clears the entry in the Source Configuration screen and enters ‘no channel source’.

Names are case insensitive.

Note: In the RollCall Source Configuration template, enter either a number, or a name, or a zero.

In the Source Names web page, enter either a number, or a name, or a blank (i.e. clear the table entry and press enter).

Press the enter or return key to finish.


Vega 30 Router User Manual Routing Use Cases

10 Routing Use Cases

The following use cases are considered for the Vega 30 Router crosspoint architecture:

• Video-only routing.

• MADI audio-only routing.

• Video and MADI routing.

• Monitoring audio/video at the router.

• Inserting audio channels in the router.

• Swapping audio channels in the router.

Lastly, a system application example is presented. This shows:

• How the Vega 30 Router may be used to implement a target system.

• How the Vega 30 Router architecture can implement some other system functions.

Section contents:

10.1 “Introduction” page 172

10.2 “Video-only Router Use Case” page 173

10.3 “MADI-only Router Use Case” page 174

10.4 “Video and MADI only router” page 175

10.5 “Monitoring a Router Input and Output” page 176

10.5.1 “Monitor a Video Input” page 176

10.5.2 “Monitor Audio in a Router Video Output” page 177

10.5.3 “Monitor a Router Video Output” page 179

10.6 “Inserting Audio Channels into Router Inputs and Outputs” page 180

10.6.1 “Inserting MADI Audio into a Video Input” page 180

10.6.2 “Inserting MADI Audio into a Video Output” page 181

10.6.3 “Inserting Embedded Audio into a Video Output” page 182

10.6.4 “Inserting MADI audio channels into a MADI Output” page 184

10.7 “Audio Channel-Swap” page 186

10.7.1 “Audio Channel-Swap in a Video Output” page 186

10.7.2 “Embedded Audio Channel-Swap in a Video Input” page 187

10.8 “System Application Example” page 189


Vega 30 Router User Manual Introduction Routing Use Cases 10.1

10.1 Introduction

Various use-case configurations are briefly outlined using diagrams. The nomenclature used to describe the how the Vega 30 Router’s video and audio crosspoints are used is shown in Figure 124.

Figure 124 Vega 30 Use Case Diagram Nomenclature for Crosspoints

Video with 16 channels of embedded audio

Router (video) inputs

MADI 64-channel audio

Switched Output

Switched Output

Router (MADI) inputs

Router (MADI) outputs

Router (video) outputs

Static RouteActively-switched sources routed to a destination

Video Crosspoint

Audio Crosspoint


Vega 30 Router User Manual Video-only Router Use Case Routing Use Cases 10.2

10.2 Video-only Router Use Case

Video routing with embedded audio:

In this use case, the Vega 30 Router is used for SDI video routing only, i.e. video with embedded audio. There is no separate audio routing and no audio processing required.

Example: Switching a SDI video signal from router port 2 to router output port 3.

Direct Video routing:

• Use RollCall Direct Video routing XY panel to make the routing: ‘destination 3 from source 2’.

Association Routing (Pre-defined video sources and destinations):

• Use RollCall Assoc routing XY panel to make the routing:‘destination 3 from source 2’.

or

• Use the Set Routes Web page to make the routing:‘destination 3 from source 2’.

Figure 125 Vega 30 Use Case - Video-only

Licenses required: None. (The Vega 30 is a basic 34 x 34 video-only router by default.)

Routing: • Association Routing (pre-defined video sources and destinations) over the video crosspoint.

or

• Direct Video routing control over the video crosspoint.

Video Crosspoint

Actively-switched output


Vega 30 Router User Manual MADI-only Router Use Case Routing Use Cases 10.3

10.3 MADI-only Router Use Case

Routing of MADI audio only:

In this use case, the Vega 30 Router is used for MADI audio routing only. No video routing, no audio embedding nor de-embedding.

Example: Switching a stereo pair:

• Audio channels 1 and 2 of MADI input 3 (audio channel sources 673 and 674);

to

• Audio channels 5 and 6 of MADI output 4 (audio channel destinations 741 and 742, destination port 47).

(See Table 61 in Appendix B on page 247 for port numbering. See Table 63 in Appendix C on page 250 for audio channel source/destination numbers.)


• Use RollCall Direct Audio routing XY panel to make the routing:

• ‘Destination 741 from channel source 673’.

and



• Create a user-defined source containing the source stereo pair in audio channels 5 and 6 and ‘null sources’ in other channels (for example, ‘MySrc 50’ below):

• Use either the RollCall ‘Assoc Routing’ XY panel or the Web ‘Set Routes’ page to make the routing:

• ‘Destination 47 from Source 50’.

Figure 126 Vega 30 Use Case - MADI-only

Licenses required: • Audio routing option, VG10-AR.

• No Video I/O options required.

Routing: • Association Routing or Direct Audio routing control over the audio crosspoint.

Audio Crosspoint

Actively-switched output

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

50 MySrc 50 - - - - - 673 674 - - - - - - - - - -


Vega 30 Router User Manual Video and MADI only router Routing Use Cases 10.4

10.4 Video and MADI only router

Video routing (with embedded audio) and separate MADI audio routing:

In this use case, the Vega 30 Router is used for video routing and MADI audio routing. There is no de-embedding nor embedding of audio channels.

See 10.2 “Video-only Router Use Case” and 10.3 “MADI-only Router Use Case”.

Figure 127 Vega 30 Use Case - Video and MADI only

Licenses required: • Video I/O options, as required.

• Audio routing option, VG10-AR.

Routing: • Association Routing with Pre-defined and User-defined audio sources and partial sources and destinations to control the video and audio crosspoints.

or

• Direct Video and Direct Audio routing control over the video and audio crosspoints respectively.

Video routing

MADI audio routing

Audio Crosspoint

Video Crosspoint


Vega 30 Router User Manual Monitoring a Router Input and Output Routing Use Cases 10.5

10.5 Monitoring a Router Input and Output

Router inputs can be monitored with the Vega 30 Router - including embedded audio.

Router outputs can be monitored with the Vega 30 Router - including embedded audio.

10.5.1 Monitor a Video Input

Produce a copy of the requisite Video Input at a router output and de-embed the audio to make a copy of the audio in a MADI output.

Example: Monitor video input 2 and an audio stereo pair (channels 7 and 8) embedded in it: This requires:

• Ensuring video input 2 signal is presented at a router output and all its embedded audio signals are presented to the audio crosspoint.

• De-embedding audio channels 7 and 8 of video input 2 (audio channel sources 23 and 24).

• Route de-embedded audio signals to audio channels 5 and 6 of MADI output 4 (audio channel destinations 741 and 742, destination port 47) for monitoring.


Figure 128 Vega 30 Use Case - Monitoring a Video Input - Copy Video and Copy Audio



Routing: • ‘Lock Route 1:1’ on the video crosspoint output corresponding to the Video Input to be monitored. Use fixed audio channel source numbers.

• Association routing. Use:

• Pre-defined video sources and destinations.

• User-defined audio sources and partial sources.

(Switched)

Copy of Video Input’s audio, for monitoring

De-muxed audio(Use fixed audio channel source numbers)

Video Input Copy of Video Input, for monitoring

Lock route using ‘Lock Route 1:1’

Video Crosspoint

Audio Crosspoint




1. In the RollCall Port Configuration template, enable ‘Lock Route’ for video output 2.

2. Use RollCall Direct Audio routing XY panel to make the routing:



The stereo pair appears in the MADI output.

Pre-defined video sources and destinations:

1. In the Port Configuration template, enable ‘Lock Route’ for video output 2.

2. Create a user-defined source containing only the monitored stereo pair in audio channels 5 and 6 and ‘null sources’ in other channels (for example, ‘MySrc 52’ below):

3. Use either the RollCall ‘Assoc Routing’ XY panel or the Web ‘Set Routes’ page to make the routing:


The stereo pair appears in the MADI output.

Router video output 2 is now a copy of router input 2, and may be used for video monitor-ing. The stereo audio channels from the router input allow the user to listen to channels 1 and 2 of the input regardless of other video routing.

10.5.2 Monitor Audio in a Router Video Output

De-embed some audio channels from a video output and route these out on a MADI channel for monitoring.

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

52 MySrc 52 - - - - - 23 24 - - - - - - - - - -

Figure 129 Vega 30 Use Case - Monitoring Audio in a Video Output

(Switched) Video Output

De-muxed audio

Monitored audio channels from the video output are routed to channels in a MADI output.

Audio Crosspoint

Video Crosspoint



Example: To monitor a stereo pair of a router video output:

• De-embed audio channels 1 and 2 of video output 3 (audio channel sources 33 and 34 of video output 3);

and

• Route these to audio channels 5 and 6 of MADI output 4 for monitoring(audio channel destinations 741 and 742, destination port 47).



• Use RollCall Direct Audio routing XY panel to make the routing:



Pre-defined video sources and destinations:

• Create a user-defined source (for example, ‘MySrc 51’ below) containing the monitored stereo pair in audio channels 5 and 6 and ‘null sources’ in other channels:



The stereo audio channels from the router output 3 allow the user to listen to channels 1 and 2 of whichever video signal is routed to router output 3.



Routing: • Association routing. Use:



• Direct Routing.

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

51 MySrc 51 - - - - - 33 34 - - - - - - - - - -



10.5.3 Monitor a Router Video Output

Produce a copy of a video output in the router for monitoring.

Figure 130 Vega 30 Use Case - Monitoring with a Copy Video Output


Routing: • Association routing. Use pre-defined video sources and destinations.

or Direct control over video crosspoint.

• Use the RollCall routing control the Edit Protect screen to ‘Destination Protect’ the two fixed routes for the switched output and the copy output.

(Switched) Video Output

Copy for monitoring

Two protected destinations

Re-entrant Switched Video

Switched Video

Router Video Output to be monitored

Video Crosspoint


Vega 30 Router User Manual Inserting Audio Channels into Router Inputs and Outputs Routing Use Cases 10.6

10.6 Inserting Audio Channels into Router Inputs and Outputs

Router inputs can have audio channels inserted into them with the Vega 30 Router.

Router outputs can have audio channels inserted into them with the Vega 30 Router.

10.6.1 Inserting MADI Audio into a Video Input

Embed MADI audio channels into a Video Input.

Figure 131 Vega 30 Use Case - Inserting Audio into a Video Input

(Switched)

MADI input with the audio channels for insertion

Video Input with inserted audio

Protected Destination

Video Input

Re-entrant Video with inserted audio

Locked 1:1 route using ‘Lock Route 1:1’

Insert

Audio to be inserted

Audio Crosspoint

Video Crosspoint



Routing: • ‘Lock Route 1:1’ on the video destination corresponding to the Video Input to have audio channels inserted into it. Use fixed audio channel source numbers.




• Use routing control screens to ‘Destination Protect’ the routes for the ‘insert audio channel’ destinations.



10.6.2 Inserting MADI Audio into a Video Output

Embed MADI audio channels into a Video Output.

Example: Insert MADI input 2 channels 1 and 2 into video output 23 embedded channels 5 and 6:

• This requires creating user-defined sources for routing to output 32.

• These sources should all have embedded audio channels 5 and 6 sourced from the same fixed MADI input channels.



1. Create user-defined sources containing an inserted stereo pair in audio channels 5 and 6 and ‘Follow video’ in other audio channels (for example, ‘MySrc 51’ to ‘MySrc 64’ below):

Figure 132 Vega 30 Use Case - Inserting Audio into a Video Output



Routing: • Association routing. Use:

• User-defined audio sources.

• Use routing control screens to ‘Destination Protect’ the fixed routes for the ‘insert audio channel’ destinations.

(Switched)


Switch Video Output with inserted audio

Audio Crosspoint

Video Crosspoint




• ‘Destination 32 from Source 51, 52, ... or 64.

The required MADI stereo pair appears in video output 2, whichever source is routed to the destination.

10.6.3 Inserting Embedded Audio into a Video Output

Embed audio channels from a Video Input into a Video Output.

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

51 MySrc 51 1DestThru

-1

DestThru

-2

DestThru

-3

DestThru

-4609 610

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16


-1

DestThru

-2

DestThru

-3

DestThru

-4609 610

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..


-1

DestThru

-2

DestThru

-3

DestThru

-4609 610

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16




Routing: • ‘Lock Route 1:1’ on the video destination corresponding to the Video Input containing the audio channels to be inserted. Use fixed audio channel source numbers.




(Switched)

Video Input containing the audio channels for insertion

Switch Video Output with inserted audio

Locked route using ‘Lock Route 1:1’

Audio Crosspoint

Video Crosspoint



Example: Insert embedded audio channels 1 and 2 on video input 2 into video output 32 embedded channels 5 and 6:

• This requires creating sources for routing to output 32 which all have embedded audio channels 5 and 6 sourced from the same fixed MADI input channels.



1. In the Port Configuration template, enable ‘Lock Route’ for video output 2.

2. Create user-defined sources containing an inserted stereo pair in audio channels 5 and 6 and ‘Follow video’ in other audio channels (for example, ‘MySrc 51’ to ‘MySrc 64’ below):



The required video input 2 stereo pair appears in video output 32 whichever source is routed to the destination.

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16


-1

DestThru

-2

DestThru

-3

DestThru

-417 18

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16


-1

DestThru

-2

DestThru

-3

DestThru

-417 18

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..


-1

DestThru

-2

DestThru

-3

DestThru

-417 18

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16



10.6.4 Inserting MADI audio channels into a MADI Output

Insert MADI audio channels into a MADI output.

Example: A stereo pair from MADI input 2 inserted into MADI output 4.


• Create a user-defined source to route a stereo pair of MADI input 2 to MADI output 4, channels 17 and 18 (for example, ‘MySrc 100’ below).

• Create user-defined sources to route required audio channels to MADI output 4, channels 17 to 32 (Destination port 48). (For example, ‘MySrc 101’ to ‘MySrc 103’ below: These all insert a stereo pair into their first two channels. MYSrc101 also routes 14 channels of MADI input 1; MySrc102 MADI input 2; and MySrc103 MADI input 3.)


Licenses required: • Audio routing option, VG10-AR.

Routing: • Use user-defined audio sources and partial sources.

• Use all partial sources to ensure the ‘Insert’ route is unaffected by any other audio routing to the destination.


(Switched)

Final switched MADI Output with inserted audio

‘Insert’ routeAudio Crosspoint

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

100 MySrc 100 - 623 624 - - - - - - - - - - - - - -

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16

101 MySrc 101 - 623 624 563 564 565 566 567 568 569 570 571 572 573 574 575 576

102 MySrc 102 - 623 624 627 628 629 630 631 632 633 634 635 636 637 638 639 640

103 MySrc 103 - 623 624 691 692 693 694 695 696 697 698 699 700 701 702 703 704




• ‘Destination 48 from Source 100’.The stereo pair appears in the MADI output. Other channels are unaffected.

• To route all 64 channels of MADI input 2 to MADI output 4 but insert the stereo pair, route:

• ‘Destination 47 from Source 39’. (First 16 channels of MADI output 4.)



• ‘Destination 50 from Source 42’. (Last 16 channels of MADI output 4.)

The MADI input 2 audio appears in MADI output 4 with an inserted stereo pair.


Vega 30 Router User Manual Audio Channel-Swap Routing Use Cases 10.7

10.7 Audio Channel-Swap

Audio channels can be swapped (shuffled) in router outputs with the Vega 30 Router.

10.7.1 Audio Channel-Swap in a Video Output

De-embed (de-mux) the embedded audio channels in a Video Output, swap audio channels around (shuffle) and re-embed onto Video Output.

Example: Swap embedded audio channels 5 and 6 on a video output.This requires:

• Creating a set of user-defined sources for routing to a video output.

• All user sources to have embedded audio channels 5 and 6 swapped.



1. Create user-defined sources containing a swapped stereo pair in audio channels 5 and 6, with ‘Follow video’ in other channels (e.g. ‘MySrc 51’ to ‘MySrc 64’ below):

Figure 135 Vega 30 Use Case - Audio Channel-Swap in a Video Output



Routing: • Use user-defined video and audio sources.

(Switched) Video Output with swapped audio channels

‘Swap’ routes

Swap

De-mux

Embed

Audio Crosspoint

Video Crosspoint

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-6

DestThru-5

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-6

DestThru-5

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-6

DestThru-5

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

Swapped Channels





The required video input stereo pair is swapped in video output 32.

10.7.2 Embedded Audio Channel-Swap in a Video Input

De-embed (de-mux) the embedded audio channels in a Video Output, swap audio channels around (shuffle) and re-embed onto Video Output.

Example: Swap embedded audio channels 5 and 6 on video input 7: This requires:

• Creating a set of user-defined sources for routing to a video output.

• All user sources to have all embedded audio channels unswapped, EXCEPT for the case of video input 7, which requires channels 5 and 6 to be defined as swapped.



1. Create user-defined sources containing ‘Follow video’ channel sources:

• a swapped stereo pair in audio channels 5 and 6 for video input 7;

• and corresponding channels in other audio channels.

(For example, ‘MySrc 51’ to ‘MySrc 64’ below, where ‘MySrc 57’ only has swapped audio channels, see below.)

Figure 136 Vega 30 Use Case - Audio Channel-Swap in a Video Input



Routing: Use:


• User-defined video and audio sources for ‘Swap’ destination.

(Switched) Video Output with swapped audio channels

‘Swap’ routes for one video input only

Swap

De-mux

Embed

Audio Crosspoint

Video Crosspoint





The required video input stereo pair is swapped at video output 32 only when video input 7 is routed there with ‘MySrc 57’.

User-defined Source

Video Source


No. Name Vid. 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-6

DestThru-5

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

.. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. .. ..


-1

DestThru

-2

DestThru

-3

DestThru

-4

DestThru

-5

DestThru

-6

DestThru

-7

DestThru

-8

DestThru

-9

DestThru-10

DestThru-11

DestThru-12

DestThru-13

DestThru-14

DestThru-15

DestThru-16

Channels swapped for one video input only


Vega 30 Router User Manual System Application Example Routing Use Cases 10.8

10.8 System Application Example

This application example aims to show how a Vega 30 Router may be used in an audio/video system. A target video system is presented which contains a variety of audio and video sub-systems. This is then implemented with a Vega 30 Router in the following sections.

10.8.1 Target System Diagram

A target system is shown in Figure 137.

The system comprises:

• Video and audio sources, each feeding a mixer.

• Embedded audio sources can be accessed and used.

• Audio channels on inputs or outputs may be swapped.

• Audio can be inserted into sources or into outputs.

• An audio mixer provides various audio signals for the system.

• A vision mixer produces a program video channel and various copies and versions.

• Feeds are taken to/from some external studio.

• An auxiliary processing unit can be optionally included into a signal path.

• System is monitored with a multiviewer unit and audio analyzer.

Figure 137 Vega 30 Use Case, Target System Diagram



The target system is now extended with added video and audio monitor points. Additionally, various signal nodes are labelled to assist in the following sections. This is shown in Figure 138

All the system functions shown in grey boxes in Figure 138 can be implemented by the Vega 30 Router.

Figure 138 Vega 30 Use Case, Extended Target System Diagram



10.8.2 System Implementation with Vega 30 Router

An implementation of the extended target system using a Vega 30 Router is shown in Figure 139 on page 191.

Figure 139 shows the main system components of Figure 138 connected to a Vega 30 Router.

The Vega 30 Router itself implements some of the target system’s functionality, including:

• Audio de-embedding.

• Audio channel shuffling.

• Audio embedding.

• Monitor routing infrastructure required.

Figure 140 shows how a Vega 30 Router’s architecture may be used for the system implementation.

Figure 139 Vega 30 Use Case, System Application Diagram using a Vega 30 Router



Figure 140 Vega 30 Use Case, System Application Example - Vega-30 Configuration



The numbers and letters in circles in Figure 140 relate back to node points in Figure 138 on page 190.

Figure 140 shows an example of how a Vega 30 Router may be used in our system application use case.

Description:

For video signals in the system:

• Video sources (1) re-enter the router (2) to allow any audio operations on inputs

to be done.

• There are signals to/from a studio (3) and a video processing unit (4).

• Four signals (5) pass to a quad-split multiviewer unit for video monitoring.

• Eight signals (6) go to a vision mixer; two signals return, PST (7) and PGM (9).

• PST and PST copy output signals are produced (8).

• PGM signal from the mixer (9) re-enters the router (10) to allow audio operations to be done.

• A final PGM output and a PGM copy (11) are produced.

• Two alternate PGM outputs (12) and then re-enter the router to allow de-embedding of audio for monitoring purposes. The final alternate PGM outputs (13) are available.

For audio in the system:

• Audio sources (1) are routed to an audio mixer (2).

• Mixed audio (3) is available to be embedded into video outputs or routed to MADI output audio channels.

• All program audio is available on a MADI output (4).

• A feed to/from a studio is present (5) and (6).

• A 64-channel MADI output (7) is available for monitoring purposes.

• De-embedding and embedding - (a) , (d), (c), (d), (e) and (g) - is done within the router on router outputs.

• Any audio routing and shuffling - (b) and (f) - is done in the audio crosspoint.


Vega 30 Router User Manual Vega 30 Rear Connections Summary Getting Started 11.1

11 Getting Started

This section guides the user through the steps required to control signal routing in a Vega 30 Router using a PC. The Vega 30 Router unit’s web page is used.

Please refer to other sections of this User Manual for detailed information. In particular to:

• Section 4 “Chassis and Connectors etc.” on page 31.

• Section 5 “Installation” on page 41.

• Section 6 “Vega 30 Web Interface” on page 45.

11.1 Vega 30 Rear Connections Summary

Figure 141 Vega 30 Router Rear Panel

MADI Outputs(HD-BNC)

Reference(HD-BNC)

“PSU”DC Power Inlets

Ethernet

Video Inputs1-34

(HD-BNC)


MADI Inputs 1 to 3(HD-BNC)

Video Outputs1-34

(HD-BNC)

13

57

24

68 . . . . . . . . . . . . 32

34

. . . . . . . . . . . . . . . 3133 1

35

7 . . . . . . . . . . . . . . . . 3133

24

68 . . . . . . . . . . . . . . . 32

34

1 2 3

3546

21


Vega 30 Router User Manual Initial Powering and Starting Up Getting Started 11.2

11.2 Initial Powering and Starting Up

The Vega 30 Router may be powered from one or two Vega 30 PSU modules.

1. Connect DC power cable(s) from the external Vega 30 PSU module(s) to the Vega 30 Router unit.

See Figure 141 for the location of the DC Power Inlets at the rear of the Vega 30 unit.

2. Connect the external Vega 30 PSU modules to an AC mains supply.

3. Turn on the AC mains to the Vega 30 PSU modules.

The Vega 30 unit starts up and the front System LED is Blue. See Figure 142a.Starting up may take up to 3 minutes.

4. When unit start up is complete, the front System LED will show either of the following:

• Flashes green - system started up OK. See Figure 142b.

• Flashes red - started up OK, but no Ethernet connection. See Figure 142c.Typically, at this stage, there will not yet be an Ethernet connection.

Note: The Vega 30 Router unit has two DC power connectors. These are for up to two separate, external Vega 30 power supply modules, which each have an IEC mains power socket.

Note: The mains supply voltage will be auto-detected by the external power supply modules, provided it is in the range 100 - 240 Vac and 50 / 60 Hz.

Important: Always ensure that the:

• Vega 30 Router unit is properly earthed.

• Power connections are correctly made.

Note: Front ‘PSU’ LEDs while starting up:

The ‘PSU 1’ and ‘PSU 2’ front LEDs show the status of DC power at each rear DC power inlet of the Vega 30 Router:

• Green - PSU fitted.

• Red - PSU not fitted.


Vega 30 Router User Manual Initial Powering and Starting Up Getting Started 11.2

5. If the front LEDs indicate another condition, first refer to Section 4.4 “Front Panel Status Indicators” on page 33 for full information on all LED states.

If required, contact your local SAM representative for further support. Contact details can be found by visiting www.s-a-m.com/support/247-support-contact-details.

11.2.1 Disconnecting Power to Vega 30

When a Vega 30 Router has to be powered down, carry out the following procedure:

1. Disconnect both external Vega 30 PSU’s from AC mains supplies.

2. Disconnect both DC power cables from the rear of the Vega 30 Router.

Figure 142 Front System LED Flashes Blue while upgrading. (Example is for Vega 30 fitted with two PSUs)

a) Vega 30 Router starting up. b) Vega 30 Router started OK. c) Vega 30 Router no Ethernet.

(For the full description of all Vega 30 Router front LED states, see Section 4.4 “Front Panel Status Indicators” on page 33.)


Vega 30 Router User Manual Preliminary Vega 30 Router Configuration Getting Started 11.3

11.3 Preliminary Vega 30 Router Configuration

The Vega 30 Router unit initially requires some network settings to be set up. The network settings may be set up via either of the following unit interfaces:

• Web Interface- see Section 6 “Vega 30 Web Interface” on page 45.

or

• RollCall Control Panel- see Section 7 “Vega 30 RollCall Templates” on page 100.

Here, the Web interface is used to describe the preliminary configuration procedure.

You will require:

• A PC with a network port configured with a static IP address on the same sub-net as the Vega 30 Router unit (255.255.0.0). Do not use the same IP address as the router default IP address, 192.168.0.101.

• A standard CAT 5 network cable. (Older PCs may require a cross-over network cable instead.)

Procedure:

1. Connect the CAT5 network cable to the RJ45 “Ethernet” port on the rear of the Vega router. (The Vega 30 Router rear connectors are shown in Figure 141.)

2. Connect the other end of the CAT5 cable to the PC’s configured network port.

3. Open a web browser on the PC.

4. Enter the default IP address of the Vega 30 Router, 192.168.0.101. The Vega 30 Router home page displays, see Figure 143.

5. Check that the license status reflects the license options purchased.

Figure 143 Vega 30 Home Page

License StatusNavigation panel


Vega 30 Router User Manual Preliminary Vega 30 Router Configuration Getting Started 11.3

6. Click ‘Configuration’ in the home page’s navigation side-bar.The Configuration Web page is shown.

On the Configuration Web page:

7. Make network settings changes as required for the Vega 30 Router and your house network. (I.e. Vega 30 Router IP address, Sub-net mask, Gateway IP address, and DNS server 1 and 2 IP addresses.)

8. Set the ‘PSU Fitted’ setting to match the PSU configuration to be used. (I.e. ‘PSU 1 fitted only’, ‘PSU 2 fitted only’, or ‘Both fitted’.)

9. Click Apply.

10. Click Restart Unit.

The Vega 30 Router restarts.

11. Disconnect the Vega 30 Router from the PC.

When the Vega 30 Router has restarted, the new settings have taken effect and the Vega 30 Router is ready to be installed in a rack and then connected to using its new IP address etc.

12. Power down the unit and install in an equipment rack. It requires a shallow, 3RU high rack-space.

13. Earth the unit’s chassis using the Chassis Ground Point, see Figure 141 on page 194.


System Network settings

PSU Fitted setting

Apply button

Restart Unit button


Vega 30 Router User Manual Connections Getting Started 11.4

11.4 Connections

Refer to Figure 141 on page 194 for a diagram of the Vega 30 Router rear connectors.

Make the following connections:

11.5 Initial Configuration

Procedure:

1. Power up the Vega 30 Router unit.

2. When the unit has fully started up, check the front LEDs. See Figure 145.

3. Connect to the unit’s Home Web page using its new IP address on your house network with a browser.

The unit’s Home page should be displayed in your browser window.

Rear Connector Connect to

DC Power Inlets DC Power from Vega 30 PSU module(s).

Ethernet RJ45 House network.

Reference HD-BNC House analogue video reference signal. Terminate the signal with the rear ‘Term’ slide switch.

Input HD-BNC Video signal input feeds from video sources.

Output HD-BNC Video signal outputs to video equipment.

MADI IN HD-BNC MADI audio signal input feeds from audio sources.

MADI OUT HD-BNC MADI audio signal outputs to audio equipment.

Table 58 Power and Signal Connections

Figure 145 Vega 30 Router Powered Up - Front Panel LEDs

a) PSU 1 fitted only. b) PSU 2 fitted only. c) Both PSU 1 and 2 fitted.

Flashing green System LED, at 2 Hz.


Vega 30 Router User Manual Initial Configuration Getting Started 11.5

4. On the Home page, check the status of:

• PSU 1 and PSU 2.

• Fan status is OK.

• Check that the standard of the video reference signal is shown in the Reference Standard box.

The unit is now ready to be initially configured.

5. Click ‘Source Names’ in the navigation panel.The Source Names Web page is shown and the Input Ports table is visible.

6. In the Input Ports table, for each of the connected video inputs:

• Select a video standard to use when switching to that input.

• Set up any 4K Source ports.

Figure 146 shows a sample screenshot of the Input Ports table.

7. Click Apply to apply the changes.

Figure 146 Sample Source Names Page - Input Ports Table


Vega 30 Router User Manual Initial Configuration Getting Started 11.5

8. Click ‘Destination Names’ in the navigation panel. The Destinations Web page is shown.

9. In the Destinations Web page:

• Set up any 4K destinations.

Figure 147 shows a sample screenshot of a Destinations table.

10. Click Apply to apply any changes.

The Vega 30 Router unit is ready to do some basic video routing.

Figure 147 Sample Destinations Page


Vega 30 Router User Manual Basic Video Routing Getting Started 11.6

11.6 Basic Video Routing

1. Click ‘Set Routes’ in the navigation panel on the Home Web page. The Set Routes Web page is shown. See Figure 148.

2. Inspect the blue Destinations buttons. These show:

• name of the Destination,

• and the name of the Routed Source to the destination.

See Figure 149.

Figure 148 Set Routes Web Page (Showing Factory Source Names)

Figure 149 Destination Buttons

Destination name

Routed Source name



To route video source 1 (the default name is “V.In 1”) to video destination 2 (the default name is “V.Out 2”):

3. Click Destination button “V.Out 2” to select the destination.Then click Source button “V.In 1” to select the next source (pre-selected source).

The destination button is highlighted along with the corresponding currently-routed source button. The pre-selected source button is also highlighted. See Figure 150.

4. Click Take to make the route.The route is made and the Web page refreshes to show the new route to the destination. See Figure 151.

Video source 1 is routed to video destination 2.

Figure 150 Pre-selecting a Source

Destination

Currently-Routed Source

Pre-selected Source



Figure 151 Route Taken

Destination

Newly-Routed Source


Vega 30 Router User Manual Basic MADI Audio Routing Getting Started 11.7

11.7 Basic MADI Audio Routing

To carry out any audio routing within the Vega 30 Router, the VG10-AR license is required.

1. Firstly, look at the Home page to check the audio routing license, VG10-AR, is present.

2. Click ‘Set Routes’ in the navigation panel. The Set Routes Web page is shown. See Figure 152.

The blue Destinations buttons and green Source buttons are labelled, indicating a destination or an (associated) source name.

At this stage, the names shown will be default ones. The form of the names varies depending on whether the source or destination is a router input port or output port or a user-defined source.

Figure 152 Set Routes Page (Factory Source Names are Shown)



Buttons Source/Destination Type Default Name

8 character 32 character

Destinations 1 to 34 Video outputs V.Out n Video Output n

Destinations 35 to 58 MADI Audio output A.Out nA,A.Out nB,A.Out nC,A.Out nD

Audio Output nA,Audio Output nB,Audio Output nC,Audio Output nD

See Note 1.

Sources 1 to 34 Video inputs V.In n Video Input n See Note 2.

Sources 35 to 46 MADI Audio input A.In nA,A.In nB,A.In nC,A.In nD

Audio Input nA,Audio Input nB,Audio Input nC,Audio Input nD

See Note 1.

Sources 47 to 500 User-defined source Src n Source n

Note 1: The Vega 30 Router MADI inputs and outputs each have 64 audio channels.Each input or output is divided up into four groups of 16 audio channels.Each 16-channel group is assigned to be a source or a destination for the router.

Such source or destination names have ‘A’, ‘B’, ‘C’ and ‘D’ suffices:

‘A’: MADI Audio channels 1 to 16.

‘B’: MADI Audio channels 17 to 32.

‘C’: MADI Audio channels 33 to 48.

‘D’: MADI Audio channels 49 to 64.

Note 2: Default source names ‘V.In n’ do refer to router video inputs 1 to 34.

However, audio channel source names ‘V.In n-m’ (used in user-defined sources) refer to audio channels at video crosspoint outputs.

Table 59 Associated Source and Destination Port Names



To route audio channels 1-16 of MADI input 1 (“A.In 1A”) to channels 49-64 of MADI output 2 (“A.Out 2D”):

3. Click Destination button “A.Out 2D” to select the destination.Click Source button “A.In 1A” to select the next source.

The destination button is highlighted and the corresponding currently-routed Source button. The next, pre-selected Source button is highlighted. See Figure 153.


Audio channels 1-16 of MADI input 1 are now routed to channels 49-64 of MADI output 2.

Figure 153 Pre-selecting a MADI Source

Pre-selected Source

Routed Source

Destination

Figure 154 MADI Route Taken

Newly-Routed Source

Destination



To route all audio channels of MADI input 1 (i.e. channels 1 to 64) to MADI output 2 (channels 1 to 64), make four audio routes:

1. Click Destination button “A.Out 2A”. Click Source button “A.In 1A”.

Click Take.

2. Click Destination button “A.Out 2B”. Click Source button “A.In 1B”.

Click Take.

3. Click Destination button “A.Out 2C”. Click Source button “A.In 1C”.

Click Take.

4. Click Destination button “A.Out 2D”. Click Source button “A.In 1D”.

Click Take.

After these four routes have been made, all channels of MADI input 1 are routed to MADI output 2.


Vega 30 Router User Manual MADI Stereo Pair Audio Routing Getting Started 11.8

11.8 MADI Stereo Pair Audio Routing

Example: Route audio channels 3 and 4 of MADI input 1 to audio channels 5 and 6 of MADI output 3.

Our routing example requires the routing of:

• audio channels 3 and 4 of MADI input 1 - i.e. audio channel sources “A.In 1A-3” and “A.In 1A-4”.

to

• audio channels 5 and 6 of MADI output 3- i.e. to destination “A.Out 3A”.

Procedure:

1. Go to the Vega 30 Router Home Web page to check the VG10-AR audio routing license (VG10-AR) is present.

In order to be able to route one or more specific audio channels in the Vega 30 Router, a user-defined source (i.e. one of source numbers 47 to 500) needs to be defined.

To define a user-defined source for a MADI stereo pair:

2. Click ‘Source Names’ in the navigation panel.The Source Names Web page is shown, with the Input Ports table visible.

3. Scroll down the page to view the Source Names table. See Figure 155.

Note: To carry out any audio routing within the Vega 30 Router, the VG10-AR license is required.

Figure 155 Source Names Page - Source Names Table



Now define source 47, a user-defined source, in row 47:

4. Go down to row 47 in the table. See Figure 155.

Figure 156 Source Names Table - Row 47

Audio channel source columns Audio 1, Audio 2, .. .. , Audio 16.



5. Enter the values shown in Figure 157 into columns “Audio 5” and “Audio 6” for Source 47.

4. Click the Apply button in Row 47.

A ‘choose the video’ dialog is shown. See Figure 158.

5. Do not select any associated video source for our example, just click Reset and then click Apply at the bottom of the dialog.

6. Now click Apply at the top of the Source Names web page.

Figure 157 Source Names Table - Entering Audio Channel Sources in Row 47

1. Enter ‘A’ into a table cell.

2. This produces a drop-down list of audio channel source names to select from.

3. Select the name required. If the name is not visible, continue to type it in.



This has defined user-defined source 47. When Source 47 is routed to a destination, it will overwrite the 5th and 6th audio channels of the destination.

To complete our routing example:

7. Click ‘Set Routes’ in the navigation panel. The Set Routes Web page is shown.

8. Select destination “A,Out 3A”.Select source “Src 47”. See Figure 159.




Figure 159 Pre-selecting Source 47

Pre-selected Source Routed Source

Destination



9. Click Take to make the route.

The route is made and the Web page refreshes to show the new route to the destination. See Figure 160.

Audio channels 3 and 4 of MADI input 1 are now routed to channels 5 and 6 of MADI output 3. Other audio channels of MADI output 3 are unaffected.

Figure 160 Source 47 Route Taken

Newly-Routed Source

Destination


Vega 30 Router User Manual Embed a MADI Stereo Audio Pair into a Video Output Getting Started 11.9

11.9 Embed a MADI Stereo Audio Pair into a Video Output

Example: The requirement is to embed audio channels 3 and 4 of MADI input 1 (audio channel sources “A.In 1A-3”,“A.In 1A-4”) into audio channels 5 and 6 of Video input 1 when Video input 1 is routed to Video output 3.

Procedure:

1. Go to the Vega 30 Router Home Web page to check the VG10-AR audio routing license (VG10-AR) is present.

In order to be able to route one or more specific audio channels in the Vega 30 Router, a user-defined source (i.e. one of source numbers 47 to 500) needs to be defined.

To define a user-defined source for a MADI stereo pair:

2. Click ‘Source Names’ in the navigation panel.The Source Names Web page is shown, with the Input Ports table visible.

3. Scroll down the page to view the Source Names table. Now define source 48, a user-defined source, in row 48:

4. Go down to row 48 in the table. See Figure 161.

5. Enter the following values shown in Figure 161 in columns “Audio 5” and “Audio 6”

Note: To carry out any audio routing within the Vega 30 Router, the VG10-AR license is required.


Audio channel source columns Audio 1, Audio 2, .. .. , Audio 16.



6. Click the Apply button in the Source 48.

A ‘choose the video’ dialog is shown. See Figure 164.

7. Click Apply at video input 1 to select video input 1 for our user-defined source.

The video input 1 name appears at the top of the dialog.

8. Then click Apply at the bottom of the dialog.

The dialog closes. The names of video input 1 appear on row 48.

The video source column of the Source 48 row is now filled out.

9. Click Apply at the top of the Source Names web page to now apply this user-defined source change. A green “Changes have been made” message briefly appears in on the Web page. See Figure 163.


(Refer to Figure 157)

• Enter ‘A’ into a table cell.This produces a drop-down list of audio channel source names to select from.

• Select the name required. Continue to type in until name is in the drop-down list.

Figure 163 ‘Apply to Save User-Defined Source definition



The new Source 48 is now ready for use.

Source 48 comprises video input 1 with modified audio changes 5 and 6, embedded from MADI input 1. This has defined user-defined source 48. When it is routed to a destination, it will overwrite the 5th and 6th audio channels.

To complete our routing example:

10. Click ‘Set Routes’ in the navigation panel. The Set Routes Web page is shown.

11. Select destination “V,Out 3” (Video output 3).Select source “Src 48”. See Figure 165.


Click Apply to select Video Input 1 in the dialog.

Lastly, click Apply to close the dialog



Figure 165 Pre-selecting Source 48

Pre-selected Source Routed Source

Destination


Vega 30 Router User Manual Output Video Signal Timing Getting Started 11.10


Video input 1 is now routed to Video output 3, along with all of its embedded audio channels, except embedded audio channels 5 and 6 in output 3, which are replaced by audio channels 3 and 4 from MADI input 1.

11.10 Output Video Signal Timing

Output signal timing is described in Section 8 “Output Video Timing - Line Sync and Offset” on page 154. And the set up procedure is given in Section 8.4 “Setting Up Router Offset” on page 160.

Figure 166 Source 48 Route Taken

Newly-Routed Source

Destination

Note: Output disruption and Vega 30 Router starting:

While the Vega 30 Router unit starts up or restarts, there may be disruption to the video outputs. This is normal: The unit starts by routing ‘1 to 1’ inputs to outputs and only adopts the last know routing settings once the control software has successfully started up.


Vega 30 Router User Manual Power Supply Module Replacement Maintenance 12.1

12 Maintenance

12.1 Power Supply Module Replacement

Power supply status is indicated on the Vega 30 front panel. See Section 4.4 “Front Panel Status Indicators” on page 33. The front status LEDs indicate which Vega 30 Power Supply Module is faulty.

If the Vega 30 unit is being run with two Power Supply Modules, then replacement of one Power Supply Module may be done with the Vega 30 powered on.

To replace a Vega 30 Power Supply Module:

1. Disconnect the Power Supply Module from its AC mains power supply.

2. Disconnect the Power Supply Module’s DC power cord from the Vega 30 unit.

3. Connect the replacement Power Supply Module’s DC power cord to the Vega 30 unit.

4. Connect the Power Supply Module to the AC mains power supply.

5. Turn on the AC mains supply.

The Power Supply Module has been replaced.

• Refer to safety information in Section 2 “Safety” on page 8 Section 2 “Safety” on page 8

• The installation and maintenance of the Vega 10 Series router(s) and any associated equipment must be carried out by persons qualified to work with equipment which may be connected to a mains electric supply.

Note: Ensure you have a replacement Vega 30 Power Supply Module before starting this procedure. SAM Order Code: VG30-PSU.


Vega 30 Router User Manual Airflow Cooling Fan Assembly Replacement Maintenance 12.2

12.2 Airflow Cooling Fan Assembly Replacement

Fan status is indicated on the Vega 30 front panel. See Section 4.4 “Front Panel Status Indicators” on page 33.

In the case of fan failure, the unit should be powered down immediately.

Depending on the length of time the Vega 30 Router has been running with no fan, the unit may need to be returned for checking and repair. Contact SAM or your SAM dealer to discuss the situation.

To replace the cooling fan:

1. Disconnect both of the unit’s Power Supply Modules from any AC mains supply.The unit is now not powered.

2. Unscrew the two M3 fan assembly retaining screws and keep them for refitting. See Figure 167a.

3. Detach the fan assembly from the unit and disconnect the fan’s multi-way internal connection from the fan header within the unit, located on the unit’s internal main board. See Figure 167b.

4. Remove the fan assembly from the unit.

Replace and refit the fan assembly:

5. Bring the new fan assembly up to the Vega 30 unit.And connect the fan’s multi-way connector to the fan multi-way header on the unit’s main board. Take care to orient the connector for the header. See Figure 167b.

6. Secure the fan housing with the two fan assembly retaining screws. Tighten the screws.

The fan assembly has been replaced.Powering on the unit after fan assembly replacement:

7. Connect the unit’s Vega 30 Power Supply Module(s) to AC mains supplies. Turn on the mains power.The Vega 30 unit starts up.

8. Check that the fan is working.

9. Wait for the unit to finish starting up and the front System indicator indicates that the unit is ready.

10. Check that the front Fan status indicator indicates that fan status is OK.

The fan has been replaced and the unit is running again.

If the cooling fan on the Vega 30 Router should stop for any reason, then the unit should be switched off immediately. Otherwise permanent damage may result.

Note: Required Items:

Before starting this replacement procedure, the items required are:

• M3 Pozi-drive screwdriver.

• Replacement Vega-30 fan assembly before starting this procedure, SAM Order Code: VG30-FAN.


Vega 30 Router User Manual Airflow Cooling Fan Assembly Replacement Maintenance 12.2

Figure 167 Vega 30 Router Fan Assembly:a) Rear Fan Assembly and Retaining Screws. b) Fan Multi-way Connection.c) Fan Assembly Removed and Fan Multi-way Header. d) Fan Multi-way Header.

Fan AssemblyRetaining screws Fan multi-way internal connection

d) Fan Multi-way Header

a) Vega 30, Rear Fan Assembly and Retaining Screws b) Fan Multi-way Internal Connection

c) Fan Assembly Removed and Fan Multi-way Header

Fan multi-way connector

Fan multi-way header

Fan multi-way headerInternal SD card and socket. For Engineering Use Only.


Vega 30 Router User Manual Software Upgrade Maintenance 12.3

12.3 Software Upgrade

This section describes upgrading the Vega 30 Router software over the network.

A software upgrade package from SAM is supplied by SAM Support and comprises a .zip file, approximately 25M bytes in size (RouterRelease.zip). Do not unzip the .zip file.

The upgrade package is associated with a Vega 30 software release, for example, v2.0.1.

12.3.1 Checking Software Version on a Vega 30 Unit

The software version number can be checked via a Vega 30 web page or a RollCall template.

12.3.1.1 Checking Software Version via Web Page

• Enter the IP address of the Vega 30 into a browser.The Home page is displayed. The unit’s software version is shown. See Figure 168.

12.3.1.2 Checking Software Version via RollCall Control Panel

• Connect to the unit with RollCall Control Panel.Unit software version is shown in the Unit Information template. See Figure 185.

Figure 168 Vega 30 Home Web Page - Software Version

License Status section

Figure 169 Vega 30 RollCall Unit Information Template - Software Version

Software version



12.3.2 Software Upgrade Procedure (with SAM RollCall Control Panel)

The Vega 30 software upgrading process follows the standard process for equipment upgrades with SAM RollCall Control Panel. For more details, please see the RollCall Control Panel User Manual.

Upgrade installation is a two-stage process:

• Stage 1: Add the upgrade package to RollCall Control Panel. See “Stage 1: Add Upgrade Package to RollCall” on page 225.

• Stage 2: Install the upgrade on the Vega 30 unit.See “Stage 2: Install the Upgrade on the Vega 30 Unit” on page 227.

These are described in the sub-sections below.

Note: Use RollCall Control Panel version v4.17.25 or later.

Note: Vega 30 software downgrades may also be carried out with the same procedure.



12.3.2.1 Stage 1: Add Upgrade Package to RollCall

1. From RollCall Control Panel, connect to the Vega 30 unit.

2. Click the Import New Upgrades icon, see Figure 170.

3. The RollCall Upgrade Packages window is displayed. See Figure 171.

4. Click the Import Upgrade Package button and navigate to the folder containing the upgrade package.

5. Click Open to open the folder.Navigate to the upgrade .zip file.

6. Click on the .zip file name (see Figure 172) to select it.Click OK.

7. A progress bar at the bottom of the RollCall Upgrade Packages window shows the progress of the upgrade package importing.

Figure 170 Import New Upgrades Icon

Figure 171 Upgrade Packages Window

Figure 172 Select Upgrade Package Window



Import completion is reported in the Import Log pane. See Figure 173.

The upgrade package has been added to RollCall Control Panel.

Now proceed to Stage 2, see Section 12.4.4.3 “Stage 2: Install License on the Vega 30 Unit” on page 239.

Figure 173 Import Log Pane in RollCall Upgrade Packages Window

Progress bar

Import Log pane



12.3.2.2 Stage 2: Install the Upgrade on the Vega 30 Unit

Next, upgrade the software on the Vega 30 unit:

8. Right-click on the connected Vega 30 name in the RollCall window. Click Unit Upgrade. See Figure 174.

RollCall’s Unit Upgrade window is displayed. See Figure 175.

Figure 174 Right-Click Menu

Figure 175 Unit Upgrade Window

Software Releases drop-down box

Upgrade button



9. In the Software Release drop-down box, select the required Software Release in the pull-down menu. See Figure 176.

10. Click the Upgrade button.

A dialog is displayed, see Figure 177.

11. Click OK.

12. A Unit Upgrade dialog message is displayed. See Figure 178.

13. Click No in response to the question: “Do you wish to save the current version before upgrading?” (Figure 178)

An Upgrade Confirmation dialog is displayed. See Figure 178.

Figure 176 Unit Upgrade Window - Software Release Selected

Figure 177 Unit Upgrade Window - Software Release Selected

Figure 178 Unit Upgrade Dialog

Note: The Vega 30 unit does not support saving of current software version. Click No in response to the message box shown in Figure 178.

Figure 179 Upgrade Confirmation Dialog



14. Click OK to proceed with the unit upgrade.

The upgrade file is then sent to the Vega 30 unit and the Vega 30 unit starts to install the software upgrade.

The upgrade installation can take up to 5 minutes to complete; the last action is for the unit to perform a restart.

During the upgrade installation process:

• The front System LED flashes blue.

• Messages are written into the Upgrade Log section of the Unit Upgrade window as the upgrade proceeds. See Figure 181.

Figure 180 Front System LED Flashes Blue while upgrading. (Example is for Vega 30 configured for one PSU)



The final Upgrade Log message reads “Upgrade Complete“, see Figure 181. After this, the Vega 30 Router unit performs a restart.

Figure 181 Upgrade Log Messages as Upgrade Proceeds

Upgrade Log

a) Upgrade Log Messages written into

window

“Clock” File Progress indicator

b) Upgrade Proceeds c) Upgrade finalizes



For the final upgrade step, the Vega 30 unit restarts itself.

The whole upgrade takes about 5 minutes. During this time, the unit will not communicate with RollCall Control Panel.

15. Wait for the unit to complete its restart. Wait for the Vega 30 front panel LEDs to indicate ‘System OK’ status - flashing green ‘System’ LED. (Front panel LED colors are described in Section 4.4 “Front Panel Status Indicators” on page 33.)

This means the unit has completed its upgrade installation and is ready for use.

See Figure 183.

Figure 182 Unit Upgrade Window - Final Upgrade Log Message before Unit Restart

Important: Wait for the Vega 30 module unit to finish restarting:

After the upgrade package file is received by the Vega 30 unit, the Vega 30 unit begins to install the individual upgrade files etc. The unit can take up to 5 minutes to do this. The final step is a Vega 30 restart.

The Vega 30 unit is only fully ready for use after it has restarted and the front panel status LEDs indicate ‘system OK’. (See Section 4.4 “Front Panel Status Indicators” on page 33.)



16. Check that the Vega 30 front LEDs indicate ‘System OK.’This means the unit restarted and is running.

(For a full description of front LEDs, see Section 4.4 “Front Panel Status Indicators” on page 33.)

If this is not the case, contact SAM Support.

When the Vega 30 unit has restarted successfully and SAM RollCall Control Panel has reconnected to the unit, the RollCall Vega 30 Unit Information screen shows the upgraded software version. See Figure 184.

Figure 183 Front System LED Flashes Green when starting is complete and system is OK. (Example is for Vega 30 configured for one PSU)



The unit software upgrade is complete.

Figure 184 Upgraded Software Version Reported on RollCall Template


Vega 30 Router User Manual Installing a License Maintenance 12.4

12.4 Installing a License

A Vega 30 license can be installed in the following ways:

• Vega 30 Web interface.

• Vega 30 RollCall Control Panel.

The available licenses are listed in:

• Section 3.2 “Order Codes” on page 16;

• and in Section 3.2 “Order Codes” on page 16.

All licenses are tied to an individual Vega 30 unit via its Ethernet MAC address. The license’s MAC address must match the MAC address of the unit.

12.4.1 To View License Status on a Vega 30 Unit

1. Enter the IP address of the Vega 30 into a browser.The home page is displayed.

2. The unit’s license status is shown. See Figure 185.

Alternatively, the license status of the unit can be viewed in the unit’s RollCall System Information template. See Figure 186.

Figure 185 Vega 30 Home Web Page - License Status




Figure 186 Vega 30 RollCall System Information Template - License Status




12.4.2 To Obtain a License

1. Note the serial number and ethernet MAC address of the Vega 30 Router.

(The serial number and ethernet MAC address information is available on the unit’s Home web page, see Figure 187.)

2. Determine which Vega 30 license(s) are required. (Licenses are listed in Section 3.2 and Section 3.2.)

3. Contact your SAM Sales Office to arrange purchase and delivery of the license file.

Licenses are supplied as a Zip File. Do not un-zip before installation.

Figure 187 Vega 30 Home Web Page - MAC Address and Vega 30 Serial Number

MAC address

Serial number

Note: Do not unzip the license file.



12.4.3 Installing a License via the Vega 30 Web Page

Licenses are installed from a license zip file.

1. Enter the IP address of the Vega 30 into a browser.The home page is displayed.

2. Navigate to the Configuration page. See Figure 188.

3. In the Import License File section,click Browse and browse to the supplied license zip file (stored on your PC or network storage).

4. When the license zip file is selected, click Import in the Import License File section.

5. The license will be installed.

6. To check that the license has installed, view the unit’s Home page, see Section 12.4.1 “To View License Status on a Vega 30 Unit” on page 234.


Import License File section

Import buttonBrowse button



12.4.4 Installing a License via RollCall Control Panel

The process of adding a license to a Vega 30 unit follows the standard process for a product with licenses administered by SAM RollCall. For more details, please see the RollCall Control Panel User Manual.

Licenses are installed from a license zip file. This license must have been generated specifically for the Vega 30 unit. (The unit’s MAC address is used in the license information.)

License installation via RollCall is a two-stage process:

• Stage 1: Add the license file to RollCall Control Panel.

• Stage 2: Install license on the Vega 30 unit.

These are described in the sub-sections below.

12.4.4.1 Preliminaries

• Check the version of RollCall Control Panel being used is valid for Vega 30 units, see Section A.15 “Software Compatibility” on page 245 for the version number.

• Run RollCall Control Panel on a PC connected to the network.

• Power up the Vega 30 unit and connect to the same network.

12.4.4.2 Stage 1: Add License to RollCall Control Panel

1. From RollCall Control Panel, connect to the Vega 30 unit.

2. Click the Edit Licenses icon or click Edit > Licenses.The License Viewer window is displayed.

3. Click on the Vega 10 tab.Available licenses in RollCall are listed.

Figure 189 shows an empty Vega 10 tab.

4. Click Import Licenses.

5. Navigate to the license zip file and select the file name. Click OK.The imported license is added to the listed licenses on the Vega 10 tab.See Figure 190.

Figure 189 License Viewer Window

Import licenses button



The license is now added to RollCall Control Panel.

Proceed to stage 2.

12.4.4.3 Stage 2: Install License on the Vega 30 Unit

The next stage is to install the license on the Vega 30 unit itself.

6. Navigate to the Vega 30 unit in the RollCall Control Panel navigation pane.

7. Right-click on the connected Vega 30 unit name and click Unit License.See Figure 191.

Figure 190 Added License

Added license

Figure 191 Right-Click Unit License



8. The Unit License window is displayed, which shows current licenses and available licenses for the unit (the MAC addresses are the same). See Figure 192.

9. Select the available license to be installed by clicking the adjacent radio button.

10. Click Install License

11. Click Yes to install the license.The license is installed on the Vega 30 and the Vega 30 restarts.Click OK.

12. Restarting takes approximately 1 minute.

When the Vega 30 finishes restarting, it is operating with the newly-installed license. This can be checked by viewing either the unit’s Home Web page or the unit’s RollCall System Information template.

Figure 192 Unit License


Vega 30 Router User Manual Physical Specifications A.1

Appendix A Specifications

A.1 Physical

A.2 Operating Environment

A.3 Compliance

A.4 Electrical

A.4.1 Vega 30 Unit

Physical Vega 30

Ports 34x34

Mounting height 3RU

Dimensions See Appendix B “Vega 30 Router Dimensions” on page 61

Weight: Vega 30 Unit:

1.3 kg (2.9 lb)

Power Supply Modules: (Up to 2-off required)

0.5 kg (1.1 lb) each

Operating Environment

Operating temp 5°C to 40°C

Storage temp -20 to +80°C

Relative Humidity 5% to 95% non-condensing

Ventilation Fan assisted. Front inlet, rear exhaust

Compliance

EMC - Emissions EN55103-1 (EU), FCC Part 15 (USA)

EMC - Immunity EN55103-2 (EU)

Safety EN60950 (EU), UL1419 (USA)

Hazardous Material RoHS-6 (UK) – Complies with EU Directive

Vega 30 Unit

Power Connector 2x 4-way mini-DIN socket

Power Consumption 84 W max

Voltage 12 V DC

Current 7 A max

Fuses

Vega 30 unit No user-serviceable fuses.


Thread ISO M4

Thread Depth Max. 20 mm


Vega 30 Router User Manual Signal Inputs Specifications A.5

A.4.2 Vega 30 Power Supply Modules

A.5 Signal Inputs

A.6 Signal Outputs

AC Inlet

AC Inlet Connector IEC 320-C14

Voltage 100 to 240 V ac, 50 / 60 Hz

Current Max. 2 A

Fuses

Vega 30 PSU Module None.

DC Output

DC Output Connector 4-way mini-DIN

Voltage 12 V dc

Current Min. 8.33 A

Video Inputs

Number and Type 34-off. HD-BNC

Impedance 75 R

Amplitude 800 mV nominal

DC offset <5 V

Return loss >15 dB: 10 MHz to 1.5 GHz >10 dB: 1.5 GHz to 3.0 GHz

Cable equalization Automatic. For Belden 1694A:

SD: 350 m (1150 ft)

HD: 200 m (650 ft)

3G: 140 m (460 ft)

Standards SD-SDI/ HD-SDI/ 3G-SDI:

• SD-SDI @ 525i59.94 & 625i50

• HD-SDI @ 720p50, 720p59.94& 720p60

• HD-SDI @ 1080i50, 1080i59.95 & 1080i60

• 3G-SDI @ 1080p50, 1080p59.94 & 1080p60

UHD support via Quad 3G-SDI.

Other standards (not including DVB-ASI) will pass.

MADI Audio Inputs


Impedance 75 R

Signals MADI to AES-1048 kHz sampling rate.56 or 64 channel modes.

Video Outputs



Vega 30 Router User Manual Reference Inputs Specifications A.7

A.7 Reference Inputs

A.8 Timed Switching

Impedance 75 R

Amplitude 800 mV ±10% pk-pk

DC offset 0 V ±0.5 V

Return loss >15 dB: 10 MHz to 1.5 GHz >10 dB: 1.5 GHz to 3.0 GHz typical

Rise / fall time SD: <650 psHD: <180 ps 3G: 90 ps

Timing jitter HD, 3G: <0.25 UISD: <0.15 UI

Alignment jitter HD, 3G: <0.15 UI SD: <0.1 UI

Standards SD-SDI/ HD-SDI/ 3G-SDI

MADI Audio Outputs


Impedance 75 R

Amplitude 800 mV ±10% pk-pk

Signals MADI to AES-1048 kHz sampling rate.64 channel modes.

Video Outputs

Reference Inputs

Number and Type 1-off looped HD-BNC. Auto-detection.

Impedance 75 ±0.1% or high Impedance (switched on rear panel)

Return Loss > 28 dB (0 - 10 MHz)

Signals 1 V pk - pk Analog Video/Syncs/Tri-level HD Syncs

Timed Switching

Switching Lines To SMPTE RP-168-2009:

Line 10 (525),

Line 6 (625),

Line 7 (HD),

Line 7 (3G).

Requires a reference input.Without a reference input, the unit will crash switch.

Progressive references cannot be used for interlaced signal switching timings.

Timed-switching only supported for a single frame rate at any one time. I.e. with a 50 Hz reference, 59.94 Hz and 60 Hz signals cannot be timed-switched.


Vega 30 Router User Manual Audio V-Fade Rates Specifications A.9

A.9 Audio V-Fade Rates

Note: V-Fade needs to be enabled on an output-by-output basis.

A.10 Built-in Audio Test Tone Generator

A.11 Router Ports

A.12 Control and Status

A.13 Default IP Address

A.14 RollCall ID Numbers

V-Fade RateDuration

(Fade out to fade in)

Fast 160 ms

Medium 400 ms

Slow 1000 ms

Audio Channel Source

Test Tone Description

737 Tone 1 979.6 Hz tone.

738 Tone 2 24 kHz tone.

739 Left Id Single Occult.

740 Right Id Double Occult.

741 Silence Silence.

Note: Channel status reports Origin as Vega.

Video Router Size

Size 34 x 34

MADI Audio

Size 3 in x 6 out(I.e. 3 x 64 audio channels in) x (6 x 64 audio channels out)

Audio Router Size

Size 741 x 928

Control and Status

Ethernet Connection

Ethernet Connectors 1 x RJ45

10/100/1000 Base-T autosense

Protocol SAM SW-P-02 over Ethernet support SAM SW-P-08 over Ethernet supportSNMP

IP Address

Default IP Address 192.168.0.101


Vega 30 Router User Manual Software Compatibility Specifications A.15

A.15 Software Compatibility

ID ID Number

Controller 824

Routing Matrix 636

Assoc Routing 837

Direct Video routing 837

Software

SAM RollCall suite(Includes RollCall Control Panel)

v4.15.52 or later

RollCall Control Panel v4.17.25 or later

Note: It is not possible to install licenses and upgrade software etc on Vega 30 units with earlier versions of RollCall Control Panel.


Vega 30 Router User Manual Source and Destination Port Numbering

Appendix B Source and Destination Port Numbering

Table 60 lists the video port source and destination numbers and Table 61 lists the MADI port source and destination numbers.

Router Video Input PortSource Number

Router Video Output PortDestination

Number

Video Input 1 1 Video Output 1 1


































Router Video Input Port Source Router Video Output Port DestinationTable 60Vega 30 Router - Video Source and Destination Port Numbering


Vega 30 Router User Manual Source and Destination Port Numbering

Router MADI Input Port

Audio Channels

Source Number

Router MADI Input Port Audio

ChannelsDestination

Number

MADI Input 1 1 to 16 35 MADI Output 1 1 to 16 35












Router MADI Source MADI Output 4 1 to 16 47

MADI Output 4 17 to 32 48











Router MADI DestinationTable 61Vega 30 Router - MADI Source and Destination Port Numbering


Vega 30 Router User Manual Audio Channel Source and Destination Names and Numbers

Appendix C Audio Channel Source and Destination Names and Numbers

It is useful to refer to Figure 8 on page 24 when reading this appendix. The figure is reproduced below for information only.

The audio crosspoint makes no distinction between Audio de-mux sources, MADI input sources and internal sources when specifying audio channel sources. Similarly with audio destinations.

For the audio crosspoint, audio channels are simply organized in a flat array. The dimensions of the array are ‘Number of Sources’ x ‘Number of Destinations’.

The audio sources and destinations include:

• Sources:

• All video crosspoint output Audio de-mux channels. (1 to 544)

• Three MADI inputs. (545 to 736)

• Internal sources.

• Destinations:

• Audio for re-embedding into all video outputs. (1 to 544)

• Six MADI outputs. (545 to 928)

Figure 193 Vega 30 Audio Routing Diagram (Recap of Figure 8 on page 24)


Vega 30 Router User Manual Audio Crosspoint - Overview of Source and Destination Numbers Audio Channel Source and Desti-

Note: Audio channel sources that have been de-embedded (de-multiplexed) from internal video are all ‘post-video-crosspoint’.

Special ‘Follow Video’ internal virtual audio channel sources are provided by Vega 30 to automatically select embedded audio from a routed video source. There are 16 ‘Follow Video’ audio channel sources. These have source numbers, but do not form part of the physical audio crosspoint size.

The audio channel source and destination numbering is summarized in Table 62 and fully-listed in Table 63 along with the default audio channel source names.

C.1 Audio Crosspoint - Overview of Source and Destination Numbers

Source Numbering Destination Numbering

Source Numbers

Description Destination Numbers

Description

1 1

Audio channels (de-multiplexed from internal

video crosspoint outputs)(34x16)

Audio channels(for multiplexing into video outputs)

(34x16)

544 544

545 545

MADI Inputs (3x64)

MADI Outputs(6x64)

736

737

Internal Audio Test Signals

740

741 Audio Silence

742

Internal virtual sources(‘Follow Video’)

757

928

Table 62 Audio Crosspoint - Overview of Source and Destination Numbers


Vega 30 Router User Manual Table of Audio Source and Destination Names and Numbers Audio Channel Source and Destination

C.2 Table of Audio Source and Destination Names and Numbers

Audio Crosspoint

Audio Channel Source Numbering Audio Destination Numbering

Source Number

Factory Name

(see Notes 1, 2)

Description

(see Note 3)

Destination Number

Description

1 V.In 1-1 Video Xpt Out 1.1 1 Video Output 1.1






















Note 1: Factory audio channel source names (e.g. “V.In n-m” etc) are over-witten by user source names.

Note 2: Factory audio channel source name “V.In n-m” does not refer to an audio channel from a video input. Rather, “V.In n-m” is an audio channel from an output of the video crosspoint.

Note 3: Where:

Video Xpt Out is internal to the Vega 30 Router and is the output of the video crosspoint.

Video Xpt Out 1 is video crosspoint output 1.

Video Xpt Out 1.N is the Nth embedded audio channel in video crosspoint output 1.

MADI Input 1.N is the Nth audio channel in MADI input 1.

Video Output 1.N is the Nth embedded audio channel in the Vega 30 Router’s video output 1.

MADI Output 1.N is the Nth audio channel in MADI output 1.

Table 63 Audio Crosspoint Channel Source and Destination Names and Numbers



























Audio Crosspoint


Source Number

Factory Name

(see Notes 1, 2)

Description

(see Note 3)

Destination Number

Description



Note 3: Where:







Table 63 Audio Crosspoint Channel Source and Destination Names and Numbers (Continued)



























Audio Crosspoint


Source Number

Factory Name

(see Notes 1, 2)

Description

(see Note 3)

Destination Number

Description



Note 3: Where:






















545 A.In 1A-1 MADI Input 1.1 545 MADI Output 1.1


561 A.In 1B-1 MADI Input 1.17 561 MADI Output 1.17


577 A.In 1C-1 MADI Input 1.33 577 MADI Output 1.33


593 A.In 1D-1 MADI Input 1.49 593 MADI Output 1.49






Audio Crosspoint


Source Number

Factory Name

(see Notes 1, 2)

Description

(see Note 3)

Destination Number

Description



Note 3: Where:






















737 979.6Hz Audio Test Tone (979.6 Hz) 737 MADI Output 4.1

738 24KHz Audio Test Tone (24 kHz) 752 MADI Output 4.16

739 LeftId Audio Test Tone (Left Id) 753 MADI Output 4.17

740 RightId Audio Test Tone (Right Id) 768 MADI Output 4.32

741 Silence Silence 769 MADI Output 4.33

742 DestThru-1 “Follow video”, emb. audio ch 1 784 MADI Output 4.48

743 DestThru-2 “Follow video,” emb. audio ch 2 785 MADI Output 4.49






Audio Crosspoint


Source Number

Factory Name

(see Notes 1, 2)

Description

(see Note 3)

Destination Number

Description



Note 3: Where:















754 DestThru-13 “Follow video,” emb. audio ch 13 880 MADI Output 6.16




912 MADI Output 6.48



Audio Crosspoint


Source Number

Factory Name

(see Notes 1, 2)

Description

(see Note 3)

Destination Number

Description



Note 3: Where:









Vega 30 Router User Manual Audio Channel Source Names Diagram Audio Channel Source and Destination Names and

C.3 Audio Channel Source Names Diagram

Finally, the audio channel source names of Table 63 are shown annotated on a Vega 30 crosspoint diagram in Figure 194.

Figure 194 Vega 30 Audio Channel Source (Factory) Names

1 = V.In 1-1

16 = V.In 1-16

17 = V.In 2-1

529 = V.In 34-1

544 = V.In 34-16

545 = A.In 1A-1

560 = A.In 1A-16

561 = A.In 1B-1

577 = A.In 1C-1

593 = A.In 1D-1

608 = A.In 1D-16

609 = A.In 2A-1

673 = A.In 3A-1

736 = A.In 3D-16

737 = 979.6Hz

738 = 24KHz

739 = LeftId

740 = RightId

741 = Silence

742 = DestThru-1

757 = DestThru-16

743 = DestThru-2

744 = DestThru-3

Access embedded audio channels of video inputs: Access (fixed) de-embedded audio channels:


Vega 30 Router User Manual Introduction SNMP MIB Files for the Vega 30 Router D.1

Appendix D SNMP MIB Files for the Vega 30 Router

D.1 Introduction

A mib file is used to manage devices in a network usually for the Simple Network Management Protocol (SNMP). Mib files represents the device, in this case a Vega 30 Router, and describes it for SNMP.

SAM mib files can be downloaded from https://s-a-m.com/support/protocols-and-mibs/.

To use the full SNMP features of the Vega 30 Router, two mib files are required:

• Probel-Common

• Vega30Router

The files are listed below.

D.2 MIB Support

The Vega30Router.mib supports the following functionality, based on SNMP V2 format (see the MIB file for details of values returned):

• Traps:

• Fan Status

• PSU 1, PSU 2

• Destination Protect

• Destination Client Name

• Destination Routed Source

• Get (read only):

• Application version, Application description, Application copyright, Application build date

• FPGA Number (A, B, C & Z), FPGA Firmware Revision (A, B, C & Z)

• Network MAC Address

• Unit Serial Number

• VG10-CSA, VG10-CSB, VG10-CSC, VG10-AR License status

• Fan Status, Fan Speed

• PSU1, PSU2 Status

• Unit Temperature

• Reference Standard

• Input Information

• Output Information

• Line sync offset

• Table of Sources

• Get/Set (Read/Write):

• Audio V-Fade rates for FPGA A, B & C

• Input Standard

• 4K Input selection

• Route Lock

• Line Sync Enable/Disable, Line Sync Line offset, Line Sync Pixel offset

• 4K output selection

• V-Fade Enable/Disable

• Source 8-Character & Source 32-Character names


https://s-a-m.com/support/protocols-and-mibs/

Vega 30 Router User Manual MIB Support SNMP MIB Files for the Vega 30 Router D.2

• Destination 8-Character & Destination 32-Character names

• Route Source to Destination

• Destination Protect, Destination Protect State

• Routing table

• Audio Routing

• Vega30 Unit Name

• Location of Device

• System Contact

• Unit IP address, Sub-Net, Gateway, Primary DNS & Secondary DNS

• PSU1 & PSU 2 connection status

• SWP-02 Port number & Protocol enable

• SWP-08 Port number & Protocol enable

• RollCall Port number & Protocol enable

• Log Server Enable, Name & Long Names

• SNMP Enable, Community Name for Get, Community Name for Set, Community name for Traps

• SNMP IP address of Trap Manager

• RTC Enable, Server & Timezone


Vega 30 Router User Manual File listing: PROBEL-COMMON.mib SNMP MIB Files for the Vega 30 Router D.3

D.3 File listing: PROBEL-COMMON.mib

---- PROBEL-COMMON.MIB-- MGL 10-08-02 V 1.00--

PROBEL-COMMON DEFINITIONS ::= BEGIN

IMPORTS

OBJECT-GROUPFROM SNMPv2-CONF

enterprises, OBJECT-TYPE, Integer32 FROM SNMPv2-SMI

DisplayString, TimeInterval, RowStatus, StorageType, TruthValue FROM SNMPv2-TC;

---- Textual conventions--

ControllerStatus ::= TEXTUAL-CONVENTIONSTATUS currentDESCRIPTION

"In a dual-redundant pair of controllers one isactive and one idle. The idle controller will fail any PDUs associated with router status or control."

SYNTAX INTEGER{controllerActive(1),controllerIdle(2)}

RouterTerminal ::= TEXTUAL-CONVENTIONSTATUS currentDESCRIPTION

"Source or destination number"SYNTAX INTEGER (1..4096)

RouterTerminalName ::= TEXTUAL-CONVENTIONSTATUS currentDESCRIPTION

"Source or Destination name"SYNTAX OCTET STRING (SIZE (0..8))

---- Node definitions--

probelLtd OBJECT IDENTIFIER ::= { enterprises 6419 }

probel OBJECT IDENTIFIER ::= { probelLtd 1 }

probelProducts OBJECT IDENTIFIER ::= { probel 1 }

-- Add product OIDs in here

-- probelSiriusRouter OBJECT IDENTIFIER ::= { probelProducts 1 }

-- probelHaloRouter OBJECT IDENTIFIER ::= { probelProducts 2 }

-- End product OIDs

probelModules OBJECT IDENTIFIER ::= { probel 2 }

END ---- PROBEL-COMMON.MIB--

End of PROBEL-COMMON.MIB file.


Vega 30 Router User Manual File listing: Vega30Router.mib SNMP MIB Files for the Vega 30 Router D.4

D.4 File listing: Vega30Router.mib

Vega30Router DEFINITIONS ::= BEGIN

IMPORTS probelProducts FROM PROBEL-COMMON

Integer32, Unsigned32, Gauge32, Counter32, Counter64, Opaque, TimeTicks, IpAddress, OBJECT-TYPE FROM SNMPv2-SMI

DisplayString FROM SNMPv2-TC;

vega30Router MODULE-IDENTITYLAST-UPDATED "201701060000Z"ORGANIZATION "Snell Advanced Media"CONTACT-INFO "[email protected]"DESCRIPTION "This MIB contains the information on the Vega30 Router Control"

::= { probelProducts 4 }

BooleanFT ::= TEXTUAL-CONVENTION STATUS current DESCRIPTION "Represents a boolean value." SYNTAX INTEGER { false(0), true(1) }

routerStatus OBJECT IDENTIFIER ::= { vega30Router 1 }

statusVersion OBJECT IDENTIFIER ::= { routerStatus 1 }

versionApplication OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The application version"::= { statusVersion 1 }

versionName OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The application name"::= { statusVersion 2 }

versionDescription OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The application description"::= { statusVersion 3 }

versionCopyright OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The application copyright"::= { statusVersion 4 }

versionBuildDate OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The application build date"::= { statusVersion 5 }

versionFPGANumberA OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA A number"::= { statusVersion 11 }

versionFPGANumberB OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA B number"::= { statusVersion 12 }

versionFPGANumberC OBJECT-TYPESYNTAX DisplayString



MAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA C number"::= { statusVersion 13 }

versionFPGANumberZ OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA Z number"::= { statusVersion 14 }

versionFirmwareRevA OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA A firmware revision"::= { statusVersion 21 }

versionFirmwareRevB OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA B firmware revision"::= { statusVersion 22 }

versionFirmwareRevC OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA C firmware revision"::= { statusVersion 23 }

versionFirmwareRevZ OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The FPGA Z firmware revision"::= { statusVersion 24 }

versionMacAddress OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The network MAC address"::= { statusVersion 31 }

versionSerialNumber OBJECT-TYPESYNTAX DisplayStringMAX-ACCESS read-onlySTATUS currentDESCRIPTION "The unit's serial number"::= { statusVersion 32 }

statusLicenses OBJECT IDENTIFIER ::= { routerStatus 2 }

licenseCSA OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates the status of license VG10-CSA"::= { statusLicenses 1 }

licenseCSB OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates the status of license VG10-CSB"::= { statusLicenses 2 }

licenseCSC OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"Indicates the status of license VG10-CSC"::= { statusLicenses 3 }

licenseAR OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-only



STATUScurrentDESCRIPTION"Indicates the status of license VG10-AR"::= { statusLicenses 4 }

statusPSU OBJECT IDENTIFIER ::= { routerStatus 3 }

statusPSU1 OBJECT-TYPESYNTAXUnsigned32 { psuOK(0), psuFault(1), psuNotFitted(2) }MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"{{poll}} The status of PSU 1"::= { statusPSU 1 }

statusPSU2 OBJECT-TYPESYNTAXUnsigned32 { psuOK(0), psuFault(1), psuNotFitted(2) }MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"{{poll}} The status of PSU 2"::= { statusPSU 2 }

statusFan OBJECT-TYPESYNTAXUnsigned32 { fanOK(0), fanProblem(1), fanFail(2) }MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"{{poll}} The status of the fan"::= { routerStatus 4 }

statusFanSpeed OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"{{poll}} The fan speed"::= { routerStatus 5 }

statusTemperature OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"{{poll}} The internal temperature"::= { routerStatus 6 }

routerDevice OBJECT IDENTIFIER ::= { vega30Router 2 }

routerGeneral OBJECT IDENTIFIER ::= { routerDevice 1 }

systemReferenceStandard OBJECT-TYPE SYNTAXUnsigned32 { stdNoSignal(0), stdSD625(1), stdSD525(2), stdHD720P50(3), stdHD720P59(4), stdHD720P60(5), stdHD1080I50(6), stdHD1080I59(7), stdHD1080I60(8), stdHD1080P50(9), stdHD1080P59(10), stdHD1080P60(11), stdOther(12) }

ACCESSread-onlySTATUScurrentDESCRIPTION"{{poll}} The reference standard for all inputs, read from h/w"::= { routerGeneral 1 }

inputTable OBJECT-TYPESYNTAXSEQUENCE OF InputEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"An array containing the information on all the inputs"

::= { routerDevice 2 }

inputEntry OBJECT-TYPESYNTAXInputEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This is the record that contains the input specific information"INDEX { inputIndex }::= { inputTable 1 }

InputEntry ::=SEQUENCE {

inputIndex Unsigned32,inputStandard Unsigned32,

input4K Unsigned32}

inputIndex OBJECT-TYPESYNTAXUnsigned32ACCESSnot-accessibleSTATUScurrent



DESCRIPTION"Auto-generated index parameter for the array"::= { inputEntry 101 }

inputStandard OBJECT-TYPE SYNTAXUnsigned32 { stdNoneOther(0), stdSD625(1), stdSD525(2), stdHD720P50(3), stdHD720P59(4), stdHD720P60(5), stdHD1080I50(6), stdHD1080I59(7), stdHD1080I60(8), stdHD1080P50(9), stdHD1080P59(10), stdHD1080P60(11) }

MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The input standard"::= { inputEntry 1 }

input4K OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Specifies the first input in a 4K group, or 0 for single input"::= { inputEntry 2 }

outputTable OBJECT-TYPE

SYNTAXSEQUENCE OF OutputEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"An array containing information on all outputs"

::= { routerDevice 3 }

outputEntry OBJECT-TYPESYNTAXOutputEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"This is the record that contains the output specific information"INDEX { outputIndex }::= { outputTable 1 }

OutputEntry ::=SEQUENCE {

outputIndex Unsigned32, outputLockRoute BooleanFT, outputEnableLineSync BooleanFT, outputLineOffset Unsigned32, outputPixelOffset Unsigned32, output4K Unsigned32, outputStandard Unsigned32, outputEnableVFade BooleanFT, outputVFade Unsigned32

}

outputIndex OBJECT-TYPESYNTAXUnsigned32ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Auto-generated index parameter for the array"::= { outputEntry 101 }

outputLockRoute OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This indicates if a route should be locked on this output"::= { outputEntry 1 }

outputEnableLineSync OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This enables/disables line sync on this output"::= { outputEntry 2 }

outputLineOffset OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This sets the line offset for synchronisaton of this output"::= { outputEntry 3 }

outputPixelOffset OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This sets the pixel offset for synchronisaton of this output"



::= { outputEntry 4 }

output4K OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"Specifies the first output in a 4K group, or 0 for single output"::= { outputEntry 5 }

outputStandard OBJECT-TYPE

SYNTAXUnsigned32 { stdNoSignal(0), stdSD625(1), stdSD525(2), stdHD720P50(3), stdHD720P59(4), stdHD720P60(5), stdHD1080I50(6), stdHD1080I59(7), stdHD1080I60(8), stdHD1080P50(9), stdHD1080P59(10), stdHD1080P60(11), stdOther(12) }

MAX-ACCESSread-onlySTATUScurrentDESCRIPTION"The output signal standard read from the hardware"::= { outputEntry 6 }

outputEnableVFade OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This enables/disables vfade on this output"::= { outputEntry 7 }

outputVFade OBJECT-TYPESYNTAXUnsigned32 { fast(0), medium(1), slow(2) }MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The output signal reference type read from the hardware"::= { outputEntry 8 }

sources OBJECT IDENTIFIER ::= { routerDevice 4 }

sourceTable OBJECT-TYPESYNTAXSEQUENCE OF SourceEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A table of all the sources"::= { sources 1 }

sourceEntry OBJECT-TYPESYNTAXSourceEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A source record"INDEX { sourceIndex }::= { sourceTable 1 }

SourceEntry ::=SEQUENCE {

sourceIndex Unsigned32,sourceName8 DisplayString,sourceName32 DisplayString}

sourceIndex OBJECT-TYPESYNTAXUnsigned32ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Auto-generated index parameter for the array"::= { sourceEntry 101 }

sourceName8 OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The 8 character name for this source"::= { sourceEntry 1 }

sourceName32 OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The 32 character name for this source"::= { sourceEntry 2 }

sourceComponentTable OBJECT-TYPESYNTAXSEQUENCE OF SourceComponentEntryMAX-ACCESSread-only



STATUScurrentDESCRIPTION"None"::= { sources 2 }

sourceComponentEntry OBJECT-TYPESYNTAXSourceComponentEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"None"INDEX { sourceComponentSourceIndex, sourceComponentIndex }::= { sourceComponentTable 1 }

SourceComponentEntry ::=SEQUENCE {

sourceComponentSourceIndex Unsigned32,sourceComponentIndex Unsigned32,sourceComponent Unsigned32}

sourceComponentSourceIndex OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSnot-accessibleSTATUS currentDESCRIPTION"Auto-generated index parameter for the array"::= { sourceComponentEntry 101 }

sourceComponentIndex OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSnot-accessibleSTATUS currentDESCRIPTION"Auto-generated index parameter for the array"::= { sourceComponentEntry 102 }

sourceComponent OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSread-writeSTATUS currentDESCRIPTION"The input number for the specified source and component"::= { sourceComponentEntry 1 }

dests OBJECT IDENTIFIER ::= { routerDevice 5 }

destTable OBJECT-TYPESYNTAXSEQUENCE OF DestEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"An array of destinations"::= { dests 1 }

destEntry OBJECT-TYPESYNTAXDestEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"A record contained information on a destination"INDEX { destIndex }::= { destTable 1 }

DestEntry ::=SEQUENCE {

destIndex Unsigned32,destName8 DisplayString,destName32 DisplayString,

destRoutedSource Unsigned32, destClientName DisplayString, destProtectStateandDevice Unsigned32

}

destIndex OBJECT-TYPESYNTAXUnsigned32ACCESSnot-accessibleSTATUScurrentDESCRIPTION"Auto-generated index parameter for the array"::= { destEntry 101 }

destName8 OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The 8 character name for this destination"::= { destEntry 1 }



destName32 OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"The 32 character name for this destination"::= { destEntry 2 }

destRoutedSource OBJECT-TYPESYNTAXUnsigned32MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This parameter is used to indicate the source that is routed to this

destination. By writing to this parameter a crosspoint can be set"

::= { destEntry 3 }

destClientName OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"If a protect has been set on this destination this object holds the name

of the client protecting this destination"::= { destEntry 4 }

destProtectStateandDevice OBJECT-TYPESYNTAXUnsigned32 { ptNotProtected(0) }MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"This object indicates both the destination protected state and the Device

ID"::= { destEntry 5 }

directRouting OBJECT IDENTIFIER ::= { routerDevice 6 }

videoRoutingTable OBJECT-TYPESYNTAXSEQUENCE OF VideoRoutingEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"None"::= { directRouting 1 }

videoRoutingEntry OBJECT-TYPE

SYNTAXVideoRoutingEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"{{index1=DirectVideo}}"INDEX { videoRoutingIndex }::= { videoRoutingTable 1 }

VideoRoutingEntry ::=SEQUENCE {

videoRoutingIndex Unsigned32,videoRoutingUnsigned32}

videoRoutingIndex OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSnot-accessibleSTATUS currentDESCRIPTION"Auto-generated index parameter for the array"::= { videoRoutingEntry 101 }

videoRouting OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSread-writeSTATUS currentDESCRIPTION"The encoded input and component routed to this output and component"::= { videoRoutingEntry 1 }

audioRoutingTable OBJECT-TYPESYNTAXSEQUENCE OF AudioRoutingEntryMAX-ACCESSread-onlySTATUScurrentDESCRIPTION"None"::= { directRouting 2 }

audioRoutingEntry OBJECT-TYPE

SYNTAXAudioRoutingEntryMAX-ACCESSread-only



STATUScurrentDESCRIPTION"{{index1=DirectAudio}}"INDEX { audioRoutingIndex }::= { audioRoutingTable 1 }

AudioRoutingEntry ::=SEQUENCE {

audioRoutingIndex Unsigned32,audioRouting Unsigned32}

audioRoutingIndex OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSnot-accessibleSTATUS currentDESCRIPTION"Auto-generated index parameter for the array"::= { audioRoutingEntry 101 }

audioRouting OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSread-writeSTATUS currentDESCRIPTION"The flat audio index representing any source audio on this destination

audio"::= { audioRoutingEntry 1 }

------------------------------------------------------------------------------- Vega30 Router configuration settings - as in the Config.json file

routerConfig OBJECT IDENTIFIER ::= { vega30Router 3 }

configGeneral OBJECT IDENTIFIER ::= { routerConfig 1 } routerName OBJECT-TYPE

SYNTAXDisplayString ACCESSread-write STATUScurrent DESCRIPTION"[[General/ControllerName]] The name of the Vega30 Router" ::= { configGeneral 1 }

configLocation OBJECT-TYPESYNTAXDisplayString MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[General/Location]] Location of the device"::= { configGeneral 2 }

configSystemContact OBJECT-TYPESYNTAXDisplayString MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[General/SystemContact]] System contact for administration"::= { configGeneral 3 }

-- Router IP Address settingsunitNetwork OBJECT IDENTIFIER ::= { routerConfig 2 }

unitIPAddress OBJECT-TYPESYNTAXIpAddressACCESSread-writeSTATUScurrentDESCRIPTION"[[Network/UNIpAddress]] The IP Address of the Router"::= { unitNetwork 1 }

unitIPSubNet OBJECT-TYPESYNTAXIpAddressACCESSread-writeSTATUScurrentDESCRIPTION"[[Network/UNIpSubNet]] The IP SubNet Address of the Router"::= { unitNetwork 2 }

unitIPGateway OBJECT-TYPESYNTAXIpAddressACCESSread-writeSTATUScurrentDESCRIPTION"[[Network/UNIpGateway]] The IP Gateway Address of the Router"::= { unitNetwork 3 }

unitPriDNSAddress OBJECT-TYPESYNTAXIpAddress



MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Network/UNIpPriDnsAddress]] The primary DNS Address of the

Router"::= { unitNetwork 4 }

unitSecDNSAddress OBJECT-TYPESYNTAXIpAddressMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Network/UNIpSecDnsAddress]] The secondary DNS Address of the

Router"::= { unitNetwork 5 }

-- Vega 30 PSU usage psu OBJECT IDENTIFIER ::= { routerConfig 4 }

psuNumber OBJECT-TYPESYNTAXUnsigned32 { both(0), psu1Only(1), psu2Only(2)}MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[PSU/Number]] This object indicates which of the PSUs are

connected to the router"::= { psu 1 }

-- Vega 30 Control Protocol Settings

protcolSettings OBJECT IDENTIFIER ::= { routerConfig 5 }

-- General Switcher (SW-P-02) settings swp02GeneralSwitcher OBJECT IDENTIFIER ::= { protcolSettings 1 }

swp02PortNumber OBJECT-TYPESYNTAXUnsigned32 MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SWP02/Port]] This Port number used for protocol clients"::= { swp02GeneralSwitcher 1 }

swp02Enable OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SWP02/Enable]] This indicates if the protocol is enabled"::= { swp02GeneralSwitcher 2 }

-- General Remote (SW-P-08) settings swp08GeneralRemote OBJECT IDENTIFIER ::= { protcolSettings 2 }

swp08PortNumber OBJECT-TYPESYNTAXUnsigned32 MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SWP08/Port]] This Port number used for protocol clients"::= { swp08GeneralRemote 1 }

swp08Enable OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SWP08/Enable]] This indicates if the protocol is enabled"::= { swp08GeneralRemote 2 }

-- RollCall settings rollCall OBJECT IDENTIFIER ::= { protcolSettings 3 }

rollCallEnable OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCall/Enable]] This indicates if the protocol is enabled"::= { rollCall 1 }

rollCallSharePortNumber OBJECT-TYPESYNTAXUnsigned32 MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCall/SharePort]] This Port number used for protocol clients"::= { rollCall 2 }

rollCallAnyLogServer OBJECT-TYPE



SYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCall/AnyLogServer]] This indicates if any log server is

enabled"::= { rollCall 3 }

rollCallLogServerName OBJECT-TYPESYNTAXDisplayString MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCall/LogServerName]] This is the name of the RollCall log

server"::= { rollCall 4 }

rollCallUseLongNames OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCall/LongNames]] This indicates if the use of Long Names is

enabled"::= { rollCall 5 }

-- RollCall+ settings rollCallPlus OBJECT IDENTIFIER ::= { protcolSettings 4 }

rollCallPlusEnable OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCallPlus/Enable]] This indicates if the protocol is enabled"::= { rollCallPlus 1 }

rollCallPlusDomain OBJECT-TYPESYNTAXUnsigned32 MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCallPlus/Domain]] This domain number used for discovery"::= { rollCallPlus 2 }

rollCallPlusAddress OBJECT-TYPESYNTAXDisplayString MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCallPlus/Address]] This is the unit's RollCall+ address"::= { rollCallPlus 3 }

rollCallPlusUseLongNames OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[RollCallPlus/LongNames]] This indicates if the use of Long Names

is enabled"::= { rollCallPlus 4 }

-- SNMP Settings snmpNetwork OBJECT IDENTIFIER ::= { protcolSettings 5 }

snmpEnable OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SNMP/Enable]] This indicates if the protocol is enabled"::= { snmpNetwork 1 }

snmpCommunityGet OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SNMP/CommunityGet]] Community name for Get operations"::= { snmpNetwork 2 }

snmpCommunitySet OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SNMP/CommunitySet]] Community name for Set operations"::= { snmpNetwork 3 }

snmpCommunityTrap OBJECT-TYPE



SYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[SNMP/CommunityTrap]] Community name sent with traps"::= { snmpNetwork 4 }

snmpTrapManagerTable OBJECT-TYPESYNTAXSEQUENCE OF SNMPTrapManagerEntryMAX-ACCESS read-writeSTATUS currentDESCRIPTION "None" ::= { snmpNetwork 5 }

snmpTrapManagerEntry OBJECT-TYPE SYNTAX SNMPTrapManagerEntry MAX-ACCESS read-write

STATUS currentDESCRIPTION"None"INDEX { snmpTrapManagerIndex}::= { snmpTrapManagerTable 1 }

SNMPTrapManagerEntry ::=SEQUENCE {

snmpTrapManagerIndexUnsigned32,snmpTrapManagerIP IpAddress}

snmpTrapManagerIndex OBJECT-TYPESYNTAX Unsigned32MAX-ACCESSnot-accessibleSTATUS currentDESCRIPTION"Auto-generated index parameter for the array"::= { snmpTrapManagerEntry 101 }

snmpTrapManagerIP OBJECT-TYPESYNTAX IpAddressMAX-ACCESSread-writeSTATUS currentDESCRIPTION"[[SNMP/TrapAddresses]] The IP Address of the Trap

Manager"::= { snmpTrapManagerEntry 1 }

-- Debug Logging settings

debugLogging OBJECT IDENTIFIER ::= { routerConfig 6 }

debugLoggingEnable OBJECT-TYPESYNTAXBooleanFT MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Logging/Enable]] This indicates if the SysLogging is enabled"::= { debugLogging 1 }

debugLoggingIPAddress OBJECT-TYPESYNTAXIpAddress MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Logging/IpAddress]] This indicates if the SysLogging is enabled"::= { debugLogging 2 }

debugLoggingPortNumber OBJECT-TYPESYNTAXUnsigned32 MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Logging/Port]] This Port number used for SysLog clients"::= { debugLogging 3 }

debugLoggingFormat OBJECT-TYPE SYNTAXUnsigned32 { logFormatRFC3164(0), logFormatRFC3164Millis(1), logFormatRFC5424(2) }

MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Logging/Format]] This Port number used for SysLog clients"::= { debugLogging 4 }

-- Clock settingsclock OBJECT IDENTIFIER ::= { routerConfig 8 }

clockRTCSetMode OBJECT-TYPESYNTAXUnsigned32 { ntpServer(0), rollCallLogServer(1) }MAX-ACCESSread-write



STATUScurrentDESCRIPTION"[[Clock/RTCSetMode]] This is the RTC mode settings"::= { clock 1 }

clockNTPServer OBJECT-TYPESYNTAXDisplayString MAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Clock/NTPServer]] This indicates the server for the NTP"::= { clock 2 }

clockTimeZone OBJECT-TYPESYNTAXDisplayStringMAX-ACCESSread-writeSTATUScurrentDESCRIPTION"[[Clock/TimeZone]] This defines the timezone as defined in

https://www.gnu.org/software/libc/manual/html_node/TZ-Variable.html"::= { clock 3 }

-------------------------------------------------------------------------------- Traps and events for the Vega30 router

routerEvents OBJECT IDENTIFIER ::= { vega30Router 101 }

destRoutedSourceEvent NOTIFICATION-TYPEOBJECTS{ destRoutedSource } STATUScurrentDESCRIPTION"This event is triggered when a crosspoint is set"::= { routerEvents 1 }

destClientNameEvent NOTIFICATION-TYPEOBJECTS{ destClientName } STATUScurrentDESCRIPTION"This event is triggered when the client name protecting a

destination changes"::= { routerEvents 2 }

destProtectStateandDeviceEvent NOTIFICATION-TYPEOBJECTS{ destProtectStateandDevice } STATUScurrentDESCRIPTION"This event is triggered when the protect state on a destination

changes"::= { routerEvents 3 }

statusPSU1Event NOTIFICATION-TYPEOBJECTS{ statusPSU1 } STATUScurrentDESCRIPTION"This event is triggered when the status of PSU 1 changes"::= { routerEvents 4 }

statusPSU2Event NOTIFICATION-TYPEOBJECTS{ statusPSU2 } STATUScurrentDESCRIPTION"This event is triggered when the status of PSU 2 changes"::= { routerEvents 5 }

statusFanEvent NOTIFICATION-TYPEOBJECTS{ statusFan } STATUScurrentDESCRIPTION"This event is triggered when the fan status changes"::= { routerEvents 6 }

END

End of Vega30Router.mib file.


Vega 30 Router User Manual Introduction Configuration File E.1

Appendix E Configuration File

E.1 Introduction

The Configuration file is a text file containing configuration information for a Vega 30 Router. The file is for backup purposes. The user is NOT advised to edit this file.

E.2 Example Vega 30 Router Configuration File

// [Vega10Config:v1.0]{

"Vega30" : {

"Clock" : {

"NTPServer" : "1.2.3.4","RTCOffset" : 0,"RTCSetMode" : 0

},"General" : {

"ControllerName" : "Vega30","Location" : "Newbury HQ","SystemContact" : "Walter Plinge"

},"Logging" : {

"Enable" : true,"Format" : 1,"IpAddress" : "","Port" : 514

},"Network" : {

"UNIpAddress" : "10.162.5.238","UNIpGateway" : "10.162.254.1","UNIpPriDnsAddress" : "10.162.1.2","UNIpSecDnsAddress" : "0.0.0.0","UNIpSubNet" : "255.255.0.0"

Note: The configuration file is for backup purposes only.

Always keep a backup copy of the configuration file.

Important: Caution:

Do not edit the file.

An incorrect configuration file can cause a unit’s settings to be lost.

If an incorrect configuration file is used, the Vega 30 Router could be rendered inoperative and the only means of recovering would be a factory reset, which would overwrite settings.

Important: Take a backup of the configuration file before carrying out a Factory Reset.


Vega 30 Router User Manual Example Vega 30 Router Configuration File Configuration File E.2

},"PSU" : {

"Number" : 0},"RollCall" : {

"AnyLogServer" : false,"Enable" : true,"LogServerName" : "","SharePort" : 2050

},"RollCallPlus" : {

"Address" : "FFFF:49:00","Domain" : 49,"Enable" : true

},"SNMP" : {

"CommunityGet" : "public","CommunitySet" : "private","CommunityTrap" : "Vega30Trap","Enable" : true,"TrapAddresses" : []

},"SWP02" : {

"Enable" : true,"Port" : 2002

},"SWP08" : {

"Enable" : true,"Port" : 2008

}}

}

End of configuration file.


Vega 30 Router User Manual Introduction Persistence File F.1

Appendix F Persistence File

F.1 Introduction

The Persistence file is a text file containing state information for a Vega 30 Router. The file is for backup purposes. The user is not advised to edit this file.

F.2 Example Vega 30 Router Persistence File

[Vega10Persistence:v1.0]

2.2.1.1.1=9

2.2.1.1.5=9

2.2.1.1.11=6

2.2.1.2.1=1

2.2.1.2.2=1

2.2.1.2.3=1

2.2.1.2.4=1

2.2.1.2.5=5

2.2.1.2.6=5

2.2.1.2.7=5

2.2.1.2.8=5

2.3.1.3.3=14

2.3.1.5.1=1

2.3.1.5.2=1

2.3.1.5.3=1

2.3.1.5.4=1

2.3.1.5.5=5

2.3.1.5.6=5

2.3.1.5.7=5

2.3.1.5.8=5

2.3.1.8.1=2

2.4.1.1.1.1="My4KSrc1"

2.4.1.1.1.5="My4KSrc2"

2.4.1.1.1.9="My3GSrc3"

2.4.1.1.1.10="My3GSrc4"

Note: The persistence file is for backup purposes only.

Always keep a backup copy of the persistence file.

Important: Caution:

Do not edit the file.

An incorrect file pushed to a Vega 30 Router can cause a unit to not behave as expected.

If a factory reset is required to recover the unit, then all persistence data will be overwritten.

Important: Take a backup of the persistence file before carrying out a Factory Reset.


Vega 30 Router User Manual Example Vega 30 Router Persistence File Persistence File F.2

2.4.1.1.1.11="My1080i"

2.4.1.1.2.1="My 4K Source 0001"

2.4.1.1.2.5="My 4K Source 0002"

2.5.1.1.1.1="My4KDst1"

2.5.1.1.1.5="My4KDst2"

2.5.1.1.1.9="My3GDst3"

2.5.1.1.1.10="My3GDst4"

2.5.1.1.1.11="MyDest5"

2.5.1.1.2.1="My 4k Destination 0001"

2.5.1.1.2.5="My 4k Destination 0002"

2.5.1.1.3.9=1

2.5.1.1.3.10=29

2.5.1.1.3.11=1

2.5.1.1.3.12=1

2.5.1.1.3.13=1

2.5.1.1.3.14=1

2.5.1.1.3.15=1

2.5.1.1.3.16=1

2.5.1.1.3.17=1

2.5.1.1.3.18=1

2.5.1.1.3.19=1

2.5.1.1.3.20=1

2.5.1.1.3.21=1

2.5.1.1.3.22=1

2.5.1.1.3.23=1

2.5.1.1.3.24=1

2.5.1.1.3.25=1

2.5.1.1.3.26=1

2.5.1.1.3.27=1

2.5.1.1.3.28=1

2.5.1.1.3.29=1

2.5.1.1.3.30=1

2.5.1.1.3.31=1

2.5.1.1.3.32=1

2.5.1.1.3.33=1

2.5.1.1.3.34=1

End of persistence file.


Vega 30 Router User Manual Example Default Names File Source and Destination Names File (Import and Export) G.1

Appendix G Source and Destination Names File (Import and Export)

Source and Destination Names can be exported from or imported into the Vega 30 Router. Extracts from such an exported file in a spreadsheet editor are shown below:

G.1 Example Default Names File

Sample file contents, showing the factory names of a Vega 30 unit’s sources and destinations:

VEGA30

Destination Association 8 Character 32 Character

1 V.Out 1 Video Output 1










.

.






35 A.Out 1A Audio Output 1 A

36 A.Out 1B Audio Output 1 B

37 A.Out 1C Audio Output 1 C

38 A.Out 1D Audio Output 1 D


.

.



56 A.Out 6B Audio Output 6 B

57 A.Out 6C Audio Output 6 C


VEGA30

Source Association 8 Character 32 Character

1 V.In 1 Video Input 1








Vega 30 Router User Manual Example Default Names File Source and Destination Names File (Import and Export) G.1




.

.







35 A.In 1A Audio Input 1 A

36 A.In 1B Audio Input 1 B

37 A.In 1C Audio Input 1 C

38 A.In 1D Audio Input 1 D


.

.



44 A.In 3B Audio Input 3 B

45 A.In 3C Audio Input 3 C


47 Src 47 Source 47

48 Src 48 Source 48

49 Src 49 Source 49

50 Src 50 Source 50

51 Src 51 Source 51

.

.

489 Src 489 Source 489













Vega 30 Router User Manual Example Real-world File Contents Source and Destination Names File (Import and Export) G.2

G.2 Example Real-world File Contents

Example file contents:

VEGA30

Destination Association 8 Character 32 Character

1 TX 1 TX 1 London

2 TX1 Bak TX 1 London Backup

3 TX2 TX2 Cardiff

4 TX2 Bak TX2 Cardiff Backup

5 EVS1 EVS 1

6 EVS2 EVS 2

7 HDD1 HDD Archive 1

.

.

55 MO6 1‐1A MADI Mix Desk 3 Ch 1‐16

56 MO6 1‐1B MADI Mix Desk 3 Ch 17‐32

57 MO6 1‐1C MADI Mix Desk 3 Ch 33‐48

58 MO6 1‐1D MADI Mix Desk 3 Ch 49‐64

VEGA30

Source Association 8 Character 32 Character

1 BBC1 BBC1 South

2 Tvone TV One

3 NHK NHK Japan

4 WDR WDR Germany

5 Pro7 ProSieben Germany

6 TV1 TV1

7 ITV ITV London

8 Drama Drama Channel

.

.

35 MADI 1A MADI In 1 Ch1‐16A

36 MADI 1B MADI In 1 Ch1‐16B

37 MADI 1C MADI In 1 Ch1‐16C

38 MADI 1D MADI In 1 Ch1‐16D

.

.

499 WDR‐Dol WDR Dolby E

500 Nick2+2 Nickelodeon Ch 1‐2 & 5‐6


Vega 30 Router User Manual Example Real-world File Contents Source and Destination Names File (Import and Export) G.2

Extracts from file opened in a text editor:

The file is in a comma-separated format with a .csv extension. Extracts from the file are shown:

VEGA30,,Destination Association,8 Character,32 Character1,TX 1,TX 1 London2,TX1 Bak,TX 1 London Backup3,TX2,TX2 Cardiff4,TX2 Bak,TX2 Cardiff Backup5,EVS1,EVS 16,EVS2,EVS 27,HDD1,HDD Archive 18,HDD2,HDD Archive 29,DVR1,Dig Vid Rec 110,DVR2,Dig Vid Rec 2..33,MCR3,Master Control Feed 334,MCR4,Master Control Feed 435,MO1 1-1A,MADI Mix Desk 1 Ch 1-16A36,MO1 1-1B,MADI Mix Desk 1 Ch 1-16B37,MO1 1-1C,MADI Mix Desk 1 Ch 1-16C38,MO1 1-1D,MADI Mix Desk 1 Ch 1-16D..57,MO6 1-1C,MADI Mix Desk 3 Ch 33-48 - Backu58,MO6 1-1D,MADI Mix Desk 3 Ch 49-64 - BackuVEGA30,,Source Association,8 Character,32 Character1,BBC1,BBC1 South2,Tvone,123456789012345678901234567890123,NHK,NHK Japan4,WDR,WDR Germany5,Pro7,ProSieben Germany6,TV1,TV17,ITV,ITV London8,Drama,Drama Channel9,Sky1,Sky 110,BBC1HD,BBC1 HD South..33,Dave,Dave34,Nick Jr,Nicklelodeon Junior35,MADI 1A,MADI In 1 Ch1-16A36,MADI 1B,MADI In 1 Ch1-16B37,MADI 1C,MADI In 1 Ch1-16C38,MADI 1D,MADI In 1 Ch1-16D..45,MADI 3C,MADI In 3 Ch1-16C46,MADI 3D,MADI In 3 Ch1-16D47,EN Audio,BBC1 English Stereo48,FR Audio,BBC1 French Stereo..498,Nick-Dol,Nickelodeon Dolby E499,WDR-Dol,WDR Dolby E500,Nick2+2,Nickelodeon Ch 1-2 & 5-6

End of import/export file extract.


Vega 30 Router User Manual

User Notes:


Vega 30 Router User Manual

User Manual

Vega 30

Last page.


vega-30 user manual - grass valley

Documents