MLC OPC UA issue from WinCC

[BGrieger]

A customer is updating an existing press line and the update changes include switching from OPC-DA to OPC-UA.  Their MLC's symbol file is built and loaded with the appropriate variables.  They can browse the variables from their MLC (14v20) with UA Test and UAExpert successfully.  When they try to browse the symbols with their Simatic WinCC tool they see the end point and connect to it, but then it shows disconnected and they can't browse the symbols.  They would like to maintain and use the connection without being disconnected.

[Leon_Paridaans]

Maybe something with Identity token or Security policy?

To check this right click the PLC > Communication > Protocols

[NoRisk4Project · Accepted solution]

Hello,
which endpoint is used by UA Expert and which by WinCC? As already mentioned, a not supported identity token or security policy could lead to refusing the connection. Do you get any (error / warning) message inside the WinCC tool?
A WireShark trace would be very helpful to see who (server or client) rejects the connection and why.

[BGrieger]

I appreciate the ideas.  I have sent the to the customer and I'm waiting for a reply.