Sonifex AVN-MPPR, Руководство пользователя

Страница: 23 / 48

15
Third Party API 5
15
Operational Specification 6
6. Operational Specification
Startup
All units will have a unique ID since each unit will need 1 MAC address for
each Ethernet port. The serial number of the unit will also be embedded
into the device, which is accessible via Ember+ and is used in the default
naming of the device.
By default, the units’ IP addresses will be provided statically from an
internally stored value in Flash, but this can be changed, though it is not
recommended, to use a Dynamic Addressing Mode. This will attempt to
connect to a DHCP server on the network to gain an IP address from it. If
this fails, then the unit will fall-back to an AutoIP address range by trying to
connect to a series of IP addresses in a defined range.
All units have a built in recovery system, that has minimal operating
firmware and an update web page that is accessed at a fixed static IP
address of 192.168.0.100 on the Ethernet port and 192.168.1.100 on the
AoIP port. This recovery system is designed to repair a system that is failing
due to a bad firmware upgrade and will start automatically if the current
firmware – that is stored on the embedded SD card – fails to start correctly
on 3 tries. In extremis, the recovery system will allow a system to be rebuilt
on a brand new SD card, though this would also require the system setup to
be re-entered.
The Virtual Mixers in the Mix Engine are controlled by settings from an
Ember+ interface that are sent via the AoIP network from the assigned
Presenter or Technician units. The metering levels are sent from the Mix
Engine and received by the appropriate Presenter or Technician units.
The Mix Engine has a webserver that is used to access the system settings
for the Virtual Mixers and for the associated Remote Units. When a Remote
Unit comes online and is authorised then it will advertise itself as being
available to the network using mDNS messages. The Mix Engine will receive
these messages and determine if the device ‘belongs’ to a Virtual Mixer
that it controls. This association will be driven by either the Hardware ID
settings on the back of the PPRs, or by internal & front panel selection on
the MPTRs.
Authorisation
When a MPPR advertises itself to the network, it also reports the value set
by the ID1 Group selector switch on the rear of the unit. When the mix
engine receives the advertisement, it checks whether the MPPR is in its list
of allowed devices. If the MPPR is in the list and if the mix engine is set to
grab the group reported by the MPPR, the MPPR will be grabbed by the mix
engine (the Auth led will turn green to show this) and it will be assigned to
the virtual mixer stored in the allowed devices. The virtual mixer LEDs
(numbers) will all flash amber together to indicate that no virtual mixer
allocation has been made.
If the MPPR is not listed in the allowed devices list on the mix engine, it will
not be grabbed by the mix engine and the Auth LED on the MPPR will
remain in the flashing yellow state. The MPPR can be added to the allowed
devices list on the Mix Engine or any MPTR via their webpages, or even
their front panels.
Once a MPPR is authorised, it will fetch the settings from the Mix Engine
and allow the presenter full control of the levels and receive audio from the
mixer output.
Control Precedence
The normal operation is expected to be a single MPPR controlling a Virtual
Mixer, but when other units, either Presenter or Technician, are connected
and are controlling the same Virtual Mixer then all units connected to a
Virtual Mixer will share the control, i.e. level controls are paralleled.
However it may be that MPTRs will want to take away the level control from
MPPRs, (see sections 3, Rotary Controls, and 4, Mixer Selection Buttons)