Hello Henri,

Here is an example how that could be done, it puts the length of each path into a comment. Of course that would also work with IDs etc.

`LIN {X 88.173, Y 74.122, Z 0, A 0, B 90, C 21.114, E1 0, E2 0, E3 0, E4 0} C_DIS`

LIN {X 89.288, Y 74.122, Z 0, A 0, B 90, C 21.066, E1 0, E2 0, E3 0, E4 0} C_DIS

LIN {X 89.288, Y 74.122, Z 20, A 0, B 90, C 21.066, E1 0, E2 0, E3 0, E4 0}

;Path length: 50

LIN {X 71.788, Y 74.122, Z 20, A 0, B 90, C 21.829, E1 0, E2 0, E3 0, E4 0}

LIN {X 71.788, Y 74.122, Z 0, A 0, B 90, C 21.829, E1 0, E2 0, E3 0, E4 0} C_DIS

LIN {X 71.788, Y 72.51, Z 0, A 0, B 90, C 22.011, E1 0, E2 0, E3 0, E4 0} C_DIS

LIN {X 71.788, Y 70.897, Z 0, A 0, B 90, C 22.191, E1 0, E2 0, E3 0, E4 0} C_DIS

This might cause issues with an older community version, let me know if you get an error message or if the robot disappears. The reason for that would be providing a Custom KRL before a movement command at the very beginning. This is fixed in the member release.

Best,

Johannes