All Activity

I downloaded the ZEISS CALYPSO 2020 service pack (7.0.20), installed it, as I understood it, he just reinstalled Calypso. Unfortunately, nothing has changed. And what is CALYPSO_Preset_Setup_7.0.0006 for, I also installed it, but everything remains the same?

Hi! I couldn't open your link, but I'll try to download and install the updates! Thanks!

I, too, am seeing this message displayed when opening various measurement programs. It began a month or two ago after upgrading to Calypso 2025 - any ideas how to 'fix' this?

I would advise to make a Datum system - then you can export your points in correct alignment. ATOS is creating alignment from first scan where direction of a scan from ATOS to the part will be Z axis. Also you can face a problem with too many points in export. You can reduce number of points in menu Operations -> Section -> Sample sections. There is also an option in creation of that section, where you can force points by fixed distance - that works only on rough mesh - it will not reduce points, but increase points, where are big triangles.

Unfortunately this is wrong selection of datums. At least one more datum should be required - i would prefer plane where is datum D. Alternatively a perpendicular plane to that plane. From this sheet you can not have strong datum to such small tolerance over that big distance. It should be better to ask engineer which of those planes are available to be a datum.

Little late to the party and love the discussion. For those interested in making CALYPSO turn green for the rounded off decimals here is a link on how to do it. It is a dirty trick. And again as discussed not really suggested but some users understand this and allow for this exception to be used in their process. https://portal.zeiss.com/knowledge-base?id=2541215

I have a bracket where I have a positional callout going back to a single datum and am curious as to what the standard practice is for setting this up. Is it something as simple as selecting the hole for the characteristic and then only selecting the opposing single datum hole under the "datum" section. Or is there some sort of specialized alignment that needs to be setup first and then referenced within the characteristic side? Our engineering group has relayed that the intent is to control the hole to the single datum hole only due to the variation that is inherent within the bending process during manufacture of the bracket.

In regards to installing CAD Interop Server https://portal.zeiss.com/knowledge-base?id=2496572

Agreed. I would appreciate a method to manage license usage without needing direct access to the server machine where the license is hosted.

Unfortunately PiWeb even if you have multiple protocols/templates there is only one option for setting the directory for all PiWeb PDF reports. The only sudo work around that might work is to use ghost protocols as an alternative path. Ghost protocols is a merged PDF output, so it would put both your PiWeb protocols into one PDF but that can then be set to a different directory and you can then keep the first protocol template to the other location you prefer. Here is a link on how to setup ghost protocols if interested. https://portal.zeiss.com/knowledge-base?id=1112672 Note the individual protocols will still be made and saved in the PiWeb PDF directory, the merged ghost script PDF would just be in addition to those PDFs, but can be controlled to a different directory. The cleaner route would to use some scripts/batch files to move the files post run if you are savey enough to do that.

Absolutely no issue leaving your stylus systems in the head when shutting down. In fact it is actually recommended to leave something in the sensor to keep the contacts from being exposed. Only thing to consider is homing issues, if you leave a very awkward styli (long/wide) in the sensor and home the sensor after the reboot, you may have a collision with homing navigation. Which a few posters above have given awesome recommendations to prevent this.

Server not started errors can be caused by a few things. First thing I would try to do is make sure you are on the latest service pack of CALYPSO 2021. Typically causes of that error is usually because some IT protection is impeding CALYPSO/PiWeb executables. Below is a link to the antivirus/firewall whitelist you may need to make sure nothing is being blocked. Things that may have worked in 2020 may still get blocked in 2021 version because they are treated as separate software's and needs to be given proper permissions. https://portal.zeiss.com/knowledge-base?id=563509 Some users have also had success with uninstalling and reinstalling the software too.

Hello Daniel, A new license activates previous versions for CALYPSO. Purchasing the license for 2025 gives you access to versions all the way back to 2013 (5.6). Just specify with the AMS representative that you need to be able to use 2023. This way they indicate on the order that you need the 2025 (activates 2025 + 2024) and 2023 license technology type (activates 2013-2023). This is only a technicality due to license technology change in 2024 specifically. You need not buy licenses for specific release years for CALYPSO. The current license release activates legacy versions as well.

What sensor and version of CALYPSO are you using? You should be able to set the sensitivity regardless of qualification settings.

It's data management request, I am not sure why they need as that either.

Danke, hatte da noch nie rein geschaut da das immer geklappt hatte. Wieder was neues gelernt.

Hi, The IT department refused to tell me specifically what setting, or settings, stopped PiWeb from printing reports due to potential risks to our security. Kinda disappointing because now that the other OMM's were upgraded to 8.0, they all have the same issue, and IT will not be available to resolve it until early April.

@Nanno Muehl Thank you very much, I just updated 2026.0 to 2026.1 so config file was the same, changed that parameter and performance are back to 2025.4 level. I can finally switch everything to 2026 and keep full speed of my workflow. Good job on fixing that problem at the first SP release

Yes I tried that. The only way I can fix the repeating issue is to toggle from the scan button to home and back. Then it works.

Hi Alejandro, it is not possible to export CAD files in a CAD format. They can be exported as .STL to use them in other software. Nanno

Hi All, Does anyone have an offline dongle Calypso 2023 with curves for sale ? We have contacted Zeiss, but they do not want to sell any older than 2025

The scan was very slow so it should not be porous

First off, I'm a newb on my GOM and Zeiss inspect(I'm actually using ATOS Pro v8). I'm looking for best practices for exporting XYZ points when you section a mesh. I was successful in exporting my points but I want to feel out what other people are doing. Here is my current workflow: 1. scanned the part 2. created a fitting plane to use as my reference plane 3. Used "construct single section" to create my line profile 4. Then I just used Export>ASCII file This worked but I noticed something weird. I sectioned my surface 4mm above the reference plane. But my Z value on the ASCII is at -3.27mm. The XY plot for the blade I exported looks right, so I know it exported the section I wanted. But I can't figure out why my ASCII Z values aren't closer to 4mm. To complicate it, I created a local alignment on top of the blade, I think my ASCII file might be aligned to that, but I'm not sure. To summarize: An I using the best workflow to export XYZ points from a mesh with no nominal CAD? How do I know which alignment my ASCII file is using?

In 2025 once a point was measured it was visualized with full splat size and fixed normal. In 2026 the visualization of scanned data changed slightly; splats adapt over time. The more a often point is observed the bigger the representing splat gets. This should give an indication where data is measured sufficiently to get a good mesh without holes. So if you just do a single quick scan on a surface you'll get porous visualization.

Then why does everything work, Calypso starts up, makes measurements, and only after the measurement is completed, when the report should be generated, an error pops up!?