hexagon logo
Register Sign in
  • Replies 40 replies
  • Subscribers 32 subscribers
  • Views 1180 views
  • Users 0 members are here
Options
Related

Move Increment to Move Point Conversion Script?

Incredible.Mr.Lucas
Confused Is anybody familiar with a script that will scour your program and replace all the Move Increments with Move Points in the alignment context in which the moves reside? My team really doesn't like Move increments, but I really like the convenience while programing. It would be neat if there were a macro that converts them all with a click of a button.Confused
Parents


  • The challenge is calculating the XYZ position after executing a feature and then executing a move increment. Doing that would need to account for your probe radius, retract values, and/or any avoidance moves built into auto features.

    Yes, with that line you have captured the challenge better than I have myself previously. Thank you. Working all that out with a script would be daunting.



    Select the move increment command and the feature right before it in the edit window, while in offline mode. Then, press Ctrl+L to execute just those two features. This will move the probe to the location of the equivalent move point position. Then, move the cursor to the line with the move increment command and press Ctrl+M. That will put a move point there. Then make sure you delete the move increment command. Now that I have typed that all out, I wonder if a script could be made to automatically do those steps for each instance of a move/increment command in a measuring routine.

    That idea you had in option one sounds like a winner! You are right, It absolutely must be executed offline. But if the script could choose the correct features and somehow replicated those Keystrokes, I believe the problem could be solved.

    Move down the edit window searching for an incremental move. Select that move and the immediate feature or move that precedes it. After both are selected, Emulate pressing CTRL+E so the computer moves the digital stylus to where the two features conclude in 3D space. Wait 60 seconds for that operation to complete, then emulate pressing CTRL+M to capture that point in 3D space as a Move Point immediately after the Incremental move in the edit window. Then delete the incremental move, move the cursor to the line after the Move point, and start over at step 1, looping the whole sequence over and over until the cursor reaches the end of the program.

    Now that it is spelled out, does anybody see a problem with this roadmapConfused? If not, What expressions are required to emulate the key pressesConfused?
Reply


  • The challenge is calculating the XYZ position after executing a feature and then executing a move increment. Doing that would need to account for your probe radius, retract values, and/or any avoidance moves built into auto features.

    Yes, with that line you have captured the challenge better than I have myself previously. Thank you. Working all that out with a script would be daunting.



    Select the move increment command and the feature right before it in the edit window, while in offline mode. Then, press Ctrl+L to execute just those two features. This will move the probe to the location of the equivalent move point position. Then, move the cursor to the line with the move increment command and press Ctrl+M. That will put a move point there. Then make sure you delete the move increment command. Now that I have typed that all out, I wonder if a script could be made to automatically do those steps for each instance of a move/increment command in a measuring routine.

    That idea you had in option one sounds like a winner! You are right, It absolutely must be executed offline. But if the script could choose the correct features and somehow replicated those Keystrokes, I believe the problem could be solved.

    Move down the edit window searching for an incremental move. Select that move and the immediate feature or move that precedes it. After both are selected, Emulate pressing CTRL+E so the computer moves the digital stylus to where the two features conclude in 3D space. Wait 60 seconds for that operation to complete, then emulate pressing CTRL+M to capture that point in 3D space as a Move Point immediately after the Incremental move in the edit window. Then delete the incremental move, move the cursor to the line after the Move point, and start over at step 1, looping the whole sequence over and over until the cursor reaches the end of the program.

    Now that it is spelled out, does anybody see a problem with this roadmapConfused? If not, What expressions are required to emulate the key pressesConfused?
Children
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement