Changes for page LoRaWAN Sensors in two different LoRaWAN Network
Last modified by Xiaoling on 2022/07/13 11:08
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Edwin1 +XWiki.Xiaoling - Content
-
... ... @@ -1,10 +1,13 @@ 1 -{{box cssClass="floatinginfobox" title="**Contents**"}} 1 +(% class="wikigeneratedid" %) 2 +**Table of Contents:** 3 + 2 2 {{toc/}} 3 -{{/box}} 4 4 5 -(% class="wikigeneratedid" %) 6 -= LoRaWAN Join Mode = 7 7 7 + 8 += 1. LoRaWAN Join Mode = 9 + 10 + 8 8 There are two different Join Mode: ABP and OTAA. Here are the differences between them: 9 9 10 10 [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/end-device-activation/ >>https://www.thethingsnetwork.org/docs/lorawan/end-device-activation/]] ... ... @@ -13,8 +13,9 @@ 13 13 Most cases we use for LoRaWAN sensors are OTAA mode., which is also the default mode for Dragino Sensors. 14 14 15 15 16 -= LoRaWAN OTAA Activation = 19 += 2. LoRaWAN OTAA Activation = 17 17 21 + 18 18 According to the activation photo as below. 19 19 20 20 The APPSKEY & NwksKey are generated during each activation. These two keys are used for further communication with LoRaWAN server. ... ... @@ -24,8 +24,10 @@ 24 24 [[image:image-20220526141011-1.png]] 25 25 26 26 27 -= LoRaWAN ABP Activation = 28 28 32 += 3. LoRaWAN ABP Activation = 33 + 34 + 29 29 ABP activation no need communication between End Device and LoRaWAN server. As long as End Device and NS has the same keys (NekSkey, AppSKey, DevAddr) , NS can get the package from End Device. 30 30 31 31 [[image:image-20220526141805-2.png]]