System network considerations, Rk. see, System desig – Biamp LTR User Manual
Page 169: Before data ca, Start, Ts (see, System, Network considerations, Ethernet utilizes sta
System Design
Message: Feedback detected in the control network.
Explanation: The potential exists for a control path to be indirectly looped back
upon itself. This condition could be dangerous, and is not allowed.
Message: Unit #__ has too many control connections.
Explanation: Although quite large, there is a limit to the quantity of control
connections within a single unit. Connections include both internal
(source and destination within same unit) and external links (source
or destination within this unit). Try moving certain control objects to
another unit (using
),
Setting up the NEXIA units after a successful compilation
Messages: Available range of Instance IDs is nearly exhausted.
Range of Instance IDs has been exhausted.
Explanation: The total number of
, as assigned to component and
line objects, is limited to 65,535. When component objects are
removed from a design, their Instance IDs are not automatically
re-assigned to new component objects. Therefore, the messages
above indicate that a significant number of Instance IDs has been
wasted. Set 'Reassign Instance IDs' under
and re-compile to recover wasted Instance IDs. CAUTION: This
will change most component Instance IDs, and will render existing
external control command scripts useless (unless Instance ID Tags
have been used in lieu of Instance ID numbers).
Once Instance IDs
have been recovered, turn off 'Reassign Instance IDs' to avoid
further re-assignments.
System Network Considerations
Ethernet allows multiple NEXIA devices to be connected on a network, for system-wide
programming and control. Ethernet supports
, and
, but does not include sharing of digital audio signals via
.
155