Discussion

Left ArrowBack to discussions page
abeachy_HG24abeachy_HG24 Posts: 79 Handy
edited August 2016 in Robotiq Products
I use the 0-255 position of the gripper quite frequently in my programs to determine if that part is the correct size, and I was wondering if there was anyway to have the 0-255 appear in the UR cap instead of the 0-100%? With the UR cap being in percent, it is more time consuming to determine the 0-255 position.
Tagged:

Comments

  • PierreOlivier_ProulxPierreOlivier_Proulx Posts: 67Beta Tester VIsion 1.1 Program, Vacuum Beta tester Handy
    edited August 2016
    @abeachy_HG24 I assume that with the old package, you would take the position value in the gripper toolbar and write it directly in your program as the object's width expectation. This is not possible with the URCap. However, what I suggest is that in your program you put that line of code after the Gripper Close instruction:
    textmsg(rq_current_pos())
    This will output in Polyscope's log the value of the gripper position. After you can easily look at the log and decide by which values the object's width is bounded.
    Pierre-Olivier Proulx
    Software Designer
    [email protected]
  • abeachy_HG24abeachy_HG24 Posts: 79 Handy
    That is correct, with the old package I would look at the toolbar and write into my program. What I do now is I assign "rq_current_pos()" to a variable and place it after the gripper close and I set the program up so the robot grips and picks up and then releases the part, and I watch the variable on the variable tab. So I found a work around, and it's not a problem. It is just more time consuming than before.
  • Etienne_SamsonEtienne_Samson Posts: 418Beta Tester Beetle, Wrist Camera URCap 1.3.0, Vacuum Beta tester Handy
    edited August 2016
    @abeachy_HG24 you could also keep using the classic instructions, check out the bottom of section 4.8.2 of the manual. You have access to a set of commands with the classic 0 to 255 and a set of "normalized" commands with 0-100% ( rq_current_pos_norm() ) . I'll see if we could also provide a conversion formula as it is not exactly a cross-multiplication.
    Etienne Samson
    Technical Support Director
    +1 418-380-2788 ext. 207
    [email protected]
  • Samuel_BouchardSamuel_Bouchard Posts: 149 Handy
    @Ryan_Weaver were you aware of that rq_current_pos_norm() variable? Makes it easier to relate what you see in the gripper toolbar and use it in your program conditions.

  • PierreOlivier_ProulxPierreOlivier_Proulx Posts: 67Beta Tester VIsion 1.1 Program, Vacuum Beta tester Handy
    Look at the file gripper_tutorial.urp in the /program folder. It contains all the useful urscript functions to control the gripper. Note that this file is overwritten each time Polyscope starts so don't ever save your work under that file name.
    Pierre-Olivier Proulx
    Software Designer
    [email protected]
  • abeachy_HG24abeachy_HG24 Posts: 79 Handy
    @Etienne_Samson that is how I am doing it currently. I'm using those classic commands to obtain the position of the gripper and to perform some gripper moves while the robot is travelling. Maybe it's not possible or useful to anyone but me, but if there was a way to toggle between the percent and the 0-255 in the toolbar that would be really helpful.
  • PierreOlivier_ProulxPierreOlivier_Proulx Posts: 67Beta Tester VIsion 1.1 Program, Vacuum Beta tester Handy
    @abeachy_HG24 I will log that as a desirable feature.
    Pierre-Olivier Proulx
    Software Designer
    [email protected]
Sign In or Register to comment.
Left ArrowBack to discussions page