Wiki source code of Switch LoRaWAN server by rejoin feature
Version 3.3 by Mengting Qiu on 2023/10/27 17:10
Hide last authors
| author | version | line-number | content |
|---|---|---|---|
 |
1.3 | 1 | **Table of Contents:** |
| |
1.2 | 2 | |
| |
1.1 | 3 | {{toc/}} |
| 4 | |||
| 5 | |||
| 6 | |||
| 7 | |||
| 8 | |||
| 9 | |||
| |
2.2 | 10 | = 1. introduction = |
| |
3.2 | 11 | |
| |
3.3 | 12 | This chapter describes switch LoRaWAN server by rejoin feature. |
| |
3.2 | 13 | |
| 14 | |||
| 15 | = 2. What is the rejoin feature? = | ||
| 16 | |||
| |
3.3 | 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. |
| |
3.2 | 18 | |
| |
3.3 | 19 | == offline rejoining （LWS007) == |
| |
3.2 | 20 | |
| 21 | |||
| 22 | (% style="color:blue" %)**AT Command: AT+DDETECT** | ||
| 23 | |||
| 24 | AT+DDETECT=<Flag>,<ACK_Timout_1>,<ACK_Timout_2> (Default Value: AT+DDETECT=1,1440,2880) | ||
| 25 | |||
| 26 | * ACK_Timout_1: Unit: min | ||
| 27 | |||
| 28 | * ACK_Timout_2: Unit: min | ||
| 29 | |||
| 30 | (% border="1" style="background-color:#f2f2f2; width:562px" %) | ||
| 31 | |(% style="background-color:#4f81bd; color:white; width:160px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:272px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:89px" %)**Response** | ||
| 32 | |(% style="width:160px" %)((( | ||
| 33 | AT+DDETECT=1,1440,2880 | ||
| 34 | |||
| 35 | value1 | ||
| 36 | )))|(% style="width:272px" %)Enable online detect|(% style="width:89px" %)((( | ||
| 37 | 1 | ||
| 38 | |||
| 39 | OK | ||
| 40 | ))) | ||
| 41 | |(% style="width:160px" %)((( | ||
| 42 | AT+DDETECT=1,?,2880 | ||
| 43 | |||
| 44 | value2 | ||
| 45 | )))|(% style="width:272px" %)Online detection packet sending time|(% style="width:89px" %)((( | ||
| 46 | |||
| 47 | |||
| 48 | OK | ||
| 49 | ))) | ||
| 50 | |(% style="width:160px" %)((( | ||
| 51 | AT+DDETECT=1,1440,？ | ||
| 52 | |||
| 53 | value3 | ||
| 54 | )))|(% style="width:272px" %)Process rejoin|(% style="width:89px" %)((( | ||
| 55 | |||
| 56 | |||
| 57 | OK | ||
| 58 | ))) | ||
| 59 | |||
| 60 | (% style="color:blue" %)**Downlink Command: 0x32** | ||
| 61 | |||
| 62 | Format: Command Code (0x32) followed by 2 bytes mode value. | ||
| 63 | |||
| 64 | If the downlink payload=320105A00B40, it means set end node to use confirm mode, while type code is 32. | ||
| 65 | |||
| 66 | * **Example 1:** Downlink Payload: 320105A00B40 ~/~/ Set AT+DDETECT=1,1440,2880 | ||
| 67 | |||
| 68 | * | ||
| 69 | ** 0x01** : Flag** | ||
| 70 | |||
| 71 | **0x05A0 **: ACK_Timout_1 : 1440minutes (24 hours) | ||
| 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 | (% style="display:none" %) (%%) | ||
| 78 | |||
| 79 | |||
| 80 | |||
| 81 | |||
| 82 | |||
| 83 | |||
| 84 | |||
| 85 | |||
| 86 | |||
| 87 | |||
| 88 | |||
| 89 | |||
| 90 | |||
| 91 |