Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 32.15
edited by Xiaoling
on 2022/07/13 15:36
Change comment: There is no comment for this version
To version 4.5
edited by Xiaoling
on 2022/05/11 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,10 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 8  
9 -
10 10  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
11 11  \\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
12 12  
... ... @@ -16,48 +16,46 @@
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17 17  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
18 18  
17 +**~1. End Device Join Screen shot, we can check:**
19 19  
20 -
21 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 -
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526164956-15.png]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
30 30  
31 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
27 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
32 32  
33 33  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34 34  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
35 35  
36 -[[image:image-20220526163608-2.png]]
32 +[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
37 37  
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
40 40  
41 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
37 +**3. Gateway Traffic Page in LoRaWAN Server**
42 42  
43 43  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
44 44  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
45 45  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
46 46  
47 -[[image:image-20220526163633-3.png]]
43 +[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
48 48  
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
51 51  
52 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
48 +**4. Data Page in LoRaWAN server**
53 53  
54 54  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
55 55  
56 -[[image:image-20220526163704-4.png]]
52 +[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
57 57  
58 58  The data for the end device set in server
59 59  
60 -[[image:image-20220526163732-5.png]]
56 +[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
61 61  
62 62  Check if OTAA Keys match the keys in device
63 63  
... ... @@ -64,7 +64,6 @@
64 64  
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
67 -
68 68  (((
69 69  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
70 70  )))
... ... @@ -99,21 +99,18 @@
99 99  Here are the freuqency tables for these bands as reference:
100 100  )))
101 101  
102 -[[image:image-20220526163801-6.png]]
97 +[[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
103 103  
104 104  US915 Channels
105 105  
106 -[[image:image-20220526163926-7.png]]
101 +[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
107 107  
108 108  AU915 Channels
109 109  
105 +[[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png||height="205" width="600"]]
110 110  
111 -[[image:image-20220526163941-8.png]]
112 -
113 113  (((
114 114  CN470 Channels
115 -
116 -
117 117  )))
118 118  
119 119  (((
... ... @@ -120,12 +120,10 @@
120 120  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
121 121  )))
122 122  
123 -[[image:image-20220526164052-9.png]]
115 +[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
124 124  
125 125  (((
126 126  TTN FREQUENCY PLAN
127 -
128 -
129 129  )))
130 130  
131 131  (((
... ... @@ -135,7 +135,6 @@
135 135  
136 136  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
137 137  
138 -
139 139  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
140 140  
141 141  * **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
... ... @@ -157,7 +157,6 @@
157 157  
158 158  = 4. Transmision on ABP Mode =
159 159  
160 -
161 161  (((
162 162  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
163 163  )))
... ... @@ -178,7 +178,7 @@
178 178  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
179 179  )))
180 180  
181 -[[image:image-20220526164508-10.png]]
169 +[[~[~[image:https://wiki.dragino.com/images/thumb/1/19/ABP_Issue-1.jpg/600px-ABP_Issue-1.jpg~|~|height="340" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:ABP_Issue-1.jpg]]
182 182  
183 183  Disable Frame Counter Check in ABP Mode
184 184  
... ... @@ -187,7 +187,6 @@
187 187  
188 188  == 5.1 How it work ==
189 189  
190 -
191 191  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
192 192  
193 193  (((
... ... @@ -194,11 +194,10 @@
194 194  Depends on Class A or Class C, the receive windows will be a little difference,
195 195  )))
196 196  
197 -[[image:image-20220531161828-1.png]]
184 +[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
198 198  
199 199  receive windows for Class A and Class C
200 200  
201 -
202 202  Below are the requirement for the End Device to receive the packets.
203 203  
204 204  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -205,31 +205,19 @@
205 205  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
206 206  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
207 207  * This packet must match the frequency of the RX1 or RX2 window.
208 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
194 +* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
209 209  
210 -
211 -
212 -
213 213  == 5.2 See Debug Info ==
214 214  
198 +**For LoRaWAN Server**
215 215  
216 -(((
217 -(% style="color:blue" %)**For LoRaWAN Server**
218 -)))
219 -
220 -(((
221 221  We can check if there is downlink message for this end node, use TTN for example:
222 -)))
223 223  
224 -(((
225 225  Configure a downstream to the end device
226 -)))
227 227  
228 -[[image:image-20220526164623-12.png]]
204 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
229 229  
230 -(((
231 231  Set a downstream in TTN and see it is sent
232 -)))
233 233  
234 234  
235 235  (((
... ... @@ -236,92 +236,96 @@
236 236  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
237 237  )))
238 238  
239 -[[image:image-20220526164650-13.png]]
213 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
240 240  
241 -(((
242 242  Gateway Traffic can see this downstream info
243 -)))
244 244  
245 245  
246 -(((
247 -(% style="color:blue" %)**For LoRaWAN Gateway**
248 -)))
218 +**For LoRaWAN Gateway**
249 249  
250 250  (((
251 251  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
252 252  )))
253 253  
254 -[[image:image-20220526164734-14.png]]
224 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
255 255  
256 -(((
257 257  Gateway Sent out this packet
227 +
228 +
229 +**For End Node**
230 +
231 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 +
233 +(% class="box infomessage" %)
234 +(((
235 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
258 258  )))
259 259  
238 +(% class="box infomessage" %)
239 +(((
240 + AT+RX2DR=3 ~-~--> The RX2 DataRate
241 +)))
260 260  
243 +(% class="box infomessage" %)
261 261  (((
262 -(% style="color:blue" %)**For End Node**
245 + AT+RX1DL=1000 ~-~--> Receive Delay 1
263 263  )))
264 264  
248 +(% class="box infomessage" %)
265 265  (((
266 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
250 + AT+RX2DL=2000 ~-~--> Receive Delay 2
267 267  )))
268 268  
269 269  (((
270 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
271 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
272 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
273 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
254 +**when the device running, we can see below info:**
255 +)))
274 274  
257 +(((
275 275  
276 276  )))
277 277  
261 +(% class="box" %)
278 278  (((
279 -(% style="color:blue" %)**when the device running, we can see below info:**
263 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
264 + [12503]TX on freq 868500000 Hz at DR 0
265 + [13992]txDone
266 + [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
267 + [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
268 + [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
269 + [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
280 280  )))
281 281  
282 -{{{ [12502]***** UpLinkCounter= 0 *****
283 - [12503]TX on freq 868500000 Hz at DR 0
284 - [13992]txDone
285 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
286 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
287 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
288 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
289 -
290 290  (((
291 291  
292 292  )))
293 293  
294 294  (((
295 -(% style="color:blue" %)**Another message:**
277 +**Another message:**
296 296  )))
297 297  
298 -{{{ [12502]***** UpLinkCounter= 0 *****
299 - [12503]TX on freq 868100000 Hz at DR 0
300 - [13992]txDone
301 - [15022]RX on freq 868100000 Hz at DR 0
302 - [15222]rxTimeOut
303 - [15987]RX on freq 869525000 Hz at DR 3
304 - [16185]rxDone --> We have got the downstream packet.
305 - Rssi= -64
306 - Receive data
307 - 1:0012345678}}}
308 308  
281 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
282 + [12503]TX on freq 868100000 Hz at DR 0
283 + [13992]txDone
284 + [15022]RX on freq 868100000 Hz at DR 0
285 + [15222]rxTimeOut
286 + [15987]RX on freq 869525000 Hz at DR 3
287 + [16185]rxDone                              ~-~-> We have got the downstream packet.
288 + Rssi= -64
289 + Receive data
290 + 1:0012345678
309 309  
310 -== 5.3 If problem doesn't solve ==
292 +== 5.3 If problem doesn’t solve ==
311 311  
294 +**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
312 312  
313 -(% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
314 -
315 315  * End node console to show the transmit freuqency and DR.
316 316  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
317 317  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
318 318  * End Node traffic (from server UI) to shows end node activity in server.
319 319  
320 -
321 -
322 322  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
323 323  
324 -
325 325  (((
326 326  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
327 327  )))
... ... @@ -334,10 +334,8 @@
334 334  So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below:
335 335  )))
336 336  
337 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
338 -
339 339  (((
340 -
316 +Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
341 341  )))
342 342  
343 343  (((
... ... @@ -347,29 +347,35 @@
347 347  
348 348  = 7. Decrypt a LoRaWAN Packet =
349 349  
326 +~1. LHT65 End device configure:
350 350  
351 -(% style="color:blue" %)**1. LHT65 End device configure:**
328 +(% class="box infomessage" %)
329 +(((
330 +Change to ABP Mode: AT+NJM=0
331 +)))
352 352  
353 -**Change to ABP Mode:  AT+NJM=0**
354 -**Change to fix frequency:  AT+CHS=904900000**
355 -**Change to fix DR:  AT+DR=0**
333 +(% class="box infomessage" %)
334 +(((
335 +Change to fix frequency: AT+CHS=904900000
336 +)))
356 356  
338 +(% class="box infomessage" %)
339 +(((
340 +Change to fix DR: AT+DR=0
341 +)))
357 357  
358 -[[image:image-20220526165525-16.png]]
343 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
359 359  
345 +2. In LG02 , configure to receive above message
360 360  
361 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
347 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
362 362  
363 -[[image:image-20220526165612-17.png]]
364 -
365 -
366 366  In LG02 console, we can see the hex receive are:
367 367  
368 -[[image:image-20220526171112-21.png]]
351 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
369 369  
353 +3. Decode the info in web
370 370  
371 -(% style="color:blue" %)**3. Decode the info in web**
372 -
373 373  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
374 374  
375 375  Need these three fields:
... ... @@ -380,145 +380,45 @@
380 380  
381 381  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
382 382  
383 -
384 384  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
385 385  
386 -[[image:image-20220526171029-20.png]]
367 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
387 387  
388 -(((
389 - The FRMPayload is the device payload.
390 -)))
369 +The FRMPayload is the device payload.
391 391  
392 392  
393 393  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
394 394  
395 -
396 396  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
397 397  
398 -
399 399  = 9. Why do I see a "MIC Mismatch" error message from the server? =
400 400  
378 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
401 401  
402 -(((
403 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
404 -)))
405 -
406 -(((
407 407  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
408 -)))
409 409  
410 -* (((
411 -Please note the distinction between "APPKEY" and "APPSKEY".
412 -)))
382 +* Please note the distinction between "APPKEY" and "APPSKEY".
413 413  
414 -(((
415 415  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
416 -)))
417 417  
418 -(((
419 419  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
420 -)))
421 421  
422 -* (((
423 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
388 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
424 424  
425 -
426 -
427 -
428 -)))
429 -
430 430  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
431 431  
432 -
433 433  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
434 434  
435 -(((
436 436  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
437 -)))
438 438  
439 -(((
440 -When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
441 -)))
396 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,
442 442  
443 -* (((
444 -Solution: Use the decoder to filter out this 00 packet.
445 -)))
446 -* (((
447 -Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
398 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
448 448  
400 +so it will send a normal uplink packet, and an additional 00 data packet.
449 449  
402 +* Solution: Use the decoder to filter out this 00 packet.
403 +* Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
450 450  
405 +(% class="wikigeneratedid" id="H" %)
451 451  
452 -)))
453 -
454 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
455 -
456 -
457 -(((
458 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
459 -)))
460 -
461 -(((
462 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
463 -)))
464 -
465 -(((
466 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
467 -)))
468 -
469 -(((
470 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
471 -)))
472 -
473 -(((
474 -AT+APPEUI=00 00 00 00 00 00 00 00
475 -)))
476 -
477 -(((
478 -
479 -)))
480 -
481 -(((
482 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
483 -)))
484 -
485 -(((
486 -You can rewrites the keys by running commands in AT Console
487 -
488 -
489 -)))
490 -
491 -(((
492 -**For example：**
493 -)))
494 -
495 -(((
496 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
497 -)))
498 -
499 -(((
500 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
501 -)))
502 -
503 -(((
504 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
505 -)))
506 -
507 -(((
508 -AT+APPEUI=2C 45 47 E3 24 12 23 24
509 -)))
510 -
511 -(((
512 -(Any combination of 16 bit codes can be used）
513 -
514 -
515 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
516 -)))
517 -
518 -
519 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
520 -
521 -
522 -
523 -(% class="wikigeneratedid" %)
524 -
image-20220526163523-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content