New odd little bug. I'm not 100% sure it is 2017 specific, but it happened on 2017.
I accidentally fat fingered an extra 0 in an auto feature. No big deal. The weird part is what happened on execution.
There is a vector point followed by an edge point. The edge point was at 10000 in Z, which is 9000mm away from reality. The program ran the vector point, and stopped as it triggered on the surface of the part with an out of machine parameter error. So,
no retract or avoidance move of the vector point before erroring out.
It should have at least finished the retract and/or avoidance move of the vector point before throwing an error for the next feature.
New odd little bug. I'm not 100% sure it is 2017 specific, but it happened on 2017.
I accidentally fat fingered an extra 0 in an auto feature. No big deal. The weird part is what happened on execution.
There is a vector point followed by an edge point. The edge point was at 10000 in Z, which is 9000mm away from reality. The program ran the vector point, and stopped as it triggered on the surface of the part with an out of machine parameter error. So,
no retract or avoidance move of the vector point before erroring out.
It should have at least finished the retract and/or avoidance move of the vector point before throwing an error for the next feature.
