User's Manual
Table Of Contents
- Foreword
- Important Safety Information
- Contents
- About this Document
- Related Publications
- Product Description
- Features
- Specifications
- Air Interface
- Product Functionality
- Contents
- Integration Goal and Objectives
- Customer Problem Isolation
- Wireline and Wireless Communications
- Design Tips for Serviceability
- Environmental Issues
- Regulatory Requirements
- Contents
- Power Supply
- Host Interface
- Power Management
- Antenna Systems
- Hardware Recommendations
- Battery Selection Criteria
- Contents
- Hardware Integration
- Application Software
- Final Assembly
- Installation
- Troubleshooting
- End User Problem Resolution
- Service Depot Repair
- Contents
- Accessories and Options
- Abbreviations and Acronyms
- Desense Overview
- Desense Measurement Techniques
- Preparing the Device Under Test
- Performance Goals
- Methods of Controlling Emissions
- Antenna
- Summary
- FLEX Application Protocol Licensing
- Licensing
5-10 July 23, 2002
Testing CreataLink2 XT Hardware Integrator’s Guide
End User Problem Resolution
End User Problem Resolution
It is time-consuming and expensive to have a unit returned to the service depot
when a temporary network or host outage may have caused the problem. Is the
problem caused by the host application, data transceiver, network, configuration,
or user error? Design the application to identify the source of end-user problems.
This function can be designed with the guidance of SmartSynch, Inc. or the network
operator.
Tests need to provide a systematic, positive acknowledgment from each of the
network components:
• Data transceiver must be able to communicate with the external application
device. If so, it will respond to a properly formatted Get Configuration CLP
command.
• Data transceiver must be able to detect the network.
Issue a Get Status CLP command. If the status information indicates the unit is in
range, the data transceiver is detecting the system. For on-board applications, a
method of extracting service information must be provided.
• Data transceiver must be registered and allowed to operate on the network.
Auto-Registration is disabled (default). Transmit a short message to another pager.
Issue a Get Status CLP command and track the message progress until the message
is delivered or fails to be delivered.
Auto-Registration is enabled. Issue a Get Status CLP command. If the status
information indicates unit registration, the data transceiver can operate on the
network.
• The host application must be up and running.
Identify the cause of the problem in the field. This avoids having to send the device
to the service depot when the problem was not caused by the device. Design the
application so that the end user can identify the most likely cause of the problem,
and refer to a help desk for a quick solution.
➧
At initial start-up, the data transceiver assumes that it is within range. It takes
approximately four minutes to determine that it is not within range.