Add points from looped features to pointcloud

Collapse
X
 
  • Filter
  • Time
  • Show
Clear All
new posts

  • Add points from looped features to pointcloud

    Hi there,
    I’m using latest service pack for 2016. I have not been able to find a way to add the hits from looped circles or cylinders to a single pointcloud. If I try to create a pointcloud outside the loop it will not accept the index numbers as part of the feature name reference so impossible to point it to anything other than the last executed instance of the feature. The intent is to concatenation all of the hits from 100+ holes into a single pointcloud and then export them to a txt file. I can put the pointcloud construction and export inside the loop but then I get 100+ pointclouds each with only 1 hole in them. Less than ideal...

    I saw an idea from AndersI on another post to write the hits to a txt file during the loop just using the file I/O functions. That allows you to append as you go. I will probably go that route.

    just curious if anyone else has encountered this issue with not being able to reference feature instances in a pointcloud? Seems like a major roadblock to many applications. Wondering if anyone has found any other work around or if this has been fixed in a later version?
    2013MR1 SP6
    Global Frames, Tesastar-M Heads, LSP-X1M/H Probes

  • #2
    Would throwing them into a set work? I am not sure if you could put a set into the point cloud though...
    PC-DMIS CAD++ 2o19 R1 SP4

    Comment


    • #3
      It doesn't work in my application. Maybe because I am using DO looping instead of PC-DMIS loop. The result is 100 sets of points that are all identical. It doesn't retain their positions in space relative to the other features.
      2013MR1 SP6
      Global Frames, Tesastar-M Heads, LSP-X1M/H Probes

      Comment


      • AndersI
        AndersI commented
        Editing a comment
        There is a setting for that (that they all get the same value), in Settings Editor, but I don't remember what it is called [...searching…] - it might be the TreatTheoValuesAsIfStoredInPartCoordinates (but I'm not completely sure what that does…). It wont help with creating the set, though...

    • #4
      The AndersI suggestion would probably work (they usually do) and create less headache for you ;P
      PC-DMIS CAD++ 2o19 R1 SP4

      Comment


      • #5
        I thought about playing with that setting but it just seems like I'm asking for trouble. Everything else about the program works and is proven. I just implemented using file I/O commands to write the point data out to a txt file. Simple and stable.

        It seems like a huge oversite that pointcloud feature can't accept instance numbers in feature references. Everything else can, why not this?
        2013MR1 SP6
        Global Frames, Tesastar-M Heads, LSP-X1M/H Probes

        Comment


        • #6
          Ok, I tried it ofline with a loop, and not with a Do/Until, but I think it could work...

          Code:
          ASSIGN/V2=0
          V1         =LOOP/START,ID=YES,NUMBER=10,START=1,SKIP=,
                        OFFSET:XAXIS=5,YAXIS=0,ZAXIS=0,ANGLE=0
          F1           =GENERIC/POINT,DEPENDENT,CARTESIAN,$
                        NOM/XYZ,<0,0,0>,$
                        MEAS/XYZ,<0,0,0>,$
                        NOM/IJK,<0,0,1>,$
                        MEAS/IJK,<0,0,1>
                        ASSIGN/V2=V2+1
                      LOOP/END
          SCN1       =FEAT/SET,CARTESIAN
                      THEO/<0,0,0>,<0,0,1>
                      ACTL/<22.5,0,0>,<0,0,1>
                      CONSTR/SET,BASIC,F1[1..V2],,
          COP1       =COP/DATA,TOTAL SIZE=10,REDUCED SIZE=10,
                      REF,SCN1,,

          Comment


          • #7
            Thanks Jeffman. Due to other details of the program structure it isn’t possible to use a PCDMIS loop. I need to use a Do or While loop. They cause the points to be stored differently. I’ve tried many possibilities and am convinced that Anders idea to just write the point data out to a file using file I/O commands is the best, most stable solution.

            i was hoping that someone would say that the problem with the pointcloud feature not accepting instance references had been fixed in a later version but I guess that it isn’t the case...
            2013MR1 SP6
            Global Frames, Tesastar-M Heads, LSP-X1M/H Probes

            Comment


            • #8
              Originally posted by DaSalo View Post
              i was hoping that someone would say that the problem with the pointcloud feature not accepting instance references had been fixed in a later version but I guess that it isn’t the case...
              Moving only some hits from a feature to a pointcloud can always be accomplished by going through a set,





              Code:
               
              SCN1 =FEAT/SET,CARTESIAN THEO/<28.408,7.96,-3>,<0,0,1> ACTL/<28.408,7.96,-3>,<0,0,1> CONSTR/SET,BASIC,CIR_ORIGO.HIT[1..3],, COP1 =COP/DATA,TOTAL SIZE=3,REDUCED SIZE=3, FINDNOMS=NO,REF=SCN1,,
              so maybe you could be more specific as to what you want to do? What are you indexing, where?
              Last edited by AndersI; 09-13-2019, 04:42 AM.
              AndersI
              SW support - Hexagon Metrology Nordic AB

              Comment

              Related Topics

              Collapse

              Working...
              X