Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 61.1 >
edited by Mengting Qiu
on 2024/01/29 15:24
To version < 78.1 >
edited by Mengting Qiu
on 2024/01/29 17:49
>
Change comment: Uploaded new attachment "image-20240129174948-14.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -230,21 +230,22 @@
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"]]
234 234  
235 235  (((
236 236  Set a downstream in TTN and see it is sent
237 237  )))
238 238  
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 +
240 240  (((
241 -This downstream info will then pass to the gateway downstream list. and the DR which is used (SF7BW500) in US915 is DR5.
242 +This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
242 242  )))
243 243  
244 244  [[image:image-20240129152049-7.png||height="463" width="1166"]]
245 245  
246 246  (((
247 -Gateway Traffic can see this downstream info
248 +Gateway Traffic can see this downlink info
248 248  )))
249 249  
250 250  
... ... @@ -254,10 +254,10 @@
254 254  )))
255 255  
256 256  (((
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:
258 +When the downlink packet 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:
258 258  )))
259 259  
260 -[[image:image-20220526164734-14.png]]
261 +[[image:image-20240129154321-9.png]]
261 261  
262 262  (((
263 263  Gateway Sent out this packet
... ... @@ -334,7 +334,7 @@
334 334  
335 335  
336 336  (((
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.
338 +In LoRaWAN, the gateway 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.
338 338  )))
339 339  
340 340  (((
... ... @@ -359,45 +359,47 @@
359 359  = 7. Decrypt a LoRaWAN Packet =
360 360  
361 361  
362 -(% style="color:blue" %)**1. LHT65 End device configure:**
363 +(% style="color:blue" %)**1. LHT65N End device configure:**
363 363  
364 364  **Change to ABP Mode:  AT+NJM=0**
365 365  
366 -**Change to fix frequency:  AT+CHS=904900000**
367 +**Change to fix frequency:  ​​​​AT+CHE=1**
367 367  
368 -**Change to fix DR:  AT+DR=0**
369 369  
370 +**AT+CFG(Print configuration):**
370 370  
371 -[[image:image-20220526165525-16.png]]
372 +[[image:image-20240129163714-2.png]][[image:image-20240129163741-3.png]]
372 372  
373 373  
374 374  
375 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
376 +**Configuration: **
376 376  
377 -[[image:image-20220526165612-17.png]]
378 +[[image:image-20240129164219-4.png||height="612" width="440"]]
378 378  
379 379  
380 -In LG02 console, we can see the hex receive are:
381 381  
382 -[[image:image-20220526171112-21.png]]
382 +(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
383 383  
384 +[[image:image-20240129164326-5.png||height="506" width="1114"]]
384 384  
385 385  
386 -(% style="color:blue" %)**3. Decode the info in web**
387 +In LPS8-v2 console, we can see the Base64 receive are:
387 387  
388 -[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
389 +[[image:image-20240129170137-6.png||height="459" width="1116"]]
389 389  
390 -Need these three fields:
391 391  
392 -LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
393 393  
394 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
393 +(% style="color:blue" %)**3. Decode the info **
395 395  
396 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
395 +Need these three fields:
397 397  
397 +LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 (from LPS8-v2)
398 398  
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]]
399 +AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF (End node Network Session Key)
400 400  
401 +AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF (End Node App Session Key)
402 +
403 +
401 401  [[image:image-20220526171029-20.png]]
402 402  
403 403  (((
... ... @@ -449,7 +449,7 @@
449 449  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
450 450  
451 451  
452 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
455 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
453 453  
454 454  
455 455  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -544,7 +544,7 @@
544 544  (Any combination of 16 bit codes can be used）
545 545  
546 546  
547 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
550 += 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
548 548  )))
549 549  
550 550  
... ... @@ -575,6 +575,3 @@
575 575  
576 576  
577 577  [[image:image-20221215223215-1.png||height="584" width="1280"]]
578 -
579 -(% class="wikigeneratedid" %)
580 -
image-20240129154321-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content

Applications

Navigation

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