PK 6xJm$! lora-node-latest/.buildinfo# Sphinx build info version 1 # This file hashes the configuration used when building these files. When it is not found, a full rebuild will be done. config: tags: PK 6xJp1M lora-node-latest/objects.inv# Sphinx inventory version 2 # Project: RN2483_Silica # Version: 1.0 # The remainder of this file is compressed using zlib. xڕMS08F[kuj(A7 dUDHdK Q+YS("Z aYWA-6 Ntktǂ#%k4K#r:GyG 2 'ߌ +`H-EhX^kF0'DR&qC0yZ-BT{آWQR^b z2c:nG a##]pUQq雃#] cL`|d+*Ż|Vw4{BAh#k3Tȁ%EVZi-fHWqM\ZȎtK% #7\Ȍݘswaڔӣn̳b= #8q^"f> >`PK 6xJN4 4 lora-node-latest/index.html
Version: | 1.40 |
---|---|
Copyright: | (C)2017 Avnet Silica company |
Date: | 14 Mar 2017 |
Reference name: | BAEVTSS002 |
Sensor Node Lora
Microchip’s Long Range Low Power End Node solution
With the growing Internet of Things, Microchip has a LoRa® Technology wireless solution to address increasing demands on end-devices for long range connectivity, low power for battery operation, and low infrastructure cost for volume deployment.
Microchip’s LoRa Technology solution is ready to run out-of-the box and with the complete LoRaWAN™ Protocol and certifications in place, it reduces time to market and saves development costs.
The RN2483 is a LoRa™-integrated modem with a range of more than 15 km (suburban), low power enabling a battery life greater than 10 years and the ability to connect millions of wireless sensor nodes to LoRa gateways and IoT-connected Cloud Servers. This robust system is due to LoRa’s unique spread-spectrum based modulation that is capable of demodulation 20 dB below the noise level. This enables high sensitivity for ultra-long range, improved network efficiency and eliminates interference. The RN2483 modem operates over the 433 and 868 MHz license-free Industry Scientific and Medical (ISM) frequency bands and serves as the end-device in the LoRa network infrastructure.
The RN2483 is a fully-certified 433/868 MHz module based on wireless LoRa® technology.
The module’s embedded LoRaWAN™ Class A protocol enables seamless connectivity to any LoRaWAN compliant network infrastructure, whether public or privately deployed. The module is specifically designed for ease of use, which shortens development time and speeds time to market. LoRa technology is ideal for battery-operated sensors and low power applications such as IoT, M2M, Smart City, Sensor networks, Industrial automation, and more.
Features:
Firmware developed using: NXP Kinetis Design Studio. For installation and configuration of the project, follow instruction inside Quick start guide for firmware 1.6 or major
The board reference documentation is available on the Avnet Silica website.
Contents:
In this guide you will be able to upload your board with the last firmware and join the Lora Network in ABP or OTAA mode.
If you are unsure about which firmware version you have then update your board with the lastest firmware avaiable.
Warning
If the window opened is named BOOTLOADER repeat the procedure, the window must be named MBED.
Warning
If accidentally has been copied the firmware in the BOOTLOADER window you have corrupted the MBED firmware and you have to fix it. Please read the fix procedure going to the page How to fix the MBED firmware
Now you have to choose which kind of connection you want OTAA or ABP.
You have to setup the board in order to send correctly messages to your operator. Follow next steps correctly:
Module Version: BAEVTSS002 firmware version 1.6
RN2483 1.0.1 Dec 15 2015 09:38:06
Send commands to RN2483. Write 'quit' to exit.
Enter 1 > Write/Read REGS
Enter 2 > RESET Module
Enter 3 > Send Payload
Enter 4 > Advanced Settings
Now if you want to use OTAA go to the paragraph OTAA Configuration otherwise if you want to use ABP go to ABP Configuration
The OTAA configuration requires the following parameters:
Enter 1 > set DEVADDR (ABP mandatory)
Enter 2 > set NWKSKEY (ABP mandatory)
Enter 3 > set APPSKEY (ABP optional)
Enter 4 > set DEVEUI (OTAA and ABP mandatory)
Enter 5 > set APPEUI (OTAA mandatory)
Enter 6 > set APPKEY (OTAA mandatory)
Enter 7 > Save Changes
Enter 8 < back
Once the board is configurated correctly you have to register the device to your provider. In this guide we used Thingpark. To follow the next steps go to Register Module.
The ABP configuration requires the following parameters:
Enter 1 > set DEVADDR (ABP mandatory)
Enter 2 > set NWKSKEY (ABP mandatory)
Enter 3 > set APPSKEY (ABP optional)
Enter 4 > set DEVEUI (OTAA and ABP mandatory)
Enter 5 > set APPEUI (OTAA mandatory)
Enter 6 > set APPKEY (OTAA mandatory)
Enter 7 > Save Changes
Enter 8 < back
Optional field but useful:
Warning
If you don’t enter the same keys wrote in the device you will be unable to send data correctly in the Lora network.
17. From the main menu of the device you have to select which mode will be used in the demo. You can have these options:
Enter 5 > Change mode Demo to OTAA join
Enter 6 < Start Demo in ABP mode
or
Enter 5 > Change mode Demo to ABP join
Enter 6 < Start Demo in OTAA mode
Select the correct one, your choose will be stored in flash memory and used every time you will turn-on the board. Then start the demo, the device will enter automatically in sleep mode.
The dark will be rappresented with a low number and a strong light with a high number.
The board has four LEDs:
LED | Color | Brief Note |
1 | Blue | RN2483 GPIO_12 |
2 | Red | RN2483 GPIO_13 |
3 | — | not fitted |
4 | Green | OpenSDA & MBED |
5 | Blue | Firmware status |
This guide permits to send messages over the Lora network. This page is written for Windows users.
Check on the backside of the board a label like this one:
If the serial number S/N is lesser than 199 then you have to update the firwmare otherwise skip the next paragraph.
Update your board with the lastest firmware avaiable:
Warning
If the window opened is named BOOTLOADER repeat the procedure, the window must be named MBED.
Warning
If accidentally has been copied the firmware in the BOOTLOADER window you have corrupted the MBED firmware and you have to fix it. Please read the fix procedure going to the page How to fix the MBED firmware
Optional field but useful:
Warning
If some key is wrong then the device will be unable to send data correctly in the Lora network.
Now take your board:
The board doesn’t have the correct device address in order to send correctly messages to your operator, so you have to set it. Follow next steps correctly:
BAEVTSS002 firmware version 1.5b
RN2483 1.0.1 Dec 15 2015 09:38:06
*** MENU CONFIG RN2483 ***
Enter 0 to print this menu
Enter 1 to see values in DEVEUI and DEVADDR registers
Enter 2 to modify DEVEUI
Enter 3 to modify DEVADDR
Enter 4 to modify APPSKEY
Enter 5 to modify NWKSKEY
Enter 6 to save changes
Enter 7 to Microchip default reset
Enter 8 to Avnet default reset
Enter 9 to exit
From this menu you will be able to change the registers DEVEUI, DEVADDR, APPSKEY and NWKSKEY. furthermore it is possible reset the RN2483 with factory reset by Microchip or by Avnet.
Warning
The BAEVTSS002 is setted by default with Avnet reset.
Changing deveui register, current value: 001B9954
Enter new deveui value, 8 hex numbers lenght (press ENTER to abort):
>>
As you can see in the first line it is displayed the current value in the register and how many numbers you have to insert in order to change the register.
Note
The current value of the register it is displayed only for DEVEUI and DEVADDR registers. APPSKEY and NWKSKEY register are write-only so their current value won’t be showed.
Changing deveui register, current value: 001B9954
Enter new deveui value, 8 hex numbers lenght (press ENTER to abort):
>> 12345678
Note
If you press Enter before to insert all the keys the procedure will abort. 12345678 is just for example, please contact your Operator in order to know which networkID you have to use. Without the correct networkID you won’t be able to send messages.
Changing deveui register, current value: **001B9954**
Enter new deveui value, 8 hex numbers lenght (press ENTER to abort):
>> 12345678
value changed
Saving modifies, please don't turn off the device...
please wait...
Saving modifies, please don't turn off the device...
please wait...success
Note
If you have to change other values use the appropiate keys. If you want only see the value of the readable register press the key 1
The dark will be rappresented with a low number and a strong light with a high number.
The board has four LEDs:
LED | Color | Brief Note |
1 | Blue | RN2483 GPIO_12 |
2 | Red | RN2483 GPIO_13 |
3 | — | not fitted |
4 | Green | OpenSDA & MBED |
5 | Blue | Firmware status |
This guide is valid if you can choose by yourself the devaddr on the registration device of the Actility webpage. If you want upgrade the firmware to the newest version then go to Quick start guide for firmware 1.4 or major.
In order to see working the Sensor Node Lora you have to register the device on the activity website clicking on Create an account. After the registration login and you will access the main page.
First up we have to register your Microchip RN2483 device, to do this, click on Device Manager arrow to open a new window.
Click the right mouse button on the Devices folder and select + Create.
In this form you have to insert the data we have stored in the RN2483. The following fields are mandatory:
Note
if your board has the Mini-USB connector then the key will be the last 4 less significant bytes from the Device EUI key but the second character will be 8 and not 0. So in this example it will be 081B9954
Optional field but useful:
Then click on the top right + create.
Warning
If some key is wrong then the device will be unable to send data correctly in the Lora network.
After the registration, you can close the window device manager and on the main page go to Logger.
Here you will see all the messages sent by your device. Now take your board:
insert antenna and battery and keeping the board on the table switch on the Lora Sensor Node.
Now the device is in sleeping mode, in 30 seconds it will wake up and it is going to sent a message. For skipping the sleeping phase, press S2 button.
After pressing S2 button you will see the first message sent by your device. Now tilt your board to 90 degrees and wait 30 seconds.
The board will send another message. Now it’s time to see the data sent. Power off the board. And in the logger window, you will have 2 rows, every row is a message received from the server. If you click on the + node you can see the unencrypted data received Payload (hex):. All messages start with the number 18, the other three number couples are the data read from the accelerometer mounted on the board. You will see the data changed when you have tilted the board and sent the second message.
This guide will provide instructions to install the development environment needed to compile and debug the demo firmware of the Sensor Node Lora. The development system is multiplatform, it supports Windows and Linux. This guide is written using Windows. The main steps are:
Hardware required:
Now you are ready to import the project in your KDS.
With the Mini-USB connector you are able to use OpenOCD inteface. It is necessary to install the mbed serial port driver.
Warning
Note
Connector CN4 is not fitted on the lora-node board. It is a connector SMD MALE STRIP 2x5 P1.27mm. You have to fit it in order to debug the board via SWD.
From the release 1.4 you can reset the RN module throught the menu. Follow the next steps:
BAEVTSS002 firmware version 1.5b
RN2483 1.0.1 Dec 15 2015 09:38:06
*** MENU CONFIG RN2483 ***
Enter 0 to print this menu
Enter 1 to see values in DEVEUI and DEVADDR registers
Enter 2 to modify DEVEUI
Enter 3 to modify DEVADDR
Enter 4 to modify APPSKEY
Enter 5 to modify NWKSKEY
Enter 6 to save changes
Enter 7 to Microchip default reset
Enter 8 to Avnet default reset
Enter 9 to exit
Starting Avnet default reset, please don't turnoff the board
Note
with the sources you can build the firmware 1.5b. You can generate the bin file to copy in the mass storage simpy using the Lora.bin
The Kinetis software development kit (KSDK) is an extensive suite of robust hardware interface and hardware abstraction layers, peripheral drivers, RTOS abstractions, stacks, and middleware designed to simplify and accelerate application development on Freescale Kinetis MCUs. The addition of Processor Expert technology for software and board configuration provides unmatched ease of use and flexibility. Included in the Kinetis SDK is full source code under a permissive open-source license for all hardware abstraction and peripheral driver software. Mainline releases include support for a collection of Kinetis MCUs, whereas standalone releases offer support for one or a few additional Kinetis MCUs only. For details read KSDK page.
The board is provided with:
The Microchip RN2483 module provides LoRaWAN™ protocol connectivity using a simple UART interface. The NXP MKLS26Z is connected to the Microchip modules using the configuration 57600 8N1 without using RTS, CTS lines. Last version used is 1.0.1.
The Light Sensor is read from the ADC converter peripheral of the MKL26Z.
The Accelerometer sensor is read from I2C interface.
The microcontroller uses the deep sleep mode VLPS, it is waken up by LPTimer every 30 seconds or by pin interrupt connected to the S2 button.
The connection used by RN2483 is ABP (Activation by Personalization). To use this connection it is required to setup the RN device only one time. Every Lora Sensor Node bought is already configured. The commands used were:
sys factoryRESETsys get hweuimac set deveui [hweui key read]mac set devaddr [last less significant hexs of hweui key]mac set appskey AFBECD56473829100192837465FAEBDCmac set nwkskey [hweui key repeated two times]mac save
After saving this setup is not required repeat the opeation of setup. In order to send data in the Lora network the two used commands are:
Please refer to Avnet Silica website.
This procedure has to be followed only if the MBED mass storage it isn’t recognized when you connect the board to the PC and the MBED drivers are installed in windows. The board uses the MK20 microprocessor in order to implementing the MBED interface. In this guide we will upload the firmware for the MK20. In this way the MBED interface will work again.