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
-
... ... @@ -205,7 +205,6 @@ 205 205 * This packet must match the frequency of the RX1 or RX2 window. 206 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.** 207 207 208 - 209 209 == 5.2 See Debug Info == 210 210 211 211 ... ... @@ -263,20 +263,15 @@ 263 263 ))) 264 264 265 265 ((( 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 + 266 266 267 267 ))) 268 268 269 269 ((( 270 -(% class="box infomessage" %) 271 -((( 272 -AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency 273 -AT+RX2DR=3 ~-~--> The RX2 DataRate 274 -AT+RX1DL=1000 ~-~--> Receive Delay 1 275 -AT+RX2DL=2000 ~-~--> Receive Delay 2 276 -))) 277 -))) 278 - 279 -((( 280 280 (% style="color:blue" %)**when the device running, we can see below info:** 281 281 ))) 282 282 ... ... @@ -308,8 +308,9 @@ 308 308 1:0012345678}}} 309 309 310 310 311 -== 5.3 If problem doesn ’t solve ==305 +== 5.3 If problem doesn't solve == 312 312 307 + 313 313 (% 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:** 314 314 315 315 * End node console to show the transmit freuqency and DR. ... ... @@ -317,8 +317,11 @@ 317 317 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. 318 318 * End Node traffic (from server UI) to shows end node activity in server. 319 319 315 + 316 + 320 320 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 321 321 319 + 322 322 ((( 323 323 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. 324 324 ))) ... ... @@ -344,19 +344,17 @@ 344 344 345 345 = 7. Decrypt a LoRaWAN Packet = 346 346 347 -~1. LHT65 End device configure: 348 348 349 -(% class="box infomessage" %) 350 -((( 351 -**Change to ABP Mode: AT+NJM=0** 352 -**Change to fix frequency: AT+CHS=904900000** 353 -**Change to fix DR: AT+DR=0** 354 -))) 346 +(% style="color:blue" %)**1. LHT65 End device configure:** 355 355 348 +**Change to ABP Mode: AT+NJM=0** 349 +**Change to fix frequency: AT+CHS=904900000** 350 +**Change to fix DR: AT+DR=0** 351 + 356 356 [[image:image-20220526165525-16.png]] 357 357 358 358 359 -2. In LG02 , configure to receive above message 355 +(% style="color:blue" %)**2. In LG02 , configure to receive above message** 360 360 361 361 [[image:image-20220526165612-17.png]] 362 362 ... ... @@ -366,7 +366,7 @@ 366 366 [[image:image-20220526171112-21.png]] 367 367 368 368 369 -3. Decode the info in web 365 +(% style="color:blue" %)**3. Decode the info in web** 370 370 371 371 [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]] 372 372