hexagon logo
Register Sign in
  • Replies 40 replies
  • Subscribers 32 subscribers
  • Views 1033 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

  • ->
    When I think about it then the script is very useless at the moment because it doesn't even consider two increment movements that follow one another
    sorry

    Don't Apologize, you've created a substantive and tremendous start point. Correct me if I'm wrong, but you are the first person to post code on this thread.


    I still don't understand why it must be so complicated? Couldn't one simply execute each command one after another, testing afterwards if the previous command was an incremental move, and if so, reading the probe position and inputting the coordinates into a move point? This would have the same problems with flow control but would solve the problems with the clearance cube, clearance planes, avoidance moves, duplicate moves, alignments, ect. Someone, please explain to me the error in my train of thought.


    Please answer this.
Reply

  • ->
    When I think about it then the script is very useless at the moment because it doesn't even consider two increment movements that follow one another
    sorry

    Don't Apologize, you've created a substantive and tremendous start point. Correct me if I'm wrong, but you are the first person to post code on this thread.


    I still don't understand why it must be so complicated? Couldn't one simply execute each command one after another, testing afterwards if the previous command was an incremental move, and if so, reading the probe position and inputting the coordinates into a move point? This would have the same problems with flow control but would solve the problems with the clearance cube, clearance planes, avoidance moves, duplicate moves, alignments, ect. Someone, please explain to me the error in my train of thought.


    Please answer this.
Children
  • in reply to Incredible.Mr.Lucas
    there is a huge problem with "Clearance Cube", because i cant think of solution to extract that infos.
    if you use this, i think it will never work with this.

    but i patch moving point, flow control command, or avoidence move also inch . the next week
  • in reply to Incredible.Mr.Lucas
    I don't think the problem with the clearance cubes is as huge as you think. I have never used them in PC-DMIS, and i have never met another programmer in real life that used them in PC-DMIS... Including the hexagon instructors, They know how to do it, they'll teach it, they just don't use it programming unless a customer specifically demands it. If you hadn't mentioned the problem with clearance cubes, it probably would have been a year or two before somebody stumbled across the bug.

    Third time,
    I still don't understand why it must be so complicated? Couldn't one simply execute each command one after another, testing afterwards if the previous command was an incremental move, and if so, reading the probe position and inputting the coordinates into a move point? This would have the same problems with flow control but would solve the problems with the clearance cube, clearance planes, avoidance moves, duplicate moves, alignments, ect. Someone, please explain to me the error in my train of thought.
  • in reply to Incredible.Mr.Lucas
    hm, i think about it
    * you need a real part for this
    * a working partprogramm
    * i dont know, if you can execute a partprogram partialy, but you need that for this task
    * inside and delete commands while excute a partprogramm .. dont realy work i think, it has to be tested

    -> inside a Move command from the actual tip position is easy trougth
    -> there is a event for exceuted commands that sound good
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement