Starting runtime mode

To run and test the application, click on "Runtime" in the menu. Here you can start the runtime in different modes.

You have the choice between "Web Viewer", "Desktop Viewer" and "Server only". The 3 runtime buttons are available for this.

Web Viewer:

The visualization server starts and shows the user interface in a selected browser.

You can set with which browser installed on your system the project is displayed.

The selected browser is displayed as an image for the Web Viewer button.

>> Web Viewer

Desktop Viewer:

The visualization server starts and shows the user interface in the QuickHMI Viewer desktop application.

>> Desktop Viewer

Server only:

The visualization server starts without showing the use interface. You can connect to the server using any browser,

our QuickHMI Desktop Viewer or our QuickHMI Android App.


In addition, you have the option to determine which initial zoom level is to be used and which ports are to be used.

You can also set the data compression between the server and the browser and set the maximal java heap size.

To do this, click on "Ports" in the “Runtime” menu.

A detailed description of the settings can be found in the "Project settings" sub-chapter.

>> Project settings

Click on "Start" to run the runtime mode.


You can use the "Simulation" button to activate the data source simulation. Have random values of your variables simulated or set them manually.

In this window all created data sources appears and can be activated for the simulation via the checkbox.

On-screen keyboard:

For devices without physical keyboards it´s possible to show an on-screen keyboard as soon as an input field is market. Here you can set the layout to be used for this keyboard.

The layout can also be changed directly during runtime. This is done by using a parameter in the URL.

How this works you can find out in the "On-screen keyboard" chapter of this documentation.

>> On-screen keyboard

Incompatible browsers:

If the runtime is started in an unofficially supported browser (supported are Firefox, Chrome, Opera, IE (>= 11) and Edge),

an error message appears which must be confirmed first.

To avoid this message the URL can be extended with the following parameter:

  • "ignoreBrowserCompatibility"

So, a call can look like this to bypass the warning message:

  • https://localhost:6064/?ignoreBrowserCompatibility