About HmiGuide

I attached the current version of “WebIQ Installation and Licensing settings for ctrlX” (PDF) One additional important hint: When you want to connect to WebIQ server running on ctrlX, you must create a special WebIQ Designer shortcut. This is described in the PDF, too. Alternatifely, just unzip "NewWebIQ-Designer-shortcut.zip" and start included script "NewWebIQ-Designer-shortcut.vbs". ... View more

If I understood the history correct, currently it's not clear where the problem comes from (communication, VR31 HW, VR31 performance, ctrlX, trending, ???...). This means you have to check all the different error reason. Do you use any communication check e.g. the Heartbeat widget? For debugging I would do the following: Create a counter variable in PLC Display the counter variable in the header of your WebIQ project, that it is always visible. With this you can verify if the communication is running stable. If communication is not stable, continue with finding the reason for it. (Communication settings, PLC performance, VR31 performance,  ....) ... View more

Keep in mind the default alignment of variables in RAM which can cause unused bytes between the structure variables. To remove that fill bytes, you can put {attribute 'pack_mode' := '1'} into the structure definition. => Because of the WORD based adress in Modbus, you should NOT use any data types with size 1. (as. BYTE, BOOLEAN,...) For more info see PLC docu: pack_mode ... View more