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.
This document contains the LabVIEW Education Edition 2009 known issues that were discovered before and since the release of LabVIEW Education Edition 2009. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.
The LabVIEW 2009 Platform Known Issues contains a full listing of known issues, including LabVIEW toolkits and modules.
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.
Issue ID—Contains the number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
Issue Title (in italics)—Describes the issue in one sentence or less.
Problem Description—Describes the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
Workaround—Provides possible ways to work around the problem. The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document.
Reported Version—Contains the earliest version of the NI SoftMotion Module the issue was reported in. If you discover the issue appears in an earlier version of LabVIEW Education Edition 2009 than is reported in this field, you can report that to NI (contact information below) to have the field updated.
Resolved Version—Contains the version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
Date Added—Contains the date the issue was added to the document (not the reported date).
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.
The known issues in this document are organized by the category of issue. Please refer to Developer Zone Article "LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in LabVIEW Education Edition 2009 Known Issues sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| NXT Module | ||||||
| 0000383 Return | Wait for Hot and Wait for Cool conditions are swapped The expected behavior from the Wait for Hot VI and the Wait for Cool VI are incorrect. The stop condition for the Wait for Hot VI should be if the measured temperature is greater than or equal to the set temperature. The stop condition for the Wait for Cool VI should be if the measured temperature is less than or equal to the set temperature. In both cases the actual behavior is the opposite from the expected behavior. Workaround: N/A
| |||||
| 137 Return | Division by ZERO and Infinity yields incorrect values. The Divide function primative in a VI targeted to an NXT outputs an incorrect value in the following cases: 1. 0/0 incorrectly outputs 0. The correct output should be NaN. 2. 1/Inf incorrectly outputs Inf. The correct output is 0. 3. 0/Inf incorrectly outputs Inf. The correction output is 0 Workaround: N/A
| |||||
| 153 Return | Remote Control Application won't halt program The NXT Application Remote Control can start a program by clicking the orange button on the NXT in the Remote Control application window, but the dark grey button in the Remote Control application window will not stop the program. Workaround: End the program by pressing the dark grey button the actual NXT
| |||||
| 189871 Return | Parallel Loops don't execute in Flat Sequence Structure If you have more than one loop in a Flat Sequence Structure the NXT will only run the loop that is highest in the UI order. Workaround: Do not use the Flat Sequence Structure or place each While Loop into its own Flat Sequence Structure.
| |||||
| 190065 Return | Value Property Node Does Not Pass Values You cannot use property nodes to pass a value of a control or indicator without using wires. Workaround: Use local variables instead of Value property nodes
| |||||
| 199 Return | Slow Bluetooth communication on Apple hardware Bluetooth communication on Apple hardware utilizing the Broadcom Bluetooth chip set is much slower than on older Apple hardware or Windows hardware. Workaround: Use a USB Bluetooth dongle instead of the built in Bluetooth hardware
| |||||
| 372 Return | The behavior Wait for Further is the opposite to what is expected. The Wait for Further VI will only exit if the value read by the Sonar sensor is less than the value wire to the Distance input rather than greater than the value wired to this input. Workaround: N/A
| |||||
| 374 Return | Motor Configurator: Update VIs causes Motor Configurator to generate error and abruptly exit. If you edit an existing control and choose to Update VIs upon exit, the motor configurator will generate an error and exit without updating your vis. This happens if you have only configured one control and not the other (DC Motor or Servo). Workaround: Create and save a dummy servo of DC control before updated your VIs even though it will not be used.
| |||||
| 419 Return | Motor VI can use the incorrect value for speed if that value is out of range. In direct mode passing a value of 128 into the Motor VI set the speed to -127 Workaround: Coerce that value that will be input into the Motor VI to between 127 and -127
| |||||
The following items are known issues in LabVIEW Education Edition 2009 Known Issues sorted by Date.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 0000383 Return | Wait for Hot and Wait for Cool conditions are swapped The expected behavior from the Wait for Hot VI and the Wait for Cool VI are incorrect. The stop condition for the Wait for Hot VI should be if the measured temperature is greater than or equal to the set temperature. The stop condition for the Wait for Cool VI should be if the measured temperature is less than or equal to the set temperature. In both cases the actual behavior is the opposite from the expected behavior. Workaround: N/A
| |||||
| 137 Return | Division by ZERO and Infinity yields incorrect values. The Divide function primative in a VI targeted to an NXT outputs an incorrect value in the following cases: 1. 0/0 incorrectly outputs 0. The correct output should be NaN. 2. 1/Inf incorrectly outputs Inf. The correct output is 0. 3. 0/Inf incorrectly outputs Inf. The correction output is 0 Workaround: N/A
| |||||
| 153 Return | Remote Control Application won't halt program The NXT Application Remote Control can start a program by clicking the orange button on the NXT in the Remote Control application window, but the dark grey button in the Remote Control application window will not stop the program. Workaround: End the program by pressing the dark grey button the actual NXT
| |||||
| 189871 Return | Parallel Loops don't execute in Flat Sequence Structure If you have more than one loop in a Flat Sequence Structure the NXT will only run the loop that is highest in the UI order. Workaround: Do not use the Flat Sequence Structure or place each While Loop into its own Flat Sequence Structure.
| |||||
| 190065 Return | Value Property Node Does Not Pass Values You cannot use property nodes to pass a value of a control or indicator without using wires. Workaround: Use local variables instead of Value property nodes
| |||||
| 199 Return | Slow Bluetooth communication on Apple hardware Bluetooth communication on Apple hardware utilizing the Broadcom Bluetooth chip set is much slower than on older Apple hardware or Windows hardware. Workaround: Use a USB Bluetooth dongle instead of the built in Bluetooth hardware
| |||||
| 372 Return | The behavior Wait for Further is the opposite to what is expected. The Wait for Further VI will only exit if the value read by the Sonar sensor is less than the value wire to the Distance input rather than greater than the value wired to this input. Workaround: N/A
| |||||
| 374 Return | Motor Configurator: Update VIs causes Motor Configurator to generate error and abruptly exit. If you edit an existing control and choose to Update VIs upon exit, the motor configurator will generate an error and exit without updating your vis. This happens if you have only configured one control and not the other (DC Motor or Servo). Workaround: Create and save a dummy servo of DC control before updated your VIs even though it will not be used.
| |||||
| 419 Return | Motor VI can use the incorrect value for speed if that value is out of range. In direct mode passing a value of 128 into the Motor VI set the speed to -127 Workaround: Coerce that value that will be input into the Motor VI to between 127 and -127
|
Document last updated on 2/24/2010