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 < 10.2 >
edited by Xiaoling
on 2022/05/26 16:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,9 @@
1 1  **~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
... ... @@ -19,7 +19,7 @@
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-20220526163523-1.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
... ... @@ -29,7 +29,7 @@
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"]]
36 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
... ... @@ -244,44 +244,36 @@
244 244  **For End Node**
245 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
252 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
252 252  )))
253 253  
254 -(% class="box infomessage" %)
255 255  (((
256 - AT+RX2DR=3 ~-~--> The RX2 DataRate
256 +
257 257  )))
258 258  
259 -(% class="box infomessage" %)
260 260  (((
261 - AT+RX1DL=1000 ~-~--> Receive Delay 1
262 -)))
263 -
264 264  (% class="box infomessage" %)
265 265  (((
266 - AT+RX2DL=2000 ~-~--> Receive Delay 2
262 +AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
263 +AT+RX2DR=3      ~-~--> The RX2 DataRate
264 +AT+RX1DL=1000   ~-~--> Receive Delay 1
265 +AT+RX2DL=2000   ~-~--> Receive Delay 2
267 267  )))
267 +)))
268 268  
269 269  (((
270 270  **when the device running, we can see below info:**
271 271  )))
272 272  
273 -(((
274 -
275 -)))
273 +{{{ [12502]***** UpLinkCounter= 0 *****
274 + [12503]TX on freq 868500000 Hz at DR 0
275 + [13992]txDone
276 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
277 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
278 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
279 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
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)}}}
284 -
285 285  (((
286 286  
287 287  )))
... ... @@ -290,16 +290,16 @@
290 290  **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}}}
289 +{{{ [12502]***** UpLinkCounter= 0 *****
290 + [12503]TX on freq 868100000 Hz at DR 0
291 + [13992]txDone
292 + [15022]RX on freq 868100000 Hz at DR 0
293 + [15222]rxTimeOut
294 + [15987]RX on freq 869525000 Hz at DR 3
295 + [16185]rxDone --> We have got the downstream packet.
296 + Rssi= -64
297 + Receive data
298 + 1:0012345678}}}
303 303  
304 304  == 5.3 If problem doesn’t solve ==
305 305  
... ... @@ -376,13 +376,13 @@
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 -(((
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 383  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
384 384  
385 -The FRMPayload is the device payload.
379 +(((
380 + The FRMPayload is the device payload.
381 +)))
386 386  
387 387  
388 388  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -413,13 +413,13 @@
413 413  
414 414  * (((
415 415  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
412 +
413 +
416 416  )))
417 417  
418 418  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
419 419  
420 -* (((
421 -If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
422 -)))
418 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
423 423  
424 424  (((
425 425  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
... ... @@ -426,23 +426,46 @@
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,
425 +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.
430 430  )))
431 431  
432 -(((
433 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
434 -)))
435 -
436 -(((
437 -so it will send a normal uplink packet, and an additional 00 data packet.
438 -)))
439 -
440 440  * (((
441 441  Solution: Use the decoder to filter out this 00 packet.
442 442  )))
443 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
445 -)))
432 +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]]
446 446  
447 -(% class="wikigeneratedid" id="H" %)
434 +
448 448  
436 +)))
437 +
438 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439 +
440 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
441 +
442 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
443 +
444 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
445 +
446 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 +
448 +AT+APPEUI=00 00 00 00 00 00 00 00
449 +
450 +
451 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
452 +
453 +You can rewrites the keys by running commands in AT Console
454 +
455 +For example：
456 +
457 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
458 +
459 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
460 +
461 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
462 +
463 +AT+APPEUI=2C 45 47 E3 24 12 23 24
464 +
465 +(Any combination of 16 bit codes can be used）
466 +
467 +
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

Applications

Navigation

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