NI Veristand 2013 Known Issues

Überblick

This document contains the NI VeriStand 2013 known issues that were discovered before and since the release of NI VeriStand 2013. 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 2013 sorted by Date.

216610 Importing a .mdl file slows significantly with larger models
303844 Cannot open a sequence by double clicking Sequence Call in the test project
309162 Cannot multi select steps by holding down shift
309168 Double clicking a stimulus file on disk with an editor already open, opens a brand new editor window
310588 Reflective memory channels are not scalable
317883 Using % in a block name causes a The MathWorks Inc. Simulink® model to fail to build
222645 VeriStand cannot import MDLs with ports inside a block with a name starting with a number
216736 Model time for an MDL is incorrect
241320 Lvmodel fails to initialize with error 1003
319481 Remote Event Frames are filtered out in Veristand
319988 XNET Database Editor throws error if there is a '.' in the name of the .dbc file
339518 XNET Device Driver fails to deploy after formatting controller
348534 Workspace graph does not function on Windows XP if no network connection is available
321998 Reflective memory in a system adds significant CPU overhead
329546 If DAQmx driver is installed on target after VeriStand Error -88717 may occur on reboot
332403 Channel Faults between serial models do not apply correctly
349731 Veristand cannot built model from LabVIEW if VI contains static reference to a shared variable
360521 XNET Bus Monitor uses the wrong network adapter if there are multiple adapters on a machine
369187 Importing XNET Database fails when signal and frame have same name but different capitalization
381933 Recursive call of nivsseq can cause Stimulus Prifle Editor to crash
382087 Channel Fault Manager does not work if one target is disconnected
382480 Setting Counter Output Pulse Generation to a Duty Cycle of 0 or 100 Causes Error
383092 Streaming a large number of waveform graphs can cause VeriStand gateway to stop responding
385803 CAN Data Replay Requires Trigger Channel be specified
386381 The Pulse Measurement task may return incorrect data
387298 VISA Error -1073807192 thrown on launching Hardware Discovery Wizard for target with Reflective Memory
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
422005 VeriStand does not allow multiple databases for a single XNET Port
426050 Some DSA Boards are not Identified by Veristand's Hardware Wizard
222544 Clicking stop on a model control linked to an MDL causes NI VeriStand to crash



ID Known Issue
216610

Return
Importing a .mdl file slows significantly with larger models
If you try to import a .mdl file with a large number of parameters and signals, the import will be increasingly slower and may lead to a crash.

Workaround: Consider breaking model into smaller components.

Reported Version: 2009    Resolved Version: N/A    Added: 7/2/2010/
303844

Return
Cannot open a sequence by double clicking Sequence Call in the test project
Cannot open a sequence by double clicking Sequence Call in the test project

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/9/2011/
309162

Return
Cannot multi select steps by holding down shift
You cannot highlight multiple items in the sequence editor.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/9/2011/
309168

Return
Double clicking a stimulus file on disk with an editor already open, opens a brand new editor window
Double clicking a stimulus file on disk with an editor already open, opens a brand new editor window

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/9/2011/
310588

Return
Reflective memory channels are not scalable
Reflective memory channels are not scalable

Workaround: Use a calculated channel or model to scale them.

Reported Version: 2010    Resolved Version: N/A    Added: 10/9/2011/
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/9/2011/
222645

Return
VeriStand cannot import MDLs with ports inside a block with a name starting with a number
VeriStand cannot import MDLs with NI VerIStand inports or outports inside a block that starts with a number.

Workaround: Rename the subsystem to not have a number at the beginning of its name.

Reported Version: 2009    Resolved Version: N/A    Added: 6/11/2010/
216736

Return
Model time for an MDL is incorrect
Model time for an MDL is incorrect

Workaround: Use a Clock block wire to an outport in your model. Then use that output as the time.

Reported Version: 2009    Resolved Version: N/A    Added: 4/13/2010/
241320

Return
Lvmodel fails to initialize with error 1003
When deploying a lvmodel to a target without LabVIEW Control Design and Simulation Module the model fails to initialize with error 1003.

Workaround: Either install LabVIEW Control Design and Simulation Module support on the RT target or reboot the target after deployment.

Reported Version: 2010    Resolved Version: N/A    Added: 9/17/2010/
319481

Return
Remote Event Frames are filtered out in Veristand
Frames without channels in the system explorer are not added to the session. This makes it so an Event Remote frame cannot be used without creating a custom device to handle it.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 7/20/2012/
319988

Return
XNET Database Editor throws error if there is a '.' in the name of the .dbc file
If you attempt to open a DBC file with a '.' in the name of the file in the XNET Database Editor in Veristand you may see the following error: " The Database specified could not be loaded, either it does not exist or it is not a valid XNET Database."

Workaround: Follow these steps 1) Open XNET Database Editor outside of Veristand 2) Import DBC File 3) Hit OK and View DBC file with corrected ALIAS

Reported Version: 2010    Resolved Version: N/A    Added: 7/20/2012/
339518

Return
XNET Device Driver fails to deploy after formatting controller
After deploying a Veristand system definition containing XNET if the controller is reformatted but the system definition is unchanged subsequent deployments will fail with an error similar to "NI VeriStand: The specified Device Driver VI was not found at the following path: C:\ni-rt\NIVeriStand\XNET\NI-XNET.llb\NI-XNET.vi"

Workaround: Change the system definition such that it needs to be saved. Save and re-deploy the system definition.

Reported Version: 2011    Resolved Version: N/A    Added: 7/20/2012/
348534

Return
Workspace graph does not function on Windows XP if no network connection is available
Workspace graph does not function on some Windows XP computers if no network connection is available

Workaround: Install the microsoft loopback adapter: http://support.microsoft.com/kb/839013 or connect the computer to another network.

Reported Version: 2011    Resolved Version: N/A    Added: 7/20/2012/
321998

Return
Reflective memory in a system adds significant CPU overhead
Adding reflective memory into a system definition adds significant CPU overhead and decreases the maximum rate achievable by the Primary Control Loop

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 10/22/2013/
329546

Return
If DAQmx driver is installed on target after VeriStand Error -88717 may occur on reboot
If DAQmx driver is installed on target after VeriStand Error -88717 may occur on reboot

Workaround: #NAME?

Reported Version: 2010    Resolved Version: N/A    Added: 10/22/2013/
332403

Return
Channel Faults between serial models do not apply correctly
If a channel fault is applied to the output of the first model or the input of the second model of two mapped models in serial execution order then the channel fault is not applied.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/22/2013/
349731

Return
Veristand cannot built model from LabVIEW if VI contains static reference to a shared variable
Veristand cannot built model from LabVIEW if VI contains static reference to a shared variable. Error 1003 will be displayed.

Workaround: Use programmatic access for shared variables

Reported Version: 2011    Resolved Version: N/A    Added: 10/22/2013/
360521

Return
XNET Bus Monitor uses the wrong network adapter if there are multiple adapters on a machine
When using a development computer with multiple network interface cards it's possible that the VeriStand XNET Bus Monitor will listen on the wrong network adapter.

Workaround: Disable the network interface card that is not used with NI VeriStand.

Reported Version: 2011    Resolved Version: N/A    Added: 10/22/2013/
369187

Return
Importing XNET Database fails when signal and frame have same name but different capitalization
Importing XNET Database fails when signal and frame have same name but different capitalization. Importing frames will fail with error 1077 stating that there is an invalid signal.

Workaround: Make signal and frame capitalization match or use different names for signals and frames

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 10/22/2013/
381933

Return
Recursive call of nivsseq can cause Stimulus Prifle Editor to crash
If a nivsseq refereneces itself it can cause the Stimulus Profile Editor to crash when it is opened

Workaround: Open the XML of the nivsseq and delete the recursive reference

Reported Version: 2012    Resolved Version: N/A    Added: 10/22/2013/
382087

Return
Channel Fault Manager does not work if one target is disconnected
Channel Fault Manager does not work if one target is disconnected

Workaround: NA

Reported Version: 2012    Resolved Version: 2012    Added: 10/22/2013/
382480

Return
Setting Counter Output Pulse Generation to a Duty Cycle of 0 or 100 Causes Error
Setting the duty cycle of a pulse generation output to 0 or 100 will cause an error and cause the VeriStand Engine to shut down.

Workaround: Set the duty cycle to the next closest value supported by the specific DAQ card being used.

Reported Version: 2012    Resolved Version: N/A    Added: 10/22/2013/
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: 10/22/2013/
385803

Return
CAN Data Replay Requires Trigger Channel be specified
CAN Data Replay will not work correctly if a trigger channel is not specified.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 10/22/2013/
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: 10/22/2013/
387298

Return
VISA Error -1073807192 thrown on launching Hardware Discovery Wizard for target with Reflective Memory
VISA Error -1073807192 is thrown on launching Hardware Discovery Wizard for target with Reflective Memory

Workaround: In MAX, go to the Software section for the target. Browse to NI Visa and select the VISA options tab on that page. Add the IP of the host PC to the Remote Access List.

Reported Version: 2012    Resolved Version: N/A    Added: 10/22/2013/
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: 10/22/2013/
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: 10/22/2013/
422005

Return
VeriStand does not allow multiple databases for a single XNET Port
VeriStand does not allow multiple databases for a single XNET Port

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 10/22/2013/
426050

Return
Some DSA Boards are not Identified by Veristand's Hardware Wizard
The Hardware Wizard can't identify some DSA boards and add them to the System Definition

Workaround: Manually add those boards

Reported Version: 2012    Resolved Version: N/A    Added: 10/22/2013/
222544

Return
Clicking stop on a model control linked to an MDL causes NI VeriStand to crash
If you click the stop button of a model control that is mapped to an MDL, NI VeriStand crashes.

Workaround: Don't click stop in the model. Instead, stop the simulation from NI VeriStand.

Reported Version: 2009    Resolved Version: N/A    Added: 4/30/2010/

Document last updated on 10/22/2013

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