The R parameters are found under the identifier "/Channel/Parameter/R", which is eventuallymapped to "/Channel/Parameter/R[u1, 1]". If you want to access other parameters, you mustcorrespondingly extend the identifier, e.g. "/Channel/Parameter/R[u2, 56]".Table 5-1 Examples of variable paths (NC access operations)Variable path Description/Channel/Parameter/R[u1,10] R parameter 10 in channel 1/Channel/Parameter/R[u1,1,5]/Channel/Parameter/R[u1,1,#5]R parameter arrayR parameters 1 to 5 in channel 1/Channel/GeometricAxis/name[u2,3] Name of the 3rd axis in channel 2/Channel/GeometricAxis/actToolBasePos[u1,3] Position of the 3rd axis in channel 15.3.2 Variable paths for GUD access operationsGUD variables can be found in the OPC UA server under the "/Sinumerik/GUD" node.The displayed GUD variables always represent only the first parameter (for GUD arrays) ofthe first NC channel (for channel-dependent GUD variables). If you want to access a differentparameter of a GUD array or a different channel, you must extend the identifier accordinglyfor the NC access.GUD arrays are 1-indexed for access, and access is always one-dimensional. This means,the index must be calculated for multi-dimensional arrays.Example 1: One-dimensional array, NC-global GUD array"UGUD.DEF" fileDEF NCK INT ARRAY[2]M17Access is performed as follows:ARRAY[0] → /NC/_N_NC_GD3_ACX/ARRAY[1]ARRAY[1] → /NC/_N_NC_GD3_ACX/ARRAY[2]Example 2: Two-dimensional array, channel-dependent GUD array"UGUD.DEF" fileDEF CHAN INT ABC[3,3]M17Functionality5.3 Variable accessSINUMERIK Integrate for Engineering Access MyMachine / OPC UAConfiguration Manual, 12/2017, 6FC5397-1DP40-6BA1 39