Hello Charles,
I’m not sure why you would be getting that as our robot does allow for indexing in the way described by your first example. I just tested it on the simulator and it works as intended:
MoveJ
Waypoint_1
Waypoint_2
var1 = Waypoint_1[0] //result of var1 is indeed the x value of Waypoint_1
Are you doing this in Polyscope (our GUI)? Or trying to accomplish this through external communication?
Hello Charles,
I was able to reproduce the same results as you found in CB3 3.8.
Suggested solution to your problem:
To work around the issue, try Assigning the position to a temporary variable (var_pose below) and then taking the X coordinate from that instead.
I am seeing same behaviour in 3.8, but none of the previous versions of CB3 software or the e-Series 5.x releases will let me address a waypoint directly in this way, which makes me think it is unintentional. @dsh can you elaborate on what you did and in what version?
@ajp I used the online simulator version 5.1.1. It appeared to work for me. Due to the holidays I won’t be in the office until Wednesday but I can check on several of our robots then and verify actual use.