All Activity

Thanks Karsten I'll check with our IT department to see what might be blocking access to the (local) file. Note: For this particular part, we cleaned up the entries in PiWeb and reloaded all measurements as a workaround.

Wonderful!

Hi, Looks to me a file /directory access issue. If you use the standard method of store the PiWeb data, the data is stored local in a SQLite database file. The name of the file is the same as the program name. If the previous file is not visible at the moment the file should be extended, a new one will be created. Check the creation time of these three files. If you use central PiWeb DB ( small business/Enterprise ) you have an issue while uploading the PiWeb Data from your local machine. In general it should be easy to merge the data to one DB-file. But this need a internal knowledge of the Db structure which is not documented. I´m sure ZEISS has it´s own merge tool. Ask them for service.

Are you talking about assembling CMM stylus systems? We are a busy high production shop and I would be very hesitant to let anyone else but those that program on the CMM's (me and one other guy) the access and ability to create stylus systems and switch out stylus probes for a lot of different reasons. How often are you finding you need to build or swap out probes and stylus systems and why are people that seem to have no grasp on the delicate nature of building CMM stylus systems allowed to create them? Who creates them in the software and qualifies them after they are built? Not including the master probe we have two basic stylus setups that cover about 90% of what we do on our Duramax VAST XXT CMMs, a straight probe and a star probe, and a few odd ones for specific jobs as needed. It very well may not be realistic for your purposes but If you are able to minimize the amount of stylus systems used in programming you may get away with not having to build as many and have less chance of error? I couldn't find any "single pin spanner" tools in a brief search or know how they would even work, just the torque screwdrivers and the fixed L-shaped pin wrenches but I did find some official (looks 3D printed) Zeiss plastic "XXT Stylii Assembly Pliers" that may prevent incorrect tightening and may be easier for whomever is assembling the stylii system to gauge the proper tightness: https://shop.metrology.zeiss.com/INTERSHOP/web/WFS/IMT-US-Site/en_US/-/USD/ViewProduct-Start?SKU=626109-0057-000&CategoryName=550000&CatalogID=500000&ExtendedNavigation=true

yeah.. not looking for the screw drivers.. can find those just about anywhere including zeiss... I am talking about the "single pin spanner" that is use to tighten the extensions and stylus to each other... I keep finding them either too loose or way overtighten to the point they are stripped.

endInspection() is better than cncBreak(). cncBreak will redlight the machine. There are cases though where cncBreak is the only thing that will stop a loop though.

@Lindsey Prestholdt GPT gives me this: wo = getRecordHead("u_Work_Order") IF STRLEN(wo) <> 10 THEN MESSAGE("WO must be exactly 10 characters.") STOP ENDIF Since the variable (wo) already exists ("u_Work_Order", entered manually at Run), you just need to validate it, not ask for it again. I do not have PCM to verify (might not be STOP, I think it is CNCBreak()?), but the logic makes sense. Been quite awhile since I have used PCM. From this core code, you can expand on it and enforce more rules (for instance, not allowing someone to just type '0000000000' 🤣)

@Marco Giraudo I did not know about the flipbook option, thank you! This is very useful.

Thanks for the responses. I too thought it was a strange requirement. Fortunately this is used internally so that'll be a few less hoops I need to jump through.

Got it. Was looking in the wrong place. Thanks.

for reference: https://www.gdandtbasics.com/angularity/

Jack, What do you select when you go to select one of the Datums with the new Engine?

Ok. Interesting. Thanks.

Richard, I'm using the latest version of Calypso and I don't see that option. Am I looking in the wrong place?

There are two different things - there is feature sorting optimization where Calypso attempts to reorder features in an optimal way to improve efficiency. This is found is Plan - Navigation - Sort Feature for Optimal Navigation. Then there is the Pallet Optimization where Calypso will look at the Pallet, and measure the entire Pallet with Stylus System #1, then swap to Stylus System #2 and measure the entire Palleter, and so-on and so-forth. This reduces the number of stylus system changes.

Incorrect. If you measure position of a circle, then yes you would just be looking at the center point location, but Calypso measures a true 3d Position on 3d features like Planes, Cylinder, Cones - so the axis line is verified for position. You even get a nice plot for it. 🙂

To a certain point I can understand why the committee wants us to use position. However now I have to wonder how Calypso determines the results. When you ask for position, doesn't it just give you the location of the features' origin? It doesn't account for the fact that the other end of the feature is pointed in a slightly different direction, right? When dealing with long features, this could make a big difference. So you'd have to add something like Total Runout to the report in addition to the position to get a better picture of what's going on, right? Or maybe add Profile? But either one of those two still doesn't tell you what the axis relationship is. They only tell you how much form error there is in relationship to the axis. Just seems easier to use Coaxiality and be done with it - It's also more representative of the intent. Glad Zeiss left us the Loose option.

If you are using the new GD&T engine Datum C would be a Common Datum, you will see the button inside of the feature selection. If you are creating this via the legacy GD&T engine you will need to create a Bore Pattern Best Fit - when Calypso creates a BPBF it will create a new alignment for you that you can use for other characteristics.

This is a misapplication of Angularity. I would just use Position, but you should speak with the Customer about this.

Be careful with Repeat commands because you do not have a break condition, so it will run indefinitely.

The not comparison is <> for PCM.

Hi everyone. I wanted to get some insight into how to properly measure the angularity for the missing tooth below. Based on my method, the value in simulation is not reading zero and I am not sure where I got it wrong. I did a test run on the machine last night and was getting similar actual values, nowhere near within tolerance. How I created the program. 1. Establish datums 2. Use self centered points on either side of the missing tooth. 3. Create symmetry point from them to find center. Project symmetry point to Datum D. 4. Create intersection between Datums D and E. Project point to D plane. 5. Create 3d line between symmetry point and projected center point. 6. Repeat process for Datum F 3d line. 7. Calculate the angle as 18.58482º and create angularity characteristic for the 3d line of the tooth, referencing the 3d line of FE as primary and D as secondary. When using D as primary, I get a different theoretical value that still is not zero. I was curious about using the GDT engine for this, but do not have any experience using those new characteristics. Currently using Calypso 2023. Any help is appreciated, TIA.

Without knowing the error a solution can´t be found 😉 I can only say that such kind of "manual mode" messages appear if you change from CALYPSO to GEAR PRO by using the Windows task bar instead of using the symbols in the CALYPSO and GEAR PRO menu bars for the change from software to software.

Hey Philpp, Thanks for sharing the commands. I have a question: where did you find them? They aren't listed in the user manual or the Help section. Best regards, Patrick

Correct - Concentricity/Coaxiality are no longer supported by ASME, so they are non-functional in the new engine if your set to ASME. Either switch to Loose, or use Position instead.