<- dhdcs:v3:file_menu|File ^ dhdcs:v3:start|DHD Communication Server ^ dhdcs:v3:logging_menu|Logging ->

====== Device Menu ======
The ''Device'' menu offers variable functions to maintain your DHD devices.

[{{ :dhdcs:v3:device-menu.png |//DHDCS Device menu//}}]

===== Reconnect =====

The ''Reconnect'' command interrupts the TCP/IP connection between the computer and the selected device and opens it again. This way, the current settings of the device are read out automatically.
<WRAP center round tip 80%>
**Tip**\\  For certain functions, transferring the commands can take quite a while, longer than the Refresh process of the Maintenance Window. In this case, the old values are shown although the new one are available to the hardware already. Use the ''Reconnect'' function to check the settings if in doubt.
</WRAP>

===== Network Config =====

With this command, you open the ''Network Config'' window of DHDCS. In this window you can change the IP settings of the selected DHD device in DHDCS devices list. 

There are two ways to change the IP configuration of a DHD device: 

[[#requested_device_is_available_in_the_list_a|(a) The requested device is available in the DHDCS devices list]] 

[[#requested_device_is_not_available_in_the_list_b|(b) The requested device is NOT available in the DHDCS devices list]] 

==== Requested device is available in the List (a) ====

  - Right-click on the device name in the list. 
  - In the contextual menu, select ''Network Config''
  - The ''Network Config'' window opens and shows the IP configuration of the device.

[{{ :dhdcs:v3:network-config.png?nolink |//The "Network Config" window shows the current IP configuration of the selected device.//}}]
 
In the ''Network Config'' window, you can change the current IP configuration of a certain device. 

=== Serial No ===

The selected device, is always represented by its ''Serial No''. This serial number is unambiguous and valid for only one DHD device. The field is used to read out settings of devices that are located in a different network segment. Find more details on this in the following section "[[#requested_device_is_not_available_in_the_list_b|Requested device is NOT available in the list (b)]]". 

=== Hardware Name ===

Every DHD system can be assigned a ''Hardware Name'' for better identification of the system. This name helps to identify the device in the network. You can choose any name, it can be up to 30 digits long but may not contain spaces. Special characters that are not allowed, can not be entered. In DHDCS only the first 10 digits of the hardware name are shown.

=== Automatically via DHCP ===

If a DHCP server is located in the network that manages the IP configuration of the selected device, select the option ''Automatically via DHCP''.

=== Fixed - Fixed IP setting ===

If you have no access to a DHCP server or want to adjust the IP configuration manually, first select ''Fixed'' and then enter the appropriate values (''IP-address, Subnet Mask, Gateway, Broadcast'') into the appropriate boxes. 

<WRAP center round tip 80%>
**Tip**\\  As factory default DHD devices will be delivered with IP basic settings based on their MAC address. See [[network:ip#ip_basic_settings|IP basic settings]] for more information.
</WRAP>

<WRAP center important 80%>
**Important**\\  In case of question concerning the parameter settings, ask your IT department or your system administrator.
</WRAP>

=== Time Server ===

DHD systems have an internal system time that can be synchronised using a NTP Time Server. To do this, enter the IP address of your NTP Time Server in the ''Time Server'' box.

Depending on your chosen time server you may need to enter some further settings. Click ''Setup time zone and DST'' to be able to enter a general time zone offset and if necessary the settings for the daylight saving time.

<WRAP center round tip 80%>
**Tip**\\  A standard Windows PC can be used as NTP time server, see [[:installation:windows_ntp_time_server|Configure Windows as a NTP time server]]
</WRAP>

With 52/XC2/XD2/XS2 cores you also can define two additional Time Servers. If the primary time server is not reachable, the core will use ''Additional Time Server 1''. If ''Additional Time Server 1'' is not reachable, the core will use ''Additional Time Server 2''.

==== Requested device is NOT available in the List (b) ====
You need to add the device manually to your list by using [[dhdcs:v3:logging_menu#add_device|Logging > Add device]].
 
After adding the device manually to the DHDCS it might be possible, that the ''Network Config'' window opens with all boxes empty. Click ''Retrieve Current''.

<WRAP center round important 80%>
**Important**\\  If ''Network Config'' window is empty:
  - Check [[dhdcs:v3:administration_menu|DHDCS settings]] of network interface and broadcast address
  - Check firewall settings
  - Check your network: are UDP broadcasts allowed?
</WRAP>

[{{ :dhdcs:v3:network-empty.png?nolink |//Entering the serial number of the desired device.//}}]

This way the device will transfer the current IP settings. These are then shown in the ''Network Config'' window and can be changed there. 

Changing the data is carried out exactly as described in [[#requested_device_is_available_in_the_list_a|Requested device is available in the List (a)]]. Changed data are finally transferred to the device by clicking ''Send''.

Nevertheless, if the device is not reacting, communication could be blocked by certain IP settings. In this case it is recommended to adjust the IP settings of the computer to the ones of the device. To do this, temporarily change the IP address of the computer to the one valid for the device. (see [[network:ip]])

==== There is no communication possible with the device ====

If, despite all efforts, the device is not reacting although there is a physical connection to your network, the communication might be blocked due to the current security settings in the network. In this case, check which measures for a higher network security may be dropped (e.g., firewalls, router, managed switches, …). 

For solving the connection problems, contact the responsible IT department and check which of the measures described in the network specification have to be done to establish a communication between PC and DHD system. 

===== Enter License =====

**See [[licensing:start|Licensing Pages]] for more Information.**

Using this command, you can enter the license codes. There are license codes for the firmware, for software operation and for feature upgrades, like the ''Enhanced DSP Processing'' license.

[{{ :dhdcs:v3:enter-license.png |//Enter license dialog//}}]

To send a license or voucher code to the DHD device, enter it in the ''License or Voucher Code'' text box and click ''Apply to Device'' button. 

If the License code entered was valid, ''Store License: Ok'' message appears. If the License code entered was invalid, ''Store License: failed, License Invalid'' error message appears.

<WRAP center round tip 80%>
**Tip**\\  You can find out all licesnses of your device on the system page of Web Apps (firmware version 9.1 or higher):
  - Double click the device entry in the DHDCS device list. Your computers browser opens.
  - Click the system icon {{:dhdcs:v3:system.svg?24|}} in Web Apps.
  - On the ''Firmware'' > ''License Information'' page, all licenses are listed.
</WRAP>

===== Show Protocol Window =====

''Show Protocol Window'' opens the protocol window. In this window, you can track all sent UDP and TCP/IP messages in the network. Select the ''Enable Protocol'' check box to start the recording of the protocol. 

If you want to see the messages of the device selected in the list only, select the ''Filter foreign UDP blocks'' check box. Click ''Clear Window'' to delete all messages in the protocol window. The log file is not affected by this. 

In the boxes ''TCP Block'' and ''UDP Block'' you can enter a TCP/IP or UDP command directly and transfer it into the network, by clicking ''Send''. 

All sent commands are saved and available in drop-down menus at the boxes ''TCP Block'' and ''UDP Block'' to be sent again. If you want to delete all saved commands, click ''Clear History''.

<WRAP center round important 80%>
**Important**\\  Use this function only if advised by your DHD distributor or DHD.
</WRAP>

===== System Status =====
==== Save To File ====

In the ''Device'' menu, select ''System Status'' > ''Save to File'' to save the currently read out status of the device. A file named ''System_Status_<Project ID>_<Hardware Name>_<Date>_<Time>.tgz'' is created. 

If you want to read out the saved content, you first have to unzip it using a ZIP-decompressor. The result is a file with the same name but the extension ''.tar''. Now, open this file using a RAR-decompressor. Finally, some files with the extension ''.xml'' emerge as well as some files necessary to show the XML files. You can view the XML files in a browser (e.g., the Microsoft Internet Explorer). For this, open ''index.xml''. The view is the same as if you had selected the device in the device list. Then, you can view the other pages like in the Maintenance software. 

<WRAP center round tip 80%>
**Tip**\\  This system state is often requested by DHD support.
</WRAP>

==== Send By Mail ====

This function creates in a first step the same zipped file like the command ''Save to File''.

Then, you instantly can send this file per e-mail to DHD support. For this, it is necessary to have an E-Mail Client installed on the PC and to set up an user account. In this case, a new mail window is opened automatically and the files created are attached. Only click ''Send'' and the e-mail is transferred to the DHD support team. 

==== Download ====

If you created a system status - file using ''Save To File'' or ''Send By Mail'' and don't want (or don't need) to create a new file, you can download the already created file here.

<WRAP center round info 80%>
**Note**\\  It is always recommended to create a fresh system status using ''Save To File'' or ''Send By Mail'' when contacting DHD support. This function is for debugging purposes only.
</WRAP>

==== Restore Snapshots ====

With this function it is possible to transfer one or more mixer and channel snapshots from the PC to the console. (Use the function [[#Save_to_File|Save to File]] to save all mixer and channel snapshots of a device)

<WRAP center round info 80%>
**Note**\\ A firmware reset is required if mixer or channel snapshot names are also being restored.\\ Otherwise the restored snapshot names will not be shown in snapshot menus.
</WRAP>

<WRAP center round important 80%>
**Important**\\  Snapshots created with firmware version 9.0 or below are not compatible with firmware version 9.1 or higher and vice versa.
</WRAP>

Alternatively you can use [[webapps:snapshots:start|Snapshots App]] to manage your Snapshots.

===== Mixer 1 to 4 =====

In Toolbox software you can create several virtual mixers for a DHD core device. Select the mixer that you want to handle. If you did not create virtual mixers, operate in ''Mixer 1''.

==== Save Snapshot 0 ====

This command copies the current parameters of a DHD core device to the ''Mixer Snapshot 0'' storage on the Micro SD-Card. This way, the settings are kept also after switching off the device and can be used as default setup after a reset. Snapshot 0 can also be loaded via the console like all other snapshots. 

<WRAP center info 80%>
**Note**\\  ''Snapshot 0'' defaults can only be saved using this command or using [[webapps:snapshots|Snapshots App]]. **There is no option to do this at the console!**
</WRAP>

First you have to select the desired device to trigger the command. After that, a security confirmation message ''Save current Parameter settings as default?'' is shown. After confirming with ''Yes'' the settings are copied.

<WRAP center important 80%>
**Important**\\  It is vital to choose the command ''Save Snapshot 0'' after every setting into operation of a new DHD device.
</WRAP>

==== Clear Parameter Memory ====

This function sets all DSP parameters of all channels to their respective default values.

<WRAP center important 80%>
**Important**\\  Resetting the parameters influences the audio processing of all channels. Make sure that it does not adversely affect important signals.
</WRAP>

===== Firmware Reset =====

Select ''Firmware Reset'' to restart the firmware of the selected device. 

<WRAP center alert 80%>
**Warning**\\  A firmware reset temporarily interrupts the audio processing of the system. Only perform a firmware reset if you are sure that it does not influence important signals.
</WRAP>

<WRAP center round info 80%>
**Note**\\  For more informations on the differences between Firmware Reset and System Reboot, visit [[installation:reset_behaviour|reset behaviour page]].
</WRAP>

===== System Reboot =====

Select ''System Reboot'' to restart the boot loader of the selected device.

<WRAP center alert 80%>
**Warning**\\  A system reboot temporarily interrupts the audio processing of the system. Only perform a system reboot if you are sure that it does not influence important signals.
</WRAP>

<WRAP center round info 80%>
**Note**\\  For more informations on the differences between Firmware Reset and System Reboot, visit [[installation:reset_behaviour|reset behaviour page]].
</WRAP>
===== Factory Test =====

This function can be used to check every single element of the fader and control modules of a mixing console. 

Before a device is shipped, the functionality of all elements is tested by DHD. If you think that your console could have a hardware problem (e.g., a key is not working), you can clarify this with the aid of this function.

Before you use this option, you should transfer an empty configuration to the device. This makes the results more clear, because there will be no overlapping with the configured functions. Therefore, add a new device to your Toolbox project and transfer this empty configuration into the device.

Testable with this function are faders, keys, encoders, potentiometers, OLED displays, brightness sensors, TFT displays and LEDs.

/* === Keys ===

By pressing a key it will light up for approx. 3 to 5 seconds. Independently if you press the same or several keys after each other, the colour of the light will change automatically depending on possible states of the key (e.g., yellow-red-green, yellow-red-yellow or green-red-green). Additionally, pressing the keys of fader modules sets the fader values to defined positions (approx. +10 dB, -6 dB, -25 dB and -oo). Of course the fader itself will only move if it is a motor fader.

=== Faders ===

The current fader position is shown in the OLED display of this fader module as a digital value (typical values: min.=0005, max.=4093).

The modules 52-4240 and 52-4241 have six LEDs next to the fader (PGM 1/2, AUX 1-4). In the factory test mode, these LEDs also represent the fader value, but not that exactly as it is done in the OLED displays. The LEDs are standing for several bits (PGM 1 = 2^6 = 64, PGM 2 = 128, AUX 1 = 256 and so on). The LEDs of the modules 52-4230 and 52-4231 do not represent a bit pattern, they are driven as a running light. 

If the console is grounded correctly, you will see a ''T'' in the OLED display when touching the fader. Also moving the fader is recognized as a touch and will cause a'' T ''in the display.

=== Encoders ===

In the OLED displays next to the encoders a value between 00000 and 65535 is shown that can be increased and decreased using the encoder. On pressing the encoder, a key of the same module lights up (pressing several times changes the colour).

=== Potentiometers ===

In the OLED displays next to the potentiometers a value between 0001 and 4093  is shown that can be increased and decreased using the potentiometer. */