hexagon logo

Move Increment to Move Point Conversion Script?

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


  • What I propose is a script that converts them after the program is finished. One that figures out the XYZ of where the incremental move starts, adds the XYZ translations of the incremental move itself, calculates the coordinates of the resultant position and hardcodes that position as a move point. I assume there is some existing infrastructure for these calculations, as this is exactly what PC-DMIS is doing when you click "Show Path Lines". Speaking of pathlines, I understand that I can go through and manipulate them to accomplish roughly what I'm after, but in a large program this would take a considerable amount of time.

    Does this exist? How difficult would it be to make it exist? Can you think of any Commands or functions that would help?


    I have not seen a script that can do that. I'm trying to think of ways to make one, but 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. That's beyond my skillset.

    I can think of two options that might make it easier to convert increment moves to point moves. One is to 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 seems less daunting, but still beyond my skillset.

    Option 2 is to select the move increment command and the feature right before it in the edit window and then right click on the selected features, select Path, then select Path Lines. This will show you the path lines for just that feature and the move increment command. Now, zoom in on the end point of the move increment path and click on the path line as close to the end as you can. That will open up the 'Move Path Line' dialog box. The values in the XYZ boxes will be the point along the path line that you clicked. You can increment these up and down if you want, but if you just click OK it will insert a move point that is awfully close to the same place as the move increment would place you. Then again, make sure to delete the move increment command.
Reply


  • What I propose is a script that converts them after the program is finished. One that figures out the XYZ of where the incremental move starts, adds the XYZ translations of the incremental move itself, calculates the coordinates of the resultant position and hardcodes that position as a move point. I assume there is some existing infrastructure for these calculations, as this is exactly what PC-DMIS is doing when you click "Show Path Lines". Speaking of pathlines, I understand that I can go through and manipulate them to accomplish roughly what I'm after, but in a large program this would take a considerable amount of time.

    Does this exist? How difficult would it be to make it exist? Can you think of any Commands or functions that would help?


    I have not seen a script that can do that. I'm trying to think of ways to make one, but 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. That's beyond my skillset.

    I can think of two options that might make it easier to convert increment moves to point moves. One is to 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 seems less daunting, but still beyond my skillset.

    Option 2 is to select the move increment command and the feature right before it in the edit window and then right click on the selected features, select Path, then select Path Lines. This will show you the path lines for just that feature and the move increment command. Now, zoom in on the end point of the move increment path and click on the path line as close to the end as you can. That will open up the 'Move Path Line' dialog box. The values in the XYZ boxes will be the point along the path line that you clicked. You can increment these up and down if you want, but if you just click OK it will insert a move point that is awfully close to the same place as the move increment would place you. Then again, make sure to delete the move increment command.
Children
No Data