20190424 FARO Arm Customer - Poor Scanning - We Found Multiple Issues

From ATTWiki
Revision as of 20:42, 24 April 2019 by Mcone (Talk | contribs)

(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to: navigation, search



Back to VTube-LASER

Contents

CUSTOMER ARM MODEL

  • FARO Arm
  • Edge
  • BluLaser Scanner

CUSTOMER ISSUE

The customer had trouble getting the FARO scanner working properly with VTube-LASER.

OUR DISCOVERY

  1. Driver was a non-approved older version (5.8.5.2). I updated to the latest version (6.3.1.5).
  2. VTube-LASER was slightly out of date. I updated to the latest version.
  3. FARO scanner alogorithm: Automatic Normal. Good.
  4. The FARO scanner setup had the reflectivity filter enabled. This must be disabled for VTube-LASER, or the scanner will not work well.
  5. The FARO scan density was set to 1/1 – which is higher than necessary. 1/16 is good for most parts. Changed the density to 1/16.
  6. There were two active cut planes but only one table surface. Rather than ask “why?” we explained that they only needed one Cut Plane. We deleted all the current cut planes and created a new one to be sure.

OUR ACTIONS

  1. We asked “what is your min diameter?” They said 3/16” - So I set their cut plane at 0.070 – which is about half of the min diameter.
  2. They were not using DCP. They did not know what it is. We explained it and its benefits, then set it ON by default. Also, we turned on DCP AUTO on by default.
  3. We noticed that Automatic Display of MASTER was not active. We turned it on by default and showed the benefits of using this new window.

RESULT

VTube-LASER measures perfectly