Critical Security Update

To help protect your systems, customers using NI driver software 2026 Q2 or earlier should visit ni.com/ni-pal-update and follow the recommended actions.

Archived: NI VeriStand 2010 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.

Overview



The following items are the IDs and titles of a subset of issues fixed between NI VeriStand 2009 and NI VeriStand 2010. If you have a CAR ID, you can search this list to validate that the issue has been fixed.
IDLegacy IDFixed Issue
176113
—
Closing System Explorer while editing a control may lose change
179095
—
Pressing delete key in System Explorer always attempts to delete item, even if editing a control value
179641
—
Invalid alarms use reported using error code for invalid procedure (error -307800)
186811
—
VeriStand SCXI Configuration is Missing SCXI-1100 Module
188910
—
DAQ MIO device cannot have more than 8 lines per port
197274
—
NI VeriStand does not install .NET framework on Windows 2008 Server
202347
—
Error Compiling Model
206055
—
Cannot import models compiled using RTW 2009a
213892
—
Lambda Power Supply Custom Device Does Not Return Values
216044
—
Unable to run more than 7 models compiled with MS Visual Studio C++ 2008 on a multi-core target
219356
—
A synchronization master without a RTSI cable causes the Workspace to fail to connect
220649
—
LIN Custom Device gives deployment error on second deployment
225642
—
Ports in subsystems: Model port data reported on wrong channel
233955
—
NI VeriStand does not read non-double data types correctly
239440
—
After Stop is pressed in the Model Control, a model built with Inline parameters has "invalid mappings" when restarted

 

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