Semtech LoRa Edge LR1110 User manual

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 1 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
LoRa Edge™ Tracker Reference Design
Evaluation Kit
(User Guide)
October 2020

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 2 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Welcome!
The LoRa Edge™ Tracker Evaluation Kit (“Kit”) is a portable reference kit designed to introduce LoRa Edge
tracking capabilities with LoRa Cloud™services, integrated with the Actility ThingPark Enterprise-based
Community Platform (Network Server) and Tago.io Application Service, and to showcase LoRaWAN®
network coverage around a building or site. It is also intended to accelerate solution development for a
wide range of stakeholders. The self-contained nature of this reference Kit makes it easy to set up, take
down and move a network in a matter of minutes.
Users can determine a gateway’s range of coverage by moving sensors to different places around a
coverage area. Furthermore, solution developers can focus on providing customer value through data
collection and analysis by using off-the-shelf hardware available from various ecosystem partners.
The GPS location data of each tracker is displayed on a dashboard that users access through a web browser.
The dashboard shows the type of displays that can be created with the data collected. The URL for the
dashboard and how to locate the login credentials for your Kit, are explained in the sections below.
What is in the Kit?
The Kit contains the following items:
Two LoRa Edge LR1110-based Tracking Devices
oTracker on/off magnets (2)
One gateway (base station) based on the LoRaWAN protocol with Ethernet or Wi-Fi backhaul
oPower adapter (region specific)
oLoRa® Gateway/Base Station antenna (only included with the U.S. model)
Figure 1: LR1110- Tracking Device

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 3 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Figure 2: LR1110 Tracker Kit Contents: LoRaWAN Gateway with Tracking Devices
Note: Within this document the term “gateway” and “base station” are used interchangeably; they are
meant to refer to the same physical device regardless of which term is used.
System Overview
The LoRa Edge Tracker Evaluation Kit demonstrates and highlights the various aspects of an asset tracking
system based on the LoRaWAN protocol. The elements used in this system are highlighted in the following
diagram.

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 4 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Figure 3: System Component Diagram
The data flow proceeds from the tracking devices through the gateway provided in the Kit to the ThingPark
Community Platform (the LoRaWAN Network Server). This network server will be configured to use the
LoRa Cloud Device Join service, which manages the LoRaWAN network join process. Once the devices have
joined the network, ThingPark Enterprise is the secure conduit for data to and from the Application Server,
which is hosted by Tago.IO. The Tago.IO service provides the interface to the position computation engine
(hosted on the LoRa Cloud portal). It also provides complete visualization of the tracking data for the
devices, which are available through a web browser. Each part of this system is independently scalable to
any size application that might be deployed. This demonstration is an example of an end-to-end
deployment of the latest LoRa Edge tracking solutions.
Not pictured is the LoRa Edge™ Config application, which is installed on smartphone devices, and talk
directly to the trackers to initialize and prepare them for operation. This functionality is discussed later in
this Users Guide.

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 5 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Getting the Kit Online
There are a few steps involved in getting your trackers online for the first time. The process of setting up
the devices is illustrative of the overall setup and system configuration. By following the steps outlined
below, you should be up-and-running quickly. Large-scale deployments can be automated by bulk import
utilities and APIs.
Creating a LoRa Cloud Portal Account
Before a LoRa Edge Tracker device can be claimed, you first must have an account on the LoRa Cloud portal.
To set up your account in a web browser, navigate to https://www.loracloud.com/.
1. Click Get Started.
Figure 4: Cloud Portal Welcome - Get Started
2. At the prompt, create an account. Use your email address and create a password.
Figure 5: LoRa Cloud Login

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 6 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
3. You should receive a confirmation email for the account. Click on the confirmation link in the email.
Your browser should open and take you to the login page. After logging into your new account, you
will need to accept the Terms & Conditions of Use. Once you accept these, your account activation
will be complete.
Creating an Application Owner and Getting Your Free Claim Allowance
Before you can claim your devices, you will need create an Application Owner. (An application owner is
used to organize a group of devices.) To create an application owner, login to the LoRa Cloud portal and
then
1. Select the LoRa Cloud Device Join tile.
Figure 6: Selecting the LoRa Cloud Device Join Tile
2. In the side panel, click Application Owners. Enter a name and then click Create New Owner, as
illustrated in Figure 7

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 7 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Figure 7: Creating a New Application Owner
Every new account has an allowance of 100 devices that can be claimed for free. You can assign
one and only one of your application owners this allowance. On the Application Owners page, click
the Assign button. You will be prompted to accept the free claim allowance for the associated
Application Owner. Accepting the assignment will allow you to claim up to 100 devices without
charge. Press OK to accept.
Figure 8: Assign your Free Allowance of Claims to an Application Owner

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 8 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Claiming a Device
To claim a device, navigate to the Device Join service in the LoRa Cloud portal at
https://www.loracloud.com/portal/join_service. From there, select the Devices link in the left pane.
The Join Server page will display. Under the Devices header, you will be presented with two options: Claim
Individual Device and Bulk Upload (CSV). In your kit, you will be provided information regarding the EUI,
JoinEUI and PIN for your device. In the web interface, if you select the Claim Individual Device you will be
presented with a form that looks like this:
Figure 9: Claiming a Device
The LR1110 Tracker EUI, PIN, and JOIN EUI can be extracted via the BLE Application that is described in
Setting-up and Operating LoRa Edge Trackers
Note: The CHIP EUI can be left blank or you can enter the Tracker EUI. Leave the EXTRA field blank.
Enter the data and then click Claim Device. If the PIN corresponds to the device credentials, the interface
will confirm that the device has been successfully claimed.
On-boarding: Network Server Specific
For the LoRa Cloud Device Join service to handle joining the device to the network, the device must to be
associated with the network server that will route the traffic to it and from it. By default, all compatible

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 9 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
network servers are enabled for use by your devices. You can skip ahead to the Using the LoRa Cloud
Device & Application Services, unless you only want to enable Join Services for a single network.
You may set up devices that will interact with more than one LoRaWAN network server. Figure 10 shows
two configuration setup examples. In the top example, a block of devices will be configured for LoRaWAN
Network Server 1 (Server 1) the join requests for devices received from that network server for a claimed
device will use the application configuration logic for appo-::a in the system. This is set on the Network
Servers configuration page of the LoRa Cloud Device Join service, or through the Application Owner API
documented here.
The second configuration example shows how the LoRa Cloud Device Join service can support integrations
with multiple network servers.
Figure 10: Relationship between LoRaWAN Network Servers and Applications in LoRa Cloud Applications IDs
The purpose of mapping the registered network server to a specific Application Owner is that specific
parameters can be set up for handling data when operating with each network server. There are three
common settings for each application definition:
name
wrapkey
nslist
The name is an arbitrary string to represent the application. The wrapkey is a specific token used for
encrypting the AppSKey, used during the transport of the AppSKey from the join server to the application
server by the network server. The nslist is a list of LoRaWAN network servers that will be associated with
this Application Owner configuration.

LR1110 Tracker Reference Design
Evaluation Kit
semtech.com/LoRa
Page 10 of 47
Quick Start Guide
Proprietary
October 2020
Semtech
Each LoRaWAN session derives a unique AppSKey which is used for encrypting the LoRaWAN payload data
between the device and the application server. The wrapkey can be null, indicating that the AppSKey will be
passed from the join server to the application server by the network server unencrypted. For more
information on working with the AppSKey, please see the documentation here.
https://www.loracloud.com/documentation/join_service?url=appskey.html.
Once the network servers are configured for a particular Application Owner via the LoRa Cloud Device Join
service, the device join process can be performed. The LoRaWAN network server that sees the join request
from the claimed device will forward this on to the LoRa Cloud Device Join service (which is operating as
the Join Server in this system). It will provide the session keys and return them, along with the join
response to the network server.
If a wrapkey is defined for the application associated with the network server, the AppSKey is returned
encrypted. Otherwise, the AppSKey will be returned in plain text by the join server. The LoRaWAN network
server will send the join response to the device. Once a data message is sent (following the join response)
to the LoRaWAN network server, the join process will be complete and the device will be configured for
operation on that network server.
Figure 11: Join Flow
Selecting ThingPark Enterprise on the LoRa Cloud Device Join Server
Once the Application Owner has been established, you must use the LoRa Cloud Device Join service to
select the network server.
1. Click NETWORK SERVERS link on the left
2. On the Network Servers page, select ThingPark Community Platform
3. Click ADD
Note: Currently the “Owner Context” for these devices is not defined.