FORUM CTRLX AUTOMATION
ctrlX World Partner Apps for ctrlX AUTOMATION
Dear Community User! We are updating our platform to a new
system.
Read more: Important
information on the platform change.
02-22-2024 07:54 AM
Hello,
I have the issue that WebIQ Trends showing up different on two different devices. The server runs on a CORE X3. On the picture attached I had connected a laptop (the trends look how they should) and a WR2110 (the trends look faulty).
On the WR21, the trends are not shown historically but show the actual values over the complete time interval (e.g. 1 minute, no affect of changing the interval).
There is a different behaviour in some other points too:
When unchecking and re-checking some trends via the Trens Select on both devices, the y-axes are grouped the way initially defined only on the laptop, not on the WR21.
In case I only selcet one trend to be shown, the laptop shows one fixed y-axis and the moving trend. On the WR21 the trend remains in the middle of the widget and the y-axis is moving instead.
Setup:
X3 with 1.20, WR2110 RC7, WebIQ 2.15.7 (both, designer and server).
The devices are offline but time is synchronised (on CORE via browser, on WR21 manually).
Any suggestions from you on how to fix that issue?
02-22-2024 12:52 PM
Some questions:
1. Are the timezones on the devices setup the same?
2. Does using the Date/Time widget in the HMI and connecting the "Systemzeit" item show the exact same time on both systems?
3. What does the system clock on both devices show? You cannot show this in the HMI
4. Is the affected system using a supported web browser?
06-12-2024 03:02 PM
reviving for similar issue.
08-07-2024 08:03 AM
To receive help on this please answer the questions I posted before. So far it's most often been one of the errors mentioned in the questions which are not WebIQ issues.
09-06-2024 10:35 AM
09-06-2024 03:10 PM
for me, i was able to fix it by checking the local hmi system time. I have no good way to set up a time server on the core, or to relay a time server from somewhere else to the core, so i have to manually set the hmi system time. It looks like webiq isnt sending a good T0 marker and is relying on synchronized timestamps (IMO).