All Activity

Gentlemen, which colors have the ports in the setup dialog? Can you please provide the zipped logging folder after you activate the yellow marked items and after you get the error message? Please provide this via you local GEAR PRO support team. Thank you.

Hi. The change of the main evaluation ranges will not effect the K-chart or the K-value. The change will effect all standardized characteristics like Fa, ffa, fHa, ... If you want to create the behaviour you describe, you have to shorten the K-diagram like in the attached screenshot (marked red). I checked also the behavior to deactivate the "tolerance evaluation" of the K-value but the K-values still appear. This seems to be a bug. I assigned this issue directly to our development team. For such cases it would be really helpful to get your measurement file .act directly through your local support team in our organization. If this happens we can document the bug and from which version on it is corrected. May I kindly ask you to provide your measurement file .act to our support team. Inform them to link the .act to issue no. 819665. Thank you.

I report the measurement duration on my piweb report, i wasnt able to find it in the variable drop down menus, but looking at the text for the measurement duration it shows exactly the same as Martin Jansky listed. For me it reports the same time displayed in Calypso Monitor, no PCM needed here it is in piweb designer and here it is in the actual report piweb generates

That is my Problem, In my case, i must slice the entire curve to 52 segments (overall lengh of the Curve is 520mm) if I will have the exact requirement. The Requirement on the Drawing is on two Measurement-Highs. So I must setup 104 Segments 🫣 and every Segment must set to Best-Fit. Now I create an workaround. I slice the Curve in 14 Segments and calculate for each of this Segments the Best-Fit. Now I let calculate the Deviation for 10mm Steps. I know that ist not the best, but the best of two Worlds between exact to the Norm/Requirements and the technical enviroment.

Hi Adrian, I hope you can help me with this; I bought a sphere with a diameter of 8 mm with the stem that I use on the sphere with a diameter of 30 mm, and when calibrating the small probe with a diameter of 0.3 mm, I get the following. "The probe calibration could not be performed with this standard sphere. Check the radius of the standard sphere's stem. It has been detected that the stem radius of the standard sphere is more than 60 percent of the radius of the standard sphere." I should also mention that the master calibrated this new 8mm diameter sphere without any problems. What is the diameter of the stem on your 8mm diameter sphere? Thanks in advance.

You can edit file qdasconv.con like this:

Hallo zusammen, hat hier niemand eine Idee wie das gelöst wird? Die Merkmalsnummer wird ja in der DFQ immer fortlaufend beschrieben, unabhängig ob ein Merkmal ausgelassen wird oder nicht. Muss ich dann über Prüfmerkmals-Attribute die Merkmalsnummer fix vergeben? Der Termin zur Schulung ist erst Ende Mai, daher wäre diese Information vorab schon sehr hilfreich. Vielen Dank im Voraus!

Hi All, Is there an easy way to write a new program that is very similar to an existing one, but the Cad model has some extra features and some of the existing features are in different place or different diameter ? Obviously I know the 'normal' method which would be creating a new feature and re-name as the old one so the characteristics will remain the same. In PC-DMIS for example I can just open a feature and re-click on the CAD model and it will automatically apply the new coordinates and diameter etc. I know that there is a CAD comparison which never worked either. Any suggestions please ?

Hello @administrator, are the following ideas still in the back of the backlog, or is it getting any attention? -> Idea #E1D80 - Autorun: Define Sequences across Layers https://portal.zeiss.com/my-voice/software/metrology/product/066cc67a-e50f-470f-9884-a3ec3253c37c/request/1d912416-6984-4549-879f-515e221e1d80 Idea #DD2E3 - AUTORUN pattern in X/Z and Y/Z https://portal.zeiss.com/my-voice/software/metrology/product/066cc67a-e50f-470f-9884-a3ec3253c37c/request/a65d9548-e1c5-4103-833c-c08f9c9dd2e3 Best Regards.

Hello! thanks for your answeres! We use V8.0 Calypso 2025 but its look like as Calypso calculate that not correct.

Hi, ich hatte gestern, den Fehler nach längeren suchen gefunden. Scheinbar ein Software-Fehler. Dieser Fehler passiert nur wenn der Drehtisch in einem bestimmten Winkelbereich steht ca. 270°. Was aber neben dem Winkel zusätzlich für den Fehler gebraucht wird, fand ich noch nicht heraus. Konnte es beheben indem ich einen Zwischenschritt eingebaut habe die Achse wieder auf 0° zu drehen, allerdings tritt nun ein anderes Problem auf, die Maschine fährt erst auf die eingestellte Sicherheitsebene Z+ und dann sofort bis auf ca. 2mm über die Tischplatte in Z- bevor sie mit dem Wechsel beginnt.

This thread helped When i found userfields.ini realized what is what in definition of paths, then i realize that the varibles not exist.

STEP AP242 is listed as supported for Calypso 2024. Just make sure you are on the latest service pack, so that you have the latest version of the CAD Interop Server.

I do have the GEARACIS 9996/tcp in this file. Even tried reentering it a second time. Still getting the same error "ACIS socket already in use!"

We are working with NX. I recently had a problem bringing in a STP model where I get a message that my STP is not in the correct CAD format. Engineering has asked if AP242 will work with Calypso 2024, or if they need to give me a STP in AP214. I don't know what to tell them. Any insight would be appreciated.

I was able to confirm CALYPSO Service Pack 8.0.12 does restore the ability to edit and save the Compact Report header.

You will need a smaller reference sphere. As Marcel mentioned above, for a passive sensor, you have to run qual passive at least once. To do this, you have to have a smaller sphere.

Hello Zac, follow the link below. The issue is that your programs are on the network and are being shared by all your CMMs. The link to the knowledge base solution will guide you on how to setup your pc correctly. ZEISS Portal

I would avoid curves - mostly due unkown position and rotation - would falsely report crash. I would try to measure a circle with 6 points to obtain center - if it's not a problem to get close enough center, then use cirle, go to bigger probe radius, relatively fast scan speed hight density of points.

Go to Features > Circle Enter in XYZ Nominal Values where you want it to be measured. (Assuming X=0.0 Y=0.0 Z=0.100?) Nominal Diameter will be the 2x Radius distance to one of the flats. Create a strategy with 6 single points starting at 30°

Hallo Luke, gehe bei deiner Ebene auf Strategie, und dann siehst du oben in der Menüleiste ein Kreissymbol mit drei Punkten . Das öffnest du mit einem Doppelklick. Da drin kannst du dann ganz unten deine Kreismittelpunkt einstellen.

I would try to scan around with a couple of Curves, and use that in an Alignment from Several Curves; and then reference that with a 6 point diameter. Without Curve, I would scan the flats and try to use a Geometry Best Fit Alignment

Hello, I would like to know the best way to measure multiple parallel flats as a circle in order to get the runout from this to an outer diameter. The parallel lines rotate randomly per part around the center of the circle, so i cant just pick up each line and then recall into a circle. I am thinking of doing a slow circle path, and then using maximum inscribed, but am worried about how the filters would adjust the sizes, and i don't know how accurate it would be without any filters enabled. See attached photo for a easier understanding of my question. Thank you!

@James Therriault, what @Pat Bryant mentioned is spot on. When the (M) material modifier is used in a position characteristic, additional deviation is allowed as the feature of size departs from maximum material condition. An internal feature of size such as a hole departs from maximum material condition (and gets bonus tolerance) as the hole gets larger, and an external feature of size such as a post departs from MMC as it gets smaller. Although that's an important clarification, it doesn't appear to account for the .0036 difference of your characteristic between the (M) result to the unmodified result. @Martin Jánský seems to be on the right track. There's a lot of feedback from programmers about the confusing way that PiWeb reports this characteristic, even if there was an SPC-related reason for it during development. It feels messy and unfinished.

If A is in -X vector, then report TP|A only X and for TP|B only Y ( or Z i don't know )