All Activity
- Today
-
[Mi...] joined the community -
[xi...] joined the community -
[Al...] joined the community -
[Al...] joined the community -
[Mi...] joined the community -
[Od...] joined the community -
[Gi...] joined the community -
Hallo Community, vielleicht könnt ihr uns weiterhelfen. In der Vergangenheit wurden hier immer wieder gute Lösungsansätze und hilfreiche Tipps vorgeschlagen, deshalb möchten wir unser Problem gerne mit euch teilen. AutoRun zeigt CAD-Modell des vorherigen (wir vermuten es) Messprogramms weiterhin an (seit CALYPSO 8.0) Bei unseren Wellen- und Verdichterrad-Messprogrammen werden je nach Position unterschiedliche CAD-Modelle geladen, um eine optimale Darstellung der zu messenden Kurven zu ermöglichen. Seit CALYPSO 8.0 tritt folgendes Phänomen auf: Beim Ablauf über die AutoRun-Oberfläche scheint das CAD-Modell des zuletzt ausgeführten Messprogramms im nachfolgenden Messprogramm weiterhin angezeigt bzw. eingeblendet zu werden. Das Verhalten tritt ausschliesslich im AutoRun-Betrieb auf. Wird derselbe Prüfplan direkt in CALYPSO geöffnet und ausgeführt, ist das Problem nicht sichtbar. In der Hierarchieansicht sind keine zusätzlichen CAD-Modelle erkennbar. Die Messung selbst läuft korrekt, betroffen scheint lediglich die Darstellung zu sein. Das Problem tritt lediglich sporadisch auf und lässt sich nicht gezielt bei jedem Durchlauf reproduzieren. Die Häufigkeit scheint zufällig zu sein. Bisher getestet: CALYPSO 8.0.08 CALYPSO 8.0.12 CALYPSO 8.0.1204 CALYPSO 8.0.1205 Das Verhalten ist in allen genannten Versionen reproduzierbar. Unter CALYPSO 7.0 trat dieses Problem nicht auf. Hat jemand ähnliche Erfahrungen gemacht oder eine Idee, wodurch dieses Verhalten verursacht werden könnte? Gibt es eventuell bekannte Änderungen im CAD-Handling oder in AutoRun seit Version 8.0? // Befehl für CAD Loeschen und Richtige Pos/Rub einlesen clearCAD() CADFile= getActualInspectionDir()+"\"+getRecordHead("u_115material")+getRecordHead("u_120pos") + ".sab" if fileExists(CADFile) == true loadCADFile(CADFile) else message(getRecordHead("u_115material")+getRecordHead("u_120pos") + ".sab" + " nicht gefunden") cncBreak() endif Zur Veranschaulichung haben wir einige Screenshots beigefügt. Zeiss-Ticket wir heute auch noch erstellt. Vielen Dank im Voraus für eure Unterstützung! Viele Grüsse
-
Thank you @Dustin Grainger, I have never tried anything with macros before, so this was a good learning opportunity. I was able to figure out the macro, and it worked how I wanted it to. Edgar, thank you for the suggestion. I do use that feature sometimes because it is so convenient, though you lose the functionality of having sub clearance groups for each bore. All in all, it's still a very good tool.
-
I thought I tried that but I will try again... Thank you...
-
[Kr...] joined the community -
[No...] joined the community -
[Be...] joined the community -
[Na...] started following Automating surface curve creation from pixel coordinates in TRITOP
-
Automating surface curve creation from pixel coordinates in TRITOP
[Na...] replied to [Se...] 's topic in Customizations & App Development
Hi Sean, for photogrammetry, there is a build in function to create points from image: ZEISS Quality Tech Guide The homologous point needs to be clicked at least in two images to create an element. This point could be used for the construction of a curve. Interactively clicking the points -> create curve from these points -> created projected curve (project on mesh) resulted in a surface curve from clicked points in the image mapping of the photogrammetry. This can be recorded in the App editor. For ATOS measurements we have an example in the documentation zeiss-inspect-app-examples/AppExamples/misc/PointPixelTransformations/doc/Documentation.md at main · ZEISS/zeiss-inspect-app-examples · GitHub to get points from pixels and vice versa. Maybe there is also another function available depending on the application behind this, if you want to share it? Nanno -
Sended PM with a link
-
You can divide your text by a divider - it should be in string section. It will give you a list, from which you can extract N-th item. Function "Trim" will remove your whitespaces if you have them at separators So here is a sample: String operations -> Split string by separator List operations -> N-th item ( first item starting by "0" ) Here is a sample code: Result: "Your"
- Yesterday
-
I appreciate the feedback. Regarding the accuracy that is one of the main reason's I'd like a trial version. Whether it is through trial or purchase I'd like to run a MSA type 1 study with probing mode active vs default. If the accuracy is way off or if the time savings is too low, we wouldn't use it. $4,000 isn't really something I want to spend just to find out right away that it isn't going to work for us.
-
From what I can find in the Calypso manuals it doesn't explicitly state it is compatible with a XTR gold sensor. However, our regional rep who handles our SMAs and calibrations said it was compatible when I asked if it was. We have two duramax's XXTs as well, but the XTR is so much slower than the XXT with discrete probing that my hope/goal is to at least bring the CMM in line with our Duramax in terms of speed on discrete points...
-
I have a string that has 5 elements separated by a "|". I am trying to split this up and have 5 text boxes to put them into to format (make it look pretty) on the report instead of trying to do it with PCM in calypso.... basically a header variable in 5 chunks separated by a "|" and want to have 5 boxes to put each chuck into it. I have search but cant find this topic (maybe i missed it). It would be easier if PiWeb had a strElement() like PCM......
-
Are you using an L shaped probe?
-
-
@Lukáš Němeček, although Calypso contains some of the most effective geometric functions available, GUI modernization and improvement have been utterly lacking in this software for years. However, if you peek at the requested improvements on "My Voice," the majority of the requests relate to GUI. There's a disconnect here that I hope Zeiss notices. Competitor software such as QVI's Zone3 does better in this respect.
-
This may help you, https://portal.zeiss.com/knowledge-base?id=523014
-
Martin Can you upload that to a drive? Google drive you mean I assume? If you can that would be great. I appreciate you very much!
-
Zak I don't think I have a SMA. Might have to go with Martin on this one.
-
Are you using a manual system (ATOS not moved by robot) or a scanbox? The workflow is described here for a scanbox: ZEISS Quality Tech Guide After the import of the reference points as 'pre-measured reference points', make sure to set the measurement dependency of your ATOS measurement series to the imported points. There was a discussion some time ago about photogrammetry and its benefits:
-
Hello everyone, I've tried to find information about this on the Knowledge Base or this forum and haven't found it, though I apologize if this has been asked before. I have a part that looks sort of like the barrel of a revolver. In each bore there is the bore itself, along with a kidney shaped slot at the bottom. Since it is all in the same bore, I created a sub clearance group that they all use, and this works as I expected; the stylus moves from feature to feature without having to fully retract out of the bore. However, things get tricky when I want to apply a pattern to these features since I have 9 bores. I am finding that no matter what I try, the navigation will always measure FeatureA(1), then FeatureA(2) and so on instead of measuring FeatureA(1), FeatureB(1), FeatureC(1), and so on. This takes a lot of extra time since the stylus is constantly jumping from bore to bore. My ideas are: Applying the pattern with a regular sub clearance group. This causes the probe to move through the part. Applying the pattern with a sub clearance group that has the "CNC Loops/Macro-Safety Group" box checked. This solves the issue of going through the part, but it is still jumping around, essentially making the clearance group irrelevant as it behaves the same as just the regular CP +Z. I feel that there is more to this feature that I'm not getting. I could try to measure all the slot features as a curve and extract the points into features later, but that sounds like a nightmare. And I wouldn't be able to measure the cylinder as part of the curve. The closest thing I can think of is to go to Plan->Navigation->Sort features for optimal navigation, which breaks up the pattern and solves the issue of jumping around the part, but it would still need to retract all the way out of the bore for each feature to avoid driving through the part. I have a PCM license but no experience in using it. Is there a way to do this without PCM? Am I trying to have my cake and eat it too? I appreciate the help.
-
Good morning Gregory, I'm not sure your SMA status, but if you have an active one with us, email cic.metrology.us@zeiss.com along with your serial number and your request and we can provide you the installation media.
-
For a little more detail, the basic shape is a cube with many same-sized holes machined parallel to axes created from opposite corners of the cube. All of these holes exhibit the same odd shaped data set. With the exception of the good form, I believe the stylus is shanking. These results lead me to believe there is either an issue during the machining or the base alignment. The measurement plan is from the customer and the results from a part they machined on their machine. I just need to be sure before I tell the customer.
-
I have it - Calypso 2018 full 6.6 + Patch 6.6.1202 But it's over 4GB - i would need to bring my big flash, copy it and upload it to my gdrive - or how you want it? I have some sort of 2017/2018/2019/2021/2023/2024 😄
-
@Chad Watton I remember many years ago that masking was tied solely to the first .25 seconds of the beginning of a scan, and it still is when scanning less than 360°. So, when you scanned 380° on a circle, the masked points might only be a portion of the 20° over-scan relative to the scanning speed. Then, Calypso changed to masking whatever the over-scan amount was. My assumption is that even though they are scanning 750°, the resulting circle is only using the data from the last 360° of the scan.
-
Looking for a copy of Calypso 6.6. I bought a machine with Calypso 2016 on it and want to upgrade to 2018. I have a license for it since I upgraded to 2025 recently. My flash drive that 6.6 came on is corrupted and I want to load it on a new computer. The portal only goes back to the 2020 version. Anyone?
-
-
How can I mask points of a freeform surface?
[No...] replied to [No...] 's topic in Curve & freeform
Thanks Martin, but I ended up recalling the points to a copy of the FF and masking the area by placing four selection boxes around it. Very clumsy method, but it worked. -
How can I mask points of a freeform surface?
[Ma...] replied to [No...] 's topic in Curve & freeform
Since i have done similar things and FF does not allow masking points i would go with that curve option. For correct creation of a curve you have to have no measured points on recalled feature. So either remove measured data from feature or just copy it and do recalled curve from that copy. Now check vectors or invert them and recall measured data into it. Do masking in evaluation tab and use that copied ff to recall filtered measured points from curve. Perhaps this easy way should be sufficient. If i need to have correct curve, then i do next steps: after recalculating first curve - it will create it's spline go to element creation window and switch to 2nd window from selection select "From curve" and select that spline - it will allow you to control distance of points along curve's spline and also exactly on CAD model. This is needed when you have bigger distance of points in curve and spline is not following curvature of a model ( air scanning ) If you need i can make some screenshots
