hexagon logo

Auto Cone extracted from a COP

We have Romer arm here with an RS3 laser on it.

I am having issues with the auto cone feature. I want to do an auto cone and then generate a circle from the auto cone, either by intersecting with an existing plane or by using the cone feature under construct a circle and create a circle at a given height.

If I take individual auto points and construct a cone, I get the results that I expect. I have been doing it this way for a couple of years now. Recently I tried to incorporate the auto cone feature into my programs and I can not get smart as to what is going on with this command.

Ex. Part I am currently working on, if I construct a cone from individual points and intersect that cone with a plane or construct a cone at a given height I get the result that I am looking for....in this case a circle with a diameter of 7.194"( verified with a caliper ). Now if I extract the same cone via the auto cone command and intersect this new cone with the same plane as above, I get a result of 7.394" and if I construct a cone at a given height( same height as the above mentioned plane ) I get a result of 6.560"

Has anyone else experienced weird result like this?

I have contacted tech support twice on this subject and have yet to get any kind of straight answer on this?
Parents
  • Sounds to me like the noise you're getting from the cone's scan isn't being filtered out properly. That noisy cone yields a noisy circle.

    If you're taking auto surface points and constructing a cone out of it, that filtering is being set inside of the feature, but since it's on a CONICAL surface, the auto surface point isn't the correct one to use. Auto surface points are going to create an average centroid from all the points subsampled. The more curved the surface, the smaller an area you have to sample to be repeatable, and therefore you'll be the most susceptible to noise. Best to stick with Auto Cone in this application.

    - are you correctly using your center offset (green) / search length (purple) / clipping parameters and confirming your pointcloud subsample via the segregated points option? This is fundamental to using any laser-extracted features in PCDMIS, please see the attached picture





    -Is your auto cone coming from a scanned pointcloud or scanned mesh? Clearly a scanned mesh will have less noise than a pointcloud

    -How are you filtering your cloud before you construct a cone from it? Are you using Random? Curvature? Uniform? What standard deviation of points are you keeping inside of the Auto Cone?

    -Is it sprayed? or are you scanning on a shiny surface? Obviously we prefer a sprayed surface. If the surface is shiny, maybe a zigzag/flyingdot scanner would prove more effective than a line scanner

    IMO, your Auto Cone isn't correlating to your Constructed Cone due to a difference in subsampling or filtering.
Reply
  • Sounds to me like the noise you're getting from the cone's scan isn't being filtered out properly. That noisy cone yields a noisy circle.

    If you're taking auto surface points and constructing a cone out of it, that filtering is being set inside of the feature, but since it's on a CONICAL surface, the auto surface point isn't the correct one to use. Auto surface points are going to create an average centroid from all the points subsampled. The more curved the surface, the smaller an area you have to sample to be repeatable, and therefore you'll be the most susceptible to noise. Best to stick with Auto Cone in this application.

    - are you correctly using your center offset (green) / search length (purple) / clipping parameters and confirming your pointcloud subsample via the segregated points option? This is fundamental to using any laser-extracted features in PCDMIS, please see the attached picture





    -Is your auto cone coming from a scanned pointcloud or scanned mesh? Clearly a scanned mesh will have less noise than a pointcloud

    -How are you filtering your cloud before you construct a cone from it? Are you using Random? Curvature? Uniform? What standard deviation of points are you keeping inside of the Auto Cone?

    -Is it sprayed? or are you scanning on a shiny surface? Obviously we prefer a sprayed surface. If the surface is shiny, maybe a zigzag/flyingdot scanner would prove more effective than a line scanner

    IMO, your Auto Cone isn't correlating to your Constructed Cone due to a difference in subsampling or filtering.
Children
No Data