All Activity

Not sure off hand, but does CBA use the AAI interface? If so: getRunMode("aai") will return true or false.

I'm just bumping this one up, does anyone have any ideas?

Are you using the automatic chip ID's? To me, it sounds like there are probes that have been taught the wrong automatic ID.

I noticed when switching between versions You have to be careful with probes as it may be off something about how probe files interact

https://portal.zeiss.com/knowledge-base?id=2802841

Hello this look to be Hardware issue i would suggest to make a new service request for HW team to check it

I have had this coming up for a while now after our last service, any idea how to correct it?

I have had a development. I have Calypso 2020 still installed on the machine, and tried that just to determine if it was a hardware issue or a software issue to ensure I exhausted all investigative options before doing something drastic. 2020 functioned without issue, so i figured something went wrong in 2024 and a clean install would be needed. But I returned to 2024 to double check everything before taking that step, and the issue was gone. 2024 had been opened and closed several times, the PC and CMM restarted several times, but using 2020 for a quick check and going back to 2024 resolved the issue. I do not understand the issue, or why that fixed it, but as of now the issue is gone.

I have had a development. I have Calypso 2020 still installed on the machine, and tried that just to determine if it was a hardware issue or a software issue to ensure I exhausted all investigative options before doing something drastic. 2020 functioned without issue, so i figured something went wrong in 2024 and a clean install would be needed. But I returned to 2024 to double check everything before taking that step, and the issue was gone. 2024 had been opened and closed several times, the PC and CMM restarted several times, but using 2020 for a quick check and going back to 2024 resolved the issue. I do not understand the issue, or why that fixed it, but as of now the issue is gone.

I'm trying to see if CBA is running and what mode its in to determine if a program will need operator inputs or not. I see that there is facsIsActive but my group is using CBA not FACS. If anyone has found a workaround for this it would be greatly appreciated

Good morning, I have a new problem occurring on our spectrum III, running Calypso 2024 with service pack 5. Starting yesterday, when an automatic probe change occurs, user driven or in a CNC run, it will swap probes, and update in the the automatic stylus change window. But it will not change the probe that it thinks its using, the auto change window will show the correct info, but everywhere else will show the previous probe still installed, like the probe system qualification window. The system will continue to run, as if the probe change occurred, but using the wrong probe data. For example, if a program is using a 3mmx25mm probe, and then changes to a 1.5mmx50mm probe, the change will physically occur, and the CNC run will continue as if it has the new correct probe, but it will try and probe the next feature using the dimensions of the previous probe, meaning it will crash if the new probe is longer than the previous. If you do a manual probe change and tell it manually what probe it has, it will properly update, but this is the only way it will change. If I have the master probe in the machine, and do an auto change through every probe in the rack, it will do every change without issue, but the probe system window will always say master probe until I manually change it. Possibly unrelated, but my probes also no longer update the qualification date in the stylus system management window, but the date will update in the probing system qualification window. If i qualify a probe, the date in the stylus system management window will only show the last date qualified before these issue began. I'm hoping I might get some help here before I delete all the stylus systems and rebuild them, or put in a call to Zeiss, both of which will be annoying and time consuming, especially given that the CMM PC is not connected to the internet. Appreciate any help. Update, I added a new stylus to the system as a check before I decide to delete and remake everything, and found that the new stylus will always be unqualified in the stylus system management. It will be entirely red with no geometry or quality values despite just being qualified and having values in the probing system qualification window. Starting to feel like I might be looking at the possibility of having to clean install calypso.

I created a .Net program for using a 36x36 Rayco Plate with 1.00" spacing for Grid location of fixturing on a CMM. (Grid size is automated in the code). If you have a smaller plate, just use the grid locations for the size plate you have. I am attaching the program for users of this forum in 7zip format to use as needed. You will need ".Net Desktop Runtime 10.0.11 (X64)" installed, or the software will attempt to install during the software install process. I had zero issues installing on Calypso v2016, v2017 and v2022 with this install other than you may need Admin rights. This allows me to add a part number (I use my CMM program name) and identify the locations on the Rayco plate. The Grid viewing area works on most displays from 15.6 inch (laptop) thru 27 inch PC monitors (as tested) and should have no issues on larger displays. Adding a part number and locations is very easy. 1. Enter a part number in the "Enter Part number/CMM Program Name" field and select "Add/Update". If the part number doesn't exist it will be added, if it exists it will be updated. Grid locations are not forced at this time, so make sure you add Grid locations, if not add them later and then it will update. 2. Enter grid locations in the "Locations (comma-separated)" field (See image Rayco Style 36x36 Grid - Fixture Location - Selection Shown.jpg) 2a. You can use as many grid locations as needed as long as they are comma-separated. 3. The grid will highlight the locations in BLUE and highlight the letter/numeric locations in RED. 4. You can remove part numbers by selecting the part number in the "Part Number/CMM Program Name" list and then selecting the "Remove" button.. (Currently one removal at a time). 5. You can export the list in a ".json" format (basically a text file. 6. You can import the list in any installation location with a known json file. 7. For that savvy programmer, the .json file can be edited manually as well and then imported. The export/Import location is tied to the PC user, example: "C:\Users\<user name>\Documents\CMM1InchFixtureGridLayout". 8. Upon closing the app, you will be prompted to save the current part list, Yes, No or Cancel. Yes will save the list (User interaction required), No, (app simply closes) or Cancel (App stays open). Feedback from users of the forum is always accepted. If anyone wants a copy of the Visual Studio Solution, message me with the request and your email address. The conversion to a Metric grid would be pretty easy in "FixtureBoardControl.vb" code. CMm 1 inch Fixture Gridf layout_publish.7z

Good morning, I have a new problem occurring on our spectrum III, running Calypso 2024 with service pack 5. Starting yesterday, when an automatic probe change occurs, user driven or in a CNC run, it will swap probes, and update in the the automatic stylus change window. But it will not change the probe that it thinks its using, the auto change window will show the correct info, but everywhere else will show the previous probe still installed, like the probe system qualification window. The system will continue to run, as if the probe change occurred, but using the wrong probe data. For example, if a program is using a 3mmx25mm probe, and then changes to a 1.5mmx50mm probe, the change will physically occur, and the CNC run will continue as if it has the new correct probe, but it will try and probe the next feature using the dimensions of the previous probe, meaning it will crash if the new probe is longer than the previous. If you do a manual probe change and tell it manually what probe it has, it will properly update, but this is the only way it will change. If I have the master probe in the machine, and do an auto change through every probe in the rack, it will do every change without issue, but the probe system window will always say master probe until I manually change it. Possibly unrelated, but my probes also no longer update the qualification date in the stylus system management window, but the date will update in the probing system qualification window. If i qualify a probe, the date in the stylus system management window will only show the last date qualified before these issue began. I'm hoping I might get some help here before I delete all the stylus systems and rebuild them, or put in a call to Zeiss, both of which will be annoying and time consuming, especially given that the CMM PC is not connected to the internet. Appreciate any help.

If you need for just a few points, then make those deviation flags, then make a point and for definition click that flag - it will create point from that flag. Now you can report it's XYZ

We are working with the free version of ZEISS Inspect. Is there a way to display the XYZ coordinates of the Surface comparison min or max with the free version? Because of this I can not Edit the Template. Thanks, Alain

@Norbert Bendl I am using BAT after reports are done and it moves this DFQ into correct folder. Perhaps this would be working way for author if it would make always a file in local drive, which would then BAT move even with folder creation.

Aha, schön da mal etwas mehr Klarheit zu haben. Für die Experimente, um das selber rauszufinden, fehlte mir leider die Zeit. Was ich allerdings suche, wäre eine Möglichkeit, den Pfad in der qdasconv.con nur zeitweise zu übergehen, ohne ihn dauerhaft rauszunehmen. Denn wir fahren mit dem Pfad aus der Config unsere Serienmessungen, und daran darf nichts verändert werden. Künftig wäre es aber von Vorteil, wenn wir auch mal temporär die obige Pfadeinstellung aktivieren und damit den Pfad in der Config kurzzeitig "ausschalten" könnten, um Messwerte für ein CAQ-System zu schreiben. Danach soll es aber alles wieder wie vorher sein. Das scheint leider nicht möglich zu sein.

Yes, magnification. oops

Thank you very much!

My argument that MMR/LMR is the simulation of a gauge I have only said to make clear what the motivation for a datum system under material requirements is. Of course this is only an illustration what is going on. But if you like the explanation the same result please have an look into the standard. See ASME Y14.5.1-2019 (only for planes, for width elements you have a similar definition there): "4.7.5 Datum Features of Size Referenced at MMB a) The candidate datum set of a cylinder is the set of axes of all datum feature simulator of MMB size that [enclose] {are enclosed within} the datum feature. For secondary or tertiary datum features, the simulators are constrained to be basically oriented and, if applicable, basically located to the higher precedence datum. [...]" This is what the software test. And in your case is seems to be the problem that their exists no valid candidate datum set. Yes I admit it can be confusing that the error message uses ISO vocabulary (the definition for the ISO standard is the same but the have other names for similar concepts), maybe we should respect the chosen standard for error message text.

In my opinion, if you like to simulate that you put the part on a surface plate then this plane should be the first datum. But nevertheless we could solve this problem for some cases. Therefore please check with ZEISS Inspect 2027 (when its released) if your problem is resolved and this error message is gone for good. Feedback on this matter is highly appreciated, so that we think about the next cases to be solved.

@Martin Jánský.2 Dann habe ich Matthias Frage falsch verstanden.🤔

Danke für die schnellen Antworten! 🙂 Vorrang hat aus meiner Erfahrung heraus immer die qdasconv. Man muss in der qdasconv den Speicherpfad aus kommentieren, dann wird vorrangig der Pfad aus Calypso genommen. Beim Speicherpfad für die Qdas darf keine Endung wie TXT oder so dahinter stehen. Im Grunde funktioniert das bei uns schon viele Jahre ganz gut. Man hat so den Vorteil für jedes Programm ganz individuell einen Speicherort für die Qdas Daten zu hinterlegen. Das einzige Problem was wir damit haben ist, das fast immer die erste Datei verschluckt wird. Ich hab das Gefühl das es mit dem Netzwerk und der Länge des Pfades zusammenhängt.

@Jörg Apfelbach You are making just a path for QDAS files - you can not alter file name here.

Hallo Matthias, wir haben auch keine Probleme, aber was mir bei deinem Eintrag auffällt, ist das am Ende deines Eintrags .txt fehlt. Bei uns sieht es so aus. Vielleicht hilft das dir. P.S. den Pfad musst du für deine Bedürfnisse anpassen. Neuer Pfad mit Messlisten Nummer erstellt 2024 "Q:\MESSRAUM\_qdas\Messprotokolle\"+strElement(3,".",dateInNumbers())+"\"+getRecordHead("u_Monat")+"\"+getRecordHead("u_Messliste")+"\"+getRecordHead("u_bearbeitungsmaschine")+"\"+getRecordHead("planid")+"_"+getRecordHead("u_Bemerkung")+"_"+getRecordHead("date")+"_"+getRecordHead("u_Schicht")+"_"+getRecordHead("u_pruefgrund")+"_Nr._"+getRecordHead("u_Auftragsnummer")+"\"+getRecordHead("u_teilebezeichnung")+"_"+getRecordHead("drawingno")+"_"+getRecordHead("time")+"_Teil_"+"_"+getRecordHead("partnbinc")+"_"+getRecordHead("vda_remark")+".pdf" ************************************************************************************************************************************************************ Messdaten abspeichern "D:\Mess-Daten\"+strElement(3,".",dateInNumbers())+"\"+getRecordHead("u_Monat")+"\"+getRecordHead("planid")+"_"+getRecordHead("measRun")+"_"+getRecordHead("u_Bemerkung")+"_"+getRecordHead("date")+"_"+getRecordHead("u_Schicht")+"_"+"_#_"+getRecordHead("u_bearbeitungsmaschine")+"_"+getRecordHead("u_pruefgrund")+"_Nr._"+getRecordHead("u_Auftragsnummer")+"\"+getRecordHead("planid")+"_"+getRecordHead("measRun")+"_"+getRecordHead("u_Bemerkung")+"_"+getRecordHead("time")+"_Teil_"+getRecordHead("u_Tischseite")+"_"+getRecordHead("u_Vorrichtungsnummer")+"_"+getRecordHead("partnbinc")+".zmp" **************************************************************************************************************************************************************