All Activity

2500_fcdfcff2533342bd8f5c17a3d8f6a9b5.pptx here's a powerpoint that helped me figure out an alignment for locating the first gear tooth.

The problem I have with a circle is that if I don't start on the top of the first tooth, then the probe will jam up against the side of the first tooth and alarm out.

I'm not sure if it works with curves, but it does with a circle. Ive not tried it on a partial circle but had success counting the number of knurls in a circular knob

Martin, I had tried by scripting, however actual.normal.y isn't works. Is it the way you are using in user defined "Normal" -> actual.normal.y..? Could you please show me step by step how did you do that? Thanks,

For a helical strategy I think it would be best to have the CAD aligned (e.g. gap aligned to X or Y), so you can make sure all traces will be on tooth tips, etc. Let us know how you make out !

Thanks @Richard Shomaker and @Sven Radtke! Glad to know that some of us remember how to address some of Calypso's quirky nuances 🤣

Richard is correct, for total runout the entire OD surface should be included, and I have done this, but thought it might be a bit much for you. I think there are a few ways to get the helical paths on the teeth, since he is showing a cylinder probably a helix path strategy. A more common simpler approach might be to check top middle bottom of the OD. Keep in mind for this, due to it being a helical gear, you will either need to calculate the twist offset alignment, which is possible, but for a beginner I just suggest finding the gap in 3 places, top, middle, bottom. Good luck !

Is there a link or anything to help with creating the WAVINESS characteristic? Do I just create a circle, or do a 2D/3D curve? Here is the part in question:

Mornings! I have 3 L-Probes we use for measuring Ball threads ( Self-Centering method ). Getting these aligned for us is running a probe qual and looking at the X-Value. I don't use a rotary joint but instead loosen the 3 screws on the top plate and guess. I usually aim for anything ≤.004" ( .102mm ). That said we have had pretty repeatable numbers using this probe. The real issue was the additional Ref-Sphere cost. We couldn't qualify our probes on the 30mm sphere so we had to by a 5mm sphere. Edit: I missed the XXT wording. A rotary adapter would be needed, my bad.

I did used to have one. And really liked it actually. I don't have the documentation for it anymore, but I can tell from experience it holds more than you would expect. It moves pretty slow, I would think that means the MMI would have less of an impact compared to the RTAB. Its also build like a tank inside of it. Its basically 1 solid gear. Structurally, I can't imagine the weight of the part having much of an impact so long as the motor can turn it.

Recently we've had issues with one of our three Duramax CMMs reporting runout or concentricity 0.002 higher than the other two CMMs or concentricity gages. All the CMMs share the same programs, calypso 2021, and same probes. Measuring the sizes seems to be no issue. CAD Presentation outputs the same visual, on either side of the cylinder. Even after flipping the part. What could be the main causes? I've tried switching the fixtures. rotating the part. recleaning probes and the part. each machine is qualified only once a week. Any suggestions appreciated. I have a step cyl from recalling circles 1 and 2 for spacial, nothing in planar, x and z origins are step cyl. back plane is y origin.

If the naming is like how the new ones are, the -300 represents the Kg workload allowance. Now, what the max mass moment of inertia is a different question. You might have to reach out to someone at Zeiss to get an answer on that though. Looks like @Chad Watton may have had one of these in the past.

Hello, does anyone know what the weight limit is for workpieces on an RT05-300 rotary table (made in West Germany 😄)? Unfortunately, I don't have the specifications or anything like that. Thanks in advance!

I wonder if data from Polyworks are only actuals or nominals with actuals. Worst case - only nominals were exported.

I appreciate your input!

Like others have mentioned, you need a rotary joint, then its easy. I use an Indicator and indicate the L to one axis along the B length (Minus the tip) to within .001" per inch of travel capable on the stylus. I use this same method for all styli that are using other axis than Z. You can only indicate one axis; all the others will fall in quite close. Other than that, the MLE should be considered from DG, not just DS. This will be helpful when the stylus is past the ML to prevent shanking.

If there are any sensor-specific parameters which are stored solely in the measurement plan (the only ones I can think of at the moment are optical settings for an O-Inspect) you can always define an alternative strategy.

Working with Binary. I did bring in the points that were supplied as a PointSet, but all of the points (4 seperate/parallel planes comprised of 12 points each)... the Z values were all "0.0000mm", which I do not believe (these are not machined surfaces). I also just learned that the customer is using Polyworks Inspector to collect/analyze the data. I'm wondering is the points are being projected to nominal, for some unknown reason...

It shouldn't be. There are some cases where if you have Navigator functions active, and open it on a machine without Navigator you will get a prompt about it. You can also setup multiple strategies inside of each feature, so that depending on the sensor they can measure it a specific way. PCM would be great for auto-selecting this for you.

So Passive and Active sensor calculations or functions are not affected?

Nothing would happen. Calypso doesn't care what sensor you used to collect data with. All it is looking for are things like Rotary Table, Stylus System Name, Stylus Number. This is one of the first things we like to showcase to new users, we have a measurement plan that we run across all of our systems at the same time (one measurement plan on the network drive), but every machine is different (DuraMax, Contura RDS, ACCURA XTR) - Calypso doesn't care because every machine has the correct stylus system built respectively for itself - it doesn't care if it needs to rotate the head to A90B90 to get to the necessary styli.

What happens, if anything, you open a program that uses the RDS XXT sensor and save while the offline or live CMM is set for a VAST XT (or XTR) sensor? I have never tried this.

https://portal.zeiss.com/my-voice/own-activities/software/metrology/product/066cc67a-e50f-470f-9884-a3ec3253c37c/request/f2cd665d-6c94-494a-a434-ba6c86bfcd77 I'm still waiting on Zeiss to even acknowledge this. 😞

As Martin said, the .zmp is just a zip archive (you can just rename the .zmp to .zip and open it). It is just a nice packaged version of the geoActuals folder, as well as protocol information. I have been able in the past to just dump data into them, but Calypso now likes to use the binary (it says text file is the default, but my default was changed to binary and I never touched it), so you will be unable to modify it. If you go into Extras - Settings - Miscellaneous you will see the option to switch between text (ASCII) and binary. Having said all of that, you could use the PointSet option, to just read the text file with the new raw data, and use that for a Profile Characteristic. With the PointSet, you can even have Calypso use that data set to build other features (this is how it works using the LineScan to measure a part).

You can use a "Table File" which will add a new row for each measurement. (You must enable table files and click the button to initialize the table file before it will work)