The central part of each DHD system is the DSP unit. This can either be operated as stand-alone version (e.g., as a router) or is connected via CAN bus (RM4200D) or Ethernet (Series 52) to one or more operating devices.

You can operate several DHD systems together, for example in several studios that are linked via one central router. To simplify the configuration, you can manage routers, operating panels and other devices in one Toolbox5 project. The DSP frames in the studios are linked to the router via MADI and Ethernet, to exchange audio and controlling signals.

Only one CAN bus is allowed per RM4200D DSP Frame. Therefore, it is not possible to operate several RM4200 DSP Frames on the same CAN bus.

There are no such limitations for Series 52 devices, because of the Ethernet structure.

The Toolbox5 software is a Windows program that does not require any additional dynamic libraries (DLL files) or other files. For installation, simply copy the program file to the hard drive. To load the software, double-click on the Toolbox5.exe. To remove the program, delete the Toolbox5.exe.

When opening Toolbox5, another software application is loaded automatically: DHD Communication Server (DHDCS). DHDCS filters TCP/IP and UDP packets from the network that are transferred to and from DHD devices and prepares them for several software applications. Please find detailed information on DHDCS in the Application Software Manual of the RM4200D.

You can use Toolbox5 without any hardware connected, for example for changing or checking configurations offline. Normally, the configuration PC is connected with the corresponding DHD system using the TCP/IP protocol via Ethernet. Alternatively, you can use a connection via the USB 2.0 interface (only RM4200D and 52/XR). To do this, Windows XP functions have to be activated using a special installation file.

The easiest way to work with DHD devices and Toolbox5 is using the Ethernet connection. In the Toolbox5 the Ethernet connection is set as the standard connection. It requires the configuration of the IP addresses. Details and characteristics of both connection types are described in the following sections.

Some modules of an RM4200D DSP Frame as well as the modules of the RM4200D user interface have an RS232 interface. This interface works also if the modules are operated with Series 52 software. Keep in mind that the interface supplies only limited functionality.

A DHD configuration project can consist of one or more systems. These systems (e.g., an 52/MX Mixing Console and the corresponding DSP unit) are called a Device in the Toolbox5 software.

Via Ethernet and the UDP protocol, several devices can be connected. If correctly configured, they can exchange control functions.

A global function means that a device can control certain parts of a different device. To do this, both systems have to be configured properly and be able to exchange data via the UDP protocol.

Generally, every device works independently from others. If a device is switched off or the connection to other devices is interrupted, only the exchanged functions stop working.

To simplify configuration and to make sure the devices are assigned properly, devices grouped together are managed within the Toolbox5 software. Each project has a project ID which is the same for all devices in a project. When setting up a new project, its ID is generated by a random generator, but it can be changed later manually.

If global functions are to be exchanged between two or more systems, the project IDs of the devices have to be identical. If not, the global functions do not work.

Vice versa, several Toolbox5 projects within the same network do not interfere if they have different project IDs.

Via the serial RS232 interface of a device (not available with every device) only the global logic functions 1 to 50 can be exchanged. This communication is compatible with RM3200D. Global potentiometers are not supported by this interface.

If several DHD systems are interconnected, their shared audio connections (MADI, Analog, Digital AES3/EBU) can be easier managed with device links. Therefore, it is also required that the linked devices are located within the same project (see Device Links)

The configuration software creates a set of configuration data, which we call Config further on. This Config contains the whole configuration of a DHD system that is specific to this application. One Config contains information for one Toolbox5 device.

The Config is stored in the flash EPROM of the main controller/communication controller of a device. The transfer to and from the device is done via TCP/IP and Ethernet. The corresponding Toolbox5 commands are Load from Device and Load to Device. This way, a Config can be read out from a device, edited in the Toolbox5 software and then written back in (see also Transfer Menu).

Before a Config can be loaded into a DHD system, all modules of the Config should be connected.

The Toolbox5 software can read Config data from a device and write it back. The data can also be stored in files. If there are several devices in a project, their Configs are managed together in a project file. In the software, this structure is shown on the left in the project tree. On top of the project tree, the project name is shown. Under that name one or more devices with assigned device names follow (see The Project Tree)

The Config of each device can be stored in a separate Config file. These files are used to import already configured devices from a project into a new or already existing one. (see also Export Device to File)

The file extension of a project file is .dp5, the extension for a device config file is .dd5.

Device Config files are mainly used to import already configured devices from other projects into a new or already existing one. During this process, already defined Global Functions might be overwritten by the imported data! Always check the correct functionality carefully, after importing configured devices.

The structure of the Config file is closely related to the firmware of the devices. This means that with every firmware update, also an update of the Toolbox5 software is necessary - and vice versa.

Basically, the data structure of the Config tolerates changes in versions. Configs that are created with an older version of Toolbox5 can normally be opened and edited with a new Toolbox5 version.

But if a Config file that was created in a recent software version is opened in an older version of Toolbox5, Toolbox5 shows a warning message. Functions that are changed in the recent software version may not be recognized or do not work correctly. If a software update was only a bug fix but did not include new functions, Toolbox5 has not necessarily to be updated.

To avoid complications, you should always use the matching versions of firmware and Toolbox5 software. It is important to check this especially when exchanging single modules. The firmware of a systems can be updated using the maintenance software that is included in Toolbox5. (see Maintenance Window) The matching versions of Toolbox5 and firmware that are recommended by DHD are available in the support section of the DHD website at update.dhd.audio. If in doubt, ask your DHD dealer.

Configuring a DHD system is a complex process. There are always different ways to do it. The sequence of the individual steps is often not static. Despite this, the following list is to be understood as a proposal, how to configure for example a brand new 52/MX. This list is neither complete nor very detailed, but it gives a basic overview of the configuration process:

  1. Set up the general options for the project. (see Device Properties)
  2. Insert a device and select the user interface 52/MX. (see Adding a Device - 52/MX or RM4200D)
  3. Select the modules for the DSP frame and assign the labels for audio and controlling signals. (see DSP Frame I/O - Configuring the DSP Frame)
  4. Put the desired fader modules in the rack and assign the keys of the operating desk to certain functions. (see Console - Configuring the Mixing Console)
  5. Set up the audio system with Aux busses, internal busses, fader channels etc. (see Audio - Configuring the Audio System)
  6. Set up the logic system to include key functions, GPIOs etc. (see Configuring the Logic System)
  7. Connect the audio signals and logic functions with output functions. (see Output Functions)
  8. Route the audio signals from the internal bus to the outputs of the 52/MX. (see Output Routing)

The type of the user interface can not be changed in the further configuration process. Select first whether you want to set up an 52/MX or an RM4200D, before changing other settings.