All Activity

Measure "Circle on a Torus" in at least 6 locations (60 degree separation). Since you are using an XXT the initial point pickup will need a reverse over-scan for optimal accuracy (a second circle path that starts where the first ended and go back over the scan to pick up lost point data from stylus normalizing). Depending on size (hard to scale from image), it may be beneficial to constrain the size for optimal fitting. Do this in 6 places minimum with even distribution/spacing. Create a Point > Recall > Select 1 circle. (creates center point) Repeat for each circle scan path you created. Create a circle > Recall points > Select points you just created as center points for torus scans. Apply the runout control to the circle construction you've just created. There are ways you could do this with patterns and indexing as well but for ease of direction, I provided the generic manual steps. Alternatively you can scan around the torus D1 in 4-5 places (full diameter scans at different points on torus) and then create intersection planes to create a circle from feature points in as many places as you prefer without adding cycle time. Each approach has its benefits. One question comes to mind though: Are you sure the torus requires a runout check? This is not standard in most scenarios on a turned component as the end radii are usually clearancing and not sealing surfaces.

I skipped 2023, and went with 2024, as it's supposed to be a true 64 bit software, for more ram access. I had intended on going with 2025, but now not so sure. The simulation I did on 2027 went smoothly, so I have some hope. I did mess around some with 2025, for some reason I had to recreate all my machines from scratch, and put a number of some kind, at the end of the machine name, or I would get some weird error.

???

I wait until most of the complaints have dwindled away before I move to the newest or newer version. We are going to upgrade to v2023 soon from 2016, 2017 and 2022. I am still seeing issues with 2024 and specifically 2025 offline. I rely heavily on the offline working properly. For 2027, fuhgettaboutit 😄

This has always worked best for me.

I tried with a new project and it works! One question: is not possible to use a personal legend bar?

Maybe try to measure "Circle on a torus" in a few places and use runout of each of them? I think I've done it before.

Hi Marcel, Now i'm the one to reply late ☺ But many thanks for the feedback. We're still having the problem. We're not saving our reports from PiWeb, we upload our results as table files *.fet, *.chr, *hdr. These table files are grapped by our internal system. We only use Piweb during creation of our programs. This error only comes when we create new programs, if I run the "tactile_optical_adjustment_and_check_lin_V4.1_C7.4" from Zeiss, the report runs fine without any errors. I work with OI543 with RT-table and dotscan from 2024. The inserted clip below is from the inspection plan and as you wrote the error is listed in this file. Maybe a setting somewhere that needs a minor adjustment?

This is the result: ====================================================================== ARRAY: COORDINATES ====================================================================== Shape: (14, 1001483, 3) Dimensions: 3 Data type: float64 Total values: 42062286 FIRST 5 ROWS [[-3.77004521 -2.5909069 5.63548731] [-3.75618393 -2.57819015 5.61667638] [-3.74682975 -2.60982676 5.63127428] [-3.74232265 -2.56547339 5.59786546] [-3.73137834 -2.58936804 5.60604099]] ====================================================================== ARRAY: NORMALS ====================================================================== Shape: (14, 1001483, 3) Dimensions: 3 Data type: float64 Total values: 42062286 FIRST 5 ROWS [[0.51937824 0.47984293 0.70710468] [0.51937836 0.47984299 0.70710462] [0.5193944 0.47983545 0.70709789] [0.51939189 0.47983265 0.7071017 ] [0.51940525 0.47982848 0.70709467]] ====================================================================== ARRAY: SCALAR VALUES ====================================================================== Shape: (14, 1001483, 1) Dimensions: 3 Data type: float64 Total values: 14020762 FIRST 5 ROWS [[0.17371252] [0.19341013] [0.18066262] [0.21199106] [0.20574836]] ====================================================================== ARRAY: TRIANGLES ====================================================================== Shape: (14, 1728100, 3) Dimensions: 3 Data type: int32 Total values: 72580200 FIRST 5 ROWS [[1 0 2] [2 3 1] [2 4 3] [3 4 5] [4 2 7]] ====================================================================== SCALAR VALUE STATISTICS ====================================================================== STAGE: 0 Total values: 1001483 Valid values: 817004 Invalid values: 184479 Minimum: -0.9999836087226868 Maximum: 0.9999943971633911 Mean: 0.12506770972503356 Median: 0.007404788630083203 Std Dev: 0.33857524864327565 STAGE: 1 Total values: 1001483 Valid values: 810624 Invalid values: 190859 Minimum: -0.9997458457946777 Maximum: 0.9999995827674866 Mean: 0.12545123292840807 Median: 0.005641367053613067 Std Dev: 0.33820176809525915 STAGE: 2 Total values: 1001483 Valid values: 806167 Invalid values: 195316 Minimum: -0.9999976754188538 Maximum: 0.9999997615814209 Mean: 0.12822237201850964 Median: 0.008725213818252087 Std Dev: 0.33852532712616873 STAGE: 3 Total values: 1001483 Valid values: 799139 Invalid values: 202344 Minimum: -0.9999946355819702 Maximum: 0.9999998211860657 Mean: 0.11647757265726937 Median: 0.00733939977362752 Std Dev: 0.3346622895754618 STAGE: 4 Total values: 1001483 Valid values: 806319 Invalid values: 195164 Minimum: -0.999889612197876 Maximum: 0.9999955296516418 Mean: 0.12375207080038801 Median: 0.006627410184592009 Std Dev: 0.33557094342534866 STAGE: 5 Total values: 1001483 Valid values: 807133 Invalid values: 194350 Minimum: -0.9999645948410034 Maximum: 0.9999971389770508 Mean: 0.12766216929258173 Median: 0.012189929373562336 Std Dev: 0.34083237602395183 STAGE: 6 Total values: 1001483 Valid values: 805712 Invalid values: 195771 Minimum: -0.9999943375587463 Maximum: 0.9999861121177673 Mean: 0.1224781303949255 Median: 0.0034620233345776796 Std Dev: 0.34337158696471554 STAGE: 7 Total values: 1001483 Valid values: 810347 Invalid values: 191136 Minimum: -0.9998605847358704 Maximum: 0.9999995827674866 Mean: 0.1223609867846869 Median: 0.003429613308981061 Std Dev: 0.34028559250643153 STAGE: 8 Total values: 1001483 Valid values: 799807 Invalid values: 201676 Minimum: -0.9999169111251831 Maximum: 0.9999849796295166 Mean: 0.12175145579847788 Median: 0.009752480313181877 Std Dev: 0.3382057162990135 STAGE: 9 Total values: 1001483 Valid values: 804530 Invalid values: 196953 Minimum: -0.9998884797096252 Maximum: 0.9999997019767761 Mean: 0.1309860663740092 Median: 0.00888607557862997 Std Dev: 0.33682884009253805 STAGE: 10 Total values: 1001483 Valid values: 811783 Invalid values: 189700 Minimum: -0.9994982481002808 Maximum: 1.0 Mean: 0.12587793787982593 Median: 0.006889908574521542 Std Dev: 0.3386338362739185 STAGE: 11 Total values: 1001483 Valid values: 805351 Invalid values: 196132 Minimum: -0.9999029636383057 Maximum: 0.9999940991401672 Mean: 0.12458094398355302 Median: 0.007014192175120115 Std Dev: 0.3372293614642635 STAGE: 12 Total values: 1001483 Valid values: 813666 Invalid values: 187817 Minimum: -0.9999779462814331 Maximum: 0.9999937415122986 Mean: 0.12616119242940965 Median: 0.009973835200071335 Std Dev: 0.3362999554437092 STAGE: 13 Total values: 1001483 Valid values: 810213 Invalid values: 191270 Minimum: -0.99960857629776 Maximum: 0.9999967217445374 Mean: 0.12320137626659115 Median: 0.008159889839589596 Std Dev: 0.3383606201434212 ====================================================================== MESH VALIDATION ====================================================================== STAGE: 0 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 1 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 2 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 3 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 4 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 5 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 6 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 7 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 8 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 9 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 10 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 11 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 12 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True STAGE: 13 Vertex count: 1001483 Triangle count: 1728100 Minimum index: 0 Maximum index: 1001482 Invalid indices: 0 Coordinate/normal match: True Coordinate/scalar match: True Array analysis complete.

Ok,it works. Thank you! 👍

Ich weiß nicht, ob das vielleicht was damit zu tun haben könnte (Auszug aus den Hinweisen in den Release Notes): So ganz verstehe ich den Absatz zwar nicht, aber ich poste es hier mal, weil man sowas ja gern überliest.

Then make symmetry line and you should be able to open GD&T ( looks like origin point ) and there is distance, where you can select from options. I usually select "Envelope" it's already show settings ( which is circumscribed or inscribed )

If you need a specific order all you can do is to either add a sort column like Martin decribed or to name your elements with a leading sort number. What we do is to put the drawing's bubble number in front of our measurement names.

Rente oder Ausstieg? 😏

You can sort the table by clicking on the column header of each column. You then get a little symbol in the the header field symbolising the sorting dicrection.

I have two lines, because distance is created with SCS.

You have to use GD&T linear distance. I have no idea what elements you have, but for this you would need to either create symmetry plane from two opposing planes or symmetry line from two opposing lines. Then on that symmetry you can use GD&T dimension, where you can set this. Also don't forget you have UF - united feature

Hello, how to create GN for 2-line distance? Thanks.

Do you have only actuals or nominals also? If you want to import measured data, you have to do it in same alignment as you captured them. I don't think you can polygonize them, but maybe i am wrong about that. In Inspect you don't move CAD model. You only modify mesh to fit alignment. If you need to alternate CAD model before making elements, then go to menu Operations -> Alignment -> something single and select translate or rotate. You have to enter old point and new point. You wil have to play with it a little to learn how it works.

What i did i modified table template to show dimension number from drawing. Since we use a lot QDAS, then for every dimension ( sometimes it's inside element, sometimes in exact dimension ) i enter keywords "qdas_k2001" and value. I placed this value to new first column and let sort by this. Otherwise it's sorting by name, but also by that icon, so it's grouped by type of element.

Why not to use section for circle or 6 planes to have cylinder? Then fitting method and use Chebyshev inside/outside or other methods there? If you insist from those six points, then make auto circle or fitting circle, then select all 6 points in tree and right click "Select all points of element" - then you have to select same method as i described at the beggining

Er meint auf "Manuelle Ausrichtung" umschalten

Das größte Problem, das ich derzeit mit unserem O-Inspect habe, betrifft die Kamera in Calypso-Version 2027. Sie funktioniert einwandfrei mit neuen Programmen, aber wenn ich Programme lade, die in Version 2025 erstellt wurden, kann die Kamera nicht initialisiert werden.

Hi Martin, I'm all set. I was able to figure out how to edit the header/Part name. Thanks for your support.

I need to organize the elements in the table so that my reports dimensions appear in the correct sequence. Currently, they are listed out of order (1,4,2,5,3, ect.). How can I organize the elements so the dimensions are reported in the proper order?