PolyWorksMS2021 ReleaseNotes EN
PolyWorksMS2021 ReleaseNotes EN
SmartGD&T is a trademark of Multi Metrics Inc. NX is a trademark or registered trademark of Siemens Digital
Industries Software Inc. or its subsidiaries in the United States and in other countries. Teamcenter is a trademark
or registered trademark of Siemens Digital Industries Software Inc. or its subsidiaries in the United States and in
other countries. All other trademarks are the property of their respective owners.
This manual, as well as the software described in it, is furnished under license and may be used or copied only in
accordance with the terms of such license. The content of this document is furnished for informational use only,
and is subject to change without notice. InnovMetric Software Inc. assumes no responsibility or liability for any
errors or inaccuracies that may appear in this document.
Except as permitted by such license, reproduction in whole or in part in any way without written permission from
InnovMetric Software is strictly prohibited.
Release Notes
2024/03/21
PolyWorks® Metrology Suite 2021
Contents
6 Compatibility
7 2021 IR11.10
7 2021 IR11.9
7 2021 IR11.8
7 2021 IR11.7
7 2021 IR11.6
7 2021 IR11.5
9 2021 IR11.4
9 2021 IR11.3
9 2021 IR11.2
9 2021 IR11.1
10 2021 IR11
11 2021 IR10
16 2021 IR9
20 2021 IR8.2
20 2021 IR8.1
20 2021 IR8
23 2021 IR7
29 2021 IR6.1
29 2021 IR6
35 2021 IR5
38 2021 IR4
57 2021 IR3.4
57 2021 IR3.3
57 2021 IR3.2
57 2021 IR3
65 2021 IR2.2
65 2021 IR2
67 2021 IR1.1
67 2021 IR1
Compatibility
The following table lists the compatibility with each version of the PolyWorks Metrology Suite at the time of
writing these release notes.
PolyWorks Ecosystem
PolyWorks Metrology
PolyWorks|AR,
Suite PolyWorks Metrology PolyWorks Collaborative
PolyWorks|DataLoop,
PolyWorks|Inspector Suite License Server Suite License Server
PolyWorks|PMI+Loop, and
PolyWorks|Modeler
PolyWorks|ReportLoop
Due to important improvements to PolyWorks|DataLoop Core, PolyWorks MS 2021 IR4 requires a 2021 IR4
DataLoop database and cannot connect to a previous version of DataLoop database.
2021 IR11.10
Fixed issue:
An issue with the CMM Leitz controller jogbox has been fixed. This issue impacted jogboxes that offer
the Orient functionality.
2021 IR11.9
Fixed issue:
A software freeze when connecting to a CMM Leitz controller has been fixed.
2021 IR11.8
Fixed issue:
Issues when scanning trimmed edge comparison points with the Nikon Metrology Laser Radar plug-in
have been fixed.
2021 IR11.7
Fixed issue:
An issue with boundary Data points not being created when using the Nikon Metrology Laser Radar plug-
in has been fixed.
2021 IR11.6
Fixed issue:
An issue with the MSCL command TREEVIEW OBJECT PROPERTIES TYPES GET has been fixed.
2021 IR11.5
As of November 2022, a required technological upgrade will unfortunately block the online download of license
keys in all versions of the PolyWorks® Metrology Suite up to 2022 IR2. Special intermediate versions have been
released to solve this problem: 2021 IR11.5, 2020 IR11.2, 2019 IR11.3, and 2018 IR12.5.
You are working with the PolyWorks Metrology Suite 2022 IR3 and later, or
Node-locked keys: clicking on Download License Keys Online with a connected dongle will display the
error message Cannot connect to the PolyWorks license key database.
Computer-locked keys: clicking on Online Activation… will display the message Your license keys could
not be activated online. Activate your license keys using the offline activation.
Solution #1: Install your license keys manually using the PolyWorks License Manager:
You can simply import/activate your license keys manually (offline methods):
Node-locked keys: import the license keys from a key file (.key). To obtain your license key file, contact your
PolyWorks provider.
If you prefer to continue using the online download of license keys, you can download and install a corrected
intermediate version that is compliant with your license:
Compatible with
PolyWorks Metrology Suite
technological upgrade
If you have any questions, please contact your local PolyWorks technical support provider.
2021 IR11.4
Fixed issue:
A software freeze when a tool change is detected while using a T-Probe with the Leica AT960/AT930 Laser
Tracker plug-in has been fixed.
2021 IR11.3
Fixed issue:
A software crash when using the Manual CMM plug-in with a serial connection has been fixed.
2021 IR11.2
Fixed issues:
2021 IR11.1
Fixed issues:
Improvements have been made to the I++ CMM plug-in for laser scanning with PC-DMIS.
Improvements to script execution speed have been made by adding MSCL commands to modify multiple
piece properties at the same time.
An issue when trying to download deleted data from PolyWorks|DataLoop has been fixed.
2021 IR11
PolyWorks|Inspector
Fixed issues:
When the selected measurement points were highlighted, the measurement points of other features
were also highlighted.
There was an issue when using slab features as tertiary datum features.
There was an issue when getting the latest device position from the workspace.
PolyWorks|Modeler
Fixed issue:
2021 IR10
General
The Chinese, Czech, French, German, Japanese, Korean, Polish, Portuguese, and Spanish user interfaces have
been updated.
PolyWorks|Inspector
When using the ISO standard, the fitting of a datum plane using
datum target areas is now performed using a Chebyshev fit instead
of a min/max fit. Items relating to this functionality have also be
added.
The Datum extraction depth text box has been added to the
Measurement tab of the properties of datum target areas
when the ISO standard is used. It specifies the depth to use
when extracting the datum from the first contact point.
The Datum extraction depth text box has been added in the
new Reference target areas section on the Objects >
Reference Targets page of the PolyWorks|Inspector Options
dialog box. It specifies the default value of the Datum
extraction depth parameters of datum target areas when the
ISO standard is used. The default value is 1.
When a feature is created using the Pick, then fit or Fit to elements submethod and its in-space orientation
cannot be determined using the point normal information, it is now determined using the fit type. When
using Min fitting, the feature is internal and, when using Max fitting, the feature is external.
Composite datum features can now be created from patterns of planes. Note that all planes included must
be parallel to each other.
The latest release of JT CAD import technology has been integrated. The following format can now be
imported:
Note that this improvement was introduced in the PolyWorks IR9 release.
It is now possible to obtain the Z.bench overall capacity and Z.bench potential capacity SPC statistic values by
using the existing MEASURE OBJECT_CONTROL_SPC STATISTIC GET macro script command.
Fixed issues:
When importing an object with a Macro Script measurement method from a project, the measurement
method and macro script are now properly imported.
An issue when changing the Data alignments property of a report item to select specific data alignments
has been fixed.
Issues with the STEP and IGES CAD model importers have been fixed.
Issues when importing GD&T controls from a SolidWorks CAD file have been fixed.
Fixed issues:
A software freeze has been fixed when using the Auto-Probe Measured function with the Leica AT400
Laser Tracker.
CMM plug-ins
The CNC CMM plug-in now supports standard Hexagon and Renishaw knuckle tool parts. Users can now add
knuckles to their tool definition, to measure features that are difficult to reach with a straight tool.
Knuckles are similar to extensions, but have one or two rotational joints depending on the model. This figure
shows the possible rotations (highlighted in orange) for one- and two-joint knuckles. Both one- and two-joint
knuckles are fully supported.
The user must therefore provide these angles when creating the tool, along with the mount rotation angle.
The mount rotation angle corresponds to the total angle of the mounting rotation and the upper knuckle joint
rotation angle if a knuckle is used. The new joint rotation angle corresponds to the lower knuckle joint
rotation. These parameters are offered when creating the tool.
The knuckle tool parts have been added to the list of available parts and can be added when creating the
tool in the Create Tool dialog box, offered through the Probing Device Properties dialog box.
Once the upper knuckle tool part has been added to the tool definition, the Mount rotation (deg) parameter
can be specified, as shown in (a).
Once the lower knuckle tool part has been added, the new Joint rotation (deg) parameter can be specified,
as shown in (b).
Both these parameters can be specified for individual tool parts. The parameters are therefore found under
the new Tool part group label, when the corresponding tool part is selected in the tool definition area. All
existing parameters relating to the entire tool are now found under the new Tool group label.
(a) (b)
When using the CNC CMM plug-in, measurements have been improved for the following tactile scanning
tools:
Renishaw SP25M tools with a Coord3 CC3-NT, Pantec Eagle, Wenzel WPC 2030, or Wenzel WPC 2040
machine controller.
Hexagon (HP-S-X*) and Leitz (LSP-*) tools, with a Hexagon or Leitz machine controller. Note that the tools
must be recalibrated for the improvements to apply.
PolyWorks|DataLoop
The new Tools > PolyWorks|DataLoop > Web Interface > Copy Link to Clipboard menu item, available in
PolyWorks|Inspector and PolyWorks|Reviewer when a PolyWorks|Inspector project is open, copies the link
to the current piece in PolyWorks|DataLoop Web Interface to the clipboard so it can be pasted elsewhere.
This item is also offered as the Copy Link to Clipboard button, as shown to the right, located in the View in
PolyWorks|DataLoop Web Interface split button on the Standard toolbar. Note that this improvement was
introduced in the PolyWorks IR9 release.
2021 IR9
General
PolyWorks|Inspector
When probing or CNC probing a feature in multiple steps in a sequence, the measurement point group name
and number, as well as the total number of groups to probe the feature, are now displayed in the name of
each step, as shown below.
The parameters are also offered through the Options for Adding Objects to Sequence menu button on
the 3D scene toolbar when editing the sequence and measurement path interactively.
Note that these new items are cleared by default, therefore changing the default assisted sequencing
behavior in PolyWorks 2021 IR9 and not allowing the assisted sequencing technology to create new tool
orientations or make changes to measurement point groups by default.
The precision of the collision avoidance has been improved for several probe components.
Fixed issues:
An issue with computing straightness on patterns of cylinders from their individual median lines has
been fixed.
The piece propagation could fail if the piece template contained a slab feature constructed from
dependent plane features.
A software freeze when uploading a project to PolyWorks|DataLoop while reviewing a control view has
been fixed.
The default user configuration folder could no longer be edited in the PolyWorks|Reviewer.
Issues when importing patterns of features from a CATIA file have been fixed.
PolyWorks|Modeler
The add-in used to import PolyWorks PWSF parametric sketch files into Autodesk Inventor now supports
versions 2021 and 2022 64-bit.
Fixed issue:
A software crash when probing with a V-Probe and the API laser tracker has been fixed.
CMM plug-ins
Several improvements were made to the 3D display of the Probing Device Properties dialog box, when using
the CNC CMM plug-in.
When creating and editing tools, the tips of a star stylus are now identified with labels in the 3D display
of the Probing Device Properties dialog box.
Several improvements were made to the mouse-based operations in the 3D display, so they are now
similar to the ones done in the 3D scene such as, translation, zoom, and rotation operations.
Fixed issue:
PolyWorks|Talisman
Fixed issues:
Unique device IDs are now generated in a different way, resulting in new values.
2021 IR8.2
Fixed issues:
A software crash when probing with the Leica Laser Tracker or Leica AT400 Laser Tracker plug-in has been
fixed.
An issue with the Faro Arm and Laser Line Probe plug-in preventing probed points timestamps from
being captured and causing the Localize Device operation to fail was fixed.
2021 IR8.1
Fixed issue:
2021 IR8
General
The Czech, German, Japanese, Korean, and Turkish user interfaces have been updated.
PolyWorks Metrology Suite 2021 – the last major release to support floating licenses on USB dongles
PolyWorks Metrology Suite License Server 2022 will no longer support a USB dongle for floating licenses. We
therefore wish to inform you that as of version 2022 of PolyWorks Metrology Suite, floating licenses will
require linking to the MAC address of the computer hosting the license server.
If you are using floating licenses on USB dongles, you will need to install a new license key file to use
PolyWorks Metrology Suite 2022. Note that the compatibility is maintained between floating licenses on USB
dongles and the 2021 or earlier releases.
For more information or to obtain your new license key file, contact your PolyWorks provider.
The latest release of Spatial’s 3D InterOp CAD import technology supports four additional formats. Like many
other software providers, Spatial must end support for Windows 7 for some technologies. Therefore, from
version 2021 IR8 of PolyWorks Metrology Suite, the CATIA V5 importation requires Windows 10 Pro. We
remind you that PolyWorks Metrology Suite 2021 is the last major release to support Windows 7 and 8.1.
PolyWorks|Inspector
When CNC probing rectangles, the longest side of the rectangle is now measured first. For projects created
before this version, the shortest side is still measured first to preserve the measurement sequence.
The latest release of Spatial’s 3D InterOp CAD import technology has been integrated. The following formats
can now be imported:
NX 1980
Parasolid 34.0
Creo 8.0
SolidWorks 2022 (PMI for this version will be supported in an upcoming release)
Fixed issues:
Macro files in a workspace could be emptied (size of 0 KB) after uploading the workspace to
PolyWorks|DataLoop.
A failure to open PolyWorks 2019 workspaces in PolyWorks 2021 IR3 has been fixed.
A crash when changing the measurement method of a Data object has been fixed.
Improvements to the residual mobility optimization of datum reference frames with no datum features
have been made.
An issue when using the >< Orientation Only GD&T modifier on a plane almost parallel to a datum plane
has been fixed.
A failure to export to PDF a formatted report containing a very large table has been fixed.
An issue when exporting to PDF a formatted report containing Japanese characters has been fixed.
Object measurement script parameters could be lost when updating the measurement script.
An issue when loading a color scale with the Load Application Settings option set to No has been fixed.
PolyWorks|Modeler
Fixed issue:
An issue with the Cut Holes in NURBS Model using Curves function has been fixed.
SDK 5.15.6.1 has been integrated into the API Radian Plus/Core (Omnitrac 2) Laser Tracker plug-in.
SDK 4.24.11.1 has been integrated into the API Radian Pro (Radian) Laser Tracker plug-in.
SDK 10.05.05.6082 has been integrated into the Nikon Metrology Laser Radar plug-in.
Fixed issue:
An issue in the Faro Probe and Scanner plug-in when using the device button to start scanning has been
fixed.
PolyWorks|DataLoop
The upload of data to PolyWorks|DataLoop can now be launched and managed as a background task using
macro commands. This allows the software to run other macro commands while the upload is performed.
To launch such uploads, add AS_BACKGROUND_TASK at the end of existing DATALOOP UPLOAD macro
commands.
2021 IR7
General
The Chinese, German, Italian, Polish, and Spanish user interfaces have been updated.
When using Microsoft Edge or Google Chrome as the default PDF reader, clicking the question mark symbol
in a PolyWorks dialog box now displays the appropriate section in the reference guide.
When opening a workspace that contains projects saved with a PolyWorks version that is no longer
supported, the message now informs the user which version of PolyWorks to use to convert the workspace
so that it can be opened in the current version.
PolyWorks|Inspector
In PolyWorks|Inspector 2021, measurement points for supported objects in a sequence can be split into
groups, making it possible to probe or CNC probe a feature in multiple steps. A variety of other steps can then
be inserted between groups of points to perform different operations, such as to use different tool
orientations. However, users could only manually split measurement points into groups in the Sequence
Editor pane once the objects had been inserted into a sequence.
It is now possible to manually split measurement points for a measurement object into multiple groups
outside of the measurement sequence in the Measurement Points pane. This allows users to first configure
the measurement of the objects, including the measurement point groups, before inserting the objects into
a sequence.
Adjustments have also been made to easily insert the measurement objects containing multiple
measurement point groups into a sequence.
Users can now manually split measurement points for a feature into groups in the Measurement Points
pane using the new Group Points button. This functionality is supported for line, plane, circle, ellipse,
cylinder, cone, and sphere features. It is not supported to group points for a local plane.
To group points for supported feature types, users can select the desired measurement points in the
pane and click the Group Points button to create a new group containing the selected points.
To guide the user in selecting the right measurement points, the points selected in the Measurement
Points pane are highlighted in the 3D scene. Here is an example in (a) for the Probe measurement
method and in (b) for the CNC Probe measurement method, showing that point 4 has been selected in
the Measurement Points pane.
(a) (b)
The new group of measurement points is created and displayed in the Measurement Points pane under
its respective group number, as shown in group 2 in the image, and the other groups for that feature are
displayed under their respective group number, as shown in group 1 in the image. Note that if a local
plane is used, the points for the local plane are automatically included in the first group of measurement
points of the object and cannot be moved to another group.
Once a new point group has been created, users can then edit the measurement points within that group
in the Measurement Points pane as they would for other measurement points. They can also create
additional groups of points from existing groups.
In addition, the existing Define from Probed Data Points, Anchor Measurement Points, and Pick Go
to Positions operations are now offered through the new Create Points menu button that has been
added to the vertical toolbar of the Measurement Points pane.
Adjustments were also made to easily insert those measurement objects into a measurement sequence.
If an object containing multiple point groups is inserted into a sequence, the number of steps
automatically inserted into the sequence corresponds to the number of point groups for that object, as
shown in (a), that have not been added to the sequence yet. Users can display the measurement points
in each group by expanding the step, as shown in (b).
(a) (b)
Fixed issues:
An issue causing a workspace to unnecessarily increase in size over time has been fixed.
An issue resulting in a software crash when opening a project in PolyWorks|Reviewer has been fixed.
The texture imported from an OBJ file was lost after saving and reopening a project.
Improvements have been made when optimizing GD&T controls using the Maximize number of in-
tolerance controls option button.
When controlling the Surface Profile of planes with plane datum features, switching between separate
and simultaneous requirements could give incorrect results.
An issue when using a composite Surface Profile control with datum targets has been fixed.
Editing a caliper tip radius could lead to a long project update. The issue has been fixed.
Some measurement sequence macro commands could return translated command arguments.
Issues with the STEP and IGES CAD model importers have been fixed.
The report table of an unmeasured Best-Fit Measurement Objects data alignment could report
deviations. The issue has been fixed and no deviations are now reported.
An issue when picking rectangle features on CAD models has been fixed.
A software crash when creating a report table, due to invalid Data points, has been fixed.
Feature extraction parameters could unexpectedly change upon creating a mesh from source data
objects.
Add Selected Objects to Optimal Location in Sequence did not add the object to the sequence if the
optimal location was inside a sequence conditional statement.
Improvements have been made to the automated sequence generation for narrow passages.
The assisted sequencing technology could not compute a CNC path under specific circumstances when
the Locate center option was used.
The Edit Points and Delete Points functions were inactive in the Measurement Points pane if the pane
was opened from the Sequence Editor contextual menu.
The text in the Guiding Instructions is now retained if the user clicks out of PolyWorks|Inspector.
PolyWorks|Modeler
The add-in used to import PolyWorks PWSF parametric sketch files into SolidWorks now supports the
SolidWorks 2021 and 2022 64-bit version.
When using the MicroRidge plug-in, a new item is now offered to manually specify device units when they are
not automatically provided by the device. This new Device units (when not provided by the device) list box
is offered in the new More section of the Gauging Device Properties dialog box.
SDK 5.15.6.0 has been integrated into the API Radian Plus/Core (Omnitrac 2) Laser Tracker plug-in.
SDK 4.24.11.0 has been integrated into the API Radian Pro (Radian) Laser Tracker plug-in.
Fixed issues:
An Internal Error message could appear when connecting to the Creaform VXprobe plug-in.
CMM plug-ins
The CNC CMM plug-in now supports the Wenzel Shapetracer 2 laser scanner, which is compatible with the
Wenzel WPC 2040 controller.
Wenzel laser profiles are now supported. The new option has been added to the Utilities section on the
General page of the Line Scan Options dialog box.
In the Scanner software section of the Scan dialog box, the device-specific Configuration button is
offered to enable the display of the laser profile configuration window and 2D view of the data acquired
by the scanner.
Fixed issues:
An issue, resulting in a disconnection with a Renishaw I++ CMM when the Troubleshoot Execution is
triggered by a collision, has been fixed.
When connected to an I++ CMM with an inferred head, there was no warning in the sequence when the
active tool orientation did not match the sequence context.
PolyWorks|DataLoop
Fixed issue:
The API URL was not completely visible when accessing the PolyWorks|DataLoop connection
parameters.
2021 IR6.1
Fixed issue:
A delay when connecting to Hexagon devices has been fixed. The issue had an impact on the Hexagon
AS1 Absolute Scanner, Hexagon/Romer Absolute Arm, and Leica Absolute Scanner plug-ins.
2021 IR6
General
PolyWorks|Inspector
When using the Auto Range color scale method, the maximum and minimum values of the color scale range
limits are initially found automatically based on the highest and lowest deviation values of color-mapped
Data objects. These color scale range limits often have to be edited, for example to exclude values from
outliers, and could previously only be edited in the Edit Color Scale dialog box.
Intuitive new tools are now offered to interactively edit color scale range limits directly in the 3D scene when
using the Auto Range method. These tools can be used to efficiently edit the color scale Max value and Min
value, adjusting the color of objects in the 3D scene accordingly.
(a)
(b)
These new tools can be accessed by hovering the mouse pointer over the color scale in the 3D scene,
which now slightly changes the background color of the color scale, as shown in (a), and changes the
pointer, as shown in (b).
Users can then interactively edit the color scale Max value or Min value range limits depending on
where the mouse pointer is placed on the color scale. If the mouse pointer is in the upper half of the color
scale, the Max value can be increased or decreased. If the mouse pointer is in the bottom half of the
color scale, the Min value can be increased or decreased. This can be done the following ways:
Left-click and drag the mouse pointer up or down to increase or decrease the range limit.
Scroll the mouse wheel up or down to increase or decrease the range limit, which jumps to the next
numerical value according to the increments of the color scale.
Note that if 0.00 is in the middle of the color scale, it remains in the middle if adjustments are made.
Users can also quickly reset the color scale to the Automatic range limits, removing all previous
custom manipulations.
Additional items are offered to change the Conversion to colors method. Users can now also open
the Edit Color Scale dialog box by selecting the shortcut menu item, or double-clicking the color
scale.
Note that a color scale shortcut menu is now also offered when using the Use Customized Scale
method, as shown in (a), and when using the Use Object Tolerances method, as shown in (b).
(a) (b)
The minimum and maximum deviations functionality is now available for patterns of features. It displays the
minimum and maximum deviations of the whole pattern.
Combo boxes in list areas now offer a search box when they contain more than 15 items. This search box
allows typing in a string to find the desired item quickly and easily. An example is shown below.
Fixed issues:
The horizontal scroll bar was not shown when displaying more columns in the Edit Measured Points
interface.
Report items that are Not updatable were not deleted after a new piece was created.
A performance issue when creating a new piece in a project containing many data alignments has been
fixed.
When inserting objects into a measurement sequence, the popup dialog of the previous step could be
displayed.
When importing PMI information from a CATIA file, the NX INDIVIDUALLY note is now correctly imported.
Numerically measured comparison points did not show the Warning color when using the Object
Tolerances color map.
Deleted elements could return when creating a polygonal model from scanned meshes and then
changing units.
A warning message was no longer shown when defining measured device position targets that have
already been measured.
PolyWorks|Modeler
The add-in used to import PolyWorks PWSF parametric sketch files into CATIA now supports the CATIA V5-6
R2020 64-bit version.
Fixed issue:
A software crash when using the Cut Holes in NURBS Models using Curves function has been fixed.
Fixed issue:
A crash has been fixed in the Faro Laser Tracker plug-in. The issue appeared when connected to the Faro
Vantage Laser Tracker and using the 6Probe while changing the probe tip.
CMM plug-ins
When using the CNC CMM plug-in, it is now possible to create a tool with a star stylus that will be calibrated
in the inferred calibration mode (only with the PHS1 and PH10M-iQ probe heads). Each tip of the star stylus
must be calibrated individually. The calibration of a tip will be inferred on the other tool orientations of the
same tip.
The calibration of a probe head with a star stylus is only possible using the tip oriented in the same direction
as the tool.
Fixed issues:
An issue when setting CNC parameters with Leitz B3, B4, and B5 controllers has been fixed.
An issue causing the CMM to stop after calibrating or changing tool orientation has been fixed.
The XYZ tool orientation offsets in the Manual CMM plug-in could change when changing tool orientation,
alignment, or device position.
PolyWorks|DataLoop
When the PLM connection parameters are configured in PolyWorks|DataLoop Core, using a PolyWorks menu
item to import CAD models when connected to PolyWorks|DataLoop accesses the CAD models stored in the
PLM instead of the local files.
When importing a CAD model, the Connection to PLM dialog box is displayed. Enter a valid username and
password and Log In to open the CAD search window for the configured PLM. To access the CAD models
stored on the local computer, press Browse Local Files instead.
The visibility of the property when creating a new piece and the requirement to enter a value for a property
before uploading can now also be configured for properties not uploaded to PolyWorks|DataLoop. The
following changes have been made:
2021 IR5
General
The Chinese, Czech, French, German, Hungarian, Korean, Italian, Japanese, Polish, Portuguese, Russian, and
Spanish user interfaces have been updated.
As the latest versions of well-known Web browsers no longer support the FTP protocol, for security concerns,
we will no longer be offering FTP download links starting with PolyWorks® 2022.
Starting immediately, you can download products using our principal content delivery system that uses the
secure HTTPS protocol. Our HTTPS download links start by downloads.polyworks.com, which must be an
allowed URL for your network.
If you have any questions, you can reach out to us at: [email protected].
The PolyWorks|DataLoop Profiler is now available in all products of the PolyWorks Metrology Suite.
Fixed issues:
When using the search box in the option dialog boxes, clicking in the box would clear its content.
The & character could be duplicated in the search results in the option dialog boxes.
PolyWorks|Inspector
Improvements have been made to CNC probing to avoid potential collisions and better measure slots and
rectangles that are deviated compared to their nominals, as shown in a). After the first side of the slot or
rectangle is measured, the location of the remaining measurement points is now adjusted to follow the actual
position and orientation of the slot or rectangle, as shown in b).
(a)
(b)
The approach and retraction distance limits when measuring slots and rectangles have also been adjusted.
The measurement paths of slots and rectangles may be changed to adjust to these improvements.
Fixed issues:
Improvements have been made to the GD&T calculations when using the SN ISO modifier.
An issue with the GD&T residual mobility optimization using a single feature has been fixed.
Repeatability issues when computing the GD&T Surface Profile have been fixed.
Issues in the Geometry Controls pane when editing a pattern of features have been fixed.
A report snapshot update issue when replacing a Data object in a project containing a surface feature
has been fixed.
An error while meshing a polygonal model could result in an empty Data object.
The measured Data points could not be selected on features probed using the Hole Smaller than Probe
submethod.
Issues when splitting the measurement points of cylinders probed using the Use Initial Circles
submethod have been fixed.
CMM plug-ins
The CNC CMM plug-in now supports the Renishaw MCR20 tool changer with two, three, and four ports.
MCR20 has been renamed to MCR20 6 Ports.
Fixed issues:
The probe tip display could be inverted when using a zCat CMM with the I++ CMM plug-in.
Unpredictable motions on a zCat CMM could cause collisions with the part.
PolyWorks|DataLoop
Two new columns, Visible and Value Required, have also been
added to the table in the PolyWorks|DataLoop Properties dialog
box. They display the status of these two parameters for each of
the PolyWorks|DataLoop properties displayed. They are hidden
by default.
The performance of the upload of projects containing multiple control views has been improved.
Fixed issue:
Users are now warned when uploading a workspace or piece will result in a version upgrade.
2021 IR4
General
The Chinese, Czech, French, German, Hungarian, Italian, Russian, and Spanish user interfaces have been
updated.
PolyWorks|Inspector Essentials Premium and Standard Packages is available in Chinese, French, Italian,
Japanese, Portuguese, and Spanish.
CNC CMM Essentials for PolyWorks|Inspector Premium Package is available in Chinese, French, Italian,
Japanese, Portuguese, and Spanish.
PolyWorks|Modeler Light Essentials is available in Chinese, French, Japanese, Italian, Portuguese, and
Spanish.
There are currently over 700 options offered in the PolyWorks|Inspector Options dialog box, on almost 145
pages and subpages, and with more options being added every year.
To help users quickly find the option they are looking for, a powerful new options search tool is now offered
in the options dialog box. By typing a search query into the new options search box, users can now simply
click a search result to open the corresponding options page.
The new options search box is in the upper left corner of the options dialog box, over the options tree
view area, in PolyWorks|Inspector, PolyWorks|Reviewer, PolyWorks|Modeler, IMAlign, and the
Workspace Manager. The search tool can be used to quickly find any option.
Tabs and spaces delimit individual search terms. For example, a search for circle 5 would return
results containing circle and 5.
Search results are immediately displayed in a window as the user enters text into the search field. The
results are updated in real time as the search string is completed or refined. Option names and paths are
displayed in the search results window, as well as in the tooltip displayed when hovering the mouse over
an item in the list. Clicking the desired option in the list of search results opens the corresponding options
page. If no option items correspond to the search string, the message No results were found is displayed
in the window.
In addition, the existing global search tool in PolyWorks|Inspector and PolyWorks|Reviewer now also
provides option search results. The results are organized within the new Options section, which can be
collapsed or expanded. The number of hits for each section is displayed in parentheses. If a large number
of results are found, they are not all displayed. To see them all, click Show all or the [...] symbol.
PolyWorks|Inspector
The collision detection functionality has been improved and now includes the entire measurement path of
measurement objects. For touch probing, collisions are now detected during the approach and retraction
movements. For tactile scanning, the full measurement path is now considered.
Macro scripts are very useful to customize workflows and to automate repetitive tasks. In
PolyWorks|Inspector, users can now easily associate macro scripts with interactive events, without having to
modify the Visual Layout, by adding event triggers.
An event trigger is an association between an event, or PolyWorks|Inspector operation, and the macro script
that is to be automatically executed when that event occurs. Users can also specify whether the macro script
is automatically executed before or after the event.
For example, an event trigger could be added to require that users enter a password before being able to
delete objects. In this example, the event would be the Edit > Delete > Objects operation and the macro script
requiring that a password be entered could automatically be executed before that event occurs.
Once event triggers have been added, they can also be edited and deleted. Event triggers should also be
tested before using them to customize enterprise solutions. Note that the event trigger feature is in its beta
phase and will be improved in upcoming versions.
To add event triggers, select the Tools > Event Triggers (BETA) menu item and press the Add Event Triggers
button to add one or several event triggers that will be associated with the same macro script.
To create a new Event Trigger script, which is a new script type, users can click the Manage Macro
Scripts button, which provides quick access to the existing Macro Scripts dialog box where they can
create the script like they would for other types of scripts: giving the script a name and description as well
as defining custom parameters that can be edited. Three default parameters are provided and cannot be
edited:
Event name: Corresponds to the event selected in the tree view area of the Add Event Triggers dialog
box (e.g., Edit > Delete > Objects).
Script execution: Corresponds to the value specified in the Add Event Triggers dialog box.
Event parameters: Reserved for event-specific parameters such as the path of an imported file.
Note that the Macro Scripts dialog box now also offers the Manage Event Triggers button, providing
quick access to the Event Triggers (BETA) dialog box.
Once an Event Trigger script has been selected from the Macro script list box in the Add Event Triggers
dialog box, the associated parameters are also displayed and custom parameter values can be edited.
Once event triggers have been added, they are listed in the Event Triggers dialog box. Selected event triggers
can be edited or deleted if needed. Buttons are also offered to test the event triggers before use.
Event triggers can be edited by pressing the Edit button, which displays the Edit Event Triggers dialog
box. It offers many of the same parameters as the Add Triggers dialog box, which can all be modified
except for the list of events itself.
It is recommended that event triggers be tested before they are used. To do so, users can perform the
operation directly in PolyWorks|Inspector (e.g., by pressing the toolbar button), and the corresponding
event trigger will automatically execute the associated script either before or after the event. Three
buttons allow users to validate or change the associated macro script if needed:
Edit Macro Script: Opens the script associated with the selected event trigger for editing.
Run Macro Script: Fully executes the script without having to perform the operation itself in
PolyWorks|Inspector.
Step into Macro Script: Steps into the script to edit it more easily, without having to perform the
operation itself.
Once event triggers have been added and tested, users can go about their regular operations in
PolyWorks|Inspector. The script associated with each event will automatically be executed before or after the
associated PolyWorks|Inspector operation, as long as the operation is launched from:
- A keyboard shortcut
Note that if the execution of an event trigger script fails before an event, the associated event is not executed
either. The MACRO END ( "Error" ) command can also be used to intentionally get the same behavior, for
example to block an operation if the password entered is incorrect.
This beta release of the new event triggers feature has the following limitations:
We do not guarantee that the event triggers added during the beta version will work as is in the future
official version. They may even be incompatible in the future.
Event triggers on the File > Save Project operation are only executed when using the menu item directly.
They are not executed when, for example, the project is saved while opening another project or exiting
the application. The workaround is to add event triggers, using the same script, to those events as well.
Event triggers on File > New Project, File > Open Project, and File > Import operations are not executed when
starting PolyWorks|Inspector from the Workspace Manager.
Other improvements
In the PolyWorks 2021 major release, it became possible to probe features in multiple steps, allowing for the
probing or CNC probing of a feature using different tool orientations. However, the diameter of all the probe
tips, of the tools or star styli, as well as reflectors used to measure the feature had to be the same.
In PolyWorks 2021 IR4, it is now possible to measure a feature in multiple steps using probe tips or reflectors
of different diameters. Each of the probed points will then be compensated accordingly. Features that can be
probed in multiple steps are supported: circles, ellipses, lines, cones, planes, spheres, and cylinders. Special
reflectors are not supported.
The tip diameter used to probe each point can now be displayed in the new Probe Tip Diameter column on
both the Points and Points of local plane tabs of the Edit Measured Points dialog box. Note that if at least
one of the probe tips or reflectors used to measure a feature has a different diameter, it is not possible to
edit the diameters.
If multiple probe tip or reflector diameters are used, (multiple values) is displayed for the Probe tip
diameter parameter (shown in (a)) and the Reflector parameters (shown in (b)) on the Probing parameters
tab.
(a) (b)
The new Probe Tip Diameter column can also be displayed in the Edit Table dialog box, making it possible
to display the Tip Dia column in report tables.
The least-squares feature-fitting algorithms of PolyWorks Metrology Suite 2021 have been certified by PTB.
Some list boxes in tables now offer a search box when they contain more than 15 items. This search box
allows typing in a string to find the desired item quickly and easily.
The latest release of Spatial’s 3D InterOp CAD import technology has been integrated. The following format
can now be imported:
Inventor 2022
Fixed issues:
There was a software crash when loading a visual layout after creating a formatted report table.
The selection of an item in a list box was not possible if a search was done to filter the list box items.
There was a graphical issue in the Point Pairs alignment when object transparency was active.
The filtering of pieces did not work if the search key was an item in a list of possible property values.
A piece propagation issue in a project containing a Datum Reference Frame (DRF) alignment has been
fixed. This problem occurred when the user language was set to a language other than English.
A piece propagation issue in a project containing features with no controls has been fixed.
A piece propagation issue when using custom measurement objects has been fixed.
Changing a piece property did not immediately update report text fields using the property.
Piece properties could be modified in the Open Piece dialog box, but they were not applied.
There was a GD&T computation issue when a curve-based datum feature was secondary to an axis-
based feature.
The measured envelope of cylinder features should now have three contact points with the Data points.
A GD&T Position control could report different values when a different data alignment was active.
A DRF alignment issue with a secondary plane datum feature to an almost parallel axis-based datum
feature has been fixed.
Using a composite datum feature with simulated data could fail to compute GD&T results.
The Max Angle extraction parameter of polyline features was not initialized using the global setting.
Inverting the orientation of a line feature could cause the feature to lose the link to the measured Data
points.
Issues with the Measurement System Analysis toolbar have been fixed.
Issues with the IGES and STEP CAD model importers have been fixed.
A problem occurred when importing GD&T controls using the U modifier from a CATIA file.
The column titles of the Best-Fit Measurement Objects pane could be partly hidden in languages other
than English.
An internal error when selecting the Circle method for the creation of device position targets has been
fixed.
A software crash when selecting subsampled Data points has been fixed.
An internal error when anchoring trimmed or hemmed edge comparison points in a project with no
reference object has been fixed.
A point compensation issue when using the Thin material probing method has been fixed.
PolyWorks|Modeler
Fixed issues:
When morphing two models, the source objects could disappear from the 3D scene.
Several improvements have been made for the Hexagon AS1 Absolute Scanner/Laser Tracker plug-in:
New macro commands have been added to allow synchronization with a robotic arm while using a
Connect Box CB21:
When scanning with the Hexagon AS1 Absolute Scanner/Laser Tracker plug-in, the scanner is now
displayed as a wireframe outline in the 3D scene.
When using the Hexagon AS1 Absolute Scanner/Laser Tracker, Hexagon/Romer Absolute Arm, and Leica
Absolute Scanner plug-ins, it is now possible to control the visibility of the RDS agent window. The new Show
RDS agent check box, which allows users to select the visibility of the RDS agent window, has been added to
the following dialog boxes:
In the Utilities section of the General page of the Line Scan Options dialog box:
In the Probing Device Properties dialog box, for the Hexagon/Romer Absolute Arm:
For the Hexagon AS1 Absolute Scanner/Laser Tracker plug-in, a new macro command allows configuring the
connection identifier of the tracker used in RDS:
The feedback during a scanning operation has been improved for the Nikon Metrology Laser Radar plug-in.
Users are now informed during the operation, and not only at the end.
SDK 10.05.02.5967 has been integrated into the Nikon Metrology Laser Radar plug-in.
When using API Laser Tracker plug-ins, the button available on the vProbe2 and the iScan3D devices was
specifically used for acquiring data. Now, new functionalities have been added to this button.
When probing:
Double-clicking the button allows changing the acquisition mode (for example, from Single to
Continuous Time)
Pressing the button for more than 1.5 seconds allows undoing the last probed point
When scanning:
The following commands have been added to the API I-360/Tracker and the API iScan/Radian Plus Tracker
scanning devices. They allow users to automate a scanning operation, more specifically to start and end a
measurement session.
Fixed issues:
Spontaneous disconnections with the Leica TDRA6000 plug-in have been fixed.
A failure to connect to ScanWorks with the Perceptron ScanWorks Probing and Scanning plug-in has been
fixed.
When using the Creaform VXscan plug-in, PolyWorks|Inspector could close unexpectedly when closing
VX Elements.
CMM plug-ins
When using the I++ CMM plug-in and connected to the Renishaw UCCserver, the assisted sequencing
technology now automatically creates any missing tool orientations and inserts them into the active
measurement sequence. This can be useful when using the empirical calibration mode.
The new tool orientations that are created by the assisted sequencing technology are added to the list of
available tool orientations and should be calibrated on the server before use. Note that these improvements
are supported for UCCserver version 5.7 or later and that the Split tools and tool orientations property
must be selected.
An additional communication protocol is now offered for the Manual CMM plug-in. The new Insight
Metrology IMUSB100 protocol has been added to the list of protocols on the General tab of the Probing
Device Properties dialog box. Note the following:
The axes homing operation is supported. Users can also specify whether the machine axes have
reference markers.
Users can import PolyWorks volumetric compensation maps (.pwmap), shown in (b), as well as Wenzel
volumetric compensation maps (.vo2).
(a) (b)
When creating or editing a tool in the CNC CMM plug-in, names for tools using the HA-TT-A0, Hexagon HA-TT-
A30, HA-TT-A60, or HA-TT-A90 adapters now display the rotation angle degrees when Automatic is selected
in the Name list box.
New items were introduced in PolyWorks 2021 IR3 that allow users to display or hide star stylus labels. These
labels display star stylus tip numbers in the 3D scene. In PolyWorks 2021 IR4, a smart mechanism has been
developed to automatically hide those labels during certain modes when using the CNC Probe measurement
method and during operations where the CMM moves.
With the CNC CMM plug-in, it is now possible to use a predefined star stylus with a lower connector. The
following star styli are now supported:
Renishaw A-5000-7811
A-5003-4011
A-5003-4787
A-5003-4788
Hexagon 03969210
03969422
03969423
The following commands have been added to the CNC CMM and I++ CMM plug-ins. They allow controlling
the density of points along the tactile scanning path for a polyline tactile scanning operation.
The CNC CMM plug-in now supports the following Wenzel laser scanners and associated tool parts. Note that
these scanners are compatible with the Wenzel WPC 2040 controller.
Scanners WM | LS 50
WM | LS 70
WM | LS 150
Extensions WM | LS 50
WM | LS 70
WM | LS 150
The following new command is offered to define the dimensions of a scanner laser plane when an I++ server
provides invalid values (i.e., when a value is equal to 0 or is a percentage).
Fixed issues:
A temperature compensation issue when using the Hexagon FB2 controller has been fixed.
The display of the CMM table could shift during a tool orientation change.
PolyWorks|DataLoop
Due to important improvements to PolyWorks|DataLoop Core, PolyWorks MS 2021 IR4 requires a 2021 IR4
DataLoop database and cannot connect to a previous version of DataLoop database.
PolyWorks|DataLoop properties can now be used to easily manage the attributes of properties of a large
number of objects at the same time. A PolyWorks|DataLoop property can be linked to multiple objects, such
as projects and templates. This allows any changes made to the attributes of the PolyWorks|DataLoop
property to be automatically spread to the corresponding property of all linked objects.
PolyWorks|DataLoop properties
The PolyWorks|DataLoop Properties dialog box can be accessed through the Tools > PolyWorks|DataLoop >
Properties menu item in PolyWorks|Inspector or in the Workspace Manager. It allows creating, editing, and
deleting PolyWorks|DataLoop properties.
The Search box, at the top of the dialog box, allows searching for a string in the existing
PolyWorks|DataLoop properties and their attributes.
A table that lists all the existing PolyWorks|DataLoop properties. It contains the following columns:
Possible Values - Lists the possible values of each of the listed PolyWorks|DataLoop properties.
Tags - Lists the tags associated with each of the listed PolyWorks|DataLoop properties. Tags make
finding specific PolyWorks|DataLoop properties through searches and filtering easier.
Filters can be activated for each column by pressing the filter icon next to the column name. To clear all
filters, press the Clear filters button in the top right corner.
The Add property button creates a new PolyWorks|DataLoop property. When pressed, the Add
PolyWorks|DataLoop Property dialog box is displayed. It allows specifying the name, possible values and
The Edit property button edits a PolyWorks|DataLoop property. When pressed, the Edit
PolyWorks|DataLoop Property dialog box is displayed. It allows adding or deleting possible values and
tags from the selected PolyWorks|DataLoop property. Note that this dialog box can also be displayed by
double-clicking the desired property in the table.
The Remove property button deletes the selected PolyWorks|DataLoop property. Note that it is
possible to remove several properties at once.
Project properties
New elements have also been added to dialog boxes that allow editing the properties of projects, piece
templates or pieces in PolyWorks|Inspector to allow using PolyWorks|DataLoop properties. The following
element has been added to the Project Properties dialog box:
The Import Custom Properties from PolyWorks|DataLoop button, as shown to the right, allows
importing a custom PolyWorks|DataLoop property in the selected project, piece or template. When
pressed, the button opens the Import PolyWorks|DataLoop Properties dialog box, that allows selecting
the properties to import. Note that it is possible to import multiple properties at once.
Manage properties
The following changes have been made to the Manage Properties dialog box:
The properties table now contains a new column that displays an icon, as shown to the right, when a
property is linked to a PolyWorks|DataLoop property.
Another icon, as shown to the right, is displayed when the property is linked to a PolyWorks|DataLoop
property that can no longer be found on the server (i.e., if it was deleted).
The Edit button now displays the Edit PolyWorks|DataLoop Property dialog box when the selected
property is linked with a PolyWorks|DataLoop property.
The Unlink property from PolyWorks|DataLoop button unlinks the selected property from its
PolyWorks|DataLoop property.
Other improvements
Due to important improvements to PolyWorks|DataLoop Core, PolyWorks MS 2021 IR4 requires a 2021 IR4
DataLoop database and cannot connect to a previous version of DataLoop database.
The new DATALOOP OBJECT INFO GET macro command allows obtaining information on a
PolyWorks|DataLoop object using its unique PolyWorks|DataLoop ID. This information includes the name
and type of the object, as well as, if applicable, the unique PolyWorks|DataLoop ID of its parent object.
Improvements have been made to the PolyWorks|DataLoop search macro commands. The DATALOOP
SEARCH macro command now allows only searching for piece templates and only searching for pieces, as
well as selecting whether the search results should include all results containing the specified string or only
the results that match the specified string exactly.
The new DATALOOP SEARCH PROPERTY VALUE macro command allows searching for pieces or piece
templates by entering the value of one of their properties. It is also possible to specify the name of the
property in which to search for the specified value.
The Collaborative Suite License Server status web page can now be accessed from the Help >
PolyWorks|DataLoop > Collaborative Suite License Server Information menu item in all PolyWorks Metrology
Suite modules.
The new DATALOOP DISCUSSION MESSAGE SEND macro command allows sending a message on the
discussion thread of the current active PolyWorks|Inspector project. It is also possible to list users and groups
to be tagged in the message, so they will be notified in PolyWorks|DataLoop Web Interface when the
message is sent.
2021 IR3.4
Fixed issue:
A compatibility issue with the Faro Arm and Laser Line Probe plug-in when using driver versions prior to
6.9.3 has been fixed. Note that this issue was only present when using PolyWorks|Inspector version 2021
IR3.2.
2021 IR3.3
Fixed issue:
An issue when importing a CATIA CAD model with PMI information has been fixed.
2021 IR3.2
The Faro Arm and Laser Line Probe plug-in now better supports the Faro Quantum Max ScanArm. Users with
driver 6.9 or later can now mount the scanner to the front, making it possible to interchange probe and laser
scanner positions.
2021 IR3.1
Fixed issue:
It was no longer possible to delete Data object elements being acquired during a scanning session. The
issue has been fixed.
2021 IR3
General
The German, Japanese, Korean, Polish, and Portuguese user interfaces have been updated.
PolyWorks|Inspector
Datum labels can now be assigned to patterns of planes. The nominal primitives of plane datum features
must have the same normal.
When opening a piece that requires propagation with a linked template from an older version of PolyWorks,
the template is now automatically updated and saved before the piece is opened and the changes are
propagated, instead of displaying an error message.
Notifications related to the propagation status of pieces and templates now display the icon, status
description and possible actions related to the current status of the piece, as shown below. The same
information is also displayed when hovering the mouse pointer over the propagation split button in the
status bar. Note that possible actions are no longer displayed in the propagation split button menu.
A new status is now available when the piece template has been changed while a piece linked with it is
open. If no changes have been made to the opened piece, the following possible actions are offered:
Propagate piece template to piece and Unlink from piece template. If changes have already been
made to the piece, the following possible actions are offered: Propagate changes to piece template,
Revert to piece template, and Unlink from piece template. Note that the new Revert to piece
template action is also available in the Piece Propagation message displayed when closing a piece.
Propagating changes to the piece template and all linked pieces is now only possible through the Tools >
Piece > Propagate to Piece Template and Linked Pieces menu item or the Piece Propagation message
displayed when closing a piece.
In the Object Control SPC Results pane, the Estimated Standard Deviation (Est Std Dev) value is now used to
calculate the value of the 3 Sigma, 5.15 Sigma, and 6 Sigma statistics, instead of the Standard Deviation (Std
Dev) value. The Est Std Dev and Std Dev columns have also switched position in the table. Note that the
corresponding report template has also been modified to reflect these changes.
Warning icons for uncalibrated tool orientations are no longer displayed in an offline simulation mode.
The performance of collision detection and avoidance was improved, leading to an increase in speed of 20%
on average. The increase is up to 10 times faster for projects containing hundreds of Reference objects.
Fixed issues:
The Use Nominal Primitive measurement method was not propagated to other pieces.
Linking a piece to a piece template could fail when the piece contained coordinate systems built from
dependent features.
An issue when loading a PolyWorks 2020 user configuration in PolyWorks 2021 has been fixed.
Precision issues when picking polylines on small CAD models have been fixed.
An issue when using a slab feature as a tertiary datum feature has been fixed.
Measuring the diameter on a dependent circle with the GN or GX modifier did not produce a measured
value. A measured value will now be computed while giving a warning message.
Issues when creating the measured envelope of Line Profile controls on polylines have been fixed.
An issue with the color scale of a Line Profile control in the Feature Navigator has been fixed.
Grouped custom measurements could not be imported from another Inspector project.
The values of property field entries were lost when clicking out of the field or in another field.
A scaling issue when importing features from a CAD file and working in inches has been fixed.
Issues with the STEP CAD model importer have been fixed.
PolyWorks|Modeler
Fixed issue:
In some edge cases, exported plane primitives could not be loaded in CAD software.
Several improvements have been made for the Hexagon AS1 Absolute Scanner/Laser Tracker, Hexagon/
Romer Absolute Arm and Leica Absolute Scanner plug-ins:
In the Scan dialog box, a new Scanning profile list box has been added, which allows users to select the
scanning profile in the RDS software section.
The most recent version of RDS must be installed as well as the compatible device firmware.
For the Hexagon AS1 Absolute Scanner/Laser Tracker plug-in, new macro commands allow obtaining
information on the current tool type, serial number, number of the active face, point type, and serial number
of the tip using the following command:
LMF 1.8 has been integrated into the Leica AT960/AT930 and ATS Laser Tracker plug-ins.
The API Radian Plus/Core (Omnitrac 2) Laser Tracker plug-in now supports the iScan3D accessory, similarly to
the API Radian Pro (Radian) Laser Tracker plug-in.
Fixed issues:
When using the Hexagon/Romer Absolute Arm plug-in, the logic of the arm buttons was inverted.
An issue with the Leica AT400 Laser Tracker plug-in when creating a reflector or switching to a reflector
after having been connected to a B-Probe has been fixed.
CMM plug-ins
The following Renishaw probe head models are now supported for the CNC CMM plug-in:
MH20
MIP
PH1
Improvements have been made to be able to easily identify star styli tips in the 3D scene when using the CNC
CMM plug-in or the I++ CMM plug-in (Renishaw UCCserver version 4.6 or later). Several options have been
added to control and customize the display of these new star stylus labels.
Star stylus tip numbers can now be displayed in the 3D scene using star stylus labels. The current star
stylus tip is identified with a bold label contour, as shown for tip #2 in the example provided.
The display status of star stylus labels can be changed by selecting or deselecting the Star stylus labels
CMM option:
using the 3D Scene Display Options menu button of the 3D Scene toolbar, as shown in the
example;
on the Display > Probing and Scanning page of the PolyWorks|Inspector Options.
The Star stylus section has been added to the Display > Probing and Scanning > Probing page of the
PolyWorks|Inspector Options. These new options can be used to specify label font size and background
color.
When using the CNC CMM plug-in, star stylus labels can be displayed both when connected to a
device as well as when the Offline Simulation mode is activated.
When using the I++ CMM plug-in, star stylus labels can be displayed when connected to the Renishaw
UCCserver version 4.6 or later.
Improvements have been made to easily adjust CNC speed parameters in a measurement sequence to the
current device after switching from the Zeiss CMM-OS plug-in to the CNC CMM plug-in:
Measurement sequence execution is automatically paused if CNC speed parameter settings are
problematic for the current device. Problematic CNC Parameters measurement sequence steps are
identified with an error icon and cannot be executed.
Possible actions are offered for problematic CNC Parameters steps to easily fix the issue.
The Adjust to Current Device functionality has been improved to correctly adjust CNC speed
parameters to the current device.
The following macro command is now offered to allow users to get calibration information in the Macro
Script Editor pane. This information, which includes calibration statistics and days since last calibration, for
example, could previously only be displayed in the Tools and Tool Orientations pane.
Fixed issue:
When using the Adjust to Current Device functionality with the CMM-OS plug-in, the converted
approach speed could cause an error when run on the machine.
PolyWorks|DataLoop
It is now possible to specify the security policy to apply to a workspace when it is first uploaded to
PolyWorks|DataLoop, as well as to change the security policy of a workspace.
When uploading the workspace to PolyWorks|DataLoop for the first time, the Security policy list box is
now displayed in the Upload to PolyWorks|DataLoop dialog box. It allows specifying the security policy
to apply to the workspace on PolyWorks|DataLoop. The default value of this list box is the default
security policy, as configured in the PolyWorks|DataLoop Core Administrator. Note that this list box is
not offered when uploading a new version of a workspace that has previously been uploaded.
To change the security policy of a workspace that has previously been uploaded to PolyWorks|DataLoop,
select the workspace in the tree view of the Workspace Manager and use the Edit > PolyWorks|DataLoop
> Security Policy menu item, or right-click the workspace in the tree view and use the PolyWorks|DataLoop
> Security Policy menu item. It displays the Security Policy dialog box, that offers a list box that allows
specifying the security policy to use for the selected workspace.
Fixed issue:
The View in PolyWorks|DataLoop Web Interface functionality was not working for piece templates.
2021 IR2.2
Fixed issue:
Downloading a piece that has the same name as the project could result in an error. The issue has been
fixed.
2021 IR2
General
The Chinese, Czech, French, German, Italian, Japanese, Korean, Polish, Portuguese, Russian, and Spanish user
interfaces have been updated.
PolyWorks|Inspector Essentials Premium and Standard Packages are available in Chinese, French, Italian,
Japanese, Portuguese, and Spanish.
CNC CMM Essentials for PolyWorks|Inspector Premium Package is available in Chinese, French, Italian,
Japanese, Portuguese, and Spanish.
PolyWorks|Modeler Light Essentials is available in Chinese, French, Italian, Japanese, Portuguese, and
Spanish.
Fixed issues:
User interface issues in the PolyWorks License Manager when using certain fonts have been fixed.
When using the Macro Script Command Language, reading the content of a file just after it was created
could result in empty lines.
Display options, such as language and fonts, were no longer saved when exporting the user configuration
in the Workspace Manager.
PolyWorks|Inspector
Propagation is now allowed when there is a coordinate system based on dependent features that only
depend on nominal features.
Fixed issues:
A software crash in the Report Editor when changing a piece or project property has been fixed.
The creation of a tool orientation from the measurement sequence could fail depending on the active
coordinate system.
Issues with the STEP CAD model importer have been fixed.
An issue when using a slab feature as a tertiary datum feature has been fixed.
A sphere feature used as secondary datum feature and nominally located on a primary datum cylinder
feature's axis could erroneously block a rotation around the axis.
The order of the intersection points between a plane feature and a polyline feature could change when
inverting the polyline direction.
A performance issue when running a macro script with the Create Features dialog box open has been
fixed.
The Conversion to colors list box of the Edit Color Scale dialog box could be blank after saving and re-
opening a project.
When editing multiple comparison points at the same time, an error message could be displayed for each
comparison point.
When using Zeiss T-Scan CS/T-Track CS or Zeiss T-Scan LV/T-Track LV, it is now possible to perform an undo
operation using the red button of the T-Point touch probe with the Zeiss colin3D software. Pressing the red
button for less than 1.5 seconds ends the current probing session, and now pressing it for more than 1.5
seconds undoes the last probed point.
Fixed issue:
PolyWorks 2021 IR1 could not properly connect to a Leica AT960 Laser Tracker.
CMM plug-ins
Support of the Renishaw SCR200 tool changer has been improved for the CNC CMM plug-in. Tool changes are
now supported for Mitutoyo CMMC controllers by using the magnetic sensor of the SCR200 (Hall sensor).
Fixed issues:
An issue when probing using a Renishaw Equator system with the I++ CMM plug-in has been fixed.
CNC parameters defined in the measurement sequence could fail to be applied to the UCCserver.
2021 IR1.1
Fixed issue:
A problem when connecting to Leica AT960, AT930, or ATS Laser Tracker devices has been fixed.
2021 IR1
General
New MACRO ARRAY commands have been added to offer more operations relating to the manipulation of
tables through scripting, such as inserting, deleting, getting, searching, and sorting elements in tables.
MACRO ARRAY ELEMENTS Removes the elements from the array at the
REMOVE AT_INDEXES specified indexes.
MACRO ARRAY ELEMENTS Sorts the array of strings using the specified
SORT STRING sort order.
PolyWorks|Inspector
When using the ISO standard, a new modifier (Orientation Only Modifier [><]) is offered. It is now possible
to create a Feature Control Frame that uses a Datum Reference Frame with this modifier.
When creating a measurement sequence, it is now possible to restrict the use of the Back and Skip buttons
offered during the execution of a measurement sequence. To do so, select one or more steps in the
measurement sequence, then choose Edit > Step Execution, and enable/disable the buttons, as shown in (a).
A symbol is displayed next to the measurement step to indicate that a restriction has been specified, and a
tooltip is displayed when moving the cursor over the symbol, as shown in (b).
(a) (b)
The behavior of the buttons offered in the guiding zone of a measurement sequence has been improved
when using a jogbox:
When an action is performed, the default choice of the next action has been reviewed.
Changes have been made when editing control views from reports. The behavior is now similar to that of the
edit mode available from the Control Reviewer pane:
When a control view is modified, an asterisk is displayed next to the control view name.
Changes can be applied by pressing the Apply Changes to Control View button, which is available from
the Control Reviewer toolbar or from the toolbar displayed in the 3D scene. Note that the appearance of
the button has changed, as shown below.
To exit the edit mode and return to the report, click the Close button in the header of the edit mode or
close the Control Reviewer pane.
The Edit Control View dialog box is no longer used. The options that were offered in that dialog box are now
available in the Control View Properties dialog box (Control View > Properties in the Control Reviewer pane).
For flush & gap gauges, a new functionality allows calculating measured tangent points from nominal tangent
points. This functionality, called Tangent points from nominal, can be enabled through the property sheet
of a flush & gap gauge when the measurement method is Extract or Probe.
The new functionality is especially useful when the profile shape is complex or the fillet does not have the
shape of an arc.
The functionality can be enabled by default by selecting the corresponding check boxes on the Objects >
Gauges > Flush & Gap page of the PolyWorks|Inspector Options dialog box.
Snapshot report items now memorize the element selection of Data and Reference objects. The element
selection can be modified by using the Edit Snapshot menu item. The element selection is also memorized
in project views (created from the View > Project Views menu item) and control views.
To improve interoperability and collaborative workflows between design, manufacturing, and quality
departments, when importing a measurement plan from PolyWorks|PMI+Loop into PolyWorks|Inspector,
annotation templates are now available to display the information using the same layout as the NX
annotation. In PolyWorks|Inspector, the template is applied by default to all the supported objects imported
from a PMI+Loop measurement plan.
Here is an example of an annotation in NX, as shown in (a), and an example of the annotation once the object
has been imported into PolyWorks|Inspector, as shown in (b).
(a) (b)
Different pieces in the same PolyWorks|Inspector project can now be opened and edited simultaneously.
Note that several read-only accesses can now be offered for a single piece, but a piece can still only be
modified by one user at a time.
Fixed issues:
A refresh issue in the Properties dialog box of report items has been fixed.
A display issue in the color scale editor when using a 4K monitor has been fixed.
Issues with drop down list boxes and the Macro Scripts > Delete button in the Customize Visual Layout
dialog box have been fixed.
A piece could not be opened if the workspace contained another object with the same name.
The ignore/use status of cross-section feature groups was not correctly propagated to other pieces.
The creation of a new piece from a template could fail if the piece contained cross-sections.
The GD&T Surface Profile of a cone feature could change when changing the active data alignment.
The result of a GD&T Position control using a composite datum feature consisting of two axis-based
features could change when changing the Fit Type of the datum features.
Duplicating a cross-section feature group did not duplicate the controls of the included features.
The normal vectors of surface reference target points were not corrected when the points were projected
onto Reference objects.
Issues when creating a nominal project and mirroring the project have been fixed.
A performance issue when creating a Best-Fit Measurement Objects alignment in a project containing
many control views has been fixed.
Report table rows could grow in height when the Word Wrap was activated.
The normal vectors of cylindrical cross-sections could be inverted for closed contours.
Issues with the STEP CAD model importer have been fixed.
A software crash when creating trimmed edge comparison points using the Sample Reference Curve
method has been fixed.
Adding objects to a sequence containing a group could remove a coordinate system activation step.
A polygonal model was not automatically generated from source objects when measuring a new piece.
Error messages related to the CNC Probe method could stick when changing to the Probe method in the
Properties dialog box.
PolyWorks|Modeler
Fixed issues:
Improvements in robustness have been made to enable a more reliable complete coverage of the
polygonal model, which results in a smaller number of cases where the tessellation is not 100%
complete.
Improvements have been made to reduce the number of coincident T-junctions. The curves that are
nearly coincident that end on the same boundary and are in opposition are now joined in a greater
number of cases.
A new plug-in is now available for the Keyence Wide Area Handheld CMM device, which is a handheld probe
combined with an optical tracker. The Keyence WM Application software version 1.3.2. or later is required.
The new plug-in must be selected from the list of plug-ins in the PolyWorks Workspace Manager Options
dialog box.
A new plug-in is now available for the Hexagon AS1 Absolute Scanner/Laser Tracker. When the AS1 Hexagon
scanner is mounted on an Absolute arm, the Hexagon/Romer Absolute Arm plug-in is used. When the system
involves a laser tracker, the new plug-in is required. RDS 6.0 is required.
The new plug-in must be selected from the list of plug-ins in the PolyWorks Workspace Manager Options
dialog box.
For the Hexagon AS1 Absolute Scanner/Laser Tracker, the Scan dialog box is similar to that of the Leica
Absolute Scanner, with the addition of the Scanner buttons section, which allows users to configure the
actions associated with the device buttons.
LMF 1.8 has been integrated into the Leica AT960/AT930 and ATS Laser Tracker plug-ins.
RDS API 6.0 has been integrated into the Hexagon/Romer Absolute Arm, Leica Absolute Scanner, and
Hexagon AS1 Absolute Scanner/Laser Tracker.
SDK 10.5.1 has been integrated into the Nikon Metrology Laser Radar plug-in.
Fixed issue:
When using the Creaform VXprobe plug-in, probing after scanning created a new alignment group and
the probing session was not the active alignment.
CMM plug-ins
New interface items have been added to configure CNC acceleration parameters when using the CNC CMM
plug-in.
The Movement acceleration can be controlled when using the COORD3 CC3-NT, Hexagon, LK, Pantec
Eagle, Sb-Elektronik CNC06, or Wenzel controllers.
The Approach acceleration can be controlled when using the COORD3 CC3-NT, Pantec Eagle, Sb-
Elektronik CNC06, or Wenzel controllers.
In the Accelerations section available on the General tab of the Edit Machine dialog box.
In the Accelerations section of the CNC Parameters dialog box. Note that existing parameters for
Speeds and Distances are now grouped together in their respective sections.
In the Sequence Editor pane, when clicking the edit step shortcut of a CNC Parameters step, shown
in (a), the dialog box displayed now offers the Accelerations section as well as the sections for
Speeds and Distances, shown in (b).
(a) (b)
Support of the Renishaw SCR200 tool changer has been improved for the CNC CMM plug-in. Tool changes are
now supported for Mitutoyo UC100/UC200 controllers with firmware versions earlier than version 2.4 using
the magnetic sensor of the SCR200 (Hall sensor).
When the I++ CMM plug-in is used with a star stylus that has been calibrated in the inferred calibration mode,
users can now specify which tip of the star stylus to use to take measurements. This improvement is offered
when using the Renishaw UCCserver (version 4.6 and later when online and version 5.3 and later when
offline) and when the Split tools and tool orientations check box is selected on the General tab of the
Probing Device Properties dialog box.
The Tip list box in the Change Tool Orientation dialog box.
In the Sequence Editor, when clicking the edit step shortcut of a Tool Orientation step, the dialog box
displayed now offers the Tip list box.
When using the assisted sequencing technology to add objects to a measurement sequence, the star
stylus tips can be specified in the Add Objects to Sequence dialog box when the Custom tool and
orientation is selected, shown in (a). When the Use Current tool and orientation is selected, the star
stylus tip, if any, that corresponds to the current tool orientation is displayed, shown in (b).
(a) (b)
When in the Edit Sequence and Measurement Path Interactively mode, the star stylus tip can be
specified in the Tools and Tool Orientations dialog box for a Custom tool and orientation, shown in
(a). When the Use Current tool and orientation is selected, the star stylus tip, if any, that corresponds
to the current tool orientation is displayed, shown in (b). The selected tip is then displayed in the
corresponding toolbar in the 3D scene, shown in (c).
(a) (b)
(c)
Once the tip of a star stylus is selected, its name is displayed in the corresponding measurement
sequence step.
When connected to the CNC CMM Scanner plug-in while in the Offline Simulation mode, users can now create
new tool orientations numerically during the scanning session when real-time quality meshing is enabled
(RTQM). This can be useful, for example, to add a missing tool orientation for scanners where the C angle
must be specified.
The Tools and Tool Orientations button can now be used during scanning to open the Tools and Tool
Orientations pane and create missing tool orientations in between scanning sessions.
Users can then specify the orientation by pressing the Create Orientations button in the Tools and Tool
Orientations pane, shown in (a), and specifying the angles in the Create Tool Orientations dialog box that
is displayed, shown in (b).
(a)
(b)
Fixed issues:
The probe head could collide with the table during calibration.
PolyWorks|DataLoop
The Windows Certificate Store is now used to validate the SSL certificate of the PolyWorks Collaborative Suite
License Server, enabling the use of internal certificate authorities.
A new option is now available on the DataLoop page of the Workspace Manager Options. The Prompt to
upload changes when closing worspace check box, cleared by default, allows displaying a message on
closing a workspace when it contains changes that have not been uploaded to PolyWorks|DataLoop. The
user can then choose to upload the new data or to close the workspace without uploading.
In PolyWorks|Inspector, a similar message is always displayed when closing a project with changes that have
not been uploaded to PolyWorks|DataLoop. If some changes are unsaved as well, the message offers three
choices: Save and upload, Save, or Do not save.
Fixed issues:
Projects stored in PolyWorks|DataLoop by other users were not visible in the PolyWorks Workspace
Manager after opening the workspace.
Large CAD models (more than 3,000,000 triangles) could not be displayed in the PolyWorks|DataLoop
Web Interface.
General
Find technical support contact information directly in PolyWorks through the new Contact Us dialog box. It can
be displayed through the Help > Contact Us menu item of the PolyWorks Metrology Suite products, except
PolyWorks|Talisman. It displays the coordinates of the local technical support team, as determined by the user’s
PolyWorks license, in the Software support section, as well as the coordinates of InnovMetric’s headquarters in
the Software development section. Examples of the Contact Us dialog box for two different regions are shown
below. Note that the Software support section is currently only available for node-locked licenses.
PolyWorks® MS 2021 – the last major release to support Windows 7 and 8.1
To continue to offer you our PolyWorks solutions with a maximum level of performance for which our products
are recognized, our teams are constantly evaluating and integrating new technologies and software
components. This approach also requires periodically readjusting the minimum configuration required for the
proper functioning of our software. We therefore wish to inform you that from version 2022 of PolyWorks
Metrology Suite, the minimum operating system required will be Windows 10 Pro.
Microsoft having announced the upcoming end of support for Windows 7 and 8.1 in the year 2021, we maintain
the compatibility of PolyWorks Metrology Suite 2021 on these 2 platforms. PolyWorks 2021 will be the last to be
installed on these operating systems.
If you have any questions, feel free to contact InnovMetric at: [email protected].
We are proud to offer you software solutions that are always at the cutting edge of technology.
Miscellaneous
Improvements have been made to the automatic backup recovery system for projects and pieces when there
is a software crash. The error report window that is now displayed allows resuming work after a crash in a
single click. If the opened project was previously saved and an automatic backup is available at the time of
crash, an error dialog box that offers three choices is displayed:
Keep backup - The backup is saved, overwriting the previous save. A restore point is created to allow
restoring the previous saved file. This choice is the default, as it minimizes potential data loss without
creating duplicates.
Keep last saved - The automatic backup is deleted and the previous save is kept. Unsaved changes are
lost.
Keep both - For PolyWorks|Inspector projects, the previously saved piece is kept and the backup is saved
under a new name in the same project. For PolyWorks|Modeler and IMAlign projects, the previously
saved project is kept and the backup is saved under a new name in the same workspace.
If the project has never been saved and a backup is available, the backup is automatically saved, and only the
piece name is changed to specify it is a backup. If there was no backup, the recent changes are lost. In both
cases, a message is displayed informing the user and offering them to restart the software.
Note that a Support Assistant report can now be created directly from a hyperlink in these dialog boxes.
Fixed issues:
Issues when running macro scripts from a visual layout button in the Workspace Manager have been
fixed.
PolyWorks|Inspector
Extended analysis of curved surfaces with the Line Profile GD&T control
Benefit from the new Line Profile GD&T tool that meets ASME and ISO standards, and offers controls with a full
or partial datum reference frame, to:
Analyze single, partial, and multisegment 2D profiles of freeform sheet metal cutouts.
Review form and positional errors of complex sections and cutouts using powerful visual aids to ensure the
fit of mating components.
Support of the 2D Line Profile GD&T control and enhanced polyline feature
The PolyWorks|Inspector GD&T toolkit now contains the Line Profile tool to measure two-dimensional profiles
using planar polyline features. As part of these improvements, new nominal polyline creation tools and
measured polyline extraction parameters are also offered. These new tools can be especially useful, for example,
for freeform sheet metal cutouts, as shown in (a), or when measuring the sections of extruded parts, as shown
in (b).
(a)
(b)
The Line Profile GD&T control is defined on the polyline feature. The nominal primitive of a polyline feature
must first be defined. This can be done either by using the new Pick on CAD Model feature creation method
or by picking on a nominal cross-section. When created this way, the nominal polyline feature component
contains information about the orientation of the CAD model surfaces adjacent to the polyline.
This information contains the tangent direction and the normal direction for each segment of the polyline,
which is needed to successfully extract the measured component.
The new polyline creation tool also introduces a new measured polyline extraction mechanism. Previous
curve-based feature extraction (for circles and rectangles, for example) uses fitting to define the feature from
the extracted list of Data points. The new mechanism for polylines instead detects the model boundary. This
is not a fit type, but rather a tracking and detection algorithm that utilizes the tangent direction of the nominal
polyline segments to sample and filter Data points and determine the most representative boundary.
Picking and measuring a polyline on the CAD model for freeform 2D sheet metal cutouts
To create the nominal polyline feature, the Polyline feature type must be selected in the Create Features
dialog box; Multiple Types is not supported.
Users can now define single segment or multisegment planar polylines directly on their CAD models, to
add the Line Profile tool on freeform 2D sheet metal cutouts.
Selecting the new Pick on CAD Model creation method for polylines, users can choose whether to pick
a Single Segment or Multiple Segments to create a polyline. The first submethod creates the polyline
immediately when a segment is picked, while the second submethod allows picking multiple segments
to form a single polyline. The submethod selection is only available when the polyline is not picked on a
cross-section.
When the Single Segment submethod is selected, the segment range can also be specified as either the
Whole Curve or Partial Curve of the CAD model. The first choice automatically selects the whole curve
when picking, while the second allows picking two points on a curve, then picking the curve between the
points to indicate which segment to keep.
The default polyline drawing type display options have been adjusted. The Arrows and Vertices are now
hidden by default in the Display > Features > Drawing Type page of the PolyWorks|Inspector Options
dialog box.
(a)
(b)
Once a cross-section is created, users can pick a complete or partial profile segment on the nominal
cross-section to define the nominal polyline feature component.
(a) (b)
The measured component of the polyline can then be calculated using the new Extract from Cross-
Section measurement method.
The extraction parameters are similar to those offered for curve-based features (such as circles), with
the following differences:
Once the nominal polyline feature component has been created, the Line Profile GD&T tool can be added on
the polyline feature. Datum features can also be specified.
To better view line profile results, it is useful to display the deviation vectors. The new Color Map section has
therefore been added to the Feature Navigator, grouping the color map options with the deviation vector
options for quick access. Examples are shown for (a), line profile results for a sheet metal cutout and (b), the
results for an extruded part.
(a)
(b)
Proper deviation value reported for the Surface Profile control when U/UZ tolerance zone modifiers are
used
When using the U or UZ tolerance zone modifiers, the deviation from the center of the tolerance zone is now
reported for the Surface Profile GD&T control.
Increase the efficiency and repeatability of 3D measurement operations thanks to technological aids added to
our measurement toolbox:
Ensure digital gauging traceability by capturing and automatically storing a mixed reality photo when
measuring a dimension with a digital gauge and PolyWorks|AR™.
Display digital readouts, axial deviations, and guidance arrows as holograms in the operator’s view to help
precisely position a machine, a tool, or a fixture using PolyWorks|AR.
Ensure digital gauging traceability by capturing and automatically storing a mixed reality photo when measuring
a dimension with a digital gauge and PolyWorks|AR.
The PolyWorks|AR mixed reality solution allows users to conveniently carry their PolyWorks|Inspector
project with them to guide their next action while performing a 3D measurement workflow or to access
project data instantaneously while reviewing measurement results.
In PolyWorks|Inspector 2020, the Gauge measurement method was introduced to perform 3D inspections
using digital gauge measurements. PolyWorks|AR 2021 now offers built-in tools for digital gauging operators.
Leveraging the Microsoft HoloLens 2 mixed reality devices, this new major release provides digital gauging
operators with automatic mixed reality photo capture to ensure measurement traceability and provides on-
screen guidance powered by holograms.
When using the Gauge measurement method with the PolyWorks|AR plug-in, operators benefit from the
3D mixed reality display, as guidance holograms are superimposed on the physical pieces in front of
them, showing them where to measure with the digital gauge and displaying the results.
For traceability, a mixed reality image is now automatically captured and stored when measuring a
dimension with a digital gauge. These mixed reality images, taken by the Microsoft HoloLens in the
PolyWorks|AR plug-in, are stored in the PolyWorks|Inspector project and associated with the
corresponding measured characteristics of the object.
The gauging images are captured from the operator’s point of view, showing the digital gauge, the
measured piece, and the guidance hologram when measuring a dimension. These images can then be
used for documentation, analysis, or traceability purposes. For example, quality engineers can refer to
the images to validate how and where the measurement was taken.
There are several ways to view captured gauging images. New menu items have been added to view the
images, as well as a new dialog box that can be used to view and manage the images.
The new View > Captured Gauging Images shortcut menu item is offered for objects for which the
Gauge measurement method is specified. This new menu item is offered for objects in the tree view,
and their annotations, as well as for objects selected in the Control Reviewer pane. Note that
multiple objects can be selected in the tree view and in the Control Reviewer pane.
If a gauging image has already been captured for a characteristic of the selected objects, the name
of the characteristic is displayed as a menu item. Selecting the characteristic opens the
corresponding image with the default Windows image viewer.
Selecting the Manage Captured Images menu item displays the new Captured Gauging Images dialog
box, which can also be used to view captured images, as well as manage the images.
Buttons are also offered to manage the images, allowing users to view the image in the image
viewer, export the image, or delete the image that is associated with the characteristic.
Note that captured gauging images can also be viewed in the same ways in PolyWorks|Reviewer.
Bring the next level of assembly guidance to operators on the shop floor
PolyWorks|AR 2021 offers a built-in mixed reality solution for the assembly guidance of fixtures and jigs that
makes the operator’s task easier than ever. Users can launch the Build/Inspect mode within
PolyWorks|Inspector and be guided by a mixed-reality display right before their eyes.
This mixed reality assembly guidance while in the Build/Inspect mode allows users to:
Organize their visual environment by resizing the Digital Readout window (DRO) and placing it in the optimal
location.
Position the fixture components precisely with the help of intuitive holographic arrows and annotations.
Control the complete assembly process without ever having to go back to the computer.
For more details on these new tools, as well as other improvements, see the PolyWorks|AR™ for HoloLens
Release Notes, available in the Technical Support Zone.
CNC CMM users will save even more time thanks to the revolutionary intelligence added to our innovative
assisted sequencing technology:
Let the assisted sequencing technology determine if multiple tool orientations are needed to measure an
object and configure the object measurement method automatically.
Export CNC CMM measurement sequences to a standard DMIS file to accelerate sequence creation in legacy
CMM software.
Features in a measurement sequence could previously only be CNC probed in a single step, acquiring all the
measurement points for the object using the same tool orientation. In PolyWorks|Inspector 2021, measurement
points for an object in a sequence can now be split into groups, making it possible to CNC Probe a feature in
multiple steps.
And now that a feature in a sequence can be CNC probed in multiple steps, it is possible to use a variety of other
steps between groups of points to perform different operations, such as to use different tool orientations to
measure an object, like the cylinder feature for the bearing axis below.
These steps to measure an object can be inserted manually when customizing the sequence or added
automatically when using the smart assisted sequencing technology. Note that related improvements have also
been made for manual feature probing operations.
This flexibility opens up many measurement scenarios that can allow the user to further improve measurement
sequence execution time, and provides an efficient user-friendly assisted sequence creation workflow.
When customizing a measurement sequence manually, measurement points for an object can now be split
into groups by selecting the points in the Sequence Editor pane and dragging them to the desired location in
the sequence, as shown in (a), or by right-clicking and selecting the new Create Step from Measurement
Points shortcut item, as shown in (b). The order of the measurement points within each group can then be
edited by selecting them and dragging them to the desired location within the group.
(a) (b)
The measurement point numbers are now displayed next to each measurement point in a sequence and the
name displayed for the steps to measure the object is now CNC Probe: or Probe:, depending on the object's
measurement method, along with the feature name, as shown in (a). The measurement point numbers within
the point group, for the selected step, are also displayed in the 3D scene, as shown in (b).
(a) (b)
Three additional parameters are now offered in the dialog box displayed when clicking the arrow of a step
containing a measurement point group.
The Delete measured component check box that, when selected, deletes the existing measured
component prior to executing the measurement step. Therefore, the check box is typically selected for
the first step to measure the feature and cleared for the subsequent steps for that feature.
The Point acquisition mode, offered for objects that use the Probe measurement method when the
Delete measured component check box is cleared, to choose the acquisition mode of the
measurement step.
The Measurement Points pane displays the groups of measurement points for the selected object.
Once measurement points have been split into groups and the feature can be measured in multiple steps, a
variety of measurement sequence steps can be manually inserted between the groups of points to perform
different operations:
When in the Edit Sequence and Measurement Path mode, the Hide Objects Added to Sequence option now
only hides objects in the 3D scene that are considered to be completely measured in the sequence. If at least
one of its measurement point groups is not in the sequence, the object will remain visible.
The following features can be CNC probed or probed in multiple steps: circles, cylinders, planes,
lines, ellipses, cones, and spheres.
Local constraining planes are not supported and the measurement points must all be measured
before the feature can be measured. When using a plane feature as a constraining plane, the plane
feature must have a measured primitive.
The Insert > Add Probed Data Points menu item has been removed from the Sequence Editor. All
measurement steps are represented as a Measurement Object step.
This affects all objects that support adding points: circles, cylinders, planes, lines, ellipses, cones,
spheres, and cross-sections.
When starting a point acquisition session for an object that supports measurement in multiple steps,
rather than validating the number of measurement points for the active session, the total number
of measurement points needed to measure the object is now validated instead.
There are less constraints on the minimum number of points needed to CNC probe or probe a
feature. It is now possible to end an acquisition session after probing as little as a single point. It is
therefore no longer necessary to be able to create a primitive to allow an acquisition session to be
successfully completed.
The diameter of probe tips or reflectors must be the same, for example when changing the tip of a
star styli.
When using the assisted sequencing technology to add objects to a sequence, the smart technology now
automatically takes care of the following to generate an efficient path, all while avoiding collisions:
Splits the measurement of each object into multiple steps when needed.
Determines if different tool orientations are needed and inserts them at the right locations within the
sequence.
Inserts steps to measure local constraining planes before the measurement of the features.
Related improvements have also been made for users that manually probe features.
For the features that can be probed in multiple steps, there are less constraints on the minimum number of
points needed to CNC probe or probe a feature. It is now possible to end an acquisition session after probing
as little as a single point. It is therefore no longer necessary to be able to create a primitive to allow an
acquisition session to be successfully completed.
When probing features using the guided point acquisition mode, it was previously only possible to probe
one group of measurement points per device position for a given object. Now, it is possible to probe
more than one group of measurement points per device position.
Therefore, these groups of points are now referred to as a measurement point groups instead of a device
position point groups and the name of these point groups has been changed from Device position point
group 1, for example, to group 1.
The functionality now works with features rather than primitives since probed points can now be acquired
on a feature whose measurement has started, but that does not yet have a measured primitive. The user
interface, as well as corresponding commands, reflect this change.
When using the Define Measurement Points from Probed Data Points functionality, measurement point
groups are now created according to the acquisition sessions instead of the device positions.
Note that when a compensation point is needed when in the guided point acquisition mode, it is acquired after
the first measurement within a group of points for a feature.
Sequences from PolyWorks|Inspector can now be exported in the DMIS file format. This new functionality can
be accessed from the File > Export > Sequence menu or from the Sequence > Export menu of the Sequence Editor
pane. It is possible to export the whole sequence, by choosing the All steps menu item, or only the selected steps,
by choosing the Selected steps menu item. Choosing an item displays a file browser, that allows browsing to the
appropriate location, entering a file name, and saving the DMIS file. Note the following:
Some sequence operations cannot yet be converted to DMIS code, but are written as text in the exported
DMIS file.
In the File > Export menu, the existing As DMIS File menu item has been renamed As DMIS Output File to avoid
confusion with the new export sequence to DMIS file functionality.
Accelerate working with large inspection projects thanks to new tools for finding, selecting, and editing objects:
Accelerate single or multi-object selection in a list box by selecting objects in the 3D Scene or Tree View or
typing a few characters of an object’s name to filter down the number of objects shown in the menu’s list.
Access directly the Apply, Close, Next, and Previous buttons of Properties windows, regardless of the scroll
position.
PolyWorks 2021 offers important improvements to increase efficiency and flexibility when handling large
projects.
Improvements have been made to list boxes to make selecting a specific object in a list containing a large
number of objects more efficient. Two new methods of selection have been introduced:
For list boxes that contain more than 15 objects located in dialog boxes, a search box is now displayed
when making a selection. As text is entered, search results are immediately displayed in the list box and
updated in real time as the search string is completed. When the list box only allows selecting one object,
as shown in (a), the list box collapses when an object is selected. When multiple objects can be selected,
as shown in (b), each object in the list box is preceded by a check box. If at least one object is selected
and the list is opened again, the selected objects are displayed at the top of the list and the search results
are displayed under the Items section.
A button has also been added next to some list boxes. It launches the Pick Objects interactive selection
mode, as shown in (c), or Pick Object if only one value can be specified in the list box, that allows changing
the selection of the list box directly from the 3D scene or the tree view. Note that elements can be added
to the existing selection by holding the CTRL key when clicking the desired object in the interactive mode.
(a) (b)
(c)
The name of the object and the bottom row of buttons in an object
Properties dialog box are now always visible when scrolling
vertically. These buttons include the Previous and Next buttons,
now represented by arrow icons, as well as the Apply and Close
buttons.
Other improvements
Airfoil gauge segmentation capabilities have been enhanced, offering new tolerance blending options to make
smooth transitions between the ends of adjacent segments that have different tolerances.
Airfoil gauge segment options are now offered to blend neighboring segment extremities. Users can choose
from a linear or smooth blending method and specify the length of the blending. They can also choose which
segments the blending method is applied to. Some examples are shown below for two segments that have
different tolerances.
In this example, the Linear blending method has been applied to the extremities of one segment (TE);
In this example, the Smooth blending method has been applied to the extremities of one segment (TE);
In this example, the Smooth blending method has been applied to the extremities of both segments (TE
and Suction);
In this example, the Linear blending method has been applied to the extremities of both segments (TE
and Suction).
These options can be specified in the new Tolerance Blending column of the Airfoil Gauge Segment Options
dialog box. The dialog box is displayed when selecting the Analyze segments check box and clicking the
Options button on the property sheet of the airfoil gauge.
These improvements impact four types of airfoil segments: LE, Pressure, TE, and Suction segments that have
been best-fit using a tolerance zone, as well as the Min and Max Distance controls for these types of
segments.
For the four cross-sections that can optionally be generated from these four types of segments, the following
will be impacted:
Line Profile
Min Deviation
Max Deviation
Mean Deviation
The name, description, and parameters of measurement scripts distributed by InnovMetric with PolyWorks are
now available in the user’s preferred language, which is selected in the Language list box on the Display page of
the Workspace Manager Options dialog box.
Measurement system analysis (MSA) is a set of tests that thoroughly analyze the performance of a measurement
system. These studies are an integral step in the preproduction process and are necessary to establish
equipment and environmental capabilities before parts go into full production. The two main steps when
conducting measurement system analysis are first, repeatability studies, and second, conducting Gauge R&R
studies. The studies are standardized, with sophisticated statistical calculations and graphical output.
PolyWorks|Inspector 2021 makes the MSA process digital and more streamlined and simplifies the complicated
process. Instead of exporting or transcribing measurement values for external analysis, the user can do
everything within the PolyWorks digital ecosystem. It also saves them from manually typing up to 900 values by
hand. And, since everything is located and calculated in one solution, it is simpler to ensure traceability of the
analysis process.
Conducting measurement system analysis can be a complicated and tedious process requiring many manual
steps that can lead to errors. PolyWorks|Inspector 2021 automates the process of creating a Gauge study
package, simplifying the process, saving time, and reducing user error. The reports that are created can also be
easily updated.
The new Measurement System Analysis toolbar can be used to automate the creation and execution of a
Gauge Study in PolyWorks|Inspector, guiding the user in designing, running, validating, and publishing the
study.
Sophisticated Gauge R&R study Excel templates are now offered for download, in addition to existing
repeatability templates
The Microsoft Excel templates are used to analyze the results of the study, by automatically linking the
Microsoft Excel sheet to the PolyWorks|Inspector project using PolyWorks|ReportLoop.
Filling in the spreadsheets manually can be tedious and error-prone. For example, in the case of the repeatability
studies, the measurement process will be adjusted, and each adjustment requires an update to the spreadsheet.
Using PolyWorks|ReportLoop to hold the object links means that the studies update automatically and never
become obsolete. When a study has been completed, the user simply chooses to report the study results, and all
necessary values are automatically populated in the proper Excel template using PolyWorks|ReportLoop. The
spreadsheet then stores the link to the PolyWorks|Inspector objects, so it can be maintained as a living
document. It can even be populated in advance and updated once inspections are complete.
Users have the study values whether they are connected to PolyWorks or not. When connected,
PolyWorks|ReportLoop will update the changed values and additional information can be inserted. When not
connected, the last known value is displayed.
In addition to two repeatability study templates released in 2020, PolyWorks|Inspector now offers two more
templates designed for Gauge R&R studies, for a total of four sophisticated study templates.
In PolyWorks|Inspector 2020, repeatability study templates were offered for the Type 1 Gauge Study analysis
method and the Gauge R Study analysis method.
Now, in PolyWorks|Inspector 2021, two Gauge R&R study templates have been released that support the
Average and Range as well as ANOVA study methods.
These Excel templates are available for free download from the Technical Support Zone and can be fully linked to
PolyWorks|ReportLoop. Note that the desired study template for the study being conducted must be
downloaded prior to publishing the study.
Intuitive new tools have been integrated to automate the MSA process and guide users in planning, designing,
conducting, and publishing their Gauge studies.
To begin, the user creates an inspection project for the study, containing some measurement objects (features,
comparison points, or gauges) with active controls. They can then start creating their Gauge study using the new
Measurement System Analysis toolbar, which is displayed by right-clicking over an empty area under the title bar
and selecting the toolbar from the list.
In a typical measurement system analysis workflow, each button in the toolbar will be used in order from left to
right, first selecting the key characteristics, then designing the study, followed by piece inspection, and finally
publishing the study.
From the control plan, the person who creates the study needs to identify which characteristics, or controls,
the study should inspect.
The Select Key Characteristics button, shown to the right, displays the corresponding dialog box.
The selected controls will be assigned a Yes value in the new Key
Characteristic column of Custom Properties in the Geometry
Controls pane. This column is displayed by right-clicking a
column header and selecting the Custom Properties > Key
Characteristic shortcut menu item.
If the Create control view check box is selected, a Gauge Study Characteristics control view is
automatically created containing all the selected key characteristics. The display in the 3D scene is also
adjusted to only show the objects for which at least one key characteristic is selected and the annotations
of those objects are displayed. Once the control view is created, any changes made to the selection of
characteristics will also automatically be updated in the control view. Clearing the Create control view
check box in the dialog box deletes the control view if one has already been created.
The Key Characteristic column can also be displayed in the Control Reviewer pane by right-clicking
over a column heading and selecting the Custom Properties > Key Characteristic shortcut menu item.
When the Gauge Study Characteristics control view is selected, the corresponding reviewing mode
is launched.
Once at least one key characteristic has been selected, Key Characteristic is added to the list of
custom properties on the Controls page of the PolyWorks|Inspector Options dialog box.
Once the key characteristics have been designated, the Gauge study itself can be prepared for the operator(s).
Several intuitive dialog boxes have been integrated to guide the user through the Gauge Repeatability and
Gauge R&R study design by automating the study creation process.
Clicking the Design Study button, shown to the right, displays the Design Study dialog box.
The user begins by choosing a Source piece template. To be able to propagate piece changes later
if needed, an existing piece template can be used, or a new piece template can automatically be
created from the active piece.
The user then chooses to design a Gauge Repeatability study or a Gauge R&R study. Clicking
Continue displays the corresponding dialog box, depending on the type of study chosen.
- The Gauge Repeatability study supports the Type 1 gauge study and the Gauge R study
analysis methods. The corresponding dialog boxes are displayed for each analysis method when
clicking Continue.
- The Gauge R&R study supports the ANOVA and the Average and range analysis methods. The
Gauge R&R - Operators and Parts dialog box is displayed after clicking Continue.
The user sets the required Study information, Study options, and Operator names and Part names
(in the case of Gauge R&R studies), then clicks the Create button to automatically generate the study.
All the pieces required for the study are automatically created and linked to the piece template for
change propagation. The pieces are created in the order in which they should be inspected and are
named study piece <piece number>.
If needed, the system also creates a Gauge Study Template. All the information and options entered by
the user are stored in the project or in the pieces in the form of piece and project properties. Depending
on the type of study selected by the user, different custom properties will be created. Only the custom
properties needed for the study selected by the user will be created.
Once a Gauge study has been created, the operators can then start the inspection process.
Clicking the Inspect Next Piece button, shown to the right, opens the first piece of the study that has some
key characteristics that are unmeasured and launches the Play Inspection tool on that piece, providing
guidance to perform the measurements.
In the case of a Gauge R&R study, a guiding instruction will give the operator the name of the piece to inspect
before launching the inspection. This guiding instruction will not be displayed in the case of a Gauge
Repeatability study, because for those studies only one operator will inspect the same piece many times.
Once all the pieces of the study have been measured, the measurement results can be published in the
associated Microsoft Excel template.
Clicking the Publish Study button, shown to the right, allows users to publish the study.
The Excel templates for the gauge studies must be downloaded by the user from the Technical Support
Zone. There are four different templates available, one for each type of study and analysis method.
The first time users publish a specific type of study, the Publish Study message box informs them that
they need to download the templates on their computer and then browse for the template. The path to
the template is then saved in the user configuration so that if the user republishes that type of template,
the message box will not be shown. If the template is moved, deleted, or renamed on the computer, the
message box is displayed again.
The user clicks the Browse button and selects the template in the file browser. The template is opened in
Excel and the correct cells are automatically populated.
The properties section of the template comes from the project properties (Study Information and Study
Options sections of the template). The Characteristic Definition section is defined from the key
characteristics that are selected in the piece template. The Measurement Results come from the measured
values of controls in the pieces of the project.
Users can then save the Excel file. The example below shows a Gauge R repeatability study that has been
published in Excel and has been linked to the PolyWorks|Inspector project using PolyWorks|ReportLoop.
PolyWorks|ReportLoop is not required to view and share the published study results, but is recommended
for users who need a link between the Excel report and the corresponding PolyWorks|Inspector project. This
allows users to easily update the spreadsheet information.
The latest release of Spatial’s 3D InterOp CAD import technology has been integrated. The following format can
now be imported:
Fixed issues
Resizing the Customize Visual Layout dialog box did not work properly on the Commands tab.
The order of pieces when importing from a PolyWorks|Inspector project was not the same as in the Piece
Properties window.
PolyWorks|Modeler
With a single click, automatically turn 3D scans into high-quality surface models directly usable in preferred
downstream applications, including FEA and mechanical simulation, machining, and CAD design, thanks to the
revolutionary surface modeling approach in PolyWorks|Modeler:
Models a polygonal surface by automating the creation of characteristic curves within a minimal number of
surface patches and fitting a continuous network of NURBS surfaces.
Creates editable models suitable for CAD design and simulation applications by automatically bounding
surface patches with continuous curves that naturally describe the part’s characteristics.
Produces lighter models with better fitting accuracy and patch continuity for downstream applications by
automatically adapting the patch size and aspect ratio to the part’s surface curvature.
For even greater flexibility, the automatic surfacing technology is perfectly integrated within our intuitive curve-
based surfacing workflow, letting users interactively edit the curve network to create optimal surface models:
Edit the automatic surfacing results intuitively by adding, deleting, or reshaping curves, as you would do in a
manual reverse-engineering workflow.
Control the description of curves that are critical for your application, such as symmetry lines, part
boundaries, and subtle feature lines, by providing predefined curves to the automatic surfacing tool.
Traditional NURBS model technologies generally cover the polygonal model with a large number of small tiles,
making the NURBS models heavy and difficult to edit in downstream applications. PolyWorks|Modeler 2021
delivers a completely new technology that does things differently. Users can now quickly and easily generate
light, easily editable, CAD-friendly NURBS models automatically.
This new technology draws characteristic curves that precisely define the part characteristics, and then
generates the minimal number of patches to cover the entire surface.
In addition to this new and improved technology, the workflow to automatically create NURBS patches from
polygonal models is now simpler, more flexible, and more efficient. Existing editing tools, useful for surface
modeling, have also been conveniently grouped together into one new toolbar.
These automatically generated NURBS surfaces are suitable for a variety of downstream applications. They can
be exported and used directly in preferred applications, including FEA and mechanical simulation, machining,
and CAD design.
With PolyWorks|Modeler tools for smart reverse engineering, increase productivity by easily converting scans
into high-quality NURBS surfaces.
Improved technology and workflow when automatically creating NURBS patches from a polygonal model
The automatic NURBS patch creation workflow is now simpler, more flexible, and more efficient. With a single
click, high-quality NURBS surfaces, with continuous curves that naturally describe the part’s characteristics, can
be created automatically. Users can also predefine critical curves, like symmetry or boundary curves, to adapt
the automatic NURBS surface creation to their application.
In addition, advanced parameters can easily be adjusted to control patch creation, if needed. Post-processing
parameters are offered that, when selected, automatically launch the fit operation and show fitting errors once
the NURBS patches have been generated.
The Create NURBS Patches from Polygonal Model dialog box, displayed when selecting the NURBS patches >
Create > From Polygonal Model menu item, has been completely redesigned, simplifying the automatic NURBS
creation workflow while allowing users to adapt the automatic NURBS surface creation to their specific
application.
When users are ready to create their NURBS surface, once the polygonal model has been cleaned up, the new
dialog box offers items to easily create NURBS patches from a polygonal model automatically.
The Use selected curves check box, selected by default, allows users to influence the end results by creating
key curves and selecting them before launching the automatic NURBS surface creation.
Clicking the Create button now uses the new algorithm and default creation parameter values, as well as any
selected curves, to automatically create a high-quality NURBS surface from the polygonal model.
This new powerful and versatile automatic surfacing tool can easily be used for a variety of applications. The
three typical workflows are described below.
Creating NURBS patches for the entire surface of a watertight polygonal model
When the polygonal model is watertight (i.e., closed polygonal model surface that encloses the volume)
such as the manifold shown in (a), users can simply click the Create button to run the algorithm and
automatically create the NURBS patches for the entire surface, as shown in (b).
(a)
(b)
Creating NURBS patches for the entire surface of an open polygonal model
When working with an open polygonal model, like the headlight shown below, it is recommended to:
First, create the boundary curves, in blue in (a), and insert them into the polygonal model.
Lastly, click the Create button to run the algorithm, which uses the selected curves to automatically
create the NURBS patches for the entire surface, as shown in (b).
(a)
(b)
If users want to create NURBS patches for just a specific part of the polygonal model surface, such as for
the hood of a car, shown below, they can:
First, create the curves delimiting the desired NURBS patch boundaries on the surface of the
polygonal model, as shown in (a), and insert them into the polygonal model.
Then, select those curves in the tree view, as well as the triangles within the curves.
Lastly, click the Create button to run the algorithm, which uses the selected curves to automatically
create the NURBS patches for that part of the polygonal model surface, as shown in (b).
(a)
(b)
Note that any type of curve that has been previously created and selected can be used by the new automatic
NURBS surfacing algorithm to create high-quality NURBS surfaces. This includes standard, boundary, feature
center, edge, fillet tangent, and even symmetry boundary curves. For example, in the hood example above,
one of the curves was not only a boundary curve but also a symmetry boundary curve. Users can therefore
benefit from the powerful new technology while still being able to control the results of the algorithm for
different applications and polygonal models.
Users can also easily adjust advanced parameters that are specific to the polygonal model to control the
automatic creation of patches, if needed, such as to create patches for subtle features of a particular
polygonal model.
The Min angular feature detection span parameter can be used to control the degree of sensitivity
used to detect polygonal model features and create curves. The smaller the angle, the higher the
degree of sensitivity and the more curves will be created to clearly define important details.
The Max relative patch size parameter determines the maximum patch size relative to the
bounding box of the polygonal model. For example, a value of 25% allows each patch to cover a
maximum of a quarter of the model. Therefore, values less than 50% generate smaller patches and
values greater than 50% generate larger patches.
Default max relative patch size Larger max relative patch size
The Post-processing section contains the Fit patches and Show fitting errors parameters. When
selected, these operations will automatically be launched once the NURBS patches have been
created.
These automatically generated NURBS model surfaces are fully editable using the standard curve-editing
toolbox that was already offered in PolyWorks|Modeler. These tools, as well as reverse-engineering and post-
processing tools, are now conveniently grouped together in the new Surface Modeling toolbar and can be used,
for example, to add or delete curves. Note that the toolbar is hidden by default and can be displayed by selecting
it in the Toolbars tab of the Customize Visual Layout dialog box. It can also be selected from the list of toolbars
offered in the shortcut menu when right-clicking over an empty area under the title bar.
Other improvements
When several curves are created at once, all of them are now automatically selected in the tree view at the
end of the creation operation. Note that this improvement applies to all curve types and all creation methods.
The new Mitutoyo U-Wave plug-in allows users to connect to Mitutoyo U-Wave devices and bring measurements
from supported gauges into their inspection projects using the Gauge measurement method. The plug-in is
compatible with the Mitutoyo U-Wave-R receiver, and the Mitutoyo U-Wave-T, Mitutoyo U-Wave-TM, and
Mitutoyo U-Wave-TC transmitters. Note that the device must be configured in the U-WAVEPAK Mitutoyo software
before it can be used in PolyWorks|Inspector.
The new plug-in must be selected from the list of plug-ins in the PolyWorks Workspace Manager Options
dialog box.
The Mitutoyo U-Wave device must also be specified using the Connect to gauging device split button on the
Devices toolbar in PolyWorks|Inspector.
Mitutoyo U-Wave device properties can be accessed by pressing the Gauging Device Properties button on
the Gauging Device toolbar, as shown in (a). The Gauging Device Properties dialog box, shown in (b), is
displayed, which allows users to select the communication port that the desired Mitutoyo U-Wave Receiver
may be connected to and test that connection. Note that commands are also offered to perform these
operations.
(a) (b)
CMM plug-ins
When the I++ CMM plug-in is used with a star stylus that has been calibrated in the inferred calibration mode,
the following possible actions are now offered for tool orientation measurement sequence steps:
Fixed issue:
Issues when calibrating multiple tools on different reference spheres have been fixed.
PolyWorks|DataLoop
A message is now displayed when a new piece is about to be created based on an out-of-date template. The
user can then choose to update the template with the latest data from PolyWorks|DataLoop or to cancel the
piece creation.
Fixed issue:
A piece that was locally deleted, then re-downloaded, was still deleted when uploaded to
PolyWorks|DataLoop.