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)
-
Attachments (0 modified, 1 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,4 +1,4 @@ 1 -**~ Contents:** 1 +**~ Table of Contents:** 2 2 3 3 {{toc/}} 4 4 ... ... @@ -182,7 +182,7 @@ 182 182 Depends on Class A or Class C, the receive windows will be a little difference, 183 183 ))) 184 184 185 -[[image:image-202205 26164547-11.png]]185 +[[image:image-20220531161828-1.png]] 186 186 187 187 receive windows for Class A and Class C 188 188 ... ... @@ -194,8 +194,6 @@ 194 194 * This packet must match the frequency of the RX1 or RX2 window. 195 195 * 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.** 196 196 197 - 198 - 199 199 == 5.2 See Debug Info == 200 200 201 201 ((( ... ... @@ -338,15 +338,7 @@ 338 338 (% class="box infomessage" %) 339 339 ((( 340 340 **Change to ABP Mode: AT+NJM=0** 341 -))) 342 - 343 -(% class="box infomessage" %) 344 -((( 345 345 **Change to fix frequency: AT+CHS=904900000** 346 -))) 347 - 348 -(% class="box infomessage" %) 349 -((( 350 350 **Change to fix DR: AT+DR=0** 351 351 ))) 352 352 ... ... @@ -435,7 +435,6 @@ 435 435 * ((( 436 436 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]] 437 437 438 - 439 439 440 440 ))) 441 441 ... ... @@ -495,8 +495,15 @@ 495 495 496 496 ((( 497 497 (Any combination of 16 bit codes can be used) 487 + 488 + 489 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? = 498 498 ))) 499 499 500 500 493 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode. 494 + 495 + 496 + 501 501 (% class="wikigeneratedid" %) 502 502
- image-20220531161828-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.6 KB - Content