All Activity

A Zeiss tech helped me out and I understand how it works now. I needed to set the MIC inside of the Select Elements dialogue to match my diameter characteristics before I calculated the fit inside of the bore pattern dialogue. It doesn't inherit the settings from the diameter characteristics. Maybe this will help someone else.

I wonder - is there an ability in feature's editor to switch from element selection to program selection ( radio buttons on top ) to select a default for all, then reverting radio buttons to features selection and selecting all to "*" as default?

@nicolas lombardot You may need to perform multiple Base Alignment Match then as what you currently have isn't stable enough. You could potentially use something like the granite to help you. Either way, garbage in = garbage out.

Where are your datums?

Extras>Settings>Measurement First page is what you're looking for. I personally set my Clearance distance to Zero as a default, then add it if its needed during programming. But i also use a starter template for my programs, so i haven't started from a blank page in a really long time.

Yes they are in the configuration for measurement, but it doesn't change a program that has been created, and created from an older version of calypso.

Caution! Please note that reading multiple components' positions is done sequentially - it is not ensured that you get data of the same time frame. To get at least an indication of the inherent delays, you can read the corresponding time information: print( f""" {gom.app.project.actual_elements['Bucket'].coordinate[0]}, {gom.app.project.actual_elements['Bucket'].get ('stage.relative_time')}, {gom.app.project.actual_elements['Extension arm'].coordinate[0]}, {gom.app.project.actual_elements['Bucket'].get ('stage.relative_time')} """) Another idea is to use the `in-stage` accessor (see Working with stages — App Development Documentation), but I don't know if this works during a live measurement.

Hi Dominik, I am not sure if this a viable solution, but you could try the following: You set up an external Python interpreter which connects to ZEISS INSPECT via WebSocket interface and uses the GOM API to read the measured components' coordinates. 1. Start with the sections "Python installation" and "ZEISS INSPECT configuration" from Using Visual Studio Code as App editor — App Development Documentation 2. Set the environment variable `TOM_PYTHON_API_URL` to according to your ZEISS INSPECT configuration, e.g. in PowerShell $env:TOM_PYTHON_API_URL = "ws://localhost:55000?0123456789ABCDEF" (with your API port and key, of course) 3. Create a Python script which reads components' coordinates Minimal example: import gom if __name__ == "__main__": while True: print(f"{gom.app.project.actual_elements['Bucket'].coordinate[0]}") time.sleep(0.1) You should only read token values from ZEISS INSPECT (as in the example above) and not call any gom API commands to prevent resource conflicts. 4. Run this Python script in your external Python interpreter This Python interpreter must have the `zeiss-inspect-api` wheel installed (step 1). Its version must match your ZEISS INSPECT version, otherwise the `import gom` will fail. The Python interpreter must be started where you set the environment variable (step 2). Hope this helps! Best regards, Matthias

You can export ASCII point files by selecting the features - File - Export - ASCII

Wasn't those definitions in main configuration for measurement? Same place like automatic identifying of element from N points? There is also strategy for cylinder either points or arcs.

Thank you for the diagram, Richard. I appreciate it! Let's see if I'm understanding this correctly. Since you can't use a material modifier on a profile feature itself since it's a surface control, the combination of the profile and position allows for the profile feature location to shift based on its material condition. Is that correct? What about the lack of a material condition in the position callout from Tom's example? Does that essentially make it a composite/single segment profile since the tolerance zone is unaffected by a material modifier?

I need to change Clearance Distance and Retract Distance defaults in certain programs where both values are too big. I have set these in Measurement Methods, but it has no effect on new features or certain programs. On large programs it is a PITA to do this on every feature made or previously created. I am also aware I can mass edit via Measurement Plan Editor. Any help is appreciated.

it's worth with Z points, but I've only a very tiny zone of coverage before and after the base alignement match, and the CMM don't plap the diameters at the good place and collision ...

@Zen Cat Typically yes, but there are cases where that doesn't apply. See the example I was discussing above.

Doesn't it need to be a feature of size to use position? And what is the shape of the tolerance zone for the position? The portion in the middle could be considered a width I suppose and control the location side to side. But the open-ended portion on the sides is what's confusing me. Isn't a boundary condition in this case just acting as profile? Sorry for all the questions. Just trying to learn something.

Usually if they invoke Position in the lower tier then they are meaning Boundary Condition - look at Page 176 of ASME Y14.5-2009 (sorry I don't have 2018 in front of me). BUT, Boundary is usually invoked with MMC on the feature in the Positional control. That's because the Profile control is controlling the size, and the Positional control is only controlling location/orientation. I have a more detailed write-up that I could share if needed, but I would have to redact information before sending it. Here is a less detailed example that could be utilized for you (if you went the Boundary approach). Regarding the tolerance – Calypso does not natively handle Boundary Conditions, so we have to set it up correctly ourselves. The tolerance is based on the following: Taking half of the Profile Callout (0.015/2 = 0.0075) and half of the Boundary Callout (0.015/2 = 0.0075) or (0.020/2 = 0.010) i. The Boundary Callout of .015 to A B will have a tolerance of 0.015 (0.0075 + 0.0075) ii. The Boundary Callout of .020 to S will have a tolerance of 0.0175 (0.0075 + 0.010) Setting the Shape of Zone to Inwards to Infinity i. This will report the largest deviation that adds material to the surface to ensure that the virtual condition has not been violated. ii. If the Profile result is 0.000, then all of the surface deviations are minus material and the Boundary Condition is verified.

Thank you very much. It's an Accura, I think I'll leave it on standby.

Found the file, it is populated with file data, all are marked as Pinned. I have never used Pinned files in Calypso, just Recently Used. In your file, are they all marked as Pinned?

What do you mean by "probe tip files"? All probes are stored in an SQL database, there are usually no extra files. If the database got corrupted during the outage, you're probably out of luck unless you have a backup of your CMM data folder or one made with Calypso's internal backup function. The only probe files I know of are PCF (which is the export format from Calypso) and SSC (which is for Planner/Simulation only). I guess if you'd be looking for PCFs you'd know where to look, because you would have exported them yourself to a known location long before the outage.

Inspect does currently handle Total Runout of a Cone. Your closest thing would be a Profile, but just note that size/angle will have some impact on that result.

I believe the limit has been completely removed. It is either on or off now.

It is controlled by this file I believe.

You need to add Z points to properly control the Spatial Rotation and Z Origin for the Base Alignment Match. I've used it with great success on massive parts with small tolerances.

Three hours to test base aligment match, and it still goes wrong, the last problem is the CMM after the match going to mesure or 10 cm above the part or 10 cm in the granit :) I don't have much time so I 'll do with two programms, and a few PCM and it will be ok.