About webiq-sk

It depends 🙂 In WebIQ tags (items) are stored per HMI project. As such if you have 9 non-identical (!) HMIs with different tags (different tags means the HMIs are not identical in WebIQ) you will have 9 different HMI projects. If you have 9 different HMIs with each one IO Handler you need a license with 9 IO Handlers if you want to run all 9 projects at the same time on the same server. Now the questions is: why do you want to do that? You could simply have a single HMI that contains all tags and have 9 different views in your HMI. Then the default 2 IO Handlers per HMI project would be sufficient. This would even make changes to the HMI easier as you'd only have to work on a single HMI project. You can have unlimited "views" in WebIQ where a "view" can be a view inside a tab panel inside a swipe panel inside a screen panel inside a tabl panel etc. You can build complex hierarchies of panel widgets in WebIQ and you could even - with some simple (Vanilla) JavaScript code - automatically open different views of the single HMI based on the URL e.g. by using "#view1" at the end of the URL, then "#view2" etc. ... View more

Sure you can have 15 clients or more connect to a single WebIQ Server instance. When it comes to WebIQ there would be no issue connecting to 12 OPC-UA data sources and using 1000 tags. However, this cannot be a simple yes or no reply, because it's completely based on how you implement your HMI and what your requirements are. In theory you could: - have 1000 tags displayed on a single HMI view (i.e. browser window) at the same time with all tags updated (changed!) every 100ms (the main issue here would probably be the graphics adapter on the display and the network latency) - have around 50 tags displayed on a single HMI view (i.e. browser window) at the same time that update every few seconds - or recording 1000 tags every second vs. recording 100 tags every 30 seconds These are not any limits or problematic for WebIQ - I just used them as arbitrary examples. Therefore our (WebIQ) recommendation is always to try it out - actually depending on how you implement an HMI you can cause more or less load on the system by splitting up the display into sub-views for example.   ... View more