User's Manual
Table Of Contents
- Introduction
- The Integrator’s Task
- Installing the Modem
- Mounting the Boomer˚III OEM Modem to Your Device
- Connecting the Data Interface Port
- Selecting & Positioning the Antenna
- Supplying Power
- Using the Modem Test Jig
- Software Development Tools
- Integration Testing
- Appendix A - NCL Interface
- Appendix B – SDK NCL-API and Port Server
- _
- Logical Architecture
- Application Interface
- Opening a Session
- Close Session
- Send Data to a Radio Host
- Receive Data From RPM
- Get RPM Status Information
- Set Configuration ITEMS Within the RPM
- Reset RPM
- Register Event Callback Function
- Enable / Disable Events
- Get Error Description
- Register Wakeup Application
- Deregister Wakeup Application
- Switch RPM On/Off
- Send Generic NCL Command To RPM
- Get Software Version
- _
- A
- Appendix C – SDK Sample programs
- Appendix D - Application Development
- Appendix E - Message Routing and Migration
- Appendix F – Guide to Desense
- Appendix G - Numeric Conversion Chart
- Appendix H - Specifications
- Appendix I - Glossary
Appendix D - Application Development _________________________ Boomer-III User Manual & Integrator’s Guide
Copyright Wavenet Technology © October 2003 118 BM310012WT04
Appendix D - Application Development
This section provides comments and advice that can help you develop
successful wireless enabled applications for DataTAC systems.
Application development for NCL-compliant wireless modem devices
is a two-part process.
The first step sets up the interface between the host/terminal
and the wireless modem. In this step you must consider the
interactions with the wireless modem, as established by the
NCL 1.2 reference specification and the vendor specific
extensions.
The second step involves addressing message routing
information to identify the message destination within the
DataTAC network.
Use the following suggestions to help you develop wireless enabled
applications.
Use Power Save mode of operation to extend battery life and
operational time for the user. We recommend that the
application does not modify this mode dynamically.
Use the Confirmed mode of operation to perform the following
functions:
• Check the SDU checksum for validity.
• Re-read SDUs received in error.
• Read past the last message in Confirmed mode to make
sure the device buffer is fully flushed. If the buffer is not
flushed, the last message is held, consuming valuable
buffer space.
Anticipate new NCL command, event, and response codes:
• Perform exact matches on event and response codes.
• Discard any unknown event type.
• Map any unknown XFAIL code to be a NAK.
Use SDU tags to uniquely identify application-generated SDUs.
Anticipate the user will move between IN_RANGE and
OUT_OF_RANGE conditions. This means you need to
provide:
• A user indicator that identifies the current operating
status.
• Recovery mechanisms when application transactions
fail as a result of losing network contact.