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 LabVIEW 2009 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
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 Developer Zone 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 LabVIEW 2009 Control Design and Simulation Module sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 118492 Return | Cannot generate C code with Optimize SubVI calls and Serial Only both on Subsystem VIs and VIs containing Simulation Nodes fail when attempting to generate code in an Embedded context using certain optimization setting - specifically the combination of Serial Only and Optimize SubVI Calls. Workaround: Either deselect Optimize SubVI Calls or select parallel code generation in your Build Specification options.
| |||||
| 131426 Return | Upgrading a Simulation VI may result in a broken VI If your simulation VI contains a State-Space, Transfer Function, or Zero-Pole-Gain node in a cycle with a SISO model wired to an input terminal, all nodes in the cycle may mutate to a MIMO datatype. Workaround: Delete the vector input wire to first indirect block in cycle that uses a wired model. Wire a scalar value to the input and wait for the type to propagate. Delete the scalar wire and recreate initial wire, it should remain a scalar now.
| |||||
| 145976 Return | Editing a Subsystem VI may not add asterisk (*) to title bar of caller VIs When making edits to a Subsystem VI, which will require recompiling the Subsystem's caller, an asterisk may not appear on the caller VI, indicating that it has changed. However, before closing the caller VI, LabVIEW will still prompt you to save the modified VI and there is no danger of unintentionally losing changes. Workaround: N/A
| |||||
| 156847 Return | Show Buffer Allocations does not work on simulation diagrams Buffer allocation for arrays and clusters do not show up on a simulation loop or subsystem when using the show buffer allocations tool. Workaround: N/A
| |||||
| 159426 Return | Strange mouse pointer behavior using Control Design and Simulation on Mac and Linux The first time you select an item from the Simulation Palette after each LabVIEW launch, it may fail to initialize and drop. Each time you select an item from the Simulation Palette the cursor may display a busy icon until the node is placed on the diagram. Workaround: If item does not appear on the cursor, select it again from the palette. If the busy icon appears for an inordinate amount of time, try to place the node on the diagram.
| |||||
| 163739 Return | Control Design MathScript functions not listed by "help classes" Typing help classes in the MathScript window lists help for classes installed with the MathScript RT Module, but does not show Control Design and Simulation classes. Workaround: Type help cdt to see the help for classes installed by the LabVIEW Control Design and Simulation Module.
| |||||
| 167071 Return | Simulation Trim and Linearize will not work on VxWorks targets Attempting to Trim or Linearize a Subsystem VI on a VxWorks target will result in an error. Workaround: Use another target such as PXI or Desktop.
| |||||
| 172558 Return | External model library interface does not automatically download to target. External model library interface does not automatically download to target. Workaround: Place a Call Library Function node that points to the library and hide it behind a case structure that always executes the empty case. This causes RT to download the shared library to the target and load it when the VI runs, or ftp the file to the target.
| |||||
| 174799 Return | Documentation: Control Design Assistant examples do not have links to help Control Design Assistant examples are missing links to the HTML help. Workaround: Browse for the HTML page in the help.
| |||||
| 174841 Return | Dependency conflicts for internal VIs in stored in vi.lib may appear when upgrading projects When using a LabVIEW project containing VIs last saved in a version before 8.6, dropping blocks onto a new VI may result in dependency conflicts relating to internal VIs stored in vi.lib. Workaround: Mass compile the project's VIs before opening the project.
| |||||
| 174968 Return | Some Control Design Assistant Examples have trouble with localized OS Opening some of the examples in an OS that uses a comma separator rather than a decimal separator will present a Warning dialolg and won't work. Workaround: Change the separator to a decimal in the localization settings.
| |||||
| 175714 Return | Collector causes crash in executable built for ARM Collector causes crash in executable built for ARM Workaround: Pass an array of data (doubles or clusters) into a Memory block that feedsback to itself and use Replace Array Subset (or Build Array for an arbitrary length) on each step of the Sim Loop. If using anything other than Euler or Discrete Only solvers, put the Replace Array Subset function inside a subVI and mark the subvi for execution on Major Steps only.
| |||||
| 175715 Return | Vector Transport Delay causes runtime error on ARM Vector Transport Delay causes runtime error on ARM Workaround: Use index array and use the scalar version of transport delay.
| |||||
| 175716 Return | Generated C code for Control & Simulation loop fails to compile if "Generate Debug Info" is TRUE Building a simulation for a Windows Console target and setting Generate Debug Info to true will cause an error. Workaround: Turn off Generate Debug Info.
| |||||
| 175721 Return | Vector Discrete Unit Delay causes runtime error on ARM Using the vector Discrete Unit Delay causes runtime error on ARM Workaround: Use MIMO transfer function with correct number of delays.
| |||||
| 181037 Return | Continuous Extended Kalman Filter, Continuous Nonlinear Noisy Plant, or Polymorphic Subsystem fails to download to RT Downloading a VI to RT fails if the VI contains a polymorphic susbsystem. The Continuous Extended Kalman Filter and Continuous Nonlinear Noisy Plant blocks from the the Simulation->Estimation palette are two examples of polymorphic subsystems included with LabVIEW. Users have been able to create their own since as early as LabVIEW 8.2. Workaround: Replace the Polymorphic Subsystem with the specific instance VI that is required. 1. Right-click the Polymorphic Subsystem block and select "Open Polymorphic VI" 2. Open the desired Instance VI from the Polymorphic VI by double-clicking it 3. Double-click the Polymorphic Subsystem block and note the configured values 3. Delete the Polymorphic Subsystem block 4. Drop the Instance Subsystem VI by dragging it to the block diagram from the VI Icon 5. Double-click the new Subsystem block and reset configured values 6. Rewire terminals on the new Subsystem block
| |||||
| 39212 41CA877V Return | CD Canonical State-Space Realization VI does not support MIMO system models The CD Canonical State-Space Realization VI works only with single-input single-output (SISO) system models. Therefore, if you wire a multiple-input multiple-output (MIMO) system model to this VI, the VI recognizes only the first (0th) element of this system model. Workaround: Use the Array functions to index a MIMO system manually and send each element to this VI.
| |||||
| 48302 3QPBCTDL Return | Broken Save and Load buttons in configuration dialog boxes If you open the configuration dialog box of the State-Space, Transfer Function, Zero-Pole-Gain, Lookup Table 1D, or Lookup Table 2D functions and click the Cancel button, the Save and Load buttons might not work the next time you open the dialog box. Workaround: Select a different parameter then return to the Lookup Table parameter
| |||||
| 49285 3YC9IPMP Return | Compiling subsystem erases clipboard Compiling a simulation subsystem erases the contents of the Windows clipboard. Workaround: N/A
| |||||
| 89687 3SBBPSE9 Return | Cannot make root locus plots part of subplots You cannot make root locus plots part of subplots. Workaround: N/A
| |||||
| 184832 Return | Simulation Model Converter may crash LabVIEW when Simulink is installed and MDL cannot be compiled When converting MDLs on a computer with Simulink installed, the MDL is compiled so that a more accurate model can be produced. If the MDL cannot be compiled, an unhandled error propagates back to LabVIEW and causes a crash. Usually, this occurs because the MDL is not runnable or has parameters involving workspace variables that are undefined. Workaround: Make sure that your MDL is runnable in Simulink. If your MDL has parameters that depend on workspace variables, be sure to provide a .M file initialization script that defines all of those variables.
| |||||
| 155420 Return | A Function Block Appears Twice in a Project When Dropped Inside Simulation Node When you drop a Function Block inside a Simulation Loop, the block and its parameters will be populated in the project twice. Workaround: Place the Function block inside a subVI. This will prevent the second instance of the function block inside the project.
| |||||
| 173772 Return | Single-stepping subsystems do not execute in LabVIEW built applications. Single-stepping subsystems do not execute in LabVIEW built applications. All subsystem outputs will remain at default values. Workaround: None
| |||||
| 175791 Return | Simulation blocks with unwired output can generate errors in an Embedded program When using a Simulation block in an ARM application or generated C code you may encounter an error if the output of the block is unwired. Workaround: Wire the block output to something like a tunnel on the border of the Sim Loop.
| |||||
| 201652 Return | Save for Previous does not work with Simulation The Save for Previous may be used on a VI containing a LabVIEW Simulation loop or subsystem, but the resulting VI will not be executable and may cause a crash when opened. Workaround: None
|
Document last updated on 6/29/2010