-
Notifications
You must be signed in to change notification settings - Fork 3
LoRa Device Tutorial
When setting up a LoRa client device, you need to do five main steps:
- Setup the firmware on the specific device and get the LoRa
DevID
(specific to device, see below) - Create a description for the device in OpenChirp (described in Device Tutorial)
- Add the LoraWAN service in OpenChirp and input the
DevID
- Add a decoder service (Byte Translator or Easybits)
- Add a TimeSeries datastore service
The most important aspect of the firmware on your device will be retrieving its DevID
and setting an appropriate AppEUI
and AppKey
. The DevID
is used to tell the network to look for your device. The AppEUI
and AppKey
are used for the network to correctly authenticate to your device. In OpenChirp you can set your own AppEUI
and AppKey
when linking in your device. The DevID
comes from the device itself.
A typical AppEUI
is a 16 digit hex number like 0000000000000000
and typical AppKey
is a 24 digit random hex string like 11B0282A189465B0B4D2D8C7FA38548C
. Both can be shared across all of your devices, but the DevID
is unique for each device.
Though the firmware is specific to your device, here are some common devices with examples that work with OpenChirp:
Creating a LoRa client device is the same as creating any other OpenChirp device. Please follow the Device Tutorial.
Once you have a device in hand with its DevID
and you have created an OpenChirp Device with a known end point, you need to add the LoRaWAN service.
Go to your device and click on the "Services" tab at the top. Enter the parameters as shown below:
OpenChirp is a research project started by the WiseLab at Carnegie Mellon University.
- Simple Device Tutorial
- PubSub Overview
- Time Series Data
- Device Tutorial
- Generate User Token Tutorial
- LoRaWAN Specific
-
Services
- Byte Translator
- Easybits
- Time Series Storage
- Event Trigger
- LoRaWAN Gateway
- GPS Mapper
- Custom Service
- Openchirp Packages
- REST API