hexagon logo

PC-DMIS 2020R2 – Profile ISO 1101

Hi & neil.challinor

I would like to ask you about your opinion about this issue.

We often have profile callouts similar to this |ꓵ|0.1 UZ -0.1| on our customer drawings,
where both tolerance “borders” are on one side of the nominal geometry.
I have seen these callouts since a few years from customers in the automotive industry as well as other industries.
I was looking forward to the new GeometricTolerance command to finally measure these callouts.


 ​​
Now it looks like the new command doesn’t support this kind of evaluation (at least I can’t get it to work).
PC-DMIS only allows me to put a value of maximum half the tolerance after the UZ modifier.
So I can’t have both “borders” on one side of the nominal geometry.



In my opinion these callouts are valid according to ISO 1101 as the standard doesn’t prohibit,
that both tolerance “borders” are on the same side of the nominal.
For me they would serve the same purpose as ISO Code fittings (egg. g6).

Furthermore as you also support the OZ modifier the calculation should already be supported by PC-DMIS.

What is your opinion on this?
Is this a valid callout but is not supported by PC-DMIS?
Do I understand the standard wrong?

Has anybody else these kind of callouts? What is your opinion about this?

Thank you for the answer.
Parents
  • This has been an issue for many people for a long time. I don't use 'profile', I dimension individual points, and you can do this using the "T" axis. Been some lively conversations about this 'elsewhere', but there is nothing in either standard forbidding having both limits on one side of nominal. I've been dealing with that for years.
Reply
  • This has been an issue for many people for a long time. I don't use 'profile', I dimension individual points, and you can do this using the "T" axis. Been some lively conversations about this 'elsewhere', but there is nothing in either standard forbidding having both limits on one side of nominal. I've been dealing with that for years.
Children
No Data