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 number given in this document. If you have feedback on this specific document, please contact NI on this NI Developer Zone post.
The following items are known issues in LabVIEW 2009 Microprocessor SDK sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Building and Distributing LabVIEW Applications | ||||||
| 97011 Return | No place to specify a name for the UI Application Build Specification for the Unix UI Target The UI Application Build Specification for the Unix UI Target is named "UI Application #" by default and cannot be renamed by the user. Workaround: N/A
| |||||
| 174390 Return | Using TCP or Serial debugging with Timed loops in a VI might display unexpected behavior When using TCP or Serial Debugging with Timed Loops if the execution stops at a breakpoint, it might not resume upon clicking Continue. Workaround: N/A
| |||||
| 117279 Return | C Generator Test Framework might time out unnecessarily The LabVIEW C Generator Test Framework might time out on an automated test even though the built application executes successfully. Workaround: Run the application outside of the LabVIEW C Generator Test Framework.
| |||||
| 171757 Return | Waveform Data type is not supported with Generate C Function Calls option Waveform datatype is not supported when an Application is built with the "Generate C Function Calls" option. The generated code will crash during waveform control assignment. Workaround: N/A
| |||||
| 176237 Return | The Target Editor does not support paths inside LabVIEW LLBs The Microprocessor SDK Target Editor (Tools>>Microprocessor SDK>>Target Editor...) does not support file paths inside LLBs. It incorrectly reports them as invlalid paths. Workaround: N/A
| |||||
| 109393 Return | When using LabVIEW Front Panels with embedded targets, cosmetic changes to the Front Panel do not cause the Application to Rebuild If cosmetic changes are made to Front Panels on embedded targets, they do not cause the Application to Rebuild if the user presses the Run Button. Workaround: The VI should be saved before pressing the Run Button.
| |||||
| Controls and Indicators | ||||||
| 173242 Return | Using the Zoom to Fit option on a Waveform Chart sets the X-axis to an incorrect position Using Zoom to Fit on a Waveform Chart might set the X-axis on the chart to a previous position on the time scale and the Waveform Chart might appear to not update. Workaround: Update scale on the X-axis to display most recent position.
| |||||
| 147451 Return | On Embedded targets, Buttons with "Latch when pressed" mechanical actions keep triggering if kept pressed Buttons with the "Latch when pressed" mechanical action should trigger only once per press. However on embedded targets, they keep triggering if the button is kept pressed, Workaround: N/A
| |||||
| 168395 Return | Graph labels are drawn improperly when they are bigger than the corresponding axis When using LabVIEW front panels with embedded targets, the axis labels might be drawn improperly if they are bigger than the axis itself, on the graph. Workaround: N/A
| |||||
| Documentation | ||||||
| 141236 Return | Incorrect information in Microprocessor SDK Porting Guide The Microprocessor SDK porting guide (MicroprocessorSDK_Porting_Guide.pdf, Chapter 10 Testing your target implementation>>LabVIEW C Generator Test Framework >>Default Configuration Files) says "Tokens in the default configuration file override the tokens in an individual configuration file." This is incorrrect. Tokens in individual configuration file override the default configuration file. Workaround: N/A
| |||||
| Functions, VIs, and Express VIs | ||||||
| 114912 Return | Flattening and Unflatening certain data types cause runtime crashes Flattening and Unflatening the following data types cause crashes: AppRefNum, VI RefNum, UDP connection, File Refnum, Semaphore refnum, Analog Waveform, Digital Waveform. Workaround: N/A
| |||||
| 133029 Return | The Scale By Power Of 2 function yields different results on embedded targets for negative numbers The Scale By Power Of 2 is implemented as an arithmetic shift operation and it is implementation dependent for negative numbers. Results might vary from target to target. Workaround: N/A
| |||||
| Installation and Activation | ||||||
| 155650 Return | Documentation for the Unix UI Target does not list "gcc-g++ 3.4.4 or later" as a dependency The Unix UI Target depends on "gcc-g++ 3.4.4 or later". The documentation does not list this as a requirement. Workaround: This component needs to be selected explicitly when installing Cygwin.
| |||||
| LabVIEW Project | ||||||
| 173174 Return | C Style Function calls might not work with Reentrant VIs Enabling C Style Function Calls for an application might generate unexpected results if one or more VIs in the application have Reentrant execution enabled and get invoked in parallel. Workaround: N/A
| |||||
| Miscellaneous | ||||||
| 176237 Return | The Target Editor does not support paths inside LabVIEW LLBs The Microprocessor SDK Target Editor (Tools>>Microprocessor SDK>>Target Editor...) does not support file paths inside LLBs. It incorrectly reports them as invalid paths. Workaround: N/A
| |||||
Document last updated on 8/12/2009