Page Comparison

To migrate a VeriStand project to a newer version of the Power Electronics Add-On it is necessary to follow a series of steps. When upgrading a project from an older version to a more recent one, follow the adequate steps listed below. Some steps are duplicated, in that case the duplicated steps should :

1. Save a backup of the orignal project by making a copy of the entire project folder on disk.

2. Follow the steps in the Uninstallation and Upgrade Procedure to upgrade the Power Electronics Add-On to the desired version. If multiple versions are to be skipped during the upgrade, it is not necessary to install intermediate versions.

3. Follow the procedures below, beginning with the section corresponding to the Add-On version used to create the original project.

4. Complete the steps in each subsequent section until the desired Power Electronics Add-On version is reached. Steps repeated across multiple sections can be skipped.
   

Anchor
1.15.Xto1.16.0 1.15.Xto1.16.0

Migrating from 1.15.X to 1.16.0

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Save and close the System Definition.

Anchor
1.14.xto1.15 1.14.xto1.15

Migrating from 1.14.X to 1.15.0

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Save and close the System Definition.

...

1. Relink all IO channels used in the VeriStand UI manager

2. Relink all IO channels used in the System Configuration Mapping page of the VeriStand project

3. Verify that all IO mappings that were configured in the Power Electronics Addon are still valid (ex. on the Sources, Switches, Digital Outputs, and Resolver pages)

Anchor
1.14.0to1.14.1 1.14.0to1.14.1

Migrating from 1.14.0 to 1.14.1

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Save and close the System Definition.Follow the steps listed

Anchor
1.13.xto1.14 1.13.xto1.14

Migrating from 1.13.X to 1.14.

...

1

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Save and close the System Definition.

4. Follow the steps listed in Migrating from 1.14.0 to 1.14.1.

Anchor
1.13.0to1.13.1 1.13.0to1.13.1

Migrating from 1.13.0 to 1.13.1

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Save and close the System Definition.Follow

...

Anchor
1.12.xto1.13 1.12.xto1.13

Migrating from 1.12.X to 1.13.

...

1

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Ensure that all the elements in the Sources and Switches pages have valid mapping elements selected. If they do not all have valid mapping selections, an error will be thrown at deployment. 

4. Expand any machines in the project and navigate to each of their Resolver and Encoder pages. If the Number of Pole Pairs parameter is set to 0, update it to 1 or another nonzero value. Any machine sensor configured to have 0 pole pairs will cause an error to be thrown at deployment.

5. Save and close the System Definition.Follow the steps listed

...

...

Target Update

As of version 1.13.0 of the Power Electronics Add-On, the Real Time target is required to have the FlexRIO driver installed, in addition to the NI VeriStand Engine. Please see the Deployment Target Software Requirements page for additional information and installation instructions.

...

Anchor
1.11.xto1.12 1.11.xto1.12

Migrating from 1.11.X to 1.12.0

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

2. If a window opens asking for files to be relinked, click Skip. The files will automatically be relinked by the system definition update process.

3. Ensure that all the elements in the Sources and Switches pages have valid mapping elements selected. If they do not all have valid mapping selections, an error will be thrown at deployment. 

4. In the Waveforms and Analog Outputs pages, identify any elements set to <Machine Name>.Mechanical Angle (Deg). Use the drop-down arrow for an element to update its value to <Machine Name>.Mechanical Angle (Turn).

5. Save and close the System Definition.Follow

...

Anchor
1.10.xto1.11 1.10.xto1.11

Migrating from 1.10.X to 1.11.0

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update.

2. Save and close the System Definition.Follow

...

Anchor
1.9.xto1.10 1.9.xto1.10

Migrating from 1.9.X to 1.10.0

Project Dependency Update

1. Open the System Definition of the existing project. This will automatically trigger a dependency update.

2. Save and close the System Definition.Follow

...

...

Anchor
1.8.xto1.9 1.8.xto1.9

Migrating from 1.8.X to 1.9.0

Project Dependency Update

When a VeriStand project created in a previous version of the Add-on is opened for the first time, a prompt is shown to the user stating that that the following files are missing on disk:

...

1. In the prompt, click the Skip button for both dependencies and Save the project. 

2. Open the System Definition of the existing project. This will automatically trigger a dependency update. 

3. If using a PMSM BLDC machine configured in Variable Ld/Lq mode, follow the steps described in the next section.

4. Save and close the System Definition.

5. Follow the steps listed in Migrating from 1.9.X to 1.10.0.

PMSM BLDC JSON File Update

If using the PMSM BLDC machine model configured to use the in Variable Ld/Lq motor type mode, the JSON file must be updated to include the DqTransformAngleOffset parameter.

1. Open the existing JSON parameter file in a text editor.

2. Add a new line under "PolePairs": and enter the following text: "DqTransformAngleOffset": 0

   1. For more information about this parameter, see the JSON Motor Model File description.

3. Save the JSON file.

Anchor
1.7.xto1.8 1.7.xto1.8

Migrating from 1.7.X to 1.8.0

Project Dependency Update

When a VeriStand project created in a previous version of the Add-on is opened for the first time, a prompt is shown to the user stating that that the following files are missing on disk.

1. In the prompt, click on the Skip button for both dependencies and Save the project. 

2. Open the System Definition of the existing project. This will automatically trigger a dependency update.

3. Save and close the System Definition.

4. Depending on the hardware configuration used by your in the project, follow the steps described in the next sections.

5. Follow the steps listed in Migrating from 1.8.X to 1.9.0.

PMSM BLDC Machines

If using one the following hardware configurations:

...

1. Open the System Definition of the existing project.

2. Navigate to one of the two PMSM SH pages.

3. Update the Sample time parameter to 4E-7 (400ns). This will update the parameter for both machines.

4. Save the System Definition. 

...

Migrating from 1.6.X to 1.7.0

...

1. Open the System Definition of the existing project. Automatically, an upgrade process of the system definition tree will be executed.
   Note: This process will generate a backup of the entire folder where the VeriStand project is saved. The backup will get stored in a zip file located in the project directory.

2. If a Window opens asking for files to be relinked, click on the Skip option (the files will automatically be relinked by the system definition updated process)

3. Browse through the System Definition Tree and click on the Circuit Model section of each circuit in the hardware configuration.

4. Click on the Reload button.

5. Save the System Definition.Follow the steps listed

...