All Activity

Hello , I change my mind. 🫢🫣 What do you think , is it right ? 1. construct 3 planes from point + normal plane from datum system , X+Y+Z 2. evaluated separately for axis for X+Y+Z + together .

Hi Norbert, The latest release of ACIS is described in the release notes for CALYPSO 8.0. I may be wrong, but ACIS is a 3D modeling program. So it’s about calculating and breaking down 3D data, not about displaying it. The display is then usually handled by a graphics engine, which (if it’s modern) uses the GPU for rendering and so on. On our computers, the NVIDIA settings always say “Autodesk Motion Builder - Compatible.” Anything else consistently causes problems.

Where did you get this information from? 😯 ACIS R35 ist the 2025 version of the ACIS CAD core. I don't think it could be much more recent in Calypso 2025. 😄 I strongly doubt ACIS only uses the CPU. While I can't provide a source explicitly stating it uses the GPU, this would be absolutely unthinkable nowadays, don't you think? Who would buy a CAD software (ACIS is not Calypso-only) that doesn't utilize the GPU? So the question is not so much "does it use the GPU at all?" but more likely "which GPU does it use?". On hybrid systems with a GPU and onboard chipset graphics, the chipset graphics is often preferred over the GPU in normal applications to save energy. This setting can be changed in Windows as well as e.g. in the nVidia control panel. Another possible reason why Calypso gets sluggish with complex models might be the fact that it intensively communicates with the CAD core to query and update all the information about the CAD entities (which you can see in the hierarchy) and to combine the rendered model with all the overlayed Calypso stuff like vector arrows, labels etc. So I rather suspect the inefficient data traffic between Calypso and ACIS is the culprit. And this is really an old concept that was introduced decades ago and was never really brought up-to-date.

What @Martin Jánský said. You can ignore the UZ 1 and just do angularity with 2 mm tolerance zone.

Hi Dave, Keep in mind that CALYPSO was developed sometime in the early 1990s. Back then, ACIS was also used as the 3D kernel, and of course, that hasn’t changed to this day. ACIS uses only the CPU and will likely never use a GPU. The current version in CALYPSO 8 is ACIS R35 2606.2.8.0. The poor performance when rotating or moving objects is mainly due to the graphics engine. It’s probably just a very old piece of software that Zeiss hasn’t (yet) brought up to current standards. The big breakthrough with CALYPSO 8.0 was supposed to not only finally be 64-bit but also deliver major performance improvements. Let’s wait and see what version 12 brings....

Thank you Martin. I'll consider that for future.

A torus is defined by axis and D1 and D2 ( or radiuses ) so this should be reportable.

Looking for information and or suggestions on how to report the Radius of this Torus. All help is appreciated.

Sometimes I need to load a fairly complex CAD model which is annoying because that means an extraordinarily long time programming because of the sluggishness of Calypso. Rotating the model in the cad window is very choppy. If the cad window is being rendered using the GPU this should be as smooth as butter, but when I look at the performance the GPU is doing almost nothing. Does Calypso even utilize the GPU at all? I have a Quadro P5000 which should handle it just fine. Is there a setting I'm missing or is this just how it is?

This section is dedicated to software "ZEISS Inspect" You should have write into section dedicated to "ZEISS Calypso" Mods can move this thread into correct section.

Hello Richard. Thank you for the response. But what do you mean: Zeiss Inspect forum, not the Calypso forum: Members post questions about Calypso all the time. Am I missing something here.

This is the Zeiss Inspect forum, not the Calypso forum. Either way, I typically never scan short or partial cones unless they have a Runout callout on them. If you are just after the angle/diameter calculations; try (3) cross sections with (4) touch points. Then I typically will lock the normal vector of the Cone. Good luck.

If you are able to access the knowledgebase, this article should be a good guide https://portal.zeiss.com/knowledge-base?id=444235

Hi @Charles Bliss. Marcel's list is a great start. If possible, retain access to your previous laptop for a time, perhaps 15-30 days. Usually when I do computer swaps on Zeiss systems, there are files and folders I realize after the fact that I needed. Since I primarily use NVMe SSDs, it's easy enough to retain the old SSD and store it in a USB enclosure. Small footprint and value-added protection.

Hello everyone. Can somebody please share proper settings for Filter & Outlier Elimination when scanning partial section of the Cone. In the attached Image I'm scanning a Nylon Segment Gear that is 30.9258mm in diameter. As you can see Cone angle is only 1 degrees and range of scan is only 162.1473 degrees.

This is nonsense callout. Same like flatness it's reporting distance from MIN to MAX point on plane defined by angle from datum. In this case it would be better to use perpendicularity - it's 90°. But you can not use assymetric tolerance.

Have you tried the option "projected tolerance Zone"? Have not used this myself, but looks like this would provide the function of an offset tolerance zone. Or not...

On old laptop do a backup and then restore on the new one Extras>Settings>Miscellaneous>Maintenance> Backup Turn off windows security temporarily on new laptop (license dongle is CryptoBox which might get blocked) Create exceptions in security for Calypso/PiWeb etc Machine and styli C:\Users\Public\Documents\Zeiss\CALYPSO\Config Programs C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\inspections Saved alignments C:Users\Public\Documents\Zeiss\CALYPSO\workarea\basesystems PDFs/table tiles C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\results Custom header info C:\Users\Public\Documents\Zeiss\CALYPSO\protocol\protform Custom Excel templates C:\Users\Public\Documents\Zeiss\CALYPSO\data\excel_report Licenses C:\ProgramData\Zeiss\license directory (program data folder is usually hidden) If connecting to the cmm machine then make sure the IP for that network is set to: 192.4.1.199, and submask 255.255.255.0

Hi Michael, I am measuring a blisk. I'm limited to programming in Calypso 2023, so I cannot place patterns on a FreeForm Surface, so currently I'm programming it as 3d Curves that I will then recall feature points into a FreeForm Surface. Due to orientation and angles, I'm measuring it as (3) cross-sections, and (2) different angles, so in total it is (6) 3d Curves, per side, so in total there are (12) 3d Curves that make up one blade. I'm looking for an efficient way to correctly recall feature points from the (12) individual 3d Curves into their respective FreeForm Surface. So for the example above, I'd need to pull the points from 3D Curve - 1-1(1), 3D Curve - 1-2(1), 3D Curve - 1-3(1), 3D Curve - 2-1(1), 3D Curve - 2-2(1), 3D Curve - 2-3(1), 3D Curve - 3-1(1), 3D Curve - 3-2(1), 3D Curve - 3-3(1), 3D Curve - 4-1(1), 3D Curve - 4-2(1), 3D Curve - 4-3(1). And that is for just the first blade, there are 115 more to create. It's a lot of manual work that I'm trying to avoid if possible.

Hi everyone, I could use some help here. I have a drawing that specifies an angularity check with an asymmetrical tolerance zone. How do I inspect this? I’ve already constructed the feature to be inspected and the datum. However, when I try to check the angularity, I can't set an asymmetrical tolerance—like you can for a surface profile, for example. Does this actually work for angularity, or do I need to inspect it differently? Thanks in advance for your help!

I just received a new laptop and need to know what folders I will need to keep from the old laptop. I don't really want to have to re-define all of my probes/tips. I currently have 5 different machines, with each on having at least 30 different tips defined. Is there a folder on the old laptop that I can just copy over to the new one? And still have them defined.

Thanks Lucas. I don't use an RDS so that explains why I haven't heard of it.

Thank you for your feedback. This would be why I am considering a Fitting Position.

Then i'm affraid only option would be separate application which would take out information from files ( .hdr, .chr, .fet ) or excel and make own protocol.

Hi Martin, Thanks a lot for your answer. I had already suspected as much, but there are so many hidden paths in CALYPSO. MyVoice isn't an option! If you just look at Zeiss's response to it (years of dithering...), MyVoice comes very close to being a black hole.