This document contains the NI VeriStand 2014 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.
The following items are known issues in NI VeriStand 2014 sorted by Date.
ID | Known Issue | |||||
---|---|---|---|---|---|---|
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.
| |||||
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.
| |||||
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.
| |||||
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.
| |||||
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
| |||||
309162 Return | Cannot multi select steps by holding down shift You cannot highlight multiple items in the sequence editor. Workaround: N/A
| |||||
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
| |||||
310588 Return | Reflective memory channels are not scalable Reflective memory channels are not scalable Workaround: Use a calculated channel or model to scale them.
| |||||
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.
| |||||
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
| |||||
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: Open XNET Database Editor outside of Veristand. Import DBC File. Hit OK and View DBC file with corrected ALIAS
| |||||
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.
| |||||
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
| |||||
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: Remove all software on the target. Install just LVRT and DAQmx (make sure the target resets after this). Install VeriStand engine
| |||||
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
| |||||
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
| |||||
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
| |||||
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: N/A
| |||||
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.
| |||||
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.
| |||||
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
| |||||
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.
| |||||
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
| |||||
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.
| |||||
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
| |||||
426453 Return | Changing an XNET signal to a different name causes the signal to get deleted. After changing the name of a signal and then refreshing the XNET database the signal is deleted. Workaround: N/A
| |||||
481040 Return | Custom device tree operations within action VI on load fail with error 1088 Attempting to do any tree operations inside a custom device action VI on load causes an error 1088. The error occurs because the tree has not been drawn yet and these tree operations cause system explorer to attempt to update the non-existent tree. Workaround: N/A
| |||||
526455 Return | Unable to apply higher-order calibration polynomial coefficients at run-time Given a system that uses N coefficients to describe a calibration equation, any additional coefficients- beyond the N initially declared- will not be immediately applied to the desired channel. Workaround: Undeploy the system. The subsequent deployment will apply the previously-entered calibration coefficients.
|
Document last updated on 5/19/2015