Changes for page Switch LoRaWAN server by rejoin feature
Last modified by Xiaoling on 2024/05/20 09:36
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. Xiaoling1 +XWiki.ting - Content
-
... ... @@ -4,21 +4,20 @@ 4 4 5 5 6 6 7 -= 1. Introduction = 8 8 9 9 9 + 10 += 1. introduction = 11 + 10 10 This chapter describes how to switch LoRaWAN server by rejoin feature. 11 11 12 12 13 13 = 2. What is the rejoin feature? = 14 14 15 - 16 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. 17 17 19 +== 2.1offline rejoining （LWS007) == 18 18 19 -== 2.1 Offline Rejoining(LWS007) == 20 - 21 - 22 22 (% style="color:blue" %)**AT Command: AT+DDETECT** 23 23 24 24 AT+DDETECT=<Flag>,<ACK_Timout_1>,<ACK_Timout_2> (Default Value: AT+DDETECT=1,1440,2880) ... ... @@ -64,16 +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. 71 71 67 +* 68 +** 0x01** : Flag** 72 72 70 + **0x05A0 **: ACK_Timout_1 : 1440minutes (24 hours) 73 73 74 - ==2.2ChangeUplink Interval==72 + **0x0B40 **: ACK_Timout_2 : 2880minutes (48 hours) 75 75 74 +* **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 76 76 +== 2.2 Change Uplink Interval == 77 + 77 77 Feature: Change LoRaWAN End Node Transmit Interval. 78 78 79 79 (% style="color:blue" %)**AT Command: AT+TDC** ... ... @@ -108,7 +108,6 @@ 108 108 109 109 = 3. Examples and Explanations = 110 110 111 - 112 112 (% style="color:blue" %)**Switching platforms by rejoin function: Use device LHT65N to switch from TTN to ChirpStack as an example.** 113 113 114 114 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. ... ... @@ -117,7 +117,6 @@ 117 117 118 118 == 3.1 Configure appropriate operation times == 119 119 120 - 121 121 (% 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.**(%%) 122 122 123 123 (% 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.** ... ... @@ -127,7 +127,6 @@ 127 127 128 128 [[image:image-20231123170814-4.png||height="631" width="696"]] 129 129 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: ... ... @@ -168,16 +168,14 @@ 168 168 169 169 == 3.3 Restore the default TDC time and the default offline detection time == 170 170 171 - 172 172 * (% style="color:blue" %)**It is recommended to restore the factory reset directly:** 173 173 174 -(% style="color:red" %)** Downlink payload: 0x04FE**171 +(% style="color:red" %)** downlink payload: 0x04FE** 175 175 176 176 [[image:image-20231124114451-10.png||height="377" width="826"]] 177 177 178 178 [[image:image-20231124115256-11.png||height="409" width="767"]] 179 179 180 - 181 181 After the delivery is successful, the node is connected to the network again and factory Settings are restored. 182 182 183 183 [[image:image-20231124141041-1.png||height="395" width="801"]]