All Activity

Hello, could you please tell me if you have solved this problem?

I will give this a try, this is not selected in my curve feature.

@Charlie Turch and @Klaus-Dieter Hermann-Kessler, thanks for both of your strategies! Very useful. Klaus, I experimented with your approach, and it works well:

@Max Haynes I don't know if this is your problem but I see this happen whenever a probe shanks out at one point on the diameter. However, I wouldn't necessarily see equal amounts on the and bottom. I would expect to see a greater deviation at the bottom. I call that the "uvula" effect. You won't see the uvula until you increase the magnification, like you did.

I have a program that had a model loaded into it but the model is for a different operation. There is no model for the current operation. I deleted the model in the hierarchy. I also deleted everything in the measurement plan that had the word model in it. The model appears to be gone until I run in simulation, where pops up as soon as I start the measurement plan. Where is this model hiding?

The value and graphics, I increased the error scaling for the post. "E side" looks great and looking at the manufactures report they seem to get a better result than i do (0.074) graphics also looks better. I would like to understand what the graphics are telling me when i see this loop. tends to happen often. Is this just normal or is something happening within? Both bores are 200mm and 30mm depth same measurement strategy, using the same datum bore.

Are you concerned about value or graphics? Graphical issue is only magnification of deviations - can be changed in total runout characteristic.

Howdy, was wondering if anyone knew of a reason as to why i get these weird curly results for runouts. the other side looks great. scan direction for feature is the same for datum cylinder. is this a projection issue?

Collect the actuls by 3d-Curve and the surface by recall the points into plane PointGenarator 3d-Curve Start Index = 135 // ° End Index = 3735 // °; start angle + 5 revolutions Step = 5 // ° 10 // inner radius; constant 0.001 // gradient of the spiral 0 // nx 0 // ny 1 // nz perpenticular surface = parallel to Z-axis point(10*cos(index)+0.001*index*cos(index), 10*sin(index)+0.001*index*sin(index), -5, 0, 0, 1) Please play with the parameter to addapt it to your part Good luck

I can't say pros and cons, we have it enabled, but we always input own speed and point density. If buying, beware, there are 2 levels of license - Navigator 1 and Navigator 2. One of them will allow for qualifying on smaller reference sphere, the other one not.

The scanning speed is also missing. That's takes place when the measured actuals recalled into the curve

You can do so by creating a polyline on the plane and using the Polyline - Connect Points with Arc option. This will also you to create an arc with the last 3 points that were clicked on the surface and if you take your time to set it up you can make a pretty smooth spiral. Mine isn't perfect 😄 but yours will hopefully be better.

Was this actually measured with a stylus or was the DotScan/LineScan used?

I've never been a fan of using the box tool for Recall Feature Points as it can easily break. Most of the time you need to manually change the size of it (usually the thickness of the box). I would strongly suggest you use Point # instead - it is more robust - also make sure Curve result points is checked - this will use the act to nom corrected points instead of the raw points (it also makes finding the correct point number much easier - just use the nominal point numbers 🙂 )

You cannot use the old GD&T Bore Pattern Best Fit for holes that are perpendicular to the axis of rotation - it will only truly work (with a pattern at least) if they are parallel to the axis of rotation. As long as you don't need any MMB/LMB evaluation - I would first use Geometry Best-Fit to the DRF (allow rotation), then evaluate the Position of each cylinder back to the Geometry Best-Fit - you will need to either use the Polar evaluation or the Special Rotation to align the axis for each hole.

On your old computer, go to C:\ProgramData\Zeiss License. Copy the license files from there. Then, on your new computer, insert the dongle and reactivate the files using the Zeiss License Management Tool.

Hallo Karsten, das kann ich dir nicht sagen ,weil ich es nicht weis. Den Befehl habe ich selber hier im Forum erhalten, als ich damals das Problem hatte. P.S schau mal unter dem Link. da gibt es ein Tool von Eric da sind viele Befehle drin. http://mimir-project.asuscomm.com/

Moin Jörg; Super vielen Dank! Das probiere ich aus.. Wobei es um einen Tasterwechsel geht, nicht nur um die Ablage. Hört sich nach einem direkten Befehl an die C99-Steuerung an, Beeindruckend! Wo gibt es denn die Liste der verfügbaren Commandos und Parameter 🙂 ??

Hallo Karsten, vielleicht hilft Dir ja der Befehl, commosCommand("TU") da wird der Taster abgelegt. Den hab ich in ein Resultatselement als Formel gelegt. Ich habe das am ende eines Programms gemacht, weil es bei unseren Bediener als zu fehl Bedienung kam , und dann beim Referenzenfahren zu Kollision kam. Weis allerdings nich,t ob das bei deinem Kalibrierprogramm geht. noch ein Beispiel : commosCommand("TU"),positionCMM(200,-15,-100,"z","x","y")) mit dem Befehl fhärt er nach dem ablegen des Taster eine bestimmte Parkposition an. Und das in der Reihenfolge wie du die x,y,z werrte eingibst.

Hi, you have to edit report template by clicking RMB on your report style ( not individual pages yet ) and click "Edit template" Now you can click on desired page ( "main" in this case ) and with double click you can edit that text. After changes store this template in your app. That was for further applications. If you want it just for now, then with double click edit directly your page ( bottom left list )

Hello everyone, I'm having som problems with the report pages. When i delete keywords from the template, they show up like "???: Unknown Keyword" in the report. How do I delete these lines completely? -Daniel

Moin! CALYPSO 7.4.24 Wir nutzen das automatische Einmessen auf allen Maschinen. Bei den DuraMax(en) sind auch weit auskragende Sterntaster vorhanden. Nach dem kompletten Einmessen zum Wochenende fahren wir die DuraMax/PC herunter. Beim neu starten kann es bei der Referenzfahrt zu einer Kollision mit der Maschinengeometrie kommen wenn bestimmte Sterntaster noch von der Kalibrierung eingewechselt sind. Daher möchte ich am Ende der Einmessung der Taster einen bestimmten Taster automatisch einwechseln lassen. In der Parkposition kann ich einen Tasterwechsel definieren jedoch wird dies im Einmessprogramm nicht ausgeführt! Ich denke mal weil es gar keine Messelemente gibt.... Wie kann ich also am Ende eines Einmessprogramms einen Tasterwechsel ausführen lassen? Danke für jeden Tipp und schon mal ein erholsames Wochenende 🙂 Gruß Karsten

Hallo Erim, wir nutzen es in der Autorun Oberfläche, und bei uns wird es dann so dargestellt. Mann sieht sofort welches Teil i.O oder N.i.O oder noch in der Toleranz ist. Wenn es außerhalb ist, wird der Reiter Rot dargestellt.

hi na_vor, We have no PCM but your answer let me hope we can use generic PCM functions anyway... I have no special idea of PCM but I´m familar with some programming languages like C, Perl, ksh ... I read the the file plugin_postFeature_pcm.txt is read before output parameters of a measurement are executed. So for my understanding this file is parsed after every Measurement. In that, I insert a simple SystemCall("write_mylog.bat") to this file in hope it will be executed for every measurement. But I see it is only executed once 😞 My Idea: Sometimes we need to use the programmable stop. For better understanding what the user has to do I would like to display a little picture using the feature "Measurement information". Unfortunately this call is "sticky" which means the executed viewer will not closed after the user press "go on with CNC" button. If I get a "user-exit" after the measurement, I can kill the called process just after the related measurement is done.