Why Does Trigger Only's Points Not Match the Required Amount on 3d Curve?

[[Ma...]]

Can someone shed some light as to what I might be doing wrong please?
I'm working offline to create a curve from a 2d line.
[list=]

I've created the 2d Line and measured it in Simulation mode.

• Created a 3d Curve and then recalled the 2d Line

• Then converted Actual to Nominal and created a segment which should consist of 73 Points to correlate with the Start Point and End Point

The thing is, I need this to be a Trigger Only Scan because of the surface I'm measuring. However, when I try to use a Trigger only and scan the surface, it appears to only measure half of the nominal points. When this is done as a scan, it measures all of the nominal points.

Where am I going wrong?!? Please help! 😱

Untitled 2.jpgUntitled.jpg

[[Ma...]]

I don't have offline seat, so i wonder if you tried it again if that glitch appears again. I think of software issue rather than yours. Try ZEISS

[[Ma...]]

Still having the same problem.
Anyone got any ideas what I'm doing wrong here?

[[Cl...]]

You stated;

"I've created the 2d Line and measured it in Simulation mode".

"Created a 3d Curve and then recalled the 2d Line".

I don't understand recalling a line into a curve? I would think it would be the other way round?
Also, should be a 2d curve, not a 3d. I would recall a 2d curve into a line.

[[Ma...]]

I'm measuring a conical sacrificial surface in 8 places located circumferential. There's no CAD model, so I've had to create the features manually from given Gauge Heights and nominal rads.
I could have used 2d curve, but we've found, historically, that some issues are created by using 2d Curves, so we tend to favour 3d Curves.
There doesn't seem to be an issue until I try to do touch trigger points to match the amount of nominal points. Scanning produces the correct scan I'd expect to see, but Touch Trigger only measures roughly half of the nominal points.

[[Ma...]]

Clarke pointed me to something. If you create curve from measured element, it will recalculate nominals of curve from measured points - but each basic element ( circle, planes, cylinders ,... ) is not evaluating first / last x points ( cca 0.5s ).
So how you created that 3d line? But this still not resolve why triger only is measuring half of points.

[[Ma...]]

We think we've solved it. I've been told by a lad at work to reduce the "End Point" by 1. So, instead of end point matching the number of points (In this case 73), the end point needs to be 72.
... no idea why this is, but it gets the results. Any idea as to why?

[[De...]]

Also the number of points should be 3 times the end point number.

[[Ma...]]

Please sign in to view this quote.

This only applies for scanning - not for trigger only.