All Activity

@Keith Forche I did try that and when I exited the BA, it prompted me to check my clearance data (as usual), then prompted to update nominals, to which I said NO. Based on what I did look at, it seemed to do what I wanted. Unfortunately, time ran out on the clock and I will have to re-visit this in the morning. @David Carr I did try using and plane with offset but gave up too early because I had another issue. I am going to try it again in the morning.

Depending on which probe head you are using (VAST XXT or VAST) the technical minimum stylus diameter is specified at 0.3mm, see below. You can still use a 0.2mm and I suspect you won't have any issues but it may be in your best interest to measure a ring gage after qualification just to ensure it is measuring accurately.

Randawgg, Thank you again! A round of applause for our boy Randawgg!

Don't use cylinders as secondary in base alignment directly. Use two circles recalled into 3d line ( just recall their centers ) - This way you will have always stable direction. In other alignments you can use cylinders freely - just not in base alignment. I got problems while having a sphere as primary and cylinder as secondary ( forged towing hook ). Even with manually scanning at right spots it was switching direction. If you help yourself with start alignment with 2d line, then cylinder in base alignment is ok too.

Can't you just Offset your Base Alignment, in "Special"?

I've experienced it with short cylinders in a Base Alignment, but using a simple Start Alignment (Circle + Point) usually corrects the issue

Create a new alignment, then select (CMM system) from the drop-down. Then create a new circle and recall the circle you want to reference. Then on the recalled circle, change its alignment to the one you just created. Use the new circle's location for your getActuals.

Randawgg, Thank you very much! That is very useful! How exactly would you recall that circle into machine coordinates?

Any solution for this? I tried everything mentioned in this topic and still error is there.

Have you thought about using a constructed plane with offset to set your Z origin?

In the original plane, use a formula for Z getActual(CopyPlane.Z)+0.0052

@Dean Yater Sorry, but you lost me with "In Original Plane, use formula to reference copy for X, Y, Z, A1 and A2. Make Z formula ref copy +0.0052." I don't get the "reference copy" term.

Possible method, but I don't have time to test. Copy Base Alignment Plane. In Copy, change Z to -0.0052. In Original Plane, use formula to reference copy for X, Y, Z, A1 and A2. Make Z formula ref copy +0.0052. Make Original a theoretical feature.

I am not sure why my left side numbers show I have a long lead, but the deviation lines indicate it is short. Any help? 17LEM Female Finish_1788961091_9-9-2026_ 9.38.10 AM.pdf

My base alignment is a plane on top for Spatial and Z Origin, a circle on top for X & Y Origin and a plane on the right side for planar. We believe the tool that is cutting the top plane is .0052" too deep and affecting some of our compound angle hole measurements. Can anyone explain how to set up the base alignment to make it appear that the top plane is .0052" higher without changing the nominal info of the other features? TIA

Recently on our DuraMax, we've had programs get flipped during manual alignment, resulting in a crash. These programs have run fine before, so it is a recent development. I've done some preliminary troubleshooting like check probe qualifications, base and start alignments, and even rebooting. Any thoughts on what could be causing this?

PositionCMM uses machine coordinates, not your base system. It will also go in the order of Z then Y then X, unless specified otherwise. Look at the last example for moving in the Y direction first. But I would recall that circle into machine coordinates first, or you'll be in for a rough time.

Hallo Matthias, vielen Dank für deine Antwort 🙂 Das stimmt, bei dem dargestellten Protokoll fehlt die Toleranz, bzw. sie wurde links unter dem Namen vom Merkmal nicht angezeigt. Ich habe heute alles geschlossen, den PC neu gestartet und plötzlich geht es - sehr nervig und nicht zufriedenstellend... Möglicherweise habe ich in PiWeb etwas umgestellt und durch das Neustarten wurde es wieder zurückgesetzt? Grüße!

If it's just a chamfer, then i would stick to the closest feature to this chamfer. In other words it's local angle If part is thin it can bend by fixture force or machined features can bend via machining forces. Then chamfer is to none machining force. So if it's chamfer of a hole - you can compare angle to plane at hole or hole itself.

I agree with the posts above when using a small stylus (sub 1mm) on a large 30mm ref sphere. A small stylus on a large ref sphere runs the risk of shanking out if the shaft is stepped. Example image below. If you can ensure this isn't occurring on your setup then I wouldn't think there should be any other limitations. I also don't think you should see any issues when using a large stylus (over 1mm) on a small ref sphere (8mm). Unless it is so large that it's contacting the shaft of the ref sphere itself when scanning from the side. Maybe others have experienced differently but I have used upwards of 5mm diameter styli on my 8mm sphere without issue at the 180/0 position.

We're having some trouble agreeing on an angle result. Depending on what the other plane is, the CMM measures the angle between 43° - 47° I'm told by the engineer that it's actually a near-perfect 45°. The customer uses a 3d scanner and their results are very close to my cmm results. Is there a super secret way to evaluate angles differently? Here's a visualization of the chamfer's profile. I added random datums to constrain the DoF.

Can someone help me understand this PCM command, positionCMM()? I'm trying to get the probe to move in the -Y direction immediately after the program is done running. This PCM command will be place in the post settings for the overall program PCM. I'll list my code below. *"variable" will be a set parameter inside of a parameter file. Actualx = getActual("circle").x Actualy = getActual("circle").y Actualz = getActual("circle").z if "variable" == 1 then positionCMM(Actualx, Actualy, Actualz) endif As soon as the program is done running the probe will just go straight up. Not sure what I'm doing wrong. Any help would be appreciated, thanks!

Oh I understand now, thanks!

Ich habe das jetzt mal bei mir getestet. Das graue Kommentarfeld als auch Kommentare im Programmierbaren stopp werden Automatisch bei mir Aktualisiert im AutoRun bei Änderungen. Ich bin bei Calypso 2025 8.0.1603

Das ist dann wohl ein Bug, denn der Kommentartext (graues Feld rechts) steht nachweislich nicht im Autorun-File, wird also dynamisch aus dem jeweiligen Prüfplan eingelesen. Aber natürlich kann es sein, dass nach dem erstmaligen Einlesen der Daten in den Arbeitsspeicher das Feld danach nicht mehr aktualisiert wird. Wir ändern an dem Kommentar nur sehr selten mal was, darum fällt sowas bei uns praktisch nicht auf. Der Kommentar ist für unsere Bediener auch nicht relevant. Wenn allerdings sogar der geänderte Text aus einem programmierten Stop nicht aktualisiert wird, ist das ein gravierendes Problem, das ich an den Support melden würde.