Hello,

a customer wants to read drive parameters (motor temperature, current, ...) from the Sinamics S120 using the Opc-Ua Server on the NC. So there is no direct connection from the client to the drive in this szenario: Client -> NC (Opc UA) -> Sinamics S120.

We already managed to read at least the temperature of the motoro (r0035) using the Opc UA path /DriveVsa/Drive/r0035[u8]. However, there seems to be no node for the current (r0068) within the address space of the Opc UA server. Only the following parameters are browsable and visible:

/DriveVsa/Drive/r0020
/DriveVsa/Drive/r0021
/DriveVsa/Drive/r0027 <- At least the smoothed current
/DriveVsa/Drive/r0034
/DriveVsa/Drive/r0035

Additionally there are 3 more parameters with a capital R (what is the difference here? Why is r0035 there twice - r0035 and R0035?):

/DriveVsa/Drive/R0035
/DriveVsa/Drive/R0078
/DriveVsa/Drive/R0081

We also gave it a try and simply called the OpcUa /Methods/ReadVar Method with an input argument of "/DriveVsa/Drive/r0068[u8]", even though the r0068 parameter is not visible in the address space. This did not only not work, but also killed the Opc-Ua Server. Only a reboot brought it back up... This actually happens every time a path is given as input argument that is not configured.

Has anybody experience with reading drive parameters through Opc Ua? Is it even possible to read parameters that are not visible within the address space such as r0068, or is the reading limited to the ones which are available in the address space (which is what I suspect  - but in this case, why?)?

I would appreciate any help, thanks!

Best regards,

Gregor