Revision D • 8/05
H
A
R
R
I
S
C
O
R
P
O
R
A T
I
O
N
4-20
4 BMX
digital Server
digital
button to be changed by the operator, leave the
setting for the button as
0
. To lockout that par-
ticular button, change the setting to
1
.
5
Repeat steps 1 - 4 for each channel that re-
quires any buttons to be locked out.
MAPPING SECTION
The mapping section
[Mapping]
lists the
BMX
digital channels, as detected at the time the
session was saved, into a table that is identical to
the inventory.txt file (see page 4-3). The section is
automatically rewritten by the BMXd
igital Server
at each save so it should not be edited.
The table entries are in hex, with
Map_0
being
a reserved position listed as
ff
for no channel de-
tected.
Map_9
up to
Map_24
are reserved for the
Net Card facet connections and are never popu-
lated. Each installed Universal module is num-
bered sequentially left to right in the frame from
01
to
3f
. Telco channels are numbered
41
to
66
.
RLS modules are numbered from
71
to
9f
. Which
numbers are used is set by the type of RLS and
Telco input (direct, router or RLS), the Telco num-
ber and the RLS position.
Map_57
and
Map_58
identify the CR Monitor
and Studio Monitor modules as
b1
and
b2
.
The channel map ends with
DSP=x
. which iden-
tifies how many DSP cards are installed in the
frame.
ROUTER ASSIGNMENT SECTIONS
Each console is assigned a unique device num-
ber by the
nqx.ini
file during start-up. Though
typically left at
device=1
for non-networked con-
soles, when multiple BMX
digital consoles and Vis-
taMax frames are networked together, each must
have a unique device number assigned (from 1 to
63) to distinctly identify its signals to the other
networked devices. The device number is used to
create the Global Signal ID number that uniquely
identifies every signal in a networked system.
RouterCommand
Either Global or Local signal ID numbers can
be used in the ‘Take commands’ section of the ses-
sion or macro file to identify sources and destina-
tions. The section header
[RouterCommand_1]
,
is used to set up the default routing for each routed
module by ‘taking’ or routing a source to a Uni-
versal module with a routed input.
A typical
[RouterCommand_1]
section on a
BMX
digital is shown below:
[RouterCommand_1]
take_1=65777,65665 ; Net Card A1 to channel 1
take_2=65779,65667 ; Net Card A2 to channel 2
take_3=65781,65669 ; Net Card A3 to channel 3
take_4=65783,65671 ; Net Card A4 to channel 4
Each Take command
(take_x=source,
destination)
must be on a separate line and
be listed in numerical order. Both source and des-
tination can be identified using their Global sig-
nal IDs, as shown above.
65777
identifies this sig-
nal as the left channel of the A1 analog input on
the Net Card in the console assigned as device
number 1. The
65665
identifies that it goes to
module 1 which is in the first slot at the left end of
the console.
Up to sixty-four of these Take commands can
be listed in numeric order in any one session file
to route sources to destinations. This routing oc-
curs when the session file is loaded (unless a mod-
ule is On, in which case it is pending until the
module is turned off).
Routes assigned by a session file are continu-
ously maintained until another session file is
loaded that changes the routing or until a new
source is selected on a module, by using a FTP
command or by using an Edge Device. All routes
are held, even if the console is turned off or loses
power, by a “persistence file” that gets updated af-
ter every route is taken.
In previous examples, one source has been
shown being routed to one destination, but any
one source can be routed to any number of desti-
