Skip to Content
Last modified by Xiaoling on 2024/05/20 09:36
From version 22.1
edited by Mengting Qiu
on 2023/11/24 11:52
Change comment: Uploaded new attachment "image-20231124115256-11.png", version {1}
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
... ... @@ -4,19 +4,19 @@
4 4  
5 5  
6 6  
7 += 1. Introduction =
7 7  
8 8  
10 +This chapter describes how to switch LoRaWAN server by rejoin feature.
9 9  
10 -= 1. introduction =
11 11  
12 -This chapter describes switch LoRaWAN server by rejoin feature.
13 += 2. What is the rejoin feature? =
13 13  
14 14  
15 -= 2. What is the rejoin feature? =
16 +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.
16 16  
17 -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.
18 18  
19 -== 2.1offline rejoining （LWS007) ==
19 +== 2.1 Offline Rejoining(LWS007) ==
20 20  
21 21  
22 22  (% style="color:blue" %)**AT Command: AT+DDETECT**
... ... @@ -64,21 +64,18 @@
64 64  If the downlink payload=320105A00B40, it means set end node to use confirm mode, while type code is 32.
65 65  
66 66  * **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.
67 67  
68 -*
69 -** 0x01** : Flag**
70 70  
71 - **0x05A0 **: ACK_Timout_1 : 1440minutes (24 hours)
72 72  
73 - **0x0B40 **: ACK_Timout_2 : 2880minutes (48 hours)
74 -
75 -* **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.
76 -
77 77  == 2.2 Change Uplink Interval ==
78 78  
76 +
79 79  Feature: Change LoRaWAN End Node Transmit Interval.
80 80  
81 -
82 82  (% style="color:blue" %)**AT Command: AT+TDC**
83 83  
84 84  (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:727.222px" %)
... ... @@ -111,6 +111,7 @@
111 111  
112 112  = 3. Examples and Explanations =
113 113  
111 +
114 114  (% style="color:blue" %)**Switching platforms by rejoin function: Use device LHT65N to switch from TTN to ChirpStack as an example.**
115 115  
116 116  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.
... ... @@ -119,6 +119,7 @@
119 119  
120 120  == 3.1 Configure appropriate operation times ==
121 121  
120 +
122 122  (% 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.**(%%) 
123 123  
124 124  (% 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.**
... ... @@ -128,6 +128,7 @@
128 128  
129 129  [[image:image-20231123170814-4.png||height="631" width="696"]]
130 130  
130 +
131 131  (% 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.**
132 132  
133 133  TDC changed successfully:
... ... @@ -149,32 +149,57 @@
149 149  == 3.2 Delete the device and add the device to the new platform ==
150 150  
151 151  
152 +Delete device：
152 152  
154 +[[image:image-20231124104002-3.png||height="302" width="653"]]
153 153  
156 +[[image:image-20231124104014-4.png||height="210" width="654"]]
154 154  
155 155  
159 +Register the device on the new platform and wait for the offline detection time for the device to automatically request to join the network.
156 156  
161 +[[image:image-20231124112845-8.png||height="449" width="935"]]
157 157  
163 +[[image:image-20231124113011-9.png||height="450" width="935"]]
158 158  
165 +[[image:image-20231124111630-6.png||height="537" width="813"]]
159 159  
160 160  
161 161  
169 +== 3.3 Restore the default TDC time and the default offline detection time ==
162 162  
163 163  
172 +* (% style="color:blue" %)**It is recommended to restore the factory reset directly:**
164 164  
174 +(% style="color:red" %)** Downlink payload: 0x04FE**
165 165  
176 + [[image:image-20231124114451-10.png||height="377" width="826"]]
166 166  
178 +[[image:image-20231124115256-11.png||height="409" width="767"]]
167 167  
168 168  
181 +After the delivery is successful, the node is connected to the network again and factory Settings are restored.
169 169  
183 +[[image:image-20231124141041-1.png||height="395" width="801"]]
170 170  
185 +[[image:image-20231124141141-2.png||height="460" width="802"]]
171 171  
172 172  
188 +* (% style="color:blue" %)**If the device has other configurations to keep, users can also choose to configure the default TDC and default offline detection time separately.**
173 173  
190 +[[image:image-20231124142829-4.png||height="451" width="626"]]
174 174  
175 175  
193 +[[image:image-20231124142645-3.png||height="452" width="622"]]
176 176  
177 177  
196 +(% style="color:red" %)**Note: To set these two commands separately, users must restore the default offline detection time before configuring the default TDC time.**
178 178  
179 179  
199 +
200 +
201 +
202 +
203 +
204 +
180 180  
image-20231124141041-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +40.3 KB
Content
image-20231124141141-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +68.5 KB
Content
image-20231124142645-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +38.3 KB
Content
image-20231124142829-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.6 KB
Content