hexagon logo

CAN I USE POINTCLOUD THIS WAY?

So, I have a part that I have to combine three adaptive circle scans. It won't let me construct a circle from those scans, so I used POINTCLOUD. I just made the scans then inserted a pointclound feature using the three scans. It lets me construct a circle out of the COP. I should add that I'm scanning with my probe and not a laser. I only saw topics talking about lasers with poinclouds so I want to make sure me doing it this way is ok. I don't really like to use linear open scans for this because there is too much I have to change to get the scan to stay a particular Z. 

PCDMIS 2024.2 CAD++

Thanks for any help

Parents
  • 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?

  • Okay, yeah. This could possibly be Workplane related, or you aren't hitting the "Select All Hits" button in the Construction Window. Possibly causing errors because the centroids of the circles are the same so it cannot create a circle due to them overlapping. Selecting all hits should resolve it, as it will change from using centroids to all hits of each feature. What version is your PC-DMIS? Select all hits is available in 2023.2 and later

  • So fancy! Someday I will have that button someday, far far far far in the future when my boss decides to upgrade.....

  • 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

Reply
  • 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

Children
No Data