Tieline interfaces, Tielines – Grass Valley NV9000-SE v.3.0 User Manual
Page 478
458
Rev 3.0 • 25 Mar 10
16. Tielines
Tieline Interfaces
Costs are updated and viewed using the ‘Tieline’ table or the ‘Tieline Path’ table accessed
through the ‘Views’ pane. See
• Hop Count
A hop count is the total number of tielines required to make the desired route. In other words,
how many times does a signal need to “hop” from tieline to tieline to reach its final destination.
Cost defaults to the hop count if no cost is entered.
• Signal Binding
When creating a tieline, the signals corresponding to the virtual levels associated with the
devices that are part of the tieline display. Each signal type within a virtual level can be selected
or deselected. If selected, the signal type is “bound” to the tieline. Once “bound,” the selected
signal type is always associated with that tieline configuration until changed.
Binding signals is an added protection that ensures that the right signal type is selected when
using a tieline to route between devices, that signal types are consistent across configurations,
and that signal types cannot be altered “on the fly.”
Tielines and the corresponding signals bound to the configuration are viewable using the
‘Tieline Signal Binding’ table accessed through the ‘Views’ pane. See
• Signal Types
On the tieline interface, signal types represent a default and consistent set of signals. The sig-
nals, and their definitions, can be shared by multiple control systems.
• Port Binding
Similar to signal binding, when a device port is selected for a tieline it is “bound” to that tieline.
Once “bound,” the port is no longer available for use in another tieline. This ensures that one
port is not accidentally used in multiple tielines.
Tielines and the corresponding ports bound to the configuration are viewable using the ‘Tieline
Port Binding’ table accessed through the ‘Views’ pane. See
Viewing the ‘Tieline Port Binding’
• Grouping
Once created, tielines can be organized in groups. Groups enable you to combine several
tielines that are always used together. For example, audio channels associated with video chan-
nels. When creating a group, a tieline can only belong to one group at a time. All tielines in a
groups are reserved and cannot be used by another group.
Similar to signal binding or port binding, tieline group binding ‘binds” the tieline to the selected
groups. This ensures that one tieline is not used outside the selected group.
Tieline Interfaces
In general, tielines are added using the ‘Add Tieline’ wizard and then managed through the
‘Tielines’ page or individual tables. All pages and tables share information so that data entered or
updated in one interface is added or updated in corresponding data fields in other interfaces.
Tielines are managed using the following interfaces: