Name X

The line to change, if you want to make this macro aware of units, is the
MODULE IMMERGE MERGE_IMALIGN_PROJECT (, $imaprojname, 2, 0.2, "$imaprojname mesh",0.6, 0.18, 0.002,400,40,,,10,,,"Off")

All those values should be variables with user input. There is so many that a multiple parameter input is almost mandatory here...

Good luck!

Here is a macro I wrote a little over a year ago to process multiple IMAlign projects in a Workspace treeview.  ::)

Beware of the parameters used for merging, they are NOT unit independant, they are hard coded to finish the macro within a 1/2 hour (I cut corners when I did this...). You could improve this macro with a multiple parameter input for these parameters (can somebody do it and post it?).

Here is the macro:



version "4.0"

#Macro for merging multiple IMAlign projects one after the other.
#Start the macro in the workspace you want to process. It needs to be active workspace.

# Works with the current workspace. Will create a polygonal model for each IMAlign project in the treeview. Polygonals models will match
# the same order. If it is stopped, it can resume to the next on the list. It can also be started from the Nth IMAlign project: just make sure
# the number of Polygonal models in the treeview is one less than where you want to start merging...
# 2009-01-08 PWuser


DECLARE nbimalignproj 0
DECLARE nbPoly 0
DECLARE workspaceid
DECLARE projcounter 1
DECLARE imaprojname

MACRO INTERACTIVITY ("Off")

WORKSPACE PROPERTIES FILENAME GET(,workspaceid )
TREEVIEW IMALIGN_PROJECT GET_NB (nbimalignproj)
TREEVIEW POLYGONAL_MODEL GET_NB (nbPoly)

WHILE $projcounter <= $nbimalignproj
    if $projcounter > $nbPoly
        TREEVIEW SELECT NONE
        TREEVIEW IMALIGN_PROJECT SELECT ($projcounter)
        TREEVIEW IMALIGN_PROJECT GET_NAME ($projcounter, imaprojname)
        MODULE IMMERGE MERGE_IMALIGN_PROJECT (, $imaprojname, 2, 0.2, "$imaprojname mesh",0.6, 0.18, 0.002,400,40,,,10,,,"Off")
        ++ projcounter
    else
        ++ projcounter
    endif
ENDWHILE

Hello,

Smoothing within IMAlign is very aggressive indeed. What is your scanner (which brand and model)? What are your scanning parameters (Interpolation step and max distance)? When you aligned in IMAlign, you must have had a standard deviation calculation done over your scans... do you have a ballpark figure for the STDDEV?

It is rare that you need to smooth within IMAlign. What is your ultimate goal? You said you want to send an STP to machine.. Do you mean that you want to create surfaces in IMEdit and then export them as STEP to use in a CAD/CAM package and eventually manufacture using those surfaces?

If that is the case, then I recommend NOT to smooth within IMAlign.

In the process of reverse-engineering (this is what you are doing) you will create a polygonal model (by making your IMAlign project go through IMMerge and be transformed from a point cloud to a skin of triangles). In IMMerge, there will be smoothing available there (although you do not want to be too agressive there either).

After creating your polygonal model, it is possible to smooth within IMEdit. If you want to smooth the low curvature regions with a more aggressive value than the high curvature areas, you can use an advanced selection based on curvature and apply a different radius of filtering based on you selection.

It is an advanced way to smooth you scans that will treat high curvature areas (where there is a lot of shape like sharp edges and tight radii) differently and may give you a much better result overall.

If you plan on making surfaces and then export them to your CAD/CAM package, the fitting of surfaces also has a "smoothing" that can be applied. It's in the "Custom Fit NURBS Patches" that you have access to a "Boundary tolerance". If you bring up that value, you will see your curvature changes decreased, effectively smoothing the resulting surfaces. This is also an advanced way to "smooth" stuff before sending it to your machining software.

All this to say that you have other means of smoothing, not only the "smooth image" command in IMAlign.

Let us know what your plan is. If you are going to a training session, these advanced methods can be discussed at the end of the basic training material, there is always time for discussions on best practices and more advanced techniques at the end of training sessions. But you must first master the basic workflows before attempting to control advanced techniques... I never saw a good result when a 2 year old tried to run before learning how to walk...

Once you master the technique for walking (basic techniques show in the basic training), then you are ready to learn how to run (advanced techniques).

Hello,

Until there is an offset plane creation method, there is:
1- translate along normal in the Edit->Edit Numerically
2- Virtual surface on the Reference, type-in the offset value you want prior to creation of the plane

Extract from the Readme:
WHAT'S FIXED IN 11.0.14

General

* JT is a 3D data format developed by Siemens PLM Software and is used
for product visualization, collaboration, and CAD data exchange.
Starting with release 11.0.14, InnovMetric offers a new optional JT
translator capable of importing:

- JT files describing NURBS-based representations of CAD parts
and assemblies

- JT files containing polygonal models

A new File > Import Reference > JT File menu item is available in
IMInspect to browse JT CAD files. Polygonal JT files are imported or
exported by using a standard polygonal file browser in the IMInspect,
IMEdit, or IMAlign modules.

Access to the new JT translator technology is controlled by a license
key. The JT translator is available free of charge to corporate members
of the JT consortium on a valid support/maintenance contract. For
non-members, please contact your authorized PolyWorks representative for
a quotation.

* A new automatic viewpoint technology is released to enhance the
operator's capability of visualizing a laser scanning session performed
in the IMInspect or IMAlign module. The new technology has been
developed with three main purposes in mind:

- The operator wants to see the current laser line while
scanning or between two scan passes.

- The operator wants to control the orientation of the 3D Scene
with the laser scanner.

- Although the operator generally wants to have a close-up view
while scanning, it is also desirable to have a mechanism to
easily obtain a global view.

To meet these requirements, InnovMetric has designed an approach that
makes the operator feel as if he is holding a camera in his hand. The
3D Scene is displayed from the general point of view of the laser
scanner. On the other hand, the laser scanner is constantly moving as
the operator is scanning the surface. To ensure viewpoint stability and
optimal graphical performance, the viewpoint is only changed if the
current laser line becomes suddenly out of sight or if the scanner
orientation is significantly changed. When such an event occurs, a new
viewpoint is computed and a quick animation is generated to make a
smooth transition between the two camera viewpoints. The Dynamic drawing
type is used to accelerate the animation. Unacceptable computer
performances are automatically identified and the animation is switched
off if necessary.

In order to zoom out and get a global view of the laser scanning session
between two scan passes, the operator simply needs to move the scanner
backward, away from the digitized surface and beyond the scanner field
of view. InnovMetric monitors the incoming flow of valid 3D points from
the device. If the flow stops, the view is automatically zoomed out. To
go back to a close-up view, the operator simply needs to move the
scanner within its field of view.

Laser scanner dialog boxes offer an Options button. A new 'Automatic
viewpoint' section has been added to the General page of this Options
interface. Three parameters control the automatic viewpoint algorithm:

- The 'Device vertical axis' combo box specifies a reference
axis for the automatic viewpoint algorithm. The algorithm tries
to keep this axis as vertical as possible while computing
intelligent viewpoints.

- The 'Scan line close-up zoom (%)' parameter controls the size
of a laser scan line on the screen. It specifies that the laser
scan line will fill a given percentage of the 3D Scene graphical
window.

* When an IMInspect Project was duplicated in the Workspace Manager
(within a Copy-Paste workflow for example), properties of Device
positions could be lost. The issue has been resolved.

* Enhancements are released for the IGES and STEP readers.

* An issue with AC files containing empty scan lines has been resolved.

IMEdit

* Bug fixes are released for the watertight tessellation and NURBS
surface fitting algorithms.

* A patch picking issue has been fixed in the interactive mode to edit
the low-/high-curvature status of NURBS patches.

IMInspect

* The DMIS file import reader (File > Import Objects > From DMIS File)
has been modified. Objects without tolerances are now imported by
default. Users who need to preserve the old behavior - of not importing
objects without tolerances - can press the Options button in the DMIS
file browser and check the 'Exclude objects without a tolerance' option.

* A bug has been fixed in the import of composite IGES curves.

* Cropped planes written in IGES files are now correctly imported.

* A new automatic viewpoint technology is released to provide efficient
visualization while probing. The new technology has been developed
having two main purposes in mind:

- For each probing operation, there is a given area of interest
in the 3D Scene. This area should be in the middle of the
computer screen, or at the very least visible.

- For most probing contexts, there is a preferred orientation
that should be used to display the 3D Scene.

Within the context of the automatic viewpoint algorithm, there are three
categories of probing operations:

- Device-driven: The area of interest and preferred orientation
are set by the probe. If the probe does not provide orientation
information (if an SMR reflector is used for example), then the
current orientation is kept. The following probing operations
are device-driven:

+ Feature probing without nominal information
+ Surface and Boundary Point Cloud probing
+ Target probing

- Object-driven: The area of interest and preferred orientation
are set by IMInspect objects. The following probing operations
are object-driven:

+ Feature probing with nominal information
+ Comparison point probing
+ 6 Surface Points Alignment
+ RPS Alignment
+ Build/Inspect

- Hybrid: The area of interest is defined by IMInspect objects
and the orientation is defined by the device. The following
probing operations are hybrid:

+ Cross-section probing
+ Gauge probing

During a probing session, an operator may perform a variety of probing
operations on different objects. When the area of interest or preferred
orientation changes, a quick animation is automatically generated to
make a smooth transition between the previous and new 3D Scene
viewpoints. The animation is automatically switched off if the computer
performance is unacceptable.

The automatic viewpoint algorithm also manages zooming factors. In all
probing modes, a close-up view is used when the probe is close to a
specifically targeted object or if an object probing mode has started. A
zoomed-out global view is used when the probe is far from a targeted
object or between object probing operations.

A new 'Automatic Viewpoint' option page has been added under the Display
branch of the Probing Options interface. Users have access to the
following parameters:

- The 'Automatic viewpoint' check box enables/disables the use
of the automatic viewpoint algorithm.

- The 'Device vertical axis' combo box specifies a reference
axis for the automatic viewpoint algorithm. The algorithm tries
to keep this axis as vertical as possible while computing
intelligent viewpoints.

- The Overview 'Project zoom (%)' parameter controls the zoom
out factor used to produce a global view. It specifies that the
project will fill a given percentage of the 3D Scene graphical
window.

- The Close-up 'With nominal object - Object zoom (%)' parameter
controls the object size on the screen. It specifies that the
object will fill a given percentage of the 3D Scene graphical
window.

- The Close-up 'Without nominal object - Min visible length'
parameter controls the zooming factor when there are no nominal
objects. It specifies a minimum visible length in units.

* In the 'Auto-extract' tab of a Feature's Properties window, users can
press the Auto-Extract Options button to set a value for the 'Shrink
nominal by' parameter. This parameter is used to exclude data points
that are too close to a feature's outer boundary. In release 11.0.14,
'Shrink nominal by' is now supported for trimmed cones, cylinders, and
spheres.

* IMInspect now offers the possibility of probing uncompensated vectors.
When a Vector creation method is set to Probe, two sub-methods are
available: Compensated and Uncompensated. The second sub-method should
be used to probe uncompensated vectors.

* Special reflectors used with laser trackers now offer three tangent
compensation methods. In previous versions, users could use the
'Internal (Hole)' method to probe holes or 'External' method to probe
pins. The compensation point was only used to determine the normal
compensation direction. Starting from version 11.0.14, a new
'Compensation point' method is available. With the new method, the
compensation point is used to determine both normal and tangent
compensation directions.

* In the 'Probing parameters' tab of the 'Edit Measured Data Points'
interface, users of special reflectors are now able to independently
invert the normal and tangent compensation directions.

* IMInspect now supports tangent compensation for Vectors probed with
a special reflector. The compensation direction is set by a compensation
point.

* When a Reference Point object is bound to a point cloud Data object
along one axis, Calipers are internally used to match the reference
point to the measured point cloud. In the Alignment tab of a reference
point's Properties window, two parameters in the 'Adjustment on point
cloud' group box control these calipers. The 'Depth' parameter was
incorrectly used. The issue has been resolved.

* The retraction distance and fit depth Caliper adjustment parameters
were not scaled when changing units. The issue has been fixed.

* In some cases, the normal vectors of unfolded cylindrical/conical
cross-sections could be inverted. The issue has been resolved.

* The FEATURE PRIMITIVE REMAP_ON_CONE_CYLINDER command used to fold
selected points and polylines defined on the XY plane onto a cone or
cylinder has been renamed FEATURE PRIMITIVE CONE_CYLINDER_MAPPING FOLD.

* A new FEATURE PRIMITIVE CONE_CYLINDER_MAPPING UNFOLD command has been
added to unfold selected 3D points and polylines on the XY plane,
using the same mathematical techniques used to unfold a conical or
cylindrical cross-section.

Plug-ins

* A new plug-in is available in IMInspect and IMAlign for the
'Perceptron xyz' laser scanner. The plug-in is started by clicking on
menu item 'Plug-ins > Perceptron > xyz'. The plug-in interface is
similar to the Perceptron Contour Probe plug-in. Unlike the Contour
Probe scanner, the Perceptron xyz scanner is mounted on a CMM. As there
are no arm buttons available to start or stop a scanning pass, a new
button has been added to the right of the 'Start Scan' button. After
having pressed 'Start Scan', users need to press the Record button (red
circle) to start a scanning pass, then the Pause button to stop a
scanning pass. Once all scanning passes have been captured, the scanning
session is completed by pressing the 'End Scan' button.

* The Manual CMM plug-in now supports a new 'Renishaw UCCserver'
protocol to be used in conjunction with a Renishaw UCClite controller.

* In the 'Coordinate system' tab of the Manual CMM plug-in Properties
window, users have the capability of translating their coordinate system
by specifying new x, y, or z coordinates for the next probed point. In a
previous patch, a bug was introduced. As a result, the new coordinates
were always 0,0,0. The issue has been resolved.

* A bug has been fixed in the CimCore plug-in. A probed point was
automatically captured when manually changing the feature selection in
either the Define Measured or Build/Inspect dialog boxes.

* A 64-bit version of the CimCore plug-in is now available in the 64-bit
version of PolyWorks. In InnovMetric's FTP site (ftp.innovmetric.com),
new CimCore portable arm drivers can be found.

- For 32-bit platforms, download:

/pub/nt/drivers/Hexagon/WinRDS_5.3.4.zip

- For 64-bit platforms, download:

/pub/nt/drivers/Hexagon/WinRDS_5.3.4_x64.zip

* A Go XYZ is now automatically invoked by the Faro Laser Tracker
plug-in after the 'Orient to Gravity' operation has been invoked. If the
tracker was locked on a reflector, the laser is returned to the
reflector location. Otherwise, the laser is returned to its Home
position.

* A bug has been fixed in the implementation of the 'Go to XYZ Position'
operation for the TrackArm plug-in.

* A device position alignment bug has been fixed in the opening of an
IMInspect project measured with a TrackArm device.

* Communication issues between a TrackArm device and a Faro Laser
Tracker have been resolved.

Extract from the Readme:

WHAT'S FIXED IN 11.0.15

General

* Enhancements are released for the IGES and STEP readers.

* The zooming factor used by the laser scanning automatic viewpoint
method was not working in units other than millimeters. The bug has been
fixed. For those who have changed the 'Scan line close-up zoom (%)'
parameter in the past month, it is recommended to put back the default
value of 40, and then adjust the value again.

IMEdit

* A new menu item 'Edit > Curve > Create from NURBS Surfaces' and a new
button on the Curve Creation toolbar are available to create the curves
delimiting the selected surfaces of a NURBS Model object. Continuous
curves extending over several surfaces are automatically identified and
created as single curves. A 'Curve discontinuity angle' parameter is
available to merge adjacent curves only if they are continuous to each
other. Curves from a CAD model can be used to accelerate a NURBS
surfacing project.

* New volume measurement and slice area measurement algorithms are
introduced. The new volume measurement algorithm now computes an exact
solution. Both algorithms can now manage polygonal models or cross-
sections that are not watertight, in which case they will report an
approximate measurement result.

IMInspect

* Version R20SP3 of Spatial's CAD translators has been integrated. It is
a major release since it supports new releases of several major CAD
vendors:

- CATIA V5 R20
- Pro/E Wildfire 5
- UG NX 7

Note that the import of features and controls (PMI) from Pro/E Wildfire
5 and UG NX 7 files is not available at this stage.

* IMInspect now incorporates built-in ISO tolerance tables. ISO
tolerances are supported for the following feature controls:

- Circle diameter and radius
- Cylinder diameter and radius
- Rectangle height and width
- Slot width

In the Feature Controls interface, users can right-click under a
tolerance column and click the 'ISO Tolerance' item to enter an ISO
tolerance code. Once the OK button is pressed, IMInspect automatically
computes the tolerance by using the feature dimension, tolerance code,
and the appropriate tolerance table. ISO tolerances are also imported
from CATIA V5, Pro/E, and SAT features and controls and converted into
numerical tolerance values.

* The rendering of most curved features (Cones, Cylinders, Circles,
Ellipses, Slots) has been enhanced. The Sphere will be finalized in the
next patch.

* IMInspect now offers the possibility of probing Circles, Cones,
Cylinders, Ellipses, Planes, Spheres, and Vectors within two or more
probing sessions. This new feature is useful when a feature is so
large that it needs to be probed using multiple device positions. A new
menu item 'Add Probed Data Points' is available in a probed object's
popup menu or in the Feature menu of the main menu bar. The new function
operates on selected features or primitives. In the operation's dialog
box, users can select a primitive to be probed, define a fixed number of
points for the new probing session, or have access to a probing zone
configuration when it applies. Users should be aware that the
compensation offsets and directions of the first probed feature remain
the same for subsequent probing sessions. Therefore, the same probe or
reflector diameter must be used when adding probed points to an
already probed feature. Or, if a special reflector was used, a reflector
with the same normal and tangent offsets must be used.

* Several minor issues have been resolved in the automatic viewpoint
algorithm used while probing.

* Starting with release 11.0.11, the 'Max data-to-ref angle' of a
Comparison Point, that should only be used for computation on point
cloud datasets, was incorrectly used for probing. The issue has been
resolved.

* Users can now create a Circle resulting from the intersection of
two coaxial Cones. The new construction method is accessed through the
circle creation dialog box by setting the 'Method' to 'From
Intersection' and the 'Sub-method' to '2 Cones'.

* Users can now create Points resulting from the intersection of two
coplanar Circles. The new construction method is accessed through the
point creation dialog box by setting the 'Method' to 'From Intersection'
and the 'Sub-method' to '2 Circles'.

* The Polyline creation method 'From Data Error Contours' has been
enhanced. The polyline names now contain tokens that indicate the error
or tolerance of their corresponding contours in the color-mapped
display.

* The flexibility of the Build/Inspect mode has been enhanced. The
compensation settings have been removed from the dialog box and
transferred to the Build/Inspect horizontal pane under a new
'Compensation' column. Three compensation configuration are available:

- None
- Toward Object
- Inverted

When the 'Distance Type' is changed, the 'Compensation' settings are
automatically changed. By default, no compensation is done when
building a 'Center point', 'Axis', or 'Polyline'. And, the compensation
is done toward the object when a 'Boundary', 'Boundary (Tangent)', or
'Surface' is built. These default settings can be modified in a new
'Build/Inspect > Compensation' option page in IMInspect's global Options
interface.

* The Build/Inspect mode now supports special reflectors.

* IMInspect's Airfoil Gauge module offers a new functionality that
automatically computes the distances between adjacent airfoils on an
unfolded cylindrical cross-section. This new functionality is useful to
inspect an assembled ring of airfoils. The new method is accessed
through the macro command MEASURE GAUGE CALIPER FROM_CROSS_SECTIONS
INTER_AIRFOIL_DISTANCES. Please contact InnovMetric's technical support
for additional information.

Plug-ins

* A new 'Change Face' button is available on the Probing Device Control
toolbar.

* The Metris plug-ins have been renamed 'Nikon Metrology'.

The probe is larger than hole option should be used only if, physically, the probe sits on top of the hole.

The diameter of the circle is then calculated based on the probe's diameter and the distance to the constraining plane.

It is a very innacurate way of measuring a diameter. The center point of the circle is going to be OK, but the diameter may vary greatly depending on the bur on the edge of the hole.

Really, the best method to get accurate results is to change the compensation method to probe orientation instead of compensation point. Then you can get many points all around the inside of the hole. The arm is accurate enough that you do not have to have a great amount of movement for the precision to be good.

The new WinRDS for 64 bit machines is out and now functionnal in Polyworks.

I think you need to find a member who will make it there... And photocopy the business card... there may be more than 250 people. If you cound all the ivistors, exhebitors, friends and relatives, plus the Innovmetric employees, it's more than that.

Anyway, I thinks that's the best exposure you could get.

Try creating an autoformated report with the default layout, customize the background of both the title and first page (adding your logo, motto, name it!), delete all items (tables and snapshots) from the report and save it on the disk somewhere.

You can then set that saved layout as a template.

I think what "Firefly" means is to change the compensation method from compensation point (the default for all Faro devices) to Probe orientation, you do not need to place the probe at the center of your probed points to compensate.

The probe orientation compensation method means that you need to orient the shank of the probe so that it sticks out of the material. The compensation orientation is recorded on the first point only, all other points can be probed with any orientation.

Trying to probe a very "tight" hole (nearly the same diameter as your probe) is a nightmare when using a compensation point. Use the probe oreintation instead, in the "Device->Compensation method" section of the probing options.

Here is one other method:
The fit method has a sub-method called "pick then fit".

For a plane, you pick three points (make a plane) and polyworks will look for points with the same normal (within max angle) and within a proximity of the picke plane extended infinitely.

The same method is available for all features. The search distance is by default 1mm around the picke feature.

If you have a perfect STL, it should work.

The Automatic viewpoint had a bug in V11.0.14: the scale was 25.4 times too small when scanning in inches.

It has been fixed in V11.0.15, comming out just about now.

The latest patch just about to come out (11.0.15) fixes the units bug in the automatic viewpoint. A few other new things added, worth a download.

What should a good training on IMInspect/Probing include?

Should all methods of alignment be covered? How much time alloted for feature probing / Feature controls vs alignments vs probing comparison points, etc...?

Any suggestions?