CAN I USE POINTCLOUD THIS WAY?

When you are constructing a circle out of the scans, what error are you getting that is not allowing you to construct them together? Are you using the "Select All Hits" button during construction, and in the correct workplane if doing 2D constructions? I only have experience constructing features from a COP from laser scanning, but I don't see why creating a COP and then using it to construct would not be okay. Since it's created out of the same hits. Does your COP hits count add up to the amount 3 circle scans would have?

this is the error I'm receiving

I honestly am not the biggest fan of it, but I do use it from time to time. I like the old ways from 2021.2 where if you selected features, it would throw the math error, and still put the construction in the Edit Window, and then I could just add the .hit etc bit of code to each feature. In 2023.2 if you get the math error, it does not create the Construction in the Edit Window. So if you want to do it the old fashioned way you have to begin typing CONST in the Edit Window to generate a constructed feature command.

I have also ran into issues where using the Select All Hits function in 2023.2 does not play well with 2021.1 when saved to an older version. It does not like the Syntax that is created. For example it creates the construction like this CIR1.HIT[..] instead of CIR1.HIT[1..CIR1.NUMHITS]. 2021.1 won't throw a fit when using [..] but it also does not calculate in my experience. So I have to edit Syntax.

SELECT ALL HITS SYNTAX

CIR4       =FEAT/CIRCLE,CARTESIAN,IN,LEAST_SQR,NO
            THEO/<-1.103,-0.61,0.791>,<0,1,0>,0.2154
            ACTL/<-1.103,-0.61,0.791>,<0,1,0>,0.2154
            CONSTR/CIRCLE,BF,2D,CIR1.HIT[..],CIR2.HIT[..],CIR3.HIT[..],,
            OUTLIER_REMOVAL/OFF,3
            FILTER/OFF,UPR=0

ORIGINAL SYNTAX

CIR4       =FEAT/CIRCLE,CARTESIAN,IN,LEAST_SQR,NO
            THEO/<-1.103,-0.61,0.791>,<0,1,0>,0.2154
            ACTL/<-1.103,-0.61,0.791>,<0,1,0>,0.2154
            CONSTR/CIRCLE,BF,2D,CIR1.HIT[1..CIR1.NUMHITS],CIR2.HIT[1..CIR2.NUMHITS],CIR3.HIT[1..CIR3.NUMHITS],,
            OUTLIER_REMOVAL/OFF,3
            FILTER/OFF,UPR=0

I will give this a try at some point today. Not really sure where to select the option all hits. Boss just gave me a different problem to solve with the EDM now, so I'll have to get back to you if this worked. I'm using PCDMIS 2024.2 CAD++

Button shown below in the same Construction Window you used when you got the Math Error.
 

Make sure you hurry up with this most important emergency so that you can get back to working on the former most important emergency! 

We must work for the same person!!!!!! aka Mr. Hurry Up And Wait. 

The option to select all hits is grayed out 

I spoke too soon. i put it on best fit instead of auto and it worked. Thanks so much.

Glad it worked for you! Is that all you needed? I actually always select Best Fit, and did not realize Auto would not work. Probably because it needs to know what type of circle construction you are performing first.

BF not BFRE? 

It can do both. I apologize for my ignorance on this, but I don't know the difference. Which one should I use? I just got done with the first round of training and we spent a week learning stuff I'll never use and never talked about scanning at all and that's the whole reason we got this machine. I'm learning more from these forums.

It can do both. I apologize for my ignorance on this, but I don't know the difference. Which one should I use? I just got done with the first round of training and we spent a week learning stuff I'll never use and never talked about scanning at all and that's the whole reason we got this machine. I'm learning more from these forums.

Thats a Neil question, pretty much always BFRE from what I learned on the forums! 

Also welcome to the Demon Tamers Guild. (I kinda like that, might get it on a coffee cup...) 

Neil DeGrasse Tyson? I have his number but he said quit calling him.

BFRE is 100% the most common thing Neil tells us that we should do. In my brain, if they didn't want me using BF it wouldn't be in the dropdown! Or they would make both BF and BFRE calculate the same as BFRE to trick us.

I'm gonna need one of those too

Or God-forbid make it the default choice so you do it without thinking. 

BFRE when you have "surface information", BF all other times.

"surface information" = a measured feature

...if I understood Neil correctly.

Seems kinda silly not to have it as default since the sole purpose of the machine is to gather measured features.

So the way I am taking that is, if I have intersect/pierce points that I am using to Construct a circle feature, I would use BF instead of BFRE because they aren't explicitly measured features, but generated from measured features. Does that sound right?

With our powers combined maybe we can summon the great and mighty Neil! 

But yes, that does make sense, but then would it be "wrong" to use a BFRE for those, would it matter, is there any difference in the measurement? Also, what if you are making something else with the pierce point? 

I believe that BF uses the vector of the points as measured, and BFRE recalculates the points and fit based on the point centroid location with no vectors considered. This is for situations like measuring a feature where you're not probing normal to the surface.