User Tools
wiki:mote_configuration
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision | |||
|
wiki:mote_configuration [2020/03/16 14:28] ghi removed |
— (current) | ||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ====== End-device configuration ====== | ||
| - | <note> | ||
| - | The way to configure an end-device is unique to each kind of end-device. Therefore, this part of the wiki is generic. Refer to the datasheet of your end-device to configure it. | ||
| - | </note> | ||
| - | |||
| - | ===== Configuration parameters ===== | ||
| - | |||
| - | ==== Pairing IDs ==== | ||
| - | |||
| - | To use an end-device with SPN, the end-device and the gateway need to be paired. To achieve this, two mechanisms are available: ABP or OTAA. | ||
| - | Each mechanism uses specific parameters. They need to be the same in both the end-device and the gateway. | ||
| - | |||
| - | === If the end-device uses OTAA (Over The Air Activation) === | ||
| - | * Device EUI (''dev_eui'') | ||
| - | * Application EUI (''app_eui'') | ||
| - | * Application key (''app_key'') | ||
| - | |||
| - | === If the end-device uses ABP (Activation By Personalisation) === | ||
| - | * Device Address (''dev_addr'') | ||
| - | * Network Session Key (''nwk_skey'') | ||
| - | * Application Session Key (''app_skey'') | ||
| - | |||
| - | ==== TX Frequencies and response window frequency ==== | ||
| - | |||
| - | End-devices send packets to the gateway using different frequencies. These frequencies must be configured and need to respect the regional parameters of the LoRaWAN specification. | ||
| - | |||
| - | To receive packets from the gateway, the end-devices open two receive windows after sending a packet. The first window uses the same frequency and radio settings as the one used to send the packet. The second window uses static parameters which need to be defined. | ||
| - | |||
| - | ==== End-device's specific parameters ==== | ||
| - | |||
| - | Most of the end-devices contain more than these parameters, however they are specific to each type of end-device. Here are a few examples of parameters: | ||
| - | * Region of the end-device | ||
| - | * LoRa device class | ||
| - | * TX power | ||
| - | * Datarate | ||
| - | * Receive and join accept delay | ||
| - | * … | ||
| - | |||
| - | These parameters can or cannot be mandatory. Refer to the constructor datasheet for proper tuning. | ||
| - | |||
| - | ===== Join procedure ===== | ||
| - | |||
| - | When using OTAA mechanism, to pair a end-device with the station, a “join” request needs to be initiated by the end-device. Depending on the used end-device, it can either be done automatically or manually. Check whether you need to trigger it yourself or not. | ||
wiki/mote_configuration.1584365316.txt.gz · Last modified: 2020/03/16 14:28 by ghi
Page Tools
