Points Set Feature

[[Pe...]]

I'm new to the forum and apologize if this topic has been addressed. I'd like to first ask someone from Zeiss to review what I'm about to share as it is quite an oversight / mistake. I must use google to search the Zeiss forum do to the restrictions on the search within the forum. I am unaware how to search +feature + points +set, I simply get a message that states these words are too common. It's a serious flaw when you desire to search for the literal name given by Zeiss and cannot.

This question is focused on some more in depth detail regarding the feature Points Set and the creation of a simple point cloud using the standard software.

Here is where I'm at. I need to create points clouds to demonstrate profile compliance at a glance. I'm using recall feature points, selecting multiple features.

Issue 1: The feature points are not probe compensated and there appears to be no 'simple' work around. The help file is not very instructive.

Issue 2: I overcame issue 1 by adding best fit.
Issue 2a: What is best fit actually doing? I noticed that if I add 2 features one from Z one from Y, when best fit is hit they shift 'down and over'.
Issue 2c. Can I create a recall feature with probe compensated points then place that feature in the point set?

Issue 3: When I began adding 20+ features to the recall, something odd happened. The Points Set feature, for 6 plane features, copied all prior points. Some planes were very small, 4 points. Some planes were scans, 2000 points. It so happens that the 'merge points' tended to take a dozen scanned plans and add them to the 4 point feature. If you open the 4 point feature and look at the strat, only 4 points exist. When you turn on show actual, you see thousands. On the first feature glitch my points are 7000, when it glitches a 2nd time on a second feature, it's 14000. There was no apparent pattern to when the glitch happens.
Issue 3a. I have looked at every property I can think of, nothing seems out. Here is what seems very odd. When I add just the 'infected' feature to the point set, then go to evaluation so I can see the points, the points when hovered over with a mouse show the probe radius but the graphic is drawn in the correct place. When I hit evaluate with no best fit the points turn green. I created 4x simple plans using 3-6 points. 2 of the 4 are 'infected' with this error. If I add a non infected plane, the the evaluate shows the points above the surface by the probe radius, both in number and in graphics. Hitting evaluate turns them red.

Thank you for any wisdom and insight you can share.

[[Pe...]]

Some information to add... Zeiss if you are reading this, I believe this is a developer 'fix' in the points set feature that is problematic.

After some testing, I believe I have identified a change in behavior between features containing 4 or less points vs features with 5 or more points.

If I create a plane with 3 or 4 probe points, the point set graphically places the points on the solid surface. If you hover, the point displays the stylus radius. When I add a 5th point, execute, and refresh the points set, the 5 points magically jump up graphically. The reported numbers appear unchanged but they are most certainly different. Pressing Evaluate, one shows red the other green.

If you combine a scanned plane with a 1,2,3,4 point feature the point set appears to copy all points into the lower point count feature. If you open the lower point count feature and display actuals, many points are present.

If you probed a 6 point plane, add it to a point set, the graphics draw in the non comped position. If you edit the plane, delete 3 of the points but do not re-probe, the points set retains the 6 points, as soon as you clear and re probe the plane, the 3 points are graphically drawn on the surface, reported with a probe comp number, but evaluate green. A single point also behaves this same way.

It seems adding a feature to the points set behaves differently if the number of points entered is 4 or less. This feels intentional and as if a developer 'fixed' an issue with a hard coded condition. Perhaps the logic is single points will be probed and added. Since probe comping the points is not straight forward, perhaps the 'fix' was to hard code the probe compensation.

[[Pe...]]

More data to add...

Given the behavior observed, I thought maybe I could create a theoretical feature, recalling the low point count features, combining them into a single feature with a greater point count. I used the Recall Feature Points.

When adding the theoretical feature, if it includes a low point count feature, the points set blows an exception error.

[[Pe...]]

Found a few work arounds... but a new issue.

For the 2x 3 point planes, which are simple small areas where I'm only trying to display the Z value I created a Points Cloud (Point Set) Feature and added the problem planes. I then include that Point Set in the larger Point Set.

My understanding on point count is not complete. I wanted to create a point cloud around a pocket to satisfy a requirement to demonstrate profile compliance. I believed I could simply probe multiple points then grab the points using a point cloud.

1 - a single point added to a Point Set with Recall shows and reads the touch point.
2 - add a second point and to the Point Set and everything goes wrong. The evaluation shows 4 points. Opening the original single point shows 2x probed points, even although only one is defined. Add a 3rd point and you get 9. The behavior looks as if with each point added all prior feature points are added. Adding 8 points which were probed prior to adding results in 1700+ points in the point set under evaluation. Deleting actual points and looking at evaluation shows 64 points when only 8 point features are added.

Can someone please explain this?