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