All Activity

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

It looks like the GPU requirements increased with this release. On 2025 the CAD would be smooth on any potato PC. I've installed 2027 on a PC with ancient Quadro K2000 and its noticeably slow with GPU use hitting 90% when rotating the model. The 2025 on the same PC - the card is not even breaking a sweat. Then, I've tested 2027 on slightly younger P2200 - the CAD was smooth with GPU use at 30%. Just told my IT guy he needs to buy 4 cards 😉

try it

Thank you Edgar!

I keep getting directed to what appears to be a Zeiss employee login page with my normal link: https://qualityforum.zeiss.com/forum I had to find a back way in today. Edit: And the site won't remember my login.

We are happy to announce that ZEISS INSPECT 2027 has been released. See ZEISS INSPECT 2027 App Development Documentation and What’s New.

Hello Zachary, i've been trying to reproduce this problem but i cant with several different CAD models. Do you have this issue with every CAD model or just this one in particular? If you could open a Software Support Ticket with your local Zeiss Support and tell them to forward it to the 2nd level we could look into it with development. Best Regards Marcel

How about trying "List Qualification"?

So I needed to delete one probe angle off the list and accidently deleted the whole thing. I have recreated the probe. I recreated all the individual angles and such, but I am going back through and calibrating them. It is taking too long. I only know how to calibrate angles one at a time. I usually use CAA probing in the area I work in and was helping out and ... messed up big time. I need to be able to program a CNC calibration for a probe that has never been calibrated at that angle. I can't seem to figure out how to do that. I am not certain I could even if the probe was just needing a recalibration. Any shortcuts?

Something seems fundamentally different about the interaction of the mouse cursor to the CAD window. I *love* the new CAD cube and the ability to rotate 90° by clicking on it. This was so overdue. However, it seems like there may have been other unintended/untested behaviors related to CAD interaction, as reported by several users in this post.

I had this happen to me. They were able to run a RDS check on it to confirm that there was an issue. They replaced the RDS. Mine was pretty severe though. At times you could visually see how far off it was, and then yes times it was off enough that either it crashed or gave crazy results.

I am having issues with one of our RDS heads. Basically at certain sequence of angle rotations it will cause the head to be so far off it is missing features, i.e. .040+inch. I set up a 1-2-3 block on the machine and measured the corner of it with a plane on the top, front and side, starting at A90, B0, which I set as my zero point. Then rotating the rds by increments on A, it will fail at certain ones. It only seems to do it at arbitrary sequences. Note that I have it going from A90, to A180 at the top (was running in "From characteristic list" order). If I run that same program with A180 after A165, then that angle doesnt fail any more. I have a ticket in with Zeiss for this since we had this issue before, but then when the tech arrived, I couldn't replicate it any more (I think IRC cal was done first thing before I could try to demonstrate it which may have fixed the issue for a time but now its back). But I was wondering if anyone has seen a problem like this before.

I used space points individually and verified the x y z values and vectors. I created the plane from the CAD, Then recalled feature points, unchecked the recalculate geometry button so I took the nominals from the CAD. This has worked for me. I am not sure if it is incorrect in some way, but thats what has worked for me.

Dang, yeah I'm trying to set a plane with points, so I can't use anything but the points method in the feature window. I'm basically having to find a spot that works, click all of my points in the same spot, and then just set them manually with X/Y values. I was hoping to find out what's causing the issue or if there's enough other people having the same issue that maybe a fix is coming.

I had this happen recently, and just used space points instead of points

C:\Program Files (x86)\Zeiss\CALYPSO 7.6\bin\PiWebReporting\defaults C:\Program Files (x86)\Zeiss\CALYPSO 7.6\bin\PiWebReporting\defaults\StatusImages I didn't play around with this, just found them when I was learning to customize our reports.

I tried these both and they each worked. I'm going to use point-tangent for this application. Thanks for the suggestions!

Unless the report is setup with Dynamic Images, the Image tool stores the image directly into the report, so you'd have to grayscale that image manually, and then reload it into the report.

That's why i proposed to make intersection of groove circle with groove central circle like this

Can you point me in the folder direction of these images for PiWeb?

When I tried circle to circle, it was tangent to both circles.

We have an offline seat, but I still can't get it to work properly. I have spent hours on the problem. I made a lot of headway when I logged in as master. That solved a huge list of issues.