All Activity

I started doing something similar, then the operators just typed random characters to fill the value. Now I am still looking at a "Black List" of characters and coding it in PCM, or perhaps, if possible, have a script check the values and redirect. And that just gave me an idea. I already have an interface for selecting part numbers, I can transfer the 4 required fields to the interface, remove from Calypso and check values there where it's a lot easier to code in VB.net. I can then call the 4 fields from the para file I generate. Now I have another task.

Explain what you mean by wrong. Maybe show a snippet of your code.

Edit the "inspset" file, search for the string (Path) in the top image and edit as needed. I would search for "X:\Calypso\QC-Calc Data\History\master Export Files\" Save the file and run the program again. Always have a backup of the file you are editing!

Planner still seems to be broken or at least I'm not setting it up correctly and need guidance. When creating a new machine and adding MasterProbe, it still does not work or show at all when attempting the legacy method of importing the MasterProbe SSC.

I am trying to use your xml code (From your link), but it crashes Notepad ++ every time I apply it. By crashing, Notepad ++ simply closes. Any hints or tips?

Hello, I have a CAD file with datum point in. These datum points are named in the CAD program and the name is in the retained in the exported STEP file. In the STEP file this is a Cartesian point. See line from the file. I would like to import this point into Calypso and keep the point name in Calypso. It should become a space point. But when I do an import of the Step file in Calypso, the points are showing up as Point1, Point2, Point3, .... and so on. The original point name is not available in Calypso. What are the possible method to import these point with name in Calypso? Implement in the step importer similar as in the Zeiss inspect; Create a import script for these points; Other CAD export format; Other method.

You cannot, pratically. Circle surface scanning is too litle. You have to start form a solid calypso allignment starting from Datum A, then scan the cone on two far section, then on charatheristic choose "semi angolo del cono".

Dear Calypso Users I have a Zeiss O-Inspect 873 where I developed a simple Calypso 2020 program that has 1 optical manual point feature (created by the optical tool “Manual Measurement”). Using a base alignment with no features and an alignment MCS (CMM System), optical sensor at 0.50X, upon execution, the CMM travels in CNC mode to the designated point in the MCS, shows the red crosshairs allowing me to adjust a particular fixture component (micro VBlock) parallel to the horizontal crosshair. When satisfied with the VBlock rotational orientation, I strike the button on top of the right joystick to end the program. This program works beautifully in Calypso desktop. However, when executing it in AutoRun, it was working well, then all of a sudden it stopped working yielding an error message. The CMM optical sensor (0.50X) moves to the proper position; the computer monitor appears to switch to camera live image mode for a brief second, but then switches back to non-live image mode, finally yielding the error message. See attached error report and screen captures. Please see attached screen shots and Error Report. I look forward to your thoughts and insights. Good Weekend Mike Roterdam Senior Metrology Engineer ErrorReport.txt

I'm curious if anyone has ever had getActual(char).toleranceState be flat out incorrect? I'm testing something offline, could it be because of that? Calypso 2025

From what I see you have about 34.576 of length to scan; I don't see the angle as only in the 1.924 reference dim. I cone with 3 or 4 circular scans should be sufficient.

Would like some insight from others on appropriate filtering and evaluation on a large diameter. I have set up this feature following the condensed cookbook guideline as a baseline. Requirements: Looking for size, location and roundness of a ~7" OD. Assume part is in an as-machined state with a fairly tight tolerance on size. Setup: Scanning using rotary table with Vast XT head, probing in X- axis, I believe it's a 3mm probe at the moment. Currently on Calypso 2023. Strategy: Speed .591"/s, 5000 points, 380º, 500 UPR, 10-5000 pre-filter, ±5 adj points, 3 sigma. Should these values be adjusted in any way and why? Would these values need to be adjusted if the part were to be shot-peened and what would those settings look like? Looking forward to learning from everyone. Thanks in advance!

If you still have the installation pack, it's stored in the tools folder.

Dont forget to CAD/Cad Model Comparison, to clean up any ghosting which usually occurs when you do this.

Well ok, by normalization you are talking about restriction in feature's evaluation tab. It' just calculating measured data with fixed attribute ( restricted ). You can get more correct center of partial circle by forcing calculation with norminal radius. Same applies to A1,2. Using "P" usually means projected. In TP you can use that for projected tolerance.

I also wanted to ask, whenever you press on the "P" you are able to change the measure reference length. Is changing the measured reference length similar to the "bended" function since you could change the reference length of your cylinder to only what was measured?

I'd say when and why. For example if I am checking a concentrcity and it is out tolerance, there are certain instances where checking normal vector within the datum feature will cause the concentricity to check better.

Thanks. All of our stations are always running the latest and greatest. Doesn't look like the Basic Reporting64 is installed.

Just wanted to comment that this is a very clever and efficient way of selecting a file in a directory. Very cool.

Okay. This is what I did. I'm attaching the settings (is it correct?) and the results, but I'm not clear about the report results. Thanks

In the start menu under CMM order or run, are you running from features or characteristics? I've found that running from Characteristics will sometime create unexpected dependencies, maybe because I've only run from the characteristics side maybe 10 times in 20 years(?). Depending on what version you're running, right click on the feature you are selecting to run and choose check use of selected features and see if it shows any unknown dependency - or - choose to execute the feature and see if it only runs or the other others you are seeing it do when chosen from the start menu. Just thinking out loud, do you have any mini-plans set-up in the program?

Allright - i was finally able to make a usable tolerance file I have implemented DIN EN 10243-1 F and E norm for length tolerances - selectable as +TOL-TOL Perhaps i'll work on those radiuses, but i can not find how to apply rule only on one side of tolerance. din10243-1.xml

The content of \config\env\values should be displayed using baseSystem().machine.environment.OMConfiguration.getMastersEnvMemory or baseSystem().machine.environment.OMConfiguration.classPool.Memory.env For Instance the default actuals path: baseSystem().machine.environment.OMConfiguration.getMastersEnvMemory.defaultPathForActuals It is just possible to access the underlying smalltalk layer using pcm. Actually, by Zeiss this kind of pcm code isn't intended to be used. So it is not documented and not easy to to figure it out.

That was what i am thinking too... But none of my strategies are dynamic or use PCM. Only manually selected from the run screen. I may have somehow "corrupted" my program. It is working fine in every other scenario I can contrive to test it except this well lived program.

There is a CZ, so do a localisation / best fit, select the 5 cylinders, and the plan A as datum, and check translation and rotation alowed

Hi Jisub, could you contact the support please with reference to this forum thread? Nanno