I have not used this client / server OPC UA combination since. We were only making some kind of proof of concept. I did understand that there could be some kind of bug. I do not know if the supposed bug has been resoved since. Perhaps you could try what piautomation is suggesting
the target is the codesys software executing the PLC code like ladder / instruction list etc...
I had some help from Codesys to debug this problem. It seems there was a problem within the target (a bug?). I only used for a proof of concept. Possibly it will work with a new version of the target
I'am testing the OPC UA client (datsasource) using the control win V3 in demo mode (version 3.5.18 patch 40).T The opc UA server is a B&R Buscontroler type X20BC008T which is to be connected to an Codesys PLC with a target 3.5.18.40. Both 'sign and encript' and loggin are recquired When configuring the datasource the OPC UA server is found and the available variables are shown and imported. I've created the datasource initialser with the same username and password used to import the variable. How...
I'am testing the OPC UA client (datsasource) using the control win V3 in demo mode (version 3.5.18 patch 40).T The opc UA server is a B&R Buscontroler type X20BC008T which is to be connected to an Codesys PLC with a target 3.5.18.40. Both 'sign and encript' and loggin are recquired When configuring the datasource the OPC UA server is found and the available variables are shown and imported. I've created the datasource initialser with the same username and password used to import the variable. How...