All Activity

For that it should give you only one axis ( not sure which one in this case ) but the other axis should be fine, because it should rotate measured feature to nominal value. So if you have measured feature to be [X+20] and Y-20 ( X is base dimension ) then it should rotate to have X exactly X+20, then Y won't be exact -20

Well there is always the trashcan for that, and at least Free-form has a working Reset. Curves on the other hand are a different story, the Reset does not work for any type of nominal manipulation.

A very complex Freeform surface and my finger hit accidently hit delete. A lot of work down the drain.

So if we did use circles would only get an X Value for TP of B1 back to AC? Two intersecting planes would only get an X value right?

When I export points from a point cloud, the results are always relative to the base alignment, even though I have my settings as shown below. Am I missing a setting somewhere else? When I export regular features manually, it is relative to the active alignment, just not point clouds. Separate question, is it possible to export points in inches? Calypso 2022, latest service pack Thanks!

Make it behave like Zeiss Inspect and we will all be happy. Danke.

agree, any software especially where you are editing and creating important things should clearly have a robust undo function.

I'll see what I can find, so if plane H is active you want to use #3 & #5 stylus ? I would initially think, there should be an easier way based on a Part# or Part Config parameter instead. However seeing the lengths you've went to on other PCM programs, we'll give you the benefit of the doubt. 🙂 it should be something to the effect of (not actual commands just theorizing) : myFeat="Plane H" if activeFeat=myFeat then doSomething endif

It's used for a measurement. I run from Features, not Characteristics. Features are generally run in the order they are created (placed in the feature list) unless a feature has an alignment other than base alignment then the alignment related features will be run prior to the feature in the list order. It is a feature tied to a dimension or PCM in dimensions and or other features, not used in any alignments.

PowerShell script to convert (Save as) an open excel file to CSV. (AI generated) This should work at the end of your CMM program. Create a batch file named "inspection_end.bat" @echo off REM Run PowerShell script from the same folder powershell -ExecutionPolicy Bypass -File "%~dp0inspection_end.ps1" exit /b Create a ps1 file (PowerShell) named "inspection_end.ps1". Use the code below. param( [Parameter(Mandatory = $true)] [string]$OutputCsvPath, [string]$WorksheetName ) # Excel constants $xlCSVUTF8 = 62 # CSV UTF-8 (Excel 2016+) $xlWorksheet = -4167 try { # Attach to running Excel $excel = [Runtime.InteropServices.Marshal]::GetActiveObject("Excel.Application") if (-not $excel) { throw "Excel is not running." } $workbook = $excel.ActiveWorkbook if (-not $workbook) { throw "No active workbook." } # Select worksheet if specified if ($WorksheetName) { $sheet = $workbook.Worksheets.Item($WorksheetName) if ($sheet.Type -ne $xlWorksheet) { throw "Specified sheet is not a worksheet." } $sheet.Activate() | Out-Null } # Suppress prompts $excel.DisplayAlerts = $false # Save As CSV (active sheet only) $workbook.SaveAs($OutputCsvPath, $xlCSVUTF8) Write-Host "Saved as CSV:`n$OutputCsvPath" } catch { Write-Error $_.Exception.Message } finally { if ($excel) { $excel.DisplayAlerts = $true } # Release COM objects foreach ($obj in @($sheet, $workbook, $excel)) { if ($obj -and [System.Runtime.InteropServices.Marshal]::IsComObject($obj)) { [void][System.Runtime.InteropServices.Marshal]::FinalReleaseComObject($obj) } } [GC]::Collect() [GC]::WaitForPendingFinalizers() } Both of these files should be in your CMM program folder (The program you are running).

Do you need to have all in one measurement plan? This is my assumption, otherwise you wouldn't open the thread If so, a mini-plan will do the job. You would have one mini-plan for the measurement from the left and another one for the measurement from the right. I don't know how it work with bar codes and Auto-Run, I have no experience in it Or can they be separate plans?

@Kevin Harold, please hear us, your customers on this one. We love the application specialists and developers at Zeiss. You people are world-class, and your expertise and support is the x-factor that helps us succeed in the measurement lab. Acknowledged that even seemingly minor functionality upgrades in a software can in reality be a huge undertaking. I understand that Calypso does not operate on a simple linear command history. Many actions affect multiple interconnected objects and states. A friend of mine and software developer (who works for a competitor to Zeiss) educated me on the architectural complexity to adding a universal undo function. It's more achievable when planned for during an initial build. That being said, she also claimed that while challenging, it is indeed possible. Users plead for the undo function is because undo is deeply wired into how humans interact with computers. The eye, brain, and hand operate as a tight feedback loop. This is why it's now a fundamental expectation across nearly every computing environment we use, professional or otherwise. Also driving the vote count is the frustration from needing to rollback a menus-deep setup in Calypso that took time and mental energy to create. The greatest strength of Calypso, the feature-based architecture, can cause heartburn from having to redo instead of undo. Evidence for that claim is the hypersensitive GUI in the Features and Characteristics lists. Misjudge the landing strip for a group or feature that you intend to move by even a pixel, and you launch an object over the moon, often with weighty consequences. An undo function that restores the position of a feature, characteristic or group to its previous position would be a monumental value-add. Team Zeiss: we are still asking for "Undo" in Calypso. We recognize it will require effort, and please feel free to educate us on whether or not this is a realistic goal. We appreciate you.

I would like to state for the record Mr. Frodermann, that I do not have 6 fingers. Tom's comment does seem to track with how the button currently works. Unfortunately, I do not have any line of communication with that team to find out what they are looking at as answers since it says "in evaluation" but I will try to ask around and see if I can get any further information to bring back here.

Hello Dragut It's a fixed value for the Waviness template and you can only modify it manually 😞 Also most of time the input shows 0.000, because it's rounded to integer 😞 A possible value at your example could be 10nm ==> input = 0.000010 ==> shown = 0.0 Therefore I prefer customized graphic for parts, which longer under production. Klaus

Currently voted as #3 all-time, #2 unresolved suggestion on MyVoice:

Why is there even an undo button? It doesn't work!!!!

When building a stylus with movable parts, what is the trick to getting the movable parts at the correct angles? And how critical is it?-Unfortunately, the biggest trick is practice, especially with XXt styli, but the methods described by other users here can help make it easier. How critical the angle is is dependent on the measurement: how far into the part you need to go (the further in the more precise you need to be), the size of the feature (especially hole diameter), and the ratio of the probe tip to the probe shaft diameter. All of these contribute to the potential for shanking the probe. I am building the stylus pictured. It can be rotated 360° (blue arrow) and the knuckle can bend back and forth as well (green arrow). Let's say that when the RDS is at 0°/0° I want the stylus to face forwards towards me and be lifted up 45° towards me. How do I ensure that it is exactly centered / forward and exactly 45° up? What if it is not exact? How far away from that can I be before it creates an issue? The way to ensure it is exactly centered is to set the probe through whatever method you choose above, then check the angles on a CMM (ideally the exact one it will be used on, to account for any slight variances in the systems) using the method Chad describes above. I personally will do a quicker version of this check as a go, where I will take 2 points on a sharp cornered object (such as as machinist block) as a quick check, then adjust until I am happy with the result, at which point I will do the full cylinder check. How far away from nominal you can be depends on the factors above, I personally shoot for under +/-0.1degree on most probes, but your actual acceptable values will vary. What angle does the reference sphere have to be at in order to qualify it without a collision? So far our reference sphere has always just been straight up. The reference sphere can be set at various angles, so long as the stylus being calibrated can access the sphere about the equator without any component hitting (The angular coverage of the sphere can be adjusted for VAST systems if necessary, dependent on if the calibration is Geometry, Tensor, or Dynamic Tensor). An easy way to ensure this is to effectively point the sphere and stylus at each other. If they make a straight line through their axes, then it should be able to access, but this is not the only viable angle set. If I have to change the angle of the reference sphere, how do I ensure it is at the correct angle? If you choose to, you can measure the exact angle of the cal sphere by measuring a cylinder along the shaft of the cal sphere, but often times you can get close enough for successful calibration with a little care and manual setting(you can probably eyeball it close enough to a 45deg rotation to work, and the tilt is typically controlled by the cal sphere stand, so that should be close as well) When I go to qualify it, if it does the thing where it guesses what angle the probe is at, but it's not what I intended, do I change the values to match what I intended, or do I adjust the stylus and try again until it matches? This depends. The guessing what angle thing can happen because the probe is too far off, but more often it occurs because you did not probe close enough to the centerline of the sphere while travelling in the direction of the axis of the probe. So ideally, you should confirm your stylus is correct via the method described by Chad above, then you would know that the error is in your manual probing and should be able to be dealt with by inputting what the values should be. Do be careful as sometimes what Calypso guesses you intended those angles to be may have a different sign than you expect, which can cause confusion. You'll usually know if you had a sign issue as soon as it starts calibrating though, it won't probe even close to along the probe shaft axis. Proper calibration start should visually be probing along the axis of the probe, and the initial point(s) should point to the center of the sphere (mostly, the CNC cal doesnt do this exactly for technical reasons, but it is still close) What if in the future I wanted to use this same set up but have the knuckle point the probe at 30° rather than 45°. I imagine I would need to create a whole new stylus system, correct? But wouldn't that require a separate adapter plate so that the CMM would recognize whether it was the 30° setup or the 45° setup? Would it make more sense to leave this one the same and buy an identical setup and make a whole new configuration? This also depends. You would normally want to create a new stylus system in Calypso for the 30deg angle, not just update your existing 45deg one, but there are cases where updating is the right option(the probe created just for Hole27 was at 45deg, they changde the part and now hole27 is cut at 30deg instead of 45 for example) . If you never intended to use the 45deg setup again, you could simply delete it out of Calypso, and then make a 30 deg probe configuration with the existing adapter plate and teach that into Calypso. If you want to have both a 30deg and a 45deg setup, yes you should have 2 different adapter plates, as fully separate physical configurations as well as separate entries in Calypso. Regarding buying new tooling and making a whole new configuration, I would say this is the best option for common or frequently used configurations, but it may make sense to tear down and use components to build new probes for short term use or one off tools. Personally I am not a fan of reusing those knuckle joints, too many cycles of adjusting them can wear them out to where the no longer hold angle very well. There are a number of videos, articles, and guides which may be useful to you on these topics and others. All of these can be found here on the Zeiss Portal, but you can also find much of the video content on the ZeissIQS youtube channel, which may be easier to search videos https://www.youtube.com/@ZEISSIQS/videos

Richard, I think we need more info : What would cause 'plane 3' to be active or not ?, this could help us solve it. Also by chance, is plane 3 always a primary datum of the base alignment for example ? This might help with the solution as well, if it is just a random feature not tied to an alignment etc, it could be more challegning.

Thank you Piotr and Kevin. I believe your recommendations have solved my issue!

Hello, I have a question regarding the Suppression Level parameter in the plot, and I would appreciate your assistance. Is it possible to modify this limit directly via PCM, or is it necessary to use custom templates with different values in order to keep the desired limit constant? Additionally, in the image below, it can be observed that the Suppression Level is set to a value of 1.0.

I hope that helps. Type name of the new user - and then press +.

I dont see on this picture clicked tick boxes to active specific values - all of them are turned off. Please activated them and then make test.

This should do. //Used to run a specific Miniplan dependent on Pallet Location Number, add additional pallet locations as needed PltNum=getRecordHead("palletlocationnumber") if PltNum=="1" then setRunID("Run Left") endif if PltNum=="2" then setRunID("Run Right") endif

👍🏻Looks nice, maybe that can be modified, with a scale for some angles.👍🏻 There used to be a 2D template for adjusting it. 😎 unfortunately, it's for VAST M5.

What is the behavior set to in "Extras-Settings-CMM-Stylus System-Stylus check during CNC start"?