All Activity

Wie Norbert sagt mache ich das auch. Ich lasse die alten Versionen immer drauf. Und beim Sicher wie Norbert sagt wird nicht alles gesichert. Die Tasterdatenbank zum Beispiel werden auch nicht gesichert und noch einige Sachen mehr.

We had a similar problem with one of are Contura, we chage the RDS head, but it not helpt, after trials the problem was two cabels connectig Measuring head with the Controler.

Look inside of protocol template and find "detailed". Another possibility is some formula/condition formating based on it's name

Those are only logs - they can be deleted, but i wonder why they appear there. I looked there and i have there logs with name of a feature and inside are measured data ( X,Y,Z ) Also some of probe system info. I am not sure why you have such naming of files, but investigate a little what's inside and perhaps you will find something enabled inside program to write those logs ( like export data, curves, ... )

Works like a charm! Thank you very much!

Kann ich so nicht bestätigen. Wir machen das seit vielen Jahren so, daß wir die neuere Calypso-Version parallel installieren. Überschrieben/gelöscht wurde da noch nie was. Da die SQL-Datenbank ja für jede angelegte Maschine separat im Config-Verzeichnis gespeichert ist, sollte da nichts passieren. Ich übernehme immer die alten Daten mit der offiziellen Datenübernahme-Funktion, die beim ersten Start aufpoppt, und das hat meistens gut funktioniert. Zusätzlich mache ich noch ein Backup mit der eingebauten Sicherungsfunktion. Die sichert aber nicht alles, das muss man wissen. Z.B. Basissysteme muss man noch separat sichern. Ich will jetzt nicht behaupten, daß damit immer alles 100% übernommen wird, aber gelöscht (d.h. gelöscht im bestehenden alten Verzeichnis) wurde da noch nie was. Was man ggf. beachten muss, ist, daß die neuere Version die Umgebungsvariable CALYPSO_DIR dauerhaft auf ihr Verzeichnis umbiegt. Das kann dazu führen, daß bei Verwendung der alten Version an bestimmten Stellen auf Daten der neueren Version zugegriffen wird (z.B. beim QDAS-Konverter). Was mich allerdings manchmal sehr stört, ist eine Inkonsistenz bei der Benennung der Ordner: Die erste auf einem Rechner installierte Version bekommt immer den Ordnernamen "CALYPSO", während alle weiteren Parallelinstallationen die Versionsnummer hinten angehängt bekommen. Dadurch muss man bei Rechnertausch oder sonstigen größeren Änderungen immer alle möglichen Config-Dateien durchforsten und die Pfade anpassen. Das sollte endlich mal geändert werden.

Norman Jank How do you make it so gray? Is it possible to also delete the starting symbol for these lines?

In the folder C:\Users\Public\Documents\Zeiss\CALYPSO\log i found 15GB of Log files. CaN I delete this ?

This has been explained many times already. You need to set your location to the USA in your profile (not in the forum). Then log out and log back in. You will then be able to access the Knowledge Base.

Hi all, I have the same problem as Rene. When I click on the links, a page with "page not found" appears even though I am logged in. Does anyone here have a reason or a solution to this? Is there another way to get the linked files? Greetings Gerry

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.