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 known issues
that were discovered before and since the release of
LabVIEW 2010 Mobile Module. 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.
Each Issue appears as a row in the table and
includes these fields:
Legacy ID - The issue's legacy
ID from NI's deprecated bug reporting database (if applicable)
Reported Version - the earliest version of LabVIEW the
issue was reported in
Resolved Version - version the issue was resolved or was no
Date Added - the date the issue was added to the document
(not reported date)
The Known Issues Document displays the issues by
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.
Additional software is needed for debugging application in the emulator on Windows Vista/ Windows 7
If you are using the LabVIEW Mobile Module on Windows Vista or Windows 7 operating systems, then you need to install Virtual PC 2007 in order to debug your application on the emulator. You can find Virtual PC 2007 here: http://www.microsoft.com/downloads/details.aspx?FamilyId=04D26402-3199-48A3-AFA2-2DC0B40A73B6&displaylang=en#filelist
Using property nodes for Array elements can cause build errors
If you use property nodes for array elements on your Front Panel, your application mught fail to build with an error of the format: 'Numeric__xxxxxxxxx_ctlid' : undeclared identifier. (where x is some numeric digit)
Japanese language strings in Mobile module can cause unexpected compiler errors
When using the Mobile Module with Japanese version of LabVIEW, strings - constants, controls, free labels etc. can contain bad characters that cause compilation errors. For accurate representation, LabVIEW does not represent these characters by their ASCII codes but they can also lead to badly formatted C code.
Workaround:You can contact National Instruments for support by going to ni.com/ask. You might need to send in the C file that contains the formatting error and the corresponding VI. National Instruments support will help you identify the bad character and replace/remove it.
Waveform Graph does not automatically update when writing values outside of of displayed scale
Waveform Graph on a Mobile VI Front Panel does not automatically update when values are written to the region outside the displayed area.
Workaround:Perform actions that prompt a screen refresh, like bringing up the soft keyboard.
The GSM Disconnect.vi doesn't work more than once in a Mobile application
The problem can be seen after performing the first call. When a second call is made after the first closes successfully, it keeps ringing without executing the close VI.
Only 17 characters are returned by bluetooth discover function with broadcom PDA
The bluetooth discover function found in examples such as Advanced Bluetooth Client.vi only returns the first 17 characters of the bluetooth devices it is querying.
Event structures that contain cases triggered by three or more Front Panel elements can cause runtime errors
Event structures use an "Event Data Cluster" to keep track of the sources of each Event case. When this cluster becomes big, it can cause runtime errors that might display a message like: "App failed. Error code xxxxxxxxx. Unable to allocate memory." (where x is some numeric digit)
Workaround:Instead of configuring multiple sources to trigger the same event case, you can create a distinct case for each source.
You probably noticed we have a new look, but our focus remains on you. We've expanded our offerings to better serve you so that you can take on the complex challenges facing humanity today, tomorrow, and for the next 100 years. It's time. Let's Engineer Ambitiously.