User's Manual
Table Of Contents
- Introduction
- The Integrator’s Task
- Installing the Modem
- Using the Modem Test Jig
- Testing
- Desense
- Application Development
- Message Routing and Migration
- Appendix A - NCL Interface
- Appendix B - Software Development Kit
- SDK Contents
- System Requirements
- SDK Software Architecture
- NCL Application Programmer’s Interface
- Implementation
- 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
- SCR Application Programmer’s Interface
- A
- Appendix C – Sample programs
- Appendix D - Wavenet Application Loader
- Appendix E - Numeric Conversion Chart
- Appendix F - Specifications
- Appendix H - Glossary
SDK SCR-API ______________________________________________ Boomer II User Manual & Integrator’s Guide
Wavenet Technology 152 BM210012WT27
Coupled with the interchangeable use of the message structures
SCRack, SCRhc, and SCRab is the function scr_NakReasonText(). The
response code field within the SCRack structure is network specific,
but the scr_NakReasonText() function will interpret the response code
appropriately for the network type specified to scr_Init() and will return
a text description of the error code, or a NULL pointer if the code
represents successful delivery.
Network Specific Messages
The SCR API defines network specific message structures for each of
the network specific SCR message types. These messages apply only to
particular versions of the DataTAC network.
When a message is passed to the scr_Encode() routine, and that
message is not valid for the specified network type, it is encoded as the
corresponding message type for the network version specified to
scr_Init() wherever possible. For example, if scr_Init() is used to set the
network type to DataTAC 5000, and an SCR_IB message is passed to
scr_Encode(), it will be encoded as a Host Request (HR) message.
Also, due to the same structure definitions and equivalent message type
constants being used across all network types for the From Network
(OB and MI) and Acknowledgment (AB and HC) messages, the
decoded structures may be interpreted as network specific structures,
and this will still work on other network types. For example, if
scr_Init() is used to set the network type to DataTAC 5000, and a
SCR_MI message is received from the network and decoded, this
decoded structure may be interpreted as an SCR_OB structure with no
side effects.
DataTAC
®
4000 Network Messages
The following message types are specific to the DataTAC 4000
network:
SCR_OB Basic Outbound message for receiving data from a
wireless device
SCR_IB Basic Inbound message for sending data to a wireless
device
SCR_AB Basic Acknowledgment of data sent to a wireless device
DataTAC
®
5000 Network Messages
The following message types are extended SCR messages that are only
used on the DataTAC 5000 network.
SCR_LR Loopback Request
SCR_LC Loopback Confirmation (response to LR)
SCR_CI Connect Indication