Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Change comment:
Uploaded new attachment "image-20240129154321-9.png", version {1}
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -230,22 +230,21 @@ 230 230 [[image:image-20240129152412-8.png||height="486" width="1206"]] 231 231 ))) 232 232 233 +[[image:image-20240123163307-7.png||height="330" width="1125"]] 233 233 234 234 ((( 235 235 Set a downstream in TTN and see it is sent 236 236 ))) 237 237 238 -(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.** 239 239 240 - 241 241 ((( 242 -This down linkinfo will then pass to the gateway downlinklist. and the DR which is used (SF7BW500) in US915 is DR5.241 +This downstream info will then pass to the gateway downstream list. and the DR which is used (SF7BW500) in US915 is DR5. 243 243 ))) 244 244 245 245 [[image:image-20240129152049-7.png||height="463" width="1166"]] 246 246 247 247 ((( 248 -Gateway Traffic can see this down linkinfo247 +Gateway Traffic can see this downstream info 249 249 ))) 250 250 251 251 ... ... @@ -255,10 +255,10 @@ 255 255 ))) 256 256 257 257 ((( 258 -When the down linkpacket appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:257 +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: 259 259 ))) 260 260 261 -[[image:image-202 40129154321-9.png]]260 +[[image:image-20220526164734-14.png]] 262 262 263 263 ((( 264 264 Gateway Sent out this packet ... ... @@ -335,7 +335,7 @@ 335 335 336 336 337 337 ((( 338 -In LoRaWAN, the gatewa ywill 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.337 +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. 339 339 ))) 340 340 341 341 ((( ... ... @@ -360,47 +360,45 @@ 360 360 = 7. Decrypt a LoRaWAN Packet = 361 361 362 362 363 -(% style="color:blue" %)**1. LHT65 NEnd device configure:**362 +(% style="color:blue" %)**1. LHT65 End device configure:** 364 364 365 365 **Change to ABP Mode: AT+NJM=0** 366 366 367 -**Change to fix frequency: AT+CHE=1**366 +**Change to fix frequency: AT+CHS=904900000** 368 368 368 +**Change to fix DR: AT+DR=0** 369 369 370 -**AT+CFG(Print configuration):** 371 371 372 -[[image:image-202 40129163714-2.png]][[image:image-20240129163741-3.png]]371 +[[image:image-20220526165525-16.png]] 373 373 374 374 375 375 376 -** Configuration:**375 +(% style="color:blue" %)**2. In LG02 , configure to receive above message** 377 377 378 -[[image:image-202 40129164219-4.png||height="612" width="440"]]377 +[[image:image-20220526165612-17.png]] 379 379 380 380 380 +In LG02 console, we can see the hex receive are: 381 381 382 - (% style="color:blue" %)**2. In LPS8-v2, configureto receive abovemessage**382 +[[image:image-20220526171112-21.png]] 383 383 384 -[[image:image-20240129164326-5.png||height="506" width="1114"]] 385 385 386 386 387 - InLPS8-v2console,wecan seetheBase64receiveare:386 +(% style="color:blue" %)**3. Decode the info in web** 388 388 389 -[[ image:image-20240129170137-6.png||height="459"width="1116"]]388 +[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]] 390 390 391 - 392 - 393 -(% style="color:blue" %)**3. Decode the info ** 394 - 395 395 Need these three fields: 396 396 397 -LoRa packet Base64format:QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 (from LPS8-v2)392 +LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02) 398 398 399 -AT+NWKSKEY= FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF(End node Network Session Key)394 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key) 400 400 401 -AT+APPSKEY= FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF(End Node App Session Key)396 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 402 402 403 403 399 +[[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]] 400 + 404 404 [[image:image-20220526171029-20.png]] 405 405 406 406 ((( ... ... @@ -452,7 +452,7 @@ 452 452 4)We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue 453 453 454 454 455 -= 10. Why Igot the payload only with "0x00" or "AA~=~="? =452 += 10. Why i got the payload only with "0x00" or "AA~=~="? = 456 456 457 457 458 458 (% style="color:blue" %)**Why sensor sends 0x00?** ... ... @@ -547,7 +547,7 @@ 547 547 (Any combination of 16 bit codes can be used) 548 548 549 549 550 -= 12. I set my device is LoRaWAN Class C mode, why Istill see Class A after boot? =547 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? = 551 551 ))) 552 552 553 553 ... ... @@ -578,3 +578,6 @@ 578 578 579 579 580 580 [[image:image-20221215223215-1.png||height="584" width="1280"]] 578 + 579 +(% class="wikigeneratedid" %) 580 +
- image-20240129163533-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -23.0 KB - Content
- image-20240129163714-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -39.2 KB - Content
- image-20240129163741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -36.5 KB - Content
- image-20240129164219-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -30.3 KB - Content
- image-20240129164326-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -80.8 KB - Content
- image-20240129170137-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.ting - Size
-
... ... @@ -1,1 +1,0 @@ 1 -115.2 KB - Content