This is an example application based on Mbed-OS LoRaWAN protocol APIs. The Mbed-OS LoRaWAN stack implementation is compliant with LoRaWAN v1.0.2 specification.

Dependents:   Projet_de_bachelor_code Projet_de_bachelor_code

Example LoRaWAN application for Mbed-OS

This is an example application based on Mbed-OS LoRaWAN protocol APIs. The Mbed-OS LoRaWAN stack implementation is compliant with LoRaWAN v1.0.2 specification. See this link for information on support for other LoRaWAN spec versions. This application can work with any Network Server if you have correct credentials for the said Network Server.

Getting Started

Supported Hardware

Mbed Enabled board with an Arduino form factor and one of the following:

OR

Mbed Enabled LoRa Module

Import the example application

For Mbed Online Compiler users:

  • Select "Import", then search for "mbed-os-example-lorawan" from "Team mbed-os-examples". Or simply, import this repo by URL.
  • NOTE: Do NOT select "Update all libraries to latest revision" as this may cause breakage with a new lib version we have not tested.

For mbed-cli users:

$ mbed import mbed-os-example-lorawan
$ cd mbed-os-example-lorawan

#OR

$ git clone git@github.com:ARMmbed/mbed-os-example-lorawan.git
$ cd mbed-os-example-lorawan
$ mbed deploy

Example configuration and radio selection

Because of the pin differences between the SX126x and SX127x radios, example application configuration files are provided with the correct pin sets in the config/ dir of this project.

Please start by selecting the correct example configuration for your radio:

  • For Mbed Online Compiler users, this can be done by simply replacing the contents of the mbed_app.json at the root of the project with the content of the correct example configuration in config/ dir.
  • For mbed-cli users, the config file can be specifed on the command line with the --app-config option (ie --app-config config/SX12xx_example_config.json)

With the correct config file selected, the user can then provide a pin set for their target board in the NC fields at the top if it is different from the default targets listed. If your device is one of the LoRa modules supported by Mbed-OS, the pin set is already provided for the modules in the target-overrides field of the config file. For more information on supported modules, please refer to the module support section

Add network credentials

Open the file mbed_app.json in the root directory of your application. This file contains all the user specific configurations your application and the Mbed OS LoRaWAN stack need. Network credentials are typically provided by LoRa network provider.

For OTAA

Please add Device EUI, Application EUI and Application Key needed for Over-the-air-activation(OTAA). For example:

"lora.device-eui": "{ YOUR_DEVICE_EUI }",
"lora.application-eui": "{ YOUR_APPLICATION_EUI }",
"lora.application-key": "{ YOUR_APPLICATION_KEY }"

For ABP

For Activation-By-Personalization (ABP) connection method, modify the mbed_app.json to enable ABP. You can do it by simply turning off OTAA. For example:

"lora.over-the-air-activation": false,

In addition to that, you need to provide Application Session Key, Network Session Key and Device Address. For example:

"lora.appskey": "{ YOUR_APPLICATION_SESSION_KEY }",
"lora.nwkskey": "{ YOUR_NETWORK_SESSION_KEY }",
"lora.device-address": " YOUR_DEVICE_ADDRESS_IN_HEX  " 

Configuring the application

The Mbed OS LoRaWAN stack provides a lot of configuration controls to the application through the Mbed OS configuration system. The previous section discusses some of these controls. This section highlights some useful features that you can configure.

Selecting a PHY

The LoRaWAN protocol is subject to various country specific regulations concerning radio emissions. That's why the Mbed OS LoRaWAN stack provides a LoRaPHY class that you can use to implement any region specific PHY layer. Currently, the Mbed OS LoRaWAN stack provides 10 different country specific implementations of LoRaPHY class. Selection of a specific PHY layer happens at compile time. By default, the Mbed OS LoRaWAN stack uses EU 868 MHz PHY. An example of selecting a PHY can be:

        "phy": {
            "help": "LoRa PHY region. 0 = EU868 (default), 1 = AS923, 2 = AU915, 3 = CN470, 4 = CN779, 5 = EU433, 6 = IN865, 7 = KR920, 8 = US915, 9 = US915_HYBRID",
            "value": "0"
        },

Duty cycling

LoRaWAN v1.0.2 specifcation is exclusively duty cycle based. This application comes with duty cycle enabled by default. In other words, the Mbed OS LoRaWAN stack enforces duty cycle. The stack keeps track of transmissions on the channels in use and schedules transmissions on channels that become available in the shortest time possible. We recommend you keep duty cycle on for compliance with your country specific regulations.

However, you can define a timer value in the application, which you can use to perform a periodic uplink when the duty cycle is turned off. Such a setup should be used only for testing or with a large enough timer value. For example:

"target_overrides": {
	"*": {
		"lora.duty-cycle-on": false
		},
	}
}

Module support

Here is a nonexhaustive list of boards and modules that we have tested with the Mbed OS LoRaWAN stack:

  • MultiTech mDot (SX1272)
  • MultiTech xDot (SX1272)
  • LTEK_FF1705 (SX1272)
  • Advantech Wise 1510 (SX1276)
  • ST B-L072Z-LRWAN1 LoRa®Discovery kit with Murata CMWX1ZZABZ-091 module (SX1276)

Here is a list of boards and modules that have been tested by the community:

  • IMST iM880B (SX1272)
  • Embedded Planet Agora (SX1276)

Compiling the application

Use Mbed CLI commands to generate a binary for the application. For example:

$ mbed compile -m YOUR_TARGET -t ARM

Running the application

Drag and drop the application binary from BUILD/YOUR_TARGET/ARM/mbed-os-example-lora.bin to your Mbed enabled target hardware, which appears as a USB device on your host machine.

Attach a serial console emulator of your choice (for example, PuTTY, Minicom or screen) to your USB device. Set the baudrate to 115200 bit/s, and reset your board by pressing the reset button.

You should see an output similar to this:

Mbed LoRaWANStack initialized 

 CONFIRMED message retries : 3 

 Adaptive data  rate (ADR) - Enabled 

 Connection - In Progress ...

 Connection - Successful 

 Dummy Sensor Value = 2.1 

 25 bytes scheduled for transmission 
 
 Message Sent to Network Server

Adding trace library

To enable Mbed trace, add to your mbed_app.json the following fields:

    "target_overrides": {
        "*": {
            "mbed-trace.enable": true
            }
     }

The trace is disabled by default to save RAM and reduce main stack usage (see chapter Memory optimization).

Please note that some targets with small RAM size (e.g. DISCO_L072CZ_LRWAN1 and MTB_MURATA_ABZ) mbed traces cannot be enabled without increasing the default "main_stack_size": 1024.

Memory optimization

Using Arm CC compiler instead of GCC reduces 3K of RAM. Currently the application takes about 15K of static RAM with Arm CC, which spills over for the platforms with 20K of RAM because you need to leave space, about 5K, for dynamic allocation. So if you reduce the application stack size, you can barely fit into the 20K platforms.

For example, add the following into config section in your mbed_app.json:

"main_stack_size": {
    "value": 2048
}

Essentially you can make the whole application with Mbed LoRaWAN stack in 6K if you drop the RTOS from Mbed OS and use a smaller standard C/C++ library like new-lib-nano. Please find instructions here.

For more information, please follow this blog post.

License and contributions

The software is provided under Apache-2.0 license. Contributions to this project are accepted under the same license. Please see contributing.md for more info.

This project contains code from other projects. The original license text is included in those source files. They must comply with our license guide.

Committer:
mbed_official
Date:
Sun Mar 11 09:45:20 2018 +0000
Revision:
3:8c7198d1a2a1
Parent:
2:dc95ac6d6d4e
Child:
12:5015dfead3f2
Added LORAWAN_ENABLED flag to disable building in unsupported devices

- Also added check for SPI as it is needed by Radio technoology

.
Commit copied from https://github.com/ARMmbed/mbed-os-example-lorawan

Who changed what in which revision?

UserRevisionLine numberNew contents of line
mbed_official 0:7037ed05f54f 1 /**
mbed_official 0:7037ed05f54f 2 * Copyright (c) 2017, Arm Limited and affiliates.
mbed_official 0:7037ed05f54f 3 * SPDX-License-Identifier: Apache-2.0
mbed_official 0:7037ed05f54f 4 *
mbed_official 0:7037ed05f54f 5 * Licensed under the Apache License, Version 2.0 (the "License");
mbed_official 0:7037ed05f54f 6 * you may not use this file except in compliance with the License.
mbed_official 0:7037ed05f54f 7 * You may obtain a copy of the License at
mbed_official 0:7037ed05f54f 8 *
mbed_official 0:7037ed05f54f 9 * http://www.apache.org/licenses/LICENSE-2.0
mbed_official 0:7037ed05f54f 10 *
mbed_official 0:7037ed05f54f 11 * Unless required by applicable law or agreed to in writing, software
mbed_official 0:7037ed05f54f 12 * distributed under the License is distributed on an "AS IS" BASIS,
mbed_official 0:7037ed05f54f 13 * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
mbed_official 0:7037ed05f54f 14 * See the License for the specific language governing permissions and
mbed_official 0:7037ed05f54f 15 * limitations under the License.
mbed_official 0:7037ed05f54f 16 */
mbed_official 0:7037ed05f54f 17 #include <stdio.h>
mbed_official 3:8c7198d1a2a1 18
mbed_official 3:8c7198d1a2a1 19 #if MBED_CONF_APP_LORAWAN_ENABLED
mbed_official 3:8c7198d1a2a1 20
mbed_official 3:8c7198d1a2a1 21 #ifdef DEVICE_SPI
mbed_official 3:8c7198d1a2a1 22
mbed_official 0:7037ed05f54f 23 #include "lorawan/LoRaWANInterface.h"
mbed_official 0:7037ed05f54f 24 #include "lorawan/system/lorawan_data_structures.h"
mbed_official 0:7037ed05f54f 25 #include "events/EventQueue.h"
mbed_official 0:7037ed05f54f 26
mbed_official 0:7037ed05f54f 27 // Application helpers
mbed_official 0:7037ed05f54f 28 #include "DummySensor.h"
mbed_official 0:7037ed05f54f 29 #include "trace_helper.h"
mbed_official 0:7037ed05f54f 30 #include "lora_radio_helper.h"
mbed_official 0:7037ed05f54f 31
mbed_official 0:7037ed05f54f 32 using namespace events;
mbed_official 0:7037ed05f54f 33
mbed_official 0:7037ed05f54f 34 uint8_t tx_buffer[LORAMAC_PHY_MAXPAYLOAD];
mbed_official 0:7037ed05f54f 35 uint8_t rx_buffer[LORAMAC_PHY_MAXPAYLOAD];
mbed_official 0:7037ed05f54f 36
mbed_official 0:7037ed05f54f 37 /*
mbed_official 0:7037ed05f54f 38 * Sets up an application dependent transmission timer in ms. Used only when Duty Cycling is off for testing
mbed_official 0:7037ed05f54f 39 */
mbed_official 0:7037ed05f54f 40 #define TX_TIMER 10000
mbed_official 0:7037ed05f54f 41
mbed_official 0:7037ed05f54f 42 /**
mbed_official 0:7037ed05f54f 43 * Maximum number of events for the event queue.
mbed_official 0:7037ed05f54f 44 * 16 is the safe number for the stack events, however, if application
mbed_official 0:7037ed05f54f 45 * also uses the queue for whatever purposes, this number should be increased.
mbed_official 0:7037ed05f54f 46 */
mbed_official 0:7037ed05f54f 47 #define MAX_NUMBER_OF_EVENTS 16
mbed_official 0:7037ed05f54f 48
mbed_official 0:7037ed05f54f 49 /**
mbed_official 0:7037ed05f54f 50 * Maximum number of retries for CONFIRMED messages before giving up
mbed_official 0:7037ed05f54f 51 */
mbed_official 0:7037ed05f54f 52 #define CONFIRMED_MSG_RETRY_COUNTER 3
mbed_official 0:7037ed05f54f 53
mbed_official 0:7037ed05f54f 54 /**
mbed_official 0:7037ed05f54f 55 * Dummy pin for dummy sensor
mbed_official 0:7037ed05f54f 56 */
mbed_official 0:7037ed05f54f 57 #define PC_9 0
mbed_official 0:7037ed05f54f 58
mbed_official 0:7037ed05f54f 59 /**
mbed_official 0:7037ed05f54f 60 * Dummy sensor class object
mbed_official 0:7037ed05f54f 61 */
mbed_official 0:7037ed05f54f 62 DS1820 ds1820(PC_9);
mbed_official 0:7037ed05f54f 63
mbed_official 0:7037ed05f54f 64 /**
mbed_official 0:7037ed05f54f 65 * This event queue is the global event queue for both the
mbed_official 0:7037ed05f54f 66 * application and stack. To conserve memory, the stack is designed to run
mbed_official 0:7037ed05f54f 67 * in the same thread as the application and the application is responsible for
mbed_official 0:7037ed05f54f 68 * providing an event queue to the stack that will be used for ISR deferment as
mbed_official 0:7037ed05f54f 69 * well as application information event queuing.
mbed_official 0:7037ed05f54f 70 */
mbed_official 0:7037ed05f54f 71 static EventQueue ev_queue(MAX_NUMBER_OF_EVENTS * EVENTS_EVENT_SIZE);
mbed_official 0:7037ed05f54f 72
mbed_official 0:7037ed05f54f 73 /**
mbed_official 0:7037ed05f54f 74 * Event handler.
mbed_official 0:7037ed05f54f 75 *
mbed_official 0:7037ed05f54f 76 * This will be passed to the LoRaWAN stack to queue events for the
mbed_official 0:7037ed05f54f 77 * application which in turn drive the application.
mbed_official 0:7037ed05f54f 78 */
mbed_official 0:7037ed05f54f 79 static void lora_event_handler(lorawan_event_t event);
mbed_official 0:7037ed05f54f 80
mbed_official 0:7037ed05f54f 81 /**
mbed_official 2:dc95ac6d6d4e 82 * Constructing Mbed LoRaWANInterface and passing it down the radio object.
mbed_official 0:7037ed05f54f 83 */
mbed_official 2:dc95ac6d6d4e 84 static LoRaWANInterface lorawan(radio);
mbed_official 0:7037ed05f54f 85
mbed_official 0:7037ed05f54f 86 /**
mbed_official 0:7037ed05f54f 87 * Application specific callbacks
mbed_official 0:7037ed05f54f 88 */
mbed_official 0:7037ed05f54f 89 static lorawan_app_callbacks_t callbacks;
mbed_official 0:7037ed05f54f 90
mbed_official 0:7037ed05f54f 91 /**
mbed_official 0:7037ed05f54f 92 * Entry point for application
mbed_official 0:7037ed05f54f 93 */
mbed_official 0:7037ed05f54f 94 int main (void)
mbed_official 0:7037ed05f54f 95 {
mbed_official 0:7037ed05f54f 96 // setup tracing
mbed_official 0:7037ed05f54f 97 setup_trace();
mbed_official 0:7037ed05f54f 98
mbed_official 0:7037ed05f54f 99 // stores the status of a call to LoRaWAN protocol
mbed_official 0:7037ed05f54f 100 lorawan_status_t retcode;
mbed_official 0:7037ed05f54f 101
mbed_official 0:7037ed05f54f 102 // Initialize LoRaWAN stack
mbed_official 2:dc95ac6d6d4e 103 if (lorawan.initialize(&ev_queue) != LORAWAN_STATUS_OK) {
mbed_official 0:7037ed05f54f 104 printf("\r\n LoRa initialization failed! \r\n");
mbed_official 0:7037ed05f54f 105 return -1;
mbed_official 0:7037ed05f54f 106 }
mbed_official 0:7037ed05f54f 107
mbed_official 0:7037ed05f54f 108 printf("\r\n Mbed LoRaWANStack initialized \r\n");
mbed_official 0:7037ed05f54f 109
mbed_official 0:7037ed05f54f 110 // prepare application callbacks
mbed_official 0:7037ed05f54f 111 callbacks.events = mbed::callback(lora_event_handler);
mbed_official 2:dc95ac6d6d4e 112 lorawan.add_app_callbacks(&callbacks);
mbed_official 0:7037ed05f54f 113
mbed_official 0:7037ed05f54f 114 // Set number of retries in case of CONFIRMED messages
mbed_official 2:dc95ac6d6d4e 115 if (lorawan.set_confirmed_msg_retries(CONFIRMED_MSG_RETRY_COUNTER)
mbed_official 0:7037ed05f54f 116 != LORAWAN_STATUS_OK) {
mbed_official 0:7037ed05f54f 117 printf("\r\n set_confirmed_msg_retries failed! \r\n\r\n");
mbed_official 0:7037ed05f54f 118 return -1;
mbed_official 0:7037ed05f54f 119 }
mbed_official 0:7037ed05f54f 120
mbed_official 0:7037ed05f54f 121 printf("\r\n CONFIRMED message retries : %d \r\n",
mbed_official 0:7037ed05f54f 122 CONFIRMED_MSG_RETRY_COUNTER);
mbed_official 0:7037ed05f54f 123
mbed_official 0:7037ed05f54f 124 // Enable adaptive data rate
mbed_official 2:dc95ac6d6d4e 125 if (lorawan.enable_adaptive_datarate() != LORAWAN_STATUS_OK) {
mbed_official 0:7037ed05f54f 126 printf("\r\n enable_adaptive_datarate failed! \r\n");
mbed_official 0:7037ed05f54f 127 return -1;
mbed_official 0:7037ed05f54f 128 }
mbed_official 0:7037ed05f54f 129
mbed_official 0:7037ed05f54f 130 printf("\r\n Adaptive data rate (ADR) - Enabled \r\n");
mbed_official 0:7037ed05f54f 131
mbed_official 2:dc95ac6d6d4e 132 retcode = lorawan.connect();
mbed_official 0:7037ed05f54f 133
mbed_official 0:7037ed05f54f 134 if (retcode == LORAWAN_STATUS_OK ||
mbed_official 0:7037ed05f54f 135 retcode == LORAWAN_STATUS_CONNECT_IN_PROGRESS) {
mbed_official 0:7037ed05f54f 136 } else {
mbed_official 0:7037ed05f54f 137 printf("\r\n Connection error, code = %d \r\n", retcode);
mbed_official 0:7037ed05f54f 138 return -1;
mbed_official 0:7037ed05f54f 139 }
mbed_official 0:7037ed05f54f 140
mbed_official 0:7037ed05f54f 141 printf("\r\n Connection - In Progress ...\r\n");
mbed_official 0:7037ed05f54f 142
mbed_official 0:7037ed05f54f 143 // make your event queue dispatching events forever
mbed_official 0:7037ed05f54f 144 ev_queue.dispatch_forever();
mbed_official 3:8c7198d1a2a1 145
mbed_official 3:8c7198d1a2a1 146 return 0;
mbed_official 0:7037ed05f54f 147 }
mbed_official 0:7037ed05f54f 148
mbed_official 3:8c7198d1a2a1 149
mbed_official 0:7037ed05f54f 150 /**
mbed_official 0:7037ed05f54f 151 * Sends a message to the Network Server
mbed_official 0:7037ed05f54f 152 */
mbed_official 0:7037ed05f54f 153 static void send_message()
mbed_official 0:7037ed05f54f 154 {
mbed_official 0:7037ed05f54f 155 uint16_t packet_len;
mbed_official 0:7037ed05f54f 156 int16_t retcode;
mbed_official 0:7037ed05f54f 157 float sensor_value;
mbed_official 0:7037ed05f54f 158
mbed_official 0:7037ed05f54f 159 if (ds1820.begin()) {
mbed_official 0:7037ed05f54f 160 ds1820.startConversion();
mbed_official 0:7037ed05f54f 161 sensor_value = ds1820.read();
mbed_official 0:7037ed05f54f 162 printf("\r\n Dummy Sensor Value = %3.1f \r\n", sensor_value);
mbed_official 0:7037ed05f54f 163 ds1820.startConversion();
mbed_official 0:7037ed05f54f 164 } else {
mbed_official 0:7037ed05f54f 165 printf("\r\n No sensor found \r\n");
mbed_official 0:7037ed05f54f 166 return;
mbed_official 0:7037ed05f54f 167 }
mbed_official 0:7037ed05f54f 168
mbed_official 0:7037ed05f54f 169 packet_len = sprintf((char*) tx_buffer, "Dummy Sensor Value is %3.1f",
mbed_official 0:7037ed05f54f 170 sensor_value);
mbed_official 0:7037ed05f54f 171
mbed_official 2:dc95ac6d6d4e 172 retcode = lorawan.send(MBED_CONF_LORA_APP_PORT, tx_buffer, packet_len,
mbed_official 0:7037ed05f54f 173 MSG_CONFIRMED_FLAG);
mbed_official 0:7037ed05f54f 174
mbed_official 0:7037ed05f54f 175 if (retcode < 0) {
mbed_official 0:7037ed05f54f 176 retcode == LORAWAN_STATUS_WOULD_BLOCK ? printf("send - WOULD BLOCK\r\n")
mbed_official 0:7037ed05f54f 177 : printf("\r\n send() - Error code %d \r\n", retcode);
mbed_official 0:7037ed05f54f 178 return;
mbed_official 0:7037ed05f54f 179 }
mbed_official 0:7037ed05f54f 180
mbed_official 0:7037ed05f54f 181 printf("\r\n %d bytes scheduled for transmission \r\n", retcode);
mbed_official 0:7037ed05f54f 182 memset(tx_buffer, 0, LORAMAC_PHY_MAXPAYLOAD);
mbed_official 0:7037ed05f54f 183 }
mbed_official 0:7037ed05f54f 184
mbed_official 0:7037ed05f54f 185 /**
mbed_official 0:7037ed05f54f 186 * Receive a message from the Network Server
mbed_official 0:7037ed05f54f 187 */
mbed_official 0:7037ed05f54f 188 static void receive_message()
mbed_official 0:7037ed05f54f 189 {
mbed_official 0:7037ed05f54f 190 int16_t retcode;
mbed_official 2:dc95ac6d6d4e 191 retcode = lorawan.receive(MBED_CONF_LORA_APP_PORT, rx_buffer,
mbed_official 0:7037ed05f54f 192 LORAMAC_PHY_MAXPAYLOAD,
mbed_official 0:7037ed05f54f 193 MSG_CONFIRMED_FLAG|MSG_UNCONFIRMED_FLAG);
mbed_official 0:7037ed05f54f 194
mbed_official 0:7037ed05f54f 195 if (retcode < 0) {
mbed_official 0:7037ed05f54f 196 printf("\r\n receive() - Error code %d \r\n", retcode);
mbed_official 0:7037ed05f54f 197 return;
mbed_official 0:7037ed05f54f 198 }
mbed_official 0:7037ed05f54f 199
mbed_official 0:7037ed05f54f 200 printf(" Data:");
mbed_official 0:7037ed05f54f 201
mbed_official 0:7037ed05f54f 202 for (uint8_t i = 0; i < retcode; i++) {
mbed_official 0:7037ed05f54f 203 printf("%x", rx_buffer[i]);
mbed_official 0:7037ed05f54f 204 }
mbed_official 0:7037ed05f54f 205
mbed_official 0:7037ed05f54f 206 printf("\r\n Data Length: %d\r\n", retcode);
mbed_official 0:7037ed05f54f 207
mbed_official 0:7037ed05f54f 208 memset(rx_buffer, 0, LORAMAC_PHY_MAXPAYLOAD);
mbed_official 0:7037ed05f54f 209 }
mbed_official 0:7037ed05f54f 210
mbed_official 0:7037ed05f54f 211 /**
mbed_official 0:7037ed05f54f 212 * Event handler
mbed_official 0:7037ed05f54f 213 */
mbed_official 0:7037ed05f54f 214 static void lora_event_handler(lorawan_event_t event)
mbed_official 0:7037ed05f54f 215 {
mbed_official 0:7037ed05f54f 216 switch (event) {
mbed_official 0:7037ed05f54f 217 case CONNECTED:
mbed_official 0:7037ed05f54f 218 printf("\r\n Connection - Successful \r\n");
mbed_official 0:7037ed05f54f 219 if (MBED_CONF_LORA_DUTY_CYCLE_ON) {
mbed_official 0:7037ed05f54f 220 send_message();
mbed_official 0:7037ed05f54f 221 } else {
mbed_official 0:7037ed05f54f 222 ev_queue.call_every(TX_TIMER, send_message);
mbed_official 0:7037ed05f54f 223 }
mbed_official 0:7037ed05f54f 224
mbed_official 0:7037ed05f54f 225 break;
mbed_official 0:7037ed05f54f 226 case DISCONNECTED:
mbed_official 0:7037ed05f54f 227 ev_queue.break_dispatch();
mbed_official 0:7037ed05f54f 228 printf("\r\n Disconnected Successfully \r\n");
mbed_official 0:7037ed05f54f 229 break;
mbed_official 0:7037ed05f54f 230 case TX_DONE:
mbed_official 0:7037ed05f54f 231 printf("\r\n Message Sent to Network Server \r\n");
mbed_official 0:7037ed05f54f 232 if (MBED_CONF_LORA_DUTY_CYCLE_ON) {
mbed_official 0:7037ed05f54f 233 send_message();
mbed_official 0:7037ed05f54f 234 }
mbed_official 0:7037ed05f54f 235 break;
mbed_official 0:7037ed05f54f 236 case TX_TIMEOUT:
mbed_official 0:7037ed05f54f 237 case TX_ERROR:
mbed_official 0:7037ed05f54f 238 case TX_CRYPTO_ERROR:
mbed_official 0:7037ed05f54f 239 case TX_SCHEDULING_ERROR:
mbed_official 0:7037ed05f54f 240 printf("\r\n Transmission Error - EventCode = %d \r\n", event);
mbed_official 0:7037ed05f54f 241 // try again
mbed_official 0:7037ed05f54f 242 if (MBED_CONF_LORA_DUTY_CYCLE_ON) {
mbed_official 0:7037ed05f54f 243 send_message();
mbed_official 0:7037ed05f54f 244 }
mbed_official 0:7037ed05f54f 245 break;
mbed_official 0:7037ed05f54f 246 case RX_DONE:
mbed_official 0:7037ed05f54f 247 printf("\r\n Received message from Network Server \r\n");
mbed_official 0:7037ed05f54f 248 receive_message();
mbed_official 0:7037ed05f54f 249 break;
mbed_official 0:7037ed05f54f 250 case RX_TIMEOUT:
mbed_official 0:7037ed05f54f 251 case RX_ERROR:
mbed_official 0:7037ed05f54f 252 printf("\r\n Error in reception - Code = %d \r\n", event);
mbed_official 0:7037ed05f54f 253 break;
mbed_official 0:7037ed05f54f 254 case JOIN_FAILURE:
mbed_official 0:7037ed05f54f 255 printf("\r\n OTAA Failed - Check Keys \r\n");
mbed_official 0:7037ed05f54f 256 break;
mbed_official 0:7037ed05f54f 257 default:
mbed_official 0:7037ed05f54f 258 MBED_ASSERT("Unknown Event");
mbed_official 0:7037ed05f54f 259 }
mbed_official 0:7037ed05f54f 260 }
mbed_official 0:7037ed05f54f 261
mbed_official 3:8c7198d1a2a1 262 #endif //DEVICE_SPI
mbed_official 3:8c7198d1a2a1 263
mbed_official 3:8c7198d1a2a1 264 #else
mbed_official 3:8c7198d1a2a1 265 int main (void)
mbed_official 3:8c7198d1a2a1 266 {
mbed_official 3:8c7198d1a2a1 267 return 0;
mbed_official 3:8c7198d1a2a1 268 }
mbed_official 3:8c7198d1a2a1 269 #endif //MBED_CONF_APP_LORAWAN_ENABLED
mbed_official 0:7037ed05f54f 270 // EOF