I have this issue with Kepsever EX 6.15: Runtime connection in Kepserver Configuration page can be established only if I disable Kepserver in Ignition gateway configuration. Error:
any idea how to solve that?
any idea how to solve that?
I don't understand what you are saying here.
- Do you know which program is generating the UascClientMessageHandler popup? It looks like Ignition is, but I don't remember seeing it before and can't find it in a web search.
- It's suggesting to me that the remote Kepware(?) service is running on 127.0.0.1 (localhost) which I assume is your Ignition gateway. Is that correct?
-
Are you saying that Kepserver EX Configuration program won't work while Ignition is connected to the Kepware server? That seems weird.
-
What OS are you using?
-
Which driver are you using in Kepserver?
You got it correct, @Transistor . OS-Windows Server 2016 VM, Vision 8.1.13
In the meantime I have isolated the problematic driver - Codesys 2.3.
Now I try to figure out which configuration parameters to tweak on Kepserver. Any thoughts?
Who's CoDeSys driver are you using? CoDeSys's or Kepware?
A bunch of us tried the OPC server written by CoDeSys and found that it was very awkward, troublesome and seemed to be old technology with no OPC UA, etc.
We purchased Kepserver EX for CoDeSys and all our problems went away.
I use Codesys v2.3 and v3 of Kepserver. V3 does not cause the problem, it is v2.3 that I disabled on about 8 devices and the problem disappeared. What configuration about Scan Mode did you use for your case, @Transistor ? The communication parameters are correct, I guess:
thank you, @Transistor . There are no differences indeed. I have focused mainly on Scan Mode options. No solution found so far.