Hi,
Trying to debug an odd issue that appears in the field. Symptoms are as follows. Sometimes when the HMI PC (running Edge 90) is connected or first connecting (can be either, may be due to poor signal) we get stuck in a Comm Loss Connecting loop. The controller itself seems fine, but I’m suspicious.
Currently running PLCNext Engineer 2022.0.2 LTS and firmware 2022.0.4 LTS.
I utilize the Screen Number to determine if we’re serving up the standard or wide screen version of the HMI screens, by simple even/odd selection. Prebuilt displays are therefore pushed to a preassigned screen number. I’m wondering if either assignments of the same screen number (due to say an engineering laptop attaching at that number and then the remote trying to use the same) or some sort of timeout cache not being cleared is causing my issue.
I’d love to go with a random screen number to possibly bypass this issue, but there appears to be no other way to pass a variable from the bootup to determine initial start screen.
Some additional information.
I am not running login as I need logged out functionality, so my PLC project is providing access control.
When I look at the HMI_STATUS structure, it only ever registers one client. All clients are lumped in as I can see the IP address flickering between the systems.