hexagon logo

Offset Plane Issues

I am revising an old program written sometime before 2012 and it's brought up some questions. First, why would one ever measure a plane and then construct an offset plane with an offset of zero? Second, if one did this, shouldn't dimensions referencing those planes give the same results? that is, the planes should be interchangeable? Instead this is what I'm seeing. I'm currently using version 2022.2 but this is translated from something earlier, probably last saved in 2017R1 in case that could possibly matter. The routine is saved as 2022.2 now though.

Parents
  • That, to me, is very clearly a resolution.
    First, why would one ever measure a plane and then construct an offset plane with an offset of zero?

    --We don't know for sure, but it's standard practice if one wants to OMIT form/flatness variation from the judged feature. It's also (apparently) a glitch in revisions that offset values shift to zero.

    Second, if one did this, shouldn't dimensions referencing those planes give the same results? that is, the planes should be interchangeable?

    FRAK and OUTPLN measured resultant values now match, as they should after executing the routine entirely. The delta between values was clearly a result of the last execution being a partial, omitting the updating of (last) MEASured ACTUAL values for one of the two planes.

    pleas elaborate on why you'd think it isn't resolved?
Reply
  • That, to me, is very clearly a resolution.
    First, why would one ever measure a plane and then construct an offset plane with an offset of zero?

    --We don't know for sure, but it's standard practice if one wants to OMIT form/flatness variation from the judged feature. It's also (apparently) a glitch in revisions that offset values shift to zero.

    Second, if one did this, shouldn't dimensions referencing those planes give the same results? that is, the planes should be interchangeable?

    FRAK and OUTPLN measured resultant values now match, as they should after executing the routine entirely. The delta between values was clearly a result of the last execution being a partial, omitting the updating of (last) MEASured ACTUAL values for one of the two planes.

    pleas elaborate on why you'd think it isn't resolved?
Children
No Data