Discussed this with SDK provider and UA Expert support. They believe the issue is with Codesys server configuration. Reported it to Codesys as bug. Will do further testing on my side with VDMA configured OPC UA server for KUKA robot.
Apologies if the wrong forum. I am using Unified Automation SDK for OPC UA client. When I connect to Codesys OPC UA server, the 3D data type variables in my Codesys project are being recognized as custom types instead of OPC UA standard ones, e.g. Application.underscore3DVector instead 3DVector. This is causing issue in my client because the variables need to be mapped to corresponding vector and matrix properties in the main application (3D simulation). I know that Codesys OPC UA server is using...
Apologies if the wrong forum. I am using Unified Automation SDK for OPC UA client. When I connect to Codesys OPC UA server, the 3D data type variables in my Codesys project are being recognized as custom types instead of OPC UA standard ones, e.g. Application.underscore3DVector instead 3DVector. This is causing issue in my client because the variables need to be mapped to corresponding vector and matrix properties in the main application (3D simulation). I know that Codesys OPC UA server is using...