LabVIEW 8.0.1 PDA Module Readme
February 2006
This file contains important last-minute information about the LabVIEW 8.01 PDA Module. Refer to the LabVIEW 8.0.1 Readme, available by selecting Start»All Programs»National Instruments»LabVIEW 8.0»Readme and opening readme_8_0_1.html, for LabVIEW known issues.
Refer to the National Instruments Web site for the latest information about LabVIEW.
Support for Windows Mobile 5.0
New Emulators
New Windows Mobile 5.0 Features
Enabling Debugging
Enumerating Pocket PC 2003 and Windows Mobile 5.0 Targets
If You Receive a "Failed to open VPC Network Driver" Error When You Launch an Emulator
Known Issues
Changes from 8.0
LabVIEW 8.0 PDA Module Readme
The LabVIEW 8.0.1 PDA Module for Pocket PC enables creating, building, deploying, running, and debugging PDA application on Windows Mobile 5.0, as well as Pocket PC 2003 devices. You must install the following tools to enable Windows Mobile 5.0 support:
- Microsoft Visual Studio 2005 Standard or Professional Edition
- ActiveSync 4.1 or later
- Windows Mobile 5.0 SDK for Pocket PC
- Visual Studio 2005 Device Command Shell (DCS)
Note: You do not need to upgrade your Microsoft tools if you do not need support for Windows Mobile 5.0.
Refer to the KnowledgeBase at ni.com for more information about installing these tools.
Visual Studio 2005 and Windows Mobile 5.0 SDK for Pocket PC include new Pocket PC 2003 and Windows Mobile 5.0 emulators. After you install the new tools, the LabVIEW PDA Module enumerates only these new emulators. You can no longer add older Pocket PC 2003 emulators to the LabVIEW project.
The LabVIEW 8.0.1 PDA Module includes the following new features for Windows Mobile 5.0:
- High-resolution support for Windows Mobile VGA devices
- Picker Picker VI
- Camera Capture VI
- New VI template for a 5.7" HMI screen (This new template also supports Pocket PC 2003)
You must configure ActiveSync and the new Pocket PC emulators to enable debugging with the LabVIEW PDA Module.
Configuring ActiveSync
Complete the following steps to enable debugging with the LabVIEW 8.0.1 PDA Module.
- Launch ActiveSync.
- Select File»Connection Settings to open the Connection Settings dialog box.
- Place a checkmark in the Allow connection to one of the following checkboxes and select DMA from the drop-down list.
- Click the OK button.
Configuring Pocket PC Emulators for Debugging
Complete the following steps to enable debugging with the new Pocket PC emulators and the LabVIEW 8.0.1 PDA Module.
- In LabVIEW, right-click a Pocket PC emulator target in the Project Explorer window and select Properties from the shortcut menu.
- Click the Launch Device Emulator Manager button.
- Right-click the emulator you want to configure and select Connect from the shortcut menu.
- Select File»Configure on the emulator to open the Emulator Properties dialog box.
- Click the Network tab and place a checkmark in the Enable NE2000 PCMICIA network adaptor and bine to: checkbox.
- Click the OK button.
- Select File»Reset»Soft on the emulator to reset the emulator.
- Save the emulator state when prompted.
Cradling the Emulator if You Are Not Connected to a Network
You must cradle the emulator to enable debugging if the host PC is not connected to a network. Complete the following steps to cradle the emulator.
- Launch the Device Emulator Manager
- Right-click the emulator you want to cradle and select Connect from the shortcut menu.
- Right-click the emulator and select Cradle from the shortcut menu.
To disconnect from ActiveSync, right-click the emulator and select Uncradle from the shortcut menu.
The LabVIEW PDA Module enumerates Pocket PC 2003 and Windows Mobile 5.0 targets. You can filter the types of targets the LabVIEW PDA Module enumerates by creating a wm50devs.txt file in the labview\PDA directory.
To enumerate Pocket PC 2003, Smartphone 2003, and Windows Mobile 5.0 targets, enter the following in the wm50devs.txt file:
[Pocket PC | Smartphone] | Windows Mobile 5.0
To enumerate Windows Mobile 5.0 targets only, enter the following in the wm50devs.txt file:
Windows Mobile 5.0
To enumerate Pocket PC 2003 and Windows Mobile 5.0 targets, enter the following in the wm50devs.txt file:
Pocket PC
Complete the following steps if you receive a Failed to open VPC Network driver. The driver might not be installed error when you launch an emulator.
Caution: Verify that Visual Studio 2005, the emulator, and the Device Emulator Manager is not running before you complete these steps.
- Delete the %userprofile%\Local Settings\Application Data\Microsoft\CoreCon\1.0 folder for each user on the host PC.
- Rename the %userprofile%\Local Settings\Application Data\Microsoft\Device Emulator folder to %userprofile%\Local Settings\Application Data\Microsoft\Device Emulator_B2.
- Install the Virtual PC Network Driver. Download the installer from the Windows Mobile 5.0 Web site.
- You cannot build a PDA VI into a PDA application if the PDA VI includes a knob with multiple needles inside of a front panel cluster. To fix this problem, create the knob with multiple needles outside of the front panel cluster and then use the Bundle function to bundle them together.
- Numeric controls and dials appear on TPC-2006 devices.
- The OldVal value for numeric controls in an Event structure are now correct.
October 2005
This file contains important last-minute information about the LabVIEW 8.0 PDA Module. Refer to the LabVIEW 8.0 Readme, available by selecting Start»All Programs»National Instruments»LabVIEW 8.0»Readme and opening readme.html, for LabVIEW known issues.
Refer to the National Instruments Web site for the latest information about LabVIEW 8.0.
Installation
Upgrading
Known Issues
Documentation Additions
Refer to the Getting Started with the LabVIEW PDA Module for installation instructions.
Pocket PC You must install the Microsoft eMbedded Visual Tools before you can install the LabVIEW 8.0 PDA Module. If you have installed the LabVIEW 7.1 PDA Module, you already have the Microsoft Mobile Developer Resource Kit, which contains the eMbedded Visual Tools. Refer to the KnowledgeBase at ni.com for information about how to download the eMbedded Visual Tools.
- You must create a LabVIEW project before you can create PDA VIs and build PDA VIs into PDA applications. You can use the PDA Project Wizard to create projects. Refer to the PDA Module book in the LabVIEW Help, available by selecting Help»Search the LabVIEW Help, for more information about creating projects.
- In previous versions of the PDA Module, the Palm OS Screen template included a standard Palm OS titlebar, which is not available in version 8.0 of the Palm OS template. Do not place controls or indicators in approximately the top 60 pixels of the screen, which was the approximate size of the Palm OS titlebar. If you have pre-8.0 PDA VIs that contain the Palm OS titlebar, you must delete the titlebar before you can build a PDA VI into a PDA application in version 8.0. You must unlock it before you can delete it.
- The datalog file format has changed in LabVIEW 8.0. PDA applications you build with LabVIEW 8.0 cannot read the datalog files from LabVIEW 7.1. To update the datalog file, use the Open/Create/Replace Datalog function to convert it on the host computer.
General
- Several front panel and block diagram objects behave differently when the execution target is a PDA device or emulator. Refer to the PDA Module book in the LabVIEW Help for information about different or unsupported front panel or block diagram functionality.
- Dynamic Add/Remove Signals is unsupported.
- Converting an array of doubles to an array of complex does not work. To fix this issue, convert each element in the array in a For Loop instead.
- The Call By Reference Node does not work in serial-only mode.
- You cannot debug a PDA application containing a Compound Arithmetic function. If you try to build a PDA VI into a PDA application with debugging enabled and your PDA VI contains a Compound Arithmetic function, the build fails. All additional builds with debugging enabled also will fail until you restart LabVIEW.
- You cannot initialize variant data with default data in a PDA VI. Placing a control, indicator, or constant that contains default data on the block diagram of PDA VI results in an empty LabVIEW variant.
- If you are zooming a graph or chart in a PDA application and draw with the log scale, it might appear as if nothing has happened. To resolve this problem, choose a larger zoom rectangle.
- If CodeWarrior for Palm OS is already installed on the host computer, the Palm OS PDA Module installer does not install CodeWarrior and does not install the required Palm OS 5 R3 SDK. You must manually install the Palm OS 5 R3 SDK. You can download this SDK from http://www.palmsource.com. Before you install the Palm OS 5 R3 SDK, copy Program Files\Metrowerks\CodeWarrior\Palm OS Support\Incs\Core\System\CharAttr.h to another location. After installation, restore the header file CharAttr.h into Program Files\Metrowerks\CodeWarrior\Palm OS Support\Incs\Core\System directory. This header file is missing from PalmOS 5 R3 SDK but is required by the PDA Module.
- Different PDA devices have different button behaviors. Use the Button Input VIs example, located in labview\examples\PDA\PalmOS\button input or labview\examples\PDA\PocketPC\button input, to determine and test the button behavior for a device. You also can open this example through the NI Example Finder.
- If you use the .Net Refnum, Event Callback Refnum, or Code Interface Nodes (CINs) in a PDA VI, you receive an error if you try to build the PDA VI into a PDA application.
- The PDA Module does not support paths in the Not a Number/Path/Refnum? function.
- Pull-down menus are not visible while a chart or graph is updating. You can place the mouse pointer on the pull-down menu to display it to make a selection.
- If you flatten data that contains an extended precision or complex precision floating-point data type, the flattened data is incompatible with any other version of LabVIEW except the PDA Module.
- The PDA Module does not support the Update Value while Typing property for string objects.
- The PDA Module does not support plotting waveforms with more than 32,000 elements.
- You must use strict C code in Formula Nodes you use in PDA VIs. However, LabVIEW does not check the C syntax in the Formula Node syntax while in edit mode. If you build a PDA VI into a PDA application that contains a Formula Node with non-strict C code, the PDA Module returns a general error.
- The PDA Module does not support significant digits. Use digits of precision instead.
- The Boolean OK, Cancel, and Stop buttons do not support different text strings for TRUE and FALSE states.
- If you right-click a terminal on a Call Library Function Node to create a control or indicator, the control or indicator might have an incorrect data range if the execution target is a PDA device or emulator. When this happens, the data range is from 0 to 0, which renders the increment and decrement arrows nonfunctional. You must manually change the data range of the control or indicator.
- 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 PDA VI into a PDA application.
- If you place a decoration under a tab control, the decoration appears on top of the tab control when you build the PDA VI into a PDA application.
- Labels on controls inside an array do not appear.
- Grouped controls are drawn on top of all tabs.
- PDA VIs do not support the Current VI's Path function, but you do not receive a broken Run button if you attempt to build a PDA VI into a PDA application.
- 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 do not set the Show front panel when called and Close afterwards if originally closed properties for a subVI that includes a front panel that displays on execution, the PDA application crashes when the application tries to call the subVI because the front panel cannot initialize. All other Window Appearance settings are unsupported in PDA VIs.
- PDA VIs assume the control reference is on the active form when you use a Property Node or the PDA-specific VIs on the Application Control palette to change values on front panel controls.
Palm OS
- You cannot build PDA VIs into PDA applications if the VI contains a 16-bit bitmap. The Palm OS template in the 7.1 version of the PDA Module contains a 16-bit bitmap. To resolve this problem, remove the 16-bit bitmap at the top of the VI that represents the application title before you build the PDA VI into a PDA application. The 8.0 version of the Palm OS template does not contain a 16-bit bitmap.
- DatalogMgr.prc does not display files on an expansion card.
- The LabVIEW Conduit is a utility that allows you to use Palm HotSync to copy files that LabVIEW recognizes to and from a Palm OS device. The PDA Module automatically installs the LabVIEW Conduit, but if you use Palm HotSync to copy PDA applications from a computer without the PDA Module installed, you must manually install the LabVIEW Conduit. Run x:\LVPalmOS\LVConduit\LVConduit.msi, where x is the CD-ROM drive, to install the LabVIEW Conduit.
- PDA applications do not run on Tungsten T3 devices in 320 x 480 mode, but do run on Tungsten T3 devices in 320 x 320 mode.
- PDA VIs do not support multi-line text on Palm OS native buttons, such as push buttons and checkboxes.
- The PDA Module does not support transparency in images.
- Palm OS does not support pen attributes, such as width or style.
- Simulator Only Running PDA applications on a Palm OS 5.3 simulator with a 160 x 220 resolution or a 320 x 480 resolution can cause the Palm OS simulator to crash. To correct this problem, run the PDA application on a PDA device.
- Emulator Only Running IrDA applications on a Palm OS emulator with the Palm OS 4.0 debug ROM crashes the emulator. To correct this problem, use the release version of the ROM.
- Emulator Only PDA VIs with filenames longer than 32 characters do not run on the Palm OS emulator.
Pocket PC
- If you copy and paste global variables, you receive a link error when you try to build the PDA VI into a PDA application.
- Key events do not capture key events from the application keys on a Pocket PC device.
- The Set PDA Auto Off VI does not work on Pocket PC 2003 devices or emulators.
- When you launch a PDA application using the Run button, the PDA Memory Usage VI might incorrectly return Used memory (bytes). To correct this problem, stop the PDA application and relaunch it using the Pocket PC device.
- XON/XOFF flow control in serial communication causes a timeout.
You can use the following properties with front panel array controls and indicators:
- Index Values
- Index Visible (read-only)
- Number of Columns (read-only)
- Number of Rows (read-only)
- Position:Left (read-only)
- Position:Top (read-only)
- Visible
Enabling Debugging with the Pocket PC 2003 Emulator
Complete the following steps to configure the Pocket PC 2003 emulator for debugging.
- Launch LabVIEW. Select Tools»Configure Pocket PC Devices.
- Under the POCKET PC 2003 platform, select Pocket PC 2003 Emulator.
- Click the Properties button.
- In the dialog box that appears, the Startup Server should be Emulator Startup Server. Click the Configure button.
- Under the Communication group, select VirtualSwitch for Ethernet and click the OK button.
- In the Device Properties dialog box, click the Test button to launch the emulator.
- When the emulator launches, click the (Windows icon)»Settings button.
- Click the Connections tab and click the Connections icon.
- In the Connections dialog box, click the Advanced tab.
- Click the Network Card button.
- Under the My network card connects to: pull-down menu, select The Internet.
- Close the emulator window. Select Save emulator state to save the settings.
© 2005–2006 National Instruments Corporation. All rights reserved.