Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 23.1 >
edited by Xiaoling
on 2022/05/26 16:49
To version < 4.6 >
edited by Xiaoling
on 2022/05/11 14:52
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,5 @@
1 1  **~ Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
... ... @@ -23,7 +23,7 @@
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526163523-1.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  
... ... @@ -33,7 +33,7 @@
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  
... ... @@ -44,7 +44,7 @@
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  
... ... @@ -53,11 +53,11 @@
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  
... ... @@ -98,15 +98,15 @@
98 98  Here are the freuqency tables for these bands as reference:
99 99  )))
100 100  
101 -[[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"]]
102 102  
103 103  US915 Channels
104 104  
105 -[[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"]]
106 106  
107 107  AU915 Channels
108 108  
109 -[[image:image-20220526163941-8.png]]
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 111  (((
112 112  CN470 Channels
... ... @@ -116,7 +116,7 @@
116 116  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.
117 117  )))
118 118  
119 -[[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"]]
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
... ... @@ -170,7 +170,7 @@
170 170  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
171 171  )))
172 172  
173 -[[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]]
174 174  
175 175  Disable Frame Counter Check in ABP Mode
176 176  
... ... @@ -185,7 +185,7 @@
185 185  Depends on Class A or Class C, the receive windows will be a little difference,
186 186  )))
187 187  
188 -[[image:image-20220526164547-11.png]]
184 +[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
... ... @@ -197,7 +197,6 @@
197 197  * This packet must match the frequency of the RX1 or RX2 window.
198 198  * 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.**
199 199  
200 -
201 201  == 5.2 See Debug Info ==
202 202  
203 203  (((
... ... @@ -212,7 +212,7 @@
212 212  Configure a downstream to the end device
213 213  )))
214 214  
215 -[[image:image-20220526164623-12.png]]
210 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
216 216  
217 217  (((
218 218  Set a downstream in TTN and see it is sent
... ... @@ -223,7 +223,7 @@
223 223  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
224 224  )))
225 225  
226 -[[image:image-20220526164650-13.png]]
221 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
227 227  
228 228  (((
229 229  Gateway Traffic can see this downstream info
... ... @@ -238,7 +238,7 @@
238 238  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:
239 239  )))
240 240  
241 -[[image:image-20220526164734-14.png]]
236 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
242 242  
243 243  (((
244 244  Gateway Sent out this packet
... ... @@ -249,55 +249,59 @@
249 249  **For End Node**
250 250  )))
251 251  
252 -(((
253 253  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
254 -)))
255 255  
249 +(% class="box infomessage" %)
256 256  (((
257 -
251 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
258 258  )))
259 259  
254 +(% class="box infomessage" %)
260 260  (((
256 + AT+RX2DR=3 ~-~--> The RX2 DataRate
257 +)))
258 +
261 261  (% class="box infomessage" %)
262 262  (((
263 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
264 -AT+RX2DR=3      ~-~--> The RX2 DataRate
265 -AT+RX1DL=1000   ~-~--> Receive Delay 1
266 -AT+RX2DL=2000   ~-~--> Receive Delay 2
261 + AT+RX1DL=1000 ~-~--> Receive Delay 1
267 267  )))
268 -)))
269 269  
264 +(% class="box infomessage" %)
270 270  (((
271 -**when the device running, we can see below info:**
266 + AT+RX2DL=2000 ~-~--> Receive Delay 2
272 272  )))
273 273  
274 -{{{ [12502]***** UpLinkCounter= 0 *****
275 - [12503]TX on freq 868500000 Hz at DR 0
276 - [13992]txDone
277 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
278 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
279 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
280 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
269 +**when the device running, we can see below info:**
281 281  
282 282  (((
283 283  
284 284  )))
285 285  
275 +{{{ [12502]***** UpLinkCounter= 0 *****
276 + [12503]TX on freq 868500000 Hz at DR 0
277 + [13992]txDone
278 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
279 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
280 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
281 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
282 +
286 286  (((
287 -**Another message:**
284 +
288 288  )))
289 289  
290 -{{{ [12502]***** UpLinkCounter= 0 *****
291 - [12503]TX on freq 868100000 Hz at DR 0
292 - [13992]txDone
293 - [15022]RX on freq 868100000 Hz at DR 0
294 - [15222]rxTimeOut
295 - [15987]RX on freq 869525000 Hz at DR 3
296 - [16185]rxDone --> We have got the downstream packet.
297 - Rssi= -64
298 - Receive data
299 - 1:0012345678}}}
287 +**Another message:**
300 300  
289 +{{{
290 + [12502]***** UpLinkCounter= 0 *****
291 + [12503]TX on freq 868100000 Hz at DR 0
292 + [13992]txDone
293 + [15022]RX on freq 868100000 Hz at DR 0
294 + [15222]rxTimeOut
295 + [15987]RX on freq 869525000 Hz at DR 3
296 + [16185]rxDone --> We have got the downstream packet.
297 + Rssi= -64
298 + Receive data
299 + 1:0012345678}}}
301 301  
302 302  == 5.3 If problem doesn’t solve ==
303 303  
... ... @@ -308,9 +308,6 @@
308 308  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
309 309  * End Node traffic (from server UI) to shows end node activity in server.
310 310  
311 -(% class="wikigeneratedid" %)
312 -​​​​​​​
313 -
314 314  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
315 315  
316 316  (((
... ... @@ -325,7 +325,9 @@
325 325  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:
326 326  )))
327 327  
328 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
324 +(((
325 +Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
326 +)))
329 329  
330 330  (((
331 331  
... ... @@ -381,9 +381,7 @@
381 381  
382 382  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
383 383  
384 -(((
385 - The FRMPayload is the device payload.
386 -)))
382 +The FRMPayload is the device payload.
387 387  
388 388  
389 389  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -392,83 +392,32 @@
392 392  
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
395 -(((
396 396  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
397 -)))
398 398  
399 -(((
400 400  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
401 -)))
402 402  
403 -* (((
404 -Please note the distinction between "APPKEY" and "APPSKEY".
405 -)))
395 +* Please note the distinction between "APPKEY" and "APPSKEY".
406 406  
407 -(((
408 408  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
409 -)))
410 410  
411 -(((
412 412  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
413 -)))
414 414  
415 -* (((
416 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
401 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
417 417  
418 -
419 -)))
420 -
421 421  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
422 422  
423 423  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
424 424  
425 -(((
426 426  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
427 -)))
428 428  
429 -(((
430 -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.
431 -)))
409 +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,
432 432  
433 -* (((
434 -Solution: Use the decoder to filter out this 00 packet.
435 -)))
436 -* (((
437 -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]]
411 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
438 438  
413 +so it will send a normal uplink packet, and an additional 00 data packet.
439 439  
440 -
441 -)))
415 +* Solution: Use the decoder to filter out this 00 packet.
416 +* 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
442 442  
443 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
444 -
445 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
446 -
447 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
448 -
449 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
450 -
451 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
452 -
453 -AT+APPEUI=00 00 00 00 00 00 00 00
454 -
455 -
456 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
457 -
458 -You can rewrites the keys by running commands in AT Console
459 -
460 -For example：
461 -
462 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
463 -
464 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
465 -
466 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
467 -
468 -AT+APPEUI=2C 45 47 E3 24 12 23 24
469 -
470 -(Any combination of 16 bit codes can be used）
471 -
472 -
473 -(% class="wikigeneratedid" %)
418 +(% class="wikigeneratedid" id="H" %)
474 474  
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

Applications

Navigation

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