In the following section, you find a short description of typical tasks for which you have to use the Maintenance Window.
First, read out the version of the currently loaded firmware using the command . Compare it to the current version recommended by DHD. If you really have to update the firmware, follow the steps described above. (see Device Firmware )
You can use two ways to find out the current firmware version in a Device:
Select the desired module in the device tree to the left. Use the command from the menu or from the contextual menu. You can also press the F11 key. The dialog Information appears, which also lists the current firmware version.
Select the desired module in the device tree to the left. Use the command from the menu or from the contextual menu. You can also use the key combination Ctrl+F11. The dialog Information appears, which also lists the current firmware version for each module of the Device.
Mixer Setups save the overall state of the RM4200D system. Using the Maintenance Window, you can save a total of 7 setups that can then be loaded into the Console by the user. The setups 1 to 6 can also be changed and saved using the Console. However, Setup 0 is the default setup which is loaded after resetting the system. You can save this setup in the Maintenance Window only; it can be loaded from the Console, but can not be saved from there. (see Save Setup 0)
If necessary, you can also save the setups 1 to 6 from the Maintenance Window to have a base setup for further adjustments during operation. (see Save Setup 1…6)
Saving a Setup is confirmed by the following output in the right part of the window:
2004-07-21 09:29:20.273 RCV TCP Stud1 Module 5194 Code 0310: Message: Setup 0 saved in RAM
2004-07-21 09:29:21.371 RCV TCP Stud1 Module 5194 Code 0312: Message: Setup stored in Flash
If you replace a module in the Console, you may have to carry out some adjustments in the Maintenance Window. To do that, follow these steps:
If necessary, use the command to find out which module ID belongs to the defective module. Write down this module ID. (see Testmode)
Display the data of the module in question using the command . Save this information as file or write down at least the version number of the firmware of the module. (see Information ()
Change the faulty module. Then identify the new module in the Device tree of the Maintenance Window.
Check whether the firmware of the spare part is up-to-date. If not, update the firmware. (see Device Firmware )
Assign the module ID written down in step 1 to the new module. Check the correct assignment using the function .
![[Important]](../pics/important.gif) | Important |
|---|---|
You should not use modules with different firmware versions within the same RM4200D! If the spare part has an older firmware version than the other modules, you need to load the already existing firmware file again. But if the module has a newer version – e.g. because it is a newly shipped part – you first have to obtain the matching firmware version and version of the Toolbox4 software and use them to update the system. If necessary, you can also replace a newer version of the firmware by an older one. This is for example useful, if you need to integrate a new spare module into a RM4200D running an older firmware version. In this case, you can “downgrade” the new module. If you have any questions about this process, ask your DHD dealer or DHD support! | |
If you change the module RM420-850, you might have to order new license codes at DHD! (see Enter license code)
![[Tip]](../pics/tip.gif) | Tip |
|---|---|
You do not need a complete RM4200D if you just want to upgrade a single module. You can also use a serial connection for the update. This is especially useful in workshop environments or when servicing RM4200D systems in the field. (see also Updating the Firmware of Single Modules) | |
Use the command for the module RM420-850 to read out the current license information for the Device. You need a license code for the core operation of the system and maybe also for the Enhanced DSP functions (“Enhanced DSP Functions”). If you want to enter a new license code, use the command . (see Enter license code)
Using the Maintenance Window you can check whether all modules are correctly registered with the CAN bus. To do this, open the node of the desired Device and check whether all available modules are actually displayed. If this is not the case, the CAN bus cable could be broken, for example.
If you want to check the function of separate keys on the Console, use the command or the F4 key. to monitor the data flow on the CAN bus. Now press keys on the Console. The system then must send the corresponding commands via the CAN bus, which are displayed in the Maintenance window. If this does not happen, there must be an error. (see also Enable CAN Protocol ()
Apart from that, you can use the CAN bus protocol to record the codes of certain keys for scripts. (see also Scripts – Controlling Special Functions with Scripts )