Skip to Content
Last modified by Xiaoling on 2024/05/20 09:36
From version 30.1
edited by Mengting Qiu
on 2023/11/24 14:43
Change comment: There is no comment for this version
To version 30.2
edited by Xiaoling
on 2024/05/20 09:25
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -6,15 +6,19 @@
6 6  
7 7  = 1. Introduction =
8 8  
9 +
9 9  This chapter describes how to switch LoRaWAN server by rejoin feature.
10 10  
11 11  
12 12  = 2. What is the rejoin feature? =
13 13  
15 +
14 14  Rejoin feature is that if the ACK packet sent by the platform to the node is not received within the set time range, the offline detection will be started.
15 15  
16 -== 2.1 Offline Rejoining （LWS007) ==
17 17  
19 +== 2.1 Offline Rejoining(LWS007) ==
20 +
21 +
18 18  (% style="color:blue" %)**AT Command: AT+DDETECT**
19 19  
20 20  AT+DDETECT=<Flag>,<ACK_Timout_1>,<ACK_Timout_2> (Default Value: AT+DDETECT=1,1440,2880)
... ... @@ -60,18 +60,16 @@
60 60  If the downlink payload=320105A00B40, it means set end node to use confirm mode, while type code is 32.
61 61  
62 62  * **Example 1:** Downlink Payload: 320105A00B40  ~/~/ Set AT+DDETECT=1,1440,2880
67 +** **0x01 : **Flag
68 +** **0x05A0 **: ACK_Timout_1 : 1440minutes (24 hours)
69 +** **0x0B40 **: ACK_Timout_2 : 2880minutes (48 hours)
70 +* **Explain**: Enable Online Detect, if end node doesn't receive any downlink within ACK_Timout_1( 1440 minutes or 24 hours). End node will use confirmed uplink to send packets during ACK_Timout_1 (the 24th hour) to ACK_Timout_2 ( the 48th hour). If from the 24th to 48th hour, end node got an downlink from server, it will switch back to unconfirmed uplink. end node will restart ACK_Timout_1. If from the 24th to 48th hour, end node still not got any downlink, means device doesn't get ACK from server within last 48 hours. Device will process rejoin, rejoin request interval is AT+RJTDC period. For AU915/ US915, device will use the sub-band used for last join.
63 63  
64 -*
65 -** 0x01** : Flag**
66 66  
67 - **0x05A0 **: ACK_Timout_1 : 1440minutes (24 hours)
68 68  
69 - **0x0B40 **: ACK_Timout_2 : 2880minutes (48 hours)
70 -
71 -* **Explain**: Enable Online Detect, if end node doesn't receive any downlink within ACK_Timout_1( 1440 minutes or 24 hours). End node will use confirmed uplink to send packets during ACK_Timout_1 (the 24th hour) to ACK_Timout_2 ( the 48th hour). If from the 24th to 48th hour, end node got an downlink from server, it will switch back to unconfirmed uplink. end node will restart ACK_Timout_1. If from the 24th to 48th hour, end node still not got any downlink, means device doesn't get ACK from server within last 48 hours. Device will process rejoin, rejoin request interval is AT+RJTDC period. For AU915/ US915, device will use the sub-band used for last join.
72 -
73 73  == 2.2 Change Uplink Interval ==
74 74  
76 +
75 75  Feature: Change LoRaWAN End Node Transmit Interval.
76 76  
77 77  (% style="color:blue" %)**AT Command: AT+TDC**
... ... @@ -106,6 +106,7 @@
106 106  
107 107  = 3. Examples and Explanations =
108 108  
111 +
109 109  (% style="color:blue" %)**Switching platforms by rejoin function: Use device LHT65N to switch from TTN to ChirpStack as an example.**
110 110  
111 111  The following example shows the parameters of the LHT65N. Users need to check the Wiki instructions to confirm the parameters of the equipment they have purchased.
... ... @@ -114,6 +114,7 @@
114 114  
115 115  == 3.1 Configure appropriate operation times ==
116 116  
120 +
117 117  (% style="color:blue" %)**Firstly, the user sent downlink commands through the original registration platform (TTN) to modify the required TDC time and offline detection time.**(%%) 
118 118  
119 119  (% style="color:red" %)**Note: Users need to set the TDC time shorter than the offline detection ACK_Timeout_1, the best offline detection time is more than twice the TDC time.**
... ... @@ -123,6 +123,7 @@
123 123  
124 124  [[image:image-20231123170814-4.png||height="631" width="696"]]
125 125  
130 +
126 126  (% style="color:red" %)**Note: When configuring the device using downlink commands, you need to wait for the original TDC time, and the platform plans downlink after the end node complete uplink.**
127 127  
128 128  TDC changed successfully:
... ... @@ -163,6 +163,7 @@
163 163  
164 164  == 3.3 Restore the default TDC time and the default offline detection time ==
165 165  
171 +
166 166  * (% style="color:blue" %)**It is recommended to restore the factory reset directly:**
167 167  
168 168  (% style="color:red" %)** Downlink payload: 0x04FE**