Debugging Mode

<URL>: host name or IP address to the installed EMU hardware
By default debugging mode is disabled

(accessing the on-line EMU-emulator)


To achieve faster web page response times and optimize bandwidth usage, the web server transfers all files in a minified form. This means, that any character not needed for building the user interface screen is removed from original design files except some few comments. The dbg command leads the web server to send non-minified codes to the browser, so that the source code shown in the browser (using developer tools with F12 function key) is not only displayed well formatted, but also includes some additional comments for a better understanding and debugging.

In addition, the dbg command will turn on the local console debugging mode and let the code to generate additional log data to the local browser’s console. This should help the developer to understand the code easier. More information at: log – logging mode

The dbg command has only an impact of how fast the page is loaded and shown. Otherwise there is no code difference between debug and non debug mode.

An online emulator is also available and should help to debug and test the capabilities build in the hardware, without the need to have the hardware itself. Checkout the following example to get an idea how the EMU-emulator is working.

dbg – Example

Since all tests are done with Chrome, it is recommended to use also the Chrome browser when you follow the dbg-example below:

Try this:

  1. Open the link above in Chrome
  2. Hit the F12-key to start developer mode
  3. Hit the F5-key to reload the page
  4. Select the tab “Sources” in the menu line
  5. In the left side panel select the tab “Sources”
  6. Expand the cloud “”
  7. Expand folder “js”
  8. You will find the Java script files now not ending with “.min.js”
    These are non-minified java scripts for better debugging.