Scanning - Stuck

[Joe_12345]

Evening all,

I'm doing a analogue scan along a surface that has some tight rads. I've noticed that a particular small rad of 2mm does not output all the points of that scan when i either A, ask for the profile, or B break out the scans as points. (please see the photo below of the issue i am getting). Im currently inspecting this profile with a 2mm ruby . The probe appears make full contact with the surface. I've changed to a 1.5mm to test but still have the same result.


im using an SM25 module to do so

https://i.ibb.co/g4w4HRZ/test1.jpg


Direction 1 tech set to line
Exec control set to defined
nominals method set to Find nominals, tolerance set at 4mm

Ive changed the exec controls to relearn to see if this is the issue as the probe might not be hitting the surface but this isnt the case. Ive uped the tolerance aswell just to see if this rad is way out but this again didn't change.

boundary type - plane, 2 crossings.

If i break the scan to points i am able to take a hit on all points as a touch probe
If i break the scan to points after scan execution then points are missing along the rad when i break out

the t values for this individual points are around 0.7 so they should be registered by the scan

Any suggestions would be great.

Thanks

[louisd]

do you have any filtering or outlier removal turned on for that scan? it's likely filtering or omitting the outliers.

[Joe_12345]

Not that i know of, I've never turned it on or had the need to turn it on. The only way i can see to access filtering is feature>construted>filter and calling the profile

These scans have just been reported using the profile dimension tool. Is there a filtering tool in the scan feature itself?

[louisd]

filtering applies to the constructed feature, not the dimension tool. Look towards the constructed scan, and confirm you don't have any filtering or outlier removal switched on.

[SingularitY]

The find noms tolerance shouldn't be that high. I would think for a 2mm ruby 2mm for find noms should be fine as long as your profile tolerance isn't close to +/-1mm.
Have you tried slowing down your acceleration and scan speed? What do you have it at currently?
I've never used relearn, only defined, so I don't know much about it. But I haven't had much issue with defined using an analog scanning probe.

[Ego Murphy]

Evening all,

I'm doing a analogue scan along a surface that has some tight rads. I've noticed that a particular small rad of 2mm does not output all the points of that scan when i either A, ask for the profile, or B break out the scans as points. (please see the photo below of the issue i am getting). Im currently inspecting this profile with a 2mm ruby . The probe appears make full contact with the surface. I've changed to a 1.5mm to test but still have the same result.


im using an SM25 module to do so

https://i.ibb.co/g4w4HRZ/test1.jpg


Direction 1 tech set to line
Exec control set to defined
nominals method set to Find nominals, tolerance set at 4mm

Ive changed the exec controls to relearn to see if this is the issue as the probe might not be hitting the surface but this isnt the case. Ive uped the tolerance aswell just to see if this rad is way out but this again didn't change.

boundary type - plane, 2 crossings.

If i break the scan to points i am able to take a hit on all points as a touch probe
If i break the scan to points after scan execution then points are missing along the rad when i break out

the t values for this individual points are around 0.7 so they should be registered by the scan

Any suggestions would be great.

Thanks

Your post is a good start - thank you for stating some of your scan settings.

However you are missing the 2 most important settings: Speed & Density.

Speed is a separate command called SCANSPEED, always millimeter per second even in Inch unit programs.
The OptionProbe statement controls Density, always points per millimeter of travel even in Inch unit programs
Both can be added by making changes in the Scan dialog, just be aware they are separate code items in your program.

Tight work = Slow Speed & High Density

Broad work = High Speed and Low Density

Your application sounds like tight work. Slow it down and densify the scan, let it crawl over the surface and explore it.
I have scanned tricky little things at a glacial 2mm/s and so-dense-it's-nearly-solid 50 points/mm.

~~~

Another issue could be the CAD surface that nominal are drawn from - a corrupt CAD surface can occasionally refuse to yield noms, and maybe someone clicked "Don't ask me again" on that error message.

[Joe_12345]

Great, thanks for all your help. I will modify and report back.