NI VeriStand 2015 SP1 Known Issues

Overview

This document contains the NI VeriStand 2015 SP1 known issues that were discovered before and since the release of NI VeriStand 2015 SP1. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Known Issues by Date

The following items are known issues in NI VeriStand 2015 SP1 sorted by Date.

317883 Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build
383092 Streaming a large number of waveform graphs can cause VeriStand gateway to stop responding
386381 The Pulse Measurement task may return incorrect data
392092 Error -200452 occurs when a 433x device uses hardware timed single point
402293 Model files imported to VeriStand with vector channels appear as Nx1 rather than 1xN
522678 Adding an FPGA target to the System Definition via the API will fail to add the Parameters section of PWM channels
527148 Programmatic deployment of VeriStand Projects to password protected targets requires user interaction
372874 Building a LabVIEW model for NI VeriStand fails if the controls or indicators have identical names.
572887 Setting the Frame Type option in the Raw Data Frame Configuration page has no effect.



ID Known Issue
317883

Return
Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build
Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build

Workaround: Do not use % in the block name.

Reported Version: 2010    Resolved Version: N/A    Added: 10/09/2011
383092

Return
Streaming a large number of waveform graphs can cause VeriStand gateway to stop responding
Streaming a large number of waveforms to the waveform graph can cause the VeriStand gateway to be overwhelmed and stop responding in a timely fashion.

Workaround: Reduce CPU usage on the gateway computer or stream fewer waveforms.

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
386381

Return
The Pulse Measurement task may return incorrect data
In certain configurations where the signal is disconnected or has a 0/100% duty cycle, the Pulse Measurement task may report invalid readings. The returned reading of the disconnected signal will be the last non 0/100% duty cycle processed by your device.

Workaround: Install NI DAQmx 9.7 drivers

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
392092

Return
Error -200452 occurs when a 433x device uses hardware timed single point
If a 433x device is set as the master or if there is only a 433x device in a system definition, using hardware timed single point will cause error -200452 to occur during deployment.

Workaround: Use at least one other device in the system definition

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
402293

Return
Model files imported to VeriStand with vector channels appear as Nx1 rather than 1xN
Model files imported to VeriStand with vector channels appear as Nx1 rather than 1xN making it impossible to map to the channel correctly.

Workaround: Use the channel mappings dialog to import from a text file instead of using the dialog.

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
522678

Return
Adding an FPGA target to the System Definition via the API will fail to add the Parameters section of PWM channels
When using the System Definition API to programmatically add an FPGA target to a System Definition file, the Parameters section typically included with PWM channels is excluded.

Workaround: Add the FPGA manually to the System Definition via the System Explorer.

Reported Version: 2014    Resolved Version: N/A    Added: 08/13/2015
527148

Return
Programmatic deployment of VeriStand Projects to password protected targets requires user interaction
When deploying a VeriStand Project to a real-time target protected with a password a user is required to interact with a login dialog box. Consequently, programmatic deployment using the API still requires user interaction, preventing truly headless deployment.

Workaround: Have an operator interact with the dialog box or do not use password protected targets for programmatic deployments.

Reported Version: 2014    Resolved Version: N/A    Added: 08/13/2015
372874

Return
Building a LabVIEW model for NI VeriStand fails if the controls or indicators have identical names.
When building a VI into a model for NI VeriStand, the build process will fail if any of the indicators or controls have identical names.

Workaround: Use different names for the controls and indicators that will become the model's inports and outports.

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 08/18/2015
572887

Return
Setting the Frame Type option in the Raw Data Frame Configuration page has no effect.
As the Frame Type is pulled from the XNET database, this System Definition setting does not affect the XNET configuration.

Workaround: Set the Frame Type as desired in the XNET database. Do not use the Raw Data Frame Type Configuration option in the System Definition.

Reported Version: 2014    Resolved Version: N/A    Added: 04/01/2016



Known Issues by Category

The following items are known issues in NI VeriStand 2015 SP1 sorted by Category.

Miscellaneous
386381 The Pulse Measurement task may return incorrect data
392092 Error -200452 occurs when a 433x device uses hardware timed single point
Model Interfacing
317883 Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build
402293 Model files imported to VeriStand with vector channels appear as Nx1 rather than 1xN
372874 Building a LabVIEW model for NI VeriStand fails if the controls or indicators have identical names.
Performance
383092 Streaming a large number of waveform graphs can cause VeriStand gateway to stop responding
System Explorer
572887 Setting the Frame Type option in the Raw Data Frame Configuration page has no effect.
Using the API
522678 Adding an FPGA target to the System Definition via the API will fail to add the Parameters section of PWM channels
527148 Programmatic deployment of VeriStand Projects to password protected targets requires user interaction



ID Known Issue
Miscellaneous
386381

Return
The Pulse Measurement task may return incorrect data
In certain configurations where the signal is disconnected or has a 0/100% duty cycle, the Pulse Measurement task may report invalid readings. The returned reading of the disconnected signal will be the last non 0/100% duty cycle processed by your device.

Workaround: Install NI DAQmx 9.7 drivers

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
392092

Return
Error -200452 occurs when a 433x device uses hardware timed single point
If a 433x device is set as the master or if there is only a 433x device in a system definition, using hardware timed single point will cause error -200452 to occur during deployment.

Workaround: Use at least one other device in the system definition

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
Model Interfacing
317883

Return
Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build
Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build

Workaround: Do not use % in the block name.

Reported Version: 2010    Resolved Version: N/A    Added: 10/09/2011
402293

Return
Model files imported to VeriStand with vector channels appear as Nx1 rather than 1xN
Model files imported to VeriStand with vector channels appear as Nx1 rather than 1xN making it impossible to map to the channel correctly.

Workaround: Use the channel mappings dialog to import from a text file instead of using the dialog.

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
372874

Return
Building a LabVIEW model for NI VeriStand fails if the controls or indicators have identical names.
When building a VI into a model for NI VeriStand, the build process will fail if any of the indicators or controls have identical names.

Workaround: Use different names for the controls and indicators that will become the model's inports and outports.

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 08/18/2015
Performance
383092

Return
Streaming a large number of waveform graphs can cause VeriStand gateway to stop responding
Streaming a large number of waveforms to the waveform graph can cause the VeriStand gateway to be overwhelmed and stop responding in a timely fashion.

Workaround: Reduce CPU usage on the gateway computer or stream fewer waveforms.

Reported Version: 2012    Resolved Version: N/A    Added: 08/04/2014
System Explorer
572887

Return
Setting the Frame Type option in the Raw Data Frame Configuration page has no effect.
As the Frame Type is pulled from the XNET database, this System Definition setting does not affect the XNET configuration.

Workaround: Set the Frame Type as desired in the XNET database. Do not use the Raw Data Frame Type Configuration option in the System Definition.

Reported Version: 2014    Resolved Version: N/A    Added: 04/01/2016
Using the API
522678

Return
Adding an FPGA target to the System Definition via the API will fail to add the Parameters section of PWM channels
When using the System Definition API to programmatically add an FPGA target to a System Definition file, the Parameters section typically included with PWM channels is excluded.

Workaround: Add the FPGA manually to the System Definition via the System Explorer.

Reported Version: 2014    Resolved Version: N/A    Added: 08/13/2015
527148

Return
Programmatic deployment of VeriStand Projects to password protected targets requires user interaction
When deploying a VeriStand Project to a real-time target protected with a password a user is required to interact with a login dialog box. Consequently, programmatic deployment using the API still requires user interaction, preventing truly headless deployment.

Workaround: Have an operator interact with the dialog box or do not use password protected targets for programmatic deployments.

Reported Version: 2014    Resolved Version: N/A    Added: 08/13/2015

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).