All Activity

Thank you Roy, I work with Meaghan and we are both trying to figure out why its not working. We already tried doing what you had suggested as that is the only way we know how to set re-qual. This used to work fine for us then one day it would not let some of our probes be set to requalify. We can do it on some and not others and that is the confusing part. I have touched off the master sphere using the re-qualification (I know in the screenshot it doesn't look like I did because I took this after) opened the qualification program we have, and selected the probe, still grayed out. This issue seems to only affect the RDS probes, as you can see our star probe will allow us to set it to requalification. The weird part is this is only affecting our ball 1 program. I am able to set the RDS and star probe to requalification on ball 2. So why is this not the case for ball 1?

@Jon Fair If he is trying to prove the CMM is repeatable, no to the casting. There's too much variability with raw parts. Use a more refined, known artifact like your training block. If he is looking at production measurement system capability, then let him use the castings. I'd do both, so you can show the variability that exists between them.

Have a new engineer here wanting to do a gage R&R on the cmm. Wants to do it on a raw casting. My opinion bad idea seeing as i check castings everyday. What is others opinion? Have the zeiss training block could do it on.

I don't think it would cost that much to have it look through the headerline and find the position of each wanted collumn. It takes me about 15 minutes writing and testing the code in PCM and it should take an experienced developer way less than that using a capable language.

it's not a bug it's a feature -- to buy more GPU ... j/k 🤣

Honestly the rotation works very similar to another metrology software I use. It isn't bad for me.

Moin! Viele Wege führen da nach Rom, man kann in PiWeb an eigene Bilder sowie auch abhängig vom hinterlegten Datensatz Merkmale anzeigen lassen. Ich mache das bei uns bei ganz vielen Teilen. Am elegantesten finde ich die interaktive CAD Ansicht, da muss man nur bei Positionen aufpassen, das der Vector stimmt. Was genau brauchst du den? Gruß, Matthias

What i found is only tangent line from two circles - so you would make intersections and ends of cylinders to make tangential line posible - then make end points on line. Now you will have 4 points, which can be selected and done plane from them.

To support this topic. Those old GOM webinars were quite useful, oriented/focused a lot on the technique (and less on the marketing and "exact-button-pressing-in-a-new-version-of-software"). I used to share them with my students as a nice external learning resource (that students like to watch, whatever on youtube is more interesting than in boring lectures). New Zeiss webinars are missing all that content. I also approached Zeiss support to get access to those webinars for educational purposes, but I never heard back Andrei

The issue is that the probes have not been qualified yet. I did qualify a few angles and they work in the list, but the ones that have never been qualified do not.

Ah makes sense, blinded by my own specific challenge. From calculated cylinders, which should be parallel, (as should supporting mesh) hence I tried cylinders! Would it not just do a best fit rather than curve the plane?

You can create tangent on circles, but for cylinders i affraid not. Cylinders may not have parallel axis so you would make curved plane if you insist on full tangent. Do you want that from mesh or calculated cylinders?

Hello all, Does anybody know a way to construct a plane that is tangent to x2 cylinders, like in the photo? Photo is close but no cigar, the plane is not touching the cylinders when zoomed in! Feel like it should be simple, maybe it’s me? Thanks in advanced

Hi Jeff, i'm also adjusting to the new CAD movement, but i believe we are having 2 systems now integrated. Please try the following: Define rotation point Set the point wherever you like and then "activate" the rotation point: It doesn't feel a 100% like the pre 2027 versions but to me it feels more familiar. Have a nice weekend everyone! Best Regards Marcel

Hello Edgars, sorry for the late reply. If you turn on the "additional report" you should also get every individual bore shown on the protocol: If you dont want to have the combined bore pattern plot on the protocol, i think you will have to create a generic PiWeb Template where you delete the marked rows in the "BorePattern.Bor (Detailed)" and adjust the size of the plot view itself: Which would be look like this: I hope this helps! Have a nice weekend! Best Regards Marcel

Can you post more info - like a sketch what you mean?

Yeah, there's definitely some wild rotation going on, compared to the behavior in the old versions. I'm having a heck of a time trying to rotate it how I want to lol

Marcel, I've had the same issue with multiple cad models. I'm guessing it's going to be hardware-related, but I will certainly open a ticket when I get a chance to.

Is there a way to assign a true position to a linear dimension in the 2026 inspect?

I just put in 2 Service request by Phone. that was two days ago. My machine has issues homing to where the alignments of every single prgram shift to the left..everytime after homing. So, i try not to shut it down now. I think it's the control box.

If you remove it and shake it, does it rattle? 😂 It only takes one bad hit to really crush the internal components of those things 🤷‍♂️

In the attached program, I created the datums, and the trihedron orientation is correct for each alignment, but when i try to change views from Z+ - Base Alignment to any other alignment, the screen flicks and it just shows the Base Alignment view. I created a whole new program from scratch and have the same issue. This doesn't happen on the other jobs I have programmed for some reason. Any help would be appreciated. 151-008785-0002 Rev. A OP1.zip

Is there a specific thing you recall I can ask them to look at to diagnose if this is the same hardware fail that you had? Seems like Zeiss gave us a bad RDS then considering that the first time this problem happened was 1 week after it got replaced. And a normal full machine calibration does not even detect the problem since the first instance of our issue was 1 day after calibration.

du kannst probieren, den folgenden Code für deinen Bedarf anzupassen und ihn in die "inspection_end_pcm.txt" packen. Dieser liest die Datei "fileIn" ein, setzt die Spalte "posHeaderIn" auf die Position "posHeaderOut" und gibt die Daten wieder in der Datei "fileOut" aus. Ich habe es bei mir nur an einer Besipiel-Datei getestet. posHeaderIn=5 // position in originary file posHeaderOut=2 // new position fileIn=directoryPath("results") + "\test_chr.txt" // input file fileOut=directoryPath("results") + "\test_out.txt" // output file if fileExists(fileOut)==true deleteFile(fileOut) endif //--------------------------------------------------------------------------------------------------------------------- defineFunctionStart("SortList") strSorted= "list(" for k=1 to subStr.size selectCase k case posHeaderIn strSorted= strSorted case posHeaderOut strSorted= strSorted + qm() + getParameterNamed(subStr,posHeaderIn)+ qm() + "," strSorted= strSorted + qm() + getParameterNamed(subStr,k)+ qm() + "," caseElse strSorted= strSorted + qm() + getParameterNamed(subStr,k)+ qm() + "," endSelect next k ANZ=len(strSorted) ANZ=ANZ-1 strSorted=mid(strSorted,1,ANZ) strSorted= strSorted + ")" strSorted=getParameterNamed(strSorted) defineFunctionEnd("strSorted") defineFunctionStart("WriteLine") outStr="" for k=1 to subStr.size outStr=outStr + chr(9) + getParameterNamed(subStr,k) next k outStr=outStr.killWhiteSpaces addToFile(fileOut,outStr) defineFunctionEnd("0") //--------------------------------------------------------------------------------------------------------------------- // header fileIn=fileIn.asFilename.contentsAsLines headerLine=getParameterNamed(fileIn,1) header = "list(" j=1 repeat // chr(9) ist ASCII-Code für Tab als Leerzeichen strCheck=strElement(j,chr(9),headerLine).trimBlanks if not(strCheck.isEmpty) header= header + qm() + strCheck + qm() + "," endif j=j+1 until strCheck.isEmpty==true // leerer Eintrag am Ende, der zu nil führt, entfernen ANZ=len(header) ANZ=ANZ-1 header=mid(header,1,ANZ) header= header + ")" header=getParameterNamed(header) subStr=header subStr=executeFunctionNamed("SortList") executeFunctionNamed("WriteLine") //--------------------------------------------------------------------------------------------------------------------- // values for i=2 to fileIn.size line1= getParameterNamed(fileIn,i) subStr = "list(" for j =1 to header.size // chr(9) ist ASCII-Code für Tab als Leerzeichen strCheck=strElement(j,chr(9),line1) subStr= subStr + qm() + strCheck + qm() + "," next j // leerer Eintrag am Ende, der zu nil führt, entfernen ANZ=len(subStr) ANZ=ANZ-1 subStr=mid(subStr,1,ANZ) subStr= subStr + ")" subStr=getParameterNamed(subStr) subStr=executeFunctionNamed("SortList") executeFunctionNamed("WriteLine") next i

Hi Richard, there was a small change to the functionality of login button necessary. Does the "ZEISS ID" button work for you? This button was the standard login behavior before the change. This is also no special employee page, just the "normal" ZEISS ID login, which shows an option for employees. Nanno