All Activity

Wir haben insgesamt 10 Messmaschinen. An den Messmaschinen werden die Programme über die Autorunoberfläche an gestartet. Die Programme haben wir zentral auf einen Server abgespeichert. Da teilweise das gleiche Programm auf mehreren Maschinen gleichzeitig läuft, ist auf dem Server für jede Maschine ein eigenes Verzeichnis für jede Maschine angelegt. So kann man von den Offlineplätzen auf die Messpunkte jeder Maschine zugreifen. Zudem ist es abgesichert, das die Messmaschinen sich nicht gegenseitig die Messpunkte "überschreiben".

Hello everyone, I have a question regarding the mirroring of nominal, actual, and inspection elements. I am working with a symmetrical component. My goal is to define elements (such as surface points, edge curves, etc.) on one side and then duplicate them to the other side using a mirror function. Current issues: The coordinate system origin is not suitable for this case. Therefore, I created an additional plane, which I intend to use as the reference plane for mirroring. After performing the mirror operation (Element → Mirror), I encounter the following problems: The edge curves parameter can no longer be edited (they appear greyed out). For nominal elements, offset points are converted into simple surface points (see attached image). original: copy: For actual elements, similar behavior occurs—the mirrored elements (e.g., edge curves) are no longer editable. The only approach that works is using the officially provided script "Mirror Evaluation". However, this script only allows mirroring along predefined planes (X, Y, or Z) and not along a user-defined plane. i also tried to change the script code ( replacing the plane) but it did not work. Has anyone experienced similar issues or found a solution for mirroring elements along a custom-defined plane while preserving their properties and editability? Thank you in advance for your support!

I'd be extremely positively impressed if this would make it into Autorun - ever. I've done a bit of research and to me it looks like the current layer structure is woven deeply into Autorun. Sequences are defined as children of single layers. Changing that structure in a way that sequences become layer-independent, but also old *.arn definitions still work, would probably need a lot of effort. But don't take my word for it. I'm no programming wizard 😶‍🌫️

Abspeichern im Prüfplanverzeichnis ist der Standard. Die nachträgliche Auswertung funktioniert übrigens sogar auf einer Offlinestation. Aber nur der Vollständigkeit halber: Man kann natürlich nur Maße hinzufügen, die sich auf die gespeicherten Messpunkte beziehen. Zusätzliche Antastungen sind nicht möglich.

An sowas ähnliches hatte ich auch schon gedacht, aber das war mir dann ehrlich gesagt zuviel Aufwand 😦So kritisch ist das Maß dann auch wieder nicht. Eigentlich ist sogar der Hülldurchmesser der einzig entscheidende. Ich denke auch, daß ich mit Hüll und Pferch am besten fahre. Danke!

Are you logged in as the Master? If not, you might be missing the necessary permissions. Or are you using versioning?

Hallo Norbert, ich habe gestern ein wenig herumprobiert, aber selbst über PCM bekomme ich es nicht hin, Punkte, die aus den 3d-Kurven zurückgerufen wurden, als Zweipunktmaß auszuwerten, tut mir leid. Vermutlich bleibt nur die Option, die Keith oben angedacht hat, nämlich den Zylinder als Hüll und als Pferch auszuwerten - das entspricht zwar nicht der Hüllbedingung, aber wenn dein Pferchzylinder in Toleranz ist, dann ist das Min-Zweipunktmaß höchstwahrscheinlich ebenfalls in Toleranz. Um zu hundert Prozent sicher zu gehen, müsstest du einen Gaußzylinder erstellen, daran ein Koordinatensystem ausrichten, und dann den Pferchzylinder in diesem Koordinatensystem auswerten, mit eingeschränkten Freiheitsgraden in x, y (wenn der Zylinder in z orientiert ist) und Normalenvektor - weil: das Zweipunktmaß orientiert sich an der Achse des Gaußzylinders (siehe ISO 17450-3).

Hallo Niklas, die Messpunkte werden im Prüfplanverzeichnis in dem Ordner "idmeaspoints" gespeichert. Normalerweise müsstest du egal wo du den Prüfplan öffnen kannst auch die Messpunkte laden können.

Yes. Every run is stored as a .act file in a sub-folder inside the directory your .gear is stored. Open the .act file that you want, change your tolerances and click on the Evaluate button.

659_0dfb1189342fdd63147d204d93c08358.pdf

et is the gap width; Eet is the gap width variance. st is the tooth thickness; Est is the tooth thickness variance. Wk is the span width; in this example it shows a k value of 2, so a span measurement over (2) teeth. MrK is the Measurement Over One Ball MdK is the Measurement Over Two Balls MdR is the Measurement Over Two Pins Da is the Major Diameter FrD is the Runout of the Major Diameter Df is the Minor Diameter FrD is the RUnout of the Minor Diameter

Quick questions on the following acronyms on the attached file called “Gear Report Clarification.png”. I did look in the help file as well in the presentation you sent us but still can’t find the answer. Est St Wk Eet et FrD

Is it possible to re-evaluate results in Gear Pro? I ran 2 samples of a part using Involute but noticed I had the wrong tolerance for the dimeter over pins. I updated the tolerance, but would like to regenerate a report.

Thanks, but i have one curve in loop 16x. I can not extract data only from one iteration for one circle ( either point range or box ). I was able to do 16 separate circles and manually fill points from each iteration. I was hoping, that i'll create a curve a circle - both will be 16 in total and circle will have only own part of recalled points. This way i am getting wrong radius or rotated recalled points ( slots are in Z axis rotation, but recalled point while opened that circle is in X axis ).

@Charlie Turch This makes the most sense to me. Thank you Charlie.

For Planes; .length pulls the Length 1, and .width pulls the Length 2. As Charlie stated, len1 will pull Length 1, and len2 will pull Length 2.

.length can be used for many things. Most commonly used with pulling the length of things like slots and rectangles.

The PCM reference says .length is for curve length. I haven't played around with it but it does return the same value as the formal curve length characteristic.

Thanks Richard. Have a .5mm probe but ended up cutting the part down to get the probe to reach. And slowed the CMM down. Lines are a lot straighter than before, notice there is quite a bit of pitting or chipping on the splines as well. I'm sure thats not helping much. Thanks again. Lou

Also looks like .width could be valid too.

From Eric Moberg's Mimir program. I'm not sure the difference between len and length is.

I believe it would be .len1 & .len2

Hi Martin, You can recall the feature points of a curve into a circle or any other feature. Insert a circle, go to recall feature points, right click on the curve and select open. From there you can use the tools in the dialogue box to select the points you want. You can select by number, range, and there are also selection tools that become available like a box to window around the points you want to select. The box tool shows up on the toolbar at the top when the dialogue opens.

Hello! The solution mentioned here is the most common resolution for that error, but I also wanted to put this link here, as well, in case anyone ever comes across this error and the above does not resolve it. There are a few more things to try listed here: https://portal.zeiss.com/knowledge-base?id=1596796

I was introduced to these by my mentor back in 2000. It's a feel type, i have used the same way he showed me since. I haven't had any problems with any stripping out on me or too loose. My calibrations have all been good too after changing. I guess i have been lucky with this.