All Activity

Oh, thank you, I'm still not using it. Something to look forward to.

This is Zeiss Inspect - not Calypso - so this function is not available here in this way.

@Ivan Servin.2 I was looking at your picture again - what is the reason for using curve? Wouldn't be enough using 3d line?

@Martin Jánský Cheers to staying on the forum when on holiday! 🍻 You are correct. The theoretical points (such as symmetry, max/min coordinate) are only available when using the recall option, not the recall feature points. I did try recalling my theoretical points into a single point. Before recalling my point in the space point, I was able to recall it in a curve. However, after recalling the point, I could no longer recall the point in the curve feature.

@Richard Shomaker Out of currisoty, how is the line profile created? Are you recalling the feature points from the profile surface or another feature? Or are you scanning that line profile? If you are using recall, try flipping the curve from inside to outside.

Thank you. I will run a test to see if it works.

I use Notepad++ search/replace. Look for #pdfFilePiWebReporting in the inspset file. I hope this helps.

I need to change the output path in each Calypso plan we have. This is the Piweb path for all the Calypso PDF files created after run. Currently the only method I know is to open each plan individually, make a change and save. Is there a external macro or file I can modify to make this change in Calypso?

I don't think this feature is able to give measured points in this way. But i think you can use single point - use only recall and select that maximum coordinate feature. I am not sure if this can be recalled as recall measured points, but point is in recall option. But thanks for trying another options and telling us. Unfortunatelly we are having Christmas holiday, so i am out of Calypso until January.

@Richard Stanich I don't think we are on the same page. I already have these points created in my program; they hold values. But for whatever reason, Curve does not allow me to recall these points. @Martin Jánský I actually have several min and max coordinate features already in the measurement plan. But again, CALYPSO does not allow you to recall these coordinate points. I tried toggling the min/max coordinates from point to 3d point, but it didn't help.

Just so you are aware, this is not this case for Calypso 2025. These diameters are no longer defaulted on the report. 🙂

This is not the case for the new GD&T engine.

I am curious why there is diameter sign for line profile. What i saw using flag with deviation number was always positive. I have also problems with visualizastion of your line curve. Can you post nominal curve with vectors?

As long as the star probe is balanced and within the limits of the graphic above, you'll be fine! Setting them up is very straightforward. We have had nothing but issues running L shaped probes, and only do so when absolutely necessary. Balancing seems very important on the XXT

Surface Comparison to RPS: Surface Profile to RPS: Line Profile to RPS: It's not always consistent either. Very strange behaviour. I've also seen it show "positive" deviation when the deviation is in both directions as well.

Saving and loading calypso files from a network share trips our IT intrusion detection system and is a giant mess. They have not been able to figure it out. Switching from using "windows file shares" to sharepoint has solved all of our calypso networking issues

What about setting your variables in the Nominal, Lower and Upper tolerance of the characteristic and change those depending on the user select.

Look at the depth of the cylinder (.150), now look at the A2 value, .0957°. Do the same for Datum F. This is a typical situation with short 3D features where the A1 and or A2 values are most likely errant. Also look at the distance from one to the other, you can calculate the error. A simple layout would show you if it's true or not for 28-Cylinder. Adjust your constraints accordingly with layout results.

The root cause might be due to a datum system showing beeing oriented in the opposite direction.

First of all, be aware that when you use a cylinder in a run-out, it will always be a total run-out over the whole length of the cylinder. Not what you might want. Secondly, the actuals do look gruesome. Yeah, position and form might be okay, but the angles are huge.

What does Datum F look like? and is this in inches?

Hello, I am having difficulty with some runout results that don't make sense to me. The position and form in the feature menu look good to me (only about .0006 different than the datum) and yet in the characteristic for the runout, it is showing about .040 which is very far out of tolerance. The form on the datum is only .0008 and the form on the feature is only .0003 and the position looks good, yet i can not seem to get a good runout result. Sometimes changing the amount of points changes the result but I haven't found a consistent number. Any advice would be appreciated.

To see it in PiWeb editor you would need to have at least one measurement with this header. You should be able to see what data was stored in measurement. If this is not working, then you can map your headers into K fields

It's going to be difficult to help much with 2014, but I might try a new config folder, just to see if that is the cause. It has been a very long time since I worked with 2014, so I don't remember exactly where the config folder is, but you can try using this document: https://portal.zeiss.com/knowledge-base?id=442607

i am trying to use some predefined values from Run in my piweb report but i cant access them below are what i have so far variable exist in pre-defined list but i can do nothing in this window, no option for mapping selected in header parameter input value in run parameter when i go to piweb it doesn't recall it shows value as "null"