User's Manual Part 2
Table Of Contents
- Chapter 2 - Windows Mobile
- Software Builds
- Where to Find Information
- Basic Usage
- Microsoft ActiveSync
- Microsoft Pocket Outlook
- Calendar: Scheduling Appointments and Meetings
- Synchronizing Calendar
- Why Use Categories in the Calendar?
- What’s an All Day Event?
- What’s a Recurrence Pattern?
- Viewing Appointments
- Creating or Changing an Appointment
- Creating an All-Day Event
- Setting a Reminder for an Appointment
- Adding a Note to an Appointment
- Making an Appointment Recurring
- Assigning an Appointment to a Category
- Sending a Meeting Request
- Finding an Appointment
- Deleting an Appointment
- Changing Calendar Options
- Contacts: Tracking Friends and Colleagues
- Tasks: Keeping a To Do List
- Notes: Capturing Thoughts and Ideas
- Messaging: Sending and Receiving E-mail Messages
- Calendar: Scheduling Appointments and Meetings
- Companion Programs
- Internet Explorer Mobile
- Chapter 3 - Configuring the Computer
- Developing Applications for the Computer
- Packaging Applications for the CN3 Computer
- Installing Applications on the Computer
- Updating the System Software
- Launching Your Application Automatically
- Customizing How Applications Load on the Computer
- Configuring CN3 Parameters
- Configuring the Color Camera
- Configuring the SF51 Scanner
- Using Configuration Parameters
Chapter 3 — Configuring the Computer
86 PRELIMINARY - CN3 Mobile Computer User’s Manual
The computer returns the CgS+BV4 transaction to the host application:
Configuring the CN3 Computer in a UDP Plus Network
Use the host computer to configure a CN3 Computer in your wireless net-
work. To send and receive configuration data or files, write a host applica-
tion that can communicate with an Intermec Application Server (IAS)
formerly Gateway or DCS 30X.
For help, see the appropriate Gateway or DCS 30X User’s Manual. Use the
Terminal Message Format (TMF) protocol to send and receive transactions
between the host application and the CN3 Computer.
To set up the IAS, configure a peer-to-peer destination name for the host
application. Create a $NGCFGRSP transaction ID that routes to this des-
tination name. The IAS uses the transaction ID to route responses from the
CN3 back to the host application. $NGCFGRSP is a special transaction
ID that the server uses to forward configuration response data from a CN3.
All configuration responses are routed with the $NGCFGRSP transaction
ID. The IAS cannot track multiple applications sending reader or configu-
ration commands. If you have two host applications sending reader or con-
figuration commands, they must both be configured to receive the
$NGCFGRSP transactions, and receive all CN3 Computer responses.
To set up the host computer, verify host computer-to-IAS communication.
To set up the application, prepare and write a host application that can
communicate with the IAS and send transactions to and receive transac-
tions from the CN3 Computer in this format.
where:
Cg is a TMF Configuration Get response.
$+ is the Change Configuration reader command.
BV4 means the Beeper Volume configuration command is currently set to a
value of 4, which is a very high beeper volume.
transaction header TMF field commands
transaction
header
A 96-byte field with message number, date, time, source application ID, destinations application ID,
transaction ID, and other. Set the system message (SYS$MSG) flag to E in the transaction header.
TMF field A 2-byte field containing one of these values:
CG Configuration Get request sent from the host application.
Cg Configuration Get response sent from the CN3 Computer to the host computer.
CS Configuration Set request sent from the host application.
Cs Configuration Set response sent from the CN3 Computer to host computer
commands The reader and configuration commands to set on the CN3 Computer or the current value to retrieve
from the CN3 Computer. To save configuration changes in flash memory, send the .+1 reader com-
mand as the last command. See the Command Reference Manual for a list of supported commands.