Show last authors
1 **Table of Contents:**
2
3 {{toc/}}
4
5
6
7 = 1. Introduction =
8
9
10 This chapter describes how to switch LoRaWAN server by rejoin feature.
11
12
13 = 2. What is the rejoin feature? =
14
15
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
18
19 == 2.1 Offline Rejoining(LWS007) ==
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 ** **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
72
73
74 == 2.2 Change Uplink Interval ==
75
76
77 Feature: Change LoRaWAN End Node Transmit Interval.
78
79 (% style="color:blue" %)**AT Command: AT+TDC**
80
81 (% border="1" cellspacing="4" style="background-color:#f2f2f2; width:727.222px" %)
82 |(% style="background-color:#4f81bd; color:white; width:165px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:227px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:329px" %)**Response**
83 |(% style="width:165px" %)AT+TDC=?|(% style="width:227px" %)Show current transmit Interval|(% style="width:329px" %)30000(((
84 OK
85
86 the interval is 30000ms = 30s
87 )))
88 |(% style="width:165px" %)AT+TDC=60000|(% style="width:227px" %)Set Transmit Interval|(% style="width:329px" %)OK(((
89 Set transmit interval to 60000ms = 60 seconds
90 )))
91
92 (((
93 (% style="color:blue" %)**Downlink Command: 0x01**
94
95 Format: Command Code (0x01) followed by 3 bytes time value.
96 )))
97
98 (((
99 If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
100 )))
101
102 * **Example 1**: Downlink Payload:** 0100001E**  ~/~/ Set Transmit Interval (TDC) = 30 seconds
103
104 * **Example 2**: Downlink Payload:** 0100003C**  ~/~/ Set Transmit Interval (TDC) = 60 seconds
105
106 (% style="display:none" %) (%%)
107
108
109 = 3. Examples and Explanations =
110
111
112 (% style="color:blue" %)**Switching platforms by rejoin function: Use device LHT65N to switch from TTN to ChirpStack as an example.**
113
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.
115 ([[User Manual for LoRaWAN End Nodes)>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes]])
116
117
118 == 3.1 Configure appropriate operation times ==
119
120
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
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.**
124
125
126 * Configuration via TTN downlink:
127
128 [[image:image-20231123170814-4.png||height="631" width="696"]]
129
130
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
133 TDC changed successfully:
134
135 [[image:image-20231124102601-1.png||height="543" width="617"]]
136
137
138 Confirm that the TDC configuration is successful, and then configure the offline detection time:
139
140
141 [[image:image-20231123170339-2.png||height="566" width="715"]]
142
143
144 * Configure using the AT commands by Serial Port Utility:
145
146 [[image:image-20231124103318-2.png||height="538" width="738"]]
147
148
149 == 3.2 Delete the device and add the device to the new platform ==
150
151
152 Delete device:
153
154 [[image:image-20231124104002-3.png||height="302" width="653"]]
155
156 [[image:image-20231124104014-4.png||height="210" width="654"]]
157
158
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.
160
161 [[image:image-20231124112845-8.png||height="449" width="935"]]
162
163 [[image:image-20231124113011-9.png||height="450" width="935"]]
164
165 [[image:image-20231124111630-6.png||height="537" width="813"]]
166
167
168
169 == 3.3 Restore the default TDC time and the default offline detection time ==
170
171
172 * (% style="color:blue" %)**It is recommended to restore the factory reset directly:**
173
174 (% style="color:red" %)** Downlink payload: 0x04FE**
175
176 [[image:image-20231124114451-10.png||height="377" width="826"]]
177
178 [[image:image-20231124115256-11.png||height="409" width="767"]]
179
180
181 After the delivery is successful, the node is connected to the network again and factory Settings are restored.
182
183 [[image:image-20231124141041-1.png||height="395" width="801"]]
184
185 [[image:image-20231124141141-2.png||height="460" width="802"]]
186
187
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.**
189
190 [[image:image-20231124142829-4.png||height="451" width="626"]]
191
192
193 [[image:image-20231124142645-3.png||height="452" width="622"]]
194
195
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.**
197
198
199
200
201
202
203
204
205
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0