<
From version < 4.17 >
edited by Xiaoling
on 2022/05/11 15:34
To version < 4.7 >
edited by Xiaoling
on 2022/05/11 14:57
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -244,36 +244,44 @@
244 244  **For End Node**
245 245  )))
246 246  
247 -(((
248 248  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
248 +
249 +(% class="box infomessage" %)
250 +(((
251 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
249 249  )))
250 250  
254 +(% class="box infomessage" %)
251 251  (((
252 -
256 + AT+RX2DR=3 ~-~--> The RX2 DataRate
253 253  )))
254 254  
259 +(% class="box infomessage" %)
255 255  (((
261 + AT+RX1DL=1000 ~-~--> Receive Delay 1
262 +)))
263 +
256 256  (% class="box infomessage" %)
257 257  (((
258 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
259 -AT+RX2DR=3      ~-~--> The RX2 DataRate
260 -AT+RX1DL=1000   ~-~--> Receive Delay 1
261 -AT+RX2DL=2000   ~-~--> Receive Delay 2
266 + AT+RX2DL=2000 ~-~--> Receive Delay 2
262 262  )))
263 -)))
264 264  
265 265  (((
266 266  **when the device running, we can see below info:**
267 267  )))
268 268  
269 -{{{ [12502]***** UpLinkCounter= 0 *****
270 - [12503]TX on freq 868500000 Hz at DR 0
271 - [13992]txDone
272 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
273 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
274 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
275 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
273 +(((
274 +
275 +)))
276 276  
277 +{{{ [12502]***** UpLinkCounter= 0 *****
278 + [12503]TX on freq 868500000 Hz at DR 0
279 + [13992]txDone
280 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
281 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
282 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
283 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
284 +
277 277  (((
278 278  
279 279  )))
... ... @@ -282,16 +282,16 @@
282 282  **Another message:**
283 283  )))
284 284  
285 -{{{ [12502]***** UpLinkCounter= 0 *****
286 - [12503]TX on freq 868100000 Hz at DR 0
287 - [13992]txDone
288 - [15022]RX on freq 868100000 Hz at DR 0
289 - [15222]rxTimeOut
290 - [15987]RX on freq 869525000 Hz at DR 3
291 - [16185]rxDone --> We have got the downstream packet.
292 - Rssi= -64
293 - Receive data
294 - 1:0012345678}}}
293 +{{{ [12502]***** UpLinkCounter= 0 *****
294 + [12503]TX on freq 868100000 Hz at DR 0
295 + [13992]txDone
296 + [15022]RX on freq 868100000 Hz at DR 0
297 + [15222]rxTimeOut
298 + [15987]RX on freq 869525000 Hz at DR 3
299 + [16185]rxDone --> We have got the downstream packet.
300 + Rssi= -64
301 + Receive data
302 + 1:0012345678}}}
295 295  
296 296  == 5.3 If problem doesn’t solve ==
297 297  
... ... @@ -368,13 +368,13 @@
368 368  
369 369  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
370 370  
379 +(((
371 371  [[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]]
381 +)))
372 372  
373 373  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
374 374  
375 -(((
376 - The FRMPayload is the device payload.
377 -)))
385 +The FRMPayload is the device payload.
378 378  
379 379  
380 380  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -409,22 +409,24 @@
409 409  
410 410  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
411 411  
412 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
420 +* (((
421 +If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
422 +)))
413 413  
414 414  (((
415 - When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
425 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
416 416  )))
417 417  
418 418  (((
419 - 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,
429 +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,
420 420  )))
421 421  
422 422  (((
423 - 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
433 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
424 424  )))
425 425  
426 426  (((
427 - uplink packet, and an additional 00 data packet.
437 +so it will send a normal uplink packet, and an additional 00 data packet.
428 428  )))
429 429  
430 430  * (((
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0