All Activity

Danke, funktioniert

valid points, @Tom Oakes There seems to be a lack of clarity into how constraints and size algorithms are applied in the new GD&T engine. My recent work assignments have me using "other" metrology software. I compliment those vendors for making it simple to switch between GD&T setups: literally a drop-down menu to change from ASME Y14.5-2009, Y14.-2018 or ISO.

Hello, I have 100 details one diameter (e.g.66+0.04). After measuring I need divide this details on 3 group: 1) 66.005..66.01;2) 66.01..66.016,3) 66.016..66.02).I made table of measuring value in PiWeb Designer and add condition for field measuring value, but I received only color group. I want make filter, and create 3 tables with different tolerance. Groups can be 3,4 or more.

Be careful with statements about how GD&T is "generally" applied. I work exclusively with cylinders. 15 years in this busy CMM room as the only programmer and I've seen maybe 100 parts come through (all were fixtures for our processes, not customer material) that would be appropriate to use a "plane-line-point" system. This only applies where a plane is the primary datum because it controls exactly 3 DOF. A cylinder in primary constrains 4 DOF so we'd use cylinder-plane-(some clocking datum: circle, line, etc) or cylinder-clock-point. Also - Adding datum shift where MMB is invoked after the fact is possible if and only if it is applied to both holes simultaneously. Same direction, same magnitude. You must not change the shift for individual FOS separately like you do with MMC. I agree that in this case it's totally possible; just making the distinction.

In addition to what others have said, Datum Shift is intended to apply to all holes of a pattern simultaneously. If one hole would "benefit" from shift but another would be pushed OOT by that shift, shift will not be applied. If, say, your basic bolt circle is oversized (Ø3.144 too large), but the circumferential locations are all correct, datum shift cannot improve your results. Likewise if the bolt circle is perfect, datum shift can attempt a rotation as allowed by feature tolerance but there may not be a datum shift that can bring all holes into tolerance if the angular location of one hole is too far from nominal. If your bolt circle is near perfect, and the angular spacing between holes is also really good, but the entire pattern is shifted to the datums in the same direction (translation and / or rotation), datum shift will improve results. I agree with Richard's observation that shift is applied when rotation / translation allowance boxes are unchecked when MMB is applied. However I've not found an appropriate use of these checkboxes. If I need a special rotation but don't use it, the rotation checkbox will not rotate to that special and positions still report big numbers.

Tom did you come up with anything regarding these additional characteristics? I never had formal PiWeb training. While I'm pretty good at figuring things out, PiWeb is the most obtuse thing I've had to work with.

I've just started working with Calypso 2024. Using the GD&T position with MMC invoked, my report now shows the size of every hole used to calculate the bonus tolerance. I'd like to remove this from the report, as the same hole sizes show up once in the PLTZF, once in the FLTZF, and once where I just called for the diameter. My part has 100 holes so eliminating these redundancies will remove 200 lines from the report. I'm just poking around now to see if I can find a setting somewhere but any help would be appreciated.

update... thanks for the information. i went and gave full access to the folder, then used PCM to rename the folder at the start of every program, then change it back at the end of every program... this way in the future, i could had conditions to it if i had to use excel for a specific program (don't know if i would since going to piweb anyways)

Without seeing everything, I'll take a guess. I assume your rack is at the extreme Y+ end of the table, though mine run along the X+ side (huge machines). Triple check that your approach parameters make sense. Open the automatic stylus change rack, select "changer", and approach parameters. Our biggest mysteries occur when an operator gets curious and makes changes without communicating. Try a full shutdown if you guys don't do it all the time. Perhaps the homing run will tidy up the movement to and from. Otherwise, I'd put in a ticket. I've had the same Accura going into the same 25 pockets since 2008. There's no wear or strange behavior that isn't found and corrected during annual calibrations.

yes.. we do not want to use excel at all... just the .txt files.. they are used in an external program company wide... several different machines, hand held devices, and manually input all use this format so i have to have it on, just not the actual excel file... I tried using some of these new excel commands with no luck.

I advise you contact your local SW support team. SQL installations/run time issues are very difficult to diagnose (there are around 10-11 common IT related settings that can cause problems - many more uncommon ones). I will re-iterate, again, that this is why SW Support recommends ZEISS sourced workstations. The hardware and OS image they are provided with is significantly more reliable related to installation and run-time problems alone. In the US, more than 92% of the installation and run-time problems reported are on non-ZEISS sourced PCs (knowing this, it seems silly to save $300 by having your IT guy source one elsewhere). Save yourself the preventable down-time. It is expensive. For those using their own sourced workstations/PCs, here are the Windows related problems you may experience with installing CALYPSO. I'll try to point out some places to start (the ZEISS Portal Knowledge Base will help with all of these too) The big ones: Install: Inadequate installation privileges - when you install, right-click on setup file and run as administrator. This helps in some situations, otherwise, get with IT. Legacy registry values that require being removed. Error logs will point to this. Invalid sector sizes on SSDs (Windows will lie to you if you dont have admin credentials when you check, it emulates 512kb sector) Pending Reboot required (this is the MOST common by far) - any changes to SQL requires a reboot to implement. Always reboot before and after install. OLE drivers remaining from previous installs Run-time: SQL EXPRESS 2022 set to "Delayed Start" is default - resolvable if needed but just wait 2-3 minutes after reboot and this goes away PC name greater than 15 characters (prevents MSMQ services from starting > prevents SQL services from starting) SQL/SDCO Services not started - Condition of the two above or various other problems Ports 1433 or 1434 blocked Improper migration of 'config' directory from a PC/machine tab move. SQL MUST BE OFF to migrate a config. If you see a "2 files were not copied" message, that config is going to fail 100% of the time. Install - unrelated to SQL but with CALYPSO itself and important: Due to 256 character limit on Windows files, Put the install media at root level directory (C:\temp\) or similar. There are very long file paths, specifically Linescan driver files for instance, that will fail install if you put the install media in longer folder paths like C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\inspections\ZEISS CALYPSO 2025 full version incl sp (8.0.08)\ - (just as an example) INSTALL THE "FULL VERSION W SERVICE PACK"! The Service Packs are complete installs. No need to install the "base version" any longer if a Service Pack has been released. If you are experiencing errors or problems you believe are not as-designed performance, make sure you are on the most current Service Pack for that version of CALYPSO before reporting to support. (I promise, this will be the first thing they ask you. Next will be if you've rebooted).

I'll have to check but I believe its all-old files. The "excel_report" files that are all dated 2/20/2013 and the ReportINI dated 4/26/2012. They should be at the same file path. We just upgraded in early September, and I backed up all that stuff as you should. Dropped the old stuff where it should go. The report has all nominals and tolerances, just no actuals. Maybe I will contact Zeiss and see what they say. Lincoln

I saw on forum they renamed executable file for excel creation to disable this. But it will disable for every program.

Recently updated to 2025. We turned on the table files for external reasons, but now with 2025 it is trying to save as a excel file also... not just the chr.txt,fet.txt, and hdr.txt files. I use the pcm code: settingPut("resultToTableFile",true) how do i get it not to try and save a report to an excel file now?

The new GD&T engine will correct for non normal space axis. You only need to do a special rotation if you want the nominals to match your drawing as shown.

Oh boy That's going to hurt...... We just had our machine serviced in September and haven't had any hard crashes from that point on. Few bumps here n there but damn. It wouldn't pick up an XTR adapter plate after power restart either. Had change manually to get it to accept the plate. Would anyone know if they have to fly back out to install a new sensor head and calibrate? @Chad Watton I think I saw you mention this in another thread. I tried it out and didn't seem to change much. Maybe its too late... Based off everyone else's experience with this, how much time do you think i have left?

Yeah, @Kyle Johnson, ACRONIS definitely is not backing up regularly on our O-inspect or our Contura, each only has a backup from the first install + two more shortly after. When I use the ACRONIS help pages in the knowledge base it states to use the "Acronis Cyber Backup" program, but both of ours for example only have the "Acronis Cyber Protect Monitor" which opens up a small window with not much to do stating there is no scheduled backup. Curious if it is just an older version.. if you try to follow anything it leads you to a "Cyper Protect Web Console" that we don't have login details for. I tried playing around for a bit but it is a bit more work than its worth for now and will look into it in the future. We also just had a Duramax install and we never heard anything about Acronis so if there is any old or new additional literature outside of the knowledge base that would be helpful, although for our 2022 Contura Install I was around for it was similarly not mentioned and I have always wondered what Acronis was on the PC.

I have 4 probe holders on our Micura. Within the last week and a half we are experiencing an error and the drives kicking off when during a program it goes to change a stylus. It stops at the very quick slight pause before it enters the probe holder. It will stop at the same spot at any of the 4 probe holders. It does not happen all the time, but we've seen up to 4 or 5 times in an 8 hour shift. It also doesn't happen only when a program is running. It will happen occasionally as well when I perform and automatic stylus change. This is the error we're getting. I thought maybe over time since it always pauses at this location in the cycle when it picks up or drops off a stylus maybe it created somewhat of a "wear spot". I have cleaned the granite and also moved the stylus rack about 1/4 inch forward and reset the holder locations and it is still happening. Is there anything else I can try or look into?

Arrived this morning to find a similar issue with our O-inspect 543... inspectors mentioned issues with the CMM and I found that it was starting a new connection with the SIMULATION configuration and the O-Inspect configuration was nowhere to be found. Checked Acronis first as @Kyle Johnson suggested and found last backup from.. ~2020.. about when we received the machine so that must have been disabled... Thankfully, using the thread @Jason Barry suggested, https://portal.zeiss.com/knowledge-base?id=483015, I was able to simply add the "O-Inspect" config back as the folder was still present on the computer and everything *appeared* to be restored. It will be a mystery as to what caused this, I can only speculate that someone was tinkering around with what they shouldn't (Or IT?) however I should note though that the C drive was also full... (I am still not sure how/am working that one out) so maybe that was the most likely cause. I went and cleared some low-hanging fruit of data that could be deleted ~about 40gb worth so no longer at capacity. I was receiving some calypso messages about no room on the drive before this. After doing this- I was still finding issues as the automatic stylus changer was working but I was getting this error message in the console: I was able to find what I believe was the fix below by manually loading every stylus we use from the racks manually and then using the Teach ID in the stylus system management. After doing so the automatic stylus changer now works and I do not get the error message anymore. I had a console output for each line assigning the stylus ID. Afterwards I was able to run a program that utilized multiple styli again without issue, so I believe my problem is resolved. Thank you all above for the thread. I hope the Teach ID was valid to do and isn't bad advice. Time to figure out why ACRONIS was backing up. 🙂

Just upgraded to '24. Now, my home screen isn't showing any recent programs. How do I turn it on?

@Shawn Hillegas If you CTRL ALT DEL after hitting start, what do your computer resources look like? Is the CPU/RAM at 100%?

@Paul Boldea@Josh Dalessandro It's been a long time since I encountered this, but I believe the fix was to uninstall (from add/remove programs) any and all versions of Microsoft SQL server on the machine, and then let Calypso try to install SQL via the installer.

That thing was getting jiggy with it 🙂

Yes but I've also tried running the same program(s) locally as well with the same issue.

Hi Štefan, there is a course for "Digital Assembly in Car Body Manufacturing" available and "Quality Control in Casting Processes" also has a section on this. This Techguide article covers the basics of interpart alignments: ZEISS Quality Tech Guide It is also possible to analyze scanned parts in the real assembly: Nanno