All Activity

what kind of symmetry plane are you using? i dont think the one under construction would work, believe you would have to use the one under feature and recall feature points from both sides of the slot

Another thing to consider is if you're using CAA with the XXT or not. CAA will save you calibration time if you have a bunch of angles to calibrate, but you'll lose some accuracy as opposed to calibrating each angle individually.

@Richard Stanich Thank you for your input. The cost of setup was getting out of hand when I first started creating probes for the jobs, and time consuming. I ran into issues swapping the two heads and ended up erasing all the probe configuration. I will continue with the RDS configuration for now. I believe in the future I will have the opportunity to utilize the XTR Gold with longer parts or tighter tolerances. Best regards

ZEISS INSPECT Hardware Service are running perfectly by design. I can get to it with port :39025 with 127.0.0.1:39025 and after I change it to 192.168.4.1:39025. and everytime I'm getting this (The connection is blocked.

Looking to upgrade to Calypso 2025 (8.0.1203) with our Win11 updates. I have installed it on an offline laptop to get familiar with it and see how it imports programs. The drawback is no output for the CAD Presentation commands on the evaluation side. I do remember hearing at the user group meeting this being an issue. Is there any resolution we know of? I scoured the forum a bit before asking, but nothing too specific about this topic that I was able to find with my limited time. I did read a lot of discouragement of v.2025 until the lates patches, but hoped since 2026 is coming or is out that this wouldn't still be an issue. What is a good alternate solution to this method in the new versions? I apologize if this is a beaten-to-death topic but I seldom use the forums.

I forgot about my own thread. 😜 The nominals of the X coordinates make Datum C some sort of Symmetry. The X coordinates do not line up if I take only that one surface. I understand what Richard is saying about how to evaluate Datum B. I would prefer to set up some sort of iterative alignment to loop these, and from what I understand that is only possible if all points are used as point sets. Any way to get around that? And how to evaluate C, since it is a symmetry? Take lines and hope for the best?

I am trying to get the position to AB and the position to A. I cannot pull up simultaneous requirement in my position box by using a symmetry plane to the slots. AI keeps telling me to use a slot to do this and that I should be using both slots. How can I do this? I'm new to this version of calypso so the new GDT position is a bit different. Need help. Thanks

I am experiencing this on v2022. I just reload the multi report. What I also have and is more frustrating, is PiWeb report will come up blank until I use F7.

Does Observer require a dashboard, third-party software? I pull the ProgramDurationRecord.xml file into excel and chart it, it's a PITA.

Beware of the Cobra Effect. If you don't know what that is then look it up. When I solely tracked number of parts inspected, I found that 2nd shift operators would just run the quickest/easiest parts, thereby inflating their numbers, and leave 3rd shift to run the more difficult/longer run time parts.

I have both sensors as well; I use both all the time. We mainly utilize the XXT sensor to save money on the cost of XTR builds. Example, prior to getting the XXT sensor, we have two jobs that require a total of 18 different probes due to compound angled features. With 28 builds that is 28 Adaptors at $1050.00 each then add the extensions, adaptors (angles), styli etc. With the RDS where I converted one job to the XXT sensor we use 7 of 9 builds permanently on the rack. The cost of the 9 builds for the XXT was about $3,050.00 for the adaptors then add extensions and styli (We bought a bundle of adaptors, a count of 10 adaptors). Typically, the XXT adaptors are $450 each. The cost savings is great; the accuracy is great. Less probe management as well, where we can now disassemble some XTR builds and use for any project that comes in where the XTR would be useful. Using data when the part was on the XTR sensor (PiWeb report) and after converting to the XXT sensor, we saw no discernable change in values that would warrant any concern.

@Mason Warmuth Bring up Task Manager and see if ZEISS_INSPECT_HardwareServer and ZEISS_INSPECT_HardwareService are running.

I would suggest to place a keyword into that element so you can then make for cycle where you scan all elements for your keyword ( it will fail, when there is no such keyword, so place it into TRY/EXCEPT, with "pass" in exception ) Now you don't need to manually place names into condition

Now i have 15:33 - wait until i get into work and i'll send what to do. I think you have to fill IP from your ATOS ( 192.168.4.201 ) into field where is your mouse pointer on last image. But i will have a verified answer tommorow. You can also try what button "Correct System" will do.

Thanks Richard.....So, I wouldn't have to use a best fit pattern for the two slots? Maybe I'm over thinking it, but I thought there was more to it than that. In the end isn't it just perpendicularity to A than? The location and rotation get locked in with AB and the orientation gets locked in when we use just A. Is that correct?

Maybe it's correct - depending how he likes my answer 😂

Due to "green" color of a surface i presume you are doing it on wrong face - in other words - on your actuals there is no surface ( it should be grey ) - green means surface viewed from inside of a material. If your scan is correct, then you have to select correct surface on model ( that side which is not viewable now ) Or your scan is not correct - missing thickness of material on actuals ( you have only a film and not thick material ) or your scan is from other machine, then you have to invert nominals.

Hi everyone, I have a contura with a Vast XXT RDS head and Vast XTR Gold. I mostly use the XXT as it provides more angle rotation and less probe setup time. I believe the XTR Gold provides more accuracy and maybe uses less travel on the machine. I have been able to rely on the xxt data using the filters and outliers. I wanted to know from your experience which one would you use? Currently the XTR Gold is not being used and is mainly collecting dust. Thank you for your input.

Bruce, I am not sure that is the problem either, because I do not get the message when we do a manual tool change.

@Luis Lozano Also there is CMM Observer, which appears to be an out of the box ready software that does what you need. I have not used it, but it seems to be fairly straight forward. Knowledge Base link https://portal.zeiss.com/knowledge-base?id=2778549

Thanks. I do have a PCM license on only one of the CMM's. I'll give it try. Thanks!

@Luis Lozano Yes, I have done this in the past. First question - Do you have PCM? If you have PCM, it is very easy to write the needed information to a text file for manipulation outside of Calypso. Use "getRecordHead(insertVariableHere)" to log program name, operator, time, and measurementDuration. Then use Task Scheduler and a PowerShell script to create a daily report (HTML is best) to automatically be sent to everyone's inbox. You will be management's hero! (no pay increase of course 🤣)

Maybe you could check writes to C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\basesystems with some script?

Got an interesting question. I have set up 2 CMM's to run on AutoRun. I am trying to see if there is a way to gather how much a CMM has run. Is there an internal "counter" folder? Don't care about what part it ran, nor any Piweb data. Just simple....amount of runs per day, per week, etc. If I can see the data, then I can sort. By date. Example. 1st shift ran cmm(s) 232 times. 2nd shift ran cmm(s) 150 times. 3rd shift ran cmm(s) 80 times. Its a project requested by management . They basically want to see the amount of output per shift. Yes, I do have a "results" folder, but i don't trust the output. Being that if the incremental part number is not changed it will simply copy over the past result. I can count the number of printouts per day on the printer but I'd have to literally be here all 4 shifts. The request is for 3 months of data. I can easily estimate, but looking to see if there is actually a "counter" internally. I'm sure there is, as i have seen the folder that defines number of hard hits/crashes. I'm just not sure it is accessible or recommended to casual operators. THANKS

The login is working again as usual. Thank you for resolving the issue so quickly.