Setting defaults.

[None_the_wiser]

We recently upgraded to 2019R2, and now the defaults on all of our auto features have changed. All of our features have avoidance moves and void detection turned on, we absolutely do not need this. I have tried going into the measurement strategies editor, changing the settings to what we normally use and saving that as a new group, then setting that group to default, but it never seems to stay. The group I created is there and the default, but none of the settings I selected seem to be active when selecting the auto features.

[neil.challinor]

From the help files

How the MSE Works

You can use the MSE to modify the settings for all each auto feature and store them as strategies and custom groups. Strategies are specific to each feature. Groups contain any modified settings for all the features.

The MSE saves the settings for each custom group in text files. These text files use the XML format. Each text file has the group name as its name with an .msexml filename extension. Whenever you delete a group, PC-DMIS deletes the corresponding .msexml file.

PC-DMIS stores these files in the C:\ProgramData\Hexagon\PC-DMIS\2019 R2 folder.

When you set a group of settings as the default (and at other times discussed in "About Default Settings" below), the MSE writes those settings into the registry for PC-DMIS auto features to use.

Check that your user account has permission to write to both the windows registry and the ProgramData folder. The behaviour you describe is typically what I would expect to see when a system has been "locked down". In my experience a lot of IT guys like to arbitrarily restrict access to virtually everything on the PC and don't necessarily look at the readme file which specifies areas PC-Dmis will need access to.

Appendix B
Required User Access Rights
PC-DMIS 2019 R2 requires read, write, and create access to the locations defined below in the file system and registry.
File System
Windows 10, Windows 8, Windows 7, and Windows Vista:
• C:\ProgramData\Hexagon\PC-DMIS\2019 R2
• C:\Users\Public\Documents\Hexagon\PC-DMIS\2019 R2
• C:\Users\UserName\AppData\Local\Hexagon\PC-DMIS\2019 R2
• Any user-specified folder locations for storing measurement routines, probes, subroutines, and so on
Registry
All of these versions have their own registry settings, which are stored in a version-specific registry key. The items shown below are for version 2019 R2.
• HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Hexagon\PC-DMIS\2019 R2 Key and all sub keys
• HKEY_CURRENT_USER\Software\Hexagon\PC-DMIS\2019 R2 and all sub keys
• HKEY_USERS\.DEFAULT\Software\Hexagon\PC-DMIS\2019 R2 and all sub keys
Notes
The first time you run a new version, PC-DMIS automatically copies the settings from the most recent version of PC-DMIS that is installed. For this to work, PC-DMIS needs to run with administrator privileges the first time you run it. During the
Appendix B
78
installation, if you select the Launch PC-DMIS check box in the setup wizard, it runs PC-DMIS as an administrator and completes this first step.
This initial migration automatically sets read, write, and create permissions on the registry for the relevant keys.
If you are using fixturing or laser sensors, the following registry keys are stored back one level:
• HKEY_LOCAL_MACHINE\SOFTWARE\Hexagon\FxtServer
• HKEY_LOCAL_MACHINE\SOFTWARE\Hexagon\PC-DMIS\NCSENSORSETTINGS
It may be easier to just apply create/read/write privileges to the HKEY_LOCAL_MACHINE\SOFTWARE\Hexagon\ key and all sub keys to cover these also.