User manual
Table Of Contents
- 1 Table of contents1 T
- 2 Package Contents
- 3 Introduction
- 4 System overview
- 5 Control Surfaces
- 6 AXUM Engine
- 6.1 Console 1-4 configuration
- 6.1.1 IP/Clock configuration
- 6.1.2 Global configuration
- 6.1.3 Mix buss configuration
- 6.1.4 Monitor buss configuration
- 6.1.5 Source configuration
- 6.1.6 Extern source configuration
- 6.1.7 Destination configuration
- 6.1.8 Talkback configuration
- 6.1.9 Processing presets
- 6.1.10 Module assignment
- 6.1.11 Module configuration
- 6.1.11.1 Module configuration page
- 6.1.11.2 Module preset 1A/1B, 2A/2B, 3A/3B, 4A/4B
- 6.1.11.3 Processing
- These are the programmed processing defaults for the modules. Depending on the startup settings these processing defaults will be used at startup (programmed defaults in global configuration).The field ‘Use at source select’ determines if the default module processing in the source configuration is used when a source is assigned via the module source select functionality and no processing preset is assigned in the ‘source configuration’.
- The following state/value processing sections are available:
- 6.1.11.4 Routing
- 6.1.11.5 Set module 1 to programmed startup state
- 6.1.12 Mix/monitor buss presets
- 6.1.13 Console presets
- 6.1.14 Surface configuration
- 6.1.15 Rack configuration
- 6.1.16 Source pools
- 6.1.17 Preset pools
- 6.1.18 Users
- 6.2 System configuration
- 6.1 Console 1-4 configuration
- 7 Surface(s) website
- 8 Block diagrams – Must be created
- 9 I/O Rack description
- 10 Available I/O rack cards
- 11 Patch panels
- 12 Specifications AXUM digital audio system
- 13 List Of Figures
- 14 List Of Tables
- 15 Declaration Of Conformity
- 16 Product Safety
- 17 Disclaimer
- 18 Appendix A - Network design for AXUM
- 19 Appendix B – Surface service
- 20 Appendix C – Engine functions
A·X·U·M User Manual Version 2.5 - 2011-01-28
AXUM from D&R - Phone: +31 294 418014 - E-Mail: info@d-r.nl - 91 -
18.2.2 MambaNet example 2
- MambaNet over layer 3(UDP or TCP)
Is used for the Axum internal communication, where you have to think of fader, knob data etc.
etc.
- Configuration over layer 3 (IP)
Is used for the Axum configuration and service access.
The MambaNet over UDP (and TCP) is connection oriented. With the destination IP address you
determine to which rack this surface hooks up.
18.3 Network design (MambaNet over Layer 2)
An AXUM system require to have an own LAN (layer 2) to work without risk of interference with office
networks and or other AXUM systems. The most basic way of describing this is:
“Each Axum system requires its own Ethernet switch”.
As you can understand this means there is no connection (so communication possible) between the
separate LANs. This creates the problem you cannot access the console(s) from a single internet
connection or from your office network. To overcome this problem you have to design the network with
a separation on ‘level 2’ (Ethernet) but a connection over ‘level 3’ (IP) must be possible.
Most simple example on such separation is:
Here you see two LAN networks, both connected to internet. With correct IP-addressing Office 1 and 2
can reach each other using the IP protocol. However, there will be no interference between Office 1
and 2 on Ethernet. In fact, you have to create the same network level-structure in your studio for
correct function.
Internet
Office 1
Ethernet
Office 2
Ethernet
DSL
(only IP)
DSL
(only IP)