Ultricore User Guide (2201DR-104)
Ultricore User Guide (2201DR-104)
David Ross
CEO, Ross Video
[email protected]
Copyright
©2021 Ross Video Limited, Ross®, and any related marks are trademarks or registered trademarks of Ross Video Limited. All other
trademarks are the property of their respective companies. PATENTS ISSUED and PENDING. All rights reserved. No part of this
publication may be reproduced, stored in a retrieval system, or transmitted in any form or by any means, mechanical, photocopying,
recording or otherwise, without the prior written permission of Ross Video. While every precaution has been taken in the preparation
of this document, Ross Video assumes no responsibility for errors or omissions. Neither is any liability assumed for damages resulting
from the use of the information contained herein.
Patents
Patent numbers US 7,034,886; US 7,508,455; US 7,602,446; US 7,802,802 B2; US 7,834,886; US 7,914,332; US 8,307,284; US
8,407,374 B2; US 8,499,019 B2; US 8,519,949 B2; US 8,743,292 B2; GB 2,419,119 B; GB 2,447,380 B; and other patents pending.
Notice
The material in this manual is furnished for informational use only. It is subject to change without notice and should not be construed
as commitment by Ross Video Limited. Ross Video Limited assumes no responsibility or liability for errors or inaccuracies that may
appear in this manual.
Safety Notices
Refer to the “Important Regulatory and Safety Notices” document that accompanied your product.
Statement of Compliance
This product has been determined to be compliant with the applicable standards, regulations, and directives for the countries where
the product is marketed.
Compliance documentation, such as certification or Declaration of Compliance for the product is available upon request by
contacting [email protected]. Please include the product; model number identifiers and serial number and country that
compliance information is needed in request.
EMC Notices
United States of America - FCC Part 15
This equipment has been tested and found to comply with the limits for a class A Digital device, pursuant to part 15 of the FCC Rules.
These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a
Commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in
accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a
residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own
expense.
Canada
This Class A device complies with Canadian ICES-003 and part 15 of the FCC Rules.
Cet appariel numerique de la classe “A” est conforme a la norme NMB-003 du Canada.
Notice — Changes or modifications to this equipment not expressly approved by Ross Video Ltd. could void the
user’s authority to operate this equipment.
European Union
This equipment is in compliance with the essential requirements and other relevant provisions established under regulation (EC) No
765/2008 and Decision No 768/2008/EC referred to as the “New Legislative Framework”.
Warning — This equipment is compliant with Class A of CISPR 32. In a residential environment this equipment may
cause radio interference.
Australia/New Zealand
This equipment is in compliance with the provisions established under the Radiocommunications Act 1992 and
Radiocommunications Labeling (Electromagnetic Compatibility) Notice 2008.
Korea
This equipment is in compliance with the provisions established under the Radio Waves Act.
Class A equipment (Broadcasting and communications service for business use).
This device is a business-use (Class A) EMC-compliant device. The seller and user are advised to be aware of this fact. This device is
intended for use in areas outside home.
International
This equipment has been tested under the requirements of CISPR 22:2008 or CISPR 32:2015 and found to comply with the limits for
a Class A Digital device.
Notice — This is a Class A product. In domestic environments, this product may cause radio interference, in which
case the user may have to take adequate measures.
Notice — Changes or modifications to this equipment not expressly approved by Ross Video Limited could void the
user’s authority to operate this equipment.
If an item becomes defective within the warranty period Ross will repair or replace the defective item, as determined solely by Ross.
Warranty repairs will be conducted at Ross, with all shipping FOB Ross dock. If repairs are conducted at the customer site, reasonable
out-of-pocket charges will apply. At the discretion of Ross, and on a temporary loan basis, plug in circuit boards or other replacement
parts may be supplied free of charge while defective items undergo repair. Return packing, shipping, and special handling costs are
the responsibility of the customer.
This warranty is void if products are subjected to misuse, neglect, accident, improper installation or application, or unauthorized
modification.
In no event shall Ross Video Limited be liable for direct, indirect, special, incidental, or consequential damages (including loss of
profit). Implied warranties, including that of merchantability and fitness for a particular purpose, are expressly limited to the duration
of this warranty.
This warranty is TRANSFERABLE to subsequent owners, subject to Ross’ notification of change of ownership.
Environmental Information
The equipment may contain hazardous substances that could impact health and the environment.
To avoid the potential release of those substances into the environment and to diminish the need for the extraction of natural
resources, Ross Video encourages you to use the appropriate take-back systems. These systems will reuse or recycle most of the
materials from your end-of-life equipment in an environmentally friendly and health conscious manner.
The crossed-out wheeled bin symbol invites you to use these systems.
If you need more information on the collection, reuse, and recycling systems, please contact your local or regional waste
administration. You can also contact Ross Video for more information on the environmental performances of our products.
This appliance may contain a Coin type battery which should not be treated as household waste.
To ensure that the battery will be treated properly use the appropriate take-back systems in your area. These systems will reuse or
recycle most of the materials from your end-of-life equipment in an environmentally friendly and health conscious manner.
Company Address
Ross Video Limited Ross Video Incorporated
8 John Street P.O. Box 880
Iroquois, Ontario Ogdensburg, New York
Canada, K0E 1K0 USA 13669-0880
Getting Started 19
General Overview .................................................................................................................................................. 19
Features ............................................................................................................................................................... 19
Typical System Equipment .................................................................................................................................... 20
Before You Begin .................................................................................................................................................. 21
Installation and Setup Overview ............................................................................................................................ 21
Implementing a System Plan ............................................................................................................................... 21
Establish Communications .................................................................................................................................. 21
Define the Routing System Database in Ultricore .............................................................................................. 22
Set up Virtual Control and Resource Management in Ultricore ......................................................................... 22
Configure the Soft Panels in Ultricore ................................................................................................................ 22
Hardware Overview 25
Front Panel Overview ............................................................................................................................................ 25
Rear Panel Overview ............................................................................................................................................. 26
Physical Installation 27
Before You Begin .................................................................................................................................................. 27
Mounting Requirements ......................................................................................................................................... 27
Connecting the Ultricore to a Network .................................................................................................................. 27
Connecting the Ultricore to Ross NK Series Devices ........................................................................................... 28
Connecting the Ultricore to a Serial Device .......................................................................................................... 29
Connecting to a Power Supply ............................................................................................................................... 29
Configuring the Loss of Power Alarm ................................................................................................................... 30
Basic Configuration 31
Getting Started ....................................................................................................................................................... 31
Launching DashBoard ........................................................................................................................................... 32
Using Walkabout to Assign an IP Address to the Ultricore Panel ........................................................................ 32
Adding the Ultricore to the Tree View in DashBoard ........................................................................................... 32
Accessing the Ultricore Interfaces in DashBoard .................................................................................................. 33
Configuring the Ultricore Mode ............................................................................................................................ 34
Overview ............................................................................................................................................................. 34
Assigning a Role to the Ultricore ........................................................................................................................ 34
Specifying the Time Source ................................................................................................................................... 35
Using an NTP Server as the Time Source ........................................................................................................... 35
Using the DashBoard Client Computer as the Time Source ............................................................................... 36
Reviewing the Network Settings for the Ultricore Panel ....................................................................................... 36
Re-naming the Ultricore ........................................................................................................................................ 37
Configuring Access for DashBoard Clients ........................................................................................................... 37
Ultricore Profiles 41
Overview ................................................................................................................................................................41
Modes of Operation ................................................................................................................................................41
Creation and Management of User Credentials ..................................................................................................41
Creation and Management of User Profiles via the Default Role Profiles Only .................................................42
Full Creation, Customization and Management of User Profiles .......................................................................42
Ultricore Profiles Interface .....................................................................................................................................42
Accessing the Ultricore Profiles Interface ...........................................................................................................42
Overview .............................................................................................................................................................43
Creating a Database of Users .................................................................................................................................44
Creating a Profile ...................................................................................................................................................44
Defining the Permissions for a Profile ...................................................................................................................46
Overview .............................................................................................................................................................46
Enabling the Ultricore Profiles Feature ..................................................................................................................47
Application of the Ultricore Profiles ......................................................................................................................47
User Data Import/Export ........................................................................................................................................48
Database Configuration 63
How a Database Determines the Routing System ..................................................................................................63
Configuration Overview .........................................................................................................................................63
Database File Management Overview ...................................................................................................................63
Creating a New Database .......................................................................................................................................64
Using the Database Builder .................................................................................................................................64
Using the Database Tab .......................................................................................................................................66
Tallies 85
Tally Types ......................................................................................................................................................... 85
Tally ID Format .................................................................................................................................................. 85
Router Tally Output Operation .............................................................................................................................. 86
Router Status over TSL UMD v3.1 Operation .................................................................................................... 86
Getting Started ....................................................................................................................................................... 87
Adding a Serial Connection Point .......................................................................................................................... 87
Adding an Ethernet Connection Point ................................................................................................................... 87
Enabling Tally ID Support ..................................................................................................................................... 87
Enabling Tally ID Support in the Active Database ............................................................................................. 87
Defining the Status Level for Tally Operation .................................................................................................... 87
Assigning the Tally IDs to the Sources .................................................................................................................. 88
Assigning the Tally IDs to the Destinations .......................................................................................................... 88
Using Categories 91
Group Categories Overview .................................................................................................................................. 91
Configuring Group Categories ............................................................................................................................... 93
Creating Group Names ........................................................................................................................................ 93
Auto Generating the Groups ............................................................................................................................... 95
Assigning Resources to a Group ......................................................................................................................... 96
Managing the Groups .......................................................................................................................................... 98
Cat/Index Categories Overview ............................................................................................................................. 99
Configuring a Cat/Index Category Setup ............................................................................................................. 100
Assigning Categories ........................................................................................................................................ 100
Assigning Indexes ............................................................................................................................................. 102
Assigning Index Filters ..................................................................................................................................... 102
Legacy Categories Overview ............................................................................................................................... 103
Configuring Legacy Categories ........................................................................................................................... 104
Category Direct Selection Mode ....................................................................................................................... 104
Numerical Index Entry Mode ............................................................................................................................ 104
Creating a Soft Panel with Categories ................................................................................................................. 105
Monitoring 179
Enabling Logging for the Ultricore ...................................................................................................................... 179
Monitoring the Network Status ............................................................................................................................ 179
Forcing an Ethernet Failover Switch ................................................................................................................. 179
Monitoring the Ultricore Mode Status ................................................................................................................. 180
Primary Status ................................................................................................................................................... 180
Client Status ...................................................................................................................................................... 180
Troubleshooting ................................................................................................................................................ 180
Using the System Logs in DashBoard ................................................................................................................. 180
Saving the Current Settings for the Ultricore ...................................................................................................... 181
Monitoring the Devices in a Routing System ...................................................................................................... 181
Monitoring via the Front Panel ............................................................................................................................ 182
Navigating the Menus ....................................................................................................................................... 182
Monitoring the Ethernet LEDs on the Rear Panel ............................................................................................... 182
Upgrading the Software ....................................................................................................................................... 183
Glossary 243
Related Publications
It is recommended to consult the following Ross documentation before installing and configuring your Ultricore:
• DashBoard User Manual, Ross Part Number: 8351DR-004
• NK-NET User Guide, Ross Part Number: 2201DR-002
• NK-IPS User Guide, Ross Part Number: 9807DR-1020
• NK Series User Guide, Ross Part Number: 9807DR-0100
• RCP-ME User Guide, Ross Part Number: 2201DR-200
Documentation Conventions
Special text formats are used in this guide to identify parts of the user interface, text that a user must enter, or a
sequence of menus and sub-menus that must be followed to reach a particular command.
Interface Elements
Bold text is used to identify a user interface element such as a dialog box, menu item, or button. For example:
In the Edit dialog, click Insert Above.
Referenced Guides
Italic text is used to identify the titles of referenced guides, manuals, or documents. For example:
For more information, refer to the Ultrix User Guide.
Menu Sequences
Menu arrows are used in procedures to identify a sequence of menu items that you must follow. For example, if a
step reads “File > Save As,” you would click the File menu and then click Save As.
Important Instructions
Star icons are used to identify important instructions or features. For example:
Contact your IT department before connecting to your facility network to ensure that there are no conflicts. They
will provide you with an appropriate value for the IP Address, Subnet Mask, and Gateway for your device.
General Overview
Ultricore is the central system controller for Ross Video’s routing systems. It allows the connection of Ethernet
based routers and remote control panels, T-Bus based Ross NK Series routers and remote control panels, and
third-party automation systems.
By collating the potentially complex aspects of a system’s switching scheme, Ultricore allows for minimal
out-of-the-box configuration of routers. This not only makes it easier to initially setup a system, but it also makes it
easier to change configuration as needed.
The DashBoard client software enables you to monitor and control your Ross routing system components,
including Ultricore from a computer. DashBoard communicates with the Ross routing system through ethernet,
TCP, connections.
Features
Some features of the Ultricore include:
• SLP discovery or manual configuration of connection to DashBoard client software
• Client and server operation with client connection failover support
• Basic system crosspoint control and status monitoring via DashBoard
• Connections for redundant power supplies
• Alarm output with locking GP connector
• Dual Gigabit Ethernet interfaces
• T-Bus with looping connectors and power for native NK series connectivity
• Non-volatile memory for system recovery and logging
• Real-time clock
• Supports a maximum of 64 levels, with a maximum matrix of 4096 sources and 4096 destinations
• Dual configurable serial ports (RS-232 or RS-422)
• Front status display for system events
• Bi-directional Ethernet and Serial protocol support for the GVG Native protocol
• Supports the Probel SW-P-08 serial protocol
• Acts as a central system controller for up to 25 DashBoard clients and up to 50 hardware clients (routers, remote
control panels, third-party control systems, etc.)
• Supports links from the NK-IPS for legacy installed systems
• Supports NK-IPS pass-through type connection for direct NK device support
• Supports Virtual Routing, Matrix Partitioning, and Mapping
• Label support1
ULTRIX-FR1
32x32 3G/HD/SD SDI Router
ENET 1 ! 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
REF 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 4 A B
OUT IN
Network Switch
PC running DashBoard
Ultricore
System Control and Interface
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET
NK Series Router
USB
USB
USB
USB
PORT 1
VIDREF
T-BUS
ALARM
GPI
GND
ALARM
+5V
Ethernet connection
Serial connection
T-Bus connection
Figure 2.1 Example of a Possible Routing System with Ultricore
Establish Communications
Ultricore supports the Walkabout system for initial configuration of IP settings. Once you establish communications
over Ethernet between the Ultricore panel and DashBoard, you can proceed to use the interfaces in DashBoard that
enable Ultricore to communicate with the other devices in your routing system.
For More Information on...
• establishing a network connection to Ultricore, refer to the section “Using Walkabout to Assign an IP Address
to the Ultricore Panel” on page 32.
Set up Define
Establish Define Core Define System Define Source
Connected Destination
Device Details System Settings Levels Labels
Devices Labels
Operation
Once configured, the Ultricore provides central controller functionality for the routing system, including:
• the storage and implementation of routing system configurations, which collect a series of routing matrices into a
system and provide a logical database view of the whole system
• switching the physical crosspoints of the routers according to the system configuration
IP:1###.###.##.###
2 3 4
2. LCD Display
The LCD display reports on the overall system status, IP address of the panel, and current fault conditions.
During normal operations, the display reports the Device Name (user assigned) and the active IP address of the
panel. Under some conditions, fault conditions are reported such as: device boot status, Walkabout locate mode
indication, SRAM battery warnings, and firmware upgrade states. The information on the display alternates
between normal operation and the error messages.
3. Navigation Positioner
The front panel includes a five-direction joystick that is used to navigate the Ultricore on the LCD Display. Refer
to the section “Monitoring via the Front Panel” on page 182 for details.
4. ETHERNET Port LEDs
Table 3.2 describes the Ultricore front panel LEDs that are used to monitor ethernet communication activity of
the Ultricore panel. When facing the front panel, the left LED reports the status of ETHERNET PORT 1 while
the right LED reports the status of ETHERNET PORT 2.
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM
ETHERNET COM2
1. PSU Ports
Two +15V DC power supply connections (PSU1, PSU2) are provided to connect to external brick power
supplies to the Ultricore panel.
2. ALARM GPO
This contact closure connector is used to report an alarm where closed is a system fault, and open when the
system is running without errors.
3. ETHERNET Ports
Ultricore communicates over an Ethernet connection to routers, and other devices. PORT 1 is the primary
Ethernet connection for Ultricore. PORT 2 is the redundant (backup) Ethernet connection. The exact steps for
connecting to your facility via an ethernet network depends on the requirements defined by your IT Department.
4. T-BUS Ports
Each port provides a loop-through connection for Ross NK series communication. This enables communication
to legacy routers and remote control panels as part of the routing system.
5. COM Ports
There are two female DB-9 serial ports used to connect to third-party automation devices. Each port can be
configured for RS-232 or RS-422 serial communication. Uses these ports to connect to third-party automation
devices that will control the routing system.
Static Discharge
Throughout this chapter, please heed the following cautionary note:
ESD Susceptibility — Static discharge can cause serious damage to sensitive semiconductor
devices. Avoid handling circuit boards in high static environments such as carpeted areas and when
synthetic fiber clothing is worn. Always exercise proper grounding precautions when working on circuit
boards and related equipment.
Mounting Requirements
The Ultricore panel is designed for installation into a standard 19” equipment rack. It has integrated rack ears,
allowing it to be screwed in using standard screws and cage nuts.
The Ultricore panel mounts in the rack frame by means of four rack screws fastened through the front mounting
ears. This should normally be sufficient to carry the load, including the weight of accompanying cables.
Under some conditions, the ambient air temperature inside rack-mount cabinets can be greater than the ambient
temperatures within a room. For safe long term reliability, ensure the ambient air temperatures at the router front
intake are within the router’s specified operating temperature range. Adequate ventilation within a rack frame must
also be maintained.
For More Information on...
• the technical specifications for the Ultricore, refer to the chapter “Technical Specifications” on page 229.
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM
ETHERNET COM2
2. If required, connect the redundant network connection for the Ultricore panel:
a. Connect one free end of a second straight through CAT5/5e/6 cable to a free port of the network hub.
b. Connect the other end of the same cable to Ethernet PORT 2 on the Ultricore rear panel.
To NK Series Device
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM
ETHERNET COM2
To NK Series Device
Figure 4.2 Ultricore — Cabling to Legacy NK Series Devices
To Serial Device
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM
ETHERNET COM2
2. Connect the other end of the same Serial Interface cable to the applicable serial port on the device.
Warning Hazardous Voltages — The safe operation of this product requires that a protective
earth connection be provided. This protective earth is provided by the ground conductor in the
equipment’s supply cord. To reduce the risk of electrical shock to operator and service personnel, this
ground connector must be connected to an earthed ground.
Warning — In some countries it may be necessary to supply the correct mains supply cord. Use only
certified cords for the country of use.
Note: It is recommended that you always connect the Power Supply Unit to the Ultricore
before connecting to Mains Power.
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM
ETHERNET COM2
2. Connect the remaining power cable into the PSU2 power supply socket if redundancy is required.
3. Connect the supplied AC power cable into the power modules.
4. Connect the supplied power cable’s three-prong male connector to an AC outlet.
GND PIN 2
Getting Started
Figure 5.1 summarizes the basic steps in configuring the Ultricore system.
Ultricore Network
Setup
Create a Database
for the Routing System
Establish Device
Connection Points in
Ultricore
Configure the
Remote Control
Panel(s)
Configure
Resource Management
(if required)
6. Enter the IP Address for the Ultricore in the IP Address field assigned in the section “To assign a static IP
address to the Ultricore panel” on page 32.
7. Perform one of the following steps:
• In the text fields provided, enter the display name and port of the Ultricore you wish to add; or
• Click Detect Frame Information to automatically retrieve the connection details.
8. Click Finish.
The Ultricore panel displays in the Tree View.
Overview
When an Ultrix router is a client to the primary Ultricore, it acts similar to an Ross NK router in the system. The
client router provides another set of inputs and outputs with a crosspoint between them. These inputs and outputs
are then available to assign in the database of the primary Ultricore.
The primary Ultricore initiates a connection point to the client device(s) in the routing system. Once
communication is established, whenever a crosspoint switch or salvo is executed on the primary Ultricore, the
commands are automatically pushed to the client device(s).
For More Information on...
• monitoring the communications between the primary Ultricore and its clients, refer to the section “Monitoring
the Ultricore Mode Status” on page 317.
Overview
The Ultricore Profiles operate as a form of hierarchical database where user permissions are organized into a
tree-like format. A profile determines which groups and pages that a user can access.
Any number of profiles may be created and can be used in the following ways:
• Group/Role — This profile type is not specific to any user or machine. Once created they can be referenced or
used by any number of users or machines. For example, a Graphics Editor profile can be created and referenced
by a team of graphics editors. When a new control panel is added to that profile, all graphics editors are updated
with the new panel automatically.
• User — A user profile identifies a specific username and can either reference an existing role as above or copy
an existing role then modify, add, or remove items to allow total customization as required. This allows a user
that has a specific profile to have the same capabilities on any DashBoard system regardless of where they log in.
• Location — This profile is defined by a specific location (user station) and assigns a consistent function
regardless of who is logged in that suits the operation in that location. In this way the DashBoard instance in front
of, for example, the audio operator in a specific control room will only have the optimize functionality for that
role. A location profile can also reference or copy and modify role profiles.
Profiles can also be created that identify a specific user at a specific user station to further optimize the user
interface in different locations. If no profile exists for the combination of user and location, the system default
profile is used.
When there are multiple possible profiles the one used is chosen as follows:
1. A User profile has the highest priority. This means that an administrator can log in anywhere and execute
Administrator level functions or an operator can login anywhere and have an optimized UI for their function.
2. A Location profile is used for all users at a specific location unless the user logged in has a profile. This allows
more or different functionality for users logged into a specific location even if they do not have a specific
profile themselves.
3. The system default profile is used in all other scenarios.
Modes of Operation
The Ultricore Profiles feature consists of three sub-functions or modes of operation.
The ULTRICORE-PRO license is required to upgrade from the basic, non-configurable profiles on the Ultricore
chassis to full, customizable configurations. The ULTRICORE-PRO license is standard on the Ultricore-BCS.
Figure 7.1 Example of the Ultricore Profiles Interface with the ULTRICORE-PRO license
Users
When the system is configured to use the user login mechanism, a list of all currently configured usernames along
with their current online status displays in this area.
Profiles
A list of all currently configured profiles. Selecting a profile (row) in this area automatically updates the items
displayed in the Profile Details, Device Tree, and Options areas.
Profile Details
This area displays the details of the profile showing the conditions under which the tree in the following section will
be applied.
Tree Nodes
A visual representation of the tree view that is defined in the Profile Details. Note that certain entries that are
specific to licenses or other conditions may be visible but not in the actual tree view. Should conditions change that
enable those entries, they will appear as shown in this display. A profile also maintains the position of items in
groups allowing the most relevant items to be the easiest to reach.
The tree nodes are organized in a hierarchy where the top level (blue icons) list system specific options, and
secondary levels (yellow icons) list specific functions.
This area only displays when the ULTRICORE-PRO license is enabled.
Group Tabs
This area displays all the available items that have not yet been assigned to the currently selected profile but are
available to define.
This area only displays when the ULTRICORE-PRO license is enabled.
3. Click Add.
4. Use the User Name field to assign a unique identifier for the user account.
5. Use the Password field to define the password the user will need to enter when logging in with this account.
6. Repeat this procedure for every new user you wish to create.
Once all the user accounts are created, you can proceed to create profiles and assign users to these profiles.
Creating a Profile
The User Profiles features offers a significant flexibility to optimize the tools in front of individual operators
which, if inadvertently mis-configured could lead to administrators being locked out. As such, it is a good idea
for the administrator to ensure that no users are actively working within the system prior to making significant
changes to users and profile settings.
Figure 7.2 Example of the Tree Nodes and Tabs for a Selected Profile
Overview
This section provides a brief overview of each area and their options.
Tree Nodes
The tree (the leftmost area) displays all the assigned options and their desired order in the tree structure much like
the tree view in DashBoard for an Ultricore. The nodes in Ultricore Profiles tree view are determined by your
system configuration and any licenses installed for your system. Buttons at the bottom of this area (Up, Down,
Remove) allow entries to be moved up and down in the tree within the group to which the item belongs or removed
if they are not required for the selected profile. When removed, the item is returned to the list of available items in
the appropriate group tab.
Group Tabs
The group tabs (the rightmost area) contain all items available in the group in question that are not included in the
selected profile’s tree currently. If an item is not in the tree currently but required, the appropriate group tab is
selected, the item required is selected and the Assign button is clicked moving it to the bottom of the appropriate
To log in
1. In the Basic Tree View, locate the device you wish to access.
2. Expand the device nodes to display the System Login sub-node.
3. Double-click the System Login sub-node.
The System Login page displays in the DashBoard window.
8. Use the IP Address field to specify the new static IP Address for the Ultricore.
9. Use the Subnet Mask field to specify the subnet mask for your network.
10. Use the Default Gateway field to specify the gateway for communications outside of the local area network
(LAN).
11. Click Apply to apply the new settings.
Figure 9.1 Work Flow for Setting up a Connection Point between Ultrix and Ultricore
Setup Notes
Keep the following mind when establishing a connection point from an Ultricore to an Ultrix router:
• Ensure unique device names for each Ultrix router. This allows identification of each individual router
throughout the setup process. You can edit the name via the Ultrix front panel interface as outlined in the Ultrix
User Guide.
• Ensure that the Remote Controller Mode is enabled for each client Ultrix router. Refer to the Ultrix User Guide
for details.
• Client hardware configuration (licensing, port configuration, etc.) is achieved via its own device node within the
DashBoard tree.
• Client Ultriscape Multiviewers are configured via the Ultriscape node within the DashBoard tree of the client
Ultrix that physically hosts that Multi-Viewer.
• Routing commands are issued to the primary device via remote control panels, external protocols or DashBoard
soft panels1. Any client router will ignore routing commands not originating from the primary while in this
connected mode.
1. Only the soft panels defined within the database of the Ultricore may control the system.
d. Click Apply to create the new device row(s) in the Servers table.
The Add Connection dialog closes.
6. In the Name column of the Servers table, click the cell of the new Ultrix row to display the drop-down menu.
7. From the drop-down menu, select the Ultrix router you which to establish a connection to.
8. If the Ultrix router is not listed in the drop-down menu:
a. Close the Connections tab.
b. Launch Walkabout to detect the on-line devices in your system.
c. Double-click the Connections node for the Ultricore to display its Connections tab.
d. Repeat steps 4 to 7.
9. In the Enabled column of the new row, select Enable.
10. Repeat steps 6 to 9 for each additional Ultrix router.
11. Click Apply at the bottom of the Connections tab to save the new settings.
Overview
Ultricore provides bi-directional translation of the following third-party protocols:
• GVG Native serial and Ethernet protocols
• Probel SW-P-08 serial protocol
Connection to third-party devices may be categorized into two broad groups: controller and controllee.
• Controllers are devices that will control the Ultricore and connect via what may be termed an incoming
connection.
• Controllees are devices to be controlled by Ultricore router and connect via what may be termed an outgoing
connection.
For More Information on...
• the protocols and ports for configuring third-party communications on Ultricore, refer to Table 9.2 and
Table 9.3.
• the commands that Ultricore supports, refer to the chapter “External Control” on page 161.
• connecting a third-party device to the serial port on the Ultricore rear panel, refer to the section “Connecting the
Ultricore to a Serial Device” on page 29.
These Ethernet servers are always running. No further configuration is required — simply configure your client
device to match the Ultricore’s TCP/IP address and port number.
a. An entry is not present in the corresponding Level column of the Source tab.
b. An entry is not present in the corresponding Level column of the Destinations tab.
c. A resulting switch will be executed.
d. A resulting switch will not be executed. Physical ports from the same logical matrix must be
entered in the same control level before a connection can be made.
Configuration Overview
The generalized work flow of configuring a database for the Ultricore is:
1. Establish connection points to external devices. Refer to the chapter “Device Communication Setup” on
page 51 for details.
2. Verify available I/O ports to ensure correct system connections. This default port naming convention of
frame.slot.port.type nomenclature is to be overwritten (if required) at this stage.
3. Create a database as outlined in the procedure “Creating a New Database” on page 64.
Ultricore does not support Unicode characters.
4. Define a soft panel or establish a connection to a remote control panel (RCP).
Exporting a Database
Enables you to capture a database configuration in a *.uda file that is saved to a location on your network that you
can specify. Refer to the section “Exporting a Database” on page 82.
Importing a Database
Enables you to import a saved *.uda file and make it available in the System Status > Database tab. Refer to the
section “Importing a Database” on page 83 for details.
Click Next, located at the bottom of the DashBoard window, to display the next page of options in the Database
Builder interface.
6. If any AUX Ports are populated with SFP modules, use the Include AUX ports menu to specify how to label
the I/O in the database.
The default is Insert at Slot, which labels the I/O in each slot as 1-18 with the AUX Ports as 17 and 18.
7. Use the Support Video Signal and Number of Audio Channels menus to define the Levels in the database.
8. Use the Breakaway Source Support menus to implement audio shuffling. The options for SDI and MADI
channels are as follows:
• None — there are no audio channels of this type.
• Mono — audio channels are applied to all levels
• Stereo — audio channels are assigned by pair (1-2, 3-4, 5-6 etc.)
• Quad — audio channels are assigned in groups of four (1-4, 5-8, 9-12 etc.)
• Oct — audio channels are assigned in groups of eight (1-8, 9-16, 17-24 etc.)
You must have SFP modules installed that support MADI.
9. Use the Disconnect Source menu to set unused audio channels to disconnect.
10. Use the Passthrough Source menu to route the sources without changes/edits.
11. If you have an UltriScape license installed, use the last set of menus to define the heads, including the number
of Picture in Picture (PIPs) that new layouts can include.
You can still create and edit layouts in a database with settings that differ from these.
12. Click Next to review the levels, destinations, and sources tables before completing the database builder.
a. Use the Levels page to review or rename the level labels if required.
b. Use the Destination page to review the destination label to physical port mapping. Renaming the labels is
also possible from this page if required.
4. In the Add Database Name field type a unique identifier for the database. When the database is currently
loaded in the system (in use), the Database node displays the database name in the tree view under the Ultricore
node.
5. Select the Include I/O Maps box to create a database to match the quantity of BNC I/O ports available in the
connected router.
Each SDI IN/OUT ports will be mapped to the default labels of SRC# and DST# respectively for Level 1 only
(SDI). The Destinations and Sources fields are ignored, but the Level field is applied.
6. Use the Levels field to specify the total number of levels available in the database.
7. Use the Sources field to specify the total number of inputs available in the database.
8. Use the Destination field to specify the total number of outputs in the database.
9. Click Database Add to create the new database and save it to the Ultricore file system.
10. Load the database to ensure it is active before proceeding to customize it.
Loading a Database
Each active database includes a unique setup saved to the Ultricore file system. You must recall a database before
you can configure the matrices, levels, sources and destinations, and soft panels for a particular setup. This also
enables you to quickly recall a saved (configured) routing setup just by recalling a different database.
3. From the Name menu in the Load Database area, select the database you want to load.
4. Click Load.
5. Verify the following to ensure the database was loaded:
• The Name, Levels, Sources, and Destination read-only fields in the Current Database area in the
Database tab report the correct values.
• The Database node in the Tree View for the Ultricore now reports the correct Database name.
If AFV (audio-follow-video) is desired on a single level database, the Audio Bypass must be enabled for each
input and output port or disable the Ultrimix function.
A single level setup with NK-A64 analog audio router attached would require the following levels:
ID Name
1 SDI
2 AnAud L
3 An Aud R
A setup using SDI with 4 embedded audio levels. This can allow independent switching of 4 of the embedded SDI
channels and grouping of 4 MADI channels.The following levels would be required:
ID Name
1 SDI
2 A1
3 A2
4 A3
5 A4
Create Source Labels with Assignments for SDI and Embedded Audio
The objective of this example is to create source labels and assignments for the SDI video and the first four
embedded audio channels for an entire Ultricore enabled slot. The remaining twelve audio channels are not used.
To create source labels with assignments for the SDI video and embedded audio levels
1. Ensure that you have the Ultrimix licensed feature enabled for the slot. Refer to the Ultrix User Guide for
details.
2. Define one level for SDI Video and 16 levels for the embedded audio as outlined in the Ultrix User Guide.
3. Select an entry point in the Sources tab from where the new labels and assignments will begin.
a. Double-click the Sources node located under the Database node.
The Sources tab opens.
b. Select the cell of the row for the entry point. The new entries will be inserted below this row.
c. Click Edit > Fill.
The Breakaway Fill dialog opens.
1. Pass through may also be selected. Pass through has the effect of passing through any audio (silence or otherwise) on the channels A5
to A16. Disconnect effectively mutes those channels on the output stream.
Creating Labels with Assignments for SDI and Embedded Audio, with Audio
Breakaways
The objective of this example is to create and insert a series of labels with assignments for SDI video and embedded
audio. Also, audio breakaway sources will be required to implement audio shuffling.
To enable the ability to shuffle audio (that is to take an audio channel and route into another stream in a different
position within that stream), we need to define that audio channel as a source and assign it across all required levels.
For example, we may wish to take channel 3 audio from an input SDI stream, and route (just that individual
channel) to channel 2 of an output SDI stream. To facilitate this, the following definitions are needed;
If only four audio levels are defined as shown in Table 10.4, and assuming no other level definitions, the user can
only route 'SDI 1 ch3' to any of the corresponding levels in the destination, i.e. cannot route 'SDI 1 ch3' to a
destination stream channel 8 as Out[1].audio.ch8 is not defined in any of the destination levels.
To enact the previous example, the user selects the destination channel by selecting the appropriate level button on
the control panel (in this case, the A2 level) before actuating the crosspoint switch (destination button SDIout1,
then, source button SDI 1 ch1). The Advanced Fill tool can automate the creation of these audio breakaway sources
saving a great deal of setup time.
To create source labels with assignments for SDI and embedded audio, with audio breakaways
1. Define one level for SDI Video and 16 levels for the embedded audio as outlined in the section “Defining the
Levels in a Database” on page 67.
2. Select an entry point in the Sources tab from where the new labels and assignments will begin.
a. Double-click the Sources node located under the Database node.
The Sources tab opens.
b. Select the cell of the row for the entry point. The new entries will be inserted below this row.
c. Click Edit > Fill.
The Breakaway Fill dialog opens.
Notice the chx automatic suffix to the label. This may be overridden by placing text in the BRK Suffix cell of the
Breakaway Fill dialog.
Overview
The following information is captured when you archive a database:
• Definitions of levels, sources, and destinations
• Salvos
• Category assignments
• Soft panels
• User assigned port labels
• Current crosspoint status
The following information is not captured: hardware specifics, and license settings.
Exporting a Database
You create an archive of a database (as a *.uda file) using the options in the System Status > Transfer tab.
To export a database to the archive
1. In the Tree View of DashBoard, double-click the System Status node.
The System Interfaces display in the DashBoard window.
2. Select the Transfer tab.
3. Locate the Export area on the tab.
4. Use the Database field to specify the database to export.
5. Click Browse... to specify the location to save the *.uda file to.
The Archive read-only field updates with the selected path and database name.
6. Click Apply.
The Downloading Archive dialog opens to report the status of the export.
Deleting a Database
Ensure the database that you are about to delete is not currently loaded and in use by Ultricore.
To delete a database
1. In the Tree View, double-click the System Status node.
The System interface displays in the DashBoard window.
2. Select the Database tab.
3. From the Delete Database Name menu, select the database you want to delete.
4. Click Database Delete.
Tally Types
Tally information may be associated with either routing system sources or destinations. Below is a summary of the
implementations.
Ultricore does not support Unicode characters.
Source Association
Tally IDs associated with routing system sources may serve two purposes:
1. Trigger any Ultriscape Multiviewers to display tally status (this requires that the Ultrix router has at least one
Ultriscape Head enabled and configured).
2. Enable the tally status to be mapped to other Tally IDs based on router crosspoint status (the destination must
have Tally ID associated and Tally Direct enabled).
To associate Tally IDs to sources in the database
• Use the Sources tab in the Database interface to associate the Tally IDs with logical sources in the Ultricore
database.
• Choose the UMD “Tally Level”.
Destination Association
A Tally ID may be associated with routing system destinations. This enables any tally status associated with router
sources to map to a different Tally ID associated with a router destination, based on current router crosspoint status.
• Use the Destinations tab in the Database interface to associate Tally IDs with logical destinations.
• When a source is switched to a destination on the selected Tally Level, Ultricore forwards the tally status of the
source that is active on the destination, but the outbound TSL message has its display ID re-mapped to the
display ID that is associated with the destination (Tally Redirect is set to ON).
Ensure the destination Tally IDs do not conflict with Tally IDs asserted by other devices.
• When the TallyID is associated with an Ultriscape PiP (slotn.headx-pip[y] or slot0.pip[y]), any assertion on this
TallyID will directly control the PiP tally visual elements and over ride any Tally associated with the PiP video
source (Tally Redirect is set to OFF).
• For switcher support, the label of the connected source to a destination is sent as TSL tally text (TSL v3.1 only
and when Tally Redirect is set to OFF).
Tally ID Format
Table 11.1 summarizes the format that the TSL protocol defines Display IDs that are associated with the tally
displays.
Example
Consider the following source and destination configurations:
For the above configuration settings, the following states are possible:
Getting Started
You must first perform the following in the active database:
1. If RS-232 or RS-422 communication is required, add a serial connection point for either incoming or outgoing
TSL protocol support.
2. Add an Ethernet connection point for outgoing TSL protocol support if not using the serial connection point
described in step 1.
3. Enable Tally ID support.
4. Assign the Tally IDs to the sources.
5. Assign the Tally IDs to the destinations.
6. Set the Tally mode to None.
Before proceeding, ensure you verify which TSL protocol you are using. The protocol determines how you must
enter the information into the Tally cells of the Sources tab. Refer to Table 11.1 for details.
To assign a Tally ID to a source in the database
1. Double-click the Sources node located under the Database node.
The Sources tab opens.
2. Verify that the Tally column displays in the Sources tab. If it does not, refer to the section “Enabling Tally ID
Support in the Active Database” on page 87.
3. Select the cell in the Tally column of the Sources tab to assign the Tally ID to.
4. Type the Tally ID you wish to assign to that source.
5. Press Enter to apply the change.
6. Repeat steps 3 to 5 for each source you wish to assign a Tally ID.
7. Click Apply at the bottom of the Sources tab to save your changes.
Before proceeding, ensure you verify which TSL protocol you are using. The protocol determines how you must
enter the information into the Tally cells of the Destinations tab. Refer to Table 11.1 for details.
To assign a Tally ID to a destination in the database
1. Double-click the Destinations node located under the Database node.
The Destinations tab opens.
2. Verify that the Tally column displays in the Destinations tab. If it does not, refer to the section “Enabling
Tally ID Support in the Active Database” on page 87.
3. Select the cell in the Tally column of the Destinations tab to assign the Tally ID to.
4. Type the Tally ID you wish to assign to that destination.
5. Press Enter to apply the change.
6. Select the Tally Redirect box to enable the connected source Tally ID to be directed to this destination Tally
ID.
7. Repeat steps 3 to 6 for each destination you wish to assign a Tally ID.
8. Click Apply at the bottom of the Destinations tab to save your changes.
The resources need to be arranged into the following groups based on the sport type:
Baseball Football
Once the group categories are defined, the user can perform switches, on a hard or soft panel, based on the group
categories.
In the example below, the user uses RCP-QE18 to select the source labeled as HD 3.
In the example below, the user uses a soft panel to select the destination labeled as SAT 1.
3. Click Apply.
The Move dialog closes and the group displays in the selected position of the tree view.
4. Click Apply in the bottom right corner to apply your changes.
2. In the right pane, select the tab for the type of resource you wish to assign to the group.
Categories Indexes
CAM_ a 1 5 D
SAT_ 2 A E
CG_ 3 B RX_
EDIT_ 4 C TX_
VTR
a. The “_” characters represents a blank space. This indicates the category will filter
resources with a space in the name (e.g. the CAM_ category will allow resources
named CAM 1, CAM 2 but not CAM3).
Once the Cat/Index categories are defined, the user can perform switches, on a hard or soft panel, based on the
categories.
In the example below, a RCP-QE18 is used to select the source labeled as CAM 1. Notice that only the sources are
available for the second button selection. In this example, the user would need to select TAKE to make the switch.
In the example below, an Ultricore soft panel is used to select the destination labeled as CG RX 2.
Assigning Categories
You can assign each destination to a specific category or multiple categories in a database. Using multiple
categories enable you to filter the destinations, and organize them into logical groups. By default, categories are
organized in alphabetical order.
2. Click Generate.
The Auto-Generate dialog opens.
3. Click Yes.
The Auto-Generate dialog closes.
All previous categories are deleted from the Categories pane and new ones are listed based on the resource
labels in your database.
4. Click Apply.
To manually create categories
1. In the Cat/Index Categories tab, click Add.
The Add Category dialog opens.
2. Use the Name field to specify a unique identifier for the new category.
The entry must match a resource name prefix.
Some example entries would be:
• “CG_” creates a category to categorize resources named CG_xxxx where xxxx is any index.
• “CG” creates a category to categorize resources named CGxxxx where xxxx is any index.
• “cg” will not categorize any resources as the category names are case sensitive.
3. Select the Insert trailing space box to represent a space character with the “_” symbol.
4. Click Apply.
The Add Category dialog closes.
The new category is listed in the Categories pane.
5. Click Apply.
Figure 12.8 illustrates direct destination entries and the resulting available destinations in the selected category.
Because we have set the VTRs numbered 6 through 10 in Figure 12.9, the Ultricore expects a two digit entry
signified by the two underlines on the button next to the category name. As only numerals 1 or 0 are the only
possible entries to make for the first digit, the Ultricore has blanked the invalid entry keys. (Figure 12.10)
To select VTR 6, press 0 then the remaining available numbers will become available, then press 6 to finish the
selection.
A soft panel can be as simple or complex in its layout as you require. The Panels interface enables you to specify
the number of destinations, sources, levels, and salvos displayed on your panel. You select a soft panel type and
specify the elements of the soft panel including giving the panel a unique name.
5. To assign all the available levels in the database to the soft panel, click .
6. To assign multiple levels to the soft panel:
a. From the Available list, select the first level you wish to add to the soft panel.
b. Press Shift.
c. From the Available list, select the other level(s) you wish to add to the soft panel.
d. Click .
The Assigned list updates to include the selected levels.
3. Use the Viewable destinations field to specify the total number of destinations for the soft panel.
4. To add a destination to the soft panel:
a. From the Available list, select the destination(s) you wish to add to the soft panel.
b. Click .
The Assigned list updates to include the selected destination(s).
5. To assign all the available destinations in the database to the soft panel, click .
6. To assign multiple destinations to the soft panel:
a. From the Available list, select the first destination you wish to add to the soft panel.
b. Press Shift.
c. From the Available list, select the other destination(s) you wish to add to the soft panel.
d. Click .
The Assigned list updates to include the selected destinations.
7. Use the provided buttons beside the Assigned list to determine the order in which the destinations are
displayed on the soft panel.
8. Click Apply at the bottom of the Panels tab to save your settings.
5. To assign all the available sources in the database to the soft panel, click .
6. To assign multiple sources to the soft panel:
a. From the Available list, select the first source you wish to add to the soft panel.
b. Press Shift.
c. From the Available list, select the other source(s) you wish to add to the soft panel.
d. Click .
The Assigned list updates to include the selected sources.
7. Use the provided buttons beside the Assigned list to determine the order in which the sources are displayed on
the soft panel.
8. Click Apply at the bottom of the Panels tab to save your settings.
3. Use the Viewable salvos field to specify the total number of salvos for the soft panel.
4. To add a salvo to the soft panel:
a. From the Available list, select the salvo you wish to add to the soft panel.
b. Click .
The Assigned list updates to include the selected source(s).
5. To assign all the available salvos in the database to the soft panel, click .
6. To assign multiple salvos to the soft panel:
a. From the Available list, select the first salvo you wish to add to the soft panel.
b. Press Shift.
c. From the Available list, select the other salvo(s) you wish to add to the soft panel.
d. Click .
The Assigned list updates to include the selected salvos.
7. Use the provided buttons beside the Assigned list to determine the order in which the salvos are displayed on
the soft panel.
8. Click Apply at the bottom of the Panels tab to save your settings.
Using a Lock
If your soft panel includes a Lock button, you have the option to protect source/level and destination/level pairs.
When another control panel or DashBoard client attempts to switch that combination, the request will be denied.
To lock a source/level pair
1. Display the soft panel in the DashBoard window.
2. Select the source/level pairs from the soft panel interface.
3. Click Lock.
The label on the button changes to Unlock and the button remains lit.
To lock a destination/level pair
1. Display the soft panel in the DashBoard window.
2. Select the destination/level pairs from the soft panel interface.
3. Click Lock.
The label on the button changes to Unlock and the button remains lit.
To clear a lock
• Click the Unlock button.
The label on the button changes to Lock and the button remains lit.
Using a Protect
A soft panel can be locked by clicking the Protect button. The button is lit until pressed again. A protect alarm
message is displayed in the System Status tab when an output is protected.
This feature protects the currently selected destination/level pair from use by other sources, as well as from other
linked panels. The Protect button is especially useful in instances where a destination must be held after a switch
has been made.
To apply a protect
• Click Protect.
The button is lit. Selecting crosspoints will not take effect and the panel does not update when buttons are
pressed.
To clear a protect
• Click Protect.
The button is no longer lit and crosspoint switches can be initiated.
1. Crosspoints
The number of Destinations and Sources available in the matrix is specified using the Destinations and Sources
interfaces.Click within the matrix or click the Destination and Source buttons to select the crosspoints for
switching the selected levels. In Figure 13.2 crosspoints were selected using the Advanced > Diagonal Presets
option.
2. Levels Button
Click a level button to include the level in the next crosspoint switch. A lit button indicates that the
corresponding level will be included in the next transition. The color and name of the button are specified using
the Levels interface. Figure 13.2 illustrates a Matrix panel with nine levels selected.
3. Follow Button
Click this button to select all crosspoints in the matrix. Clicking TAKE after clicking Follow will then switch all
crosspoints at the same time on all available levels.
4. TAKE Button
Click this button to execute the switch between crosspoints. If you are using a soft panel with the Take
Operation set to Direct, a TAKE button is not displayed because the transitions will occur automatically after a
crosspoint switch is selected.
5. Lock Button
Click this button to prevent switching of the selected crosspoints. If you are using a soft panel with the
Protection Operation set to Disable, the Lock and Protect buttons are not displayed.
6. Protect Button
Click this button to prevent switching of the selected crosspoints except in the DashBoard client session the
Protect was initiated in.
5. Click Take.
The icon on the matrix is solid in the color that matches the level and the TAKE button is no longer lit.
6. Click TAKE.
The icons on the matrix is solid in the color that matches the level and the TAKE button is no longer lit.
To make a crosspoint switch on multiple levels
1. In the Basic Tree View, expand the Soft Panels node for the Ultricore.
2. Double-click the node for a matrix soft panel.
The Matrix Panel tab opens.
3. Select each level from the toolbar or select Follow to include all levels.
4. Select the first source and destination inside the matrix.
5. Select the additional crosspoints to switch.
When multiple levels are selected, the circle on the crosspoint is divided into colored sections with each section
representing a level. In th example below, Levels 2, 4, and 6 are selected with multiple crosspoint selections on
the matrix.
6. Click TAKE.
The icons on the matrix are solid in the color that matches the level and the TAKE button is no longer lit.
Diagonal Presets
Crosspoint selection is organized into a diagonal line that starts with the top left corner of the matrix (e.g. Src 1 and
Dest 1), continues in single step intervals (e.g. Src 2 and Dest 2, Src 3 and Dest 3 etc.) and ends with the bottom
right corner of the matrix (e.g. Src1 6 and Dest 16).
To use the Diagonal Preset
1. Select each level from the toolbar or select Follow to include all levels.
2. Click Advanced > Diagonal Presets.
3. Click TAKE.
R-Diagonal Presets
Crosspoint selection is organized into a diagonal line that starts with the top right corner of the matrix (e.g. Src 16
and Dest 1), continues in single step intervals (e.g. Src 15 and Dest 2, Src 14 and Dest 3 etc.) and ends with the
bottom left corner of the matrix (e.g. Src 1 and Dest 16).
To use the R-Diagonal Preset
1. Select each level from the toolbar or select Follow to include all levels.
2. Click Advanced > R-Diagonal Presets.
2. Use the Repeat Interval field to specify the number seconds the crosspoint switch will continuously loop for.
3. Use the Levels menu to specify the levels the crosspoint will include.
4. Use the Destinations menu to select the outputs on the router.
5. Use the Sources menu to select the input signals to route to the output for the switch.
6. Click Start.
The menu closes and the crosspoint switch begins. The loop continues for the length of time specified in step 2.
To stop the loop, click Advanced > Stop Automation.
1. Destination Bus
Each button in this crosspoint row represents a configured output for the selected router. Selecting a button
includes the destination in the next crosspoint switch. The number of destinations and label for each button is
defined by its entry in the Destinations interface. A destination selected to be included in the next crosspoint
switch will have a lit button. For example, Dest 2 is selected in Figure 13.3.
2. Lock Button
Click this button to prevent switching of the selected crosspoints. If you are using a soft panel with the
Protection Operation set to Disable, the Lock button is not displayed.
3. Take Button
Click this button to execute the switch between the selected crosspoints. If you are using a soft panel with the
Take Operation set to Direct, a TAKE button is not displayed because the transitions will occur automatically
after a crosspoint switch is selected.
5. Clear Button
Clicking this button clears the selections made for the next crosspoint switch in the soft panel interface.
6. Multi Select Button
Clicking this button enables you to perform a switch on multiple crosspoint combinations. If you are using a soft
panel with the Selection Operation set to Single, a Multi Select button is not displayed.
7. Level Button(s)
Click a level button to include the level in a crosspoint that you are configuring in the matrix. A lit button
indicates that the corresponding level will be included in the next transition. The color and name of the button are
specified using the Levels interface. Figure 13.3 illustrates a MultiBus panel with three levels selected.
8. Follow Button
Click this button to select all levels in the matrix. If you are using a soft panel with the Take Operation set to
Confirm, pressing Take after pressing Follow will then switch all crosspoints at the same time on all available
levels.
9. Source Bus
Each button in this crosspoint row represents a configured input for the selected router. Selecting a button
includes the source in the next crosspoint switch. The label for the button is defined by its entry in the Sources
tab of the Database. A source selected to be included in the next crosspoint switch will have a lit button. For
example, in Figure 13.3 the Src 1 is selected for the next transition while the Src 4 is the current source in use.
10.Machine Control Button (not shown)
If you are using a soft panel with the Machine Control set to Enabled, the MACHINE CONTROL button is
displayed. Refer to the section “Enabling Machine Control” on page 108 for details on this button.
7. Click Take.
To make a crosspoint switch using multiple levels
1. In the Basic Tree View, expand the Soft Panels node for the Ultricore.
2. Double-click the node for a MultiBus Panel.
The MultiBus Panel tab opens.
3. Select each level from the toolbar or select Follow to include all levels.
When multiple levels are selected, the center row of the panel reports the level status using a horizontal bar to
represent the level.
4. Select a Src button from the Source bus located at the bottom of the interface.
The button is now lit.
5. Select the Dest buttons for the outputs to include in the crosspoint switch.
The Dest, Preset, and Take buttons are now lit. In the example below, Follow is selected and Dest 5 will
switch with Src 4 on all levels.
6. Click TAKE.
7. Click TAKE.
Figure 13.4 Example of a Group Category Soft Panel for an Ultricore Router
1. Group Window
This area of the soft panel interface may include the following buttons:
› SOURCES, DESTINATIONS Buttons — Clicking one of these buttons updates the button matrix to display the
sources or destinations available as per the selected category. The button labels update to display the source or
destination labels.
› BACK Button — Click this button to return the navigation to the previous category selection (back one level).
› RESET Button — Click this button to clear all selections on the interface. This button is only available on the
Classic Category soft panels.
› SELECT Button — This button is only available on the Classic Category soft panels.
› TOP Button — This button is only available on the Group Category soft panels.
When using a Group Category soft panel and the Info > Non-group Resources setting is set to Hide, only the
resources assigned to a group are displayed on the soft panel.
2. Status Window
The bottom right corner of each soft panel includes a status window. For each level in the list of available levels,
a corresponding status indicator display will indicate the current source for the currently selected destination.
The following buttons are located on the right-side of the soft panel interface:
› Individual Level Buttons — Click a level button to include the level in a crosspoint that you are configuring in
the matrix. A lit button indicates that the corresponding level will be included in the next transition. The color
and name of the button are specified using the Levels interface.
› CURRENT button — This button updates the level display area to show the current status for all displayed
levels.
› FOLLOW Button — Click this button to select all levels in the matrix. Clicking TAKE after clicking Follow
will then switch all crosspoints at the same time on all available levels.
› PENDING button — This button updates the level display area to show status for the currently pending
operation (if selected source has not been switched yet. e.g. before TAKE is pressed). The user may clear
individual source selections by selecting the levels to be cleared, then pressing CLEAR SRC SEL button.
› CLEAR Button — Click this button to clear all selections on the interface.
Figure 13.5 Status Protected — Destination Figure 13.6 Status Protected — User
5. To select a source:
a. Click SRC from the category navigation tools.
b. Select a SRC button from the Source bus located in the middle of the interface.
If your Category soft panel was created with the Take Operation set to Confirm, the TAKE button is lit.
Otherwise the crosspoint switch automatically occurs.
6. Click TAKE.
Figure 13.7 Example of the Default Push Button Soft Panel — Portrait
Figure 13.8 Example of the Default Push Button Soft Panel — Landscape
› — the current status is not the same for all levels (ie a breakaway switch has occurred).
› — the current destination is protected. Only the panel that initiated the protect may switch this
destination.
4. Levels Area
The Levels area displays the available router levels as individual buttons. The current source for a given router
level is displayed each level button. Select a Level button to include this level in the next source selection
operation. Select the button again to toggle the level selection setting.
› FOLLOW Button — toggles the selection for all displayed levels.
› CLEAR Button — toggles the currently active level buttons.
5. Operation Area
This area provides buttons for soft panel and router control.
› PROTECT Button — protect the current destination. The following occurs:
• The destination button displays a blue border.
• The Current Destination area displays . When a destination is protected, only the panel that initiated
the protect can change the destination status.
• The PROTECT button is now labeled as UNPROTECT. Toggle the button to disable the protect.
Only the panel that initiated the protect may change the protect status.
3. Use the Display Icons menu to specify whether buttons will display the default icons based on window type
(Enable) or will only display the label text as determined by the database (Disable).
4. Use the Orientation menu to specify the layout on the monitor. Choose from the following:
• Portrait — orients the soft panel in a horizontal layout, where the soft panel is taller than it is wide.
• Landscape — orients the soft panel in a vertical layout, where the soft panel is wider than it is tall.
6. Click TAKE.
To make a crosspoint switch on multiple levels using the Push Button Panel
1. In the Basic Tree View, expand the Soft Panels node for the Ultricore.
2. Double-click the node for a Push Button Panel.
The Push Button Panel tab opens.
3. Select each level from the Levels window or click Follow to include all levels.
The Level buttons are lit in the toolbar.
4. Select a DEST button from the Destination window.
6. Click TAKE.
Creating Salvos
The Salvos tab enables you to create, delete, re-name, and manage your salvos in an interface that is off-line. The
Salvo tab layout is similar to the Matrix Panel layout where crosspoints are arranged in a grid layout with sources in
columns and the destinations in rows.
To create a salvo
1. In the Basic Tree View, expand the Database node for the Ultricore.
2. Double-click the Salvos node.
The Salvos tab opens.
b. Click the button in the Source toolbar for the source to use for the switch.
The grid updates to indicate the new selections. Notice that each level is represented by a corresponding slice
of the crosspoint indicator. In the case below, there are seven crosspoint switches selected that will affect two
levels.
7. Select the Follow button to enable the levels to automatically follow the switches.
Click Advanced > Clear Dest Presets to cancel the destination selections or click Advanced > Clear All
Presets to clear the workspace.
8. Click Apply.
The salvo settings are updated.
2. In the Basic Tree View, expand the Database node for the Ultricore router.
3. Double-click the Salvos node.
The Salvos tab opens.
6. Click Apply.
To create a salvo based on selected destinations
Editing a Salvo
Once a salvo is created in the database, you can edit its crosspoint selections,
To edit a salvo
1. In the Basic Tree View, expand the Database node for the Ultricore router.
2. Double-click the Salvos node.
The Salvos tab opens.
3. Select the salvo from the Salvos list.
The grid updates to display the crosspoint selections currently saved for the salvo.
4. Perform steps 4 to 7 as outlined in the procedure “To create a salvo” on page 137.
5. Click Apply to save your changes.
To re-name a salvo
1. In the Basic Tree View, expand the Database node for the Ultricore router.
2. Double-click the Salvos node.
The Salvos tab opens.
3. Select the salvo from the Salvos list.
The grid updates to display the crosspoint selections saved for the salvo.
4. Click Edit > Rename.
The Rename Salvo dialog opens.
5. Type a new name for the salvo in the Name field.
6. Click Apply.
The Rename Salvo dialog closes and the salvo displays with the new name in the Salvos list.
Recalling a Salvo
Once you have saved a salvo, you can recall it for use on a soft panel in DashBoard.
You cannot recall salvos from a Category soft panel.
For More Information on...
• adding salvos to customized soft panels, refer to the section “Creating a Soft Panel” on page 108.
To recall a salvo from a Matrix panel
1. In the Basic Tree View, expand the Soft Panels node for the Ultricore router.
2. Double-click the node for a Matrix Panel.
The Matrix Panel tab opens.
3. Click Salvo.
4. Click Recall.
The Execute Salvo dialog opens. Notice that the Active column reports whether the salvo is currently in use
(ON) or not (OFF).
Overview
Introducing an Ultricore to an existing Ross NK system requires specific configuration to enable the Ultricore to
manage the devices in the routing system.
Ultricore does not support Unicode characters.
Connection Diagrams
Figure 15.1 provides an example of a routing system with an Ultricore Central Controller, an NK-IPS, and several
Ross NK devices. Communication between the NK-IPS and the Ross NK devices is over T-Bus, while the Ultricore
communicates with the NK-IPS via Ethernet.
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
Network Switch
PC running DashBoard
NK-IPS
Network Bridge
Service
POWER T-BUS Port
ETHERNET
NK-MD32
Machine Control / Data Router
17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
POWER
RCP-NKM
Remote Control Panel
PSU
T-BUS
RCP-NKQ
Remote Control Panel
PSU
T-BUS
NK-A64
32x32 Stereo Analog Audio Router
T-BUS
29-32 25-28 29-32 25-28
Figure 15.2 provides an example of an Ultricore Central Controller, Ultrix router, NK-NET and various NK
devices.
The NK-NET requires phantom power from the T-Bus to operate. This is available from any Ross NK series
router.
ULTRIX-FR1
32x32 3G/HD/SD SDI Router
ENET 1 ! 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
REF 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 4 A B
OUT IN
Network Switch
PC running
r DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
NK-3G64
64X64 3G/HD/SD SDI Router
T-BUS VIDREF
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
NK-NET
TBUS
RCP-NKM
Remote Control Panel
PSU
T-BUS
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
NK-3G-16
16x16 3G/HD/SD SDI Router
NK-NET
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
TBUS
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
Figure 15.2 Connection Example with Two NK-NETs and an Ultrix Router
All Ross NK routers are automatically discovered1 and appear in the available matrix list ready for label
assignment.
1. Once an ethernet connection point has been established for ethernet connections.
4. In a row of the provided table, type the IP Address of the Ultricore you want to establish a connection to.
Upon a successful connection and a refresh of the current DashBoard view (click the Refresh button), a check
mark displays next to the successful connection. In the above example, an IP Address is entered for Server 1.
5. Verify in the Connections area that a connection is establish.
6. Configure the Remote Control Panel layout as outlined in the user guide for your panel.
It does not matter where the machine control is mapped (either row 3 or 300), but the input and outputs physical
ports must be mapped to the same row ID.
a. In the Basic Tree View toolbar, click to display the Add New Connection dialog.
c. In the IP Address field, enter the IP Address of the Ultricore you noted in step 1.
d. Click Finish to apply your change and close the dialog.
3. Verify that a new node displays in the Basic Tree View. Note that the new node will have the same name as
your Ultricore device (where the default name is Ultricore).
4. Complete the device configuration by double-clicking the device under the IPS node in the tree view. Refer to
the user guide that accompanied your device for configuration details.
ULTRIX-FR2
64x64 3G/HD/SD SDI Router
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
AUX A AUX B
ENET 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
REF 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 4 A B
OUT IN
Network Switch
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
NK-V32-HQ
32x32 Analog Video Router
25 26 27 28 29 30 31 32 25 26 27 28 29 30 31 32
VID REF
17 18 19 20 21 22 23 24 17 18 19 20 21 22 23 24
T-BUS
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
NK-A64
64x64 Stereo Analog Audio Router
61-64 57-60 61-64 57-60
Figure 16.1 Routing System with Legacy Routers and No Remote Control Panels
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET NK-V32-HQ
32x32 Analog Video Router
25 26 27 28 29 30 31 32 25 26 27 28 29 30 31 32
VID REF
17 18 19 20 21 22 23 24 17 18 19 20 21 22 23 24
T-BUS
1 2 3 4 5 6 7 8 1 2 3 4 5 6 7 8
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET NK-A64
64x64 Stereo Analog Audio Router
61-64 57-60 61-64 57-60
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
RCP-ME
Remote Control Panel
ETHERNET
PSU
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
Third-Party Router
Controlled via GVG Protocol
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
Third-Party Router
Controlled via GVG Protocol
Figure 16.4 Using Ultricore to Integrate Existing Routers with a Third-Party Controller
USB
USB
USB
PORT 1
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
NK-NET
T-BUS to Ethernet Adapter
ETHERNET
TBUS
NK-NET
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
RCP-ME
Remote Control Panel
ETHERNET
PSU
PC running DashBoard
Automation Device
Controlled via GVG Protocol
ULTRIX-FR2
64x64 3G/HD/SD SDI Router
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
AUX A AUX B
ENET 1 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
REF 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 4 A B
OUT IN
USB
USB
USB
USB
Ultricore PORT 1
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
RCP-NKM
Remote Control Panel
PSU
T-BUS
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
RCP-ME
Remote Control Panel
ETHERNET
PSU
Third-Party Router
Controlled via GVG Protocol
Caution — Observe T-Bus power limitations. Ultricore has one loop through T-Bus port where
the NK-IPS has eight.
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
RCP-NKM
Remote Control Panel
PSU
T-BUS
RCP-NKQ
Remote Control Panel
PSU
T-BUS
RCP-NKQ
Remote Control Panel
PSU
T-BUS
ULTRIX-FR2
64x64 3G/HD/SD SDI Router
! 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
! 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
AUX A AUX B
ENET 1 ! 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
OUT IN
Ultrix-HDBNC-IO
REF AUX A AUX B
REF 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16
1 4 A B
OUT IN
PC running DashBoard
Ultricore
Central Controller
PSU 1 COM1
T-BUS
PORT 1 PORT 2
PSU 2 ALARM COM2
ETHERNET
RCP-NKM
Remote Control Panel
PSU
T-BUS
NK-3G-16
16x16 3G/HD/SD SDI Router
1 3 5 7 9 11 13 15 1 3 5 7 9 11 13 15
Automation Device
Controlled via GVG Protocol
USB
USB
USB
USB
PORT 1
Ethernet Communication
The Ethernet interfaces to these protocols are automatically started with Ultricore and no further configuration is
necessary. However, you must configure your external control systems to match the settings outlined in Table 9.2.
For More Information on...
• defining an ethernet connection between Ultricore and an external device, refer to the section “Incoming
Ethernet Connections” on page 57.
Serial Communication
If you are using a serial connection, you must first define the serial connection point as outlined in the section
“Defining a Serial Connection” on page 59 and selecting GVG Native or Probel SW-P-08 from the Protocol menu
and the settings as outlined in Table 9.3.
1. Only available natively on the Ultricore Central Controller. Serial connections from Ultrix requires an
external USB-serial converter.
6. From the Device ID drop-down menu, select the device you want to define the logical matrix for. This is the
name given to the device when you established a connection point with it on the Connections tab.
The Device ID menu lists only the third-party devices that have a valid connection point with the Ultricore
router.
7. Define the matrix size as follows:
Protocol Options
Some protocols provide additional configuration options via the Protocol Options dialog. These options can be
accessed via the Protocol Servers table on the Database > Connections interface. Selecting an Options button to
on the table opens this dialog.
The Protocol Options are outlined with the respective protocol details in the following sections.
Table 17.2 summarizes the settings in the Protocol Options dialog for the GVG Series 7000 Native protocol.
Table 17.2 Protocol Options — GVG Series 7000 Native
Option Setting Notes
L4 Echo Yes Send command acknowledgments on
protocol layer 4 (Ethernet only)
No Do not send acknowledgments. This is the
default.
Table 17.3 lists the GVG Native Protocol commands the Ultricore supports.
BK,E,ON Set level 4 echo to on An err=00 response will be returned for successful commands
that do not generate their own response (eg. Take commands).
This is a per session setting.
BK,E,OFF Set level 4 echo to off (default) No response will be given for commands that do not generate
their own response.
QD[,dest_name] Query Destination status by name No information is returned for unmatched destination levels
Qd[,dest_name] Query Destination status by name Sets response src_name to NO_XPT for unmatched
destination levels
QJ[,destIndex] Query Destination status by No information is returned for unmatched destination levels
indexa
Qj Query Destination status by Sets response srcIndex to 0xFFFe for unmatched destination
indexa levels
QN,parameter
QN,S Query source names/labels
RossTalk Commands
The RossTalk protocol is a plain text based protocol that allows control of Ross Video equipment.
Each command should be terminated by a carriage return and a line feed (CR/LF).
To send RossTalk commands to Ultricore
1. Create a network connection to the Ultricore router on Port 7788.
2. At the prompt, enter the commands you wish to send. Refer to Table 17.4 for a list of supported commands.
XPT D:<dest> S:<source> Crosspoint command for a router Range start value must be less than the end value
I:<user_id> [L:<levels>] TAKE where: Single levels and ranges can be mixed in the list (eg.
• <dest> is the logical destination ID L:1,3,4-8,12-17)
from the active database (1-based) There are no spaces between numbers or ranges
• <source> is the logical source ID Invalid numbers or improperly specified ranges will be
from the active database (1-based) ignored
• <user_id> is the numeric An argument is separated from its value using a single colon
user/panel ID that will be used to (:)
request the switch Command arguments are separated single spaces
• <levels> is an optional parameter The arguments may be specified in any order, (e.g. these are
equivalent: XPT D:1 S:4 I:2 and XPT S:4 I:2 D:1)
specifying comma-separated list of
1-based level IDs to switch (for Examples:
breakaway, e.g. L:1,2,4). If no • ID 7 requesting to switch Dest 2 to Source 1 on Levels 1,3,5
levels are specified, a follow and 12-16
switch (all valid levels) is • XPT I:7 D:2 S:1 L:1,3,5,12-16
requested.
• <levels> supports ranges specified
by two numbers separated by dash
(e.g. L:1-16)
Table 17.7 lists the Probel SW-P-08 Serial Protocol commands the Ultricore supports.
17 Protect Device Name Request 18 Protect Device Name Response Get name of device that hold
protect
19 Protect Tally Dump Request 20 Protect Tally Dump Get all protect status
21 Crosspoint Tally Dump Request 22, 23 Crosspoint Tally Dump Get all crosspoint status
Cmd22: Byte max dest 191
Cmd23: Word max. dest.
65535
100 All Source Names Request 106 Source Name Response Get all source names (8 char.
max.)
101 Single Source Name Request 106 Source Name Response Get single source names (8
char. max.)
102 All Destination Association Name 107 Destination Association Name Get destination names (8
Request Response char. max.)
103 Single Destination Association Names 107 Destination Association Name Get single destination name
Request Response (8 char. max.)
105 Single UMD Labels Request 108 UMD Label Response Get single source label (16
char. max.)
120 Crosspoint Connect On Go Group 122 Crosspoint Connect On Go Group Add crosspoint to preset
Salvo Salvo Acknowledge group
121 Crosspoint Go Group Salvo 123 Crosspoint Go Done Group Salvo Switch/clear preset group
Acknowledge
124 Crosspoint Salvo Group Interrogate 125 Crosspoint Group Salvo Tally Preset group status
EXTENDED
129 Extended Crosspoint Interrogate 131 Extended Crosspoint Tally Get crosspoint status
130 Extended Crosspoint Connect 132 Extended Crosspoint Connected Take single crosspoint
138 Extended Protect Interrogate 139 Extended Protect Tally Get destination protect status
140 Extended Protect Connect 141 Extended Protect Connected Protect a destination
142 Extended Protect Disconnect 143 Extended Protect Disconnected Turn off protect for a
destination
147 Extended Protect Tally Dump 148 Extended Protect Tally Dump Message Get all protect status for
given level
149 Extended Crosspoint Tally Dump 151 Extended Crosspoint Tally Dump Word Get destination status for
Message given level
228 Extended All Source Names 234 Extended Source Name Response Get source names (8 char
max.)
229 Extended Single Source Name 234 Extended Source Name Response Get single source name (8
char max.)
230 Extended All Destination Association 235 Extended Destination Association Get all destination names (8
Names Names Response char. max.)
231 Extended Single Destination 235 Extended Destination Association Get single destination name
Association Name Names Response (8 char. max.)
232 Extended Single UMD Label Request 236 Extended UMD Labels Response Get all source labels (16 char.
max.)
233 Extended Single UMD Label Request 236 Extended UMD Labels Response Get single source label (16
char. max.)
248 Extended Crosspoint Connect On Go 250 Extended Crosspoint Connect On Go Preset group acknowledge
Group Salvo Group Salvo Acknowledge
124 Crosspoint Group Salvo Interrogate 253 Extended Crosspoint Group Salvo Tally Preset group status
NVISION Commands
Ultricore supports the NVISION NP16 Ethernet protocol.
Ensure that the Ultrix router has the Ultricore-NVISION license installed. Refer to the Ultrix User Guide for
details.
NP16 Commands
The NP16 protocol defines the message format: Protocol ID | Sequence Number | byte count | Command
Each field consists of a 32bit number where:
• Protocol ID — 0x0000000C (Router Control Protocol)
• Sequence number — controller generated and added to Ultricore response message
• byte count — total number of bytes in message including header (<8176)
• Command — refer to Table 17.10
The protocol is zero based, meaning that destination 0 in the protocol relates to destination ID#1 in Ultrix. This is
true for sources, destinations, and level values.
Refer to Table 17.10 for a list of supported NP16 commands.
0x58 Release destination lock/protect Releases the destination lock and protect
a. Green/Red may be swapped by configuring the Global Tally Settings in the Ultriscape
Head interface for an Ultrix router. Refer to the Ultrix User Guide for details on these
settings.
Protocol Implementation
Ultricore implements the protocol with the following structure: Header | Control | DisplayData | VBC | XData.
Table 17.16 lists the TSL UMD Protocol v4.0 commands the Ultricore supports.
Display Data 16 ASCII display characters (20h - 7Eh) UMD display text
VBC
Bit 7 0
XData1
Bits 2-3 Text display valuea Sets PiP label (UMD) text background color
Bits 4-5 Left hand tally valuea Displayed in either border or text
background; can be either or both
Bit 6 Reserved
Bit 7 0
XData2
Table 17.18 summarizes the settings in the Protocol Options dialog for the TSL UMD v5.0 protocol.
Table 17.18 Protocol Options — TSL UMD v5.0 protocol
Option Setting Notes
Wrapping Yes Wrap commands for TCP mode
No Do not wrap commands (UPD mode). This
is the default.
PBC in Count Value Yes Include the Packet Byte Count field when
calculating the byte count value
No Do not include the Packet Byte Count field
in the byte count value. This is the default.
Protocol Implementation
Ultricore implements the protocol with the following structure: PBC | Ver. | Flags | Screen | DMSG (Index, Control,
Length, Text).
Table 17.19 lists the TSL UMD Protocol v5.0 commands the Ultricore supports.
Bits 2-3 Text display valuea Sets text background and border color
Bits 4-5 Left hand tally valuea Sets left-hand tally indicator color
02 Crosspoint Connect
12 Protect Connect
14 Protect Disconnect
104 All UMD Labels Request UMD Label Response Only one set of labels is
currently supported. UMD
Labels replicate source
labels.
5. Use the SNMP Trap Destination IP Address field to specify the target address to which traps should be sent.
An example of a valid target is provided in the SNMP area.
Establishing a Connection
To establish a connection between the Ember+ client and the Ultricore
1. Configure your network streams as outlined in the Ultrix User Guide.
2. Configure your router database as outlined in “Database Configuration” on page 63.
3. Install the Ultricore-EMBER+ license on the Ultricore. Refer to “Software License Keys” on page 39. This
enables the Ultricore to start an Ember+ server and listen to incoming connections.
4. Add the Ultricore in the Ember+ control system interface using the IP Address assigned to the Ultricore.
5. In the Ember+ controls system, set the TCP port to 9000 for the Ultricore.
3. Use the Ember Plus menu to specify the operation mode required by your Ember+ control system. Choose
from the following:
• Virtual Mode — each level is represented by a Matrix and the Labels will be the one defined in the
Destinations and Sources tabs.
Supported Commands
We support the Get Directory and Connect commands. The router is represented using the Ember+ Matrix
object including Labels. This allows the Ember+ control system to see the number of levels, number of sources and
destinations and their labels, the per destination status, and issue switch commands.
If you make changes to the router database (such as Levels, Destinations and Sources) after establishing
communications, you may need to refresh/reload/reconnect the connection.
Primary Status
If the Ultricore is configured as a primary, the Ultricore Clients table in the Communication Settings interface
reports on the status between it and each client device connected to it. Each client is listed in the table, with the most
recently connected device displayed at the bottom of the list.
Client Status
If the Ultricore router is configured as a client, the Communication Settings interface reports on the
communications between it and the primary.
Troubleshooting
If you have lost communication between the primary Ultricore and its clients:
1. Verify that each device is installed correctly.
2. Verify that each devoce is installed with a network connection to your facility.
3. Verify the Ethernet settings for each device are valid.
4. Verify that the primary Ultricore reports a list of valid connections to clients in its Ultricore Clients table.
5. Verify that each client Ultricore is running software compatible to the primary Ultricore.
3. Expand the Panels sub-node to display a list of remote control panels communicating with Ultricore.
All remote control devices communicating with Ultricore are listed under the Panels sub-node.
Up
Back Forward
Down
Figure 18.2 Positioner Movement
If you have any questions pertaining to the installation or operation of Ultricore, please contact us at the numbers
listed in the section “Contacting Technical Support” on page 16. Our technical staff is always available for
consultation, training, or service.
Ultricore in DashBoard
Ultricore groups the configuration, monitoring, and operating features in a Tree View in the DashBoard client
window. Each node of the tree opens to reveal one or more sub-nodes, giving access to the configuration options for
your system.
Ultricore includes the following interfaces, as separate nodes, in the DashBoard Tree View.
System Status
Double-clicking the System Status node displays two types of tabs within the same DashBoard window: Status
(read-only) tabs located on the left, and a series of Configuration tabs located on the right. This interface is similar
to an openGear® card tab system.
Database
Expanding the Database node enables you to configure the connection points, matrices, destinations, sources,
groups, levels, soft panels, and salvos for the system. The settings are saved locally on the Ultricore.
Devices
The sub-nodes under Devices provide a list of external devices in the routing system currently communicating with
the Ultricore.
Soft Panels
The Soft Panels tree provides access to the Matrix, MultiBus, and Category soft panels for the Ultricore. From these
panels you can perform crosspoint switches, and manage salvos via a DashBoard interface.
Status Tabs
The Status tabs display read-only information about the Ultricore hardware and software.
Product Tab
Table 19.1 summarizes the read-only information displayed in the Product tab.
Other Tab
Table 19.2 summarizes the read-only information displayed in the Other tab.
Configuration Tabs
The Configuration tabs of the DashBoard window provide network setup options for the Ultricore panel and
managing the Ultricore databases.
Network Tab
Table 19.3 summarizes the fields and menus displayed in the Network tab. The options in the Network tab are
organized into two sections: Settings (editable fields), and Ethernet Redundancy (read-only fields).
a. The Levels, Sources, and Destinations fields indicate the initial values when the database was
created. Levels, Sources, and Destinations can be removed from or added to the database on
their respective configuration tabs. Doing so will not alter the fields in the Database tab.
b. This message displays for a maximum of 10 seconds only.
Transfer Tab
Table 19.5 summarizes the options displayed in the Transfer tab.
Table 19.5 Transfer Tab
Item Parameters Description
Export
Database: <database name> Selects the database to be exported
Save As: *.uda Automatically updates with the name of the database
archive
Browse... Enables you to save or re-name the database to a
specific location. The default location is
Apply Click to begin exporting the file to specified location
Import
Archive File: *.uda Indicates the last file that was imported
Browse... Enables you to specify the database to import
Retrieve Database As: <database name> Indicates the file currently selected for importing
Apply Click to begin the import
Logs Tab
This tab includes the System Log, Controller Communications Log, and DashBoard Communications Log. The
read-only information displayed in the logs is used by Ross Technical Support for diagnostic purposes.
Database Interfaces
The Database interfaces enable you to configure devices in your routing system and configure control aspects for
Ultricore. Note that the currently active database name is displayed in parentheses in the tree view. Unicode names
are also supported so that names may be defined in other languages or writing systems.
Most of the interfaces are organized into a table format with a row of buttons at the bottom of the interface. You can
select individual cells, columns, or rows of entries to define.
A summary of each interface is provided in the following sub-sections.
Database Builder
The Database Builder interface helps you to quickly create a database by grouping basic controls on four pages:
Quick Start, Levels, Destinations, and Sources. The same controls are available as sub-nodes of the Database
interface.
Quick Start
The Quick Start options display by default when the Database Builder displays in DashBoard. From this page you
can define the database properties including: type of signals (video, audio) the number of Ultricore routers that the
database includes, the audio elements of the database, and basic UltriScape parameters.
Table 19.8 summarizes the fields displayed in the options in the Quick Start page.
Table 19.7 Database Builder — Quick Start
Item Parameters Description
Database name <name> Assigns a unique identifier for the device in the routing
system. This name is also used when matrices are defined in
the Ultricore system.
Frame select table Displays a list of detected routers in your network. Select a
box to apply the database to the specified router.
Include AUX ports None Do not create entries for AUX ports in the database
Insert at slot Create AUX port entries as they are physically located
within the Ultricore chassis (e.g. ports 17 and 18).
At the end Create AUX ports after BNC entries
Video support Yes Creates a database that includes video and audio signals
No Creates an audio-only database
Audio channels # Specifies the quantity of audio channels (levels) required
Breakaway source Yes Create sources for audio breakaways/shuffles
support
No Audio breakaways are not included in this database
SDI audio per channel Creates audio breakaway sources using the selected audio
channel grouping size
MADI channels per Creates MADI sources using the selected audio channel
source grouping size
Disconnect source? Yes Creates a source that will disconnect (mute) SDI and audio
channels
No This option is not included in the database
Passthrough source? Yes Sources are routed without changes/edits
No This option is not included in the database
Levels
Once you defined the options on the Quick Start interface, you can proceed to preview and customize the levels,
destinations, and sources this database will include. Clicking Next on the Quick Start page displays the Levels
page. (Figure 19.5)
The options in the Levels page are organized into a table where each row represents a level and the columns provide
the options for configuring that level. From this page you assign a unique name to each level, a color that represents
the level to make it easier to identify the level in a soft panel.
Destinations
Clicking Next on the Levels page displays the Destinations page. (Figure 19.6)
The Destinations page enables the assignment of logical labels (used by remote control panels and soft panels) to
physical outputs of the attached matrices or routers. The options in the Destination page are organized into a table
where each row associates a name of the destination with one or more logical matrix output sockets.
Sources
Clicking Next on the Destinations page displays the Sources page. (Figure 19.7)
The Sources page enables the assignment of labels (used by remote control panels and soft panels) to inputs of the
attached matrices or routers. The options in the Sources page are organized into a table where each row associates a
name of the source with one or more logical matrix input sockets.
Clients Table
The Clients table lists the connection details of remote client devices (e.g. external devices connecting to this
Ultricore) currently communicating with the Ultricore.
Table 19.8 summarizes the read-only fields displayed in the Clients table in the Connections tab.
Table 19.8 Connections Tab — Clients
Item Parameters Description
Device ID <name> Specifies the external device for the connection
point
Name <name> Assigns a unique identifier for the device in the
routing system. This name is also used when
matrices are defined in the Ultricore system.
Protocol GVG Native The device uses the third-party GVG protocol to
(read-only) communicate.
Refer to “GVG Series 7000 Native Protocol
Commands” on page 163.
NVISION This device communicates via the third-party
NVISION protocol. Refer to “NVISION
Commands” on page 168.
OGP This device uses the openGear Protocol to
communicate with Ultricore.
Probel SW-P-08 The device uses the third-party protocol known as
Probel SW-P-08.
Servers Table
The Servers table lists the connection details of external devices that Ultricore has established a connection point to
(e.g. devices that are controlled by this Ultricore). Entries in the Servers table are managed by the user as outlined in
the chapter “Device Communication Setup” on page 51.
Table 19.9 Connections Tab — Servers
Item Parameters Description
ID # Auto-numbered field (read-only).
Device ID <name> Specifies the external device for the connection
point
Name <name> Assigns a unique identifier for the device in the
routing system. This name is also used when
matrices are defined in the Ultricore system.
Table 19.10 summarizes the options displayed in the Third Party Matrices tab.
Table 19.8 summarizes the options displayed in the main area of the Port Labels tab (from left to right on the
interface).
Bottom Toolbar
Refer to Table 19.35 for a summary of the buttons displayed in the Bottom toolbar of the Database interfaces.
Levels Tab
A level is a specific grouping of signal input and output ports, that may be controlled separately from other groups
(a breakaway). Typically a level is associated with input/output ports that are used with sets of similar or related
signals, such as SDI Video, AES Audio, Analog Video, Analog Audio, Timecode, or Machine control, and often
include routing matrices that are dedicated to controlling that specific type of signal.
The options in the Levels tab are organized into a table where each row represents a level and the columns provide
the options for configuring that level. From this tab you can assign a unique name to each level, a color that
represents the level, and a textual description of the level to make it easier to identify the level in the soft panels.
Sources Tab
The Sources tab enables the assignment of labels (used by remote control panels and soft panels) to physical input
sources to specific sources based on the routers connected to the Ultricore (and listed in the Database interface).
The rows in the table are dependent on the database that is currently loaded. The Sources tab is organized into a
table where each row associates a name of the source with one or more logical matrix input sockets.
Categories Area
Table 19.14 summarizes the options displayed in the Categories area of the Cat/Index Categories tab.
Indexes Area
Table 19.16 summarizes the options displayed in the Indexes area of the Cat/Index Categories tab.
The Group Categories tab is organized into three panels and a bottom toolbar.
Table 19.18 summarizes the options displayed in the left panel of the Group Categories tab. This panel displays all
the created groups and sub-groups, and/or resources in a top-down hierarchy. Note that the nodes are sorted by type
and then by alphabetical order.
Table 19.20 summarizes the options displayed in the right panel of the Group Categories tab. This panel displays
the available destinations, sources, and levels that can be arranged into group categories.
Salvos Tab
A salvo is a set of pre-defined switch events. The Salvos tab provides a list of the global salvos available in the
currently selected database. From this tab you can create salvos, rename, and delete salvos.
The workspace in the Salvos tab displays a grid pattern with sources at the top and the destinations along the left
side. A list of currently available (saved) salvos displays on the far left-side of the tab. The toolbar on the far
right-side displays a button for each level available in the database with each button set in the color specified for the
level. The toolbar in the bottom right corner of the interface displays three buttons: Advanced, Cancel, and Apply.
Advanced Menus
Clicking the Advanced button in the Salvos tab displays the options outlined in Table 19.25.
Users
When the system is configured to use the user login mechanism, a list of all currently configured usernames along
with their current online status displays in this area.
Profiles
A list of all currently configured profiles. Selecting a profile (row) in this area automatically updates the items
displayed in the Profile Details, Device Tree, and Options areas.
Profile Details
This area displays the details of the profile showing the conditions under which the tree in the following section will
be applied.
Tree Nodes
A visual representation of the tree view that is defined in the Profile Details. Note that certain entries that are
specific to licenses or other conditions may be visible but not in the actual tree view. Should conditions change that
enable those entries, they will appear as shown in this display. A profile also maintains the position of items in
groups allowing the most relevant items to be the easiest to reach.
The tree nodes are organized in a hierarchy where the top level (blue icons) list system specific options, and
secondary levels (yellow icons) list specific functions.
This area only displays when the ULTRICORE-PRO license is enabled.
Group Tabs
This area displays all the available items that have not yet been assigned to the currently selected profile but are
available to define.
This area only displays when the ULTRICORE-PRO license is enabled.
Panels Menu
The Panels menu displays on the left side of the interface. This menu provides a list of soft panels saved in the
current database. Selecting a soft panel from the list updates the tab entires in the Panels tab with the settings for
that soft panel.
Info Tab
Use the options in the Info tab to assign a panel a unique identifier, select the panel style template to use, and how
the panel will perform tasks such as Take transitions. This is the default tab that the interface opens on. Table 19.26
summarizes the fields and menus displayed in the Info tab.
a. This menu is only available when the Panel Style is set to Group Category.
Levels Tab
Use the options in the Levels tab to specify the number of levels for the panel, and organize them in a hierarchy for
the panel. Table 19.27 summarizes the fields and menus displayed in the Levels tab.
Sources Tab
Use the options in the Sources tab to specify which router inputs will be available in Source bus of the soft panel,
and their hierarchy. Table 19.29 summarizes the fields and menus displayed in the Sources tab.
Table 19.29 Sources Tab
Item Parameters Description
Viewable <integer> Specifies the maximum number of sources, as
Sources selectable buttons, on the panel. This field is not
displayed when the Panel Style is set to Group
Category or Cat/Index Category.
Available <integer> Lists all the sources in the current database
Assigned <integer> Specifies which sources will be available in the
soft panel
Salvos Tab
Use the options in the Salvos tab to specify the total number of salvos displayed in the soft panel and their
hierarchy. Table 19.30 summarizes the fields and menus displayed in the Salvos tab.
Table 19.30 Salvos Tab
Item Parameters Description
Viewable # Specifies the maximum number of salvos that will
salvos be listed on the Recall Salvos dialog for the panel.
This field is not displayed when the Panel Style is
set to Matrix.
Available # Lists all the salvos in the current database
Assigned # Specifies which salvos will be available in the soft
panel
Favorites Tab
The Favorites tab only displays when the Panel Style is set to Ultritouch PB.
Buttons
Table 19.33 summarizes the buttons displayed in all Panel sub-tabs.
In the Available area, clicking this button toggles the sorting order between
alphabetical or database-index (based on the current order listed in the Levels,
Destinations, or Sources tabs)
Moves the selected items in the Available list to the Assigned list.
Moves the selected item(s) from the Assigned list back to the Available list. These
items will not be available in the soft panel window.
Moves all the available labels to the Assigned list
Removes all the items from the Assigned list back to the Available list. These items
will not be available in the soft panel window.
Up Moves the selected item in the Assigned list up one position. This changes the
order of the displayed items on the soft panel.
Down Moves the selected item in the Assigned list down one position. This changes the
order of the displayed items on the soft panel.
Top Moves the selected item in the Assigned list to the top of the list. This changes the
order of the displayed items on the soft panel.
Bottom Moves the selected item in the Assigned list to the bottom of the list. This changes
the order of the displayed items on the soft panel.
In the Assigned area, clicking this button arranges the items into alphanumerical
order.
In the Assigned area, clicking this button arranges the items in the Assigned list
according to the order established in the Levels, Destinations, or Sources tabs.
Bottom Toolbar
The bottom toolbar of each tab in the Database includes buttons for applying changes made to settings in the
interface, or adding elements to the table in the interface. Table 19.35 summarizes the buttons displayed in the
Bottom toolbar. Note that not all buttons display in all tabs.
Table 19.35 Bottom Toolbar Items
Button Description
Edit Displays the Edit dialog for the tab. Refer to Table 19.36 for details.
Find Displays the Find dialog that enables the entering of criteria for searching of the
tab contents.
Fill Label Applies a custom label to the selected port
Reset Label Reverts the label content to the previously saved text
Delete Removes the selected port from the list for the matrix
Add Adds the selected port from the list for the matrix
Cancel Discards any recent changes made in the tab, and reverts to the previously saved
table settings.
Apply Applies changes made in the tab and updates the Ultricore database
Deletea When working in an interface with a table layout, clicking this button removes the
currently active row from the table.
When working in an interface with lists on the left toolbar, clicking this button
removes the selected item from the list. You will still need to click Apply to
completely remove the item from the database.
Fill A range of name cells may be filled with consecutive numerical data. For example,
VTR1 to VTR4 may be entered quickly by defining a prefix (in this case VTR) and
a suffix that will numerically increment.
Selecting Fill from the Insert toolbar, a dialog displays prompting you to enter a
prefix (alphanumeric) and the start/end numerical values.
This method adds rows to the destination table inserting below the active row.
Fill & Replace Enables you to overwrite a range of cells in the table. Rows beneath the currently
active row are overwritten with data from the Fill & Replace dialog.
Insert Above Inserts a new row above the currently active row in the table. Any existing data is
moved down the table by one row.
Insert Below Inserts a new row below the currently active row in the table. Any existing data is
moved up one row.
Insert Series Inserts a sequential range of labels below the currently selected row.
Paste Pastes the copied cell data from the clipboard. In some interfaces, such as in the
Salvo tab, the copied salvo settings are pasted in entirety.
Paste Below Pastes the copied cell data, from the clipboard, to currently selected cell.
Rename When working in an interface with lists on the left toolbar, clicking this button
enables you to provide a different name/label to the selected item.
Reset All IDs Resets the source/destination ID numbers based on their current row number.
It is recommended to verify the interfaces that referenced IDs (such as Soft Panels,
Salvos, etc.)
a. Ensure the ID numbers are correctly sequenced when deleting and inserting entries in the tabs.
Refer to the Reset All IDs row in this table.
BRK I/O Select the box to insert a label with this I/O assignment on
all BRK Level selections.
For example, IN 1 ch1 | slot1.in[1].audio.ch1 |
slot1.in[1].audio.ch1 | slot1.in[1].audio.ch1.
BRK Level Select the box to include this level when creating a
breakaway label. For example, IN 1 ch1.
BRK Suffix <text> By default, breakaway label naming uses the chx part of the
Ultricore name. A user defined suffix may be entered here.
Assign Click this button to automatically fill the I/O Assignment
column based on the Slot, Port, Starting Channel settings
to the selected row(s).
a. The Breakaway Fill dialog uses the default naming convention of FrameName.slot
n.in/out[p].type.chx.
Table 19.39 summarizes the options displayed in the Destinations Fill dialog.
Table 19.39 Destinations Fill Dialog
Item Parameters Description
Fill Custom Insert labels with assignments for a custom range defined
by the Range setting
Entire Slot Insert labels with assignments for a single router slot
Entire Device Insert labels with assignments for the entire router/device
Name <text> The prefix for the label creation. For example, typing VTR
results in labels VTR 1, VTR 2, etc.
Take care when determining label names. While a long
name may be nice and descriptive for the Destination tab,
many control devices have limited screen space and labels
may be truncated.
Starting # The starting numerical extension for the label creation. For
example, typing 3 results in labels Name3, Name4, etc.
Range # Specifies the quantity of labels for custom fill range
Slot # The Ultricore slot number to start the label assignment
froma
Port # The Ultricore port to start the label assignment froma
a. The Fill Destination dialog uses the default naming convention of FrameName.slot
n.in/out[p].type.chx.
Devices Interface
The Devices node summarizes the hardware components of the routing system. The nodes represent a hierarchy of
the routing system communicating with the Ultricore.
Frame Information
Below the Frame Inventory table are the fields that report status information on the Ultricore hardware such as the
version of the system firmware and reporting the current date and time. From this area you can also specify the NTP
Server to be used as the time source for the Ultricore.
Alarms
From the Alarms table you can specify what components the Ultricore monitors such as the SD Card, the chassis
battery, and the ENET ports.
By default, the Ultricore monitors the following components (these options in the Alarms table are enabled):
• SD Card Free Space
• SD Card Presence
• Battery
The Alarms table also displays read-only State column that reports the status of each enabled alarm using color
indicators which vary in severity from green (valid), yellow (caution), to red (alarm). For example, if the SD Card
status is set to red in the Alarms table, an SD Card is not detected or the SD Card not mounted correctly inside the
chassis.
Communication Settings
The Frame Communications area enables you to monitor the status of the Ethernet connections of the Ultricore.
From here you can verify the network settings of the active Ethernet port on the chassis, and view the mode of the
control system (primary/client).
Serial Ports
The Serial Ports area enables you to monitor the COM1 and COM2 ports on the Ultricore chassis. Each enabled
alarm using color indicators which vary in severity from green (valid), yellow (caution), to red (alarm).
Panels
The Panels node provides a list of physical remote control panels within the routing system. For example, if you
have any RCP-ME or an RCP-QE setup in your system, each device would display as a sub-node under the Panels
node. Double-clicking the sub-node updates the DashBoard client window with the interface for that remote control
panel.
Matrix Panel
The Matrix Panel provides a visual representation of multi-level crosspoints, in a grid layout, and offers a
convenient and easy way to select and switch crosspoints. The columns of the grid represent the configured Sources
and are labeled with the labels specified in the Input Name cells of the Sources tab. The rows of the grid represent
the configured Destinations and display the labels specified in the Destination tab.
Right-side Toolbar
Table 19.40 summarizes the buttons displayed in the toolbar on the right-side of the interface.
Table 19.40 Matrix Panel Toolbar Items
Button Description
Level # Each configured level in the currently active database is represented with a button.
When selected, the button is lit with the color assigned to the level. Crosspoint
selections on the matrix are also lit this color when the level is included in the next
switch.
Follow Automatically selects all the Level buttons listed on the Matrix panel (buttons are
now lit). All levels are now included in next crosspoint selection.
TAKE Performs a Take transition to the next crosspoint selection.
Lock Locks the Matrix panel from all switches or function button operation.
Protect Protects the currently selected source/destination level pair from use by other
sources, as well as from other linked panels.
Free Removes the Lock and Protect from the next crosspoint switch.
Salvo Menus
Table 19.41 summarizes the options displayed in the Salvo menu.
Table 19.41 Matrix Panel — Salvo Menus
Button Description
Recall Recalls and applies the last saved salvo settings.
Edit Enables you to load a salvo, update its settings, and then save your changes.
Save Saves the current crosspoint selection as a local salvo.
Capture Current Status Automatically creates a salvo based on the currently selected destination and
source positions.
Capture Dest Status Automatically creates a salvo based on the currently selected destination positions.
Advanced Menus
Table 19.42 summarizes the options displayed in the Advanced menu.
Table 19.42 Matrix Panel — Advanced Menus
Button Description
Clear All Presets Removes all selections currently made on the soft panel and returns the panel to its
default destination and source selections.
Clear Dest Presets Removes only the selections made on the Destinations bus. No destination buttons
are selected.
Diagonal Presets The destination and source crosspoint selections are automatically made starting at
the top left corner and progressively moving down the grid in a 1:1 pattern. For
example, Src1 and Dest1, Src2 and Dest2, Src3 and Dest3 etc.
R-Diagonal Presets The destination and source crosspoint selections are automatically made starting at
the top right corner and progressively moving down the grid in a 1:1 pattern. For
example, Src10 and Dest1, Src9 and Dest2, Src8 and Dest3 etc.
Setup Automation Automatically loops the crosspoint switches for the specified length of time.
Stop Automation Stops the automatic loop of crosspoint switches that was initiated using the Setup
Automation option.
MultiBus Panel
The MultiBus Panel provides breakaway control and status monitoring of several destinations simultaneously. The
MultiBus Panel interface is organized into two buses with a central status row of indicators for the levels. The
toolbar on the far left of the interface provides options for locking and protecting crosspoints, setting up the
transition, and selecting the levels. The bottom row of the interface is populated with buttons for the salvos defined
in the database.
Left Toolbar
Table 19.43 summarizes the fields and information displayed in the left toolbar of the MultiBus Panel.
Table 19.43 MultiBus Panel — Left Toolbar Items
Button Description
Lock Locks the MultiBus panel from all switches or function button operation.
Take Performs a Take transition to the next crosspoint selection.
Preset Enables you to configure a crosspoint switch that will not take effect until the Take
button is selected.
Clear Clears the selections in the crosspoint buses. No buttons are lit and the fields in the
Destination buses are blank.
Multi Select Enables you to assign a single source to multiple destinations for a multi-switch
configuration.
Level # Each configured level in the currently active database is represented with a button.
When selected, the button is lit with the color assigned to the level. Crosspoint
selections on the matrix are also lit this color when the level is included in the next
switch.
Follow Automatically selects all the Level buttons listed on the Matrix panel (buttons are
now lit). All levels are now included in next crosspoint selection.
Destinations Bus
Each Destination is represented as a distinct box on the top bus of the MultiBus Panel. Figure 19.24 provides an
example of a Destination bus. The Destination bus only displays the destinations specified when the soft panel was
configured.
Table 19.44 summarizes the buttons displayed for each Destination in the MultiBus Panel.
Table 19.44 MultiBus Panel — Destination Items
Button Description
Name The Destination name/label is reported at the top of each area and displays as a
selectable button. This enables for quick identification on the bus when selecting
crosspoint switches.
The Destinations available on the bus is dependent on the database currently
loaded on the router and how many destinations were specified when the soft panel
was configured.
Level # This field reports the level(s) that the destination was associated with on the last
crosspoint switch.
Source # This field reports the source(s) currently selected on the Source bus located near
the bottom of the MultiBus Panel interface.
Lock Locks the Destination from all switches or function button operation.
Protect Protects the currently selected Destination from use by other sources, as well as
from other linked panels.
Sources Bus
Each Source is represented as a distinct button on the bottom bus of the MultiBus Panel. Figure 19.25 provides an
example of a Source bus. The Source bus only displays the sources, and in the hierarchy, specified when the soft
panel was configured.
Category Panel
There are two types of Category Panels: Classic and Group. Each Category Panel organizes the sources and
destinations according to the definitions set in the applicable Category interface for the database. The top toolbar is
used in conjunction with the central button matrix for selecting sources and destinations. The left side of the
interface provides access to level selection, and reports on the breakaway status with fields for each level. Some
functions are category type specific. Refer to the section “Using Category Panels” on page 125 for details.
Ultritouch PB Panels
You can control an Ultrix router via Ultritouch by loading a saved soft panel using the Ultritouch hard panel
interface. Loading a soft panel to Ultritouch requires a similar method as loading a soft panel in the Ultrix and/or
Ultricore menu system. You select the device in the Ultritouch > All Connections interface, navigate to the specific
soft panel you wish to load, and select it from the provided list.
Ethernet Ports
Each Ethernet port uses a single 9-pin, RJ45 connector to interface with a local network, RCP-ME, RCP-QE, and
other devices that use an ethernet protocol for communications. The Ethernet ports are operated in a link aggregated
or bonded configuration to provide failover functionality.
Specifications
Table 20.1 Technical Specifications — Ethernet Ports
Item Specifications
Standards Accommodated 1000BASE-T (GbE) network
Connection RJ45
ALARM Connector
The ALARM connector on the Ultricore rear panel is used to configure alarm during loss of power to the panel.
Specifications
Table 20.2 Technical Specifications — GPO Alarm Port
Item Specifications
Alarm Mechanical relay normally closed output
Connection 3-pin header
Pinouts
Refer to Figure 20.2 and Table 20.3 for the pinout assignment of the ALARM port on the Ultricore rear panel.
321
ALARM
Figure 20.1 ALARM Connector on Ultricore Rear Panel — Pinouts Assignment
2 Alarm Output
Refer to Figure 20.2 for the signal pinouts for the 3-pin connector plug.
Connector
Tie Wrap
(without cable)
Cable
Serial Ports
The COM 1 and COM 2 ports on the Ultricore rear panel are used to connect to a third-party device that
communicates via a supported serial protocol.
Specifications
Table 20.4 Technical Specifications — Serial Ports
Item Specifications
Standards Accommodated RS-232/RS-422 (switchable) serial
Maximum Baud 115200
Connection DB9 female
Pinouts
This section outlines the signal pinouts for the two COM ports.
2 Tx -Rx
3 Rx +Tx
4 N/C N/C
5 Ground/shield Ground/shield
6 N/C N/C
7 N/C +Rx
8 N/C -Tx
9 N/C N/C
Specifications
Table 20.6 Technical Specifications — T-Bus Ports
Item Specifications
Standards Accommodated Ross Video proprietary T-Bus
Cabling Type CAT3 or better
Connection 8P8C modular jack
Pinouts
This section outlines the signal pinouts for the two T-Bus ports.
2 Ground
3 +Tx/Rx
4 N/C
5 N/C
6 -Tx/Rx
7 +15 VDCa
8 +15 VDCa
a. 7W total for both ports and not 7W each.
BSD
Copyright (c) 1991,1993, The Regents of the University of California. All rights reserved.
Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.
2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other
materials provided with the distribution.
3. <BSD Advertising Clause omitted per the July 22, 1999 licensing change ftp://ftp.cs.berkeley.edu/pub/4bsd/README.Impt.License.Change> California, Berke-
ley and its contributors.
4. Neither the name of the University nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior
written permission.
THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING,
BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN
NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CON-
SEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR
PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABIL-
ITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF
THE POSSIBILITY OF SUCH DAMAGE.
Dual GPL
Portions of this software are copyright (C) 1996-2002 The FreeType Project (www.freetype.org). All rights reserved.
GPL
GNU GENERAL PUBLIC LICENSE
Version 3, 29 June 2007
Copyright (C) 2007 Free Software Foundation, Inc. <http://fsf.org/>
Preamble
The GNU General Public License is a free, copyleft license for software and other kinds of works.
The licenses for most software and other practical works are designed to take away your freedom to share and change the works. By contrast, the GNU General Pub-
lic License is intended to guarantee your freedom to share and change all versions of a program--to make sure it remains free software for all its users. We, the Free
Software Foundation, use the GNU General Public License for most of our software; it applies also to any other work released this way by its authors. You can apply
it to your programs, too.
When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distrib-
ute copies of free software (and charge for them if you wish), that you receive source code or can get it if you want it, that you can change the software or use pieces
of it in new free programs, and that you know you can do these things.
To protect your rights, we need to prevent others from denying you these rights or asking you to surrender the rights. Therefore, you have certain responsibilities if
you distribute copies of the software, or if you modify it: responsibilities to respect the freedom of others.
For example, if you distribute copies of such a program, whether gratis or for a fee, you must pass on to the recipients the same freedoms that you received. You must
make sure that they, too, receive or can get the source code. And you must show them these terms so they know their rights.
Developers that use the GNU GPL protect your rights with two steps: (1) assert copyright on the software, and (2) offer you this License giving you legal permission
to copy, distribute and/or modify it.
For the developers' and authors' protection, the GPL clearly explains that there is no warranty for this free software. For both users' and authors' sake, the GPL
requires that modified versions be marked as changed, so that their problems will not be attributed erroneously to authors of previous versions.
Some devices are designed to deny users access to install or run modified versions of the software inside them, although the manufacturer can do so. This is funda-
mentally incompatible with the aim of protecting users' freedom to change the software. The systematic pattern of such abuse occurs in the area of products for indi-
viduals to use, which is precisely where it is most unacceptable. Therefore, we have designed this version of the GPL to prohibit the practice for those products. If
Finally, every program is threatened constantly by software patents. States should not allow patents to restrict development and use of software on general-purpose
computers, but in those that do, we wish to avoid the special danger that patents applied to a free program could make it effectively proprietary. To prevent this, the
GPL assures that patents cannot be used to render the program non-free.
The precise terms and conditions for copying, distribution and modification follow.
0. Definitions.
"Copyright" also means copyright-like laws that apply to other kinds of works, such as semiconductor masks.
"The Program" refers to any copyrightable work licensed under this License. Each licensee is addressed as "you". "Licensees" and "recipients" may be individuals or
organizations.
To "modify" a work means to copy from or adapt all or part of the work in a fashion requiring copyright permission, other than the making of an exact copy. The
resulting work is called a "modified version" of the earlier work or a work "based on" the earlier work.
A "covered work" means either the unmodified Program or a work based on the Program.
To "propagate" a work means to do anything with it that, without permission, would make you directly or secondarily liable for infringement under applicable copy-
right law, except executing it on a computer or modifying a private copy. Propagation includes copying, distribution (with or without modification), making available
to the public, and in some countries other activities as well.
To "convey" a work means any kind of propagation that enables other parties to make or receive copies. Mere interaction with a user through a computer network,
with no transfer of a copy, is not conveying.
An interactive user interface displays "Appropriate Legal Notices" to the extent that it includes a convenient and prominently visible feature that (1) displays an
appropriate copyright notice, and (2) tells the user that there is no warranty for the work (except to the extent that warranties are provided), that licensees may convey
the work under this License, and how to view a copy of this License. If the interface presents a list of user commands or options, such as a menu, a prominent item in
the list meets this criterion.
1. Source Code.
The "source code" for a work means the preferred form of the work for making modifications to it. "Object code" means any non-source form of a work.
A "Standard Interface" means an interface that either is an official standard defined by a recognized standards body, or, in the case of interfaces specified for a partic-
ular programming language, one that is widely used among developers working in that language.
The "System Libraries" of an executable work include anything, other than the work as a whole, that (a) is included in the normal form of packaging a Major Compo-
nent, but which is not part of that Major Component, and (b) serves only to enable use of the work with that Major Component, or to implement a Standard Interface
for which an implementation is available to the public in source code form. A "Major Component", in this context, means a major essential component (kernel, win-
dow system, and so on) of the specific operating system (if any) on which the executable work runs, or a compiler used to produce the work, or an object code inter-
preter used to run it.
The "Corresponding Source" for a work in object code form means all the source code needed to generate, install, and (for an executable work) run the object code
and to modify the work, including scripts to control those activities. However, it does not include the work's System Libraries, or general-purpose tools or generally
available free programs which are used unmodified in performing those activities but which are not part of the work. For example, Corresponding Source includes
interface definition files associated with source files for the work, and the source code for shared libraries and dynamically linked subprograms that the work is spe-
cifically designed to require, such as by intimate data communication or control flow between those subprograms and other parts of the work.
The Corresponding Source need not include anything that users can regenerate automatically from other parts of the Corresponding Source.
The Corresponding Source for a work in source code form is that same work.
2. Basic Permissions.
All rights granted under this License are granted for the term of copyright on the Program, and are irrevocable provided the stated conditions are met. This License
explicitly affirms your unlimited permission to run the unmodified Program. The output from running a covered work is covered by this License only if the output,
given its content, constitutes a covered work. This License acknowledges your rights of fair use or other equivalent, as provided by copyright law.
You may make, run and propagate covered works that you do not convey, without conditions so long as your license otherwise remains in force. You may convey
covered works to others for the sole purpose of having them make modifications exclusively for you, or provide you with facilities for running those works, provided
that you comply with the terms of this License in conveying all material for which you do not control copyright. Those thus making or running the covered works for
you must do so exclusively on your behalf, under your direction and control, on terms that prohibit them from making any copies of your copyrighted material out-
side their relationship with you.
Conveying under any other circumstances is permitted solely under the conditions stated below. Sublicensing is not allowed; section 10 makes it unnecessary.
When you convey a covered work, you waive any legal power to forbid circumvention of technological measures to the extent such circumvention is effected by
exercising rights under this License with respect to the covered work, and you disclaim any intention to limit operation or modification of the work as a means of
enforcing, against the work's users, your or third parties' legal rights to forbid circumvention of technological measures.
You may charge any price or no price for each copy that you convey, and you may offer support or warranty protection for a fee.
a. The work must carry prominent notices stating that you modified it, and giving a relevant date.
b. The work must carry prominent notices stating that it is released under this License and any conditions
added under section 7. This requirement modifies the requirement in section 4 to "keep intact all notices".
c. You must license the entire work, as a whole, under this License to anyone who comes into possession of a
copy. This License will therefore apply, along with any applicable section 7 additional terms, to the whole
of the work, and all its parts, regardless of how they are packaged. This License gives no permission to
license the work in any other way, but it does not invalidate such permission if you have separately received
it.
d. If the work has interactive user interfaces, each must display Appropriate Legal Notices; however, if the
Program has interactive interfaces that do not display Appropriate Legal Notices, your work need not make
them do so.
A compilation of a covered work with other separate and independent works, which are not by their nature extensions of the covered work, and which are not com-
bined with it such as to form a larger program, in or on a volume of a storage or distribution medium, is called an "aggregate" if the compilation and its resulting
copyright are not used to limit the access or legal rights of the compilation's users beyond what the individual works permit. Inclusion of a covered work in an aggre-
gate does not cause this License to apply to the other parts of the aggregate.
a. Convey the object code in, or embodied in, a physical product (including a physical distribution medium),
accompanied by the Corresponding Source fixed on a durable physical medium customarily used for
software interchange.
b. Convey the object code in, or embodied in, a physical product (including a physical distribution medium),
accompanied by a written offer, valid for at least three years and valid for as long as you offer spare parts or
customer support for that product model, to give anyone who possesses the object code either (1) a copy of
the Corresponding Source for all the software in the product that is covered by this License, on a durable
physical medium customarily used for software interchange, for a price no more than your reasonable cost
of physically performing this conveying of source, or (2) access to copy the Corresponding Source from a
network server at no charge.
c. c) Convey individual copies of the object code with a copy of the written offer to provide the
Corresponding Source. This alternative is allowed only occasionally and noncommercially, and only if you
received the object code with such an offer, in accord with subsection 6b.
d. d) Convey the object code by offering access from a designated place (gratis or for a charge), and offer
equivalent access to the Corresponding Source in the same way through the same place at no further charge.
You need not require recipients to copy the Corresponding Source along with the object code. If the place to
copy the object code is a network server, the Corresponding Source may be on a different server (operated
by you or a third party) that supports equivalent copying facilities, provided you maintain clear directions
next to the object code saying where to find the Corresponding Source. Regardless of what server hosts the
Corresponding Source, you remain obligated to ensure that it is available for as long as needed to satisfy
these requirements.
e. e) Convey the object code using peer-to-peer transmission, provided you inform other peers where the
object code and Corresponding Source of the work are being offered to the general public at no charge
under subsection 6d.
A separable portion of the object code, whose source code is excluded from the Corresponding Source as a System Library, need not be included in conveying the
object code work.
"Installation Information" for a User Product means any methods, procedures, authorization keys, or other information required to install and execute modified ver-
sions of a covered work in that User Product from a modified version of its Corresponding Source. The information must suffice to ensure that the continued func-
tioning of the modified object code is in no case prevented or interfered with solely because modification has been made.
If you convey an object code work under this section in, or with, or specifically for use in, a User Product, and the conveying occurs as part of a transaction in which
the right of possession and use of the User Product is transferred to the recipient in perpetuity or for a fixed term (regardless of how the transaction is characterized),
the Corresponding Source conveyed under this section must be accompanied by the Installation Information. But this requirement does not apply if neither you nor
any third party retains the ability to install modified object code on the User Product (for example, the work has been installed in ROM).
The requirement to provide Installation Information does not include a requirement to continue to provide support service, warranty, or updates for a work that has
been modified or installed by the recipient, or for the User Product in which it has been modified or installed. Access to a network may be denied when the modifica-
tion itself materially and adversely affects the operation of the network or violates the rules and protocols for communication across the network.
Corresponding Source conveyed, and Installation Information provided, in accord with this section must be in a format that is publicly documented (and with an
implementation available to the public in source code form), and must require no special password or key for unpacking, reading or copying.
7. Additional Terms.
"Additional permissions" are terms that supplement the terms of this License by making exceptions from one or more of its conditions. Additional permissions that
are applicable to the entire Program shall be treated as though they were included in this License, to the extent that they are valid under applicable law. If additional
permissions apply only to part of the Program, that part may be used separately under those permissions, but the entire Program remains governed by this License
without regard to the additional permissions.
When you convey a copy of a covered work, you may at your option remove any additional permissions from that copy, or from any part of it. (Additional permis-
sions may be written to require their own removal in certain cases when you modify the work.) You may place additional permissions on material, added by you to a
covered work, for which you have or can give appropriate copyright permission.
Notwithstanding any other provision of this License, for material you add to a covered work, you may (if authorized by the copyright holders of that material) supple-
ment the terms of this License with terms:
a. Disclaiming warranty or limiting liability differently from the terms of sections 15 and 16 of this License;
or
b. Requiring preservation of specified reasonable legal notices or author attributions in that material or in the
Appropriate Legal Notices displayed by works containing it; or
c. Prohibiting misrepresentation of the origin of that material, or requiring that modified versions of such
material be marked in reasonable ways as different from the original version; or
d. Limiting the use for publicity purposes of names of licensors or authors of the material; or
e. Declining to grant rights under trademark law for use of some trade names, trademarks, or service marks; or
f. Requiring indemnification of licensors and authors of that material by anyone who conveys the material (or
modified versions of it) with contractual assumptions of liability to the recipient, for any liability that these
contractual assumptions directly impose on those licensors and authors.
All other non-permissive additional terms are considered "further restrictions" within the meaning of section 10. If the Program as you received it, or any part of it,
contains a notice stating that it is governed by this License along with a term that is a further restriction, you may remove that term. If a license document contains a
further restriction but permits relicensing or conveying under this License, you may add to a covered work material governed by the terms of that license document,
provided that the further restriction does not survive such relicensing or conveying.
If you add terms to a covered work in accord with this section, you must place, in the relevant source files, a statement of the additional terms that apply to those files,
or a notice indicating where to find the applicable terms.
Additional terms, permissive or non-permissive, may be stated in the form of a separately written license, or stated as exceptions; the above requirements apply either
way.
8. Termination.
You may not propagate or modify a covered work except as expressly provided under this License. Any attempt otherwise to propagate or modify it is void, and will
automatically terminate your rights under this License (including any patent licenses granted under the third paragraph of section 11).
However, if you cease all violation of this License, then your license from a particular copyright holder is reinstated (a) provisionally, unless and until the copyright
holder explicitly and finally terminates your license, and (b) permanently, if the copyright holder fails to notify you of the violation by some reasonable means prior
to 60 days after the cessation.
Moreover, your license from a particular copyright holder is reinstated permanently if the copyright holder notifies you of the violation by some reasonable means,
this is the first time you have received notice of violation of this License (for any work) from that copyright holder, and you cure the violation prior to 30 days after
your receipt of the notice.
Termination of your rights under this section does not terminate the licenses of parties who have received copies or rights from you under this License. If your rights
have been terminated and not permanently reinstated, you do not qualify to receive new licenses for the same material under section 10.
An "entity transaction" is a transaction transferring control of an organization, or substantially all assets of one, or subdividing an organization, or merging organiza-
tions. If propagation of a covered work results from an entity transaction, each party to that transaction who receives a copy of the work also receives whatever
licenses to the work the party's predecessor in interest had or could give under the previous paragraph, plus a right to possession of the Corresponding Source of the
work from the predecessor in interest, if the predecessor has it or can get it with reasonable efforts.
You may not impose any further restrictions on the exercise of the rights granted or affirmed under this License. For example, you may not impose a license fee, roy-
alty, or other charge for exercise of rights granted under this License, and you may not initiate litigation (including a cross-claim or counterclaim in a lawsuit) alleging
that any patent claim is infringed by making, using, selling, offering for sale, or importing the Program or any portion of it.
11. Patents.
A "contributor" is a copyright holder who authorizes use under this License of the Program or a work on which the Program is based. The work thus licensed is called
the contributor's "contributor version".
A contributor's "essential patent claims" are all patent claims owned or controlled by the contributor, whether already acquired or hereafter acquired, that would be
infringed by some manner, permitted by this License, of making, using, or selling its contributor version, but do not include claims that would be infringed only as a
consequence of further modification of the contributor version. For purposes of this definition, "control" includes the right to grant patent sublicenses in a manner
consistent with the requirements of this License.
Each contributor grants you a non-exclusive, worldwide, royalty-free patent license under the contributor's essential patent claims, to make, use, sell, offer for sale,
import and otherwise run, modify and propagate the contents of its contributor version.
In the following three paragraphs, a "patent license" is any express agreement or commitment, however denominated, not to enforce a patent (such as an express per-
mission to practice a patent or covenant not to sue for patent infringement). To "grant" such a patent license to a party means to make such an agreement or commit-
ment not to enforce a patent against the party.
If you convey a covered work, knowingly relying on a patent license, and the Corresponding Source of the work is not available for anyone to copy, free of charge
and under the terms of this License, through a publicly available network server or other readily accessible means, then you must either (1) cause the Corresponding
Source to be so available, or (2) arrange to deprive yourself of the benefit of the patent license for this particular work, or (3) arrange, in a manner consistent with the
requirements of this License, to extend the patent license to downstream recipients. "Knowingly relying" means you have actual knowledge that, but for the patent
license, your conveying the covered work in a country, or your recipient's use of the covered work in a country, would infringe one or more identifiable patents in that
country that you have reason to believe are valid.
If, pursuant to or in connection with a single transaction or arrangement, you convey, or propagate by procuring conveyance of, a covered work, and grant a patent
license to some of the parties receiving the covered work authorizing them to use, propagate, modify or convey a specific copy of the covered work, then the patent
license you grant is automatically extended to all recipients of the covered work and works based on it.
A patent license is "discriminatory" if it does not include within the scope of its coverage, prohibits the exercise of, or is conditioned on the non-exercise of one or
more of the rights that are specifically granted under this License. You may not convey a covered work if you are a party to an arrangement with a third party that is
in the business of distributing software, under which you make payment to the third party based on the extent of your activity of conveying the work, and under which
the third party grants, to any of the parties who would receive the covered work from you, a discriminatory patent license (a) in connection with copies of the covered
work conveyed by you (or copies made from those copies), or (b) primarily for and in connection with specific products or compilations that contain the covered
work, unless you entered into that arrangement, or that patent license was granted, prior to 28 March 2007.
Nothing in this License shall be construed as excluding or limiting any implied license or other defenses to infringement that may otherwise be available to you under
applicable patent law.
Each version is given a distinguishing version number. If the Program specifies that a certain numbered version of the GNU General Public License "or any later ver-
sion" applies to it, you have the option of following the terms and conditions either of that numbered version or of any later version published by the Free Software
Foundation. If the Program does not specify a version number of the GNU General Public License, you may choose any version ever published by the Free Software
Foundation.
If the Program specifies that a proxy can decide which future versions of the GNU General Public License can be used, that proxy's public statement of acceptance of
a version permanently authorizes you to choose that version for the Program.
Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.
This version of the GNU Lesser General Public License incorporates the terms and conditions of version 3 of the GNU General Public License, supplemented by the
additional permissions listed below.
0. Additional Definitions.
As used herein, "this License" refers to version 3 of the GNU Lesser General Public License, and the "GNU GPL" refers to version 3 of the GNU General Public
License.
"The Library" refers to a covered work governed by this License, other than an Application or a Combined Work as defined below.
An "Application" is any work that makes use of an interface provided by the Library, but which is not otherwise based on the Library. Defining a subclass of a class
defined by the Library is deemed a mode of using an interface provided by the Library.
A "Combined Work" is a work produced by combining or linking an Application with the Library. The particular version of the Library with which the Combined
The "Minimal Corresponding Source" for a Combined Work means the Corresponding Source for the Combined Work, excluding any source code for portions of the
Combined Work that, considered in isolation, are based on the Application, and not on the Linked Version.
The "Corresponding Application Code" for a Combined Work means the object code and/or source code for the Application, including any data and utility programs
needed for reproducing the Combined Work from the Application, but excluding the System Libraries of the Combined Work.
a. under this License, provided that you make a good faith effort to ensure that, in the event an Application
does not supply the function or data, the facility still operates, and performs whatever part of its purpose
remains meaningful, or
b. under the GNU GPL, with none of the additional permissions of this License applicable to that copy.
3. Object Code Incorporating Material from Library Header Files.
The object code form of an Application may incorporate material from a header file that is part of the Library. You may convey such object code under terms of your
choice, provided that, if the incorporated material is not limited to numerical parameters, data structure layouts and accessors, or small macros, inline functions and
templates (ten or fewer lines in length), you do both of the following:
a. Give prominent notice with each copy of the object code that the Library is used in it and that the Library
and its use are covered by this License.
b. Accompany the object code with a copy of the GNU GPL and this license document.
4. Combined Works.
You may convey a Combined Work under terms of your choice that, taken together, effectively do not restrict modification of the portions of the Library contained in
the Combined Work and reverse engineering for debugging such modifications, if you also do each of the following:
a. Give prominent notice with each copy of the Combined Work that the Library is used in it and that the
Library and its use are covered by this License.
b. Accompany the Combined Work with a copy of the GNU GPL and this license document.
c. For a Combined Work that displays copyright notices during execution, include the copyright notice for the
Library among these notices, as well as a reference directing the user to the copies of the GNU GPL and
this license document.
d. Do one of the following:
1) Convey the Minimal Corresponding Source under the terms of this License, and the Corresponding
Application Code in a form suitable for, and under terms that permit, the user to recombine or relink the
a. Accompany the combined library with a copy of the same work based on the Library, uncombined with any
other library facilities, conveyed under the terms of this License.
b. Give prominent notice with the combined library that part of it is a work based on the Library, and
explaining where to find the accompanying uncombined form of the same work.
6. Revised Versions of the GNU Lesser General Public License.
The Free Software Foundation may publish revised and/or new versions of the GNU Lesser General Public License from time to time. Such new versions will be sim-
ilar in spirit to the present version, but may differ in detail to address new problems or concerns.
Each version is given a distinguishing version number. If the Library as you received it specifies that a certain numbered version of the GNU Lesser General Public
License "or any later version" applies to it, you have the option of following the terms and conditions either of that published version or of any later version published
by the Free Software Foundation. If the Library as you received it does not specify a version number of the GNU Lesser General Public License, you may choose any
version of the GNU Lesser General Public License ever published by the Free Software Foundation.
If the Library as you received it specifies that a proxy can decide whether future versions of the GNU Lesser General Public License shall apply, that proxy's public
statement of acceptance of any version is permanent authorization for you to choose that version for the Library.
MIT
Copyright 1987, 1988 by MIT Student Information Processing Board.
Permission to use, copy, modify, and distribute this software and its documentation for any purpose is hereby granted, provided that the names of M.I.T. and the
M.I.T. S.I.P.B. not be used in advertising or publicity pertaining to distribution of the software without specific, written prior permission. M.I.T. and the M.I.T.
S.I.P.B. make no representations about the suitability of this software for any purpose. It is provided "as is" without express or implied warranty.
zlib
Copyright (C) 1995-1998 Jean-loup Gailly and Mark Adler
This software is provided 'as-is', without any express or implied warranty. In no event will the authors be held liable for any damages arising from the use of this soft-
ware.
Permission is granted to anyone to use this software for any purpose, including commercial applications, and to alter it and redistribute it freely, subject to the follow-
ing restrictions:
1. The origin of this software must not be misrepresented; you must not claim that you wrote the original
software. If you use this software in a product, an acknowledgment in the product documentation would be
appreciated but is not required.
2. Altered source versions must be plainly marked as such, and must not be misrepresented as being the
original software.
3. This notice may not be removed or altered from any source distribution.Jean-loup Gailly Mark Adler
[email protected] [email protected]
The data format used by the zlib library is described by RFCs (Request for Comments) 1950 to 1952 in the files ftp://ds.internic.net/rfc/rfc1950.txt (zlib format),
rfc1951.txt (deflate format) and rfc1952.txt (gzip format).