User Tools

Site Tools


wiki:mote_configuration

This is an old revision of the document!


Mote configuration

The way to configure a mote is unique for each kind of device. Therefore, this part of the wiki is generic. Refer to the datasheet of your device to configure it.

Configuration parameters

Pairing IDs

To use a mote with SPN , the mote 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 mote and the gateway.

If the mote uses OTAA

  • Device EUI (dev_eui)
  • Application EUI (app_eui)
  • Application key (app_key)

If the mote uses ABP

  • Device Address (dev_addr)
  • Network Session Key (nwk_skey)
  • Application Session Key (app_skey)

TX Frequencies and response window frequency

Motes send packets to the gateway using different frequencies, at least 3 different ones (though one at a time). These frequencies must be configured and need to respect the regional parameters of the LoRaWAN specification.

To receive packets from the gateway, the motes 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.

Mote's specific parameters

Most of the motes contain more than these parameters, however they are specific to each type of mote. Here are a few examples of parameters:

  • region of the mote
  • 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 mote with the station, a “join” request needs to be initiated by the mote. Depending on the used mote, it can either be done automatically or manually. Check whether you need to trigger it yourself or not.

wiki/mote_configuration.1507824703.txt.gz · Last modified: 2020/02/21 11:53 (external edit)