hexagon logo

Portable flips the part 180° in alignment

This is getting ridiculous, sometimes when running alignments on planes, PC-DMIS flips the part 180°, despite the
fact that all my vectors are correct, theos and whatnots. We have to remeasure the part several times and hope
to hit the correct millisecond PC-DMIS uses to create the alignment correctly...

This is unacceptable and needs to be fixed - is it just me that suffers from this? We are burning daylight because
of the software at this point and not because the parts are incorrect - because we never get to the point where
we can see that...

 It doesn't even work with bestfit alignments as the primary plane used for alignment gets flipped.

If this is a "thing" in PC-DMIS that can't be fixed, please tell me that so I can find another software that works...

Is there anything in the settings editor or the general settings that can cause this behaviour?

EDIT: Pardon my tone, but we have higher-ups whipping our behinds.

PLAN_A     =ELEMENT/PLAN,REKTANGULÄRA,KONTUR,NEJ,GAUSS
            TEOR/<0,-312.819,-170.147>,<-1,0,0>
            MÄTT/<786.374,-681.37,-725.283>,<-0.0237684,0.999715,-0.0022286>
            KONSTR/PLAN,BA,PKT_A1,PKT_A2,PKT_A3,,
            TA_BORT_EXTREMVÄRDEN/AV,3
            FILTER/AV,VÅGLÄNGD=0
            REFDEF/A,ELEMENT=PLAN_A,,
A1         =UPPRIKTNING/START,ÅTERKALLA:START,LISTA=JA
              UPPRIKTNING/PRIMÄR,XMINUS,PLAN_A
              UPPRIKTNING/FLYTTA,X-AXEL,PLAN_A
            UPPRIKTNING/SLUT

This is the measurement and alignment that flips.

Parents
  • Changed the PLAN_A from BF to BFRE and that seem to have worked (for now) OR we hit that millisecond...
    If this is the way forward (using BFRE instead of BF) why is that?

  • You should always use BFRE if you are constructing a feature from actual measured points.  BF should only be used when the inputs to the construction do not have surface data (think intersection points / pierce points / generic points / cast points, circle centroids etc).  BFRE first fits a feature through the centroids of the raw hits, then applies the probe radius compensation whereas BF simply fits the feature through the already compensated hit locations.  Because BF is not considering the probe radius direction, it can sometimes flip the direction of the plane - as you are seeing.

  • This was unknown to me, so please file this under the user error category,   Grimacing

    It started working as soon as I changed it to BFRE and as you might recall, I have been hassling you about this "flip" a couple of times...
    I (most probably all of us) really appreciate your presence in these forums, you should be awarded the "lifesaver" trophy!

    This could mean that a huge headache has been removed from our portable endeavours! Heart eyes
    (doing a happy dance... and no, there are no images or videos from that dance routine so don't ask)

  • I've had issues with 3D best fit alignments if I'm not using enough features. For example, if I use 2 circles and do a 3D best fit, there is an occasion where it will flip the entire cad 180 degrees. What we have found that we need to use at least 3 features, as this essentially creates a 3 point plane of the features centroids. We almost never use BFRE as we usually just leave it on Auto because auto selects "BF", and that's what we use.

     Is Best Fit Recomp doing the same thing as Probe Compensation? Or are these two separate calculations? 

  • Similar but different.  Each hit has a radius correction value stored with it internally (based on whichever tip was used to take the hit).  BFRE then applies that radius correction value along the surface vector (based on the feature it has already constructed through the raw hit centroids).  "Normal" probe compensation applies the probe radius value along the probe hit direction which, depending on various factors, may or may not be approaching square to the surface.  If your probe isn't approaching square to the surface when you take your initial hits, you get cosine error.  Performing a BFRE construction on those same hits will correct the cosine error.

Reply
  • Similar but different.  Each hit has a radius correction value stored with it internally (based on whichever tip was used to take the hit).  BFRE then applies that radius correction value along the surface vector (based on the feature it has already constructed through the raw hit centroids).  "Normal" probe compensation applies the probe radius value along the probe hit direction which, depending on various factors, may or may not be approaching square to the surface.  If your probe isn't approaching square to the surface when you take your initial hits, you get cosine error.  Performing a BFRE construction on those same hits will correct the cosine error.

Children
No Data