All Activity

I will add another point of view, which is that the time between calibrations/probe checks determines how many parts need to be quarantined and sorted if an issue is found. Calibrate Monday, run all week, Calibrate the next Monday and find an issue? 1 week of production to quarantine and sort. Calibrate Monday, run all day, Calibrate Tuesday and find an issue? 1 day of production to quarantine and sort. So calibration frequency may be less about the CMM losing accuracy over a certain period, and more amount what is an acceptable amount of risk for the company

As defined above, every work scenario is different. We have a lot of Duramax CMM's that I set the global stylus limit values to require a qualification of all probes every 24 hours, with a sigma value of 0.002mm max. The protocol requires that all styli be cleaned before running the qualification program. I do this because on some of them, several different operators use the CMM (set to run in the autorun interface) on different shifts and there is no way to absolutely ensure every part is clean before every part is run and dirt/debri/sticky-stuff can accumulate on the probe that can not be seen with the naked eye and will affect results. I have a daily (every 24 hours) qualification program set to qualify as passive (doesn't take long) and a once a week (generally Monday) that qualifies with the geometry qualification, which takes about 25 minutes. In the limit values, you can set how many hours elapse before the CMM won't run without the styli being qualified.

Don't all of these file extensions need to be deleted? .sab/eval.sab/.fct

Regarding the 2nd issue of merging CAD models reference - CALYPSO: Merged CAD Entities For the deleting CAD issue is this only one program that won't delete the model? Or all programs on your system?

You could also implement a CALYPSO: Rotate/Swivel Position if it doesn't hurt your cycle time too much. You may want to skip steps 5-6 to avoid the +Z CP.

Have you tried zirconia probes ?

Within the features themselves. By pressing the button on the XY control box joy-stick.

Thanks! Are the "position points" inserted within the strategy of features, or is there a stand-alone "feature" that you can create (that positions the machine)?

Hi Jens, I am not sure whether this is supported as part of the mentioned command, but in the mean time you could achieve the desired effect by renaming the new points after they have been created: elem = gom.app.project.actual_elements['Section_1'] gom.script.selection3d.select_all_points_of_element (elements=[elem]) points=gom.script.primitive.create_equidistant_vector_points_on_section ( name=f'{elem.name}_Point', point_distance=3.0) for i in range(len(points)): gom.script.sys.edit_properties (data=[points[i]], elem_name=f'{elem.name}_Point_{i+1:02}') Maybe this works for you.

@Clarke Gilbert @Jens Kröcher Exactly what I was looking for. Thank you.

In the start measurement window on the right side is a drop-down selection [Navigate-Feature To Feature] for either "Use Clearance Plane" or "Use Position Points Only". Yes, move the probe to a safe/clear area and set the position-point(s).

That is a great idea. How can I program with the clearance cube turned off? Is there a work instruction that you can forward me? Do I simply turn off the clearance cube and insert move points inside each feature? And rotate the wrist during move points? For example, create 3 move points (move away from the part) and the change the wrist angle on the 2nd or 3rd move point.

Both machines have VAST XTR so maybe the possible rotation is the issue? I will have to install it on the machine with XT only. Thanks!

Have you tried running it with position points instead of the clearance cube?

Try adding a daily master part verification. This will immediately alert you if there is any problem with the styli. Or instead of a master part, create an artifact with multiple geometries. Use it to measure size/form/position/orientation of those geometries using every styli rotation/angle. This may take 10-15 minutes, but is well worth the time.

Good morning, I have a part that barely fits in my machine volume. When the head rotates the Z-axis goes all the way up and maxes out because my clearance cube is almost the height of my machine volume. Is there any way to force a head rotate between features without moving up in the Z-axis? The only workaround that has been somewhat successful for me is reducing the height of the clearance cube, which is risky because then my part physically extends beyond the clearance cube. Thanks, Lukas

Well this is normal behaviour. I am using box definition with coordinates from alignment ( base or special ) but not from view ( from drawing box by mouse ). You have to use alignment from curves - this will prepare your alignment. Now you have to duplicate that curve, use previously made alignment as feature's alignment and recall measured points. Now you can make box selection from this duplicate. You just have to go to box definition and set there features' alignment ( i am selecting name of alignment ).

Hello everyone, I have a problem with deleting a CAD model in the program. First method: I delete the model in the program hierarchy, close the program, save it and open it, but the model is still active. Second method: In CAD-VIEW-DELETE, I delete the model and close the program, save it and open it, but the model is still active. Third method: Modify CAD elements-Modify bodies-Edit-Delete body, delete the model and close the program, save it and open it, but the model is still active. If I have more models, there will always be one that cannot be deleted. The only method to delete a CAD model is to delete the files directly in the program folder, which is very clumsy. Another problem concerns merging models. If I create a program and insert multiple models, they merge into one when I save and close the program and they can no longer be manipulated and behave as one whole. Only one CAD model is visible in the hierarchy. Not a single thing makes sense to me why this is so? It worked in the previous version of CALYPS. Thanks a lot for the insights and ideas Calypso 7.8.1201 (12.03.2025)

Attached you will find a script that automatically creates equidistant points on the selected sections. The naming of the created points consists of the name of the selected section followed by “_Point” and a sequential number. Is it possible to have the numbering start with a leading zero, so that the first point is named “_Point_01” instead of “_Point_1”? # -*- coding: utf-8 -*- import gom elements = gom.ElementSelection({ 'category': [ 'key', 'elements', 'part', gom.app.project.parts['Part'], 'explorer_category', 'actual' ] }) selected = [elem for elem in elements if elem.is_selected] for elem in selected: gom.script.selection3d.deselect_all () gom.script.selection3d.select_all_points_of_element(elements=[elem]) MCAD_ELEMENT=gom.script.primitive.create_equidistant_vector_points_on_section ( name=f'{elem.name}_Point', point_distance=106.5, properties=gom.Binary ('eAHEmEtsXNUZx3+GAE4gpAb6EKrakeMW8xh77DgmmYQmDTFK2iRExAQUlY7mce0ZmFdmJnFMlXLTTakUCXXRgti0Eo9NpKAsKh5CIiyQEELJAvEQqIuqlbooFYgNFYKk+n/nHs+d8dhOKkW9lu1z7/3O/3s/zp2uVZIHN44cY9fUT3dOPcB0I1tqNdPpqXJQCaqt/Y1aPWi0SkETd/WxmrVrWMNa1qwF3lxdLRaBQ1O7DxxI7N53YP/UvdOJ8dT4xmhDdJ071c8G239ZVwLITZ471cf3gDUQlsmSI6BMhiZFasxxYf7cqau4AVgFYY4aNcr88rT2GcOwX8s7gJu7IFoEVKgjWK0zHOEIJQp8uFeg3wFWQzhNjQpp0jzIg+ymQPpVYR4CDpp+fewBhiCcIMskATNs4m6yJNnIOGNMkGSCFJvYTJIcBfJssLdZNjNJ3nbk2MiYUf1i/+kTwt0E3Nold54aVaoE5GlRo0GGMiV7kmHONGhR5PFrpYXMeCOE9y7a9dAC5ftfitf3wUyt9Y3ANRA2qZClTJm3H/lsQm9+DAx0SSSzNygQmCwVarZ+Ypv4e+ftiNHsjSjWGa9bwWyttXdk1aQNyHzxa7O11yIeAt3+OzMqft8CrjXJWzTMKrMMfxTH3keWirA/1tMfAGu7kI+aJk1KJkV+UrheMkVIlRYPn9HuVVFcbx/Q3U4XtstKmaFOljyPkWXWPNaweBHHQNwI+OOION4F3ALhrMXfCPs79j2waNeuk5JhG7DFrLmKMeDFo396/ecf7/n0pWfP/O61/7y8Q14dY4QUI2zmOgh3U6VJPYonPkrtWycg77hukx+jxcWvljf1hWvgm6sIt1KkRYUyP0HrgCwFW8sBLbIkcOEsZ+rvPQwyxiAJqpGb9OSwuTJvaAGSYNBQ5OR5ygQkbCUlRO+pRsnTpGnUde4iYYmS4FckmKNIySiTpr6cEpAmQd1ckWSOBlnqbCHBcbYyGuMn7qMdGikJCsyTiFFJlplIP+EFlJg1LdJWDlKG3aZo65NGKdCI0m9LpK8slov0zTFrtisbnTitZyb2IxvGE1MUzrLSUyktnQsUoiTR+1THe2+V9vtkhNCWU7viXJIxmdKsJ09q4Ve6dtK2cdI0TRcVL9FJ7wazxjtpZa5OmhR1jvV4L9SWUalQL0Ulu82Y7ZeiUJR5/3gab/lG9L+wSH9XLloWofJW0v4KqUqaiulUMK9Js06rJ+25k2qi5/tOmXohtK3T6223bbxGzrvVRdpcajQOmb6K7WHLNjVSRaJrAj4bM8ajYB1b0at8u52hKJucBJJm1Cz7/7dwbx9cKQt3VoTJy64IQ1Y7XJVokWB4oWqq1g1yp+Wr1n5e0pBTtbp3DzMWp80VPSLfuOjXylcgd6/oUtVzd+1q/5t/L9VDfHxd+LN6yC1Af6zJ3Re9/f0ftH8XWFPVOg18e4FS8TRvMaUhTgNQezb0HOLX6U/X/VAoIxFKnH6DxafvGbJQnQxHKREwx0BRcvph0Dfjg9YutfPwncLVWDQYSarOudTVz1+fFM0wcFOXHPHamInV0b3ne0mggc5l3NjDQrzJjUgmgcYS4OK2E8/dpnuNdjdAqFqvrJP285aTJR4n4PhBcdAgdj2EOzuo/LB26A6PtPKQOAQaxDqsnIvGl1ka1CwKC7ycFN99wI86Bu37rHqO29C9Z8GzO8hatOqp1t1obYuceEuyysaSRDz6nUV0hcXuJ6pgz2vH0tHhpXdxIbu5LHjqbqH74VAe7Hn+6GWQzjnezZrndwjucoPt+kef3Xvyk5Nn35wb+bp49smzkaK8NHTeThEpN2F3uMO7oR6194wNYD65C3zxxvKK9YUWxz8D1q8I3eQxStStIyjX/CToeoU/vDQ5/EGc6eJRW0pt7xPfXgZ1edypxj+tyqzon16nGgdXp2buVnuXhz758n/xkPPH4suXA5WOdV1mdPzjY+BT31wJ3r1KkeOtcqGGrnOB0/4f1SshwdLObEYjlYvR2jvi7k94BYtfF6/PTMuK7ST/fNuWUE+WTmidk3VKFrIKoYZiBeErvxWPFQNGnWlwmYqqY7CgS9EEn6HETNR9VcMktMyqfBh+4pJY+gOZjieCjbeIv23u5Zd2QezdIm5+r3lx08C/ro5bSq0+y6OReGovahQFe6rxQYVQh4cmOz+/JLF973E6e7ErdrZTl35hu2C8U9XRpV772B71shDLe18a22h+svn708uLExWsraAm1gGgocafxTWQ+rVKkhOnnQEPmbP89yQ/DtxPbsFmi0/me6x1SkV9K4h/Bxuwdj0OfLdDJsWlymM8bJzZ6hyJwubs1uUVjj59LQZ3CaXTifeBU/awff7SqkD2+CWB+7rVdkev+Hn3L8uDEfb/FwAA//8DALwt7oQBJuM='), start_point={'point': gom.Vec3d (0.0, 0.0, 0.0)}, start_point_offset=0.0) print(f"--> geselecteerd: {elem.name} (type={elem.type})") CreatePoints.py

When I wanted an answer to the exact same question, I chose to try a few things out. Instead of calibrating after a certain time, I regularly checked my calibrations for two things: 1. Does the probe still measures the correct diameter of the ref sphere and 2. If I use multiple probes in one program, how far do the X/Y/Z coordinates of the ref sphere spread. I found that a probe holds its diameter calibration value quite stably easily over at least two weeks, but multiple probes tend to drift away from each other after some time. So, what I do is, when I use only a single probe in a program, I check daily if it still holds its diameter value. No calibration needed. But if I use multiple probes in a program, I check them daily to each other and if they aren't within my spec (I want them to hold their position to each other within 5 microns), I calibrate them all in one go (but just the ones that I need). I'm pretty happy with that.

I would do it like Clarke, but a bit easier: Blade_Number = inquireList("Which Blade are you measuring?", "Blade_1", "Blade_2", "Blade_3",...) selectCase Blade_Number case "Blade_3" vX=11 case "Blade_4" vX=12 endSelect Then replace the 11 in your formula with the variable vX

So once a week would be recommended. We used to do it every morning, but then production complained that it was blocking the CMM for too long. Since then, we only do it once a week. Or in case of a major collision.

We are measuring cast iron parts, and all sections are inspected using scanning. We perform daily probe calibration and conduct monthly machine inspections as well. However, despite these measures, we experienced a dimensional issue caused by stylus wear. The problem was detected when scanning a specific surface, where a dimensional deviation occurred. We are documenting this incident and planning to implement regular stylus replacements moving forward.

Probably lots of trains of thought on this and while this answer is unhelpful it would be - it depends. How clean is your CMM environment, is junk prone to accumulated on your probes? What kind of material are the parts you are running? If it is a rough surface and you are using scan paths then you may wear down the probe tips without realizing and not catch it until your next qualification. Are you the only one operating the CMM or have full confidence in other operators not to have a crash? How would you know if something wasn't out of whack without qualification at regular intervals? That said for us I run a basic qualification program at the beginning of each shift on our CMMs that covers our main couple of stylus systems that cover about 90% of the parts we inspect. The program takes about five minutes to run and gives me some peace of mind that something didn't get screwy if I wasn't around to babysit the CMM or operators running on it. I do a full requalification if a probe is being replaced or setting up a new one, otherwise that daily qualification is sufficient for our needs. We could probably get away with a weekly qualification but it's quick enough to just get it in every morning.

@Mark - We do store our programs on a network, very rarely would we have the same program up on more than one CMM at the same time and I am aware of some weird issues that occur in that scenario. That does not seem to be the issue here. I tried storing the programs locally but the issue would still occur, also checked latency and our ethernet cables to see if that was an issue without luck. Initially it was just on one of our CMMs but now it has begun happening on a second one, identical setup. More details and attempts to correct the issue can be found over here: