Skip to Content
Last modified by Xiaoling on 2022/07/13 11:08
From version 3.2
edited by Xiaoling
on 2022/07/13 11:07
Change comment: There is no comment for this version
To version 3.1
edited by Edwin Chen
on 2022/05/26 14:19
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,13 +1,10 @@
1 -(% class="wikigeneratedid" %)
2 -**Table of Contents:**
3 -
1 +{{box cssClass="floatinginfobox" title="**Contents**"}}
4 4  {{toc/}}
3 +{{/box}}
5 5  
5 +(% class="wikigeneratedid" %)
6 += LoRaWAN Join Mode =
6 6  
7 -
8 -= 1.  LoRaWAN Join Mode =
9 -
10 -
11 11  There are two different Join Mode: ABP and OTAA. Here are the differences between them:
12 12  
13 13  [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/end-device-activation/ >>https://www.thethingsnetwork.org/docs/lorawan/end-device-activation/]]
... ... @@ -16,9 +16,8 @@
16 16  Most cases we use for LoRaWAN sensors are OTAA mode., which is also the default mode for Dragino Sensors.
17 17  
18 18  
19 -= 2.  LoRaWAN OTAA Activation =
16 += LoRaWAN OTAA Activation =
20 20  
21 -
22 22  According to the activation photo as below.
23 23  
24 24  The APPSKEY & NwksKey are generated during each activation. These two keys are used for further communication with LoRaWAN server.
... ... @@ -28,10 +28,8 @@
28 28  [[image:image-20220526141011-1.png]]
29 29  
30 30  
27 += LoRaWAN ABP Activation =
31 31  
32 -= 3.  LoRaWAN ABP Activation =
33 -
34 -
35 35  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.
36 36  
37 37  [[image:image-20220526141805-2.png]]