Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.7 >
edited by Xiaoling
on 2022/05/11 14:57
To version < 32.16 >
edited by Xiaoling
on 2022/08/12 11:06
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. OTAA Join Process Debug =
7 7  
9 +
8 8  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.
9 9  \\**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:**
10 10  
... ... @@ -14,52 +14,57 @@
14 14  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
15 15  * 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)
16 16  
17 -**~1. End Device Join Screen shot, we can check:**
18 18  
20 +
21 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 +
19 19  * If the device is sending join request to server?
20 20  * What frequency the device is sending?
21 21  
22 -[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
26 +[[image:image-20220526164956-15.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
26 26  
27 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
28 28  
32 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
33 +
29 29  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
30 30  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
31 31  
32 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
37 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
36 36  
37 -**3. Gateway Traffic Page in LoRaWAN Server**
42 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
38 38  
39 39  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
40 40  * 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.
41 41  * 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.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
48 +[[image:image-20220526163633-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
47 47  
48 -**4. Data Page in LoRaWAN server**
53 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
49 49  
50 50  * 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.
51 51  
52 -[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
57 +[[image:image-20220526163704-4.png]]
53 53  
54 54  The data for the end device set in server
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
61 +[[image:image-20220526163732-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
60 60  
66 +
61 61  = 2. Notice of US915/CN470/AU915 Frequency band =
62 62  
69 +
63 63  (((
64 64  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
65 65  )))
... ... @@ -94,18 +94,21 @@
94 94  Here are the freuqency tables for these bands as reference:
95 95  )))
96 96  
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"]]
104 +[[image:image-20220526163801-6.png]]
98 98  
99 99  US915 Channels
100 100  
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"]]
108 +[[image:image-20220526163926-7.png]]
102 102  
103 103  AU915 Channels
104 104  
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"]]
106 106  
113 +[[image:image-20220526163941-8.png]]
114 +
107 107  (((
108 108  CN470 Channels
117 +
118 +
109 109  )))
110 110  
111 111  (((
... ... @@ -112,10 +112,12 @@
112 112  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.
113 113  )))
114 114  
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"]]
125 +[[image:image-20220526164052-9.png]]
116 116  
117 117  (((
118 118  TTN FREQUENCY PLAN
129 +
130 +
119 119  )))
120 120  
121 121  (((
... ... @@ -123,8 +123,10 @@
123 123  )))
124 124  
125 125  
138 +
126 126  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
127 127  
141 +
128 128  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:
129 129  
130 130  * **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.
... ... @@ -144,8 +144,10 @@
144 144  )))
145 145  
146 146  
161 +
147 147  = 4. Transmision on ABP Mode =
148 148  
164 +
149 149  (((
150 150  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.
151 151  )))
... ... @@ -166,15 +166,17 @@
166 166  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
167 167  )))
168 168  
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]]
185 +[[image:image-20220526164508-10.png]]
170 170  
171 171  Disable Frame Counter Check in ABP Mode
172 172  
173 173  
190 +
174 174  = 5. Downstream Debug =
175 175  
176 176  == 5.1 How it work ==
177 177  
195 +
178 178  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.
179 179  
180 180  (((
... ... @@ -181,10 +181,11 @@
181 181  Depends on Class A or Class C, the receive windows will be a little difference,
182 182  )))
183 183  
184 -[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
202 +[[image:image-20220531161828-1.png]]
185 185  
186 186  receive windows for Class A and Class C
187 187  
206 +
188 188  Below are the requirement for the End Device to receive the packets.
189 189  
190 190  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -191,12 +191,16 @@
191 191  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
192 192  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
193 193  * This packet must match the frequency of the RX1 or RX2 window.
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.**
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.**
195 195  
215 +
216 +
217 +
196 196  == 5.2 See Debug Info ==
197 197  
220 +
198 198  (((
199 -**For LoRaWAN Server**
222 +(% style="color:blue" %)**For LoRaWAN Server**
200 200  )))
201 201  
202 202  (((
... ... @@ -207,7 +207,7 @@
207 207  Configure a downstream to the end device
208 208  )))
209 209  
210 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
233 +[[image:image-20220526164623-12.png]]
211 211  
212 212  (((
213 213  Set a downstream in TTN and see it is sent
... ... @@ -218,7 +218,7 @@
218 218  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
219 219  )))
220 220  
221 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
244 +[[image:image-20220526164650-13.png]]
222 222  
223 223  (((
224 224  Gateway Traffic can see this downstream info
... ... @@ -225,8 +225,9 @@
225 225  )))
226 226  
227 227  
251 +
228 228  (((
229 -**For LoRaWAN Gateway**
253 +(% style="color:blue" %)**For LoRaWAN Gateway**
230 230  )))
231 231  
232 232  (((
... ... @@ -233,7 +233,7 @@
233 233  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:
234 234  )))
235 235  
236 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
260 +[[image:image-20220526164734-14.png]]
237 237  
238 238  (((
239 239  Gateway Sent out this packet
... ... @@ -240,78 +240,76 @@
240 240  )))
241 241  
242 242  
243 -(((
244 -**For End Node**
245 -)))
246 246  
247 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
248 -
249 -(% class="box infomessage" %)
250 250  (((
251 - AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
269 +(% style="color:blue" %)**For End Node**
252 252  )))
253 253  
254 -(% class="box infomessage" %)
255 255  (((
256 - AT+RX2DR=3 ~-~--> The RX2 DataRate
273 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
257 257  )))
258 258  
259 -(% class="box infomessage" %)
260 260  (((
261 - AT+RX1DL=1000 ~-~--> Receive Delay 1
262 -)))
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
263 263  
264 -(% class="box infomessage" %)
265 -(((
266 - AT+RX2DL=2000 ~-~--> Receive Delay 2
267 -)))
268 268  
269 -(((
270 -**when the device running, we can see below info:**
283 +
271 271  )))
272 272  
273 273  (((
274 -
287 +(% style="color:blue" %)**when the device running, we can see below info:**
275 275  )))
276 276  
277 -{{{ [12502]***** UpLinkCounter= 0 *****
278 - [12503]TX on freq 868500000 Hz at DR 0
279 - [13992]txDone
280 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
281 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
282 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
283 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
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)}}}
284 284  
285 285  (((
286 286  
300 +
301 +
287 287  )))
288 288  
289 289  (((
290 -**Another message:**
305 +(% style="color:blue" %)**Another message:**
291 291  )))
292 292  
293 -{{{ [12502]***** UpLinkCounter= 0 *****
294 - [12503]TX on freq 868100000 Hz at DR 0
295 - [13992]txDone
296 - [15022]RX on freq 868100000 Hz at DR 0
297 - [15222]rxTimeOut
298 - [15987]RX on freq 869525000 Hz at DR 3
299 - [16185]rxDone --> We have got the downstream packet.
300 - Rssi= -64
301 - Receive data
302 - 1:0012345678}}}
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}}}
303 303  
304 -== 5.3 If problem doesn’t solve ==
305 305  
306 -**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:**
307 307  
321 +== 5.3 If problem doesn't solve ==
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 +
308 308  * End node console to show the transmit freuqency and DR.
309 309  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
310 310  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
311 311  * End Node traffic (from server UI) to shows end node activity in server.
312 312  
331 +
332 +
333 +
313 313  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
314 314  
336 +
315 315  (((
316 316  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.
317 317  )))
... ... @@ -335,37 +335,34 @@
335 335  )))
336 336  
337 337  
360 +
338 338  = 7. Decrypt a LoRaWAN Packet =
339 339  
340 -~1. LHT65 End device configure:
341 341  
342 -(% class="box infomessage" %)
343 -(((
344 -Change to ABP Mode: AT+NJM=0
345 -)))
364 +(% style="color:blue" %)**1. LHT65 End device configure:**
346 346  
347 -(% class="box infomessage" %)
348 -(((
349 -Change to fix frequency: AT+CHS=904900000
350 -)))
366 +**Change to ABP Mode:  AT+NJM=0**
367 +**Change to fix frequency:  AT+CHS=904900000**
368 +**Change to fix DR:  AT+DR=0**
351 351  
352 -(% class="box infomessage" %)
353 -(((
354 -Change to fix DR: AT+DR=0
355 -)))
356 356  
357 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
371 +[[image:image-20220526165525-16.png]]
358 358  
359 -2. In LG02 , configure to receive above message
360 360  
361 -[[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  
375 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
376 +
377 +[[image:image-20220526165612-17.png]]
378 +
379 +
363 363  In LG02 console, we can see the hex receive are:
364 364  
365 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
382 +[[image:image-20220526171112-21.png]]
366 366  
367 -3. Decode the info in web
368 368  
385 +
386 +(% style="color:blue" %)**3. Decode the info in web**
387 +
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
370 370  
371 371  Need these three fields:
... ... @@ -376,23 +376,29 @@
376 376  
377 377  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
378 378  
379 -(((
398 +
380 380  [[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]]
381 -)))
382 382  
383 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
401 +[[image:image-20220526171029-20.png]]
384 384  
385 -The FRMPayload is the device payload.
403 +(((
404 + The FRMPayload is the device payload.
405 +)))
386 386  
387 387  
408 +
388 388  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
389 389  
411 +
390 390  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.
391 391  
414 +
415 +
392 392  = 9. Why do I see a "MIC Mismatch" error message from the server? =
393 393  
418 +
394 394  (((
395 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
420 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
396 396  )))
397 397  
398 398  (((
... ... @@ -413,36 +413,105 @@
413 413  
414 414  * (((
415 415  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
441 +
442 +
443 +
444 +
416 416  )))
417 417  
418 418  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
419 419  
449 +
450 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
451 +
452 +(((
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 +
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 +)))
459 +
420 420  * (((
421 -If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
461 +Solution: Use the decoder to filter out this 00 packet.
422 422  )))
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]]
423 423  
466 +
467 +
468 +
469 +)))
470 +
471 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
472 +
473 +
424 424  (((
425 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
475 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
426 426  )))
427 427  
428 428  (((
429 -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,
479 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
430 430  )))
431 431  
432 432  (((
433 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
483 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
434 434  )))
435 435  
436 436  (((
437 -so it will send a normal uplink packet, and an additional 00 data packet.
487 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
438 438  )))
439 439  
440 -* (((
441 -Solution: Use the decoder to filter out this 00 packet.
490 +(((
491 +AT+APPEUI=00 00 00 00 00 00 00 00
442 442  )))
443 -* (((
444 -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
493 +
494 +(((
495 +
445 445  )))
446 446  
447 -(% class="wikigeneratedid" id="H" %)
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 +
448 448  
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,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0