hexagon logo
Register Sign in
  • Replies 22 replies
  • Subscribers 17 subscribers
  • Views 461 views
  • Users 0 members are here
Options
Related

Autofeature line screwing me up_Anyone else see this?

DAN_M
Using PC DMIS 2022.1. (Issue started for me with this version of PC DMIS. Was not a problem with previous versions)

I have a lot of turned parts where an arc intersects with a flat plane & I have to report the diameter of where it breaks out. To do this, I intersect an "autofeature line" with an "autofeature circle" to get an intersection point. Do it in 6 places. Construct the 6 points together to get a circle. (Yes I have an alignment that recalls startup with all 6DOF properly constrained and yes I am using correct workplanes while measuring & constructing). I have done this for years and it has always worked. Slight smile

When I do this in 2022, PC DMIS complains about a math error and it won't do the construction. Disappointed

To get around this, I have to delete the autofeature lines & replace the lines with autofeature points and then construct a line through the pnts and then use THAT to create the intersections in each place. Alien

Is pretty annoying..is causing me to change programs that have been "Validated" for years. Is anyone else having issues using "autofeature line" ??Frog

Parents


  • When the lines were auto features, the vectors were correct..definitely made sure of that Disappointed Thanks for the suggestion...your suggestion is to create a line...I had to create a line (just a different kind..you suggest HIT values and I used pnts) in order for it to work instead of being able to use the autofeature directly

    I didn't know if a constructed .HIT line would react the same way as the auto feature line. In that case, you use the same auto feature data points rather than individual vector points.

    My thought process is that if the .HIT points reacted the same way as the auto feature, then we could say that there might be a bug in the auto feature creation. However, if the .HIT works then something else is messed up.

    #thedemonstrikes
Reply


  • When the lines were auto features, the vectors were correct..definitely made sure of that Disappointed Thanks for the suggestion...your suggestion is to create a line...I had to create a line (just a different kind..you suggest HIT values and I used pnts) in order for it to work instead of being able to use the autofeature directly

    I didn't know if a constructed .HIT line would react the same way as the auto feature line. In that case, you use the same auto feature data points rather than individual vector points.

    My thought process is that if the .HIT points reacted the same way as the auto feature, then we could say that there might be a bug in the auto feature creation. However, if the .HIT works then something else is messed up.

    #thedemonstrikes
Children
No Data
© 2024 Hexagon AB and/or its subsidiaries. Privacy Policy | Cloud Services Agreement