I'm wondering the same. Using the old symbol configurator opc ua server gave the node id using a string. Must be a way to specify this at build time?
Hi Yet another OPC UA question. When setting up a OPC server using "Communcation manager" (Symbol set and information model) in Codesys the NodeId is always given as "opaque" type. At least when browsing using UAExpert. Other standard OPC objects use numeric (or string) identifier, but for some reason my variables seems to get opaque/binary type. See attached photo. How can I change this? I can't see that this is a parameter in the CodesysControl.cfg. Can this be specified in the information model...
Hi After much trail and error I think I found the root cause to my OPC UA problem. The problem is that I cannot manage to build and download a program with a a custom OPC UA Information model. We use a Weidmueller WL2000 PLS, but the problem also exsist on the Win V3 PLC. Our custom information model is based on the latest versions of the OPC UA Core Nodeset v 1.05.03 (2023-09-20) and UA/DI nodeset 1.04.0 (2022-11-03) Those nodesets are installed in the Codesys Information Model Repository (3.5.19.6)...
Hi. Thanks for the answer. I think I found your post on the Wago forum. I have tried installing all different nodeset versions of the opcfoundation.org/UA but neither work. Though I could not find the nodeset version called 15.09.2021 anywhere online. The opcfoundation repository only goes back to version 1.04.11 2022-03-29. Also wondering how I can generate a custom information model that only refrences the latest version of nodesets?
Hi Did you found a solution for this? I also have the same problem
Hi Anyone have a solution for this? What is the reason?
Hi, Did you manage to solve the problem? I'm experiencing the same thing using a exported nodeset from UaModeler.