QuickHMI
fast, easy, efficient!

QuickHMI FAQ – Häufig gestellte Fragen zu unserem HMI Scada System2025-01-10T13:20:18+01:00

QuickHMI FAQ - Frequently asked questions about your HMI/SCADA system

Here you will find answers to the most frequently asked questions about QuickHMI. Discover how you can get the most out of our modern HMI/SCADA-System and benefit from helpful tips for your projects.

picture: QuickHMI HMI Scada FAQ
What hardware system requirements do I need?2022-09-08T10:15:21+02:00

Generally it should be either modern, commercially available computer hardware. The following list gives an overview of the recommended equipment:

QuickHMI-Editor

  • CPU: at least 1.6 GHz or higher
  • 64 bit operating system
  • RAM: at least 2 GB, recommended 4-8GB
  • Hard drive: at least 60 GB SATA2
  • Network: 100 Mbps
  • Graphics: 3D-capable graphics chip with DirectX 9.0 support. A 3D-capable graphics card with its own 512 MB graphics memory is recommended (shared memory is not recommended).

QuickHMI Standalone Runtime

  • CPU: at least 1.6 GHz or higher
  • 64 bit operating system
  • RAM: at least 2 GB, recommended 4-8GB
  • Hard drive: at least 60 GB SATA2
  • Network: 100 Mbps
  • Execution of the software on the Raspberry Pi from version 3 possible

QuickHMI Viewer (alternative, if not desired in the browser)

  • CPU: at least 1.6 GHz or higher
  • 64 bit operating system
  • RAM: at least 2 GB, recommended 4-8GB
  • Network: 100 Mbps
  • Graphics: 3D-capable graphics chip
  • Execution of the software on the Raspberry Pi from version 3 possible
Which operating systems and components are required for the execution of QuickHMI?2022-09-08T10:15:21+02:00

QuickHMI-Editor

The QuickHMI Editor is executable under Windows 7 or Windows Server 2008 R2 or higher.
The .NET Framework 4.5.2 is required for the execution. If this is not available, you will be informed during the setup and you will continue to be given the option of an installation.
Depending on the operating system, it may be necessary to activate the .Net Framework 3.5 manually before installation under Windows. In this case, you will receive a corresponding message from the setup.

QuickHMI standalone runtime and QuickHMI Viewer

QuickHMI standalone runtime and QuickHMI Viewer work on Windows and Linux if the OpenJRE/OpenJDK 12 or newer and OpenJFX is supported by the operating system. Furthermore, there is an Android app available for Android, which can be executed from version 4.4 (Kitkat).
Running the QuickHMI server and the QuickHMI viewer requires OpenJRE/OpenJDK 12 and OpenJFX or later.

Execution by browser

The system can be invoked by all operating systems that provide an HTML5-capable browser.

The following browsers are tested and released for the compatibility with QuickHMI:

  • Chrome version 54 or higher
  • Mozilla Firefox version 46 or higher
  • Opera version 41 or higher

The use of other browsers may be limited, but not recommended. The browser should be installed in the newest possible version and kept up to date.

Does QuickHMI work in 32-bit / 64-bit environments?2022-09-08T10:15:21+02:00
Running the QuickHMI requires a 64-bit environment.
The display in the browser, however, can be performed on all 32/64-bit operating systems with HTML5-capable browser.
What is the QuickHMI Editor and what is it for?2022-09-08T10:15:20+02:00

With the QuickHMI Editor you create and edit the visualization project.
For surface creation you have many tools and resources available. It is a WYSIWYG-editor. Changes already made, you can view by pressing a key directly in an execution mode.

What is the QuickHMI Viewer and what is it for?2022-09-08T10:15:20+02:00

The QuickHMI Viewer provides an additional display medium (client) in the runtime environment.
Alternatively, the QuickHMI viewer can be used if viewing in the browser is not possible or desired.

In addition, the QuickHMI Viewer gives you the opportunity to adjust the provided software graphically and functionally to your requirements or corporate design. For this purpose, the QuickHMI viewer was released as an open source project.

You can find the Github project under:

https://github.com/IndiSystemsGmbH/QuickHMI-Viewer

What is the QuickHMI standalone runtime?2022-09-08T10:15:20+02:00

The QuickHMI standalone runtime provides the central server processes within the live environment and it communicates with the connected devices (PLC, Database, etc.).
The QuickHMI Viewer (Clients) and the browsers connect with the QuickHMI server (Part of the QuickHMI standalone runtime).
The QuickHMI standalone runtime is usually installed on a separate pc or server. But the installation can also be effected on a Client-PC.

Must the QuickHMI Viewer to be parameterized when it is used in the live environment?2022-09-08T10:15:20+02:00
No, the viewer has to be connected only with the server via TCP/IP.
All data required for the HMI-project process (such as masks, graphics etc.) pulls the viewer after connecting automatically from the server.
What should be considered when using QuickHMI in a network?2024-06-17T12:04:40+02:00

The network participants must be able to connect to the network. The connection must not be interrupted by a firewall or similar. Unfortunately, we cannot assist you with the configuration of your network; if in doubt, please contact your network administrator.
The QuickHMI viewers connect to the QuickHMI server. The QuickHMI server connects to the parameterized devices, such as PLCs.

Do I need to "roll out" the HMI project on all computers with the QuickHMI Viewer, for example during a project update?2022-09-08T10:15:02+02:00

No, after the start, the viewer pulls the project itself from the server.
If an update of the project should be carried out, that must be done only within the QuickHMI Server (Part of the QuickHMI standalone runtime).

Do I need the QuickHMI standalone runtime during design time with the QuickHMI Editor?2022-09-08T10:15:02+02:00

No, you don't need the QuickHMI Editor and the QuickHMI standalone runtime at design time. For developer tests is an own internal runtime environment integrated in the QuickHMI Editor.

How can I understand the basic principle of the QuickHMI license model?2022-09-08T10:15:02+02:00

The license model of QuickHMI is kept as simple as possible.

To create and maintenance your QuickHMI project with the QuickHMI-Editor you need to have an Editor license for each pc or workstation.

You do not need any other QuickHMI licenses.

Can I use QuickHMI non-commercial free of charge for teaching purposes at a school/university?2023-12-14T08:42:15+01:00

If you need a free license for schools or universities please contact us via e-mail at [email protected].
You'll receive a serial key as soon as possible.

How can I get the licenses?2023-12-05T11:35:24+01:00

To get the licenses you have the following possibilities:

  • on our website
  • by sending an email to [email protected]
  • by phone at +49 421 989703-30
  • by fax to +49 421 989703-39
How is the license to install?2024-03-05T14:10:44+01:00

The required license for the editor is delivered in a license file. After installing the license, the program will guide you through an activation procedure.

If you need help, please call us!

What type of PLC and devices can I connect with QuickHMI?2024-10-29T14:03:53+01:00

QuickHMI is compatible with:

  • Siemens S7 controllers via put/get access (200, 300, 400, 1200, 1500, ET200SP series as well as SoftPLC WinAC RTX), Logo!0BA7 and Logo!0BA8 as well as CPUs from other manufacturers (e.g. VIPA 100V/200V/300V/300S)
  • Siemens S7 controllers via symbolic access (1200, 1500, ET200 series) 1*)
  • OPC UA interface
  • TWINCAT2 from version 2.1 and TWINCAT3 2*)
  • MODBUS TCP, RTU, RTU via TCP or ASCCI
  • Allen-Bradley “Control Logix” or “Compact Logix” controllers via Ethernet/IP protocol
  • KNX/EIB
  • MQTT protocol
  • Various SQL databases using JDBC
  • Files from the file system with the file system data source
  • InfluxDB

Native migration of additional protocols is planned.

*1) Certain requirements must be met for symbolic access:

  1. The controller software must have been created with at least TIA version 17.
  2. If software components were created with an earlier version, they must be recompiled and transferred with TIA version 17 or higher. The same applies to the hardware configuration of the PLC.
  3. At least the following firmware versions are required:
    • S7-1200 series with firmware versions V4.5, tested and validated up to version 4.6
    • S7-1500 series from firmware version V2.9 , tested and validated up to version 3.1
    • S7-ET200SP series from firmware version V2.9 , tested and validated up to version 3.1
  4. If a password has been assigned at controller level, you must have it. The password can be transferred up to firmware version 3.0 (1500 and ET200 series) or 4.6 (S7-1200 series). For higher firmware versions, the login mechanism has changed on the PLC side; the new “Anonymous” user must be configured and enabled in the PLC.

*2) TwinCat data sources are not executable under Linux. If these are to be executable under Linux, the use of OPC UA data sources is recommended.

How would you describe the software architecture of QuickHMI in the productive mode?2022-09-08T10:15:01+02:00

QuickHMI is a client-server architecture, where the clients do not connect directly to the plant but to the QuickHMI server process.
The installed services of the QuickHMI server communicate with the connected devices (e.g. PLC) and make the data available centrally to the clients in the network.
The clients connect to the runtime and visualize the data or send write commands to the server, which then forwards them to the devices (eg PLC).
As an alternative to the client-server architecture with central processing, the system can also be operated as a pure client application.
If you have any questions, we are happy to advise you and look forward to hearing from you via [email protected]

What happens to my data after registration?2022-09-08T10:15:01+02:00
The data entered by you will be kept confidential in accordance with the Federal Data Protection Act.
A processing of the data occur only for internal purposes, such as the management of licenses, newsletter etc. A disclosure to third parties is excluded.
Does QuickHMI support querying or writing variables with symbolic addressing from a S7 PLC?2022-09-08T10:15:01+02:00

No, natively it can be read or written only absolute addresses of S7 PLC.

However, access to variables with symbolic addressing is possible via the OPC UA interface. This requires an OPC UA server with the corresponding function.
The latest-generation S7-1500 controllers already have an integrated OPC UA server for accessing the symbolic variables.

I cannot access an S7-1200, 1500 or ET200 PLC, what do I have to set?2024-10-29T13:05:15+01:00

It is possible to access inputs, outputs, flags and enabled DBs with QuickHMI. Access to an S7-1200, 1500 or ET200 controller is deactivated by default. You must carry out the following steps to enable access to the controller:

If you use absolute addressing (Put/Get) for access, you can only access non-optimized blocks. If you use symbolic addressing, however, you can access non-optimized and optimized areas.

Prerequisites for put/get access

Access to an S7-1200- 1500- or ET200 is deactivated by default. To activate it, you must carry out the following steps:

Up to firmware version 3.0 (S7-1500 and ET200) or 4.6 (S7-1200)

  1. Allow the general access. Activate in the property settings section protection the option 'Connection mechanism - Allow access PUT/GET communication from remote partner.
  2. Enable access to your DBs. Go to DB properties and deactivate 'optimized access'.
  3. Load to PLC, done!
    If the changes don't have any effect, use 'extended download to device' to load to PLC.

Firmware version 3.1 (S7-1500 and ET200) or 4.7 (S7-1200) and higher:

  1. Go to “Security settings” in the project navigation.
  2. Double-click on “Users and roles”.
  3. Select the “Roles” tab.
  4. Create a new role and assign a name, for example “HMI_Access”.
  5. Open the “Runtime rights” tab.
  6. Select the corresponding PLC from the “Functional rights categories”.
  7. Activate the “HMI access” access level in the “Function rights”.
  8. Go to the “Users” tab in the “Users and roles” area.
  9. Activate the user “Anonymous”.
  10. Confirm the displayed message with “OK”.
  11. Assign the newly created role to the anonymous user under “Assigned roles”.
  12. Open the “Device view”.
  13. Go to the “Properties” of the CPU.
  14. Select “Protection & Security > Connection mechanisms” in the area navigation.
  15. Activate the option “Allow access via PUT/GET communication by remote partner”.
  16. Save the configuration, translate the project and transfer the changes to the CPU.

Certain requirements must also be met for symbolic access:

  1. The controller software must have been created with at least TIA version 17.
  2. If software components were created with an earlier version, they must be recompiled and transferred with TIA version 17 or higher. The same applies to the hardware configuration of the PLC.
  3. At least the following firmware versions are required:
    • S7-1200 series with firmware versions V4.5 to 4.6
    • S7-1500 series from firmware version V2.9 to 3.1
    • S7-ET200 series from firmware version V2.9 to 3.1
  4. If a password has been assigned at controller level, you must have it. The password can be transferred up to firmware version 3.0 (1500 and ET200 series) or 4.6 (S7-1200 series). For higher firmware versions, the login mechanism has changed on the PLC side; the new “Anonymous” user must be configured and enabled in the PLC.

Important, firmware version 3.1 (S7-1500 and ET200) or 4.7 (S7-1200) and higher: Configuration of the “Anonymous” user for symbolic access.

  1. Go to “Security settings” in the project navigation.
  2. Double-click on “Users and roles”.
  3. Select the “Roles” tab.
  4. Create a new role and assign a name, for example “symb_Access”.
  5. Open the “Runtime rights” tab.
  6. Select the corresponding PLC from the “Functional rights categories”.
  7. Activate the desired access level “Full access”, “HMI access” or “Read access” in the “Function rights”.
  8. Go to the “Users” tab in the “Users and roles” area.
  9. Activate the user “Anonymous”.
  10. Confirm the displayed message with “OK”.
  11. Assign the newly created role to the anonymous user under “Assigned roles”.
  12. Save the configuration, translate the project and transfer the changes to the CPU.
Access to a Logo! PLC doesn't work, what should I do?2025-01-08T09:35:10+01:00

It is possible to access inputs, outputs, flags and accessible DBs. The access to a Logo! plc is disabled by default. You have to process the following steps (sorry only screenshots in german language available):

1. Choose Extras >> Ethernet-Connection (Context menu) new connection:

picture: logo connection overview

2. Use the following settings:

picture: logo tsap overview

3. Save and load to the plc, done!

Warning message about a non-secure connection (NET::ERR_CERT_AUTHORITY_INVALID) appears when accessing the Runtime Server via a browser, what can I do about this?2024-02-20T14:25:19+01:00

The warning message is displayed because we deliver QuickHMI with a self-signed SSL certificate. This certificate is not signed by an official certificate authority and therefore gives you this error. However, the connection is in fact encrypted and secure. The browser simply reports that it cannot check whether the server is who it claims to be.

If you do not want to see this message, you have two possibilites:
1. You can purchase an SSL certificate from a certificate authority or use a free of charge service. In both cases, you will receive a certificate that you must import into the Runtime Manager then. After that, you will no longer receive this error message.
2. You can set the QuickHMI certificate as trustworthy: You can configure your computer so that it recognizes the certificate issued and signed by QuickHMI itself as valid.

To do this, first save the certificate from the browser in a local file and then import the certificate into your "Trusted root certification authorities".

It is important that you use the host name that is also entered in the certificate for the connection in the browser.

Nach oben