All Activity

Quick update - it has been confirmed that CALYPSO patch 8.0.1601 contains additional fixes for the external (outer) torus issues mentioned above. So as of testing today both internal and external torus navigation issues should be resolved in 8.0.1601.

We're trying to make improvements on a method for inspecting cams for a family of parts. The method we've been grandfathered into uses single points and a probe with the same diameter as the specified follower; it takes hours to program and very slow to run. One of our Contura's has a Curve license, and I've been trying to figure out the nuances of this package. I have a few questions that I'm hoping to get some insight on. Side note, some of the drawings are from the 70s and I'm not sure if there's accurate CAD available. Here's what I've done so far: Imported a text file of the provided angle/radius chart of the cam profile Curve parameters: Space point evaluation, exact number of points in strategy Duplicate curve set as theoretical feature Curve Distance (Pitch Size): Inner Curve = measured curve, Outer curve = theoretical curve; tolerances are max/min of the tolerance band Curve Form (Pitch Shape): Tolerance offset = Average Curve Distance Curve Jump (Pitch Waviness): 2 points, 50% overlap The inspection notes define Pitch Shape as the distance of each inspection point from the average Pitch Size. Pitch Waviness is the max allowable deviation difference per degree. Here's where things are weird. Curve Distance outputs a positive value, but Curve Form the outputs are negative. I've tried reversing the inner and outer curves, but it did not make a difference. My questions are: With Curve, can I use a standard probe instead of the follower specific size? i.e. the follower sizes vary by part, but I always have a 3mm ready to go. Why is Curve Form giving me negative values and is there a way to fix this? Some inspection charts only provide data points in 5-degree increments but still have the 1-degree tolerance. How would you go about calculating that?

@TIM MCKAY I do this often. Especially when I do not have a proper CAD, but need to align the volume to the global axes for normal viewing during clipping. These instructions are for 2023, so it may be slightly different for 2026. Instructions for alignment without a traditional CAD (.stp, etc) Create the solid mesh from your volume Operations>Alignment>Initial Alignment>3-2-1 My go to is using ZZZ, YY, and X to establish a rough alignment normal to the axes. If available, use a flat plane to level in ZZZ Tweak the mesh orientation/rotation in X and Y after the 3-2-1 alignment using Operations>Alignment>Single Element Transformation>Set Matrix With your mesh best effort aligned normal to the global axes, go to Operations>CAD>Actual Mesh To CAD Your mesh turns blue, signifying that it is now considered the reference "CAD" Delete all alignments, and the mesh, leaving the CAD and volume for your part Go to Operations>Alignment>Initial Alignment>Prealignment (Volume) Make sure to check that the target is the CAD, Use only reliable surfaces is checked. If it won't align, use a nominal point on the CAD and an actual point on the volume From the aligned volume, create the mesh again Go to Operations>Alignment>Initial Alignment>Prealignment Inside the part drop down should be the CAD, Aligned Volume, and Aligned Mesh It is the same process with a traditional CAD, except there is no need for the 3-2-1 alignment and alignment tweaking. You align directly to the proper CAD.

@Jackie Williams You're in the Features Setting Editor. You want to be in the Characteristics Settings Editor (found under Resources)

I remember one experience trying to qualify a flimsy star-type stylus system on an XXT. I couldn't get a good qualification and assumed a sensitive probing dynamic would improve my results, but it wasn't until I tried a robust setting that I get a better qualification. It didn't make sense at first but then I thought maybe more pressure helps stabilize the probe. I don't know if that works across the board, but it worked in that instance.

Well you have to decide how far away you need those points and calculate. I got cca 1s per point, so sometimes it can be faster to scan than take points ( when you need point density ) or take single points ( larger area with less dense point ) if it make sense.

Unfortunately not, we need data collects every 10mm or so down the bore.

@Roy Espinoza I think i have used restriction for radius, then Gauss

@Martin Jánský Did they both have the same evaluation?

I have never changed any of this setting on any of the machines under my control. The above issue is one someone else's machine. I am looking into what that setting might be and will update the post. The 2nd part of my curiosity is does this setting have any affect on qualifying the other stylus systems?

@Roy Espinoza I was testing a cylinder a time ago, where i compared profile of cylinder with filled datums of that feature against profile of FF - same measured points ( either one was recalled into another ) and results were very different.

We cannot select the "Selected features" button.

This is treating it as two separate DRF's. This is straight from Uncle Carl.

Might work.

Maybe: copy & paste all of the circles, and change the Z value of the 2nd set (using the Measurement Plan Editor), and them Recall Feature Points into new Cylinders... still a little work, but probably faster than extracting all of the Cylinders (definitely faster, if you are not using a CAD model)

I need to change about 3 dozen circles to cylinders so I can use them in a common datum. When I open one up and change it, I get the error message below. Any ideas on how to get around this without having to make new cylinders from scratch?

sorry, i mean: u and w are fixed, and you have to check/evaluate v. 😵

The thing you show in the operator window is editable under the user defined report variables. I can't remember which thing it's under in the top bar. I don't currently have Calypso access at my current job.

Insane! Thanks a lot! I didn't expect it to be that easy. Never payed attention to that log file before. Does the log grow or does it always mirror the state of the last run? Because if it doesn't grow and missing files are marked, I probably won't need all the other check functions. 👍

This is not a composite control frame, it should be treated as two separate DRF's. In this case the bottom DRF to no datums would just be FORM.

Edit: Missing files are labeled with MISSING in the protocols.log file: C:\Users\Public\Documents\Zeiss\CALYPSO\workarea\results\somtehing_2026_07_28_pwr.pdf MISSING By the way: Why can't I edit my posts anymore?

Hello Norbert, all generated files are logged in the protocols.log file located in the actuals directory (directoryPath("actuals")): baseSystem().machine.inspection.settings.protocollog settingGet("protocollog") remark: baseSystem().machine.inspection.settings.blabla is the "same" as settingGet("blabla") If the table file option is activated in the start window: baseSystem().machine.inspection.settings.resultToTableFileDialog settingGet("resultToTableFileDialog") settingGet("resultToTableFile") shows if table files are activated You can check custom path settings with baseSystem().machine.inspection.settings.protocolSettings.outputFileDefinition settingGet("protocolSettings").outputFileDefinition especially (returns nil if not) baseSystem().machine.inspection.settings.protocolSettings.outputFileDefinition.tableFileHdr baseSystem().machine.inspection.protocol.protocolSettings.outputFileDefinition.tableFileChr baseSystem().machine.inspection.protocol.protocolSettings.outputFileDefinition.tableFileFet

I was told, and it should still be on the forum (many years ago maybe 2015 or so), you turn off Stylus Update when you are re-qualifying a stylus. You have to reference the Master Sphere, but you do not change the Master Probe data to keep all of your styli matched as if they were all qualified together.

Should be possible with getActual(feature).error return value: 0 -> no error -5 -> 'Not enough points available for the feature calculation' (Every value characterizes a type of error as for instance -8 -> 'Error during iteration of the feature calculation')