Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 32.16
edited by Xiaoling
on 2022/08/12 11:06
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,57 +16,52 @@
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  
27 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 31  
32 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
33 -
34 34  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
35 35  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
36 36  
37 -[[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"]]
38 38  
39 39  Console Output from Gateway to see packets between end node and server.
40 40  
41 41  
42 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
37 +**3. Gateway Traffic Page in LoRaWAN Server**
43 43  
44 44  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
45 45  * 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.
46 46  * 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.
47 47  
48 -[[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"]]
49 49  
50 50  The Traffic for the End node in the server, use TTN as example
51 51  
52 52  
53 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
48 +**4. Data Page in LoRaWAN server**
54 54  
55 55  * 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.
56 56  
57 -[[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"]]
58 58  
59 59  The data for the end device set in server
60 60  
61 -[[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"]]
62 62  
63 63  Check if OTAA Keys match the keys in device
64 64  
65 65  
66 -
67 67  = 2. Notice of US915/CN470/AU915 Frequency band =
68 68  
69 -
70 70  (((
71 71  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
72 72  )))
... ... @@ -101,21 +101,18 @@
101 101  Here are the freuqency tables for these bands as reference:
102 102  )))
103 103  
104 -[[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"]]
105 105  
106 106  US915 Channels
107 107  
108 -[[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"]]
109 109  
110 110  AU915 Channels
111 111  
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"]]
112 112  
113 -[[image:image-20220526163941-8.png]]
114 -
115 115  (((
116 116  CN470 Channels
117 -
118 -
119 119  )))
120 120  
121 121  (((
... ... @@ -122,12 +122,10 @@
122 122  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.
123 123  )))
124 124  
125 -[[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"]]
126 126  
127 127  (((
128 128  TTN FREQUENCY PLAN
129 -
130 -
131 131  )))
132 132  
133 133  (((
... ... @@ -135,10 +135,8 @@
135 135  )))
136 136  
137 137  
138 -
139 139  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
140 140  
141 -
142 142  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:
143 143  
144 144  * **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.
... ... @@ -158,10 +158,8 @@
158 158  )))
159 159  
160 160  
161 -
162 162  = 4. Transmision on ABP Mode =
163 163  
164 -
165 165  (((
166 166  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.
167 167  )))
... ... @@ -182,17 +182,15 @@
182 182  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
183 183  )))
184 184  
185 -[[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]]
186 186  
187 187  Disable Frame Counter Check in ABP Mode
188 188  
189 189  
190 -
191 191  = 5. Downstream Debug =
192 192  
193 193  == 5.1 How it work ==
194 194  
195 -
196 196  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.
197 197  
198 198  (((
... ... @@ -199,11 +199,10 @@
199 199  Depends on Class A or Class C, the receive windows will be a little difference,
200 200  )))
201 201  
202 -[[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"]]
203 203  
204 204  receive windows for Class A and Class C
205 205  
206 -
207 207  Below are the requirement for the End Device to receive the packets.
208 208  
209 209  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -210,31 +210,19 @@
210 210  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
211 211  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 212  * This packet must match the frequency of the RX1 or RX2 window.
213 -* 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.**
214 214  
215 -
216 -
217 -
218 218  == 5.2 See Debug Info ==
219 219  
198 +**For LoRaWAN Server**
220 220  
221 -(((
222 -(% style="color:blue" %)**For LoRaWAN Server**
223 -)))
224 -
225 -(((
226 226  We can check if there is downlink message for this end node, use TTN for example:
227 -)))
228 228  
229 -(((
230 230  Configure a downstream to the end device
231 -)))
232 232  
233 -[[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"]]
234 234  
235 -(((
236 236  Set a downstream in TTN and see it is sent
237 -)))
238 238  
239 239  
240 240  (((
... ... @@ -241,99 +241,96 @@
241 241  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
242 242  )))
243 243  
244 -[[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"]]
245 245  
246 -(((
247 247  Gateway Traffic can see this downstream info
248 -)))
249 249  
250 250  
218 +**For LoRaWAN Gateway**
251 251  
252 252  (((
253 -(% style="color:blue" %)**For LoRaWAN Gateway**
254 -)))
255 -
256 -(((
257 257  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:
258 258  )))
259 259  
260 -[[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"]]
261 261  
262 -(((
263 263  Gateway Sent out this packet
264 -)))
265 265  
266 266  
229 +**For End Node**
267 267  
231 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 +
233 +(% class="box infomessage" %)
268 268  (((
269 -(% style="color:blue" %)**For End Node**
235 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
270 270  )))
271 271  
238 +(% class="box infomessage" %)
272 272  (((
273 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
240 + AT+RX2DR=3 ~-~--> The RX2 DataRate
274 274  )))
275 275  
243 +(% class="box infomessage" %)
276 276  (((
277 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
278 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
279 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
280 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
245 + AT+RX1DL=1000 ~-~--> Receive Delay 1
246 +)))
281 281  
248 +(% class="box infomessage" %)
249 +(((
250 + AT+RX2DL=2000 ~-~--> Receive Delay 2
251 +)))
282 282  
253 +(((
254 +**when the device running, we can see below info:**
255 +)))
256 +
257 +(((
283 283  
284 284  )))
285 285  
261 +(% class="box" %)
286 286  (((
287 -(% 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)
288 288  )))
289 289  
290 -{{{ [12502]***** UpLinkCounter= 0 *****
291 - [12503]TX on freq 868500000 Hz at DR 0
292 - [13992]txDone
293 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
294 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
295 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
296 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
297 -
298 298  (((
299 299  
300 -
301 -
302 302  )))
303 303  
304 304  (((
305 -(% style="color:blue" %)**Another message:**
277 +**Another message:**
306 306  )))
307 307  
308 -{{{ [12502]***** UpLinkCounter= 0 *****
309 - [12503]TX on freq 868100000 Hz at DR 0
310 - [13992]txDone
311 - [15022]RX on freq 868100000 Hz at DR 0
312 - [15222]rxTimeOut
313 - [15987]RX on freq 869525000 Hz at DR 3
314 - [16185]rxDone --> We have got the downstream packet.
315 - Rssi= -64
316 - Receive data
317 - 1:0012345678}}}
318 318  
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
319 319  
292 +== 5.3 If problem doesn’t solve ==
320 320  
321 -== 5.3 If problem doesn't solve ==
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:**
322 322  
323 -
324 -(% 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:**
325 -
326 326  * End node console to show the transmit freuqency and DR.
327 327  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
328 328  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
329 329  * End Node traffic (from server UI) to shows end node activity in server.
330 330  
331 -
332 -
333 -
334 334  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335 335  
336 -
337 337  (((
338 338  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.
339 339  )))
... ... @@ -346,10 +346,8 @@
346 346  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:
347 347  )))
348 348  
349 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
350 -
351 351  (((
352 -
316 +Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
353 353  )))
354 354  
355 355  (((
... ... @@ -357,34 +357,37 @@
357 357  )))
358 358  
359 359  
360 -
361 361  = 7. Decrypt a LoRaWAN Packet =
362 362  
326 +~1. LHT65 End device configure:
363 363  
364 -(% style="color:blue" %)**1. LHT65 End device configure:**
328 +(% class="box infomessage" %)
329 +(((
330 +Change to ABP Mode: AT+NJM=0
331 +)))
365 365  
366 -**Change to ABP Mode:  AT+NJM=0**
367 -**Change to fix frequency:  AT+CHS=904900000**
368 -**Change to fix DR:  AT+DR=0**
333 +(% class="box infomessage" %)
334 +(((
335 +Change to fix frequency: AT+CHS=904900000
336 +)))
369 369  
338 +(% class="box infomessage" %)
339 +(((
340 +Change to fix DR: AT+DR=0
341 +)))
370 370  
371 -[[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"]]
372 372  
345 +2. In LG02 , configure to receive above message
373 373  
347 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
374 374  
375 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
376 -
377 -[[image:image-20220526165612-17.png]]
378 -
379 -
380 380  In LG02 console, we can see the hex receive are:
381 381  
382 -[[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"]]
383 383  
353 +3. Decode the info in web
384 384  
385 -
386 -(% style="color:blue" %)**3. Decode the info in web**
387 -
388 388  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
389 389  
390 390  Need these three fields:
... ... @@ -395,148 +395,45 @@
395 395  
396 396  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
397 397  
398 -
399 399  [[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]]
400 400  
401 -[[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"]]
402 402  
403 -(((
404 - The FRMPayload is the device payload.
405 -)))
369 +The FRMPayload is the device payload.
406 406  
407 407  
408 -
409 409  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
410 410  
411 -
412 412  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.
413 413  
414 -
415 -
416 416  = 9. Why do I see a "MIC Mismatch" error message from the server? =
417 417  
378 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
418 418  
419 -(((
420 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
421 -)))
422 -
423 -(((
424 424  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
425 -)))
426 426  
427 -* (((
428 -Please note the distinction between "APPKEY" and "APPSKEY".
429 -)))
382 +* Please note the distinction between "APPKEY" and "APPSKEY".
430 430  
431 -(((
432 432  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
433 -)))
434 434  
435 -(((
436 436  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
437 -)))
438 438  
439 -* (((
440 -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.
441 441  
442 -
443 -
444 -
445 -)))
446 -
447 447  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
448 448  
449 -
450 450  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
451 451  
452 -(((
453 453  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
454 -)))
455 455  
456 -(((
457 -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.
458 -)))
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,
459 459  
460 -* (((
461 -Solution: Use the decoder to filter out this 00 packet.
462 -)))
463 -* (((
464 -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,
465 465  
400 +so it will send a normal uplink packet, and an additional 00 data packet.
466 466  
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
467 467  
405 +(% class="wikigeneratedid" id="H" %)
468 468  
469 -)))
470 -
471 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
472 -
473 -
474 -(((
475 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
476 -)))
477 -
478 -(((
479 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
480 -)))
481 -
482 -(((
483 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
484 -)))
485 -
486 -(((
487 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
488 -)))
489 -
490 -(((
491 -AT+APPEUI=00 00 00 00 00 00 00 00
492 -)))
493 -
494 -(((
495 -
496 -)))
497 -
498 -(((
499 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
500 -)))
501 -
502 -(((
503 -You can rewrites the keys by running commands in AT Console
504 -
505 -
506 -)))
507 -
508 -(((
509 -**For example：**
510 -)))
511 -
512 -(((
513 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
514 -)))
515 -
516 -(((
517 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
518 -)))
519 -
520 -(((
521 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
522 -)))
523 -
524 -(((
525 -AT+APPEUI=2C 45 47 E3 24 12 23 24
526 -)))
527 -
528 -(((
529 -(Any combination of 16 bit codes can be used）
530 -
531 -
532 -
533 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
534 -)))
535 -
536 -
537 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
538 -
539 -
540 -
541 -(% class="wikigeneratedid" %)
542 -
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