All Activity

Yes, that is what i have been doing for so long is going into View and Multiple report and bring it back up. My bad, i was thinking you were talking about reloading the whole PiWeb report, like the Standard Protocol one that i am using currently. This is why the frustration has set in having to go in and reload the Multiple Report again.

I have been doing this for nearly two decades. I create the Base Alignment from the tooling balls. Add a Prompt to load part after that completes. The remainder of the program runs from a separate alignment, not the Base Alignment. Which works well for me because I never use the Base Alignment for any reportable requirements. All Features/Characteristics are tied at minimum to the separate alignment (I call it the CNC Alignment).

Hello, I have mesh/CAD comparison of a certain part. In this deviation analysis I can clearly see the deviating areas but what I am trying to do is to mark deviation where we have a sharp angle deviation from the surface. Does anyone know if this is possible? You can see in the image where we have this deviation but I don't know if this is sharp enough or not. Any tool that would give me that measure?

If you are able to create CAD Presentations, have you turned on the "Display plots in report"? Resources Character settings Editor Display plots in report Then you select any characteristic that has a CAD Presentation.

Ich verstehe sowieso ganz allgemein betrachtet nicht die Motivation hinter den modernen Farbschemata in aller möglichen Software. Das muss so ein albernes Lifestyle-Dings sein, dem man Lesbarkeit, Ergomnomie und wasweissich alles opfert, nur um "cool" und "futuristisch" auszusehen. Da würde ich noch lieber mit dem Mickymaus-Design der 90er-Jahre arbeiten. Was ich aber noch schlimmer finde als so ein Design zum Standard zu machen, ist die konsequente Beschneidung der Fähigkeit des Anwenders, dieses zu verändern. Früher waren Farbeinsteller allgemeiner Standard und das war sehr gut so. Heute bekommt man nur noch die feste Auswahl zwischen, Pest, Ruhr und Cholera. Warum?

In the top menu select View Then select Multiple Report This will regenerate the PiWeb report. One thing to remember, if you have opened any characteristics, the regenerated report will only reflect the characteristics viewed. If that happens, you have to cycle thru all characteristics, re-run the part with "Clear existing results" turned off.

Calypso_basic_ISO 5459 Section.pdf good questions about best practices, for me I use inscribe and circonscribe only to have diameters values, for GD&T and datum I use Gauss wich is more stable (even with ISO I should use tangentiel for datum). LEAST SQUARES DATUM DEFINITION.pdf the least squares datum definition article explain some behaviors of the differents methodes (even it give me a headache, it's realy interesting)

I tried this and if i dont use ALT-TAB right away and bring it up after it disappears. Then it is no longer there. Thank you for the information to try. I am drawing a blank on how to reload multi report? When you reload it does it stay up on the screen. How long after that do you have to reload multi report again because it keeps going away? It's frustrating for sure, i guess i am to the point of wanting to make it stop because i have been working with this for 2 years now. Thank you for the information to try out.

OK so if you can not scan hole as a cylinder, then you have to use that small plane at that hole for rotation. |Perpendicularity | 0.01 | A-B | C><| |TP | 0.01 | A-B | C><| Parallelism - that's odd

I have just recently discovered from ZEISS Inspect software due strange behaviour. According to ASME and ISO - datums are always as tangential element and elements used for axis are always perpendicular to previously defined element. At least that's how i interpret it now.

If you set up Smart Services you can view utilization and see the breakdown of how long the machine was in and out of cycle with times....Zeiss offers a free version with a limited history and a purchased version with longer storage times. It also allows you to see collision speeds/detection for each CMM

David, We use CNC information in similar way. To display the set-up picture we use irfanview which make it easy to aligned size, position, no frame, no buttons... To remove the displayed picture automatically I add a small script to C:\Users\Public\Documents\ZEISS\CALYPSO\workarea\inspections called "inspection_start.bat" --> See CALYPSO documentation This will kill ALL irfanview process just if the user press the START button. O.K. this is a real hard-kill option. Better will be to identify MY irfanview process but I´m sorry: Windows has the most dreadful Process ID management system I can imagine. I’m not wasting my time on it. inspection_start.bat

Hi Damian, Deviation measures have specific behaviour. For Min and Max deviation measures the tolerances can not be set. The values are taken from the segments they are analyzed on. It is only possible to set tolerances for average, range and profile error deviation measures. This information can be found on the manual (F1) Hope this helps

Kleines Update, ich verwende Calypso 2025 und Martin sein Code funktioniert prima. Ich habe keine PCM Lizenz.

Hallo Jörg, bilde ein Koordinatensystem mit 6°. Setze deinen Antastpunkt in diesem Koordinatensystem auf die Fläche. Jetzt sollte der Vektor senkrecht zur Fläche sein. Gruß Wolfgang

I measured Datum A with 16 self centering points (ball Ø3.5), also checked with tangential feature, result was the same, so I chose faster measurement with self centering. Thanks for help 🙂 Is there any source where I can read about LSQ, tangential etc. how and when to use them?

Thank you martin: Please see attached picture. Please note Ø of hole is 3.5 cm.

To be more clear, I'm speaking of the Evaluation command, "CAD Presentation" that lets you use a created/saved CAD image (usually with deviations displayed) as a picture inserted into PiWeb report (StandardProtocol). It worked well in all previous versions I'm familiar with. It "runs" with no runtime errors, but leaves the PiWeb report blank in that area. It lists the feature but fails to display the image as normal. It even lets me create a new feature in this version as normal, but still does not produce an image on PiWeb. I am using a "Planner" offline key to test it, but I don't think it has any bearings on whether it would be better or worse on a machine license. Like I said, I had heard that it was "broken" this version, but hoped it was 'fixed' by 2026 (or end of 2025 updates). If this specific feature does not work, how does one display the plotted images of CAD deviations from Freeform Profiles onto a report in this version??

Well nothing is changing - only nominal representation. So you only link deviation in Z against nominal point and measured point. Unless you want to keep some numbers, then point in new alignment is the easiest and the most predictable. Of course you can move origin in new alignment to keep your old nominal value and still keep that correction in needed axis.

@Tom Oakes Yes, you are correct. The GBF does not move the origin where as a new alignment would change the nominal origin.

@Richard Shomaker But doesn't setting that point as Z origin establish a new z origin, which would offset the curve the difference between the BA and the 2nd alignment? Where the geometry best fit should report the difference between where the point's z nominal and actual.

I am curious how you want to measure this, but your only option here is either make many lines and do tangential feature ( radius between lines ) or curves. Then form a plane from each circle's center. But still it should be tangential element - in this case vector of that plane should be outwards from material.

In Autorun: Tools --> Always leave the CAD window open

As Isagani mentioned, from the ZEISS Portal KB - CALYPSO: How to Add Set-Up Information to a Measurement Plan

Yeah, I think the base alignment match needs to be replaced by a better process, or as you suggested provide more visibility to how it is matching. Polyworks has a one of the more effective processes I've seen for matching point cloud meshes.