About ChrisLarkin

HmiGuide · ‎12-01-2022

>>However, there's usually no reason to rename the item if the item name on your PLC changes, because the item name and item alias can be completely different.<< Seen from a theoritical point a agree, but for understanding a program, it's worse when you have different names on PLC and HMI side.

webiq-sk · ‎11-28-2022

Some additional info: each TLS certificate in general has expiration dates and dates from when on they are valid. If the date/time on the system is way off and does not fall in the validity period of the certificate errors like these will occur by design. This is not limited to WebIQ, but to any other system using these certificates so it will also happen on normal web servers as well. Therefore having the correct time set on a system is always recommended, preferably by using NTP.

cc2go · ‎11-08-2022

Good news, we identified the issue, it will be solved with v1.18 of ctrlX Works. As I already mentioned, device is working properly, just ignore the red symbol, when using in current verison like v1.16

webiq-sk · ‎08-19-2022

If you have the app not loaded or running you can open the file json/layouts/app-model.json. There you will find the "time-format" setting for your trend display which you can change: If you only use "$ss" there only the seconds would be shown etc. Please be careful when editing this file and be sure to make a backup before making any changes as if this file contains invalid JSON the app will not work anymore.

ChrisLarkin · ‎08-10-2022

It looks like there is an issue with my version of UA Client, it does not appear to create a certificate. I've successfully connected to the OPC-UA server using Web IQ, a certificate was generated correctly and I was able to trust it and gain a full connection to the server. Consider the issue resolved.

About ChrisLarkin

Re: Renaming variables

Re: OPC-UA "waiting_for_recconnect"

Re: IO-Link error

Re: Trend time resolution

Re: OPC-UA server cannot connect