Requirements
In order to use PC-DMIS to scan your parts with an analog probe (SP600 or SP25), there are several requirements that need to be met.
SMP400 controller
Sheffield interfac.dll version 2.68 or higher
PC-DMIS Version 3.7 MR2
Calibrated CMM
Functionality
The chart below summarizes the available PC-DMIS scanning features and the status of their support on Sheffield CMM’s with the SMP400.
PC-DMIS SCAN TYPES | SUPPORTED? | NOTES |
LINEAROPEN | YES | The SMP400 only supports Line Technique (constant increment) and Spherical Boundary. |
LINEARCLOSED | YES | |
PATCH | YES | |
CIRCLE | YES | Open-loop and closed-loop. |
CYLINDER | YES | |
AXIS | YES | Closed-loop |
CENTER | YES | |
LINE | YES | |
ROTARY | NO | This is part of a future development effort. |
SECTION | NO | This is in the testing phase and is not released at this time. |
UV | NO | This is in the testing phase and is not released at this time. This is for Touch mode only. |
FREEFORM | NO | To implement this scan type requires defined scans which are not supported on the SMP400. |
PERIMETER | NO | To implement this scan type requires defined scans which are not supported on the SMP400. Closed-loop. |
Unsupported scan controls/methods
Boundary Types (Plane, Cylinder, Cone): Boundary conditions tell PC-DMIS when to stop a scan. Only the spherical boundary type is functional with the SMP400. Use of the other types may cause continuous and erroneous scans.
Control Points: Control Points are not supported, so variable scan speeds during a scan cannot be done. Scans performed at their initial speed end at that same speed.
Defined Scans: The Generate button, which allows you to define a scanning path to be overlaid upon the CAD, is not supported as it generates defined-type scans which the controller does not support.
Scanning Limitations
There is a 4000-point limitation in the Sheffield controller. Scans requiring more data must partially scan features and combine them to create the desired feature. No warning is issued when the buffer is full and the CMM continues the scan path even after the buffer has been filled.
ScanSpeed does not affect the Center scan; it is at a fixed speed determined by the controller.
Defined scans (where the actual nominal scan points are sent to the controller) are not supported.
OPEN/CLOSED LOOP Scanning
Currently, Open Loop only works with circular paths and features such as Circle and Cylinder. This does not refer to Linear Open and Linear Closed scans.
Feature Scans (for example, Circle, Cylinder, and Axis) are implemented as Open Loop scans. Other scans (Linear Open, Linear Closed, Center, Rotary) are implemented as Closed Loop. The final implementation is that the feature scans are Open Loop, and all other scan types are Closed Loop. The registry entry currently used is removed.
Controls over whether the executed scans are either Open or Closed are accomplished by editing the Settings Editor value: UseClosedLoop found in the Sheffield section.
If you wish to control the type of scan being performed for a measurement routine, you must quit PC-DMIS and launch the Settings Editor.
OPEN LOOP UseClosedLoop FALSE
CLOSED LOOP UseClosedLoop TRUE
There are no controls to change to Open or Closed with PC-DMIS commands, or by the loss of surface with an Open loop. The global value defined in the PC-DMIS Settings Editor application is a global default.
Scan Speeds
In order to scan in OPEN LOOP at speeds greater than 35 mm/s, you should define a repeatable alignment using more than the minimum number of points. If the scan begins and deflects at a value other than expected, there isn’t any method to reduce the speed automatically and scan in CLOSED LOOP.
You should not perform CLOSED LOOP scans faster than 20 mm/s on diameters 50 mm or smaller. This is application-specific but if you experience visible CMM vibrations and poor measurement results during a scan, you may be scanning the feature too fast for CLOSED LOOP.
To best apply all analog scanning applications, it is best to begin measuring the feature at the slowest speed possible and monitor performance and accuracy. Once you confirm acceptable performance and accuracy, increase the speed until you reach a point where you get acceptable measurement results without degraded accuracy in relation to speed.
Recommended Settings
Settings Editor
Settings Name | Recommended Value | Comment |
MovePositionTol | 1 | - |
MPHits | 1 | - |
MPVectors | 1 | - |
PointDensity | 4 | - |
ScanSpeed | 150 | ScanSpeed is the systems? MAXIMUM allowable scanning speed. |
SendProbeOffsets | TRUE | - |
SMP400Baud | 57600 or 115200 (recommended) | You can configure the baud rate settings on board the SMP400 by the jumper pin location. Contact Hardware Technical Support to change from 57600 to 115200. |
UpdateComm | FALSE | - |
UseVectorTouch | FALSE | - |
UseNewCancel | TRUE | - |
UsePartAlignment | FALSE | - |
Parameter Settings - Opt. Probe tab
Settings Name | Recommended Value | Comment |
# of Return Data | 0 | Set this to 0 (zero) to disable the controller-based scan filtering. PC-DMIS requires unfiltered scan data from the controller. Filtered data results in an undersized measurement. |
Positioning Accuracy | 10 | - |
Probing Accuracy | 1 | - |
PointDensity | See comment. | This represents the number of readings to record per mm. Since this is an application-specific setting, you may need to contact Hexagon Technical Support to set this value to a particular number. |
Offset Force | CMM Model Dependent | Set this value to 0.150 for an Endeavor CMM, or 0.250 for a Discovery or Apollo CMM. |