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 2010 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 2010 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 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.
| |||||
| 89687 3SBBPSE9 Return | Cannot make root locus plots part of subplots You cannot make root locus plots part of subplots. Workaround: N/A
| |||||
| 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.
| |||||
| 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.
| |||||
| 201449 Return | A Feedback Node on a Simulation Diagram causes the VI to fail to compile The Feedback Node does not make sense semantically within a Simulation Diagram, due to the fact that most ODE Solvers will execute the diagram multiple times per iteration and may need to reject steps and try again, filling the Feedback Node with bad data. Workaround: Use the Memory block from the Simulation Utility palette. If a delay of greater than 1 is desired you can chain multiple memory blocks in sequence.
| |||||
| 224620 Return | Triggered Subsystems may not perform as expected in certain situations There are two situations where a triggered subsystem may not perform as expected. First, if a node that uses the discrete step size as part of its calculations (such as the discrete integrator) is inside a triggered subsystem, the node will use the global discrete step size rather than the interval between triggers as the discrete step size for its calculations. For example, consider a discrete integrator in a simulation with a discrete step size of .1 inside a triggered subsystem. If the integrator has a constant value of 1 as its input, and it is triggered at t=2 and t=5, its output value after t=5 would be .1, not 2. Second, if a trigger occurs on a time step that is not also a discrete time step (i.e., the trigger occurs at t=1.5, and the discrete step size is set to 1), the triggered subsystem will execute, but none of the discrete nodes inside it will execute. Workaround: N/A
| |||||
| 229977 Return | VI with Simulation opens with broken run arrow but no errors Sometimes a VI that uses Simulation from an earlier version of LabVIEW will be broken after opening. This could be a Subsystem VI or a VI with a Simulation Loop. Clicking the run arrow will open the Error List window, showing the broken VI, but no errors will be listed. Workaround: Select any single node on the Simulation Diagram and choose Edit->Clean Up Diagram (Ctrl-U) Having selected a single node will mean that nothing gets moved by the Clean Up Diagram command, but the VI will become runnable.
| |||||
| 238092 Return | Single Stepping Sim Params are not being updated When you double-click on a single stepping subsystem and change settings beneath the Simulation Parameters heading the newly configured values don't affect the execution of the subsystem call. Workaround: A few possibilities (choose one of the three): 1. Drop a new copy of the subsystem from disk, palette, or icon then configure your settings 2. Force a change to the subsystem by dropping a constant then deleting it then go back and configure your settings 3. Make the Simulation Parameters that you wish to change from default values come from terminal and wire your configuration in
| |||||
| 242420 Return | Direct Transfer Function, State Space, ZPK, and Discrete Filter VIs incorrectly output zero The Transfer Function, State Space, Zero-pole-gain, or Discrete Filter VIs will output only zero if the VI mode changes from indirect to direct through the parameter configuration page. Workaround: Force a mode change through means other than the configuration page. For the discrete blocks, drag the block outside the simulation loop and then move it back.
|
Document last updated on 7/30/2010