You can use the DHD Communication Server to log activities of a DHD system in detail or in a long-time recording. To make the troubleshooting successful, the following tips may help:

  • Use a dedicated computer for monitoring the system. For complex systems with a high number of Global functions, there can emerge heavy network traffic that needs to be logged. To do that, use a sufficiently powerful PC.
  • Check the network. Before starting the logging, check the used network. You must avoid to operate DHD devices and the logging computer with the DHDCS in an existing office network. The data traffic in such a network can disturb the transfer of UDP messages significantly. A DHD system with several devices should have its own network segment in which also the computer with the DHDCS is running.
  • If necessary, use two network adapters. If you need to remotely control the logging computer, it should be equipped with two network adapters. One should be located in the same network as the DHD devices, the other one in the general network where also the controlling computer is running.

For more information on recommended network architecture, see General Network Specifications.

  • Make sure there is enough free disk space. Especially for long time logging, it is necessary to have enough space available for the log files. If you want to store the files on a file server, check in advance whether this works in your network as desired.
  • While Log Level 0 logs only the most critical system events like reboots or I/O box reconnections, Log Level 6 is more useful for debugging. It provides additional detailed data about events like pressing a button, fader movements or control data sent from automation systems. You can change the Log Level in the Main Window for each device by right-clicking on the devices list entry.

Use Log Level 0 for general logging. Use Log Level 6 for debugging.

  • Compress the logfiles. Use an archive or compressing program to reduce the size of the protocol files, especially if you want to transfer the files via e-mail. By compressing, the file size is reduced to 5-10% of the original size.
  • Plan the trouble shooting. Certain errors occur only under certain conditions. If you suspect such an error, try to find out, when and under which conditions it is probable. Often, an error can be related to certain times of the day or certain user procedures. Record especially at the times in question. This way, try to keep the amount of data as low as possible to make analysis easier.
  • Use special software to analyse logging data. Short log files can be analysed using the Windows Editor. But if you have to search several hundred Megabyte of data for a certain message, the effort is very high. In such cases, use a software that can handle and search big text files. One of these programs is for example Notepad++ (www.notepad-plus-plus.org). Using it, you can effectively search huge text files and extract important information.

If you have any questions concerning the analysis of log files, please contact your local DHD distributor.

Log Level 0 messages will automatically be logged if UDP broadcasts are enabled on your Network. To setup a higher log level, right click on the devices list entry and select the designated log level DHDCS will automatically establish a TCP connection to the device.

If UDP broadcasts are disabled or you added your device manually, select Log Level 1 instead of log level 0. This will produce the same output as log level 0.

The function TCP Protocol ON & TCP Protocol OFF is a legacy function used for logging of 52-4200 systems. It is not recommended to use this function with current systems, since parallel use with one of the Log Levels 0-6 will generate many redundant log messages. It will unnecessarily fill up the logfile and make it less readable.

Active TCP connections will be displayed as TCP entry in Main Window, ''Conn'' table column.

You can prevent DHDCS from being closed when loggig is active. To do so, go to Logging Menu, Options Window and enable Do not quit server while protocol is active. Closing the server, while any TCP logging connection is active (any log level is set), will result in Protocol is active. Server could not stop. error message.