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?
Our models here always have the correct draft angles on them. We make our own models here. The patterns are made from our models. It's not always a draft angle I am measuring....I have also had cone features that were part of the casting design ( nice cones ) that when done with auto cone, come up way off.
Since you mentioned that draft angles do not make nice cones ( vertex far away ) , I assume you are talking about the constructed cone. Again, the results that I get from the constructed cone isn't what I have an issue with. If you look back at my original post, I verified my results with a caliper. The result from the constructed cone and the caliper matched. It is the auto cone that gave the wrong results. It would just be nice If I could trust the results from auto cone. Only reason I would like to make more use of the auto cone feature is that it reduces lines of code. On average I take 20 surface points to construct my cones. 20 lines of code versus 1 line of code for each cone feature.
I have had auto cones give results over an inch off on a 9 inch dia. circle, way beyond measurement error.
Tech support finally did remote in last week( after I posted this thread ) and saw what I am talking about. That person did not have an answer. They said they were gonna get other people involved. That is the last I heard from them. If I am doing some thing wrong, I would like to know what that is. I don't think I am though, I think it is in the software.
Our models here always have the correct draft angles on them. We make our own models here. The patterns are made from our models. It's not always a draft angle I am measuring....I have also had cone features that were part of the casting design ( nice cones ) that when done with auto cone, come up way off.
Since you mentioned that draft angles do not make nice cones ( vertex far away ) , I assume you are talking about the constructed cone. Again, the results that I get from the constructed cone isn't what I have an issue with. If you look back at my original post, I verified my results with a caliper. The result from the constructed cone and the caliper matched. It is the auto cone that gave the wrong results. It would just be nice If I could trust the results from auto cone. Only reason I would like to make more use of the auto cone feature is that it reduces lines of code. On average I take 20 surface points to construct my cones. 20 lines of code versus 1 line of code for each cone feature.
I have had auto cones give results over an inch off on a 9 inch dia. circle, way beyond measurement error.
Tech support finally did remote in last week( after I posted this thread ) and saw what I am talking about. That person did not have an answer. They said they were gonna get other people involved. That is the last I heard from them. If I am doing some thing wrong, I would like to know what that is. I don't think I am though, I think it is in the software.