The application will automatically starts a procedure to join a LoRaWAN network (see configuration).
Once a network is joined (i.e. when the corresponding event is triggered), uplinks are sent periodically. This periodic action is based on the LoRa Basics Modem alarm functionality. Each time the alarm-related event is triggered, the application requests an uplink.
The content of the uplink is the value read out from the charge counter by calling smtc_modem_get_charge().
The application is also capable of displaying data and meta-data of a received downlink.
Several parameters can be updated in main_lorawan.h header file:
| Constant | Description | Possible values | Default Value |
|---|---|---|---|
LORAWAN_APP_PORT |
LoRaWAN FPort used for the uplink messages | [1, 223] | 2 |
LORAWAN_CONFIRMED_MSG_ON |
Request a confirmation from the LNS that the uplink message has been received | {true,false} |
false |
APP_TX_DUTYCYCLE |
Delay in second between two uplinks | uint32_t |
60 |
When compiling with arm-none-eabi-gcc toolchain, all these constant are configurable through command line with the EXTRAFLAGS.
See README.md.
Here follow the steps that shall be seen in logs to indicate the expected behavior of the application:
INFO: Modem Initialization
INFO: ###### ===== LoRa Basics Modem LoRaWAN Class A/C demo application ==== ######
INFO: ###### ===== BASICS MODEM RESET EVENT ==== ######
Following this print you shall find application and LoRaWAN parameters prints
INFO: ###### ===== JOINED EVENT ==== ######
INFO: ###### ===== ALARM EVENT ==== ######
INFO: Request uplink
INFO: ###### ===== TX DONE EVENT ==== ######
Even though the lorawan example can run with the LoRaWAN class set to SMTC_MODEM_CLASS_C AND the region set to SMTC_MODEM_REGION_WW2G4, this configuration is not supported.