is it possible to program/operate using the scaning function (linear/patch/perimeter) with a TP20 probe? And if so does it actually drag the probe or take single points? and is it worth using it for a large surface or should i stick to single points? Thanks.
I played around with it a little bit. I haven't written it off yet as pointless but my first impression is that it was clumsy and harder to manage than individual points. I didn't really see a huge benefit to going stitch scan vs just taking the points and constructing the features other than cleaner code and graphics window. (But I can group the points to clean up the code window)
I'll readily admit though that I'm not an authority on this part of PC-DMIS and there's a good chance I just need to learn it better to see the major benefit.
I played around with it a little bit. I haven't written it off yet as pointless but my first impression is that it was clumsy and harder to manage than individual points. I didn't really see a huge benefit to going stitch scan vs just taking the points and constructing the features other than cleaner code and graphics window. (But I can group the points to clean up the code window)
I'll readily admit though that I'm not an authority on this part of PC-DMIS and there's a good chance I just need to learn it better to see the major benefit.
I think it depends on how many points you are taking and on what kind of surface. Yes taking single points and then constructing them is very versatile, can place them where you want and exactly how many you want. However I find it is much easier to spread the points evenly across a surface when using the scanning options. It will also take the points faster than if you took 100 single points compared to 100 points in a scan. Not to mention the programming time is reduced when using a scan compared to single points, and this gives more benefit when the points used increases.
Learning to use the scanning functions well can be a pain but I think in the end it does pay off, especially if you are measuring lots of surface profiles.
TP20 is a touch trigger probe so it is not a scanning probe (one that drags along a surface).
If you have CAD available scanning is good to use and is very efficient in my opinion
I uses linear scans and perimeter scans daily.
How much point density you use has a huge impact on time through and at times points work well. But when I am following a perimeter with odd geometry especially curves and surfaces or flat areas with projected features or features cut out. Following the geometry and avoiding areas work well. A true benefit is updated or change to a scan. F9 scan make change , regenerate done. If you have 15 points that make up that scan now you have to do that 15 times. That is a small short scan example. Scanning has it's own issues here and there as well as I have had issues with CAD surfaces not playing well. I have had to integrate points with scans to get the coverage desired.
Like everything in this job it is a tool to use and works well and effectively when used in the correct circumstances.
There are often times when I could do it this way or that way. How many points do you use is a common question. FCF callout and accuracy desired along with manufacturing methods as well as throughput time and other conversations with engineering and customers drive all of these.
