CE API. Programming Guide. For: HX3 with Windows CE 5.0. VX3Plus with Windows CE 5.0. VX7 with Windows CE 5.0

Transcription

1 CE API For: HX2 with Windows CE 5.0 HX3 with Windows CE 5.0 MX3Plus with Windows CE 5.0 MX7 with Windows CE 5.0 MX7 Tecton with Windows CE 6.0 or Windows Mobile 6.5 MX8 with Windows CE 5.0 or Windows Mobile 6.1 MX9 with Windows CE 5.0 or Windows Mobile 6.5 VX3Plus with Windows CE 5.0 VX6 with Windows CE 5.0 VX7 with Windows CE 5.0 Thor VM1 with Windows CE 6.0 Thor VM2 with Windows CE 6.0 Programming Guide

2 Disclaimer Honeywell International Inc. ( HII ) reserves the right to make changes in specifications and other information contained in this document without prior notice, and the reader should in all cases consult HII to determine whether any such changes have been made. The information in this publication does not represent a commitment on the part of HII. HII shall not be liable for technical or editorial errors or omissions contained herein; nor for incidental or consequential damages resulting from the furnishing, performance, or use of this material. This document contains proprietary information that is protected by copyright. All rights are reserved. No part of this document may be photocopied, reproduced, or translated into another language without the prior written consent of HII Honeywell International Inc. All rights reserved. Web Address: Microsoft Windows, ActiveSync, MSN, Outlook, Windows Mobile, the Windows logo, and Windows Media are registered trademarks or trademarks of Microsoft Corporation. Intel and Intel XScale are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries. Summit Data Communications, the Laird Technologies Logo, the Summit logo, and "Connected. No Matter What" are trademarks of Laird Technologies, Inc. The Bluetooth word mark and logos are owned by the Bluetooth SIG, Inc. Hand Held is a trademark of Hand Held Products, Inc., a subsidiary of Honeywell International. Intermec is a trademark or registered trtademark of Intermec Technologies Corporation. Symbol is a registered trademark of Symbol Technologies. MOTOROLA, MOTO, MOTOROLA SOLUTIONS and the Stylized M Logo are trademarks or registered trademarks of Motorola Trademark Holdings, LLC and are used under license. Acrobat Reader 2013 with express permission from Adobe Systems Incorporated. Other product names or marks mentioned in this document may be trademarks or registered trademarks of other companies and are the property of their respective owners. Patents For patent information, please refer to Limited Warranty Refer to for your product s warranty information.

3 Table of Contents Chapter 1 - Introduction 1-1 Application Programming Interface (API) 1-1 Identify your Windows CE Equipment 1-1 Windows Mobile Equipped Computers 1-1 CE 6.x Equipped Computers 1-2 CE 5.x Equipped Computers 1-2 Chapter 2 - Battery API Calls 2-1 LXEBatteryIsCharging 2-2 LXEBatteryIsDischarging 2-3 LXEBatteryChargeBackup 2-4 LXEBatteryDischargeBackup 2-5 LXEBatteryIsACPower 2-6 LXEBatteryReadVoltage 2-7 LXEBatteryReadPercent 2-8 LXEBatteryReadmaHr 2-9 Chapter 3 - PCMCIA API Calls 3-1 LXEPcmciaHasCard 3-3 LXEPcmciaDisableSlot 3-4 LXEPcmciaEnableSlot 3-5 LXEPcmciaWriteProtect 3-6 LXEHasInternalDrive 3-7 Chapter 4 - Power Management API Calls 4-1 LXEPowerMgrEnable 4-2 LXEPowerMgrToNormal 4-3 LXEPowerMgrAlwaysOn 4-4 LXEPowerMgrDisplayNormal 4-5 LXEPowerMgrDisplayOn 4-6 LXEPowerMgrBacklightNormal 4-7 LXEPowerMgrBacklightOn 4-8 LXEPowerMgrBacklightTimeout 4-9 LXEPowerMgrGetBacklightTimeout 4-10 LXEPowerMgrDisplayTimeout 4-11 LXEPowerMgrGetDisplayTimeout 4-12 LXEPowerMgrSuspendTimeout 4-13 LXEPowerMgrGetSuspendTimeout 4-14 LXEPowerMgrPrimaryEvents 4-15 LXEForcePowerKeyPrimaryEvent 4-16 i

4 LXEForceKeyPrimaryEvent 4-17 LXEForceTouchPrimaryEvent 4-18 LXEForceScanPrimaryEvent 4-19 LXEForceUserPrimaryEvent 4-20 LXEForcePCMCIAPrimaryEvent 4-21 LXEForceCOM1PrimaryEvent 4-22 LXEForceCOM2PrimaryEvent 4-23 LXEForceCOM3PrimaryEvent 4-24 LXEForceUSBPrimaryEvent 4-25 LXEForceDockedPrimaryEvent 4-26 LXEForceSystemPrimaryEvent 4-27 LXESetCOMSystemActivity 4-29 LXEIsCOMSystemActivity 4-31 Chapter 5 - Scanner and DC Wedge API Calls 5-1 LXEHasIntScanner 5-2 LXEHasIntRFID 5-3 LXEScannerEnable 5-4 LXEScannerDisable 5-5 LXEScannerInputEnable 5-6 LXEScannerInputDisable 5-7 LXEScannerReset 5-8 LXEScannerStart 5-9 LXEScannerStop 5-10 LXEScannerForceScan 5-11 LXEScannerGetStatus 5-12 LXEScannerGetData 5-13 LXEScannerPutData 5-14 LXEScannerMsgBufSet 5-15 LXEScannerMsgBufGet 5-16 LXEScannerGetDataIndex 5-17 LXEScannerKeysOff 5-19 LXEScannerKeysOn 5-20 LXEScannerKeyStatus 5-21 LXEScannerPowerOff 5-22 LXEScannerPowerOn 5-23 LXEScannerForcePower 5-24 LXEScannerAttachPort 5-26 LXEScannerSetKey 5-28 LXEScannerSetSerial 5-30 ii

5 LXEScannerSetPower 5-31 LXEScannerSetWindow 5-32 LXEScannerCtrlCodeOff 5-34 LXEScannerCtrlCodeOn 5-35 LXEScannerSymStripLead 5-36 LXEScannerStripLead 5-37 LXEScannerSymStripTrail 5-39 LXEScannerStripTrail 5-40 LXEScannerSymPrefix 5-42 LXEScannerPrefix 5-43 LXEScannerSymSuffix 5-45 LXEScannerSuffix 5-46 LXEScannerSymEnable 5-48 LXEScannerOption 5-49 LXEScannerHasOption 5-51 LXEScannerSymIsEnabled 5-52 LXEScannerIsOptionEnabled 5-53 LXEScannerGetParam 5-54 LXEScannerSetParam 5-55 LXEScannerSymGetConfig 5-56 LXEScannerSymSetConfig 5-58 LXEScannerSymRemove 5-60 LXEScannerSSModeGet 5-61 LXEScannerSSModeSet 5-62 LXEScannerSSReset 5-63 Chapter 6 - Version Control API Calls 6-1 LXEVersionOS 6-2 LXEVersionOAL 6-3 LXEVersionBoot 6-4 LXEVersionFPGA 6-5 LXEVersionAPI 6-6 LXEVersionSerial 6-7 LXEInfoCopyright 6-8 LXEInfoGetCodecInfo 6-9 LXEInfoGetCPUInfo 6-10 LXEInfoROMID 6-12 LXEInfoRAMID 6-13 LXEInfoGetROMInfo 6-14 LXEInfoGetRAMInfo 6-16 iii

6 LXEInfoGetUUID 6-18 Chapter 7 - Display API Calls 7-1 LXEHasColorLCD 7-2 LXEShowTaskbar 7-3 LXEGetContrast 7-4 LXESetContrast 7-5 LXEGetBrightness 7-6 LXESetBrightness 7-7 LXESetBacklightOn 7-8 LXEGetBacklightOn 7-9 LXEIsBacklightOn 7-10 LXESetDisplayOn 7-11 LXEGetDisplayOn 7-12 LXEIsDisplayOn 7-13 LXESetVibration 7-14 LXESetTouch 7-15 LXESetHX3AlphaMode 7-16 LXESetHX3AlphaLED 7-17 Chapter 8 - Audio API Calls 8-1 LXEAudioGetGain 8-2 LXEAudioSetGain 8-3 LXEAudioLoadGain 8-4 LXEAudioSaveGain 8-5 LXEGetBoost 8-6 LXEAudioSetBoost 8-8 LXEAudioLoadBoost 8-10 LXEAudioSaveBoost 8-11 LXEAudioGetVolume 8-12 LXEAudioSetVolume 8-13 LXEAudioLoadVolume 8-14 LXEAudioSaveVolume 8-15 LXEAudioGetMasterVolume 8-16 LXEAudioSetMasterVolume 8-17 LXEAudioLoadMasterVolume 8-18 LXEAudioSaveMasterVolume 8-19 LXEAudioGetSpeakerVolume 8-20 LXEAudioSetSpeakerSpeakerVolume 8-21 LXEAudioLoadSpeakerVolume 8-22 LXEAudioSaveSpeakerVolume 8-23 iv

7 LXEAudioGetHeadsetVolume 8-24 LXEAudioSetHeadsetVolume 8-25 LXEAudioLoadHeadsetVolume 8-26 LXEAudioSaveHeadsetVolume 8-27 LXEAudioGetRecordIn 8-28 LXEAudioSetRecordIn 8-30 LXEAudioLoadRecordIn 8-32 LXEAudioSaveRecordIn 8-33 LXEAudioGetSidetone 8-34 LXEAudioSetSidetone 8-35 LXEAudioLoadSidetone 8-36 LXEAudioSaveSidetone 8-37 LXEAudioGetHeadSet 8-38 LXEAudioSetHeadSet 8-39 LXEAudioLoadHeadSet 8-40 LXEAudioSaveHeadSet 8-41 Chapter 9 - Keyboard API Calls 9-1 LXEKeyboardSetLayout 9-2 LXEKeyboardGetLayout 9-3 LXEKbdTypeGet 9-4 LXEKeyboardSetModMessage 9-6 LXEKeyboardGetModMessage 9-7 Chapter 10 - Miscellaneous API Calls 10-1 LXEBoot 10-2 LXEBootCold 10-4 LXEBootClear 10-5 LXEIsTurboOn 10-6 LXETurboOn 10-7 LXETurboOff 10-8 LXEWarmBoot 10-9 LXERestart LXEShutDown LXELoadUserReg LXESaveUserReg LXELoadFactoryDefaults LXEGetSuspendType Chapter 11 - Peripheral Control API Calls 11-1 LXEPowerCOM LXEPowerCOM1RI 11-3 v

8 LXEPreserveStateCOM LXEPowerCOM LXEPowerCOM2RI 11-6 LXEPowerCOM LXEPowerCOM3RI 11-8 LXEIsPowerCOM LXEPreserveStateCOM LXEPowerCOM LXESuspendPowerCOM LXEResetCOM LXEPowerCOM4RI LXEPowerCOM LXEPowerCOM5RI LXEResetCOM LXEPowerGPS LXEIsPowerGPS LXEResetGPS LXEPowerImager LXEResetImager LXEPowerCFslot LXEPowerSDslot LXEPowerSDslot LXEPowerVib LXEPowerUSBHost LXEPowerHeater LXEResetRaptor LXEPowerFlashlight Chapter 12 - Bluetooth API Calls 12-1 LXEBTTurnBTOn 12-2 LXEBTTurnBTOff 12-3 LXEBTMakeDiscoverable 12-4 LXEBTMakeNotDiscoverable 12-5 LXEBTStartDiscovery 12-6 LXEBTGetDiscoveredDevices 12-7 LXEBTGetPairedDevices 12-9 LXEBTGetActiveDevices LXEBTConnectDevice LXEBTDisconnectDevice LXEBTAllowScannerData vi

9 LXEBTSetLinkSupervisionTimeout LXEBTSetReconnectTimer LXEBTDeleteDevice LXEBTGetLinkSupervisionTimeout LXEBTGetReconnectTimer LXEBTGetBTAddress LXEBTSetBluetoothMode LXEBTGetBluetoothMode LXEBTConnectDeviceOnPort LXEBTGetCurrentInquiryResult LXEBTCancelDiscovery LXEBTGetBluetoothState LXEBTDeleteDiscoveredDevice LXEBTSetAutoReconnectOnBoot LXEBTGetAutoReconnectOnBoot LXEBTSetBTFriendlyName LXEBTGetRemoteDeviceInfo LXEBTSetClearTableOnBoot LXEBTGetClearTableOnBoot LXEBTSetAutoReconnectFlag LXEBTGetAutoReconnectFlag LXEBTListOPPCapableDevices LXEBTRegisterOPPCallback LXEBTUnRegisterOPPCallback LXEBTSendFile LXEBTSetOPPPaths LXEBTGetOPPPaths LXEBTSetWriteCapable LXEBTGetWriteCapable LXEBTSetEnableOPPNotifications LXEBTGetEnableOPPNotifications LXEBTSetDisableLXEZPairingOPP LXEBTGetDisableLXEZPairingOPP LXEBTOPPDiscover LXEBTOPPIsMacAddrOPP LXEBTSetFileSizeMax LXEBTGetFileSizeMax Chapter 13 - WWAN API Calls 13-1 LXEWWANDoATCommand 13-2 vii

10 LXEWWANRadioDisable 13-3 LXEWWANRadioEnable 13-4 LXEWWANGetFirmwareVersion 13-5 LXEWWANGetSoftwareVersion 13-6 LXEWWANGetRadioType 13-7 LXEWWANGetSignalStrength 13-8 LXEWWANGetSerialNumber 13-9 LXEWWANGetSIMRequiresPIN LXEWWANSetSIMSecurity LXEWWANSetSIMPIN LXEWWANGetSIMStatus LXEWWANSetPhoneNumber LXEWWANSetUsername LXEWWANSetPassword LXEWWANSetAPN LXEWWANConnect LXEWWANDisconnect LXEWWANGetConnectionStatus LXEWWANGetNetwork LXEWWANAllowRoaming LXEWWANAutoconnect LXEWWANAutoreconnect LXEWWANUseDHCP LXEWWANUseDynamicNameServers LXEWWANSetStaticIP LXEWWANSetPrimaryDNS LXEWWANSetSecondaryDNS Chapter 14 - Win32 API Calls 14-1 GetLastError 14-1 NLedDriverSetDevice 14-2 Honeywell definitions for LedNum 14-4 HX2, HX3, MX3Plus, MX7, MX9 and VX3Plus 14-4 MX7 Tecton 14-4 Thor VM Thor VM Chapter 15 - Reference Material 15-1 Primary Events for Power Management APIs 15-1 MX MX7 Tecton 15-2 viii

11 Thor VM1 and Thor VM CE 5.0 Devices except MX Power Management States 15-4 Symbology Descriptors 15-5 Symbol and generic Symbologies 15-5 Intermec Symbologies 15-5 Hand Held Products Symbologies 15-5 Honeywell N43XX Symbologies 15-6 Symbology Values 15-7 Hexadecimal and Hat Encoded Characters 15-9 Using the Bluetooth OPP API Service Callback Function Messages Sent to the Registered Callback Callback Function Return Values Callback Function Usage Sending a File Receiving a File OPP Data Types Return Codes Error Codes Board Address Structure Callback Returns Enumerated Type Callback Messages Enumerated Type ap_data Pointer Format USER CALLBACK Type Chapter 16 - Technical Assistance 16-1 ix

12 x

13 Chapter 1 - Introduction This document details only the Honeywell-specific API calls. It also shows which calls from the standard Honeywell API are and are not supported on each of the Honeywell computers. It is intended as an appendix to the standard Microsoft Windows Pocket PC or Windows CE API documentation. Application Programming Interface (API) Also known as Application Programmer s Interface, an API is a specification of the methods an application programmer can use to access services provided by a software module. APIs are implemented by writing function calls in the program, which provide the linkage to the required subroutine for execution. Thus, an API implies that some program module is available in the computer to perform the operation or that it must be linked into the existing program to perform the tasks. The CE Application Programmer s Interface (API) is designed to enable application programmers to access the functionality of Microsoft Windows CE equipped Honeywell computer hardware without requiring them to understand the details of the hardware design. This programming guide describes, in a general way, the functions that comprise the API. This guide is for the application programmer working with Honeywell computers with a Microsoft Windows CE or Windows Mobile operating system only. Identify your Windows CE Equipment This document details the Honeywell specific API calls for Honeywell s family of computers running various versions of the Microsoft Windows CE operating system (including devices with a Windows Mobile operating system). The supported computers and operating systems are displayed below. Note: Although some products appear physically similar, there are significant differences in the API specifications for each computer type and available operating system. Please use the chart below for help in identifying your equipment. For more information, please refer to the reference guide for the appropriate Honeywell computer. This manual DOES NOT cover devices with operating systems other than Microsoft Windows CE and Windows Mobile. Examples of equipment not covered include any legacy DOS equipment, the Thor VM1 with a Windows Embedded Standard operating system and any device such as the Kärv or Förj with a Windows XP or Windows 7 operating system. Contact Technical Assistance for information on archived guides for obsolete products. Windows Mobile Equipped Computers Computers in this section are quipped with a Microsoft Windows Mobile operating system. These computers may also available be with Microsoft Windows CE 5.x or Microsoft Windows CE 6.x operating systems. API support may vary by operating system type. MX7 Tecton with Windows Mobile MX8 with Windows Mobile MX9 with Windows Mobile 1-1

14 CE 6.x Equipped Computers Computers in this section are quipped with a Microsoft Windows CE 6.0 operating system. These computers may also be available with either Microsoft Windows Mobile or Windows Embedded Standard (not covered in this document) operating systems. API support may vary by operating system. MX7 Tecton MX7 Tecton CS Designed for use in cold environments Thor VM1 Thor VM2 CE 5.x Equipped Computers Computers in this section are quipped with a Microsoft Windows CE 5.0 operating system. These computers may also be available with a Microsoft Windows Mobile operating systems. API support may vary by operating system. HX2 HX3 MX9 MX9CS MX9HL Designed for use in cold environments For use in hazardous locations: Class 1, Division 2, Groups A, B, C and D The user is strongly cautioned to review the MX9 User Guide for warnings and cautions on using the MX9HL in a hazardous environment. MX8 MX7 MX7CS Designed for use in cold environments MX3Plus VX3Plus VX6 VX7 1-2

15 Chapter 2 - Battery API Calls API support is listed for each Honeywell computer with a Microsoft Windows CE operating system indicated by the following designations: Yes The Honeywell computer supports this API. No The Honeywell computer does not support this API. On these computers, the API returns a not supported function result to the calling application. See GetLastError() for more information. N/A The Honeywell computer does not support this API. The API was created after the release of the computer and the API is not defined for this model of Honeywell computer. Calling this API on a computer marked as N/A may give unpredictable results including the possibility the Honeywell computer may lock up and require rebooting. 2-1

16 LXEBatteryIsCharging int LXEBatteryIsCharging(void); This function returns: TRUE if the backup battery is charging, or FALSE if the backup battery is not charging. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 No - - MX9 Windows Mobile 6.5 No - - MX7 Tecton and Tecton CS CE 6.0 No - - Thor VM1 CE 6.0 No - - Thor VM2 CE 6.0 No - - HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 No - - VX6 CE 5.0 No - - VX7 CE 5.0 No

17 LXEBatteryIsDischarging int LXEBatteryIsDischarging(void); This function returns: TRUE if the backup battery is discharging, or FALSE if the backup battery is not discharging. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 No - - MX9 Windows Mobile 6.5 No - - MX7 Tecton and Tecton CS CE 6.0 No - - Thor VM1 CE 6.0 No - - Thor VM2 CE 6.0 No - - HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 No - - VX6 CE 5.0 No - - VX7 CE 5.0 No

18 LXEBatteryChargeBackup int LXEBatteryChargeBackup(void); This function generates a system event which causes the battery driver to start charging the backup battery. In normal operation, this API would not be used as the power management driver monitors the battery voltage and initiates a charge as necessary. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 No - - MX9 Windows Mobile 6.5 No - - MX7 Tecton and Tecton CS CE 6.0 No - - Thor VM1 CE 6.0 No - - Thor VM2 CE 6.0 No - - HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 No - - VX6 CE 5.0 No - - VX7 CE 5.0 No

19 LXEBatteryDischargeBackup int LXEBatteryDischargeBackup(void); This function generates a system event which causes the battery driver to start discharging the backup battery. This is used to condition the NiCad battery. When the battery discharges to a sufficiently low value, the hardware detects this and automatically begins the recharge cycle. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 No - - MX9 Windows Mobile 6.5 No - - MX7 Tecton and Tecton CS CE 6.0 No - - Thor VM1 CE 6.0 No - - Thor VM2 CE 6.0 No - - HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 No - - VX6 CE 5.0 No - - VX7 CE 5.0 No

20 LXEBatteryIsACPower int LXEBatteryIsACPower(int *status); This function sets the status variable to: 1 if the computer has external power supplied, or 0 if the computer is powered only by battery. This reflects the power state as of the last status loop of the battery driver which occurs every 500 ms. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 2-6

21 LXEBatteryReadVoltage int LXEBatteryReadVoltage(int *vmain, int *vback); This function returns the current voltage of both the main battery vmain and the backup battery vback, in millivolts. This is the value read by the last poll of the battery driver, which occurs every 10 seconds. For the MX7, HX2 and HX3 the value returned is the average for the last 6 readings from the poll of the battery driver. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 2-7

22 LXEBatteryReadPercent int LXEBatteryReadPercent(int *pmain, int *pback); This function returns the current percentage of full charge of both the main battery pmain and the backup battery pback, in percent notation. This is the value read by the last poll of the battery driver, which occurs every 10 seconds. In addition, the battery driver assumes a linear charge lifetime, which is only approximately accurate. This value reflects the distance between fully charged (100%) and discharged to the critically low voltage trip point (0%). For the MX7, HX2 and HX3 the value returned is the average for the last 6 readings from the poll of the battery driver. For the MX7, HX2 and HX3 this API returns the error message ERROR_NOT_READY if the battery driver thread is not currently running. This can occur during cold and warm booting of the device as well as when recovering from suspend mode. If this error message is returned by this API the user must keep calling this API until the error message is no longer being returned, indicating that the correct return value can now be obtained. Note: The 0% end of the percentage range DOES NOT correspond to zero battery power. Instead, it corresponds to the critically low point below which the computer does not have enough power to operate. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 2-8

23 LXEBatteryReadmaHr int LXEBatteryReadmAhr(int *pmain); This function returns the current charge in ma/hours of the main battery pmain. This is the value read by the last poll of the battery driver which occurs every 10 seconds. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 No - - MX9 Windows Mobile 6.5 No - - MX7 Tecton and Tecton CS CE 6.0 No - - Thor VM1 CE 6.0 No - - Thor VM2 CE 6.0 No - - HX2 CE 5.0 No - - HX3 CE 5.0 No - - MX3Plus CE 5.0 No - - MX7 & MX7CS CE 5.0 No - - MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 No - - VX6 CE 5.0 No - - VX7 CE 5.0 No

24 2-10

25 Chapter 3 - PCMCIA API Calls API support is listed for each Honeywell computer with a Microsoft Windows CE operating system indicated by the following designations: Yes The Honeywell computer supports this API. No The Honeywell computer does not support this API. On these computers, the API returns a not supported function result to the calling application. See GetLastError() for more information. N/A The Honeywell computer does not support this API. The API was created after the release of the computer and the API is not defined for this model of Honeywell computer. Calling this API on a computer marked as N/A may give unpredictable results including the possibility the Honeywell computer may lock up and require rebooting. For the PCMCIA APIs, the parameter slot can have the values shown in the tables below (where X indicates the slot is present on the device): When a device does not exist on a given computer platform, GetLastError() returns ERROR_DEV_NOT_EXIST (55). If the function is not supported on the given slot, GetLastError() returns ERROR_NOT SUPPORTED (50). Windows Mobile Devices Constant Value SLOT_PCMCIA 0 SLOT_PCMCIA2 1 MX7 Tecton MX8 SLOT_COMPACTFLASH 1 X X SLOT_INTATA 2 SLOT_SMSC (on-board Ethernet controller) MX9 3 X SLOT_SDMMC 4 X X X SLOT_USB_RADIO 5 SLOT_SDMMC2 6 X X SLOT_FLASH 7 X X SLOT_FLASH_RAW 8 X X 3-1

26 CE 6.0 Devices Constant Value MX7 Tecton SLOT_PCMCIA 0 SLOT_PCMCIA2 1 SLOT_COMPACTFLASH 1 SLOT_INTATA 2 SLOT_SMSC (on-board Ethernet controller) 3 Thor VM1 Thor VM2 SLOT_SDMMC 4 X X SLOT_USB_RADIO 5 SLOT_SDMMC2 6 X X SLOT_FLASH 7 X SLOT_FLASH_RAW 8 X CE 5.0 Devices Constant Value MX3Plus VX3XPlus VX6 VX7 SLOT_PCMCIA 0 X X SLOT_PCMCIA2 1 X MX7 MX7CS HX2 HX3 MX8 MX9 MX9HL MX9CS SLOT_COMPACTFLASH 1 X X * X X X SLOT_INTATA 2 X X SLOT_SMSC (on-board Ethernet controller) 3 X X X SLOT_SDMMC 4 X X X X X SLOT_USB_RADIO 5 X X X ** SLOT_SDMMC2 6 X SLOT_FLASH 7 X SLOT_FLASH_RAW 8 X Note: Note: * SLOT_COMPACTFLASH is valid only for MX7s with a Summit radio. ** SLOT_USB_RADIO is only valid for MX7's without a Summit radio. 3-2

27 LXEPcmciaHasCard int LXEPcmciaHasCard(int slot, int *status); Please refer to this table for a list of valid options for the slot parameter. This function returns status of the specified slot: 1 If a card is inserted in the slot, or 0 If a card is not inserted in the slot. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 3-3

28 LXEPcmciaDisableSlot int LXEPcmciaDisableSlot(int slot); Please refer to this table for a list of valid options for the slot parameter. This function disables the specified slot. It does this by setting an internal flag which causes any card insertions on the slot to be ignored. It then removes power from the slot. Normally, the card would be detected by the PCMCIA driver and power restored to the slot. However, the internal flag prevents this happening, and the card is disabled. The slot can still be powered and accessed by applications or diagnostic software, but it is inhibited from detection by the PCMCIA driver. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 No - - HX3 CE 5.0 No - - MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 No - - MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 3-4

29 LXEPcmciaEnableSlot int LXEPcmciaEnableSlot(int slot); Please refer to this table for a list of valid options for the slot parameter. This function enables the specified slot, generally after being deactivated by the disable function, listed previously. It does this by clearing an internal flag which causes any card insertions on the slot to be ignored. The card is then detected by the PCMCIA driver and power is restored to the slot, restoring the card to normal operation. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 No - - HX3 CE 5.0 No - - MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 No - - MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 3-5

30 LXEPcmciaWriteProtect int LXEPcmciaWriteProtect(int slot, int val); This function causes the card in the specified slot to be write protected. This sets an internal flag which inhibits the PCMCIA driver from allowing writes to the card. It is undefined what happens when a non-sram card is write protected; it is safe to assume the card is no longer going to function properly. Please refer to this table for a list of valid options for the slot parameter. The argument val is: 1 to write protect the card, and 0 to allow writes to the card. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 No - - MX9 Windows Mobile 6.5 No - - MX7 Tecton and Tecton CS CE 6.0 No - - Thor VM1 CE 6.0 No - - Thor VM2 CE 6.0 No - - HX2 CE 5.0 No - - HX3 CE 5.0 No - - MX3Plus CE 5.0 No - - MX7 & MX7CS CE 5.0 No - - MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 No - - VX3Plus CE 5.0 No - - VX6 CE 5.0 No - - VX7 CE 5.0 No

31 LXEHasInternalDrive int LXEHasInternalDrive(void); This function returns the presence of the internal storage card: 1 card is inserted in the slot 0 no card in the slot. MX8 Windows Mobile 6.1 No - - MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 No - - MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 3-7

32 3-8

33 Chapter 4 - Power Management API Calls API support is listed for each Honeywell computer with a Microsoft Windows CE operating system indicated by the following designations: Yes The Honeywell computer supports this API. No The Honeywell computer does not support this API. On these computers, the API returns a not supported function result to the calling application. See GetLastError() for more information. N/A The Honeywell computer does not support this API. The API was created after the release of the computer and the API is not defined for this model of Honeywell computer. Calling this API on a computer marked as N/A may give unpredictable results including the possibility the Honeywell computer may lock up and require rebooting. This section assumes the user is familiar with the power management features and power management states (or power modes) of the particular Honeywell computer. For more details on power management and primary events, please refer to the reference guide for the Honeywell computer. Note: On some devices which do not support power management, the API may return success. However, the API has no effect on the device. This is harmless to the calling application. 4-1

34 LXEPowerMgrEnable int LXEPowerMgrEnable(void); This function generates a system event which causes the power management driver to return to normal operation. The most common usage is following an LXEPowerMgrAlwaysOn() command. This call has the same function as LXEPowerMgrToNormal(). On CE 4.x and later devices, the thread generating user events is terminated, see LXEPowerMgrAlwaysOn(). MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-2

35 LXEPowerMgrToNormal int LXEPowerMgrToNormal(void); This function generates a system event which causes the power management driver to return to normal operation. The most common usage is following an LXEPowerMgrAlwaysOn() command. This call has the same function as LXEPowerMgrEnable(). On CE 4.x and later devices, the thread generating user events is terminated, see LXEPowerMgrAlwaysOn(). MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-3

36 LXEPowerMgrAlwaysOn int LXEPowerMgrAlwaysOn(void); This function generates a system event which causes the power management driver to disable operation, leaving all power always on. This disables all display and backlight controls, as well as the OS suspend timer. For CE 4.x and later equipped computers, this function spins off a thread which generates user events once per second to keep the power manager in the D0 (On) state. Note: This thread is in the application space, so two applications have two separate threads. Both threads must be terminated to restore power management to normal. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-4

37 LXEPowerMgrDisplayNormal int LXEPowerMgrDisplayNormal(void); This function generates a system event which causes the power management driver to start handling display on/off timing and events normally. The most common usage is following an LXEPowerMgrDisplayOn() command. On CE 4.x and later devices, the thread generating user events is terminated, see LXEPowerMgrDisplayOn(). MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-5

38 LXEPowerMgrDisplayOn int LXEPowerMgrDisplayOn(void); This function generates a system event which causes the power management driver to disable monitoring display on/off timing and events, leaving display power always on. This has no effect on other power management subsystems. For CE 4.x and later equipped computers, this function spins off a thread which generates user events once per second to keep the power manager in the D1 (User Idle) state. Note: This thread is in the application space, so two applications have two separate threads. Both threads must be terminated to restore power management to normal. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-6

39 LXEPowerMgrBacklightNormal int LXEPowerMgrBacklightNormal(void); This function generates a system event which causes the power management driver to start handling backlight on/off timing and events normally. The most common usage is following an LXEPowerMgrBacklightOn() command. On CE 4.x and later devices, the thread generating user events is terminated, see LXEPowerMgrBacklightOn(). MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-7

40 LXEPowerMgrBacklightOn int LXEPowerMgrBacklightOn(void); This function generates a system event which causes the power management driver to disable monitoring backlight on/off timing and events, leaving backlight power always on. This has no effect on other power management subsystems. For CE 4.x and later equipped computers, this function spins off a thread which generates user events once per second to keep the power manager in the D0 (On) state. Note: This thread is in the application space, so two applications have two separate threads. Both threads must be terminated to restore power management to normal. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-8

41 LXEPowerMgrBacklightTimeout int LXEPowerMgrBacklightTimeout(int valbatt, int valac); This function changes the values of the backlight power management timeouts (given in seconds) and saves them to the registry. The function then generates the event necessary to cause the driver to reload its registry information, so that the new value takes effect immediately. The argument valbatt is the timeout when running under battery power, and the argument valac is the timeout when running under external AC power. For CE 4.x and later equipped computers, this function sets timeouts for power management state D1 (User Idle), which is entered when there are no user events in the given timeout period. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-9

42 LXEPowerMgrGetBacklightTimeout int LXEPowerMgrGetBacklightTimeout(int *valbatt, int *valac); This function returns the values of the backlight power management timeouts (given in seconds). The argument valbatt is the timeout when running under battery power, and the argument valac is the timeout when running under external AC power. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-10

43 LXEPowerMgrDisplayTimeout int LXEPowerMgrDisplayTimeout(int valbatt, int valac); This function changes the values of the display power management timeouts (given in seconds) and saves them to the registry. The function then generates the event necessary to cause the driver to reload its registry information, so that the new value takes effect immediately. The argument valbatt is the timeout when running under battery power, and the argument valac is the timeout when running under external AC power. For CE 4.x and later equipped computers, this function sets timeouts for power management state D2 (System Idle), which is entered when there are no system events in the given timeout period. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-11

44 LXEPowerMgrGetDisplayTimeout int LXEPowerMgrGetDisplayTimeout(int *valbatt, int *valac); This function returns the values of the display power management timeouts (given in seconds). The argument valbatt is the timeout when running under battery power, and the argument valac is the timeout when running under external AC power. For CE 4.x and later equipped computers, this function returns timeouts for power management state D2 (System Idle), which is entered when there are no system events in the given timeout period. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-12

45 LXEPowerMgrSuspendTimeout int LXEPowerMgrSuspendTimeout(int valbatt, int valac); This function changes the values of the suspend power management timeouts (given in seconds) and saves them to the registry. The function then generates the event necessary to cause the driver to reload its registry information, so that the new value takes effect immediately. The argument valbatt is the timeout when running under battery power, and the argument valac is the timeout when running under external AC power. For CE 4.x and later equipped computers, this function sets timeouts for power management state D3 (Suspend), which is entered when there are no system events in the given timeout period. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-13

46 LXEPowerMgrGetSuspendTimeout int LXEPowerMgrGetSuspendTimeout(int *valbatt, int *valac); This function returns the values of the suspend power management timeouts (given in seconds). The argument valbatt is the timeout when running under battery power, and the argument valac is the timeout when running under external AC power. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-14

47 LXEPowerMgrPrimaryEvents int LXEPowerMgrPrimaryEvents(unsigned long val); This function changes the bitmask of primary events that affect waking from suspend, and saves it to the registry. The function then generates the event necessary to cause the driver to reload its registry information, so that the new value takes effect immediately. Valid values within the bitmask are listed in the Primary Events tables. MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-15

48 LXEForcePowerKeyPrimaryEvent int LXEForcePowerKeyPrimaryEvent(void); This function generates a user event which simulates a power keypress to the power management driver. This is primarily of use in diagnostic software, or to force a wakeup of the power management system. Note: This event has no effect on the computer going into suspend, only the transition to power management state D1 (user idle). MX8 Windows Mobile 6.1 Yes lxeapi.h lxeapi.lib MX7 Tecton Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX9 Windows Mobile 6.5 Yes lxeapi.h lxeapi.lib MX7 Tecton and Tecton CS CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM1 CE 6.0 Yes lxeapi.h lxeapi.lib Thor VM2 CE 6.0 Yes lxeapi.h lxeapi.lib HX2 CE 5.0 Yes lxeapi.h lxeapi.lib HX3 CE 5.0 Yes lxeapi.h lxeapi.lib MX3Plus CE 5.0 Yes lxeapi.h lxeapi.lib MX7 & MX7CS CE 5.0 Yes lxeapi.h lxeapi.lib MX8 CE 5.0 Yes lxeapi.h lxeapi.lib MX9, MX9CS & MX9HL CE 5.0 Yes lxeapi.h lxeapi.lib VX3Plus CE 5.0 No - - VX6 CE 5.0 Yes lxeapi.h lxeapi.lib VX7 CE 5.0 Yes lxeapi.h lxeapi.lib 4-16