All Activity

I am trying to detect which probing sensor is in use. VAST XTR Gold RDS CAA XXT Can this be done with PCM or a script? I would prefer a script as I don't have a full PCM license on every CMM. Since I have introduced a third tier to our Probe rack for the RDS styli, I need to detect which sensor is active to trigger a message or other event to warn an operator of impending crash if the third tier is not retracted. Eventually I will use a switch or laser to determine if the third tier is in the correct position.

This used to potentially cause problems if two machines were running the same program and finished at the exact same time

Completely agree but this time I just received this message so I will be heading over to the CMM to adjust that program (if I can figure out an easy way to only display the one characteristic and hide the other 3).

It depends who your audience is. But its hard to make everyone happy. Quality will want one thing, supplier quality will want another, and engineering will want something entirely different, production etc.....

NVM, I found the old FAQ from Zeiss where they tell you how to go into the config folder and change the password. Good thing I'm a data hoarder.

Unless your report will have something for machinist, then keep only things related for customer. From TP your machinists won't know what to do. Give them coordinates and diameters and they can improve it. I usually make extra characteristics for them, or they have an guidance for machining edits from given report.

The way I read the FCF is that the minor diameter is datum -F-, and has a position tol. of .010 @MMC and perpendicularity tol. of .002 @MMC. The countersink has a position tol. of 0 @LMC to datum -F-. I read it more like figure 10-27

10.x.x.x are "non routeable private IP addresses" It is 100% coming from inside your own IT infrastructure. (Similar to how 192.168.x.x is also non routable and popular for home routers)

Hi all, I wanted to ask what everyone does or if there is a correct method used for reporting out True Position on CMM Reports. Let's just imagine the part is a rectangle about 5" x 5" and .5" thick. Has a couple locator pins pressed into the top plane, the plane is Datum A, the pins are Datums B and C. The part has a hole pattern around the outside of the rectangle and here is the callout. What I want to know - What do you report out on your report? Do you report everything like this below or do you hide some of this and report just the Diametral XY Dimension and its tolerance? The purpose of this is just to provide a pass/fail for a final assembly. This is not to provide a machinist or anyone else to make adjustments if necessary, so I feel like I could probably hide some of it?

I am not sure if Calypso is using this angle - i would believe it will use only origin. But you could use some theoretical feature combined with this angle by formulas.

It's turned part, so i would scan just lines in part axis ( as viewed ) For small lines i usually do points instead of scan. If curve is available, then you can scan curve - make alignment from bestfit of curve to have correct data for small lines.

I'm interested, located in Europe however PM me when it's allowed for you to work with non-US guys

Check the complementary angle (20)°, to see if there is something wrong with your theoretical plane or if the angle is 60°.

Does anyone remember how to set a new master password? Or where to look up where passwords are stored in the program files? Its for nothing shady I swear. I inherited a cmm from Germany and don't know any of the master/user passwords on the cmm computer. Feel free to PM me instructions if you don't want to post it on the forum. I know there used to be the FAQ about where to go into the files and change it.

Good evening, how can I calculate this angle? I created a theoretical plane by placing it at the intersection, but it gives me a result of 60° Any help is appreciated, thank you

Hallo, wie die Überschrift bereits sagt möchte ich die Ellipse als sekundären Bezug verwenden, aber sie bleibt weiter verdreht: Wie kann ich der Ellipse sagen das sie die Verdrehung vorgibt im Startwinkel?

It works well; we have one folder per CMM for the measurement points and results. The base... is local on the CMM PC anyway. Like @Richard Shomakersaid, it’s just a matter of measuring simultaneously.

Hi everyone, I didn't even realize that GOM/Zeiss Inspect supports the 3D SpaceMouse. It would be great if they extended this support to VMR robot control as well. I have an idea regarding this; if you think it's a good one, please vote for it. https://portal.zeiss.com/my-voice/software/metrology/product/eaafdea8-9296-485d-82c1-cc6d1ca0eca2/request/e6a3c082-d85a-4fcb-a0e2-c9602e931f5f

As long as both users aren't actively trying to "program" at the same time - there are no issues with having the exact same measurement plan open at the exact same time. Though I would recommend that anyone who has operators should actively be using AutoRun instead of the native GUI of Calypso.

What happens when two or more CMM's have the same program open, maybe not at the same time, they could be seconds to hours apart from each other. For network control and running from the local drive, I created an interface that lets users copy files from the network location to the local drive. They can't delete or paste to the master network location, if edits are performed, they are logged in an excel workbook Rev History worksheet, the files are then moved to a "transfer folder" based on the CMM they were run on (In my case we have multiple versions installed), reviewed for the edits and either denied or approved. If edits are denied, the parts ran are reviewed for the results, if the edits are approved a designee moves the files to the master network folder, prior to the move the original is appended "- History (date) (Initials). History files are moved to a "#History" folder. Users login to the app, perform actions (all actions are logged) and file restrictions are handled in the app.

I see the minor diameter being controlled for location in the TP of .010, the actual thread is TP .000L typically by Pitch Diamter and the Pitch Diameter would allow for a tolerance for the modifier L. Also, you have a virtual shift condition for -F- based on the minor diameter tolerance. Chamfers are a product of the minor diameter drilled hole and are typically controlled from the title block with something like:

The **tempFileString** mentioned above is actually the App's UUID which you can find in the App's properties or its `metainfo.json` file (App Explorer).

Does anyone know if generateTabelColumn() is somehow able to control the position of a newly inserted column? (for example, insert as 15th column from the left) We want to import such a table to a CAQ system, and for this we need to order a custom import module. Now the manufacturer requests example files and I'm not even sure if the file I provide today will always look the same in the future, because I can't control where generateTable Column() puts a new column. Of course they could make the import module search for the column name first, but this would make it more complex, as in "more expensive".

Ein Versuch bisher: Je eine Seite wird mit einem Formwerkzeug hergestellt. Ich habe die Schräge oben und unten mit einer Geraden gescannt, einen Schnittpunkt gemacht für Z null und dann einen Punk für das Maß 21,2. Der Schnitt und der Punkt für 21,2 bilden ein Koordinatensystem von wo ich dann oben und unten einen Raumpunkt auf der schräge mache die genau 2,74mm ergeben. Danach eine Gerade daraus gemacht und den Rest dazu auszuwerten. Mal sehen wie stabil das funktioniert.

As far as as position on a countersink. You will presumably machine both the thread and csink at the same time, theoretically they should be close within a few tenths. Since they give you 0.235" max and a regular NASM csink for .138-32 helicoil is 0.180" - 0.210", you can give yourself a massive tolerance by machining the diameter within that range. Unless I got totally confused by LMC and how it works here.