Error -307702 When Deploying LabVIEW Model in VeriStand

Issue Details

I created a model in LabVIEW for use in VeriStand, and it compiled successfully without an errors. I added this LabVIEW-built model into my system definition file in VeriStand, but when I go to deploy, I receive the following error:

Error -307702 occurred at <path to VI>

Possible reason(s):

NI VeriStand: The size of the imported model data in the system definition file conflicts with the size in the specified model file. This error can occur if the model file contains a different number of inports, outports, signals, or parameters than when it was imported. This error also can occur if two or more models contain a global parameter with the same name but different dimensions. To correct this error, reload the model in the System Explorer window and verify the dimensions of any global parameters that multiple models contain. Alternatively, change the Scope for Global Parameters option on the Parameters page for a model to Model to avoid conflicts caused when the model shares the global parameter with other models.

Solution

This error can occur if the controls and indicators used in the model contain special characters or white space. This also may be operating system-dependent. For example, a model built for Windows that contains these characters might be able to deploy, but the same model built for Linux Real-Time will throw the deployment error.

To fix this, do the following:

1. In your VI, disconnect all controls and indicators from the VI's connector pane.

2. Rename the the controls and indicators to remove any whitespace or special characters such as back or forward slashes.
3. Reconnect the controls and indicators to the connector pane.
4. Rebuild the VI for the desired target.
5. In VeriStand, reload the model in the System Explorer or the Mapping Diagram.
6. Try to deploy to verify the error is no longer present.

Additional Information

Even if a control does not contain special characters, there have been instances where this error is thrown due to some corruption of the control linking. Following the steps above to disconnect controls and reconnect them should still resolve the problem.