hexagon logo

PC-DMIS Measurement Routine Migrations

Starting with PC-DMIS 2021.2, PC-DMIS doesn’t allow loading of measurement routines created in PC-DMIS 2015 and earlier and will generate an error. See: I am getting the error message "Serialization error This version of PC-DMIS can only read measurement routines created in version...."
In PC-DMIS 2022.1, only PRG files from 2016 or newer will be allowed. This “rolling” restriction will continue with each new release of PC-DMIS.

For instance:
Installed Version Can read back to (or pull forward from)

2021.2 2015.1
2022.1 2016
Future projection:
2022.2 2017 R1
2023.1 2017 R2
2023.2 2018 R1
Etc.

To use older routines with a current PC-DMIS release, you need to save all the older measurement routines to any version at least as recent as that defined by the current restrictions. This can be done one file at a time but if you have a significant number of files it can be very time-consuming. To help facilitate this process, we’ve created and shared two utilities.


Conversion Utilities for PC-DMIS (hexagonmi.com)

Utility Home : SaveMRtoRequiredVersion

This will automatically open the measurement routines and save them to the desired version. (simply opens, saves and closes routines)

Utility #2: Migration_Utility

This is a little more intelligent and performs the same task as utility 1 but also handles migration from Xactmeasure to the new, geometric tolerance command. It requires you to install the most recent service pack of 2020 R1 as well as your desired version (2020 R2 or higher). It asks you to navigate to three folders – the source folder containing your routines, a destination for routines that generate migration reports and a destination for routines that do not generate migration reports. The utility will then sort routines into the relevant destination folders making it easier for you to identify those that migrated successfully and those that require editing. Please see here for a more detailed description: Documentation. It also saves probe files associated with each routine in the current probe format.

While these utilities are being provided free of charge, there is no implied support. Please be sure to back-up all of your files before starting this process.

*** Please be sure to read the help documentation on these tools. It is brief and will often answer the very questions which we are seeing posted here.

Parents
  • neil.challinor Using PC-DMIS 2021.1+ at least lets me get started. One thing I noticed is the migration status window says, for PC-DMIS 2022.1, "valid version found:2022.(". The number after the decimal is showing "(" for any version of PC-DMIS I try. Could this explain the issue with why it will save in 2020 R1 format but fail when opening the target version? Is there an issue with the name that it obtains?

    ** pcd_ver = PRO.MainWindowTitle.Substring(19, 1); returns "("
    ** pcd_ver = PRO.MainWindowTitle.Substring(17, 1); returns the correct version number.
    ** Why would this be different for me than you?

  • I believe the logic for obtaining the pcd_ver value is flawed. The parenthesis you see in the label text is probably the first parenthesis from the "(release)" text in the windowtitle... Please post a screenshot of your windowtitle/caption from your 2020 R2 version.

    pcd_ver = PRO.MainWindowTitle.Substring(19, 1);


    The position to look for pcd_ver is hardcoded at string index 19 with a length of 1.
Reply
  • I believe the logic for obtaining the pcd_ver value is flawed. The parenthesis you see in the label text is probably the first parenthesis from the "(release)" text in the windowtitle... Please post a screenshot of your windowtitle/caption from your 2020 R2 version.

    pcd_ver = PRO.MainWindowTitle.Substring(19, 1);


    The position to look for pcd_ver is hardcoded at string index 19 with a length of 1.
Children
No Data