GD&T engine MMC

[[Pa...]]

I've just started working with Calypso 2024.  Using the GD&T position with MMC invoked, my report now shows the size of every hole used to calculate the bonus tolerance.  I'd like to remove this from the report, as the same hole sizes show up once in the PLTZF, once in the FLTZF, and once where I just called for the diameter.  My part has 100 holes so eliminating these redundancies will remove 200 lines from the report.  

I'm just poking around now to see if I can find a setting somewhere but any help would be appreciated.

[[Ky...]]

I don't think the separate characteristics are necessary in the new GD&T engine. After you make sure that the size tolerance is set correctly in the characteristic (the diameter symbol next to the MMC symbol in the characteristic), you can delete or hide any additional diameter characteristics you or the system made (see https://portal.zeiss.com/knowledge-base?id=1128721 for instructions on hiding the characteristics, assuming you are in the US).

[[Pa...]]

Unfortunately this isn't a solution, Kyle, though I am in the US.  I'm familiar with the process in the linked KB article, which has been necessary since they broke the ability to mask and use text fields as we were doing prior to 2022 with the rollout of PiWeb.  

The additional characteristics appear on the report but nowhere else in the program.  They do not show in the chars list so I cannot mask, mark, rename, or anything else.  In my last program they just made a 70 page document into a 116 page document.  The world ended here in the eyes of my internal customers.

This output is way too much for my colleagues.  I'm forced to avoid using the GDT positions as long as this persists. 

It would be really handy if Zeiss would roll out documentation on major changes like this one beyond the release notes.  So many of the selections in GDT position use language which does not appear in ISO or ASME (like the "suggested" term that appears in all evaluation dropdowns) that we're forced to guess and test to discover what it all means.  I believe the entire purpose of creating, selling, and supporting this (really really expensive) software is to ease the inspection burden on industry, which is to say we all have full time jobs.  Those of us capable of discerning what the obtuse language means through testing are (at least in my case) very busy with daily demands, and likely none of us has a manager that wants to hear "I got the training.  I just won't know how to use it without an indeterminate number of hours testing".

My take:  Stick with the language in the specs. If you ain't got documentation it ain't ready yet.  

Rant over.

[[Sh...]]

I am having this same issue.  The problem at our company is that if it shows up that it is non conforming on our PiWeb Report for these specific diameter dimensions for MMC/MMB or LMC/LMB, it is then tagged "nonconforming".  Unfortunately, no amount of training or guidelines for our company is going to help.  I'm half tempted to not use the GDT Position now and I hope this has been corrected in new versions of Calypso.

[[Sh...]]

All, I put in a ticket with Zeiss and we figured out a solution for this issue.  If any of you are familiar with hiding the ".M, .L" characteristics mentioned on Knowledgebase -  https://portal.zeiss.com/knowledge-base?id=458620 , the solution is an addition to that code in PiWeb.  For my specific case I wanted to hide the diameters for GDT Position for MMR/LMR and to do that we used the code: 

{^((?!\.\(M|L\)|\^Diameter For).)*$}

If there is anything else that you particularly want to hide, I suggest being very specific in that code about the characteristic name so that you don't accidentally hide something important.

[[Lu...]]

I had the same issue and were told by Zeiss guys I can't hide what you want to hide

The only solution I have is to make a "Result element" and define the characteristics with variables

That's a lot of manual work with high risk of mistake but I have no better idea

I haven't tried the solution above that Shawn has posted

[[Ri...]]

Please sign in to view this quote.

I am under the impression that regardless of hiding via PiWeb, if the feature is OOT, it will still show up in the "No. values: red" at the top of the report.

[[Sh...]]

Please sign in to view this quote.

Oh I wouldn't be surprised but at least our company is aware of that and are excepting of it.  Surprised that has not been fixed yet though, huge problem.  I think if we all bombard the My Voice with likes on created issues, Germany may react.

[[Ri...]]

Please sign in to view this quote.

They should have a toggle for users who are not using SPC through PiWeb, just turn it off. 🫤