I was programming a small radius today from and it kept flipping on me when I ran the program. I initially programmed it to 270 to 300 degrees. When I went to ran the program it was way off. The probe would crash into the part in an attempt to go through the part. I F9ed the feature again and it appears that the angle vector had been flipped. So I changed it to 0 to 30 degrees and ran it again. Same thing happened. It is a macro (part family) program. The diameter of the feature is a variable (not sure if that is causing the problem). I ended up having to remake the feature (90 to 120 now!!!) and it seems to be running fine. I didn't check to see if the angle vector was actually flipping in the code, but I think that's what was happening. What do you do when you encounter this kind of issue? Would adding +0 to the angle vector work?
I get this all the time. I've not figured out exactly why, but I get it a lot when I paste with pattern. I check after the PwP, everything is fine, then when the operators go to run the program it switches it.
I suspect it has something to do with either the backsaves I do (I program in 2017, they run in 2015), or that STUPID MUTHA F*$%@*! CW/CCW thing. I despise CW/CCW in CMM nomenclature, especially when there's another perfectly logical and mathematically correct way to express rotational direction that doesn't depend on direction of view.....
Angle vector and surface vector MUST be different !!!!!!!
Angle vector define the side where the measure begins, it cannot be along the surface vector.
(Here, you should use 0,0,1, with start at 0 and end -30, CCW (I'm not at the cmm to check...)