Documentation Home Page Power Electronics Add-On for NI VeriStand Home Page
Pour la documentation en FRANÇAIS, utilisez l'outil de traduction de votre navigateur Chrome, Edge ou Safari. Voir un exemple.

Project Migration Procedure

To migrate a VeriStand project to a newer version of the Power Electronics Add-On:

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

  2. 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.

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.

Verify IO Channel Mapping

The names of the channels for all the IO in the Power Electronics Addon has been modified to match the IO nomenclature used by NI. DIO channels are now named ConnX.DIOXX, AI channels are now named ConnX.AIXX, and AO channels are now named ConnX.AOXX. After migrating a project from a previous version of the Power Electronics Addon, it is recommended to

  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)

As of version 1.15.0, the Power Electronics Add-On allows users to configure DIO channel direction for certain FPGAs. In new projects, DO channel mappings are are set to Not Connected by default, but in migrated projects, previously unmapped DO channels remain unmapped. This results in a warning advising the user to map all DIO channels. It is recommended, but not required, to set these unmapped channels to Not Connected.

The project is now compatible with version 1.15.0.

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.

The project is now compatible with version 1.14.1. To continue migrating to a later version, follow the steps in Migrating from 1.14.X to 1.15.0.

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.

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.

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.

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.

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.

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.

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.

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:

  • eHSx64_IM_IO_7868R.lvbitx

  • hardware_configuration.json

  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.

PMSM BLDC JSON File Update

If using the PMSM BLDC machine model configured in Variable Ld/Lq 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.

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 in the project, follow the steps described in the next sections.

PMSM BLDC Machines

If using one the following hardware configurations:

  • Dual_eHSx64_Quad_PMSM_VDQ_IO_Dual_7868R

  • eHSx64_Dual_PMSM_VDQ_IO_7868R

  1. Open the System Definition of the existing project.

  2. Browse through the System Definition Tree and expand each PMSM VDQ section in the hardware configuration.

  3. Rename each PMSM VDQ page to PMSM BLDC for consistency.

  4. If the Digital Outputs, Analog Outputs, or Waveforms pages contain elements mapped to PMSM VDQ channels, use the drop-down arrow for each element to update its mapping to PMSM BLDC.

  5. Save the System Definition.

Hall Effect Pages

If using one of the following hardware configurations:

  • Dual_eHSx64_Quad_PMSM_VDQ_IO_Dual_7868R

  • eHSx64_Dual_PMSM_VDQ_IO_7868R

  • eHSx32_Dual_PMSM_SH_IO_7868R

  1. Open the System Definition of the existing project. 

  2. Navigate to the Hall Effect page under each machine.

  3. Remove all Hall Effect pages from the System Definition tree.

    VeriStand will open three different dialog windows specifying that error 36 has occurred (this will occur for each Hall Effect sensor removed). This is expected behavior due to removing the sensor. If these pages are not removed manually, the user will see an error upon deployment.

  4. Save the System Definition.

PMSM SH Machines

When using the following hardware configurations:

  • eHSx32_Dual_PMSM_SH_IO_7868R

  • eHSx128_Dual_PMSM_SH_IO_7976R

  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

This procedure is required when upgrading a VeriStand project created in the 1.6.X version of the Power Electronics Add-On.

  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.

OPAL-RT TECHNOLOGIES, Inc. | 1751, rue Richardson, bureau 1060 | Montréal, Québec Canada H3K 1G6 | opal-rt.com | +1 514-935-2323