hexagon logo

Surface Profile - Iterate and Repierce function

Can someone give me a rundown of what the iterate and repierce function does? I turn it on and all of a sudden my surface profile improves significantly. Is that real?

On a similar topic, has anyone else had trouble with vector least square best fit causing a best fit error? I have had several parts now that had profile dimensions set to vector best fit, which runs fine offline, that have given me best fit errors at the end of the program. If I hunt down the offending dimension and change it to least squares the error goes away immediately. I have also had a similar problem if I set the iterate and repierce function with too small of a tolerance. I'm using an .039 (1mm) ruby and have found I need to set the repierce tolerance to at least .025 to reliably run through the program without any best fit errors. This seems to be related to features with very large radiuses of contour (almost flat, but not quite). My assumption is that the math runs out to too many decimal places and it can't handle it.

Thanks for any advice. I am inspecting a part that is just one giant contour, no flats at all, and need to have all of my ducks in a row around how all of the surface profile options work.
Parents
  • Sorry if my question was poorly worded, or if this is something any programmer should already know the answer to. I've been begging for the level 2 classes from Hexagon, but of course "anyone should be an expert after one whole week of classroom training" Rolling eyes (Or so those who haven't attempted any kind of CMM programming seem to think). I just want to know if I use this for a best fit hole pattern will it
    slowly and quietly chews away at the integrity of your programs' nominals and eventually something breaks and your program falls apart in a sudden and catastrophic failure
    ? Any information, even if it's just a tip on where to get more information, would be greatly appreciated.

Reply
  • Sorry if my question was poorly worded, or if this is something any programmer should already know the answer to. I've been begging for the level 2 classes from Hexagon, but of course "anyone should be an expert after one whole week of classroom training" Rolling eyes (Or so those who haven't attempted any kind of CMM programming seem to think). I just want to know if I use this for a best fit hole pattern will it
    slowly and quietly chews away at the integrity of your programs' nominals and eventually something breaks and your program falls apart in a sudden and catastrophic failure
    ? Any information, even if it's just a tip on where to get more information, would be greatly appreciated.

Children
No Data