Archived: NI VeriStand 2011 Bug Fixes

NI does not actively maintain this document.

This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.


The following items are the IDs and titles of a subset of issues fixed between NI VeriStand 2010 and NI VeriStand 2011. If you have a CAR ID, you can search this list to validate that the issue has been fixed.


Use this table to identify issues that were fixed in VeriStand 2011.
ID Fixed Issue
149703 Deploying a VI to a target that was running VeriStand unsets it as startup exe. Must reinstall to fix
176352 Import settings checkbox for Models can not be changed by clicking the boolean text.
185544 Graph control background plot color cannot be changed
187134 Need to expose documentation for .net dll in 2010
206801 Temp Gauge scale min and max do not update
208943 TDMS Viewer in VS does not show initial timestamp correctly
209565 Document XML Schema for NI VeriStand Custom Devices
222546 Model inports and outports cannot be configured with a default value
233003 Associate nivssdf and nivsproj with veristand so you can launch from file
240196 Examples may search for VeriStand API VIs when first opened
240398 Unclear error thrown when using daq and fpga in an unidentified chassis
241159 Model parameter manager takes a while to close, locking user out of sys explorer
241408 Built in thermocouple scaling does not work for 9219
242105 Custom Device Path property does not work on VxWorks
243455 Stop Macro Player function hangs indefinitely if Macro was paused, not running
244193 Counter frequency channels created with invalid min and max Hz of zero
244558 Clicking add data folder under reflective memory throws error and fails
245381 Import XNET Frames doesn't automatically select Signals if the hierarchy is deeper than 2
246557 VeriStand 2010 Import .dbc file
247356 Parameter values not updated if model changes value but it is not refreshed in System Explorer
247357 Model Parameter manager slow with large set of parameters
247362 LVModel generation fails for inputs with deep clustering
248320 Reset Dependencies does not work properly
249210 MDL files linked by relative path crash MATLAB®
251326 XNET bus monitor does not display frames if raw frame logging is used
254228 Custom devices added to a single target are deployed to all targets in a system definition
254231 VeriStand can download dependent file multiple times to same target
254899 Veristand: Degradation in performance the more CAN channels added
255534 Hidden Aliases Still Show in the Workspace
257917 delete multiple items doesn't properlly react to ok / cancel
258756 FPGA scaling with negative integer wordlength for FXP Data always produces Inf values
275996 Missing ClientAPI Assembly in Visual Studio 2010 Add Reference Dialog
276513 Manifest not embedded in DLL when building a custom model DLL with VC 9.0 or 10.0 for NI VeriStand
282611 Veristand 2010 - Can't reconnect to remote target after network goes down then back up if anything is deployed
282669 Opening a nivstest with a generator mapped to an invalid alias throws cryptic error
283556 Inline the get set channel value by reference VIs
283910 NIVS 2010 Holds Onto one Exported Reflective Memory Channel if RM Channels Were Ever Exported
284264 Scroll Bar in XNET Frame List Window is not clickable
284397 Running a project programatically doesn't load items linked in the system defintion with a relative path
286720 Large Alias Files Fails to Load in Veristand
286762 Veristand 2010 - Can't deploy system definition file that has two targets while one target has a XNET resource
287203 Calling Get Parameter while Gateway is Connection will result in Get Parameter to Return Erroneous Data
287794 Default indicator units do not appear when opening workspace
288388 Large models with many parameter take a long time to load
289232 Bus monitor: Delayed Display
290868 NI VeriStand Stimulus Profile Editor can not be closed, if mapping dialog closed by "X"
291291 csv file with mixed integer and float data gets imported as all integers, truncating the floats
291398 Host TDMS logging creates very fragmented files
293327 Importing Models is different if you use the VeriStand API vs using the System Explorer
293820 System Explorer API Model Constructor Doesn't Import all Model Parameters
295128 graphs leave "invalid" tag prepended to signal name even after the signal becomes valid again
295710 Reflective Memory Data Channels at Some Addresses (or Address Ranges) Cause Unacceptable Latency in RT Engine
298866 If two custom devices use the same page GUID, all tree browsers fail and some crash
299092 Can't add more than two counters to an existing DAQ MIO device
299103 Pressing delete while editing the legend text deletes the channel
300280 Decimated model only has one tick to finish before it's late
301749 Veristand sinewave.c Example Does Not Support ANSI C
305597 Can't delete missing custom devices
306199 Veristand returns error 63 when deploying to target that has the wrong vstand engine version
306847 Reflective memory channels are not faultable
307207 Error 1172 from adding LabVIEW model with outport name that includes a new line character
308014 Can't set default colors on new controls
313529 Faulting a specific model channel faults the wrong channel.


Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  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).