Building a pro64 network, Connecting pro64 devices, Basic routing – Aviom AllFrame User Manual

Page 64: A-net connections, 64 n, Uilding, Etwork, All frame

Advertising
background image

52

b

uilding

a

P

ro

64 n

eTwork

ALL

FRAME

Multi-Modular I/O System

b

uildiNg

A

P

ro

64 N

etWork

Configuring a Pro64 network involves a few basic steps: selecting I/O devices and/or merger hubs for the

application, connecting I/O devices with Cat-5e or fiber optic cables, assigning hardware inputs to an A-Net Slot,

and activating input channels to make them available to output devices in the network.

Any number of Pro64 I/O devices, MH10/MH10f Merger Hubs and RCI Remote Control Interfaces can be connected

and located anywhere in a Pro64 network.

Connecting Pro64 Devices

Start by setting one (and only one) Pro64 device to be the network Control Master. Because there are some

operations that can only be executed at the Control Master, be sure that the device designated as the Control

Master is accessible. Once all Pro64 devices in the network are enumerated (indicated by illuminated A-Net LEDs),

you can activate and route audio channels and VDCs as needed.

Basic Routing

To output the mic/line audio inputs connected to the F6 Modular I/O Frame, the device must be connected to

another Pro64 device somewhere in the network that can output its data. This device can be a standalone Pro64

analog or digital device, or a console interface card such as the 6416Y2 console card for use in Yamaha digital

products supporting the MY expansion card format.

The diagrams that follow use generic input and output device icons. Any Pro64 I/O device can be substituted

unless otherwise noted. Connect an RCI Remote Control Interface at any convenient location in the diagrams that

follow to provide a monitor station and hardware remote control of active mic preamp parameters.

A-Net Connections

In Auto Mode, the A-Net ports on a device can be connected to other Pro64 devices interchangeably. In the

following examples, network performance and functionality are unaffected by the changes in cabling.

Example 1: Port A connected to Port B

B A

B A

Input

B A

Output

B A

Input

B A

Output

B A

Input

B A

Input

B A

Output

1 2

Merger

3 4 5 6 7 8 9 10

B A

B A

Input

B A

Output

B A

Input

B A

Output

B A

Input

B A

Input

B A

Output

1 2

Merger

3 4 5 6 7 8 9 10

The A-Net cable can be connected to either Port A or Port B. Reversing the A-Net connections creates the same network pathway. Either

unused port can be used to further expand the network.

Advertising