QTERM -G56/G58 INDUSTRIAL HMI TERMINAL WINDOWS CE …beijerinc.com/pdf/qsi_qterm-g56-g58_wince_manual.pdf · QTERM®-G56/G58 INDUSTRIAL HMI TERMINAL WINDOWS CE MANUAL BEIJER ELECTRONICS

QTERM®-G56/G58INDUSTRIAL HMI TERMINAL

WINDOWS CE MANUAL

BEIJER ELECTRONICS2212 South West Temple #50

Salt Lake City, Utah 84115-2648USA

Phone 801-466-8770Fax 801-466-8792

Email [email protected] http://www.beijerelectronicsinc.comM01-033-00 Rev 03

Copyright © 2011 Beijer Electronics. Printed in the USA. All rights reserved. No part of this publication may be reproduced, in any form or by any means with-out prior written permission from Beijer Electronics.

QTERM is a registered trademark of Beijer Electronics.Microsoft, Windows, Windows NT, Windows 2000, Windows XP, Vista, ActiveSync and their respective logos are registered trademarks of Microsoft Corpora-tion in the United States and other countries.All other brand and product names used in this manual are trademarks or registered trademarks of their respective companies.

Manual updated 27 March 2011.

FCC Compliance Information

This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Operation of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

Any modification to the QTERM-G56/G58 (including changes to the recommended antenna configuration) that are not expressly approved by Beijer Electronics could void the user’s authority to operate the QTERM-G56/G58.

Additionally, the QTERM-G56/G58 may contain the following FCC module-certified components depending on product configuration: AU792U07A31817, AU792U09D24824, AU792U04A22740, or Q72WLC300GRS.

Notes

QTERM-G56/G58 Industrial HMI Terminal i

CONTENTS

CHAPTER 1. INTRODUCTION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .1

CHAPTER 2. PRODUCT DESCRIPTION AND ARCHITECTURE . . . . . . . . . . . . . . . . . . . . . . . . .32.1 QTERM-G56 Description and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .3

2.1.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32.1.2 Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4

2.1.2.1 Connector Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .42.1.2.1.1 Power and USB Device Interfaces . . . . . . . . . . . . . . . . . . . . . . .42.1.2.1.2 Serial Multiprotocol Port Interface. . . . . . . . . . . . . . . . . . . . . . .52.1.2.1.3 Additional Serial Interface (without Ethernet option) . . . . . . . .52.1.2.1.4 Network Interface (with Ethernet option) . . . . . . . . . . . . . . . . .52.1.2.1.5 Accessory Cable Wire Color Code and Demo Cable Pinout . . .5

2.1.2.2 Integral Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .62.1.2.2.1 Power and USB Device Interfaces with Integral Cable . . . . . . .72.1.2.2.2 Serial Interface with Integral Cable . . . . . . . . . . . . . . . . . . . . . .72.1.2.2.3 Additional Serial Interface with Integral Cable (without Ethernet option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .72.1.2.2.4 Network Interface with Integral Cable (with Ethernet option) .72.1.2.2.5 E-stop Option with Integral Cable . . . . . . . . . . . . . . . . . . . . . . .82.1.2.2.6 Power and USB Device Interfaces with E-stop Option and Integral Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.1.2.2.7 Serial Interface with E-Stop Option and Integral Cable (without Ethernet option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.1.2.2.8 Additional Serial Interface with E-Stop Option and Integral Cable (without Ethernet option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82.1.2.2.9 Network Interface with E-Stop Option and Integral Cable (with Ethernet option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.1.2.2.10 Serial Interface with E-stop Option and Integral Cable (with Ethernet option) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .92.1.2.2.11 E-stop Switch Interface with Integral Cable . . . . . . . . . . . . . .92.1.2.2.12 Integral Cable Wire Color Code. . . . . . . . . . . . . . . . . . . . . . . .9

2.2 QTERM-G58 Description and Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.2.1 Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .102.2.2 Supported Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .11

2.2.2.1 Connector Interface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .112.2.2.1.1 Power and USB Device Interfaces . . . . . . . . . . . . . . . . . . . . . .122.2.2.1.2 Serial Multiprotocol Port Interface. . . . . . . . . . . . . . . . . . . . . .122.2.2.1.3 Accessory Cable Wire Color Code and Demo Cable Pinout . .12

2.3 Hardware . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.3.0.1 Processor. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.3.0.2 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .132.3.0.3 Touch Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142.3.0.4 Keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142.3.0.5 Speaker . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .142.3.0.6 Real-Time Clock . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152.3.0.7 System Memory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .15

Contents

ii QTERM-G56/G58 Industrial HMI Terminal

2.3.0.8 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .152.3.0.9 Housing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .16

2.4 Developer’s Kit . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .162.5 Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .17

2.5.1 Bootloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172.5.2 Windows CE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .172.5.3 Device Drivers. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .182.5.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .192.5.5 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19

CHAPTER 3. GETTING STARTED. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.1 Power On/Off/Reset . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21

3.1.1 Turn On the QTERM-G56/G58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .213.1.2 Power and Charge the Battery Powered QTERM-G58. . . . . . . . . . . . . . . . . . . . .223.1.3 Turn Off the QTERM-G56/G58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .223.1.4 Reset the QTERM-G56/G58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

3.2 Touch Screen . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233.2.1 Touch Screen Care . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233.2.2 Touch Screen Use . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .23

3.3 Function Keys . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .233.4 System Settings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243.5 RotationCE . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .243.6 Install Third-Party or Custom Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .253.7 Run Third-Party Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .263.8 Build Your Own Software. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .26

CHAPTER 4. SYSTEM SETTINGS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274.1 Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27

4.1.1 Stylus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .274.1.1.1 Double-Tap. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .284.1.1.2 Recalibrate . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29

4.1.2 PC Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .294.1.3 Keyboard . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .304.1.4 Date/Time . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .314.1.5 Volume and Sounds. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .324.1.6 Network and Dial-up Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .334.1.7 Storage Manager . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35

4.2 QTERM Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374.2.1 Audio . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374.2.2 Display. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374.2.3 Keypad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .374.2.4 Power. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .38

4.3 Registry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .384.4 File System Filter . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394.5 System Path . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .394.6 Boot-up Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .404.7 Applications. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

4.7.1 Microsoft . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

Contents

QTERM-G56/G58 Industrial HMI Terminal iii

4.7.2 Beijer Electronics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .41

CHAPTER 5. CONNECT TO A PC VIA ACTIVESYNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435.2 Connect the USB Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435.3 Download/Install ActiveSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .435.4 Connect the PC and QTERM-G56/G58 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44

CHAPTER 6. APPLICATION DEVELOPMENT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

6.1.1 Glossary. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .476.1.2 Related Documents . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .47

6.2 Setup . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .486.2.1 Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .486.2.2 SDK Installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .486.2.3 Target Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

6.2.3.1 ActiveSync . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496.2.3.2 Manual Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .49

6.2.4 Microsoft Visual Studio 2005/2008 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .496.2.4.1 Native . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .516.2.4.2 Managed . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .53

6.2.5 Remote Tools. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .546.3 Software Drivers . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .55

6.3.1 Keypad. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .556.3.1.1 Default Registry Setting for 24-Key Keypad . . . . . . . . . . . . . . . . . . . . . .566.3.1.2 Default Registry Setting for 40-Key Keypad . . . . . . . . . . . . . . . . . . . . . .58

6.3.2 Backlight . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .606.3.2.1 Keypad LEDs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .63

6.3.2.1.1 Setting the Shift and Power LEDS . . . . . . . . . . . . . . . . . . . . . .656.3.3 Serial Port . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .656.3.4 Network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .66

CHAPTER 7. OPTIONAL PERIPHERALS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .697.1 Wireless Ethernet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .69

CHAPTER 8. SPECIFICATIONS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .718.1 QTERM-G56. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .718.2 QTERM-G58. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73

CHAPTER 9. MECHANICAL . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .779.1 Layout and Dimensions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .779.2 Integral Cable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .789.3 Break Out Box (BOB) Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81

CHAPTER 10. TECHNICAL SUPPORT. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8310.1 Software Upgrades . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83

10.1.1 Operating System . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .8310.1.2 Bootloader . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .86

10.2 System Backup and Recovery . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .88

iv QTERM-G56/G58 Industrial HMI Terminal

FIGURES

Figure 1, QTERM-G56 Handheld Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .4Figure 2, QTERM-G56 Integral Cable Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .6Figure 3, QTERM-G58 Handheld Connector . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .12Figure 4, QTERM-G56/G58 Display . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .14Figure 5, Windows CE Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .19Figure 6, Demo Application . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .20Figure 7, Windows CE Desktop. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .21Figure 8, Windows CE Start Menu . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Figure 9, RotationCE System Tray Icon . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .24Figure 10, RotationCE Pop-up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .25Figure 11, Windows CE Control Panel . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .27Figure 12, Stylus Properties, Double-Tap . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .28Figure 13, Stylus Properties, Calibration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .29Figure 14, PC Connection Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Figure 15, Keyboard Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .30Figure 16, Date/Time Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .31Figure 17, Volume & Sounds Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .32Figure 18, QTERM-G56 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Figure 19, QTERM-G58 Network Connections . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .34Figure 20, Storage Properties, Internal Flash Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .35Figure 21, Storage Properties, Internal Flash Drive Scan Disk . . . . . . . . . . . . . . . . . . . . . . .35Figure 22, Storage Properties, Format Drive . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .36Figure 23, QTERM Panel. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .37Figure 24, ActiveSync, Get Connected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .44Figure 25, ActiveSync Partnership. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Figure 26, ActiveSync, Connected. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .45Figure 27, ActiveSync, Explore Device . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .46Figure 28, QTERM-G56/G58 Device Connection with Visual Studio . . . . . . . . . . . . . . . . .50Figure 29, Visual Studio, Connect to QTERM-G56/G58 Device . . . . . . . . . . . . . . . . . . . . .51Figure 30, Visual Studio, Native Project Properties. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .52Figure 31, Visual Studio, Managed Project Properties . . . . . . . . . . . . . . . . . . . . . . . . . . . . .54Figure 32, Key Number Mapping, 24-Key Keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .58Figure 33, Key Number Mapping, 40-Key Keypad . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .60Figure 34, Wireless Zero Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .65Figure 35, QTERM-G56/G58 Front and Back View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .73Figure 36, QTERM-G56/G58 Side View. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Figure 37, QTERM-G56/G58 Integral Cable. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .74Figure 38, QTERM-G56/G58 BOB Pinouts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .77Figure 39, WinVerCE. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .80Figure 40, System Package Upgrade . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Figure 41, System Package Upgrade Complete . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .81Figure 42, Bootloader Active . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Figure 43, Bootloader Setup. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .82Figure 44, Bootloader Load from Disk . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .83Figure 45, Bootloader Connected via USB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .84Figure 46, Recovery Image Desktop . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85Figure 47, Windows Explorer View Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .85

QTERM-G56/G58 Industrial HMI Terminal 1

CHAPTER 1

INTRODUCTION

The QTERM®-G56 and QTERM-G58 industrial HMI terminals are rugged yet economical graphic terminals for use in a wide range of commercial industrial applications. They have been designed with a robust set of industrial-grade features and options.

• Windows® Embedded CE 6.0 operating system

• Atmel AT91SAM9261S processor running at 192 MHz

• 256 Mbytes non-volatile storage (with support for larger capacities)

• 64 Mbytes of DDR SDRAM

• Bright TFT color QVGA display with 600 nit brightness

• Analog-resistive touch screen

• Built-in speaker

• One EIA-232/422/485 (software configurable) serial port

• Wireless (802.11b/g) Ethernet on QTERM-G58 only

• 10/100Base-T wired Ethernet on QTERM-G56 (E) only

• Wide operating temperature of -20 to 60 °C (-20 to 55 °C with wireless Ethernet option), storage temperature of -30 to 70 °C

• 8 to 32 VDC input voltage range

• Built-in protection from power transients and spikes (SAE J1455 compliant)

• Support for application development with industry standard tools such as Microsoft® Visual Studio 2005 and 2008

• Optional Developer’s Kit that includes: Break Out Box (BOB), power supply, BOB-to-unit connection cable, USB-to-unit connection cable, and Getting Started guide. The user man-ual and SDK are preloaded on the unit’s internal non-volatile storage device, which is also accessible via USB.

Introduction

2 QTERM-G56/G58 Industrial HMI Terminal

Notes


CHAPTER 2

PRODUCT DESCRIPTION AND ARCHITECTURE

2.1 QTERM-G56 Description and Interfaces

2.1.1 Description

The QTERM-G56 is a rugged handheld color LCD graphic terminal. It features a robust list of industrial-grade hardware features and options, including wired Ethernet.

The QTERM-G56 features a QVGA (320x240 pixel) transflective color TFT liquid crystal dis-play (LCD, 65536 colors) with integrated 4-wire analog-resistive touch screen. The display includes a light emitting diode (LED) backlight with software-controlled dimming capability. The LED provides reasonable contrast at low power consumption and easy readability. The transflective display provides excellent contrast in sunlight and high ambient light environments.

The QTERM-G56 is equipped with one serial “multiprotocol port,” which is a software-select-able EIA-232/422/485 serial port. The multiprotocol port 485 interface supports soft-ware-selectable AC terminations and a fail-safe network, which holds the 485 signal lines in a known state when no transceiver is transmitting. The terminal may optionally include one wired 10/100Base-T Ethernet interface. The QTERM-G56 without the Ethernet option includes a second EIA-232 serial port with RTS/CTS flow control.

User input occurs through the touch screen and a rugged 24-key or 40-key membrane keypad with steel snap domes. The standard keypad comes with four or five LEDs under the soft keys that can be used as status or alarm indicators. Power and shift buttons with LEDs are included on both keypad configurations. The power button enables and disables the internal power sup-ply for low power consumption. The terminal may optionally include a software-enabled elec-troluminescent keypad backlight.

The standard 40-key keypad legend allows for function/soft keys, eight-way directional con-trol and numeric entry in the unshifted mode and alphanumeric data entry in the shifted mode. Keys can perform alternate functions when the shift key is enabled. The keypad legend can be customized with your logo/name and custom keys.

The terminal is equipped with 4 MB of NOR flash memory, 64 MB of RAM memory, and 256 MB of internal NAND flash memory for mass storage. The NAND memory is accessible as a FAT-formatted file system both from the application and via the USB device interface (although not simultaneously).

The QTERM-G56 terminal includes a switching power supply with a wide input voltage range of 8 to 32 VDC. Typically, power is supplied through the 12-pin circular push-lock connector or integral cable. The unit may also be powered from a 5 volt USB host port.

QTERM-G56 Description and Interfaces Product Description and Architecture


Other features include a speaker with software-controlled volume. All units feature a real-time clock with one second resolution and battery backup power. The terminal may optionally include an integral cable. Terminals with the integral cable may optionally include a 2-pole, normally closed emergency stop switch.

2.1.2 Supported Interfaces

2.1.2.1 Connector Interface

The QTERM-G56 handheld terminal comes with one serial multiprotocol port through a 12-pin round connector (Hirose HR30-8R-12SC) or integral cable with strain relief, termi-nated with a DB15f connector. The multiprotocol port interface is software-selectable to EIA-232, EIA-422 or EIA-485. The EIA-485 interface includes AC terminations and a fail-safe network, each of which can be set in software. Units without the Ethernet option also include one serial EIA-232 auxiliary port.

Figure 1 shows the handheld unit connector orientation.

2.1.2.1.1 Power and USB Device Interfaces

The following table shows the pinout for the power and USB device interfaces.

EIA-232with proper cables and grounding the terminal can communicate up to five meters at a top speed of 115,200 bps

EIA-422 permits operation at distances up to 2,000 meters

EIA-485 permits multiple terminals to be connected in a multi-drop chain

Figure 1QTERM-G56 Handheld Connector

PinRegulated (standard)

PC USBHost Port

1 8 - 32 VDC 4.5 - 5.5 VDC

2 Ground Ground

11 N/A USB D+

12 N/A USB D-

Product Description and Architecture QTERM-G56 Description and Interfaces


2.1.2.1.2 Serial Multiprotocol Port Interface

The following table shows the connector pinout for the selected type of serial interface on the multiprotocol port.

2.1.2.1.3 Additional Serial Interface (without Ethernet option)

The following table shows the connector pinout for the G56L EIA-232 serial interface.

2.1.2.1.4 Network Interface (with Ethernet option)

The following table shows the cable pinout for the 10/100Base-T network interface.

2.1.2.1.5 Accessory Cable Wire Color Code and Demo Cable Pinout

The following table shows the wire color code for the 12-pin round connector to unterminated (“blank”) accessory cable and the pinout to the demo cable, which terminates in a 15-pin female D subminiature connector (DB15f); see section 2.1.2.2, “Integral Cable” for a diagram showing the DB15f orientation. The cable contains fifteen conductors; however, only twelve conductors are connected to pins on the round connector and DB15f. Ten of the fifteen con-ductors in the cable are wired as 100 ohm twisted pairs, as shown in the table. One of the fif-teen conductors is a non-insulated drain wire that is shorted to the foil shielding in the cable. This drain wire is not connected to the round connector or DB15f connector.

Pin EIA-232 EIA-422 EIA-485

3 Tx Tx- RTx-

4 RTS (out) Tx+ RTx+

5 Rx Rx+ No signal

6 CTS (in) Rx- No signal

Pin EIA-232

7 Tx

8 RTS (out)

9 Rx

10 CTS (in)

Pin Ethernet

7 Tx+

8 Tx-

9 Rx+

10 Rx-



2.1.2.2 Integral Cable

The QTERM-G56 can be optionally equipped with an integral cable (instead of the 12-pin round connector). This cable is terminated with a DB15f connector. Figure 2 shows the inte-gral cable connector orientation.

RoundConnector Pin

Wire Color Twisted PairsDemo Cable DB15f Pin

1 Brown – 9

2 Red with Black Stripe – 1

3 Black Pair #1 4

4 White Pair #1 5

5 Red Pair #2 10

6 Green Pair #2 11

7 White with Red Stripe Pair #3 7

8 White with Green Stripe Pair #3 14

9 Yellow Pair #4 6

10 Blue Pair #4 13

11 Orange Pair #5 2

12 Gray Pair #5 3

No Connect Violet – 8

No Connect Green with Black Stripe – 12

No Connect Drain – 15

Figure 2QTERM-G56 Integral Cable Connector



2.1.2.2.1 Power and USB Device Interfaces with Integral Cable

The following table shows the pinout for the power and USB device interfaces when the inte-gral cable option is selected.

2.1.2.2.2 Serial Interface with Integral Cable

The following table shows the pinout for the selected type of serial interface on the multiproto-col port.

2.1.2.2.3 Additional Serial Interface with Integral Cable (without Ethernet option)

The following table shows the pinout for the EIA-232 serial interface with integral cable.

2.1.2.2.4 Network Interface with Integral Cable (with Ethernet option)

The following table shows the pinout for the 10/100Base-T network interface.

DB15f Pin Regulated (standard) 5 Volt USB Host

9 8 - 32 VDC 4.5 - 5.5 VDC

1 Ground Ground

2 N/A USB D+

3 N/A USB D-

DB15f Pin EIA-232 EIA-422 EIA-485

4 Tx Tx- RTx-


10 Rx Rx+ No connect

11 CTS (in) Rx- No connect

Pin EIA-232

7 Tx

14 RTS (out)

6 Rx

13 CTS (in)

DB15f Pin Ethernet

7 Tx+

14 Tx-

6 Rx+

13 Rx-



2.1.2.2.5 E-stop Option with Integral Cable

If the terminal is equipped with the E-stop option (which requires the integral cable), the DB15f pinout changes to accommodate the switch signals, as shown below.

2.1.2.2.6 Power and USB Device Interfaces with E-stop Option and Integral Cable

The following table shows the pinout for the power and USB device interfaces when the E-stop option and integral cable are selected.

2.1.2.2.7 Serial Interface with E-Stop Option and Integral Cable (without Ethernet option)

The following table shows the pinout for the selected type of serial interface on the multiproto-col port with integral cable and E-stop option.

2.1.2.2.8 Additional Serial Interface with E-Stop Option and Integral Cable (without Ethernet option)

The following table shows the pinout for the EIA-232 serial interface with integral cable and E-stop option.

DB15f Pin Regulated (standard) 5 Volt USB Host

9 8 - 32 VDC 4.5 - 5.5 VDC

1 Ground Ground

2 N/A USB D+

3 N/A USB D-

DB15f EIA-232 EIA-422 EIA-485

4 Tx Tx- Rtx-

14 RTS (out) Tx+ Rtx+

10 Rx Rx+ No connect

13 CTS (in) Rx- No connect

Pin EIA-232

7 Tx

6 Rx



2.1.2.2.9 Network Interface with E-Stop Option and Integral Cable (with Ethernet option)

The following table shows the pinout for the 10/100Base-T network interface with integral cable and E-stop option.

2.1.2.2.10 Serial Interface with E-stop Option and Integral Cable (with Ethernet option)

The following table shows the pinout for each type of serial or network interface.

NOTE ☞ Due to pin constraints, the EIA-422 and EIA-485 multiprotocol serial port interfaces are not available with the E-stop/integral cable/Ethernet options, and the EIA-232 interface does not have RTS/CTS flow control. The terminal should be set to EIA-232 only with no hardware handshaking

2.1.2.2.11 E-stop Switch Interface with Integral Cable

The following table shows the integral cable pinout for the two-pole normally closed E-stop switch. The conductors for each pole (Pole 1 and Pole 2) of the switch are shorted until the switch is activated. After activation, each pole is an open circuit until the switch is reset.

2.1.2.2.12 Integral Cable Wire Color Code

The following table shows the wire color code for the DB15f connector on the integral cable; this information is provided to facilitate removal of the DB15f if desired. Ten of the fifteen conductors in the cable are wired as 100 ohm twisted pairs, as shown in the table. One of the fifteen conductors is a non-insulated drain wire that is shorted to the foil shielding in the cable.

DB15f Pin Ethernet

7 Tx+

14 Tx-

6 Rx+

13 Rx-

DB15f Pin EIA-232

4 Tx

10 Rx

DB15f Pin E-stop Switch

5 Pole 1

8 Pole 1

11 Pole 2

12 Pole 2



2.2 QTERM-G58 Description and Interfaces

2.2.1 Description

The QTERM-G58 is a rugged handheld color LCD graphic terminal. It features a robust list of industrial-grade hardware features and options, including wireless (802.11b/g) Ethernet and battery power.

The QTERM-G58 features a QVGA (320x240 pixel) transflective color TFT liquid crystal dis-play (LCD, 65536 colors) with integrated 4-wire analog-resistive touch screen. The display includes a light emitting diode (LED) backlight with software-controlled dimming capability. The LED provides reasonable contrast at low power consumption and easy readability. The transflective display provides excellent contrast in sunlight and high ambient light environ-ments.

The QTERM-G58 is equipped with one serial “multiprotocol port,” which is a software-select-able EIA-232/422/485 serial port. The multiprotocol port 485 interface supports soft-ware-selectable AC terminations and a fail-safe network, which holds the 485 signal lines in a known state when no transceiver is transmitting. The G58 also integrates an internal lith-ium-polymer battery pack for portable operation. The G58 may optionally include an 802.11b/g wireless Ethernet interface.

User input occurs through the touch screen and a rugged 24-key or 40-key membrane keypad with steel snap domes. The standard keypad comes with four or five LEDs under the soft keys

DB15f Pin Wire Color Twisted Pairs

1 Red with Black Stripe –

2 Orange Pair #5

3 Gray Pair #5

4 Black Pair #1

5 White Pair #1

6 Yellow Pair #4

7 White with Red Stripe Pair #3

8 Violet –

9 Brown –

10 Red Pair #2

11 Green Pair #2

12 Green with Black Stripe –

13 Blue Pair #4

14 White with Green Stripe Pair #3

15 Violet –



that can be used as status or alarm indicators. Power and shift buttons with LEDs are included on both keypad configurations. The power button enables and disables the internal power sup-ply for low power consumption (and extended battery life). The terminal may optionally include a software-enabled electroluminescent keypad backlight.

The standard 40-key keypad legend allows for function/soft keys, eight-way directional con-trol and numeric entry in the unshifted mode and alphanumeric data entry in the shifted mode. Keys can perform alternate functions when the shift key is enabled.

The keypad legend can be customized with your logo/name and custom keys.

The QTERM-G58 terminal is equipped with 4 MB of NOR flash memory, 64 MB of RAM memory, and 256 MB of internal NAND flash memory for mass storage. The NAND memory is accessible as a FAT-formatted file system both from the application and via the USB device interface (although not simultaneously).

The QTERM-G58 terminal includes a switching power supply with a wide input voltage range of 8 to 32 VDC. Typically, power is supplied through the 12-pin circular push-lock connector or integral cable. The unit may be operated from a 5 volt USB host port, but note that in this case it is powered from the internal battery, not the USB host. To conserve battery power, the optional 802.11b/g wireless Ethernet interface is not accessible.

Other features include a speaker with software-controlled volume. All units feature a real-time clock with one second resolution and battery backup power.

2.2.2 Supported Interfaces

2.2.2.1 Connector Interface

The QTERM-G58 handheld terminal comes with one serial multiprotocol port through a 12-pin round connector (Hirose HR30-8R-12SC). The multiprotocol port interface is soft-ware-selectable to EIA-232, EIA-422 or EIA-485. The EIA-485 interface includes AC termi-nations and a fail-safe network, each of which can be set in software.

EIA-232with proper cables and grounding the terminal can communicate up to five meters at a top speed of 115,200 bps

EIA-422 permits operation at distances up to 2,000 meters

EIA-485 permits multiple terminals to be connected in a multi-drop chain



Figure 3 shows the handheld unit connector orientation.

2.2.2.1.1 Power and USB Device Interfaces

The following table shows the pinout for the power and USB device interfaces.

2.2.2.1.2 Serial Multiprotocol Port Interface

The following table shows the connector pinout for the selected type of serial interface on the mulitport.

2.2.2.1.3 Accessory Cable Wire Color Code and Demo Cable Pinout

The following table shows the wire color code for the 12-pin round connector to unterminated (“blank”) accessory cable and the pinout to the demo cable, which terminates in a 15-pin female D subminiature connector (DB15f). The cable contains fifteen conductors; however, only twelve conductors are connected to pins on the round connector and DB15f. Ten of the fifteen conductors in the cable are wired as 100 ohm twisted pairs, as shown in the table. One of the fifteen conductors is a non-insulated drain wire that is shorted to the foil shielding in the cable. This drain wire is not connected to the round connector or DB15f connector.

Figure 3QTERM-G58 Handheld Connector

PinRegulated (standard)

PC USBHost Port

1 8 - 32 VDC 4.5 - 5.5 VDC

2 Ground Ground

11 N/A USB D+

12 N/A USB D-

Pin EIA-232 EIA-422 EIA-485

3 Tx Tx- RTx-


5 Rx Rx+ No signal

6 CTS (in) Rx- No signal

Product Description and Architecture Hardware


2.3 Hardware

Both the QTERM-G56 and QTERM-G58 include the following hardware components.

2.3.0.1 Processor

The processor in the QTERM-G56/G58 is the Atmel AT91SAM9261S processor, running at 192 MHz.

2.3.0.2 Display

The standard QTERM-G56/G58 features a QVGA (320x240 pixel) transflective color TFT LCD (65536 colors). The display includes a light emitting diode (LED) backlight with soft-ware-controlled dimming capability. The LED backlight provides reasonable contrast at low power consumption and easy readability. The transflective display provides excellent contrast in sunlight and high ambient light environments. Refer to Figure 4.

RoundConnector Pin

Wire Color Twisted PairsDemo Cable DB15f Pin

1 Brown – 9

2 Red with Black Stripe – 1

3 Black Pair #1 4

4 White Pair #1 5

5 Red Pair #2 10

6 Green Pair #2 11

7 White with Red Stripe Pair #3 7

8 White with Green Stripe Pair #3 14

9 Yellow Pair #4 6

10 Blue Pair #4 13

11 Orange Pair #5 2

12 Gray Pair #5 3

No Connect Violet – 8

No Connect Green with Black Stripe – 12

No Connect Drain – 15

Hardware Product Description and Architecture


2.3.0.3 Touch Screen

The QTERM-G56/G58 provides user input through an integrated 4-wire analog-resistive touch screen.

2.3.0.4 Keypad

User input occurs through a rugged 24-key or 40-key membrane keypad with steel snap domes. The standard keypad comes with four or five LEDs under the soft keys that can be used as status or alarm indicators. Power and shift buttons with LEDs are included on both keypad configurations. The power button enables and disables the internal power supply for true shut-down.

The standard 40-key keypad legend allows for function/soft keys, eight-way directional con-trol and numeric entry in the unshifted mode and alphanumeric data entry in the shifted mode. Keys can perform alternate functions when the shift key is enabled.

The keypad legend can be customized with your logo/name and custom keys.

2.3.0.5 Speaker

The QTERM-G56/G58 includes an internally mounted 20 x 40 mm speaker, providing the ability to play a variety of audio, including audible feedback, warnings, messages, and media clips.

The terminal includes an audio decoder that allows it to play PCM audio (.wav) files (includ-ing MP3 files).

Figure 4QTERM-G56/G58 Display

Product Description and Architecture Hardware


2.3.0.6 Real-Time Clock

The QTERM-G56/G58 terminal includes a battery-backed real-time clock. The real-time clock can be used to time/date stamp messages or for timed polling and program execution.

2.3.0.7 System Memory

DRAMThe QTERM-G56/G58 includes 64 Mbytes of SDRAM volatile memory with a maximum bandwidth of 192 Mbytes per second.

NAND FlashThe QTERM-G56/G58 uses an internal 256 Mbytes NAND flash to hold the main Windows CE image and provide non-volatile storage for user applications and data. This is accessible as a FAT-formatted file system both from the application and the USB device port (but not simul-taneously). Refer to section 4.1.7 for information on accessing the internal flash memory using the USB device port.

NOTE ☞ The terminal may be customized with a larger capacity flash. Contact Beijer Electronics tech-nical support at http://www.beijerelectronicsinc.com/support/contact/?type=tech for more information.

2.3.0.8 Power Supply

The QTERM-G56/G58 has an 8- to 32-volt input range and can be powered directly from a 12- or 24-volt power supply. The terminal includes circuitry to protect against normal varia-tions such as transients and spikes (SAEJ1455 compliant).

Power is supplied to the terminal via the 12-pin round connector or integral cable. DC power must be in the range of 8 to 32 volts (the current will vary depending on the input voltage; see the following table).

WARNING There may be danger of leakage if the battery is incorrectly replaced, creating a potential health hazard. Replace the battery only with the same (CR2032) or equivalent type as recom-mended by the manufacturer. Dispose of used batteries according to the manufacturer’s instructions.

CAUTIONQTERM-G56/58 power must come from an SELV (Safety Extra Low Voltage) power source and should have a current limit on its output of 5 Amperes. It must provide a minimum of 8 volts DC power and be limited to a maximum of 32 volts DC. Limiting may be inherent to the supply or may be provided by supplementary overcurrent devices. If the QTERM-G56/G58 does not respond or exhibits abnormal behavior on power up, disconnect power and contact Beijer Electronics for technical support.

Developer’s Kit Product Description and Architecture


2.3.0.9 Housing

The QTERM-G56/G58 housing is made of a tough, automotive grade polycarbonate that is designed to withstand everyday use in commercial industrial environments.

2.4 Developer’s Kit

The QTERM-G56/G58 Developer’s Kit includes the following:

• Break Out Box with power supplyThis device is used to power the QTERM-G56/G58 and provide serial and Ethernet and/or USB device communications connections to the QTERM-G56/G58. Refer to Chapter 6, “Application Development” for more information on setting up the QTERM-G56/G58 to debug and develop applications. Refer to section 9.3, “Break Out Box (BOB) Pinouts” for pinout and connection information.

• USB device connectionThe host can communicate with the QTERM-G56/G58 during a remote debugging session via ActiveSync over a USB connection. The QTERM-G56/G58 Developer’s Kit includes a USB cable that can be used for the ActiveSync connection. Refer to Chapter 5, “Connect to a PC Via ActiveSync” for information on setting up an ActiveSync connection.

QTERM-G56 Current Consumption

Terminal 12 VDC 24 VDC

Power off 2 mA 5 mA

Idle 75 mA 50 mA

Ethernet option, active 155 mA 90 mA

Ethernet option, idle 130 mA 80 mA

Active 200 mA 115 mA

EL Keypad Backlight add 10 mA add 6 mA

QTERM-G58 Current Consumption

Terminal 12 VDC 24 VDC Battery

Power off 2 mA 5 mA —

Idle 100 mA 65 mA 110 mA

Active 180 mA 100 mA 195 mA

Charging add 1200 mA max — —

Wireless Ethernet add 95 mA add 50 mA add 125 mA

EL Keypad Backlight add 10 mA add 6 mA add 13 mA

Product Description and Architecture Software


The SDK provides support for developing applications for the QTERM-G56/G58 in the form of libraries and header files. Refer to section 6.2.2, “SDK Installation” for more information on the software development kit.

Source code and a Microsoft Visual Studio 2008 solution are provided for the demo applica-tion preinstalled on QTERM-G56/G58 terminals with the Developer’s Kit. The demo is a .NET-based application that is written in C# and provides several examples of how to interface with the QTERM-G56/G58 hardware.

2.5 Software

2.5.1 Bootloader

The QTERM-G56/G58 has a bootloader application that executes on boot-up, loads the Win-dows CE kernel into memory, and boots the kernel. The QTERM-G56/G58 has a typical 20-second boot time. Refer to section 10.1.2, “Bootloader” for information on upgrading the bootloader.

2.5.2 Windows CE

The QTERM-G56/G58 runs the Windows Embedded CE 6.0 operating system. Windows CE is a resource-constrained and scalable version of Microsoft Windows for embedded hardware that offers broad support for third-party application development, software, and hardware.

The QTERM-G56/G58 utilizes the Core or Professional (optional) version of Windows CE that includes application support libraries, graphical shell (Windows Explorer), and other items. The Core version does not include Windows Media Player (codecs are included) and Internet Explorer. The graphical shell contains program management and control panel rou-tines. Following are some of the components that are included with the QTERM-G56/G58. For a complete list, refer to the document available from the following website:http://www.microsoft.com/windowsembedded/en-us/products/windowsce/component-library.mspx

• Active Template Library

• Microsoft Foundation Classes

• .NET Compact Framework v3.5

• ActiveSync

• Local Area Networking

• Wide Area Networking

• Peer-to-Peer Networking

• Power Management

Software Product Description and Architecture


• Hive-based (persistent) Registry

• Direct Draw video graphics engine

• Command Shell

• Graphical Shell

• Soft Keyboard

Windows CE on the QTERM-G56/G58 uses about 50 Mbytes of disk space in the form of hid-den/reserved sectors. Thus the disk capacity seen via a USB device or from the OS/application will be less than the expected 256 MB. The operating system may need to be upgraded for future releases. See Chapter 10, “Technical Support” for details on how to upgrade the QTERM-G56/G58 system package.

2.5.3 Device Drivers

The QTERM-G56/G58 contains hardware peripherals that require additional support beyond that provided by Windows CE to set up and operate. Beijer Electronics provides software device drivers for these peripherals as part of the standard operating system installation. Fol-lowing is a list of some peripherals requiring Beijer Electronics-provided support.

• LCD display

• Display and keypad backlight

• Audio codec/controller

• Touch screen

• Integrated keypad

• Serial port

• Ethernet interface

• USB device port

• Power management

• Real time clock

Device drivers are included in the operating system as dynamically linked libraries. They are loaded and initialized at boot-up and provide run-time interfaces for application programming.

A standard driver application interface allows you to dynamically configure the hardware without detailed knowledge about the components. For example, you can set the display and keypad backlight intensities and re-map the keypad key functions. See Chapter 6, “Application Development” for details on the device driver program interfaces and how they can be used in user applications.

Product Description and Architecture Software


2.5.4 System Settings

Control panel applets provide a graphical user interface for controlling some of the QTERM-G56/G58 hardware peripherals. These applets utilize the device driver interfaces described in the previous section. Display the control panel in Windows CE by tapping the Start menu and then Settings, Control Panel (see Figure 5).

The QTERM Input Panel desktop shortcut provides a convenient central location to access most of the commonly used hardware controls. Refer to Chapter 4, “System Settings” for detailed information about the QTERM Panel and other control panel applets that control the QTERM-G56/G58 hardware.

2.5.5 Applications

Windows CE comes with several user applications (see section 2.5.2, “Windows CE”). In addition, there are a variety of utility applications available with Windows CE. These applica-tions are located either in the \Windows directory or on the internal NAND flash. Beijer Elec-tronics provides applications to supplement the Windows CE applications, including RegEditCE.exe for editing the registry. These applications are located on the internal NAND flash in the \HardDisk\bin directory. In addition, you can write your own applications for the QTERM-G56/G58. These applications must be compiled for Windows CE running on an ARM platform. See Chapter 6, “Application Development” for application development setup instructions and code samples.

The QTERM-G56/G58 Developer’s Kit includes a special application called “QTERM Demo” (see Figure 6).You can access the demo from a desktop shortcut. QTERM Demo can be down-loaded from http://www.beijerelectronicsinc.com and installed on any Windows CE enabled QTERM-G56/G58. This application highlights some of the hardware and software capabilities of the QTERM-G56/G58 and illustrates the potential for user applications. QTERM Demo is a .NET-based C# Smart Device application compiled with Microsoft Visual Studio 2008.

Figure 5Windows CE Control Panel

Software Product Description and Architecture


Figure 6Demo Application


CHAPTER 3

GETTING STARTED

3.1 Power On/Off/Reset

3.1.1 Turn On the QTERM-G56/G58

When you connect power to the QTERM-G56/G58 terminal (see section 2.3.0.8, “Power Sup-ply”), the unit will remain unpowered until you press the green power button on the keypad. The unit is turned on or off by pressing the power button.

When you press the green power button, the QTERM-G56/G58 boots and loads the operating system, as shown below.

Icons for software your company has installed may be displayed in addition to those shown above.

To use the QTERM-G56/G58, press the keys on the QTERM-G56/G58 keypad, or tap the icons/buttons on the touch screen.

Refer to section 3.2, “Touch Screen” for information on using the touch screen.

Figure 7Windows CE Desktop

Power On/Off/Reset Getting Started


3.1.2 Power and Charge the Battery Powered QTERM-G58

The QTERM-G58 includes an internal rechargeable battery pack for untethered operation. Press the power button on the keypad to power the terminal on and off.

Power (8 to 32 VDC) may be connected to the G58 terminal at any time. When external power is detected, the terminal will use external power instead of the battery for operation.

Charge the internal battery by connecting a 12 VDC supply and ground to the power pins of the terminal. Beijer Electronics offers charging cable accessories for standard AC main power (with optional international plug kit) and a vehicle cigarette lighter adapter. If the terminal is powered off at connection, the power and shift LEDs on the keypad will light, and the display will show a battery charging icon. The icon and shift LED will flash during charging. A con-tinuously lit shift LED and static battery icon on the display indicate that charging is complete. If the unit is powered on when the charge power supply is connected, the unit will boot up as usual, charging will continue, and status icons will be displayed in the system tray area.

3.1.3 Turn Off the QTERM-G56/G58

You can use one of three methods to turn off the QTERM-G56/G58, as follows:

• Press the green power button. Press the same button again to turn it back on.

• On the QTERM-G56, disconnect the cable from the power source. Reconnect the cable to the power source to power the unit back on. (The QTERM-G58 will automatically switch to battery power and continue operating when the cable is disconnected.)

• If you have a Developer's Kit with a Break Out Box, set the power switch on the Break Out Box to the “off” position. Set it to the “on” position to power the unit back on.

When the QTERM-G56/G58 is powered off, information in the Windows CE registry and any data stored on the internal flash hard-disk (\HardDisk) is retained. However, the Windows CE file system root folder is RAM-based and will be lost. Consequently, any information that must be retained must be stored under the \HardDisk folder. To avoid losing data, make sure you close any open applications and back up data to a persistent storage location before power-ing off the QTERM-G56/G58. Corruption will occur if data is being written to files located on \HardDisk during a loss of power.

WARNINGThe QTERM-G58 internal battery pack is not user-serviceable. Contact Beijer Electronics for battery service or replacement.DO NOT attempt to remove the battery pack from the terminal housing.DO NOT puncture, bend, or place mechanical strain on the battery pack.DO NOT attempt to charge the battery pack by any means other than the battery charge cir-cuitry included on the QTERM-G58 circuit board.

Getting Started Touch Screen


3.1.4 Reset the QTERM-G56/G58

Reset the QTERM-G56/G58 if the system stops operating. Press and hold the green power button until the power LED goes out (usually about seven seconds). Release the power button, and the unit will automatically restart. If the QTERM-G56/G58 does not restart, verify that the cable is fully seated and has power.

To place the QTERM-G56/G58 into a special recovery mode (SOS), hold down the shift key and one other key. Refer to section 10.2, “System Backup and Recovery” for information.

3.2 Touch Screen

3.2.1 Touch Screen Care

Use only your fingertip or a stylus to tap the touch screen. Other objects (such as either end of a pencil) will damage the transparent film or plastic backing. Use a light touch, just hard enough for the screen to respond.

To clean the touch screen, moisten a soft cloth with water or a window cleaner such as Win-dex®. Then gently wipe the screen clean with the cloth. Do not spray liquid directly on the touch screen.

3.2.2 Touch Screen Use

When you tap or press on the QTERM-G56/G58 touch screen, it responds with a clicking sound. Tap on an icon (e.g., “My Device”) to highlight and select the item. Tap twice (dou-ble-tap) on an icon to open the item or start the program.

Tap [Start] to display the Windows Start menu, which gives you access to all system functions and programs. Any of the menu options with right-pointing arrows will open a sub-menu. Tap once on an option to display its sub-menu. For example, tap Programs, and a sub-menu of all user programs loaded on your QTERM-G56/G58 is displayed.

Tap the screen background to close the Start menu, or tap [Start] again.

NOTE ☞ If you are having problems selecting functions on the touch screen, you may need to recali-brate the touch screen. Refer to section 4.1.1.2, “Recalibrate” on page 29 for information.

3.3 Function Keys

The function keys are mapped by default to the keyboard keys F1, F2, F3, F4, and optionally F5 depending on your chosen keypad configuration. The keys may be mapped to any keyboard or mouse (cursor control) function. You can modify the Windows CE registry or write a pro-gram to set the keypad mappings. Refer to section 6.3.1, “Keypad” for more details.

System Settings Getting Started


3.4 System Settings

To access the system settings (double-tap, calibration, PC connection, keyboard, date/time, volume/sounds, network/dial-up connections, and storage manager) through the Windows CE control panel, select Start, Settings, and Control Panel as shown below.

Refer to Chapter 4, “System Settings” for information on the control panel settings.

3.5 RotationCE

Some Windows CE shell dialogs may be larger than the screen so that you cannot access all elements in the dialog box. In these cases it can be helpful to rotate the screen to portrait mode.

RotationCE is a utility included with the QTERM-G56/G58. You will find an icon for it in the Windows CE system tray (you may need to scroll through the icons by clicking the small blue arrows). Tap the small yellow up-arrow icon to open the utility (see Figure 9).

Figure 8Windows CE Start Menu

Figure 9RotationCE System Tray Icon

Getting Started Install Third-Party or Custom Software


A pop-up appears with arrows that allow you to quickly rotate the screen to a more convenient orientation (see Figure 10).

• Tap the arrow on the left to rotate the screen counter-clockwise 90 degrees.

• Tap the arrow on the right to rotate the screen clockwise 90 degrees.

• Tap the arrow in the center to rotate the screen 180 degrees.

• Tap anywhere on the screen outside the pop-up to close the pop-up.

You can also use the “Always on top” and “Auto hide” options in the Taskbar & Start Menu dialog box to help access elements in a dialog box that are not visible. Tap Start, Settings, and Taskbar & Start Menu. Select Always on top to ensure that the taskbar is always visible. Select Auto hide to hide the taskbar. To redisplay the taskbar, point to the area of your screen where the taskbar is located. To assure that your taskbar will be visible whenever you point to it, click Always on top in addition to Auto hide.

3.6 Install Third-Party or Custom Software

You can install any software application on the QTERM-G56/G58 that is compatible with Windows CE, has been compiled for the ARM platform, and does not exceed the system requirements of your QTERM-G56/G58. You can download it from a network or the Internet (depending on your interface setup), or you can use ActiveSync (refer to Chapter 5, “Connect to a PC Via ActiveSync” for information).

Third-party software applications are typically packaged in a Microsoft CAB file format, which are then packaged in a PC-side installer executable or Microsoft MSI file. The bare CAB files can be copied to the QTERM-G56/G58 and installed manually, or the MSI file can be executed on a PC and the included CAB file downloaded and installed via ActiveSync.

For applications installed via ActiveSync, execute the downloaded installation file from Win-dows Explorer on a PC. The application installer should automatically launch ActiveSync,

Figure 10RotationCE Pop-up

Run Third-Party Software Getting Started


download a CAB file to the QTERM-G56/G58, and initiate installation of the CAB file on the QTERM-G56/G58.

A CAB file can be downloaded directly to the QTERM-G56/G58 without ActiveSync. For this type of installation, double-tap the CAB file from a Windows Explorer session on the QTERM-G56/G58 to initiate the installation process.

NOTE ☞ It is recommended that the destination of the CAB file installation files be in the HardDisk directory because that location is on the internal persistent storage, otherwise the installation will be lost after a power cycle.

NOTE ☞ See section 10.1.1, “Operating System” on page 83 for information about UpgradeCE.exe, a Beijer Electronics package manager program that can be used similarly to the Windows CE CAB installer. UpgradeCE.exe software application packages and settings are retained even after system firmware upgrades.

3.7 Run Third-Party Software

Third-party or custom software installed on the QTERM-G56/G58 may be listed in the Start menu under “Programs.” Tap a program name in the menu to run the program.

A program may also have an icon on the desktop. If so, double-tap the icon to start the pro-gram.

3.8 Build Your Own Software

You can write your own applications and program your own key functions (for the function keys on the QTERM-G56/G58) using Microsoft programming tools. Refer to Chapter 6, “Application Development” for more information.


CHAPTER 4

SYSTEM SETTINGS

4.1 Control Panel

Many of the system settings can be adjusted through the Windows CE control panel. To access the control panel, select Start, Settings, and Control Panel.

Applets on the control panel that are used to configure QTERM-G56/G58 settings include the following (see Figure 11):

• Stylus (double-tap speed and recalibration)

• PC Connection

• Keyboard

• Date/Time

• Volume and Sounds

• Network and Dial-up Connections

• Storage Manager

4.1.1 Stylus

Use the Stylus applet to set the double-tap speed and spacing or to recalibrate the touch screen. You should recalibrate any time it becomes difficult to make selections or to double-tap items on the screen. Double-tap the Stylus icon on the control panel, and the Stylus Properties dia-log box is displayed.

Figure 11Windows CE Control Panel

Control Panel System Settings


4.1.1.1 Double-Tap

To set the speed and distance between double-taps, tap the Double-Tap tab, as shown below.

On the checkered grid at the top, tap the grid twice (double-tap) using a tap speed that is com-fortable for you. The tap speed should be quick, but not so quick that it becomes difficult to do.

Below the checkered grid is an image of a “director’s” sign. Double-tap on the image to test your new setting. The top of the sign should lift up or drop down with each double-tap. If it does not, reset the double-tap action on the checkered grid.

You can keep resetting the double-tap until it is right for you. Tap [OK] to save any changes and exit. Tap [X] to exit the dialog box without saving.

Figure 12Stylus Properties, Double-Tap

System Settings Control Panel


4.1.1.2 Recalibrate

To recalibrate the touch screen, tap the Calibration tab, as shown below.

Tap [Recalibrate], and a large “+” symbol is displayed on the screen. Tap and hold briefly as close to the center of the symbol as possible. When you lift the stylus, the symbol moves to another location on the screen. Tap and hold the center of the symbol again; lift the stylus, and the symbol moves again. In order to fully calibrate the touch screen, you must continue this process until you have tapped the center of the symbol five times. These five taps are used to calculate the horizontal and vertical offset parameters of the touch screen. If the symbol con-tinues to move after the fifth tap, the calibration was unsuccessful and you must repeat the five taps. An unsuccessful calibration results when the offset calculated for one calibration point

differs from another. If the calibration is successful, the “+” symbol is no longer visible. Tap the touch screen one more time, or press [Enter], to save the calibration settings.

Touch screen calibration data is stored in the persistent registry (see section 4.3, “Registry” for more information). After the unit has been calibrated once, the calibration data is retained between re-boots. The touch screen calibration screen automatically appears when you boot the unit if there is no calibration data present in the registry.

4.1.2 PC Connection

Use the PC Connection control panel applet to enable or disable remote connections with a desktop PC (ActiveSync). Refer to Chapter 5, “Connect to a PC Via ActiveSync” on page 43 for more information about setting up an ActiveSync connection. Select the checkbox labeled, “Allow connection with desktop computer when device is attached” to enable remote PC con-nections with the QTERM-G56/G58 (see Figure 14).

Figure 13Stylus Properties, Calibration



The default device used for remote connection is the USB device port, which appears in Win-dows CE as the serial port device on COM5 (“USB COM5”).

Tap [OK] to save any changes and exit. Tap [X] to exit the dialog box without saving.

4.1.3 Keyboard

Use the Keyboard applet to set the repeat delay and repeat rate for keyboard keys. These parameters apply to any connected USB keyboard as well as the QTERM-G56/G58 keypad buttons. Double-tap the Keyboard icon on the control panel, and the Keyboard Properties dia-log box is displayed, as shown below.

Figure 14PC Connection Properties

Figure 15Keyboard Properties



Enable Character RepeatSelect this option to turn the key repeat feature on or off. If “on,” a key entry repeats if you hold down the key on the keyboard or keypad. All keypad repeats are disabled if this checkbox is not selected.

Repeat DelayIf you enabled “character repeat,” use this function to select the delay time that you want between when a key is pressed and when it begins to repeat automatically. Tap and hold the slider and slide it up or down the slider bar to set the delay, or tap the left or right arrow button at the ends of the slider bar to move by smaller increments.

Repeat RateIf you enabled “character repeat,” use this function to select the time that you want between each repeat when a key begins to repeat automatically. Tap and hold the slider and slide it up or down the slider bar to set the delay, or tap the left or right arrow button at the ends of the slider bar to move by smaller increments.

Tap in the data entry box at the bottom of the dialog box, and press a key to test the repeat delay and repeat rate. You can reset the delay and rate until the settings are right for you.


4.1.4 Date/Time

Use this applet to set the time and date on the QTERM-G56/G58. Tap the Date/Time icon on the control panel, or tap the clock on the task bar (see Figure 16).

To change the year, continuously change the month to successive or prior months until the desired year is reached. Alternatively, tap the year display, and type the year using the on-screen soft keyboard.

Figure 16Date/Time Properties



To change the month, tap the left-pointing arrow at the top of the calendar to select the previ-ous month, or tap the right-pointing arrow to select the next month. Alternatively, tap the month display, and select the desired month from the pop-up list. To select a date in a month, tap the date in the calendar.

To change the time, in the “Current Time” box, tap the hour, minute, or AM/PM position to select it, then tap the selection arrows to increase or decrease the number. Alternatively, tap the time display to select the hours, minutes, seconds, or “AM/PM” field, and enter the time using the on-screen soft keyboard.

To select a different time zone, tap the drop-down arrow for the “Time Zone” box and then tap the correct time zone in the drop-down list.

The checkbox “Automatically adjust clock for daylight saving” is selected by default. If the QTERM-G56/G58 will be used in an area that does not follow daylight savings time, deselect this option.

NOTE ☞ The QTERM-G56/G58 has been updated to be compliant with the latest dates for daylight sav-ings time changes (per the U.S. daylight savings time zones and dates change effective in 2007).

Tap [Apply] to apply changes in the settings without exiting the dialog box. Tap [OK] to apply the changes and exit. Tap [X] to exit the dialog box without saving your settings.

4.1.5 Volume and Sounds

Use this applet to adjust the volume of system responses and to specify for which screen actions the QTERM-G56/G58 will respond with a sound. Tap the Volume & Sounds icon on the control panel to display the Volume & Sounds Properties dialog box, as shown below.

Figure 17Volume & Sounds Properties



To enable sounds and adjust the volume, tap the Volume tab.

Enable sounds for:

EventsIf you want a sound emitted when the system gives a warning or a system event occurs, select this option.

ApplicationsIf you want sounds generated by programs, select this option.

NotificationsIf you want sounds emitted for alarms, appointments, and reminders, select this option.

Enable clicks and taps for:

Key clicksSelect this option if you want to hear clicks when you press a key on either the keypad or an external keyboard. If you select key clicks, also select whether you want the click sound to be Loud or Soft.

Screen tapsSelect this option if you want to hear a sound when you tap the screen. If you select this option, also select whether you want the tap sound to be Loud or Soft.

System VolumeUse the slider at the left-hand side of the dialog box to select the overall volume of system sounds. Tap and hold the slider and slide it up or down the slider bar to adjust the sounds louder or softer, or tap the Soft or Loud arrows to adjust it in smaller increments. A sound is emitted as you make each adjustment so you can monitor the setting.

Tap [OK] to save the settings and exit the dialog box. Tap [X] to exit the dialog box without saving your settings.

4.1.6 Network and Dial-up Connections

The Network and Dial-up Connections control panel applet launches a Network Connections application (see Figure 18 and Figure 19), which is used to set up and configure remote con-nections. An icon is created for each connection (connectoid). Once configured, the connec-toid can be launched to initiate the remote connection.



The default connectoid for QTERM-G56 remote connections is the DM9CE1. The DM9CE1 connection uses the internal 10/100 Ethernet adapter to provide a standard TCP/IP interface.

The default connectoid for QTERM-G58 remote connections is the RT250USB. The RT250USB connection uses the optional internal USB WiFi Ethernet adapter to provide a standard TCP/IP interface.

Both the DM9CE1 and RT250USB connections automatically obtain IP configuration (address, subnet mask, and gateway) if DHCP is enabled. Right-click, or select File, Proper-ties from the menu for the DM9CE1 connectoid to configure DHCP or static values, as well as name servers for this connection. DHCP is enabled by default.

Running ipconfig from the command shell (Start, Programs, Command Prompt) lists detailed information for the QTERM-G56/G58 network connections.

Figure 18QTERM-G56 Network Connections

Figure 19QTERM-G58 Network Connections



4.1.7 Storage Manager

Use the Storage Manager applet to administer the QTERM-G56/G58’s internal and external storage devices. The contents of the \HardDisk directory are located on an internal NAND flash device. The contents of \USBHardDisk, \USBHardDisk2, and so on, are located on exter-nal USB memory drives. These devices may be formatted, scanned, and defragmented using the Storage Manager utility.

Figure 20 shows the Storage Manager applet on the QTERM-G56/G58 internal flash memory.

Figure 21 shows the results of a scan disk operation on the internal flash storage device.

Figure 20Storage Properties, Internal Flash Drive

Figure 21Storage Properties, Internal Flash Drive Scan Disk



The storage device must be dismounted before formatting, scanning, or defragmenting. For the internal flash device, it is recommended that these operations be performed only from the recovery Windows CE image (refer to section 10.2, “System Backup and Recovery”). The main Windows CE operating system image actively accesses files on the internal flash device. This access is interrupted by storage administration operations. Re-mounting the device will fail, and it must be rebooted to return it to a working state.

Figure 22 shows the Storage Manager’s Format dialog box launched from the recovery image for the internal flash storage.

FAT32 Quick Format is recommended for reformatting operations on the internal storage. Sometimes a full format may be desired, but allow several minutes for completion. Note that the eXFAT format option is selected by default; FAT32 must be manually selected from the drop-down box.

WARNING ☞ Use caution when formatting the internal flash device! The result will be a complete loss of user data, user applications, and main operating system package. A recovery procedure will be required to restore the QTERM-G56/G58 to a usable state. Refer to section 10.2, “System Backup and Recovery” for more information.

NOTE ☞ Beijer Electronics recommends that the partition configuration be left intact for storage devices. Do not remove partitions or create new partitions as this may cause data on the devices to be irretrievable.

Figure 22Storage Properties, Format Drive

System Settings QTERM Panel


4.2 QTERM Panel

The QTERM Panel provides quick access to all of the QTERM-G56/G58 hardware controls, including those for the display and keypad backlight, touch screen, speaker, keypad, and power saving/screen saver modes.

To open the QTERM Panel (see Figure 23), tap the Input Panel desktop shortcut.


4.2.1 Audio

Tap the Up or Down button to increase or decrease the speaker volume. Use this control for more precision for the volume setting than the Volume and Sounds Control Panel applet pro-vides. Tap Mute to turn the audio off.

4.2.2 Display

Tap Decrease or Increase to set the intensity of the display and keypad backlight from 0 to 100%.

Tap On or Off to enable or disable the keypad backlight.

Tap the Touch Screen Calibration button to initiate the calibration procedure. Refer to section 4.1.1.2, “Recalibrate” for more details.

4.2.3 Keypad

The Enable Character Repeat, Repeat, and Delay controls are identical to those found in the Keyboard Control Panel applet. Refer to section 4.1.3, “Keyboard” for more information on these controls.

Figure 23QTERM Panel

Registry System Settings


The keypad keys may be optionally mapped to mouse/cursor functions as described in section 3.3, “Function Keys” and section 6.3.1, “Keypad”. The Cursor Acceleration control affects the mouse pointer acceleration when it is controlled from a keypad key that is mapped for that function. Tap the Slow or Fast button to increase or decrease the acceleration. Increased acceleration reduces the time required for the cursor to traverse a distance as the keypad key is held, but also reduces the cursor accuracy.

4.2.4 Power

The power saving controls affect the transition times from full on to User Idle and System Idle power states when the QTERM-G56/G58 is not in use. In User Idle mode, the display intensity is dimmed to a low level. In System Idle mode, it is disabled. Touch screen or keypad activity will cause the QTERM-G56/G58 to transition out of an idle state.

Tap the drop-down arrow for the User Idle or System Idle settings to select the number of sec-onds or minutes after which the QTERM-G56/G58 will enter the selected power mode. The User Idle and System Idle time-outs can be adjusted to a continuous range of time values by typing a number in the drop-down box or via a programmatic interface.

Disable or enable the transition to User Idle or System Idle power states by tapping Disable or Enable at “User Idle mode after” or “System Idle mode after.” You can also type 0 in either drop-down box to disable the transition.

Disabling the User Idle mode transition automatically disables the System Idle transition, regardless of the System Idle time-out or button setting. Set the User Idle mode transition time-out to one second to skip the User Idle and transition directly to System Idle.

4.3 Registry

Windows CE uses a registry to store system settings and run-time configuration data. The QTERM-G56/G58 supports a hive-based registry, meaning that the settings in the registry are maintained between power cycles. The hive registry is stored in special system files on the internal flash hard-disk. The memory resident registry is periodically (every few seconds) written to the hive files. You can modify the registry in several ways.

• Windows CE provides an API (RegOpenKeyEx or RegQueryValueEx) and a C++ wrapper class (CReg via creg.hxx provided in the QTERM-G56/G58 SDK) for use in applications as a programmatic interface.

• You can run the RegEditCE.exe registry editing application on the QTERM-G56/G58.

• Microsoft Visual Studio 2008 and Microsoft Visual Studio 2005 each come with a suite of remote debugging tools, including remote registry editors. Refer to Chapter 6, “Application Development” for information on setting up a host PC to use these tools.

System Settings File System Filter


4.4 File System Filter

Certain system files included on the internal flash hard-disk are critical to the functioning of the QTERM-G56/G58 terminal. In order to reduce the possibility of accidental deletion or cor-ruption, Beijer Electronics has developed and installed a file system filter, which is a special device driver that prevents write access to a list of files specified in a registry key. The default contents of this registry key are as follows:

[HKEY_LOCAL_MACHINE\System\StorageManager\LockFiles]"Lock"=dword:00000001"Files"=multi_sz:"\\HardDisk\\nk.bin",

"\\HardDisk\\nk_SOS.bin","\\HardDisk\\bin\\boot.bat","\\HardDisk\\bin\\RotateScreen.exe","\\HardDisk\\system.mfs","\\HardDisk\\MFS"

The file system filter can be enabled or disabled by setting or clearing, respectively, the “Lock” registry value. The “Files” multi-string registry value contains the list of locked files and direc-tories. Directories in the list are locked along with all sub-files and subdirectories. Other items may be added to this list by the application programmer.

NOTE ☞ The QTERM-G56/G58 has been provided with a boot recovery image. When booted to the recovery image, you can restore the nk.bin file or other lost files (refer to section 10.2, “System Backup and Recovery” for more details on emergency recovery).

The \HardDisk\bin\LockCE.exe program can be used from a command prompt shell to lock or unlock the files/directories in the list. LockCE 0 unlocks; LockCE 1 locks.

4.5 System Path

The default Windows CE system path on the QTERM-G56/G58 is \Windows;\Hard-Disk\bin;\HardDisk\fonts. Windows will search the \Windows directory first, then the \Hard-Disk\bin directory for executables and supporting dynamically-linked libraries. For example, when explorer.exe is executed from the root directory in the command shell, Windows will find \Windows\explorer.exe.

The system path can be modified via a registry setting. Following is an example of the registry key in which two directories have been added to the default path.

[HKEY_LOCAL_MACHINE\Loader]"SystemPath"=multi_sz:"\\HardDisk\\bin\\",

"\\HardDisk\\fonts\\""\\HardDisk\\Programs\\""\\Temp\\"

Boot-up Configuration System Settings


4.6 Boot-up Configuration

There are two methods of configuring the QTERM-G56/G58 to automatically launch applica-tions or scripts at boot time.

The first method of auto-launching applications is managed by a program called BootUpCE.exe that is launched when Windows CE boots. BootUpCE initiates touch screen calibration (if necessary), then launches a command shell and executes a batch file: \HardDisk\bin\boot.bat. This batch file can be used to launch an application or run a custom boot-up script. For example, to launch WinVerCE after boot, boot.bat should look something like the following:

@echo Launching WinVerCEstart \HardDisk\bin\WinVerCE.exe

Because \HardDisk\bin\boot.bat is on the locked files list (refer to section 4.4, “File System Filter”), it must be unlocked before writing a modified version.

The second and more advanced method of configuring Windows CE to launch one or more applications in a specific order uses the [HKEY_LOCAL_MACHINE\Init] registry key. The following MSDN articles describe this method in detail.

http://msdn.microsoft.com/en-us/library/aa913970.aspxhttp://msdn.microsoft.com/en-us/library/aa448482.aspx

For reference, HKEY_LOCAL_MACHINE\init contains the following default value on the QTERM-G56/G58:

[HKEY_LOCAL_MACHINE\init]"Launch20"="device.dll""Launch30"="gwes.dll""Launch31"="InitRotate.exe""Depend31"=hex:14,00, 1e,00"Depend30"=hex:14,00"Launch32"="explorer.exe""Depend32"=hex:14,00,1e,00"Launch60"="servicesStart.exe""Depend60"=hex:14,00"Launch65"="bootupCE.exe""Depend65"=hex:14,00,1e,00,20,00"Launch70"="RotationCE.exe""Depend70"=hex:14,00, 1e,00,20,00"Launch71"="InitWiFiEnable.exe""Depend71"=hex:40,0

System Settings Applications


As the above registry values illustrate, the Windows CE graphical shell is launched as part of this boot-up procedure (explorer.exe). The “Launch32” registry value can be modified to point to an alternate program in order to launch a custom shell or to run a program without a shell.

4.7 Applications

4.7.1 Microsoft

Microsoft applications that come with the QTERM-G56/G58 include, but are not limited to, the following:

4.7.2 Beijer Electronics

Applications written and provided by Beijer Electronics include the following:

Application Description Path

Windows Explorer Standard graphical shell \Windows\explorer.exe

Command Prompt Command-line shell \Windows\cmd.exe

Media Player1

1. Included in professional license Windows Embedded CE versions only.

Video and audio decoder/player \Windows\ceplayer.exe

Internet Explorer1 Web browser \Windows\iesample.exe

ActiveSyncHost PC synchronization and communi-cation server

\Windwos\repllog.exe

Control Panel Device configuration utilities \Windows\ctlpnl.exe

Windows CE Load CAB file installer \Windows\wceload.exe


CleanHiveCECauses the persistent registry to revert to factory defaults. Reboot QTERM-G56/G58 after executing.

\HardDisk\bin\CleanHiveCE.exe

LockCE

Locks/unlocks protected files (refer to section 4.4, “File System Filter”). Single command line parameter either 0 (unlock) or 1 (lock).

\HardDisk\bin\LockCE.exe

MinTermCE Serial port console and test program. \HardDisk\bin\MinTermCE.exe

PolygonsCE Display test program. \HardDisk\bin\PolygonsCE.exe

QeditCE Small, simple graphical editor \HardDisk\bin\QeditCE.exe

Applications System Settings


RegEditCELocal registry editor tool (similar to Remote Registry Editor).

\HardDisk\bin\RegEditCE.exe

SleepCE

Causes a delay of N milliseconds for the calling batch file where the number N is passed to the program as a command line parameter.

\HardDisk\bin\SleepCE.exe

QTermDemo

Application written to demonstrate QTERM-G56/G58 functionality and fea-tures. Source code provided for this appli-cation upon request to demonstrate application development for the QTERM-G56/G58, including custom device driver interfaces.

\HardDisk\QTermDemo\QTermDemo.exe

QTermPanelCE Refer to section 4.2, “QTERM Panel.” \HardDisk\bin\QTermPanelCE.exe

WinVerCE Displays the current version of the Win-dows CE kernel, firmware, and release date.

\HardDisk\bin\WinVerCE.exe

WaitForAPIsCE [WinCE API enum value or values]

Causes the calling process to delay execu-tion until the specified Windows CE appli-cation programming interfaces are ready, e.g., SH_SHELL(21) and SH_WMGR(17). Multiple APIs may be specified, separated by spaces.

\HardDisk\bin\WaitForAPIsCE.exe

WaveRecCE.exeRecords 5 seconds of audio from the default wave device and saves it to the file 1.wav in the MyDevice folder.

\HardDisk\bin\WaveRecCE.exe

RecSndCE.exeRecords 5 seconds of audio from the selected wave device and then plays it back to another selected wave device.

\HardDisk\bin\ RecSndCE.exe



CHAPTER 5

CONNECT TO A PC VIA ACTIVESYNC

5.1 Introduction

You can use Microsoft ActiveSync to communicate directly between the QTERM-G56/G58 and a PC computer. To set up an ActiveSync connection between your QTERM-G56/G58 and a PC computer, do the following:

Connect the USB cable between the QTERM-G56/G58 and the PC (see section 5.2, “Con-nect the USB Cable”).

Load ActiveSync on the PC to which the QTERM-G56/G58 will be connected (see section 5.3, “Download/Install ActiveSync”).

Start ActiveSync on the PC and on the QTERM-G56/G58 (see section 5.4, “Connect the PC and QTERM-G56/G58”).

5.2 Connect the USB Cable

Connect one end of the USB cable (included in the Developer’s Kit) to the USB port on the QTERM-G56/G58 and the other end to a USB port on the PC. For best results the cable should not exceed six feet in length.

5.3 Download/Install ActiveSync

Download ActiveSync from the Microsoft website and install it on your PC as follows.

1. On your PC, open your Web browser, and navigate to the Microsoft Download Center at http://www.microsoft.com/downloads/Search.aspx?displaylang=en.

2. Type ActiveSync in the search box and begin the search.

3. ActiveSync 4.2 and 4.5 are the two latest versions as of January 2010. Both will work with the QTERM-G56/G58. Follow the appropriate link and download the desired version.

4. Install ActiveSync on your PC by executing the downloaded installer file or executable and following the instructions.

5. When the installation is finished, ActiveSync automatically launches the “Get Connected” wizard that will search the PC’s USB ports for a connection. If you are not ready to con-nect to the QTERM-G56/G58, cancel this option.

Connect the PC and QTERM-G56/G58 Connect to a PC Via ActiveSync


5.4 Connect the PC and QTERM-G56/G58

With the cable connected and ActiveSync installed on your PC (see section 5.3, “Down-load/Install ActiveSync”), do the following to establish a connection between the PC and the QTERM-G56/G58.

1. On the QTERM-G56/G58, open the control panel (Start, Settings, Control Panel). Open the PC Connection control applet. Select the “Enable direct connections to the desktop computer” checkbox to enable the ActiveSync connections on the terminal.

NOTE ☞ The “Enable direct connections to the desktop computer” setting remains persistent across power cycles and will not need to be changed each time you use ActiveSync.

2. On your PC, start ActiveSync.

3. Open the File menu, and select Get Connected, or select Connection Settings and then click [Connect].

4. Click [Next]. The QTERM-G56/G58 automatically responds to the PC’s ActiveSync con-nection request. (See Figure 24.)

When the “Connecting to Host” message appears on the QTERM-G56/G58, the Active-Sync window on the PC displays “Connecting.....”

5. When the ActiveSync connection is established, the PC displays a window titled “New Partnership” (see Figure 25). Typically, you should select No and then click [Next].

Figure 24ActiveSync, Get Connected

Connect to a PC Via ActiveSync Connect the PC and QTERM-G56/G58


The ActiveSync window then displays “Connected” (see Figure 26).

6. You can now browse the QTERM-G56/G58 file system by selecting the Explore icon or the Explore option on the PC’s ActiveSync File menu (see Figure 27).

Figure 25ActiveSync Partnership

Figure 26ActiveSync, Connected

Connect the PC and QTERM-G56/G58 Connect to a PC Via ActiveSync


Figure 27ActiveSync, Explore Device


CHAPTER 6

APPLICATION DEVELOPMENT

6.1 Introduction

This chapter describes the process of developing and debugging applications for the QTERM-G56/G58 and assumes familiarity with the C programming language and Windows application remote debugging procedures. (If necessary, consult the Microsoft MSDN library for a refresher on remote debugging.) This information is intended for integrators and applica-tion developers as a guide in setting up the QTERM-G56/G58 for application development and as a reference for programmatic interfaces (API) to software drivers for various terminal peripherals.

The QTERM-G56/G58 is a Windows CE-based computer with specialized hardware peripher-als that make it suitable for industrial applications. Application development and debugging procedures for the QTERM-G56/G58, as well as the software driver API, are similar to other Windows CE-based devices. This chapter provides instructions and references for QTERM-G56/G58-specific functionality, not for standard interfaces. For example, the QTERM-G56/G58 has a serial port, but the serial port driver interface is not documented in this manual because the interface is a standard, well-known API.

6.1.1 Glossary

APIApplication Program Interface

SDKSoftware Development Kit

IDEIntegrated Development Environment

6.1.2 Related Documents

• Microsoft Visual Studio 2005 MSDN Library

• Microsoft Visual Studio 2008 MSDN Library

• Windows Embedded CE 6.0 Documentationhttp://msdn.microsoft.com/en-us/library/bb159115.aspx

• Shared Windows Mobile 6 and Windows Embedded CE 6.0 Libraryhttp://msdn.microsoft.com/en-us/library/bb158484.aspx

Setup Application Development


6.2 Setup

6.2.1 Prerequisites

The following are required before setting up the QTERM-G56/G58 for application develop-ment. Either an Ethernet or USB connection is required (both are included here for complete-ness).

Ethernet connection:The host can communicate with the QTERM-G56/G58 during a remote debugging session over an Ethernet network. The QTERM-G56/G58 should be connected to the same network and on the same subnet as the host.

The network can be established using the internal 10/100 Ethernet adapter. Use the DM9CE1 connectoid to configure the internal Ethernet connection (refer to section 4.1.6, “Network and Dial-up Connections”). Use the Windows CE Wireless Zero Configuration tool to configure the wireless Ethernet connection (refer to section 7.1, “Wireless Ethernet”).

USB connection:The host can communicate with the QTERM-G56/G58 during a remote debugging session via ActiveSync over a USB connection. The QTERM-G56/G58 Developer’s Kit includes a USB cable that can be used for the ActiveSync connection.

Software Development Kit:The SDK is an MSI installable file distributed by Beijer Electronics. The SDK should be installed so that the host IDE knows how to connect to the QTERM-G56/G58. The SDK also provides headers and libraries that correspond to the available services and features included in the QTERM-G56/G58 Windows CE image.

Integrated Development Environment:Microsoft Visual Studio 2005 and/or Microsoft Visual Studio 2008 should be installed as a development environment for the QTERM-G56/G58 application. These programs are used to compile and remotely debug the application.The latest service packs and updates for these Microsoft programs must be installed.

6.2.2 SDK Installation

The latest Software Development Kit is available from the Beijer Electronics website (http://www.beijerelectronicsinc.com). The SDK and Windows CE image release dates should match to ensure that all features and services in the image correspond to those offered in the SDK. Use the latest available SDK version if the release date of the most recent Windows CE image supersedes that of the SDK.

To install the SDK on your PC host, download the .msi file from the Beijer Electronics web-site, right-click the file name, and select Install. After the installation is complete, verify that

Application Development Setup


“QTERM-G56/G58” appears in the Tools, Connect to Device dialog box in Microsoft Visual Studio 2005 and Microsoft Visual Studio 2008.

6.2.3 Target Setup

6.2.3.1 ActiveSync

You can use the ActiveSync protocol to establish a remote debugging connection with the Inte-grated Development Environment. Refer to Chapter 5, “Connect to a PC Via ActiveSync” for ActiveSync setup instructions.

6.2.3.2 Manual Server

If you do not use ActiveSync, you must set up a manual Ethernet client server on the QTERM-G56/G58. You must configure this server to respond to debug or download connec-tion requests from the host PC's IDE. ActiveSync has the advantage of easier setup because the IP address of the target is negotiated automatically; however, it also uses a slower connection over the USB port.

At a QTERM-G56/G58 command prompt window, navigate to \HardDisk\bin\client. Instruc-tions for using conmanclient2.exe and cmaccept.exe can be found online at http://msdn2.microsoft.com/en-us/library/ms228708(VS.80).aspx. These instructions apply to both Microsoft Visual Studio 2005 and Microsoft Visual Studio 2008.

6.2.4 Microsoft Visual Studio 2005/2008

Take the following steps to configure Visual Studio to connect with the QTERM-G56/G58 tar-get. (Refer to Figure 28.)

1. From the Visual Studio Tools menu, select Options, Device Tools, Devices.

2. Select G5x from the “Show devices for platform” drop-down box. “G5x ARMV4I Device” should be the only device listed in the “Devices” box.

3. Select Properties.

4. From the “Default output location on device” drop-down box, select the desired location for deploying the Visual Studio project executables and libraries. Select Root folder if you want to download to \HardDisk. The path to the directory in the root location is specified in the Visual Studio Project Properties dialog box.

5. Click [Configure].

6. If using ActiveSync, select Obtain an IP address automatically using ActiveSync.



If using the ConMan Ethernet client (manual server), select Use specific IP address, and type in the IP address of the QTERM-G56/G58. Detailed instructions are available online at http://msdn2.microsoft.com/en-us/library/ms228708(VS.80).aspx.

Figure 28QTERM-G56/G58 Device Connection with Visual Studio



7. Verify the device connection. From the Tools menu, select Connect to Device. Refer to Figure 29.

8. Make sure the selected platform is “G5x,” and the device is “G5x ARMV4I Device.”

The status bar at the bottom of the Visual Studio workspace window should indicate a success-ful connection.

You can use Visual Studio to construct sample native and managed applications to test the Build, Deploy, and Debug process. Take the following steps.

6.2.4.1 Native

1. From the Visual Studio File menu, select New Project.

2. Select Visual C++, Smart Device, and MFC Smart Device Application in the window on the right.

3. Select a directory for the project, and click [OK].

4. Click [Next]. Move the “G5x” to the “Selected SDKs” column. It should be the only selected SDK (move any others to the left).

5. Continue to configure the application with the next few dialog boxes as desired.

6. Enable the Device toolbar from the View, Toolbars menu.

Figure 29Visual Studio, Connect to QTERM-G56/G58 Device



7. Make sure that the “Target Device” drop-down list shows “G5x ARMV4I Device.” If not, click [Device Options] (next to the drop-down list), and select G5x from the “Show devices for platform” drop-down list.

8. Right-click the project from the Solution Explorer window, and select Properties to bring up the Property Pages for the project.

9. In Configuration Properties, Debugging and Deployment, set the Remote Executable and Remote Directory parameters, respectively (see Figure 30). These parameters determine the path in the QTERM-G56/G58 file system where the executable will be deployed and executed.

Figure 30Visual Studio, Native Project Properties



6.2.4.2 Managed

The QTERM-G56/G58 comes with the .NET Compact Framework v3.5 pre-installed. Most applications targeting the .NET Compact Framework v2.0 are compatible with v3.5.

Visual Studio 2005 will deploy, install, and debug with the .NET Compact Framework v2.0 by default, if “Deploy the latest version of the .NET Compact Framework” is checked (see Figure 31). Uncheck this box to debug with the preinstalled version (v3.5). Visual Studio 2005 does not have an option to deploy and install v3.5.

Visual Studio 2008 offers a selection between v2.0 and v3.5 at the time of project creation (refer to step 2 below). If “Deploy the latest version of the .NET Compact Framework” is checked (see Figure 31), Visual Studio will deploy, install, and debug with the selected ver-sion.

1. From the Visual Studio File menu, select New Project.

2. In Visual Studio 2005, select Other Languages, Visual C#, Smart Device, Windows CE 5.0, and Device Application in the window on the right.

In Visual Studio 2008, select Visual C#, Smart Device, and Smart Device Project in the window on the right. In the “Add New Smart Device Project” dialog box, select Windows CE as the target platform, the desired .NET Compact Framework version (v3.5 is installed by default on the QTERM-G56/G58), and Device Application from Templates.

3. Select a directory for the project, and click [OK].

4. Enable the Device toolbar from the View, Toolbars menu.

5. Make sure that the “Target Device” drop-down list shows “G5x ARMV4I Device.” If not, click [Device Options] (next to the drop-down list), and select G5x from the “Show devices for platform” drop-down list.

6. Right-click the project from the Solution Explorer window, and select Properties to bring up the Property Pages for the project.

7. In Devices, select G5x ARMV4I Device from the Target device drop-down list.

8. In Devices, select the desired Output file folder (see Figure 31). This parameter determines the path in the QTERM-G56/G58 file system where the executable will be deployed and executed.



6.2.5 Remote Tools

Microsoft provides several remote tools with the Visual Studio 2005 and Visual Studio 2008 installation, such as Remote Registry Editor and Remote Zoom In (for screen capture). These tools work over an established remote debugging connection. Follow the procedures outlined in sections 6.2.1 through 6.2.3 to set up this connection.

Note that there may be a delay the first time a remote tool requests to connect to the QTERM-G56/G58 target. The platform manager framework copies required libraries and exe-

Figure 31Visual Studio, Managed Project Properties

Application Development Software Drivers


cutables for running the remote tool during this time. Subsequent connection requests will not have this delay unless the QTERM-G56/G58 has been rebooted since the last request.

Refer to the following MSDN links for additional information about the Microsoft remote tools: http://msdn.microsoft.com/en-us/library/aa935548.aspxhttp://msdn.microsoft.com/en-us/library/aa935675.aspx

6.3 Software Drivers

Software access and control of specialized hardware peripherals on the QTERM-G56/G58 are provided through device driver and registry interfaces. These interfaces utilize the standard Windows stream driver API (e.g., CreateFile, WriteFile, ReadFile, and DeviceIoControl) and registry access API (RegOpenKeyEx, RegQueryValueEx, etc.). Most QTERM-G56/G58 peripherals do not fit the typical model for stream devices that transfer large amounts of data, thus the traditional operations like read and write are not supported. The primary access and control mechanism is the DeviceIoControl function, which provides flexibility via custom IOCTL codes. Refer to Microsoft documentation for a detailed description of the driver and registry API functions.

The following sections outline the behavior, supported IOCTL codes, and registry keys/values for each peripheral.

IOCTL codes are described in the form of sample C code and in-line comments. The inputs and outputs of each IOCTL are described. Sample calls are provided to illustrate proper usage for each IOCTL. IOCTL defines and enumeration values for input and output parameters to the DeviceIoControl function are described in the file QTermPublic.h that is included in the software development kit distribution (\Program Files\Windows CE Tools\wce600\G5x\ Include\Armv4i\QTermPublic.h). For example, the keypad button key defines are listed in this header file. The sample code below references QTermPublic.h as appropriate.

Registry keys/values are listed in a standard [key] “value” format. These keys/values may be queried or set programmatically via the registry access API or by using a utility program like RegEditCE.exe (refer to section 4.7.2, “Beijer Electronics” on page 41).

NOTE ☞ The code in the following sections is included “as is” for illustration purposes only. It is rec-ommended that the application developer check the return value for success or failure of device driver API calls.

6.3.1 Keypad

The keypad driver initiates scans of keys and reports presses to the GWES (graphical, window, and events) Windows CE subsystem.

Auto-repeat is supported, including variable initial delay and repeat rate. These parameters apply globally to all keys in the built-in keypad and to any externally connected USB keyboard

Software Drivers Application Development


and can be set via keypad driver DeviceIoControl calls or via the Keyboard control panel applet (refer to section 4.1.3, “Keyboard” on page 30).

Each key can be individually assigned a virtual key code. Supported virtual key codes include all Windows CE standard supported codes (defined in winuser.h, found in the QTERM-G56/G58 SDK distribution located at \Program Files\Windows CE Tools\wce600\G5x\Include\Armv4i). Independent control of a press vs. a release key code is not supported; all actions occur on a press (as opposed to a key release). Refer to section 3.3, “Function Keys” for default key mappings.

API, described via code examples:HANDLE hDevice;hDevice = CreateFile(TEXT("KEY1:"), GENERIC_READ, 0, NULL, OPEN_EXISTING, 0, NULL);

// set cursor key acceleration// applies only when mouse cursor key codes are usedint accel = 5; // 0 to QTERM_KEY_MAX_ACCEL, defined in QTermGLPublic.hDeviceIoControl(hDevice, IOCTL_KEYPAD_SET_ACCEL, &accel, sizeof(accel), NULL, 0, NULL, NULL);// get cursor key accelerationDeviceIoControl(hDevice, IOCTL_KEYPAD_GET_ACCEL, NULL, 0, &accel, sizeof(accel), NULL, NULL);

// set auto repeat delay and rate (global)#include <keybd.h> // from SDK, for struct defn// all int32 struct members, only first 2 matter// delay is in ms// repeat rate is in keys/secKBDI_AUTOREPEAT_INFO ai = { delay, repeatRate, 0, 0 };DeviceIoControl(hDevice, IOCTL_KBD_SET_AUTOREPEAT, &ai, sizeof(ai), NULL, 0, NULL, NULL);

CloseHandle(hDevice);

6.3.1.1 Default Registry Setting for 24-Key Keypad

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\KEYPAD\TYPE24]"RowNum"=dword:6"ColumnMask"=dword:F;only last 4 bits for columns"ShiftKeyIndex"=dword:a;the location in the key list and bitmap"PowerKeyIndex"=dword:b

; layout of G58 24 keys pad:; row 0:key12 key13 key14 key15; row 1:key16 key17 key18 key19; row 2:key20 key01 key02 key03; row 5:key21 key04 key05 key06; row 4:key10 key07 key08 key09; row 3:key11 key22 key00 key23;; default using Windows XP/2000 english keyboard layout; when shift key is pressed, find the base key; refer to winuser.h for standard set.; 0x100xx means it is requires inverted shift key, eg. 1BB means +, but has; to invert shift key; 0x2aabb means it is combination of two keys aa and bb



; 0x3aabb means it is combination of two keys aa and bb, and invert shift; key

"KEY0"=dword:30;<0>row 30x02"KEY0_Shift"=dword:36;<^>value when shift key is pressed"KEY1"=dword:31;<1>row20x04"KEY1_Shift"=dword:32625;<UP+LEFT>"KEY2"=dword:32 ;<2>row 20x02"KEY2_Shift"=dword:10026;<UP>"KEY3"=dword:33;<3>row 20x01"KEY3_Shift"=dword:32627;<UP+RIGHT>"KEY4"=dword:34;<4>row 50x04"KEY4_Shift"=dword:10025;<LEFT>"KEY5"=dword:35;<5>row 50x02"KEY5_Shift"=dword:35;<%>"KEY6"=dword:36 ;<6>row 50x01"KEY6_Shift"=dword:10027;<RIGHT>"KEY7"=dword:37;<7>row 40x04"KEY7_Shift"=dword:32825 ;<DOWN+LEFT>"KEY8"=dword:38;<8>row 40x02"KEY8_Shift"=dword:10028;<DOWN>"KEY9"=dword:39;<9>row 40x01"KEY9_Shift"=dword:32827 ;<DOWN+RIGHT>"KEY10"=dword:10 ;<SHIFT>"KEY10_Shift"=dword:10;<SHIFT>"KEY11"=dword:DF;<POWER>"KEY11_Shift"=dword:DF;<POWER>"KEY12"=dword:70;<F1>row 00x08"KEY12_Shift"=dword:70;<F1>"KEY13"=dword:71;<F2>row 00x04"KEY13_Shift"=dword:71;<F2>"KEY14"=dword:72;<F3>row 00x02"KEY14_Shift"=dword:72;<F3>"KEY15"=dword:73;<F4>row 00x01"KEY15_Shift"=dword:73;<F4>"KEY16"=dword:100BB;<+>row 10x08"KEY16_Shift"=dword:39;<(>"KEY17"=dword:BD;<->row10x04"KEY17_Shift"=dword:30;<)>"KEY18"=dword:6A;<*>row 10x02"KEY18_Shift"=dword:BC;<<>"KEY19"=dword:BF;</>row 10x01"KEY19_Shift"=dword:BE;<>>"KEY20"=dword:BE;<.>row 20x08"KEY20_Shift"=dword:100DE;<'>"KEY21"=dword:BB;<=>row 50x08"KEY21_Shift"=dword:33;<#>"KEY22"=dword:1B;<ESC>row 30x04"KEY22_Shift"=dword:1002E;<DELETE>"KEY23"=dword:0D;<ENTER>row 30x01"KEY23_Shift"=dword:20;<SPACE>



Figure 32 shows key number mapping for the 24-key keypad.

Changes to these registry settings take effect only after a reboot.

6.3.1.2 Default Registry Setting for 40-Key Keypad

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\KEYPAD\TYPE40]"RowNum"=dword:8"ColumnMask"=dword:1F;only last 5 bits for columns"ShiftKeyIndex"=dword:a;the location in the key list and bitmap"PowerKeyIndex"=dword:b

; layout of G58 40 keys pad:; row 0:key12 key13 key14 key15 key16; row 1:key17 key18 key19 key20 key21; row 2:key24 key25 key26 key27 key28; row 5:key29 key30 key31 key32 key33; row 4:key34 key35 key01 key02 key03; row 3:key36 key37 key04 key05 key06; row 6:key10 key38 key07 key08 key09; row 7:key11 key39 key22 key00 key23;; default using Windows XP/2000 english keyboard layout; when shift key is pressed, find the base key; refer to winuser.h for standard set.; 0x100xx means it is requires inverted shift key, eg. 1BB means +, but has: to invert shift key; 0x2aabb means it is combination of two keys aa and bb; 0x3aabb means it is combination of two keys aa and bb, and invert shift; key

"KEY0"=dword:30;<0>row 40x02"KEY0_Shift"=dword:10030;<0>value when shift key is pressed"KEY1"=dword:31;<1>row50x04"KEY1_Shift"=dword:10031;<1>"KEY2"=dword:32 ;<2>row 50x02"KEY2_Shift"=dword:10032;<2>"KEY3"=dword:33;<3>row 50x01"KEY3_Shift"=dword:10033;<3>

Figure 32Key Number Mapping, 24-Key Keypad



"KEY4"=dword:34;<4>row 20x04"KEY4_Shift"=dword:10034;<4>"KEY5"=dword:35;<5>row 20x02"KEY5_Shift"=dword:10035;<5>"KEY6"=dword:36 ;<6>row 20x01"KEY6_Shift"=dword:10036;<6>"KEY7"=dword:37;<7>row 30x04"KEY7_Shift"=dword:10037;<7>"KEY8"=dword:38;<8>row 30x02"KEY8_Shift"=dword:10038;<8>"KEY9"=dword:39;<9>row 30x01"KEY9_Shift"=dword:10039;<9>"KEY10"=dword:10 ;<SHIFT>"KEY10_Shift"=dword:10;<SHIFT>"KEY11"=dword:DF;<POWER>"KEY11_Shift"=dword:DF;<POWER>"KEY12"=dword:70;<F1>row 70x10"KEY12_Shift"=dword:41;<A>"KEY13"=dword:71;<F2>row 70x08"KEY13_Shift"=dword:42;<B>"KEY14"=dword:72;<F3>row 70x04"KEY14_Shift"=dword:43;<C>"KEY15"=dword:73;<F4>row 70x02"KEY15_Shift"=dword:44;<D>"KEY16"=dword:74;<F5>row 70x01"KEY16_Shift"=dword:45;<E>"KEY17"=dword:10037;<&>row00x10"KEY17_Shift"=dword:46;<F>"KEY18"=dword:10035;<%>row 00x08"KEY18_Shift"=dword:47;<G>"KEY19"=dword:22625;<up+left>row 00x04"KEY19_Shift"=dword:48;<H>"KEY20"=dword:26;<up>row 00x02"KEY20_Shift"=dword:49;<I>"KEY21"=dword:22627;<up+right>row 00x01"KEY21_Shift"=dword:4a;<J>"KEY22"=dword:1b;<ESC>row 30x04"KEY22_Shift"=dword:1002E;<DELETE>"KEY23"=dword:0d;<ENTER>row 30x01"KEY23_Shift"=dword:20;<SPACE>"KEY24"=dword:10039;<(>row 60x10"KEY24_Shift"=dword:4b;<K>"KEY25"=dword:10030;<)>row60x08"KEY25_Shift"=dword:4c;<L>"KEY26"=dword:25;<left>row 60x04"KEY26_Shift"=dword:4d;<M>"KEY27"=dword:10032;<@>row 60x02"KEY27_Shift"=dword:4e;<N>"KEY28"=dword:27;<right>row 60x01"KEY28_Shift"=dword:4f;<O>"KEY29"=dword:10033;<#>row 10x10"KEY29_Shift"=dword:50;<P>"KEY30"=dword:100bf;<?>row 10x08"KEY30_Shift"=dword:51;<Q>"KEY31"=dword:22825;<down+left>row 10x04"KEY31_Shift"=dword:52;<R>



"KEY32"=dword:28;<down>row 10x02"KEY32_Shift"=dword:53;<S>"KEY33"=dword:22827;<down+right>row10x01"KEY33_Shift"=dword:54;<T>"KEY34"=dword:bf;</>row 50x10"KEY34_Shift"=dword:55;<U>"KEY35"=dword:10038;<*>row 50x08"KEY35_Shift"=dword:56;<V>"KEY36"=dword:100BB;<+>row 20x08"KEY36_Shift"=dword:57;<W>"KEY37"=dword:BD;<->row 50x08"KEY37_Shift"=dword:58;<X>"KEY38"=dword:100DE;<'>row 30x04"KEY38_Shift"=dword:59;<Y>"KEY39"=dword:be;<.>row 30x01"KEY39_Shift"=dword:5a;<Z>

Figure 32 shows key number mapping for the 40-key keypad.


6.3.2 Backlight

The backlight driver is responsible for enabling/disabling the display and setting the intensity levels of the display. The user may control these operations programmatically or via a user interface.

The QTERMPanelCE application also includes Increase/Decrease buttons for this setting (refer to section 4.2, “QTERM Panel”).

The Windows CE power manager contains timers that can be used to enable power-down and/or power-off modes for the display and keypad backlight after a specified time has elapsed. The power-down and power-off modes correspond to User Idle and System Idle sys-tem power states. Set timers for User Idle and System Idle state transitions via driver Device-IoControl calls, the QTERM Panel application (refer to section 4.2.4, “Power” for more

Figure 33Key Number Mapping, 40-Key Keypad



information on QTERM Panel power state controls), or registry values. Set the power state timer values to 0 to disable transition to User Idle and/or System Idle states. Disabling transi-tion to User Idle also prevents transition to System Idle. To retain the System Idle transition, set the User Idle timer to one second. The state transition timers are cumulative; the System Idle transition will occur only after both the User Idle and System Idle timers expire.

A transition to User Idle causes both the display and keypad backlights to dim to the specified intensity. This intensity level can be set via a DeviceIoControl call. Any user activity will cause the power manager to transition out of User Idle to a full on state, and thus restore the prior backlight intensity levels. Examples of user activity are pressing the touch screen or key-pad, or using a USB mouse or keyboard (specifically, when the event defined in the [HKLM\System\GWE\ActivityEvent] registry key is signaled).

A transition to System Idle causes the display backlight, keypad backlight, and the LCD dis-play to be disabled. Any user activity will cause the power manager to transition out of System Idle to a full on state, and thus restore the prior backlight intensity levels.

The backlight driver is responsible for enabling/disabling the display and setting the intensity level of the display backlight. The user may control these operations programmatically or via a user interface.

The intensity of the display backlight and keypad enable/disable can be independently con-trolled via driver DeviceIo-Control calls. The QTERM Panel application also includes controls for these settings (refer to section 4.2, “QTERM Panel”).

The Windows CE power manager contains timers that can be used to enable power-down and/or power-off modes for the display and keypad backlight after a specified time has elapsed. The power-down and power-off modes correspond to User Idle and System Idle sys-tem power states. Set timers for User Idle and System Idle state transitions via driver Device-IoControl calls, the QTERM Panel application (refer to section 4.2.4, “Power” for more information on QTERM Panel power state controls), or registry values. Set the power state timer values to 0 to disable transition to User Idle and/or System Idle states. Disabling the tran-sition to User Idle also prevents transition to System Idle. To retain the System Idle transition, set the User Idle timer to one second. The state transition timers are cumulative; the System Idle transition will occur only after both the User Idle and System Idle timers expire.

A transition to User Idle causes both the display and keypad backlights to dim to the specified intensity. This intensity level can be set via a DeviceIoControl call. Any user activity will cause the power manager to transition out of User Idle to a full on state and thus restore the prior backlight intensity levels. Examples of user activity are pressing the touch screen or key-pad (specifically, when the event defined in the [HKLM\System\GWE\ActivityEvent] registry key is signaled).

A transition to System Idle causes the display backlight, keypad backlight, and the LCD dis-play to be disabled. Any user activity will cause the power manager to transition out of System Idle to a full on state and thus restore the prior backlight intensity levels. Note that although the device driver allows for an intensity setting in the range of 0 to 100 for the keypad back-



light, it is an “on or off” device so a setting greater than or equal to 50 will turn the keypad backlight on, and a value less than 50 will turn it off.

API, described via code examples:HANDLE hDevice;hDevice = CreateFile(TEXT("BLT1:"), GENERIC_READ, 0, NULL, OPEN_EXISTING, 0, NULL);// set/get backlight intensityint intensity = 80; // 0 to 100%DeviceIoControl(hDevice, IOCTL_BACKLIGHT_SET_INTENSITY, &intensity, sizeof(intensity), NULL, 0, NULL, NULL);DeviceIoControl(hDevice, IOCTL_BACKLIGHT_GET_INTENSITY, NULL, 0, &intensity, sizeof(intensity), NULL, NULL);// set/get keypad backlight intensityintensity = 0; // 0 to 100% -- value > 50, keypad backlight is on, value < 50, keypad backlight will be off

DeviceIoControl(hDevice, IOCTL_BACKLIGHT_KEYPAD_SET_INTENSITY, &intensity, sizeof(intensity), NULL, 0, NULL, NULL);DeviceIoControl(hDevice, IOCTL_BACKLIGHT_KEYPAD_GET_INTENSITY, NULL, 0, &intensity, sizeof(intensity), NULL, NULL);

// set/get keypad AND display backlight power-down intensityintensity = 15; // 0 to 100%DeviceIoControl(hDevice, IOCTL_BACKLIGHT_POWERDOWN_SET_INTENSITY, &intensity, sizeof(intensity), NULL, 0, NULL, NULL);DeviceIoControl(hDevice, IOCTL_BACKLIGHT_POWERDOWN_GET_INTENSITY, NULL, 0, &intensity, sizeof(intensity), NULL, NULL);

// set or get the backlight power down or power off timeout valueint pwrTime; // seconds// set power down (User Idle transition timer)DeviceIoControl(hDevice, IOCTL_BACKLIGHT_SET_POWERDOWN, &pwrTime, sizeof(pwrTime), NULL, 0, NULL, NULL);DeviceIoControl(hDevice, IOCTL_BACKLIGHT_GET_POWERDOWN, NULL, 0, &pwrTime, sizeof(pwrTime), NULL, NULL);// set power off (System Idle transition timer)DeviceIoControl(hDevice, IOCTL_BACKLIGHT_SET_POWEROFF, &pwrTime, sizeof(pwrTime), NULL, 0, NULL, NULL);DeviceIoControl(hDevice, IOCTL_BACKLIGHT_GET_POWEROFF, NULL, 0, &pwrTime, sizeof(pwrTime), NULL, NULL);

CloseHandle(hDevice);

Example registry settings:Following are the defaults for the prototype unit.

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Backlight] "BacklightIntensity"=dword:00000064 ; 100% "BacklightKeypadIntensity"=dword:00000064 ; 100% "BacklightPowerDownIntensity"=dword:2 ; 2% ; used for UserIdle

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Power\Timeouts] "ACUserIdle"=dword:3C ; sec from last user activity 0x3c=60s "ACSystemIdle"=dword:12C ; sec from start of UserIdle 0x12c=300s=5min




6.3.2.1 Keypad LEDs

Included with the QTERM-G56/G58 are up to seven controllable LEDs, with the number determined by whether the terminal has a 24-key or 40-key keypad. There are two state LEDs that can either be on or off. Settings you can access using “DeviceIoControl” have been included in the operating system for controlling these LEDs programmatically.

Example Code (C#):using System;using System.IO;using System.Runtime.InteropServices;

namespace SmartDeviceProject2{ class LEDControl { //registry setting will need to be modified for shift and power leds to work

private const int NUM_LEDS = 7;

[DllImport("coredll.dll", CallingConvention = CallingConvention.Winapi, CharSet = CharSet.Auto, EntryPoint = "KernelIoControl", PreserveSig = true, SetLastError = true)]

public static extern Boolean KernelIoControl(UInt32 dwIoControlCode, UIntPtr lpInBuf, UInt32 nInBufSize, UIntPtr lpOutBuf, UInt32 nOutBufSize, UIntPtr lpBytesReturned);

[DllImport("coredll.dll")] public static extern UIntPtr CreateFile(string filename, FileAccess fileaccess, FileShare fileshare, int security, FileMode fm, int flags, UIntPtr template);

[DllImport("coredll.dll")] public static extern Boolean DeviceIoControl(UIntPtr device, int ioreq, UInt32[] invar, int invarsize, UInt32[] outvar, int outvarsize, UInt32[] bytes_returned, Boolean overlapped);

[DllImport("coredll.dll")] public static extern UInt32 GetLastError(); private static Int32 FILE_DEVICE_KEYPAD = 0x9001; private static Int32 FUNCTION_KEYPAD_SET_LED = 0x827; private static Int32 FUNCTION_KEYPAD_GET_LED = 0x828; private static Int32 FILE_ANY_ACCESS = 0x0; private static Int32 METHOD_BUFFERED = 0x0; private static UIntPtr INVALID_HANDLE_VALUE = (UIntPtr)(0xffffffff);

private static Int32 IOCTL_KEYPAD_SET_LED = ((FILE_DEVICE_KEYPAD) << 16) | ((FILE_ANY_ACCESS) << 14) | (FUNCTION_KEYPAD_SET_LED << 2) | ((METHOD_BUFFERED));

private static Int32 IOCTL_KEYPAD_GET_LED = ((FILE_DEVICE_KEYPAD) << 16) | ((FILE_ANY_ACCESS) << 14) | (FUNCTION_KEYPAD_GET_LED << 2) | ((METHOD_BUFFERED));



private UIntPtr hKeypad;

public LEDControl() { hKeypad = CreateFile("KBD1:", FileAccess.Read, FileShare.None, 0, FileMode.Open, 0, UIntPtr.Zero);

if ((null == hKeypad) || (INVALID_HANDLE_VALUE == hKeypad)) { System.Windows.Forms.MessageBox.Show("Couldn't open Keypad driver");

throw (new Exception("Unable to Create Keypad Handle")); } }

public bool SetLED(int ledNumber, bool state) { if (ledNumber < 0 || ledNumber >= NUM_LEDS) { return false; } UInt32 ledStates = ReadLEDStates(); UInt32 ledState = (UInt32)(1 << ledNumber); if (state) { ledStates = ledState | ledStates; } else { if ((ledState & ledStates) > 0) { ledStates = ledStates ^ ledState; } } WriteLEDStates(ledStates); return true; }

public bool GetLED(int ledNumber, ref bool state) { if (ledNumber < 0 || ledNumber >= NUM_LEDS) { return false; } UInt32 ledStates = ReadLEDStates(); UInt32 ledState = (UInt32)(1 << ledNumber); if ((ledStates & ledState) > 0) { state = true; } else { state = false; } return true; }

private UInt32 ReadLEDStates() { UInt32[] ledOut = new UInt32[1]; if (!DeviceIoControl(hKeypad, IOCTL_KEYPAD_GET_LED, null, 0, ledOut, 4, null, false))



{ System.Windows.Forms.MessageBox.Show(String.Format("DeviceIoControl(IOCTL_KEYPAD_GET_LED) failed, GetLastError={0}

throw (new Exception("Unable to Read LEDs")); } return ledOut[0]; }

private void WriteLEDStates(UInt32 ledStates) { UInt32[] ledIn = new UInt32[1]; ledIn[0] = ledStates; if (!DeviceIoControl(hKeypad, IOCTL_KEYPAD_SET_LED, ledIn, 4, null, 0, null, false)) {

System.Windows.Forms.MessageBox.Show(String.Format("DeviceIoControl(IOCTL_KEYPAD_SET_LED) failed, GetLastError={0}

throw (new Exception("Unable to Write LEDs")); } } }}

6.3.2.1.1 Setting the Shift and Power LEDS

To change the state of the shift or power LEDs, the registry setting “LEDusrMask” (DWord) in [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\KEYPAD] must be set to 0xFF. Set the value to 0x1F (default) to be able to set all LEDs exception power and shift.

6.3.3 Serial Port

Refer to the following MSDN website regarding programming serial connections for informa-tion about and examples of the Windows CE serial port API: http://msdn.microsoft.com/en-us/library/aa913128.aspx.

The serial port driver uses the stream driver interface. COM1 and COM2 drivers have port names of COM1: and COM2:, which can be passed to the CreateFile function to open these ports. COM2 is only available on units with the dual serial port option.

The MinTermCE.exe is a simple terminal program (refer to section 4.7.2) that can be used to test communications over the QTERM-G56/G58 serial ports.

The QTERM-G56/G58 is available with one serial “multiprotocol port,” which is a soft-ware-selectable EIA-232/422/485 serial port. The multiprotocol port 485 interface supports software-selectable AC terminations and a fail-safe network, which holds the 485 signal lines in a known state when no transceiver is transmitting. The multiprotocol serial port is COM1: on all G56/G58 units. Configuration of the multiprotocol port is done thru a registry setting as described below.



The registry key [HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial1] contains two values used to configure the multiprotocol port.

"PortType" (a dword value)Value of 0 selects 232 modeValue of 1 selects 422 modeValue of 2 selects 485 with fail-safe enabledValue of 3 selects 485 with termination enabledNote that if the following registry value (“SetupBitsValue”) has a setting other

than 0,the “PortType” setting will be ignored.

"SetupBitsValue" (a dword value) - the bits in this register map to control bits of the multiprotocol IC as follows:

Bit 0 selects between 232 mode and 485 mode (1=485 mode)Bit 1 controls a signal called fastBit 2 controls the half duplex settingBit 3 controls the shutdown signal (0=shutdown)Bit 4 controls the 485 termination (1=termination enabled)Bit 5 controls the 485 fail safeAll other bits are unused

Example registry settings:Following are the defaults for the prototype unit.

[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\Serial1]"PortType"=dword:0 ;select 232 mode"SetupBitsValue"=dword:0 ;


6.3.4 Network

Windows CE provides a standard API called Winsock for programming with TCP/IP-based network connections. Network connections are available for multiple interfaces and peripher-als on the QTERM-G56/G58, such as internal 10/100Base-T wired Ethernet on the G56, and optional internal WiFi adapter on the G58. Refer to section 4.1.6, “Network and Dial-up Con-nections” and Chapter 7, “Optional Peripherals” for additional information on these interfaces and peripherals.

Refer to the following MSDN articles for detailed information and programming reference for the Winsock Windows CE API:http://msdn.microsoft.com/en-us/library/aa926807.aspxhttp://msdn.microsoft.com/en-us/library/aa925696.aspx

Refer to the following MSDN article for Winsock programming samples:http://msdn.microsoft.com/en-us/library/aa916375.aspx



Following are some MSDN articles describing networking, connectivity, and using sockets with the .NET Compact Framework:http://msdn.microsoft.com/en-us/library/8y3swehx.aspxhttp://msdn.microsoft.com/en-us/library/b6xa24z5.aspx



Notes


CHAPTER 7

OPTIONAL PERIPHERALS

7.1 Wireless Ethernet

The QTERM-G58 (not the G56) provides 802.11b/g wireless Ethernet capability via an inter-nal USB WiFi adapter: Xterasys model XN-3135G. For more information about the adapter refer to: http://www.xterasys.com/product/xn3135g.htm. This device utilizes the Ralink RT2501USB chipset.

Drivers for this device are included in the QTERM-G58 file distribution. Other USB WiFi devices that include the same Ralink chipset may work with the Xterasys drivers on the QTERM-G58.

Windows CE provides a programmatic interface for using the WiFi adapter via the Winsock API. Refer to section 6.3.4, “Network” for more information on Winsock.

Wireless Ethernet adapter configuration in Windows CE is provided by the Wireless Zero Con-figuration service. For more information about this service refer to: http://msdn.microsoft.com/en-us/library/aa916223.aspx.

Access the Wireless Zero Configuration by tapping the network icon in the notification area of the task bar, then tapping the right pointing arrow. (See Figure 34.)

The WiFi device is powered up by an application included as part of the operating system. By default, the device is powered up. This can be disabled by changing the following registry value:

Figure 34Wireless Zero Configuration

Wireless Ethernet Optional Peripherals


[HKEY_LOCAL_MACHINE\Drivers\BuiltIn\OHCI] "WiFiPowerEnable"=dword:1

A value of 0 will disable the WiFi power at power-up.

The power can be controlled at run-time using the following IOCTL (shown using C# example code):

private static int enable = 0; //desired setting, 0 is off, non-zero is onprivate static Int32 FILE_DEVICE_OIO = 0x9008;private static Int32 FUNCTION_OIO_SET_WIFI_ENABLE = 0x810;private static Int32 IOCTL_OIO_SET_WIFI_ENABLE = (FILE_DEVICE_OIO) << 16) |

((FILE_ANY_ACCESS) << 14) | (FUNCTION_OIO_SET_WIFI_ENABLE << 2) |((METHOD_BUFFERED));

hOIO = CreateFile("OIO1:", FileAccess.Read, FileShare.None, 0, FileMode.Open, 0, UIntPtr.Zero);

DeviceIoControl(hOIO, IOCTL_OIO_SET_WIFI_ENABLE, null, enable, null, 0, null, false);


CHAPTER 8

SPECIFICATIONS

8.1 QTERM-G56

TERMINAL DISPLAY

Active Matrix ColorTFT LCD display, 262,144 colors (Color transflective sunlight readable)

Pixels 320 x 240

Pixel Pitch 0.2235 mm

Lighting Light emitting diode brightness is software-controllable

Backlight Brightness 200 cd/m2 typical

ContrastTransmissive: 150:1 typical

Reflective: 15:1 typical

Size89 mm (3.5") diagonal70 mm x 54 mm “live area”

TOUCH SCREEN

Analog-resistive operation

Transparent touch area over viewable display

KEYPAD

24 or 40 keys

Steel snap domes in membrane

Lighted keypad with electroluminescent lighting (optional)

Optional emergency stop switch (2-pole, normally closed; available with integral cable only)

INTERFACE

SerialSoftware-selectable EIA-232/422/485 serial port with select-able 485 AC terminations and fail-safe network

Serial (second port, without Ethernet option)

EIA-232 serial port with hardware (RTS/CTS) or software (XON/XOFF) handshaking (RTS/CTS not available with inte-gral cable option)

Baud Rates 600 – 115200 bps

Flow controlNoneXON/XOFF (software)RTS/CTS (hardware)

QTERM-G56 Specifications


Data formats

7 or 8 data bits1 or 2 stop bitsEven, odd, or no parity(Development tools support only 8 data bits)

Connector12-pin round (Hirose HR30-8R-12SC)Integral cable with DB15f (optional)

Ethernet (optional) 10/100Base-T with support for TCP/IP

USB deviceUSB 2.0 full speed (12 megabits/second) for access to internal NAND flash file system

MEMORY

Standard 64 MB SDRAM

Flash 256 MB NAND flash accessible as FAT-formatted file system

SPEAKER

Sealed 1 W 8 O speaker, 83 dB nominal at 100 mm, 1 W input power

Software programmable volume

REAL-TIME CLOCK

StandardIndependent processor-based real-time clock with battery backup, 1 second resolution

PHYSICAL

Housing ABS/polycarbonate case with molded rubber boot

Size 129 x 234 x 43 mm

Mass 510 g

ENVIRONMENTAL

SealingNEMA-12 (Standard)

NEMA-4 (optional)

TemperatureOperating: -20 to 60 °C

Storage: -30 to 70 °C

Humidity 0 to 95%, non-condensing

Vibration 5 to 2000 Hz, 4 g RMS

Shock20 g, 6 ms, 6 axis1.5 m onto concrete

POWER

8 to 32 VDC

5 VDC USB Host Port

INTERFACE (continued)

Specifications QTERM-G58


8.2 QTERM-G58

CPU

Atmel AT91SAM9261S processor

Speed: 192 MHz

Cache: 32 Kbytes instruction cache, 32 Kbytes data cache

SOFTWARE

Operating system:Microsoft Windows Embedded CE version 6.0 R3 Core or Professional (optional)

CUSTOMIZING

Keypad legend Customize with logo/name or graphics

Custom configurations available with setup fee and minimum order quantity.

CERTIFICATION

FCC Part 15, Class A

CE Certification

TERMINAL DISPLAY

Active Matrix ColorTFT LCD display, 262,144 colors (Color transflective sunlight read-able)

Pixels 320 x 240

Pixel Pitch 0.2235 mm

Lighting Light emitting diode brightness is software-controllable

Backlight Brightness 200 cd/m2 typical

ContrastTransmissive: 150:1 typical

Reflective: 15:1 typical

Size89 mm (3.5”) diagonal70 mm x 54 mm “live area”

TOUCH SCREEN

Analog-resistive operation

Transparent touch area over viewable display

KEYPAD

24 or 40 keys

Steel snap domes in membrane

Lighted keypad with electroluminescent lighting (optional)



INTERFACE

SerialSoftware-selectable EIA-232/422/485 serial port with select-able 485 AC terminations and fail-safe network

Baud Rates 600 – 115200 bps

Flow controlNoneXON/XOFF (software)RTS/CTS (hardware)

Data formats

7 or 8 data bits1 or 2 stop bitsEven, odd, or no parity(Development tools support only 8 data bits)

Connector 12-pin round (Hirose HR30-8R-12SC)

Wireless Ethernet (optional)

802.11b/gInfrastructure or Ad Hoc modeEncryption: 128-bit WEP, WPA, WPA2 (TKIP/AES)Dual internal antennas for receive diversity

USB deviceUSB 2.0 full speed (12 megabits/second) for access to internal NAND flash file system

MEMORY

Standard 64 MB SDRAM

Flash 256 MB NAND flash accessible as FAT-formatted file system

SPEAKER

Sealed 1 W 8 O speaker, 83 dB nominal at 100 mm, 1 W input power

Software programmable volume

REAL-TIME CLOCK

StandardIndependent processor-based real-time clock with battery backup, 1 second resolution

PHYSICAL

Housing ABS/polycarbonate case with molded rubber boot

Size129 x 234 x 43 mm129 x 234 x 50 mm battery and wireless Ethernet option

Mass510 g665 g battery option

ENVIRONMENTAL

Sealing NEMA-4

Specifications QTERM-G58


Temperature

Operating: -20 to 60 °C (-20 to 55 °C with wireless Ethernet option)

Storage: -30 to 70 °C

Battery charge: 0 to 40 °C

Humidity 0 to 95%, non-condensing

Vibration 5 to 2000 Hz, 4 g RMS

Shock20 g, 6 ms, 6 axis1.5 m onto concrete

POWER

8 to 32 VDC

5 VDC USB Host Port (wireless Ethernet disabled)

OPTIONAL BATTERY

Power Internal Lithium-polymer rechargeable battery pack

Battery life 10+ hours active life, 3 hours recharge time

CPU

Atmel AT91SAM9261S processor

Speed: 192 MHz

Cache: 32 Kbytes instruction cache, 32 Kbytes data cache

SOFTWARE

Operating system:Microsoft Windows Embedded CE version 6.0 R3 Core or Professional (optional)

CUSTOMIZING

Keypad legend Customize with logo/name or graphics

Custom configurations available with setup fee and minimum order quantity.

CERTIFICATION

FCC Part 15, Class A

CE Certification

ENVIRONMENTAL (continued)



Notes


CHAPTER 9

MECHANICAL

9.1 Layout and Dimensions

Figure 35QTERM-G56/G58 Front and Back View

Integral Cable Mechanical


9.2 Integral Cable

NOTE ☞ Your cable configuration may be customized with a different connector type. Contact Beijer Electronics technical support at http://www.beijerelectronicsinc.com/support/contact/?type=tech if you have cable connector questions.

Figure 36QTERM-G56/G58 Side View

Figure 37QTERM-G56/G58 Integral Cable

Mechanical Integral Cable


Integral Cable Mechanical


Mechanical Break Out Box (BOB) Pinouts


9.3 Break Out Box (BOB) Pinouts

Figure 38QTERM-G56/G58 BOB Pinouts

QTERM®-G56/G58BOB Pinouts

Device Pin Net Name

USB Host 1 +5V

2 D-

3 D+

4 Ground

Ethernet* 1 Tx+

2 Tx-

3 Rx+

4 NC

5 NC

6 Rx-

7 NC

8 NC

Com 1* 1 NC

2 232 Tx or 422 Tx-

3 232 Rx or 422 Rx+

4 NC

5 Ground

6 NC

7 232 CTS or 422 Rx-

8 232 RTS or 422 Tx+

9 NC

Com 2* 1 NC

2 Tx

3 Rx

4 NC

5 Ground

6 NC

7 NC

8 NC

9 NC

* Relative to terminalImages shown at actual size.

Break Out Box (BOB) Pinouts Mechanical


Power is applied with a coaxial plug with negative ground polarity (positive voltage on the center conductor and ground on the barrel). The Developer’s Kit includes a 12V wall mount power supply with compatible coaxial plug (2.1 mm inside, 5.5 mm outside diameter).

NOTE ☞ The Break Out Box may have a USB Host or Ethernet connector, but not both.


CHAPTER 10

TECHNICAL SUPPORT

10.1 Software Upgrades

This section provides instructions to install future software releases for the QTERM-G56/G58. You can obtain the latest releases of QTERM-G56/G58 firmware and Windows CE operating system software from the following Beijer Electronics website: http://www.beijerelectronicsinc.com/support/files

10.1.1 Operating System

The QTERM-G56/G58 Windows CE-based operating system is contained in an image file called NK.bin. This file is packaged along with several other files and directories to form a sys-tem package distribution. The QTERM-G56/G58 has an internal flash-based hard drive that is programmed at the factory with the system package distribution. Periodically, Beijer Electron-ics creates new versions of the operating system image (NK.bin), other files/directories in the distribution, or the directory structure of the distribution. Revisions to any of these results in a new release of the system package distribution. Upgrading the system package is the only way to install new versions of items in the package, including the operating system image.

Beijer Electronics has developed an update and package manager application called UpgradeCE.exe. This program can be used to upgrade the system package with updates from the Beijer Electronics website, as well as to install custom application packages. One advan-tage of using UpgradeCE.exe rather than a CAB file or other update/install method is that reg-istry settings are preserved, even after installation of a new operating system image (normally, installing a new NK.bin causes registry settings to revert to factory defaults).

For more information about CAB files and the wceload process refer to the following website: http://msdn.microsoft.com/en-us/library/aa924383.aspx.

For detailed information about UpgradeCE.exe, refer to the following website: http://www.beijerelectronicsinc.com/engfiles/TREQ/Apps/UpgradeCE.html.

The WinVerCE.exe utility (refer to section 4.7.2, “Beijer Electronics” on page 41) can be used to determine the current system package version. Run WinVerCE.exe from the Start Menu on the QTERM-G56/G58 task bar in the Beijer Electronics shortcut folder. The “Project Version” and “Build Date” fields indicate the version and build date of the system package, respectively (see Figure 39). These fields are updated when a new version of the system package is installed. “Kernel Version” refers to the Windows CE kernel version and license level.

Software Upgrades Technical Support


To upgrade the QTERM-G56/G58 system package, take the following steps:

1. Download the latest system package zip file. This file is available on the Beijer Electronics website at: http://www.beijerelectronicsinc.com/support/files/.

The latter includes previous images and other items for download in addition to the latest system package zip file.

The zip file contains the latest version of UpgradeCE.exe, the system package distribution, and release notes.

NOTE ☞ Be sure to read the release notes for the system package distribution! It is important to be aware of changes to the system that could potentially affect applications and general behavior before upgrading.

2. Connect the QTERM-G56/58 directly to a PC with the supplied 12-pin round connector to USB adapter cable. A mass storage device drive should appear inside your My Computer drive list.

3. Unzip the system package zip file to the folder \HardDisk\Temp. Retain any directory structure.

4. Open Windows Explorer from the Start menu, and navigate to the folder \HardDisk\Temp.

5. Double-tap the icon called “UpgradeCE” to launch the installer.

This will initiate the system package upgrade process. (Refer to Figure 40.) UpgradeCE displays a status line for each file in the package, indicating whether that file is up-to-date or needs to be updated. Larger files that need to be updated (e.g., NK.bin) will take longer and display multiple status lines indicating copy progress.

Figure 39WinVerCE

Technical Support Software Upgrades


6. Once complete, UpgradeCE will indicate success and ask for confirmation to reboot. (See Figure 41.) Answer y or n. The installation is not complete and UpgradeCE is disabled for further upgrades until after a reboot.

UpgradeCE will request a reboot only if files requiring an update are in use or if the NK.bin operating system image needs to be updated. It is common for the NK.bin image to require updating in system package upgrades.

7. After rebooting the QTERM-G56/G58, run the WinVerCE.exe program to verify that the system package was successfully upgraded.

Figure 40System Package Upgrade

Figure 41System Package Upgrade Complete

Software Upgrades Technical Support


10.1.2 Bootloader

The QTERM-G56/G58 bootloader has been designed to facilitate OS image updates as well as allow for access to the built-in mass storage device (NAND flash) via a USB connection to a host PC for system backup and recovery. Access the bootloader by pressing the [Shift] key while powering-up the unit. This will bypass the normal WinCE boot process and go to the bootloader. Figure 42 shows the screen that is displayed when the bootloader is active.

Press the [F1] key on the keypad or touch press F1 to enter setup on the screen to access the bootloader setup screen. The bootloader setup screen lets you specify various options related to loading an OS image for system updates and for boot behavior when connected to a host PC as a USB device. Figure 43 shows the bootloader setup-screen.

The Windows CE OS image file (NK.BIN) is stored in a reserved area of the internal mass storage device (NAND flash). This area is not accessible through the file system or when con-nected as a USB device. When the OS is to be upgraded, the bootloader setup screen allows you to specify where the unit will locate the image file used for the upgrade. The options are as follows:

Figure 42Bootloader Active

Figure 43Bootloader Setup

Technical Support Software Upgrades


• Read the image from the user accessible area of the mass-storage device (i.e., load from disk)

• Receive the image via the Ethernet interface utilizing TFTP protocol.

• Receive the image via USB device serial port interface (note that the bootloader presents a compound device USB interface that includes a mass storage device and a communications device).

The information displayed on the screen of Figure 43 will vary depending on your device con-figuration. For example, on a G56 unit without the Ethernet option, the “Load from TFTP” option will not be present on the screen shown in Figure 43. A G56 unit also will not display the battery charge status icon.

Figure 44 shows the setup screen after the “Load from Disk” option has been selected.

Perform the following steps to update the WinCE OS image.

1. Connect the unit to a PC as a USB device. This can be done by bypassing the normal WinCE OS boot process as described earlier (hold the [Shift] key while powering up) or by selecting Skip OS load if USB powered from the drop-down box shown in Figure 43.

2. Copy the WinCE OS image file (NK.BIN) to the device.

3. Disconnect the unit from the host PC.

4. For G56 units only: Repower the unit and bypass the normal WinCE OS boot process as described in step 1.

5. Press the [F1] key on the keypad to display the setup screen.

6. Select Load from Disk.

7. Select Normal from the list of available disk images

Figure 44Bootloader Load from Disk

System Backup and Recovery Technical Support


8. Select Write image on load complete.

9. Tap [OK] (this will redisplay the screen shown in Figure 42).

A progress bar will be displayed while the image is being read from the internal mass storage device. Note that the bootloader cannot access the internal mass storage device while it is being used as a USB device.

Once the image has been successfully read from the disk (or loaded via TFTP/USB communi-cations port if selected), it may be automatically written to the reserved area of the internal mass storage device if that option was selected on the setup screen. If the “Write Image on Load Complete” option was not selected, two new buttons will appear allowing you to write the image or launch the image manually.

Figure 45 shows the screen displayed when the unit is connected as a USB device (normal WinCE OS image boot process bypassed).

While connected as a USB device the setup screen may still be accessed and different options may be selected, but no loading from disk will occur until disconnected from the host PC.

10.2 System Backup and Recovery

The QTERM-G56/G58 contains a special recovery image known as the SOS (Small Operating System) image. This is a stripped down version of the main Windows CE operating system.

If the main Windows CE operating system (or any other system critical file that prevents proper booting) becomes corrupted, you will be able to access and repair the corruption by booting to the recovery image. In addition, if the bootloader detects a boot failure of the main operating system image due to a corruption, it will automatically boot the recovery image.

To manually boot the QTERM-G56/G58 to the SOS image, press the [Shift] key and one other key as you press the power key.

Figure 45Bootloader Connected via USB

Technical Support System Backup and Recovery


The SOS image will always boot to the touch screen calibration screen, even if it has been cal-ibrated on a previous boot. This is because the SOS maintains no persistent registry (or other) information. Calibrate the touch screen to proceed to the recovery image desktop (see Figure 46). Press the [Esc] key on the QTERM-G56/G58 keypad to bypass the touch calibration screen.

The Windows CE display color scheme for the recovery image is high contrast with a white background to help distinguish the recovery from the main image. The Windows Explorer view options have also been set to show hidden files in order to aid backup operations (see Fig-ure 47).

The SOS image may be useful for recovery and diagnostics when no USB host PC is available.

Alternatively, the QTERM-G56/G58 can be connected as a USB mass storage device to any USB host. This can be done (as described earlier) by holding down the [Shift] key while pow-ering up the device (section 10.1.2, “Bootloader”). Pressing [Shift] while powering up the device bypasses the normal Windows CE boot process.

Figure 46Recovery Image Desktop

Figure 47Windows Explorer View Options



To perform system backup and recovery, connect the QTERM-G56/G58 as a USB mass stor-age device to a PC. By pressing the [Shift] key while powering up the device connected via a USB cable, the content of the internal mass storage device (NAND flash) should be available on the PC as a removable device. You can browse the contents of the device using Windows Explorer on the PC. To copy all data from the device, browse to the device, select all files and folders, copy, and paste (or drag and drop) to a chosen backup location.

To backup the main flash storage, take the following steps.

1. Using the appropriate cable, connect the QTERM-G56/G58 to the USB port of the PC.

2. Hold down the [Shift] key, and power on the unit.

3. Verify that the screen shown in Figure 45 is displayed on the unit. (If not, you may need to power off the unit and repeat step 2)

4. The unit should automatically be detected by the PC as a USB mass storage device (the first time a unit is connected to the PC, it may take a moment while the appropriate drivers are set up).

5. Using Windows Explorer on the PC (Start, My Computer), locate the device.

6. Open the device.

7. Select all files and directories.

8. Copy (or drag and drop) the files and folders to a chosen backup location on the PC.

NOTE ☞ The (hidden) OS image cannot be copied or overwritten using this method. The OS image can be obtained from the Beijer Electronics website. It can be written to the reserved area using the procedure described in section 10.1.2.

To restore the main flash storage, take the following steps.

1. Boot to the SOS image as described above. Use the Storage Manager, Control Panel applet to administer the main flash storage. The flash may be reformatted, scanned, and/or defragmented with this Windows CE utility to help treat corruption of the file system tables. Incorrect file sizes and remaining free space are two indications of this kind of cor-ruption. Refer to section 4.1.7, “Storage Manager” for more details.

OR

Use the PC to format the flash (browse to the device, right-click, select Format or Proper-ties, then Tools).

2. Using the appropriate cable, connect the QTERM-G56/G58 to the USB port of the PC.

3. Hold down the [Shift] key, and power on the unit.

Technical Support System Backup and Recovery


4. Verify that the screen shown in Figure 45 is displayed on the unit. (If not, you may need to power off the unit and repeat step 2)

5. The unit should automatically be detected by the PC as a USB mass storage device (the first time a unit is connected to the PC, it may take a moment while the appropriate drivers are set up).

6. Using Windows Explorer on the PC (Start, My Computer), locate the device.

7. Copy all files and directories from the backup location selected earlier (step 8 of the backup procedure) and paste them to the device.

8. Reboot and verify that the main image boots and loads the correct application.

9. Recalibrate the touch screen using the Stylus, Control Panel applet (refer to section 4.1.1.2, “Recalibrate”). This is necessary because the main flash backup files may have been obtained from a different QTERM-G56/G58. Each QTERM-G56/G58 touch screen requires custom calibration, thus the correct calibration data must be regenerated for the unit being restored.

NOTE ☞ Beijer Electronics recommends creating a backup copy of the main flash storage using this procedure after end user applications are installed and configured. This will reduce time and effort spent trying to restore units that encounter corruption issues.



Notes