All Activity

Same as Zen and Pat methods using self centering point and min/max coordinate. Scan the bore across lands and grooves using a line feature, use maximum coordinate (for ID) to get the farthest point from the center of the bore, then create a self centering point using the farthest point. Use the self centering point feature on your alignment in planar rotation. Rotate your alignment to get the land. In the attached pic, I have an external spline with 64 teeth that is why I used minimum coordinate.

It has not been resolved yet. I tested the 1st fix attempt from Germany in mid February. The issue is still ongoing and I look forward to testing the next fix. I have added move points to all of our programs with a torus as the stop gap solution for the short term.

Hello, in Inspect you would usually align the mesh to a nominal CAD. In cases without CAD data, the part can be scanned in the correct coordinate system, or an initial alignment like 3-2-1 is used. As @Jochen Heller suggested, the symmetry plane is like a Gaussian plane through the part with a constraint in this example. The direction constraint could be defined by any element with a direction, maybe even with a plane in viewing direction, if you want to visually define a plane similar to the video (ZEISS Quality Tech Guide). With a UDIP it is also possible to construct a coordinate system in a similar way, after the first direction is defined. For further inspections I suggest using defined elements for the directions, also for repeatability. For a first coordinate system, a UDIP could be used in Inspect. The rotations can be refined by using rotate. But again, for an inspection task I don't think manual alignments should be used. For following inspection task on measured parts, a pseudo CAD from an aligned mesh could be used as a nominal element for a prealignment in the standard workflow. 27-03-2026_17-26-02.mp4 If you want to play around with the UDIP (very powerful tool by the way 🙂 ZEISS Quality Tech Guide) you can install the App and apply it to a nominal plane like a measuring principle. For reverse engineering of free form surfaces, the coordinate system should not be that important, because there are nor directional constraints like for a cylinder axis or plane normal. Nanno Coordinate system.addon

Hi, there could be several 3D placeholders, one for each stage on a report page with the inspection details for all elements on it ZEISS Quality Tech Guide to get a quick view of the status. There is also the possibility to create stage ranges dynamically by expressions. With the expression project_statistics.all.number_of_within_tolerance != project_statistics.all.number_of_toleranced_attributes there will be a stage range with all stages with at least one inspection out of tolerance. If you set this stage range active with report style 'Table', the table will only show stages, where this condition is met. When the stage range is active and a report page is created with this view, it will update dynamically. The table needs one visible check, but the display could be edited to something like this:

hahaha, okay, understood

Undo button, Go through it's pockets and look for loose change.

Hallo zusammen, mir Stellt sich die Frage ob es einen Weg gibt, die Tastereinmessung im Piweb-Protokoll abzuspeichern. Hintergrund ist das bei uns mehre unterschiedliche Leute, in unterschiedlichen Abteilungen die Tastereinmessung durchführen, im Arbeitsprotokoll wird die Personal-Nr. nicht abspeichert. Den Arbeitsprotokollkopf kann man nicht bearbeiten? Hat jemand eine Idee wie ich das umsetzen kann? Hinweis es sollte ohne PCM funktionieren.

Update: Instead of using results element for the calibration date, it was added in the comment. Thanks to Michael Schultze for sharing the knowledge.

I don't think so. The Position of a CF to A would just be the orientation of the symmetric plane to A (Perpendicularity), but the Position of a 2x pattern to A would be each of their orientations to A (Perpendicularity) as well as their respective orientation and location to each other.

Moin Manuel, also ich empfehle Dir bzw. wir weißen nur die Streuung und den Durchmesser/Radius von den Tastern aus. Die Position wird ja durch das Kalibrieren/Einmessen komepnsiert. LG Christian

A brilliant joke to round off the weekend. I’ll be laughing out loud over and over again for days to come! Thank you so much!

We use AutoRun on some of our machines, but for others the desk dropdown would be massive. Thank you anyway

Hi Monika, I´ve changed this in the "Charateristic" directly. You just have to pay attention to which direction the + and - - goes into the material (Ø gets smaller) + goes in the other direction. This works for th hole curve.

Hi everyone, Does anyone know if there's an undo button, or if there's a way to access it? Thanks a lot.

I'm interested, isn't it the same thing in this case - pattern or continuous feture?

I enclosed send the drawing details. That is in 2 outer ground diamters. The lengths of cylinder: 22h6 about 25mm long, 25h6 about 30mm long.

Yes this was corrected in Calypso 2024 and beyond. Also note that there was a huge change in the way the DRF was built inside of the GD&T engine in 2023 and 2024+. Mainly it is in the fact that no matter what orientation the program was in, the 2023 engine built the DRF in the X/Y plane, but 2024+ tried to retain the original orientation, so if you open a program in 2024+ that was built in 2023 be prepared to update the nominals of the Position characteristics.

I mean "technically" you should, but given that it is only .020" deep that might pose to be a challenge.

You are correct. For whatever reason I was looking at it as a continuous feature. You would still need to measure it as planes, correct?

@Tom Oakes No. The cookbook does not follow the d:r rule per the ISO spec in most cases. In addition, it makes no note of the d:r rule. According to the ISO spec you would actually need to use a 1mm stylus for a 251mm diameter, and then scale up from there. Having said all of that, the ISO spec still never says that you should use; it just specifies requirements for whichever one you do use. In addition, I did notice that the ISO spec requirements that I showed was for Longwave-pass which I wouldn't think you should use Longwave-pass filters for a roundness evaluation. I will also note that per NIST, they only use the 50UPR when certifying ring gages (regardless of size).......

Thanks, Martin. I'll keep playing around with it to see what happens. I did also start a dedicated thread for this issue here in General Category as well, in case there are other answers there.

Thanks Lucas. Pending further input, I'll chalk it up to Beta and see if it corrects when we upgrade next.

@CASEY SNODGRASS I've never got this resolved - restarting Calypso is working and i can not replicate this behaviour on purpose - it's random

Hello Casey, I believe this behavior is expected in CALYPSO 2023. I tested this on my system and receive the same icons in the PiWeb report. Please keep in mind that the GD&T engine is a beta version in CALYPSO 2023. I hope this helps even though it might not be the answer you are looking for.

Side note: All the new gdt engine icon DO show up in the characteristics tab, just not on the PiWeb report