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.
You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID. If you have feedback on this document, please contact NI on this NI Forum post.
National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. However, NI has become aware of a number of issues of potential significance regarding Microsoft Windows 7. To learn how Windows 7 affects your use of NI products, visit ni.com/info and enter the Info Code windows7.
The following items are known issues in NI VeriStand 2010 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| ActiveX and .NET | ||||||
| 275996 Return | The NationalInstruments.VeriStand.ClientAPI.dll assembly is missing from the Visual Studio 2010 Add Reference dialog The NationalInstruments.VeriStand.ClientAPI.dll assembly is missing from the Visual Studio 2010 Add Reference dialog. Note however that Visual Studio 2005 and 2008 Add Reference dialogs correctly list this assembly. Workaround: From the Visual Studio Add Reference dialog, browse to: <Windows> \Assembly\GAC_MSIL\NationalInstruments.VeriStand.ClientAPI\ 2010.0.0.0__a6d690c380daa308 and select the NationalInstruments.VeriStand.ClientAPI.dll assembly.
| |||||
| Custom Device | ||||||
| 242105 Return | Get Item Property (Path).vi can return an invalid path on a VxWorks target The Custom Device API function Get Item Property (Path).vi can return an invalid path on a VxWorks target. This function will return the path as saved on the host desktop machine. It is not properly formatted for the VxWorks OS. Workaround: Instead of using the function Set Item Property (Path).vi to save a path property, use the function Set Item Property (String Array).vi and cast the path into an array of strings. Then use Get Item Property (String Array).vi in the Driver VI on the target and cast the array of strings back to a path.
| |||||
| 247218 Return | Unable to add multiple custom devices of the same type in VeriStand 2010 Unable to add multiple custom devices of the same type in VeriStand 2010 Workaround: Rename the existing Custom Device first to make sure it's not the default name. Then add the second Custom Device.
| |||||
| 248320 Return | Reset Dependencies does not work properly Reset Dependencies assumes that the property name Dependency_%d starts at 0 but adding a new Dependency starts at 1. Workaround: N/A
| |||||
| 248334 Return | Get Custom Device Dependencies VI does not work Error 36 occurs if you call NI VeriStand - Get Custom Device Dependencies.vi in a custom device's engine. As well, an array of one element is always returned if NI VeriStand - Get Custom Device Dependencies.vi is call in the configuration portion of the custom device. Workaround: N/A
| |||||
| 253699 Return | Custom Device Template Tool in NI VeriStand 2010 fails with localized LabVIEW Error -4500 occurs when you run the Custom Device template tool with a localized version of LabVIEW. Workaround: Either create the custom device in an English version of LabVIEW or create the project manually.
| |||||
| 298866 Return | If two custom devices use the same page GUID, the system explorer becomes unresponsive If two custom devices use the same page GUID, the system explorer becomes unresponsive Workaround: Change the GUID of one of the custom devices
| |||||
| Deploying to a Target | ||||||
| 149703 Return | After connecting using LabVIEW to a RT target that has NI VeriStand installed, the VeriStand engine will no longer launch When connecting to a RT using a LabVIEW, the VeriStand engine will not launch even after rebooting the RT target. Connecting to the RT target using LabVIEW unsets NI VeriStand as a startup application on the RT target. Workaround: Using Measurement & Automation Explorer, reinstall NI VeriStand to the RT target.
| |||||
| 178790 Return | If system definition file is not refreshed after updating a FPGA bitfile, the error is misleading After a FPGA bitfile has been recompiled or updated, the system definition files that use the bitfile need to be refreshed. If this is not done an error is correctly reported when the system definition file is loaded by the VeriStand engine. However the error explanation is misleading. Workaround: When error -63106 is reported it means that the FPGA configurations need to be refreshed. Open the system definition file and refresh each of the FPGA targets.
| |||||
| 254228 Return | Custom devices added to a single target are deployed to all targets in a system defintion If you have a system definition with multiple targets in it, any custom devices on a single target are actually deployed to all targets. Workaround: N/A
| |||||
| 282611 Return | Cannot reconnect to remote target after network goes down then back up if anything is deployed After deploying to a remote target, if the network communication goes down and then back up, you will not be able to reconnect or redeploy to the target. Workaround: Reboot the remote system and the redeploy from the Project Explorer after it comes back up
| |||||
| 286762 Return | Cannot deploy system definition file that has a cRIO target and another target has a XNET resource If you created a system definition file that has two controllers (e.g. one cRIO and one PXI) and have an XNET resource configured under one of the targets, you will not be able to deploy the system definition file because it will try to deploy the XNET resource to both targets and cRIO doesn't support XNET. Workaround: N/A
| |||||
| 306199 Return | Veristand returns error 63 when deploying to target that has the wrong NI VeriStand engine version Veristand returns error 63 (The network connection was refused by the server) when deploying to target that has a NI VeriStand engine version that does not match the version being used on the host machine. Workaround: Reinstall the correct version of the NI VeriStand engine to the target.
| |||||
| 316421 Return | A system using a SMIO X Series board will hang when during undeployment If a NI VeriStand system uses a SMIO X Series board, it will hang when it undeploys from the target. Workaround: This was an issue in the DAQmx driver and was fixed in DAQmx 9.5.
| |||||
| Documentation | ||||||
| 177226 Return | Context help is unavailable for several System Explorer configuration pages When using the context help (Ctrl-H) in the System Explorer window, for several of the pages the context help window is empty. Workaround: Although not all pages have context help, some pages, such as the Controller page, Calculated Channels page, and Stimulus page have help topics and context help. On these pages, move the cursor over items to view descriptions. For other pages refer to the help topic for the page. Go to the menu Help>>Help for this Page to view help for a specific page.
| |||||
| Miscellaneous | ||||||
| 176126 Return | Error code when using Execution API when NI VeriStand is not running is not specific. If NI VeriStand is not running when you use the Execution API a .NET exception error is returned. The error number is 1172. It is not obvious from the error that the reason for the error is that NI VeriStand is not running. Workaround: Make sure NI VeriStand is running before using the Execution API.
| |||||
| 208943 Return | TDMS Viewer does not show initial timestamp correctly TDMS Viewer, in particular the Analog values (graph) tab, does not show the correct timestamp (it shows 1/1/1904, the initial timestamp also on LabVIEW) for .tdms files logged by Veristand Workaround: N/A
| |||||
| 241408 Return | Built in thermocouple scaling does not work for 9219 Built in thermocouple scaling does not work for 9219 Workaround: N/A
| |||||
| 306847 Return | Rreflective memory channels are not faultable Reflective memory channels are not faultable Workaround: N/A
| |||||
| 308014 Return | Can't set default colors on new controls on the Workspace Can't set default colors on new controls on the Workspace 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.
| |||||
| Model Interfacing | ||||||
| 149395 Return | Only signals marked as test points can be probed when running a model as a MDL Only signals marked as test points can be probed when running a model as a MDL Workaround: Mark the signals you want to probe as a test point, before importing the model in System Explorer.
| |||||
| 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.
| |||||
| 222546 Return | Model inports and outports cannot be configured with a default value Model inports and outports cannot be configured with a default value Workaround: Use the Model Initial Values add-on: decibel.ni.com/content/docs/DOC-13955
| |||||
| 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.
| |||||
| 231904 Return | VxWorks compiler for building models is not supported on Vista or Windows 7 The VxWorks compiler used for building out files for RT is not supported on Windows Vista or 7. Workaround: You need Windows XP in order to create a model out file. Once created you can use the the model out file on any of the supported OSes including Windows Vista and Windows 7.
| |||||
| 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.
| |||||
| 249210 Return | Matlab crashes when running a project with a .mdl file If an .mdl file located in the same directory as the system definition file, or a subdirectory, is added to the system definition, Matlab may crash when the VeriStand project is deployed. Workaround: Move the .mdl file outside of the same directory as the system definition to prevent relative paths from being used.
| |||||
| 247357 Return | Model Parameter manager slow with large set of parameters Model Parameter manager slow with large set of parameters Workaround: Import fewer parameters or use the Host Execution API to set the parameter value directly
| |||||
| 258349 Return | .lvmodel generation fails if VI is named model.vi If you try to build a .lvmodel out of a VI named model.vi, the build will fail with error 1054. Workaround: Rename the VI to a different name.
| |||||
| 276513 Return | Manifest not embedded when building a custom model DLL in Visual Studio 9.0 or 10.0 Manifest not embedded when building a custom model DLL in Visual Studio 9.0 or 10.0 Workaround: Add "mt.exe -manifest $@.manifest -outputresource:$@;2" to your .mak file.
| |||||
| 288388 Return | Large models with many parameter take a long time to load It takes a very long time (over a minute) to load load the list of parameters for large models. Workaround: N/A
| |||||
| 300280 Return | Decimated model only has one tick to finish before it's late A decimated model only has one tick to complete, even though it should get all N ticks. As well, if a decimated model is late, no other models will run until it completes. Workaround: N/A
| |||||
| 307207 Return | Error 1172 from adding LabVIEW model with outport name that includes a new line character Error 1172 from adding LabVIEW model with outport name that includes a new line character Workaround: Do not have indicators with new line characters in the name
| |||||
| 317883 Return | Using % in a block name causes a Simulink model to fail to build Using % in a block name causes a Simulink model to fail to build Workaround: Do not use % in the block name.
| |||||
| Performance | ||||||
| 176118 Return | Errors from the VeriStand engine on RT, may be reported with the explanation that it is an unknown error When errors from the VeriStand engine on RT is reported on the host it may not have the correct explanation. The explanation may be reported as unknown error. This happens when the corresponding driver is not installed. The correct error number is reported but there is no explanation. Workaround: Make sure NI-DAQmx, NI-RIO and NI-CAN is installed on the host computer.
| |||||
| 243455 Return | The Stop Macro Player function hangs if the macro is currently paused The Stop Macro Player function hangs indefinitely if the macro is currently paused. This affects the Macro Player tool and the execution API. This can happen, for instance, if you pause a macro running in the Macro Player tool and then hit Stop. The tool will then hang. When you try to close Project Explorer or the Workspace window, you will see a dialog indicating that the Macro Player tool VI is being reset. At this point, VeriStand itself is hung. Workaround: Do not stop a paused macro. Instead, briefly start the macro and then stop it.
| |||||
| 251326 Return | XNET bus monitor does not display frames if raw frame logging is used XNET bus monitor does not display frames if raw frame logging is used Workaround: Reduce the number of bytes to read on the raw frame data logging setup.
| |||||
| 279698 Return | DAQ DO doesn't update if an FPGA personality is also present When you have a system definition with both a DAQ and an FPGA card, the digital output of the DAQ board doesn't update. Workaround: 1) Unset the FPGA board as chassis master. Visit the controller page and set it to auto-timing which will use the MHz timing source. 2) Include an AI or AO channel to the DAQ configuration
| |||||
| 255808 Return | UDP Waveform dt incorrect if LP decimated - disrupts Workspace Graphs If you set the Data Processing Loop decimation to be a factor other than 1, then the dt of UDP waveform data packets is not correct. Workspace graphs get affected by this and think they are missing data which leads to an increase in CPU usage. Workaround: N/A
| |||||
| 284874 Return | Cannot remove scaling from a channel with the Channel Scaling and Calibration Tool If scaling is set on a channel through the Channel Scaling and Calibration workspace tool, the scaling cannot be removed using the tool. Workaround: Use the API to remove scaling or keep the scaling but make a 0 offset and the first order term equal to 1.
| |||||
| 286798 Return | Repeatly opening and closing a project in VeriStand 2010 cuases a memory leak The size of the NI VeriStand.exe grows in memory when opening/closing a project which eventually slows down edit-time performance. Workaround: Occasionally close VeriStand to remove these memory allocations.
| |||||
| 289232 Return | Display is delayed in the Bus Monitor If there is a lot of data going to the bus monitor, the displayed frames are delayed by several minutes due to the time it takes to process and display the values. Workaround: N/A
| |||||
| 291398 Return | Host TDMS logging creates very fragmented files When TDMS logging is done on the host machine, the files created are very fragmented and larger than expected. Workaround: N/A
| |||||
| 287794 Return | Default indicator units do not appear when opening workspace When the workspace contains a control/indicator that is mapped to a channel with default units, the unit label does not appear when opening the workspace. Opening and closing the properties for the control/indicator causes the unit label to appear. Workaround: Use the "New Units" field of the indicator instead.
| |||||
| 291291 Return | A csv file with mixed integer and float data gets imported as all integers A csv file with mixed integer and float data gets imported as all integers and truncates the floats. Workaround: In your csv file put a decimal point after the integer values (eg. 2.0)
| |||||
| 295710 Return | Reflective Memory Data Channels at Some Addresses Causes Latency in the RT Engine Some Read data channels at some addresses, a single data channel can cause large latency. At other addresses, the data channel behaves as expected until another read data channel is added. Workaround: N/A
| |||||
| 300280 Return | Decimated model only has one tick to finish before it's late A decimated model only has one tick to complete, even though it should get all N ticks. As well, if a decimated model is late, no other models will run until it completes. Workaround: N/A
| |||||
| 284915 Return | Channel calibration data does not follow the channel but scaling does If you have two identical system definitions, scaling that's been applied to Channel A in System Definition A also gets applied to Channel A in System Definition B. However, the calibration data does not. Workaround: N/A
| |||||
| System Explorer | ||||||
| 244558 Return | Clicking add data folder for reflective memory throws error If you click 'add data folder' in system explorer it throws error -307602. Workaround: Right click reflective memory and select add data folder instead
| |||||
| 255983 Return | Reversed transmitted/received CAN frames when importing into VeriStand VeriStand assumes that a CAN database file is written from the perspective of the controller. If a user imports a database written from the perspective of the device under test, the incoming and outgoing frames are reversed. Workaround: N/A
| |||||
| 246557 Return | Missing signals when importing a .dbc file to NI VeriStand 2010 If you have the same frame used in multiple ECUs, importing the .dbc file may result in missing signals from those frames or error 1088. Workaround: If the same frame is used in multiple ECUs, export them into their own FIBEX files.
| |||||
| 250448 Return | System configurations with custom devices do not upgrade from 2009 to 2010 due to bad property data type Error 1172 occurs if deploying a System Definition that has been upgraded from 2009 to 2010 and has a custom device in it. Workaround: N/A
| |||||
| 299093 Return | AI channels are not enumerate correctly for DAQ devices with 16 differential AI chennels If you add a MIO DAQ device and specify 16 AI differential channels, it enumerates them AI0 to AI7 and then AI16 to AI23. Workaround: Add the DAQ card with the default input configuration and then change the channels to differential after adding it
| |||||
| 286720 Return | Large alias files fails to load in NI Veristand Importing very large alias files will cause NI VeriStand to hang. Workaround: N/A
| |||||
| 299092 Return | Cannot add more than two counters to an existing DAQ MIO device Cannot add more than two counters to an existing DAQ MIO device in the system definition. Workaround: Delete the device and add it back in with the desired number of counters
| |||||
| 305597 Return | Cannot delete missing custom devices If you open a system definition with a custom device inside it and that device is not installed on your system the delete button is greyed out and you cannot delete it. Workaround: The missing custom device needs to be installed on the machine in order to delete it from the system definition
| |||||
| Upgrade - Migration | ||||||
| 318323 Return | Opening a VI with a .NET indicator or control in a newer version of LabVIEW picks the old assembly from GAC When opening up one of older 2010 VIs in LabView 2011 that used the NI VeriStand API, it doesn't upgrade successfully. The VI expected to find the 2011.0.0.0 assembly but found the 2010.0.0.0 instead. Workaround: See KnowledgeBase.
| |||||
| Using the API | ||||||
| 244847 Return | VeriStand Gateway crashes after several API calls Repeated deploying and undeploying a System Definition using the API causes the VeriStand Gateway to crash. Workaround: N/A
| |||||
Document last updated on 10/12/2011