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 - 90 -
18 Appendix A - Network design for AXUM
The platform AXUM design is according to the OSI-Model and makes use of protocols on different
levels. It is important to understand the philosophy on the different levels in networking and the way
the AXUM implemented this.
With this knowledge, you can make an advanced network setup within your studio(s) give you
possibilities for:
- Remote configuration
- Remote service
- Connecting multiple AXUM racks to internet.
- Secure working within office-networks.
18.1 Network levels
Most of the people are aware of IP addresses. IP stands for ‘Internet Protocol’ and is in the OSI-Model
called a ‘level 3’ protocol. In smaller office-networks, you normally only have to care about this ‘level 3’
(so IP).
The LAN connections (Local Area Network) normally use the Ethernet technology. Where the Ethernet
is called a ‘level 2’ protocol.
For your understanding ‘level 1’ is the physical cable like CAT5e (often called RJ45-cable or Ethernet-
cable).
An example how these ‘levels’ are used in an office network is your connection to the Internet:
- Your LAN connections are Ethernet
- Your WAN connection is DSL or GPRS/HDSPA
The fact is that the ‘level 3’ IP can be send on LAN and WAN, but the ‘level 2’ Ethernet is only
available in the local area.
18.2 AXUM Network implementation
The AXUM system communication, where you have to think of fader, knob data etc. is based on the
protocol MambaNet. MambaNet may run over other protocols and this can be L2 and L3 protocols.
Two examples of a valid AXUM solution:
18.2.1 MambaNet example 1
- MambaNet over layer 2 (Ethernet)
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.
This makes sense because then the AXUM internal communication is independent of any IP address
assignment and will always work independent on the IP-configuration. Second, the configuration is
based on IP so with a good network design you can access configuration and service functionality
over Internet.
Because layer 2 is a package switched solution this gives the restriction you can only use one AXUM
rack in the Ethernet network. The next example can be used in a multi-rack network setup.










