Archived: LabVIEW 2010 Mobile Module Known Issues

Publish Date: Jul 22, 2018 | 4 Ratings | 1.00 out of 5 | Print

Overview

This document has been archived and is no longer updated by National Instruments.

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:
  • Issue ID
  • Legacy ID - The issue's legacy ID from NI's deprecated bug reporting database (if applicable)
  • Issue Title
  • Problem Description
  • Workaround
  • Reported Version - the earliest version of LabVIEW the issue was reported in
  • Resolved Version - version the issue was resolved or was no longer applicable
  • Date Added - the date the issue was added to the document (not reported date)

Document Organization

The Known Issues Document displays the issues by issue category.

Known Issues by Category

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.

Contacting NI

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.

Known Issues by Category

The following items are known issues in LabVIEW 2010 Mobile Module Issues sorted by Category.

Building and Distributing LabVIEW Applications
237798 Additional software is needed for debugging application in the emulator on Windows Vista/ Windows 7
235326 Using property nodes for Array elements can cause build errors
237855 Japanese language strings in Mobile module can cause unexpected compiler errors
Controls and Indicators
187912 Waveform Graph does not automatically update when writing values outside of of displayed scale
Functions, VIs, and Express VIs
145003 The GSM Disconnect.vi doesn't work more than once in a Mobile application
178424 Only 17 characters are returned by bluetooth discover function with broadcom PDA
184443 Event structures that contain cases triggered by three or more Front Panel elements can cause runtime errors



ID Known Issue
Building and Distributing LabVIEW Applications
237798

Return
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

Workaround: N/A

Reported Version: 2010    Resolved Version: 2011    Added: 07/29/2010
235326

Return
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)

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 07/30/2010
237855

Return
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.

Reported Version: 2010    Resolved Version: N/A    Added: 07/30/2010
Controls and Indicators
187912

Return
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.

Reported Version: 2009    Resolved Version: 2011    Added: 07/30/2010
Functions, VIs, and Express VIs
145003

Return
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.

Workaround: N/A

Reported Version: 8.5.1    Resolved Version: 2011    Added: 08/03/2009
178424

Return
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.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 08/03/2009
184443

Return
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.

Reported Version: 2009    Resolved Version: N/A    Added: 07/30/2010

Document last updated on 7/6/2012

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit