All Activity

If you are willing to send "inspection" and "inspset" file then i can look into that. I think those problems are often very specific and needs individual solving

Did you ever find the fix? I'm currently having the same problem on one of the program.

If you need for dialog in python, then you can use mesh selector. Or you can iterate through parts ( something like this ) for part in gom.app.project.part:

I know it has been a while since this post was made, is there a variable i can use for 'Part Name' that will allow me to grab the part name from multiple parts in the program? My concern being, the part name changes in the program to reflect the export name of the mesh.

For small chamfers i usually do this: measure both facing features ( like plane and cylinder ) make intersection to obtain 2x 2d line make intersection with those 2d lines ( it will make a point as sharp corner without chamfer ) make a touch point with coordinates from previous step and fill correct angles - use plane point ( forcing vectors ) now you touch that chamfer make theoretical line with origin from getActual("touched_point").x ( y,z ) and correct angles now you can measure distances from intersections of this Theo line and measured features. I can also post a full program with this approach

what is the best approach to measuring a chamfer on Zeiss Calypso? drawing is .50X45 Deg

I follow the cookbook but i run aditional tests and in my tests you can increase more then 50% more speed then recomended in cookbook the better way for circular scans circles u run one with max values on cookbook u create a local aligment in hat circle and u run additional scans with incresed speeds and you should look for diameter x and Y coordinates of the center and error form. this way you can have a good idea how far you can go between precision and speed. For filters i use from cookbook. im using this values

Don't you think a user savvy enough to know how to change the pw would also mess with the log if one existed? 🤔 Like I always said: Calypso's security is a stale joke.

I couldn't find anything either. If this is not logged, it should be. I think I have an issue where one or more users are logging in and out of Master and messing around with settings. I am changing the master user pword, again, problem is, a savvy user would know how to find the master pword and change it. I know I can change the master pword to what I want and then change it back to what it was.

I can not find anything which would be like a log. Perhaps there is a file rewriting it's content which could contain user change, but i doubt that.

Dictionary>>keyNotFoundErrorFor:Index: Makes me think of a pattern. Is the feature using a pattern? Is the characteristic calling from a pattern?

How can I determine when a user change has occurred in Calypso, particularly when in AutoRun. Is there a log file of user changes or some other file I can look at?

Was genau geht denn schief? Werden gar keine Dateien gespeichert oder haben sie den falschen Namen oder Pfad? Habt oder hattet ihr evtl. mehrere parallele Installationen verschiedener Calypso-Versionen? Dann gilt, dass in \users\public\documents\Zeiss\ nur die erste installierte Version den Verzeichnisnamen "CALYPSO" bekommt. Alle weiteren erhalten die Revisionsnummer als Anhängsel. Das müsste dann ggf. in der Pfaddefinition angepasst werden. Falls scheinbar gar keine Dateien geschrieben werden, prüfe auch mal die Datei protocols.log. Dort stehen die tatsächlich geschriebenen Dateinamen inkl. Pfad drin, und, falls das Schreiben aus irgendeinem Grund schiefging, auch das Anhängsel "MISSING".

Ja, die Felder sind hier auch vorhanden

The theoretical lines with distance 2,74 are not really defined. How to decide where to put them in the tolerance zone of position 28? Maybe position 17 should be TED aswell and they forgot the frame. Shouldnt the triangle base of datum B be on the arrows of postion 19 for symmetrie?

It seems that datum B should be symmetry of dimension 19. I am curious how to figure out which feature use to allow MMB. Dimension pos.(17) 19 should work like prism - defined touch points are 2.74 and 19 is like from vise clamping

Hallo Zusammen, ich stehe auf dem Schlauch und komme nicht weiter. In dem gezeigten Zeichnung Ausschnitt ist der Bezug B eine Theoretische Linie zwischen den zwei Schrägen Flächen. Diese scanne ich mit einer Geraden. Wie kann ich nun den Bezug B bauen? Dieser wandert ja je nach dem wie die Fertigung fräst nach außen oder innen um die Höhe von 2,74 zu erreichen. Ich arbeite mit Calypso 8.0.1603 ich habe keine Kurve Freiform oder PCM Lizenz. Danke für eure Hilfe.

sind bei deinem Kollegen die benutzerdefinierten Protokollkopffelder "u_xxx..." vorhanden?

We also largely stick to the standard procedure for inspections. In serial production, timing does play a role, after all. I adjust my approach depending on the specific feature involved; I measure a precision fit more slowly than a drilled mounting hole. The diameter matters, too—I scan larger diameters faster than smaller ones. And, as Karsten mentioned, I run tests: I use 1, 1.5, 2, 3, and 4 mm probes as well as disc styli.

Hello Erfan, if the activation fails for some reason (corrupted file for example), the license has to be revoked and a new one needs to be activated. To do this correctly, support needs the used license etc., so I recommend reaching out to the support again. If it still fails, the issue needs to be send to our license support in Germany I think. Nanno

This settings is stored in Calypso instalation. If you need to have tranfered to another station, then either send program with stored values inside this program ( not for all users ) and let him store those values inside his station. Or send those values via another means ( email, fileshare, ... )

Well, it depends.. We mostly stick to the cookbook. If the surface is rougher, we’ll sometimes use just 3 mm/s if it clearly yields better results. The speed with XXT sensors is also generally quite slow—somewhere between 3 and 10 mm/s. If possible, we use a 3-mm ball, but often the components are too small, and we need 1.5-mm or even 0.8-mm balls. All in all, if you have time, it's worth trying out different speeds to see how the results change when using the same filters.

Hallo zusammen, ich hätte gerade bei einem Kollegen die pdf-/dfq Ausgabenamen angepasst, gültig für alle Benutzer über die Master-Anmeldung. Leider wird der Name der Dateien dann nicht so befüllt, wie gefordert. Bei mir funktioniert es mit dem unten angegebenen Pfad (Ich hab Calypso 7.8, der Kollege 8.0) Woran kann das liegen? "C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\results\"+getRecordHead("vda_subjno")+"_"+getRecordHead("u_serie")+"_"+getRecordHead("u_mfumsa")+"_"+getRecordHead("u_arbg")+"_"+getRecordHead("u_teilnummer")+"_"+getRecordHead("date")+"_"+getRecordHead("time")+".pdf" "C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\results\"+getRecordHead("vda_subjno")+"_"+getRecordHead("u_serie")+"_"+getRecordHead("u_mfumsa")+"_"+getRecordHead("u_arbg")+"_"+getRecordHead("u_teilnummer")+"_"+getRecordHead("date")+"_"+getRecordHead("time")+".dfq" Den Ausgabenamen der Messpunkte-Datei hätte ich auch angepasst, übernimmt es aber auch nicht, hier hab ich folgendes eingestellt: getRecordHead("vda_subjno")+"_"+getRecordHead("u_serie")+"_"+getRecordHead("u_arbg")+"_"+getRecordHead("u_teilnummer")+"_"+getRecordHead("date")+"_"+getRecordHead("time")+".zmp" Sollte also im idmeaspoints abgelegt werden. Vielen Dank

All I can say is we are using exactly this to calibrate our probes since 2007 (when we migrated to Calypso) and it works reliably. We have to locate the sphere manually once (e.g. after maintenance) but after that all qualifications are done with probe calibration programs via Autorun. Each program starts with the master probe, followed by the probes to be calibrated.

Hi folks, What scan speed are you running on Vast XXT? How do you decide the value? Just follow the cookbook?