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
  • Measure the same cone both as auto cone and as measured cone (or a constructed one),
    construct a point (Cast point) from the two cones and compare the Z values,
    you will notice a difference - the auto cone has the start end (the surface you clicked) as cast point, the measured (and a constructed) cone has the vertex.
    Now construct circle on a certain height from CONE_START on each of them, and you will get different circles.

    CONE_VERTEX (if that's the name in English) gives the same result irrespective of how the cone is measured (which is natural, as it is the same cone, with the vertex at the same position).


    Ok, this is all fine and dandy. I understand the cone start and end of the auto cone and the vertex of the constructed cone. Maybe I am not putting the right information into the fields when using the construct a circle via a cone command( I really can't get smart to what is going on with that option ) But I am still confused as to why I would get different results when intersecting the cones with an existing plane, in this case my level plane.

    I just again tried intersecting an auto cone with my level plane ( same program as my original post ) and depending on which end of the cone I clicked on, I got different results. One end I got 7.195" and if I clicked on the other end of the cone and intersected with the same plane as above I got the 7.394" again( same result as my original post ). I can live with the 7.195 vs 7.194( from my original post )


    Why the two different results? Shouldn't make any difference which end of the cone I click on. To make things even worse, during offline programming, no matter what method I use, the intersect method, or the cone height method, no matter which end I click on, I get the result that I am looking for. Every thing looks good until the operator runs the program on the part and the results are out in left field, like my original post.


    I think some thing is majorly screwed up with the auto cone feature when trying to construct circles from them. Every thing else looks good on them when you look at the angle, the cast point, the length etc, etc.....just do not try to construct a circle from them.










Reply
  • Measure the same cone both as auto cone and as measured cone (or a constructed one),
    construct a point (Cast point) from the two cones and compare the Z values,
    you will notice a difference - the auto cone has the start end (the surface you clicked) as cast point, the measured (and a constructed) cone has the vertex.
    Now construct circle on a certain height from CONE_START on each of them, and you will get different circles.

    CONE_VERTEX (if that's the name in English) gives the same result irrespective of how the cone is measured (which is natural, as it is the same cone, with the vertex at the same position).


    Ok, this is all fine and dandy. I understand the cone start and end of the auto cone and the vertex of the constructed cone. Maybe I am not putting the right information into the fields when using the construct a circle via a cone command( I really can't get smart to what is going on with that option ) But I am still confused as to why I would get different results when intersecting the cones with an existing plane, in this case my level plane.

    I just again tried intersecting an auto cone with my level plane ( same program as my original post ) and depending on which end of the cone I clicked on, I got different results. One end I got 7.195" and if I clicked on the other end of the cone and intersected with the same plane as above I got the 7.394" again( same result as my original post ). I can live with the 7.195 vs 7.194( from my original post )


    Why the two different results? Shouldn't make any difference which end of the cone I click on. To make things even worse, during offline programming, no matter what method I use, the intersect method, or the cone height method, no matter which end I click on, I get the result that I am looking for. Every thing looks good until the operator runs the program on the part and the results are out in left field, like my original post.


    I think some thing is majorly screwed up with the auto cone feature when trying to construct circles from them. Every thing else looks good on them when you look at the angle, the cast point, the length etc, etc.....just do not try to construct a circle from them.










Children