Archived: LabVIEW 8.6 Mobile Module Known Issues

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 8.6 Mobile Module known issues that were discovered before and since the release of the LabVIEW 8.6 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.

Known Issues

The following items are known issues in the LabVIEW 8.6 Mobile Module.

 Installation Known Issues
Known Issue
(Windows 2000) The Mobile Module installs Microsoft ActiveSync 4.2. You might receive a Microsoft Office Outlook error that states Either there is no default mail client or the current mail client cannot fulfill the messaging request. Please run Microsoft Office Outlook and set it as the default mail client.

Workaround—You do not need to install Microsoft Outlook nor does Outlook have to be your default mail client. Click the OK button to continue installation.
The Mobile Module automatically installs ActiveSync 4.2 if ActiveSync is not already installed. When you install the Mobile Module and do not already have ActiveSync, the installer automatically reboots the computer without alerting you. To resolve this issue, rerun the installer (setup.exe) to complete the installation or install ActiveSync before you install the Mobile Module.

Workaround—Rerun the installer (setup.exe) to complete the installation or install ActiveSync before you install the Mobile Module.
If you install LabVIEW and the Mobile Module to custom locations that contain non-ASCII characters, errors occur when you build Mobile VIs into Mobile applications.

Workaround—Install LabVIEW and the Mobile Module to the default installation locations.
 General Known Issues
Known Issue
Passing a control reference through a zero-iteration For Loop can cause a crash.

Workaround—Use a local variable for the control reference instead of using the output tunnel from a zero-iteration For Loop.
Several front panel and block diagram objects behave differently when the execution target is a Mobile target. Refer to the Mobile Module book in the LabVIEW Help for information about different or unsupported front panel or block diagram functionality.
The Mobile Module does not support significant digits.

Workaround—Use digits of precision instead.
If you flatten data that contains an extended precision or complex precision floating-point data type, the flattened data is incompatible with any other LabVIEW version or add-on except the Mobile Module.
Any binary operation involving a dynamic data type and a non-scalar non-dynamic data type, such as a 1D array, does not work correctly.
If you copy and paste global variables, you receive a link error when you try to build the Mobile VI into an application.
When you create a VI that uses multiple global variables, do not copy controls from one global variable to another global variable. Controls copied from one global variable to another global variable result in errors when you build the Mobile VI into an application.
XON/XOFF flow control in serial communication causes a timeout if you use the Serial Compatibility VIs. This is not an issue if you use the VISA VIs and functions.
When a timestamp in a Mobile VI is rounded to the nearest integer, the timestamp is always rounded down to the next lowest integer. The effect of this behavior is that the Round to Nearest and Round to -Infinity functions produce the same output on timestamps.
LabVIEW stores colors as RGB values. Windows Mobile and Windows CE operating systems store colors as BGR values. If you place a color box constant inside of a nested array or cluster constant, the colors might render incorrectly because the red and blue components are exchanged when you build a Mobile VI into a Mobile application.

Workaround—Place the color box constant inside a single array or cluster constant on the block diagram and use the Build Array or Bundle function to nest the array or cluster.
Different Mobile devices have different button behaviors. Use the Button Input VIs example, located in the labview\examples\PDA\button input directory, to determine and test the button behavior for a device. Use the Key Events - Pocket PC example, located in the labview\examples\PDA\key events directory, to determine how to handle key events in an Event structure. You also can open these examples through the NI Example Finder.
Mobile VIs do not support the values of Z, X, or T in digital data controls and digital waveform controls. You can use values of 0, 1, L, and H.
Smartphone menus can have only two top-level menu items no matter how many top-level items are in the VI.
The PDA Pick Color VI does not support Samsung or Motorola Q Smartphones.
The Mobile Module does not support creating a source distribution. If you right-click Build Specifications in the Project Explorer window and select New»Source Distribution from the shortcut menu, LabVIEW displays an error message in the Source Distribution Properties dialog box.
(Windows Vista/XP) You must install the Virtual PC 2007 to use Mobile emulators for debugging or TCP/IP applications.
 Windows Vista Known Issues
Known Issue
ActiveSync has been replaced with Windows Mobile Device Center, which you must download from, in Vista.
If you install the Mobile Module on a computer that runs a non-English version of Vista, you might receive a Command line option syntax error. Type Command/? for Help error.

Workaround—Click the OK button to continue the installation.
 User Interface Known Issues
Known Issue
Users can select items in a tree indicator.

Workaround—Disable the tree indicator.
If you select a multi-needle dial, gauge, or meter control, you can move only the current needle using keys. Pressing the <Tab> key moves the focus to the next control and not the next needle.
If a dial is on a tab control but not on the initially displayed tab, the dial has the background rectangle color of the front panel instead of that of the tab control when the dial is shown.

Workaround—Make sure the tab that contains the dial is shown initially. Or, make sure that the background color of the tab is the same as the color of the front panel.
Charts draw incorrectly when the number of points on screen exceeds the chart history length.

Workaround—Change the chart history length to accommodate the number of points drawn on the chart before it scrolls.
100031 The focus rectangle of the task ring control is partially visible and is not erased when the control is out of focus.
The 2D Boolean OK, Cancel, and Stop buttons do not support different text strings for TRUE and FALSE states.
Scroll bars and multiline inputs/outputs are unsupported for string controls if you use the password display mode.
3D borders on tank indicators do not scale with the rest of the indicator when you build a Mobile VI into an application.
Tab controls redraw slowly when you switch tabs. You might see shadows of the controls on the previous tab as LabVIEW redraws the controls on the current tab.
Autoscaling of the y-axis for multiplot XY graphs is not supported.
Duplicate scales and plot legends are unsupported.
Captions are always displayed behind the control.

Workaround—To resolve this issue for button controls, use Boolean text.
You cannot use front panel data binding with radio buttons controls.
Arrays of DAQmx task name controls are not visible on the front panel of a Mobile application.

Workaround—You can use an array of DAQmx task name controls in a Mobile VI to write values even though the controls are not visible in the Mobile application.
 VIs, Functions, and Structures Known Issues
Known Issue
The Bluetooth Discover function does not return the local Bluetooth device address if the device has a Broadcom Bluetooth function.
When you use the Display Message to User Express VI to display a message to a user, execution of other loops is halted.

Workaround—Use a subVI instead of a dialog box.
The Escape XML and Unescape XML VIs are unsupported.
Dynamic Add/Remove Signals is unsupported.
If you use the .NET Refnum, Event Callback Refnum, or Code Interface Nodes (CINs) in a Mobile VI, you receive an error if you try to build the VI into a Mobile application.
The Mobile Module does not support paths in the Not a Number/Path/Refnum? function.
You must use strict C code in Formula Nodes you use in Mobile VIs. However, LabVIEW does not check the C syntax in the Formula Node syntax while in edit mode. If you build a VI into a Mobile application that contains a Formula Node with non-strict C code, LabVIEW returns a general error.
The Delay Values Express VI and the Trigger and Gate Express VI do not function correctly in Mobile VIs because maintaining state in local variables between calls to a subVI is not supported.
The Configuration File VIs are unsupported.
 Building VIs into Applications Known Issues
Known Issue
The Optimize subVI calls build option is unsupported.
You might receive an error that states This property is writable only when the VI is in edit mode, or this method is available only when the VI is in edit mode. This error occurs if the VI is running on the host and you try to build the VI into an application. You must stop the VI on the host before building.
 Properties and Methods Known Issues
Known Issue
The Mobile Module does not support the Update Value while Typing property for string objects.
 Graphs and Charts Known Issues
Known Issue
The Mobile Module does not support plotting waveforms with more than 32,000 elements.
If you are using the Zoom Chart of Graph VI and set the zoom style to Zoom to Rectangle, the x and y axis changes properly, but the graph is not correct.
If you are zooming a graph or chart in a Mobile application and draw with the log scale, it might appear as if nothing has happened.

Workaround—Choose a larger zoom rectangle.
Pull-down menus are not visible while a chart or graph is updating.

Workaround—You can place the mouse pointer on the pull-down menu to display it to make a selection.
 Tools and Drivers
Known Issue
You must install the VISA driver to use VISA. Select Start»All Programs»National Instruments»VISA»Windows Mobile Driver Installation.
You must install the Virtual PC 2007 to use ARM-based emulators. Download the driver from the Windows Mobile 5.0 Web site.
Projects you created in version 8.0 of the Mobile Module use the Microsoft eMbedded Visual Tools, which you had to download and install. You do not have to download and install these tools with version 8.2 or later of the Mobile Module. However, if the eMbedded Visual Tools are not installed on the host PC, you receive a build error when you build the Mobile VI into a Mobile application.

Workaround—Download and install the eMbedded Visual Tools or use a new target. In version 8.2 or later, targets that are in all capital letters are eMbedded Visual Tools targets. If you need to download and install the eMbedded Visual Tools, visit the National Instruments Web site at and enter pdaevc for more information about the eMbedded Visual Tools.
 Additions to the Help
Known Issue
You can use the Label property to get a reference to the label object of a control or indicator.
You can run Mobile applications built for devices that run Pocket PC 2003 or Windows Mobile 5.0 on devices that run Windows Mobile 6.0. Use a target that runs Pocket PC 2003 or Windows Mobile 5.0 to programmatically download or run Mobile applications from the project.
You now can wire a control reference to the Zoom Chart or Graph VI and the Clear PDA Chart VI.
 Documentation Known Issues
Known Issue
The Detailed Help link in the Context Help window does not open the correct topic for the Inline C Node.

Workaround—Open the LabVIEW Help by selecting Help»Search the LabVIEW Help. Click the Index tab and select Inline C Node.
The Help button in the Add/Remove Headers dialog box does not open the correct help topic.

Workaround—Open the LabVIEW Help by selecting Help»Search the LabVIEW Help. Click the Index tab and select Add/Remove Headers dialog box (Embedded Targets, PDA, TPC).


Additional Resources

Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).