All Activity

Hello Elijah, Choose the light bulb on the bottom right corner, then select loose.

Hello All, In the C:\Users\u7bkudanian\AppData\Local\Zeiss\CALYPSOFileDialog.exe path, there will be a user.config file. Its ASCII so you can open it and remove certain recent programs or just delete that file and the Recent list will be blank.

I needed a probe angle adjustment while testing a CMM plan. I used the joystick head articulation button to select a new probe angle. When the angle was selected, I went to measure a point by clicking on the cad model. I turned the articulation button off and moved the head around to add "CMM Position" points to the strategy. I closed the feature dialog and RT clicked / Executed measurement. The probe went into an over traveling / collision direction!!!! Has anyone else noticed this? Is there an effective way to let Calypso know what probe angle it has? During this the RDS rotate stylus indicates the actual probe angle. For some reason the strategy dialog has not caught up yet.

Good evening, I am new to Calypso Zeiss.I am busy with dmis export of the measured points and i want to use a very specific header.Is it possible to modify header fields according to my needs.I mean i want that the header uses whatever fields i give.For example of one field PR(1)=12345678 Thank you in advance.

we have a Knowledge base article also on How to Customize the Standard Protocol Header https://portal.zeiss.com/knowledge-base?id=454780

I believe so by mapping header variables Here's a doc I stumbled upon .. https://qualityforum.zeiss.com/migration/images/267_af4856641ffdecd817e9e29ae54f4816.pdf

I need the display of the additional coordinates in the PiWeb protocol itself, please show, how did you gray the theoretical values?. is it possible for the right values that the symbol is not drawing...maybe a dot? thanks for the answer

@TIM MCKAY Interesting. Can you post the code for review? How are your programs set up (for example, is it one part or many stages)?

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?