All Activity

When using best fit of bore pattern; Use 'View Tolerance' under Best Fit Method if you want it to match results you would get using a functional gage. See my post about view tolerance here:

I got 99% of it to work. The problem is with the error message. I found a work around but it only works if i do it manually. The variable is stored in the protheadpara file, so when i delete that i get no message and program runs. I tried to do the deletion with PCM in the inspection_end_pcm.txt file... and it does delete it, but when it comes back, i get the error message, but when i cancel and manual delete...no message.....Am I loosing my mind?

This is a Park Lock Wheel on an output shaft. I have a finished program with no taper. Before heat treat our process puts a taper on the minor dia (see attached pic). I'd like to modify the finished program to the sizes on the process specs before heat treat.

O.K. Lets try: Reference A is the left side of the body in your drawing. Reference B is unclear. On the one hand, it could be formed from the sides of the body (Bx) or from two holes B1 an B2 define (By). The Position tolerance definition match not the norm DIN EN ISO 1101. In the position tolerance 0.3 to A, no further degree of freedom is restricted. And no CZ is specified either. This means that each hole is toleranced individually. It is NOT a drilling pattern. The same applies to tolerance 0.3 for B, although in this case there is the additional issue that ‘B’ is not clearly defined. Regards Karsten

The GDT is only asking you to check the Orientation of the bores to the datum planes

Unless you specifically are not using the RSH, make sure you setup your reference spheres as RSH, so that the correct shaft radius is pulled in. Otherwise, if you leave it on Other and just set the Sphere Radius, the default Shaft Radius is 6mm. If you tell it an RSH, and CZSphereD8 the Shaft Radius will default to 1.5mm

I only changed it in the setting, I had no collision with the stem after that

Deleted, ignore

One thing I have seen done when there are multiple programs is putting in a programmable stop at the last feature reminding the operator to run the other program

Thanks Jens, But did you have to change the stem or did you just change it in the settings?

Yes, I had to set it to 1,5mm to make it work

For a true simulation with collision detection you need to build your styli with the Stylus System Creator and import them (SSC) in Planner. Make sure you first import the correct master probe.

Hello everyone, Does anyone have an 8mm diameter calibration sphere? If so, could you tell me the diameter of its stem? I've acquired an 8mm sphere, and although the Master probe calibrates it correctly, I then get an error when calibrating any probe. I receive the following warning: "Probe calibration could not be performed with this reference sphere. Check the stem radius of the reference sphere. It has been detected that the stem radius of the reference sphere is more than 60 percent of the radius of the reference sphere."

Only problem with UTF8 are special characters like diameter sign, ěšáí and so on.

Hallo WM_NC team, Thank you for providing the test data. A change in behaviour of GEAR PRO has been implemented. GEAR_PRO_2024_7.2.0402_2026.02.12 Enabling/disabling the ‘K-chart overun’ feature => Enabling/disabling the entire K-chart view When K-chart / K-chart-overun feature is enabled => enabling/disabling the tolerance evaluation of ‘K-chart-overrung’ has no effect – value is always displayed in red GEAR_PRO_2025_7.4.0022_2026.02.12 Activating/deactivating the ‘K-chart overrun’ feature => the defined K-charts are always displayed – exceedances of the tolerance band are shown in red, but have no ‘quality effect’ such as OK/nOK When K-chart / K-chart-overun feature is enabled => enabling/disabling the tolerance evaluation of ‘K-chart-overrung’ has no effect – value is always displayed in red ----------------------------------------------------------------- Question: Why does the numerical value of ‘K-chart overrun’ always appear in red (tolerance exceedance)? Answer: The existence of the value itself already indicates that the tolerance band has been exceeded. - ‘K-chart overrun’ is the amount by which the tolerance is exceeded. ----------------------------------------------------------------- The following is also interesting for your test data. Due to standard rounding rules, rounded values can appeared within tolerance, but are marked as out of tolerance. For example: Value: 0.0071 / Tolerance 0.007 => displayed value 0.007 [0.007] Some would like to resolve this seemingly contradictory situation. You can do it by switching the setting I showed here: Please note: This only affects the report display – all values remain accurate for other exports.

My offer still stands - but time is running short, dear Carl 🤣:

Ich habe mir sowieso ein Powershell-Script zur Rückkonvertierung nach ANSI geschrieben, weil unser QDAS-System (V14) UTF-8 weder ohne noch mit BOM korrekt verarbeitet. Ich bin leider nicht für unser QDAS zuständig, weiß also nicht ob da nur was falsch konfiguriert ist. Aber wir haben eine Riesenmenge ANSI-Datensätze in der Datenbank und das System ist nicht in der Lage, ANSI-Umlaute und UTF-8 Umlaute als "gleich" zu erkennen, darum legt es ständig neue Datensätze an. Ich habe also gar keine andere Wahl als rückwärts zu konvertieren. Oder gibt es da eine andere Lösung?

OK, so what i see is you need 1x Result element with this formula and disabled tolerances ( name "ElementResult1" ) It will produce "1" or "0". Now 1x Result element for setting "iO" with this formula ( name "ElementResult-iO" ) Apply this condition Now 1x Result element for setting "NiO" with this formula ( name "ElementResult-NiO" ) And this condition I won't be able to help further - i will be whole week outside Calypso

Hi Martin, Thank you for showing me this. Can you help clarify it a bit further. This will display an iO and niO in the name of the pdf generated correct?, Also, this showed up when I try running the program.

This is doable without PCM. Search forum for "N.i.o." It's only in default names of protocols ( and other files ) Found this:

Guten Tag Ich habe bei einem Taster festgestellt das dieser durch das Scanning abgeschliffen ist. Das Problem, erkannt habe ich das erst nach Maßproblemen am Bauteil und als ich den Taster optisch betrachtet habe. Bei der Kalibrierung werden Sigma Werte von 0,0007 ermittelt, weshalb der Taster als i.O. bewertet wird, im Test mit Tensor und Dynamischen Tensor eingemessen. Auf unserem Konturenmessgerät habe ich den Taster abgefahren und festgestellt das mittlerweile 0,014mm abgeschliffen wurden. Warum ist der Sigma Wert immer noch so gering? Bisher konnte ich mich immer darauf verlassen durch den Sigma Wert zu bewerten ob der Taster iO oder NiO ist, als Grenze haben wir uns 0,0010mm gesetzt. Ich habe dann noch eine Vergleichsmessung auf einem Endmaß gemacht, immer der gleiche Antastpunkt je 3x mit unterschiedlichen eingemessenen Tastersystemen und nur der defekte reist aus. Mache ich in der Bewertung nur auf Grund des Sigma Wertes etwas falsch? Bilder sind angehängt. Defekter Taster aber Sigma beim einmessen i.O.pdf

For future reference my friend. How to Take Screenshots on Windows 11 | Microsoft Windows

Hello everyone, Im trying to create a system where reports will be sorted into Passed(no OOT measurement) and Failed( 1 or more OOT measurement). This then will dictate where the report will be save into 2 separate folders. Based on what I research online, it seems doable. I think it might require PCM (I am planning to purchase) and maybe Piweb enterprise. The goal is to be able to sort through the data quickly or even import it directly into a report. If anyone have an idea please help me out. Thank you!

How can I toggle between the two? This is the setting I'm using for evaluation

Using Length as you marked will move nominals in direction of nominal vectors - aka make diameter bigger/smaller. To move curve along X,Y,Z it's on another tab "Coordinate axes direction". If you are lucky and it's only translation in one axis, then it's safe. Otherwise i would preffer copying this curve, changing it's alignment to have origin and vector from original circle, and just translate. Another option would be making alternative circle, it's strategy and making new curve from this circle's strategy.