Good morning. I hope all is well with everyone. Just wondering, does pc dmis have an option to search for the fatest measurement routine? Thaks for your insight.
...... buyer beware. There is an optimize path function, but I have yet to hear that it is a 'good' thing. And, depending on they type of work you do, it is 100% useless.
I check sheet metal, on dedicated fixtures, that have many many 'things' in the way that are not part of the part, and rarely do I get any kind of cad for those 'things', and even if I did, things like clamps, clamp arms, clamp feet are apt to be 'not 100% correct', so no way for Pcdmis to 'optimize' around them.
brain power is your best bet to 'optimize' the program.
Even brain power can be a 'problem' when trying to optimize. Probe changes are time killers, but if you have to change the build using a rack, nothing you can do about the time required, so, do everything possible with 'probe a', then change to 'probe b', and so on. Just rotations are a time killer, but even so, sometimes it is quicker to do stuff at angle XX, then do stuff (that is 'right there') at YY, then switch back to XX to continue, it all depends on what is happening. Yeah, it can be a quandary! Smaller prehit/retract IF YOU CAN DO IT will reduce cycle time a lot since touch speed is so much slower than move speed (My Global is 500 move vs 6 touch!) but watch out that you don't make it so small that it causes issues moving between features.
MOVE/POINT is generally a better option than MOVE/CLEARPLANE (I avoid MOVE/INCREMENT as a false trigger really mucks those up). I use both, CP to start the program, then MP in the body.
Even brain power can be a 'problem' when trying to optimize. Probe changes are time killers, but if you have to change the build using a rack, nothing you can do about the time required, so, do everything possible with 'probe a', then change to 'probe b', and so on. Just rotations are a time killer, but even so, sometimes it is quicker to do stuff at angle XX, then do stuff (that is 'right there') at YY, then switch back to XX to continue, it all depends on what is happening. Yeah, it can be a quandary! Smaller prehit/retract IF YOU CAN DO IT will reduce cycle time a lot since touch speed is so much slower than move speed (My Global is 500 move vs 6 touch!) but watch out that you don't make it so small that it causes issues moving between features.
MOVE/POINT is generally a better option than MOVE/CLEARPLANE (I avoid MOVE/INCREMENT as a false trigger really mucks those up). I use both, CP to start the program, then MP in the body.
