Display MoreAs an option, you can store point name in addition in a CHAR array and declare your points as one array point.
Than you use an index to identify a point and its second name from the CHAR array:
DECL E6POS XMyPoint[10] ; or DECL E6AXIS...
XMyPoint[1] = {X ..., Y ..., Z ..., A ..., B ..., C ..., ...}
XMyPoint[2] = {X ..., Y ..., Z ..., A ..., B ..., C ..., ...}
....
XMyPoint[10] = {X ..., Y ..., Z ..., A ..., B ..., C ..., ...}
DECL CHAR MyPoint_name[10,32]
MyPoint_name[1,] = " MyPoint_1"
MyPoint_name[2,] = " MyPoint_2"
....
MyPoint_name[10,] = " MyPoint_10"
_________________________________________
...
LIN XMyPoint[1]
...
SWRITE(POS_NAME[], STATE, OFFSET, MyPoint_name[1,])
this is actually really interesting and useful information! thanks for this. the client i am working with that sits on the kuka controller is listening via UDP and TCP and has a live heartbeat. the variables it is monitoring currently are all live variables on the controller as things can change usually between setups. so it's not so useful to have direct settings like this in the sense it was setup for but definitely something that is helpful to know moving forward if i can add additional watch variables.
i've currently solved my issue with client side changes and c sharp logic as it's easier to change this side.