Sierra Wireless AirPrime XS1110 User manual

AirPrime XS1110
Development Kit User Guide
41113415
Rev 2.0

Development Kit User Guide
Rev 2.0 Apr.20 2 41113415
Important
Notice
Due to the nature of wireless communications, transmission and reception of data
can never be guaranteed. Data may be delayed, corrupted (i.e., have errors) or
be totally lost. Although significant delays or losses of data are rare when wireless
devices such as the Sierra Wireless product are used in a normal manner with a
well-constructed network, the Sierra Wireless product should not be used in
situations where failure to transmit or receive data could result in damage of any
kind to the user or any other party, including but not limited to personal injury,
death, or loss of property. Sierra Wireless accepts no responsibility for damages
of any kind resulting from delays or errors in data transmitted or received using
the Sierra Wireless product, or for failure of the Sierra Wireless product to
transmit or receive such data.
Safety and
Hazards
Do not operate the Sierra Wireless product in areas where blasting is in progress,
where explosive atmospheres may be present, near medical equipment, near life
support equipment, or any equipment which may be susceptible to any form of
radio interference. In such areas, the Sierra Wireless product MUST BE
POWERED OFF. The Sierra Wireless product can transmit signals that could
interfere with this equipment.
Do not operate the Sierra Wireless product in any aircraft, whether the aircraft is
on the ground or in flight. In aircraft, the Sierra Wireless product MUST BE
POWERED OFF. When operating, the Sierra Wireless product can transmit
signals that could interfere with various onboard systems.
Note: Some airlines may permit the use of cellular phones while the aircraft is on the
ground and the door is open. Sierra Wireless products may be used at this time.
The driver or operator of any vehicle should not operate the Sierra Wireless
product while in control of a vehicle. Doing so will detract from the driver or
operator's control and operation of that vehicle. In some states and provinces,
operating such communications devices while in control of a vehicle is an offence.
Limitation of
Liability
The information in this manual is subject to change without notice and does not
represent a commitment on the part of Sierra Wireless. SIERRA WIRELESS AND
ITS AFFILIATES SPECIFICALLY DISCLAIM LIABILITY FOR ANY AND ALL
DIRECT, INDIRECT, SPECIAL, GENERAL, INCIDENTAL, CONSEQUENTIAL,
PUNITIVE OR EXEMPLARY DAMAGES INCLUDING, BUT NOT LIMITED TO,
LOSS OF PROFITS OR REVENUE OR ANTICIPATED PROFITS OR REVENUE
ARISING OUT OF THE USE OR INABILITY TO USE ANY SIERRA WIRELESS
PRODUCT, EVEN IF SIERRA WIRELESS AND/OR ITS AFFILIATES HAS BEEN
ADVISED OF THE POSSIBILITY OF SUCH DAMAGES OR THEY ARE
FORESEEABLE OR FOR CLAIMS BY ANY THIRD PARTY.
Notwithstanding the foregoing, in no event shall Sierra Wireless and/or its
affiliates aggregate liability arising under or in connection with the Sierra Wireless
product, regardless of the number of events, occurrences, or claims giving rise to
liability, be in excess of the price paid by the purchaser for the Sierra Wireless
product.

Preface
Rev 2.0 Apr.20 3 41113415
Patents This product may contain technology developed by or for Sierra Wireless Inc. This
product is manufactured or sold by Sierra Wireless Inc. or its affiliates under one
or more patents licensed from MMP Portfolio Licensing.
Copyright © 2020 Sierra Wireless. All rights reserved.
Trademarks Sierra Wireless®, AirPrime®, AirLink®, AirVantage® and the Sierra Wireless logo
are registered trademarks of Sierra Wireless.
Windows® and Windows Vista® are registered trademarks of Microsoft
Corporation.
Other trademarks are the property of their respective owners.
Contact
Information
Revision
History
Sales information and technical
support, including warranty and returns
Web: sierrawireless.com/company/contact-us/
Global toll-free number: 1-877-687-7795
6:00 am to 5:00 pm PST
Corporate and product information Web: sierrawireless.com
Revision
number
Release date Changes
1.0 September 05, 2019 Creation
1.1 September 10, 2019 Updated SYSTEM0 on page 8
1.2 March 05, 2020 Updated Development Kit photos to the latest version
1.3 March 11, 2020 Updated images
2.0 April 16, 2020 Minor text edits
Changed Figure 4-5
Changed Map description on page 17

Rev 2.0 Apr.20 4 41113415
Contents
Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5
Hardware Overview . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6
Interfaces . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Module . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7
Antenna Connection. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
SYSTEM0. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8
I2C . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9
BOOT Mode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10
1PPS / INT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 11
WAKE UP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
NRESET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Micro-B USB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 12
Software Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
System Requirements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
USB Driver and GNSS Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14
Installing the USB Driver. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15
Using GNSS Tool . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17
Troubleshooting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Setup Troubleshooting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19
Causes of Poor GNSS Signals. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20
References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

Rev 2.0 Apr.20 5 41113415
1
1: Introduction
The main purpose of the Development Kit is to simplify the evaluation process for
GNSS modules and to help testers operate our products with convenience and ease.
Figure 1-1: Development Kit
This device can communicate with computer devices via USB cable, and it must be
used in conjunction with the software, GNSS Tool, for users to record all module data
such as satellites’ status, time-to-first-fix (TTFF), date and time.
Note that:
•The GNSS signal may be cut off or become seriously weakened if you operate
the Development Kit inside any infrastructure such as buildings, tunnels, or near
any huge objects and/or obstruction. Signal being cut off does not mean the
Development Kit has malfunctioned; it will operate properly again once it receives
clear GNSS signals (works normally under the open sky).
•Select a suitable external passive antenna based on the satellite system that you
use.

Rev 2.0 Apr.20 6 41113415
2
2: Hardware Overview
The following figure identifies the location of the Development Kit’s connectors and
other components.
Figure 2-1: Development Kit Connectors and Components
Refer to the subsequent chapter, Interfaces on page 7, for detailed description.
Figure 2-2: RF SMA Connector

Rev 2.0 Apr.20 7 41113415
3
3: Interfaces
This section describes the physical interfaces available on the Development Kit.
Module
The Development Kit includes an XS1110 module.
Figure 3-1: XS1110 on the Development Kit
Note that the XS1110 requires an external RF antenna to be connected to the RF
SMA connector of the Development Kit.
Table 3-1: Module Details
Component PCB Label Description
Module XS XS1110 module

Development Kit User Guide
Rev 2.0 Apr.20 8 41113415
Antenna Connection
The RF SMA connector is used to connect an external antenna for the XS1110
module.
Figure 3-2: RF SMA Connector
SYSTEM0
The SYSTEM0 header is used to set whether transmissions are done via UART
or I2C.
Figure 3-3: SYSTEM0 Header
To set transmission selection to UART, disconnect jumper on SYSTEM0 for
SYSTEM0 pins to pull high (default).
Table 3-2: Antenna Connector Details
Component PCB Label Description
RF SMA Connector SMA1 External antenna connector for the XS1110
module
Table 3-3: SYSTEM0 Details
Component PCB Label Description
2-pin header P20 •Transmission selection (UART or I2C)
•SYSTEM0 : 0=I2C ; 1=UART

Interfaces
Rev 2.0 Apr.20 9 41113415
Figure 3-4: No Jumper on SYSTEM0 for UART Transmission
To set transmission selection to I2C, short SYSTEM0 with a jumper. SYSTEM0
pins will then enter pull low status. The Development Kit must then be re-powered
(by unplugging then replugging the power supply), after which the NRESET
button must be pressed to reboot the module to change transmission selection
from UART to I2C.
Figure 3-5: Jumper Across SYSTEM0 for I2C Transmission
I2C
Connectivity to peripheral devices are available through the I2C interface.
Figure 3-6: I2C Header

Development Kit User Guide
Rev 2.0 Apr.20 10 41113415
Pins 01 to 02 have to be configured by connecting them with jumpers.
See Figure 3-4 and Figure 3-5 on page 9 for jumper configuration consistent with
SYSTEM0 settings.
Mismatching jumper connections will result in pin error after reboot; in this case,
I2C features will not be enabled.
BOOT Mode
The BOOT Mode header is used to place the module in Flash download mode to
perform firmware updates.
Figure 3-7: BOOT Mode Header
Table 3-4: I2C Header Details
Component PCB Label Description
5-pin header P1 I2C signals; refer to Table 3-5 for details
Table 3-5: I2C Header Pins
Pin Number Pin Name Description
1 GND Ground
2 GND Ground
3 RX0 / I2CSDA I2C serial data (in slave mode)
4 TX0 / I2CSCL I2C serial clock (in slave mode)
5 GND Ground
Table 3-6: BOOT Mode Details
Component PCB Label Description
2-pin header P23 Add a jumper to make the module ready for
firmware upgrade

Interfaces
Rev 2.0 Apr.20 11 41113415
1PPS / INT
Connectivity to peripheral devices is supported via the 1PPS and INT (for I2C)
header.
Figure 3-8: 1PPS / INT Header
Table 3-7: 1PPS / INT Details
Component PCB Label Description
5-pin header P2 1PPS / INT header
Table 3-8: 1PPS / INT Header Pins
Pin Number Pin Name Description
1 GND Ground
2 GND Ground
3 INT Interrupt pin for I2C application
4 GND Ground
5 1PPS 1PPS time mark output

Development Kit User Guide
Rev 2.0 Apr.20 12 41113415
WAKE UP
The WAKE UP pushbutton wakes the module up.
Figure 3-9: WAKE UP Button
NRESET
The NRESET pushbutton reboots the module.
Figure 3-10: NRESET Button
Micro-B USB
The Micro-B USB connector provides for power and serial access from a host
device, and interfaces to an on-board CP2102N IC which provides access to the
module’s UART interface.
When the Development Kit is powered ON:
•LED1 (Power) is lit,
•the host device can connect to the XS1110’s console, and
Table 3-9: WAKE UP Button Details
Component PCB Label Description
Button SWITCH 3 Pushing the WAKE UP button wakes the
module up from sleep mode.
Table 3-10: NRESET Button Details
Component PCB Label Description
Button SWITCH 2 Pushing the NRESET button reboots the
module.

Interfaces
Rev 2.0 Apr.20 13 41113415
•the module’s UART access becomes accessible (default setting of
115200kbps baud rate and update rate of 1Hz).
Figure 3-11: Micro-B USB Connector and Power LED
Table 3-11: Micro-B USB Connector Details
Component PCB Label Description
Micro-B USB connector JP1 Connects the Development Kit to a host
device and provides access to the module’s
UART interface

Rev 2.0 Apr.20 14 41113415
4
4: Software Usage
System Requirements
•Operating System: Microsoft Windows 7, 8, and 10
•USB Driver: CP210x VCPInstaller.zip
·For Windows 7, Windows 8 or Windows 8.1, please use CP210xVCP driver
v6.7 or the latest version (v6.7.5).
·For Windows 10, please use CP210xVCP driver v6.7.5; v10.1.1
•GUI Tool: GNSS Tool
•Microsoft .NET Framework 4.5
•Microsoft Visual C++ 2015 Redistributable Package (x86)
USB Driver and GNSS Tool
Before setting up the connection between the module’s UART port and the PC, you
will need the Development Kit USB Driver (CP210x VCP) and GNSS Tool.exe to
operate the Development Kit.
Please download and install the USB Driver (CP210x VCP) from https://
source.sierrawireless.com/resources/airprime/software/cp210x-windows-drivers.
Please download the GNSS tool from https://source.sierrawireless.com/resources/
airprime/software/gnss_tool/.
Important: Please check whether you have the correct USB driver before you proceed to the
next step. The Development Kit will not function without the correct driver.

Software Usage
Rev 2.0 Apr.20 15 41113415
Installing the USB Driver
1. Double click CP210x_VCP_Win.exe to begin driver installation:
Figure 4-1: Driver Installation Folder
2. Click Install:
Figure 4-2: Starting the Installation Process
3. After the installation is complete, you may need to restart your computer.
Please follow the instructions on screen to restart your computer.
4. After the computer has restarted, right click on My Computer and select
Manage:
Figure 4-3: Selecting Manage

Development Kit User Guide
Rev 2.0 Apr.20 16 41113415
5. Left click Device Manager and select Ports (COM &LPT). Check to see if a
device named Silicon Labs CP210x USB to UART Bridge (COM#) is
present. If so, the Development Kit is set up and ready for use.
Figure 4-4: Accessing the Port Properties
“COM9” represents the virtual COM port number generated for the USB
connection to the Development Kit. This generated COM port value must match
the COM port value in the program setting for the application to establish proper
communication with the Development Kit.

Software Usage
Rev 2.0 Apr.20 17 41113415
Using GNSS Tool
Microsoft Framework 4.5 or higher is required before you launch the GNSS Tool
software on your PC.
Double click GNSSTool.exe to start the application, the main screen of the
program is shown below:
Figure 4-5: Main Program Screen
1. Command Tx and Rx List: clicking on this menu item will display the
Command window.
2. NMEA List: clicking on this menu item will display a window with NMEA infor-
mation.
3. CNR Signal: clicking on this menu item will display the CNR signal window.
4. Sky View: clicking on this menu item will display a window with a sky view of
satellites.
5. Statistics Plot: clicking on this menu item will display the statistics plot
window.
6. CEP: clicking on this menu item will display the CEP (Circular Error Probable)
window, which can calculate the CEP in real-time or from a historical position.

Development Kit User Guide
Rev 2.0 Apr.20 18 41113415
After the Development Kit is connected with the PC, please choose the correct
<COM Port> and <Baud Rate>.
Figure 4-6: COM Port Dialog
If you want more information about the GNSS Tool software, refer to AirPrime
GNSS Tool User Guide.

Rev 2.0 Apr.20 19 41113415
5
5: Troubleshooting
Setup Troubleshooting
Note: If these troubleshooting steps do not solve the problem, please contact us or send the
module back to us for inspection.
Table 5-1: Troubleshooting Causes and Solutions
Problem Possible Cause Solution
Cannot find
GNSS device
USB was not set up properly Check to see if the Development Kit was
set up properly, and make sure that the
device is receiving enough power
through the USB cable (red LED should
light up continuously).
No NMEA data or
GNSS signals
1. USB was not set up properly.
2. COM port or baud rate value is
incorrect.
1. Check to see if the USB connector
to the PC or Development Kit is
connected properly.
2. Double check to see if the proper
COM port and baud rate value are
selected.
Poor GNSS
Signal Reception
1. If it is used inside a vehicle, the
anti-sunscreen film on the
windshield may interfere and
weaken the GNSS signal.
2. The vehicle might be under some
area with a dense overhead canopy
such as a forest, buildings, tunnels,
etc.
For both problems, the user may
connect an external active antenna to
the Development Kit, and then place the
antenna on top of the car’s roof to
improve signal reception.

Development Kit User Guide
Rev 2.0 Apr.20 20 41113415
Causes of Poor GNSS Signals
It is possible to have weak GNSS signal in the following situations:
Table 5-2: Examples Where Poor GNSS Signals May Occur
Inside a tunnel, where the GNSS signal is blocked.
Underneath infrastructure (e.g. a bridge), where the GNSS signal is blocked.
Inside a building, where the GNSS signal is blocked.