All Activity

Increasing Max. angle can bring more selected mesh. For bestfit - you can select areas on mesh, which can bring mesh into a correct position. If it's rotary part, then it will help only with rotation. Otherwise if you have problems with depth and or angle, then you can select only one mesh-cylinder for bestfit and measure only this one within bestfit alignment. You can select measured cylinder and in properties you can select to calculate it only in certain alignment.

Hi Martin, Thanks for fast response. Angle selection of fitting element U mean to play with the Max Angle in fitting element; Your second remark: I already have a pre alignment with best fit of full part. You say it will help if I create another best fit alignment based on area's on datums or area around it? This means I have to select MESH data manually with select through surface and make a new best fit alignment? This scanning program needs to run via kiosk without any manual steps, is this possible?

You can play with angle selection of fitting element. Also you can use bestfit on certain areas of a mesh to improve CAD<->mesh fitting

Currently we are validating geometric quality of 3D printed parts with narrow tolerances. On TPD drawing datum system ABC is applied on small planes/cylinders for long parts. I tried to gather as much mesh on or in these spots so that the fitted planes and cylinders are as reliable as possible. Before the ABC alignment a pre alignment is set where the whole part is best fit. I notice that whenever I rescan the same item, the results of position accuracy tolerancies vary and in some occasions lead to out of specs. My question is via which ways I can improve the fitting of small cylinders? Sometimes the fit results in a slightly different direction and has big impact on all other measurements. I read on internet that a possible solution is to make sections where circles can be fit. With these circles I can construct a more reliable cylinder.

Funny enough, when you ask chatgpt about MIBA errors now. Its like "oh and also here is how to change the background color" for no reason whatsoever other than Jeff asked a bonus question three years ago 😄 😄😄

I think you have to just iterate through scans and measurements. I can not verify this but something similar should do the trick: for mserie in gom.app.project.measurement_series: for measurement in mserie.measurements: left = gom.api.project.get_image_acquisition (measurement, 'left camera', [0])[0] right = gom.api.project.get_image_acquisition (measurement, 'right camera', [0])[0] Also you can use numbers instead of names ( example: gom.app.project.measurement_series[0] instead ...measurement_series['Scan1'] ) I often checking results via print to see what is in there.

Übungswürfel_Zeichnung.tif

Hello everyone, There have been changes to the technical drawing and a D reference has been added. Along with this, the runout value has also changed. I need to check the runout based on 2 plane points and one cylinder point. In Calyso, I can select 2 references for runout: 1 plane and 1 cylinder. I haven't seen 2 different plane points for runout before. I'm using Calyso 2021. Could this be related to the new GD&T? Benim düşüncem,

I've created a python scrip that access the image acquisition for each scan to extract a circular object. I'm doing this many times <100 for a part so this lends itself to automation. The issue is that the background changes across the part - while the object i'm extracting stays the same. From what i understand the image i'm accessing as the default exposure associated with it, or maybe the first. But the scans that i've taken have more than one. How do I access these additional images? I am using the way the scripting documentation shows how to access them to begin with: left = gom.api.project.get_image_acquisition (measurement, 'left camera', [0])[0] right = gom.api.project.get_image_acquisition (measurement, 'right camera', [0])[0] The measurements here are taken from one of the measurements in the series - generally more than 10 of them: scanImages = gom.app.project.measurement_series[measurement_series_name].measurements Can someone help point me in the direction if i'm going down the wrong path. ideally i'd like to use the different exposures to threshold out the object i'm looking for instead of forcing something from the base exposure.

Richard - I'll give that a try. Thanks. Ivan - That would still be a pre-defined starting point. It would be the same as the original scenario except now it would be in a different spot. It still wouldn't be a true best fit. A best fit allows the bolt circle centerpoint to move around so that all of the error from all of the individual holes is minimized. That will give a better picture than just an average, or a location to a pre-defined point. Make sense? Did I explain that sufficiently? Hope that helped.

@Andrew. L CAD files are here ---> "C:\Users\Public\Documents\Zeiss\CALYPSO\cad" on your CMM desktop computer.

Could you not add a special alignment offset/rotation? See my screenshot below. This offset allowed me to reposition the nominals to be 0,0.

The way I was reading balloon 2101 is that the surface has the UOS and an "additional" requirement. The first requirement (Note 7) would be: PROFILE| .040 U .030|A|B|C The second requirement (Note 17) would depend on what "MEASURED SURFACE" means. If measured surface = nominal surface, then size and form would be controlled by: PROFILE| .015 U .015| to no datums. if measured surface = actual surface, then only form would be controlled by: DYNAMIC PROFILE| .015| to no datums. The surface would need to be inside both profile tolerance zones.

If you switch over to Loose, you can use Alignments and then apply Best-Fit constraints.

Ya, that's what I thought. I'm going to use the constructed bolt circle as the center. Although it won't be a true best fit, it should get me reasonably close.

Hello 🙂 I am just starting out with Calypso on an O-INSPECT machine. Could you tell me if the only way to duplicate a line (for example, to create a parallel line at a distance of 10 mm) is to copy it and modify its Y or X origin? Or is there a specific construction method for this? I ask because when I copy a "virtual" line, the camera moves to that location, but there is nothing there. If duplicating and modifying the origin is the only way, how do I include an unmeasured/dummy element in PiWeb? Thanks, and have a great day.

Can you please walk me thru what strategy I would use for the dimple so that I can clock to it? I do have a 1mm star probe and regular probe as well as some larger straight probes. I want to probe the dimple and have it find the center like how it does when you locate the probe rack, but I don't know how to do that. The dimple is much to small to do the strategies I would use if it were bigger.

Just FYI a new service pack just dropped and it looks like there are several fixes for simulation. Downloading now!

None that I'm aware of, short of putting a bogus secondary datum in there.

Any way to fix it?

It goes to the center of the DRF. If you only have a Plane as the Primary, then it will go to the center of the plane. Very annoying indeed.

Hi everyone, I am looking for the PDF drawings and CAD files for the following parts. Unfortunately, I can no longer locate my files. Would anyone be able to share them? Any help is greatly appreciated!

So I looks like they expect a very rough surface texture and they want a .015 band of surface variation ignored. If that's the case, then I think you want some type of data filtering to happen.

This is very true. They were recently bought by MiniTab. At first, I was like great, we'll get a bunch of nice MiniTab integrations. BUT NO. All they changed was switching from a perpetual license to a subscription model. Legacy clients like myself are unaffected. But I don't see any reason to upgrade ever. I'm sticking to version 4.1 and 4.3 for life.

Hi, please try to use the App "Export Volume as Slices" from our Software Store to export the volume data into a set of TIFF images. -> https://software-store.zeiss.com/de/products/apps/export-volume-as-slices Best, Lorenz