Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -39,7 +39,6 @@ 39 39 Console Output from Gateway to see packets between end node and server. 40 40 41 41 42 - 43 43 (% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server** 44 44 45 45 * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings. ... ... @@ -51,7 +51,6 @@ 51 51 The Traffic for the End node in the server, use TTN as example 52 52 53 53 54 - 55 55 (% style="color:blue" %)**4. Data Page in LoRaWAN server** 56 56 57 57 * 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. ... ... @@ -60,7 +60,6 @@ 60 60 61 61 The data for the end device set in server 62 62 63 - 64 64 [[image:image-20220526163732-5.png]] 65 65 66 66 Check if OTAA Keys match the keys in device ... ... @@ -108,7 +108,6 @@ 108 108 109 109 US915 Channels 110 110 111 - 112 112 [[image:image-20220526163926-7.png]] 113 113 114 114 AU915 Channels ... ... @@ -218,6 +218,7 @@ 218 218 219 219 220 220 217 + 221 221 == 5.2 See Debug Info == 222 222 223 223 ... ... @@ -333,6 +333,7 @@ 333 333 334 334 335 335 333 + 336 336 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 337 337 338 338 ... ... @@ -449,23 +449,27 @@ 449 449 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 450 450 451 451 452 -* *Whythishappen:**450 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 453 453 454 -For US915, AU915 or AS923 frequencies.It is possible because: . 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 455 456 -When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled. 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 +))) 457 457 458 -When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end 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 following an additional 00 data packet to handle this MAC command response. 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]] 459 459 460 460 461 -**How to solve:** 462 462 463 -Solution: Use the decoder to filter out this 0x00 packet. 468 + 469 +))) 464 464 465 -Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]] 466 - 467 - 468 - 469 469 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 470 470 471 471