All Activity

Yes, this can be true that the nominal and actual plane are geometrical "equal" due to an established alignment/datum system. Nevertheless, in general you are not forced to do that, e.g. in the automotive industry an RPS alignment is usually established and not a planar datum in a Geometric alignment and then it happens often that the nominal and actual plane can differ. Even for advanced evaluation processes with a 'Geometric alignment' you can simulate a different alignment to see how the deviation would change. In all of these situations 'Actual section' as measuring principle can fit better to the application of the customer. If 'Referenced construction' fits better to your application simply use it! But please be aware when to use what due to the expected differences. Regards

Hello, I am working with two CMM's. One of them has the "Fixed Plane" grayed out and one works perfectly fine. I have no idea why, and I have been trying for days to get this fixed. Does anyone have any ideas of why the Fixed plane is grayed out? Thank you.

Hi, sorry for waking up this thread. You can edit this import by your needs inside import window. As Nanno posted link, there is an option. At bottom there is an preview of an element - change that into "Surface point", which will allow you to have vectors inside ASCII file. Also you can select if you want to have imported points as Actuals or Nominals ( when you want to import nominal points or measured points ) Now right clicking on column header you are defining which column is which. Today I was able to perform and test this approach. I needed to measure exactly on the same points as at Calypso. With help of another thread I was able to perform surface profile check within 0,02mm difference against Accura ( real deviation was 0,01mm - doubled because of profile callout ). Pretty impressive while I was scanning sandblasted part without spray. Later i made a screenrecord video to make sure i won't forget it 🙂

Yes, length of relief and amount of tip relief in this case

Thanks for the replies. I believe what I was La and Ca. In Gear Pro it's Ca and LCa. Picture is attached. Lou

Hi Community. Is there a PCM command in witch I can get the status of an element or feature? I search for a query for a feature/element not can be calculated. (magenta one) Is there a way to check ? (maybe true or false) Best greetings Sven

... Unsere Tasterdatenbank wurde bei der Installation von 8.0 migriert. Das führte dazu, das der Inhalt von 7.4 nicht mehr lesbar was ( SDo Fehler.. ) Ich durfte die Tasterdefinition komplett neu eintippen. Zeiss Support konnte nicht helfen: Nicht zu vergessen sind userfields.ini und dazugehörige Dateien samt Aktivierung in den Protokollkopfparameter. Eventuelle batch Dateien in ../workarea/inspections. War da nicht auch das kopieren der lokalen PiWeb datenbanken in den neuen Ordnerbereich notwendig wenn diese noch von Interesse sind? Es gibt bestimmt noch mehr. Wir mussten z.B. linePlot.ptx ändern um den Zeitstrahl sichtbar zu machen. Diese Datei ist in PiWeb Kontextmenu im Standardprotokoll fest auf einen Pfad programmiert der in C:\programme(x86)/... liegt.

I tried to be creative 🙂 Will have a look later on the tangential element(switch to outside) and look for differences between base-alignment and TP datums. Thank you for your time and support. Greetings André

Hallo zusammen, für mich stellt sich die Frage was genau jetzt in die einzelnen Ordner wandert. Grundsätzlich werden beim Import der Daten von der 6.8 in die 8.0 auch die eingestellten "Pfade" übernommen: Das gleiche gilt für die PiWeb Reporting Vorlagen: Wenn man zusätzlich noch Protokolle oder Messpunkte in einen eigenen Pfad evtl. im Results Ordner oder Unterordner ablegt, dann kann das Chaos Perfekt sein 🙂 Im Regelfall reicht es die Pfade unter "Arbeitsumgebung\Pfade" sowie im Reiter "PiWeb Reporting" anzupassen.(Einfach auf das rechtsstehende Symbol klicken dann wird der Pfad der jeweiligen CALYPSO Version eingetragen) Bzgl. der von @Karsten Kankowski angesprochenen SQL Probleme, dies kann ich nicht bestätigen, der Microsoft SQL Server 2022 der für CALYPSO 8.0 benötigt wird ist grundsätzlich kompatibel mit CALYPSO Versionen bis mindestens 6.0 (ist zumindest die älteste Version die wir bis dato damit gestartet haben). Aber auch hier, Ausnahmen bestätigen die Regel 🙂 Gruß Marcel

I think you should use outside tangential instead of inner ( i think it's in/out of material - not a definition of a hole/stem ) Form of KreisD_1 is also that little like 4H8? Then only reason for that would be difference between base alignment and TP datums ( and/or your second feature in distance measurement )

Dear colleagues, As much of CALYPSO still dates back to the 1990s, when IT was simply a tool and usually worked, I’m hoping for the standard functionality of that era. Virtually every piece of software (even CATIA...) could be controlled or enhanced via environment variables. One example is the batch files, which still work well as user exits. Now I would like to trigger a user input via one of these batch files, *calculation_end.bat*. I would then like to use this input – for example, a name – as a log header variable in a PiWeb log. We do not have PCM, which is probably the biggest limitation for such functionality. So is there a way to get an environment variable into PiWeb somehow? e.g. Zaphod_Beeblebrox=42 as environment variable Best Regards Karsten

Oha, Da hat Zeiss mal wieder etwas "ungenau" geantwortet. Mein Erfahrung ist, dass es besser ist die Konfiguration in den neueren Versionen mit murren und fluchen komplett neu zu machen. Werden irgendwelche Config dateien übernommen kommt es schnell mal zu Problemen; auch wenn Zeis behauptet das es keine gäbe. Fakt war bei uns auf jeden Fall das der Planner/Simulation nicht mehr lief und das die SQL Datenbank der alten Version ohne Warnung oder Nachfrage überschrieben wurde. Ein starten der alten Version war damit ausgeschlossen.... Wer dir auch immer gesagt hat das es einfach so ginge: Lade denjenigen auf seine Kosten ein und lass ihn die Konfiguration eintragen...

Here are some further information: The change to tangentialelement seems not to change the results Greetings André

Your instalation is correct. Files are in Program files and so on. Configs are in this path, so workarea ( inspections ), protocol templates and so on. If you don't have it, then in settings change your path to correct one ( CALYPSO 8.0 ), but i think it's done already. Now just copy inspection programs from old to new path and perhaps your templates, which you should redo into new ones ( you are missing new features in PiWeb )

OK, TP is from D-AB - is that an alignment or filled datums? According to norms - datums have to be tangential elements and perpendicular to higher datum. If you have an alignment and you are measuring YZ from that alignment, then you should have same numbers. Otherwise you will have different numbers.

I'm going to test this as soon as possible. Stay tuned...

Hallo Kollegen, ich hatte kürzlich ein Update von Version 6.8 auf Version 8.0. Der Techniker von Zeiss sagte ich solle einfach dazu installieren. Aber jetzt hab ein wenig durcheinander. Jetzt werden zwei verschiedene Ordner verwendet: C:\Users\Public\Documents\Zeiss\CALYPSO und C:\Users\Public\Documents\Zeiss\CALYPSO 8.0 Kann ich Version 6.8 einfach deinstallieren ohne etwas zu verlieren? Bzw. wie ist da die richtige Vorgehensweise?

Hello again, the additional report helps a lot as you can see: I will invest it further with new maschined parts. @Martin Jánský To be honest i don't understand the use of a tangential element in that case. The roundness of the element is 0,001mm so i'm not sure if it makes sense to switch. And i'm quite not sure where to switch to tangential element. Greetings André

Hi Lucas, Yes, the path is defined correctly. You can also see that because "Inspections" is selected at the bottom in the Filename field. The issue is that the Inspections folder itself should be opened in the Explorer window, rather than just appearing in the Filename field.

I wish there was a way to click 'apply' after a program is already built ,and it would apply to features AN characteristics if you choose. Also the option to UNDP or remove cookbook settings if you choose.

OK so then i think use correct evaluation - tangential element - that can do a lot.

I don't have 26, but i would say - explore that recorded script. Certainly you can remove some of it's content to fulfill your goals.

User Interface. It's Calypso's greatest weakness. The geometry wizards who designed and manage Calypso's architecture need to team up with an entirely different group to modernize Calypso's UI. My kids' Roblox games have more visually-fluent interface.

Hi Thomas, The path that CALYPSO opens when you click "Find" is set at Extras > Settings > Environment > Paths (Default Path for Measurement Plans). It is strange that renaming "CALYPSOFileDialog.exe" would open a different path than the one specified by the Default Path for Measurement Plans. Is the default path on your systems set to the Inspections folder?

You need to enable additional printout on those positions. You are reporting Simple distance which may not be the same as your DRF. Go to characteristics setting editor - Report - additional report - and change to "On" on those position. It will show you correct Y and Z used for position.