Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 62.1
edited by Mengting Qiu
on 2024/01/29 15:43
Change comment: Uploaded new attachment "image-20240129154321-9.png", version {1}
To version 100.1
edited by Bei Jinggeng
on 2025/04/29 13:36
Change comment: Uploaded new attachment "image-20250429133640-7.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Bei
Content
... ... @@ -163,9 +163,112 @@
163 163  )))
164 164  
165 165  
166 -= 4. Transmision on ABP Mode =
166 += 4. Why i see packet lost =
167 167  
168 +== **1. Signal problem** ==
168 168  
170 +
171 +1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
172 +
173 +Reason:
174 +
175 +When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
176 +At this time, the server is at risk of losing uplink.
177 +
178 +
179 +Solution:
180 +
181 +Users can manually fix the DR value.
182 +
183 +
184 +(% style="color:red" %)
185 +**Notice:**
186 +
187 +* User need to set Adaptive Data Rate(ADR)=0 first. otherwise device will respond to server's ADR command and change the DR according to server auto-adjustment.
188 +
189 +* Data Rate specifies Spreading Factor. The mapping varies in different frequency bands. User can check this link for detail. [[rp2-1.0.3-lorawan-regional-parameters.pdf>>https://lora-alliance.org/resource_hub/rp2-1-0-3-lorawan-regional-parameters/]]
190 +
191 +(% style="color:blue" %)**AT Command: AT+DR**
192 +
193 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
194 +|(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:147px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response**
195 +|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
196 +OK
197 +)))
198 +|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
199 +
200 +)))
201 +
202 +(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
203 +
204 +If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
205 +
206 +* **Example 1**: Downlink Payload: **220001FF**  ~/~/ Set AT+DR=1.
207 +
208 +* **Example 2**: Downlink Payload: **220000FF**  ~/~/ Set AT+DR=0.
209 +
210 +(% style="display:none" %) (%%)
211 +
212 +
213 +2)  (% style="color:blue" %)**Node antenna problem**
214 +
215 +Reason:
216 +
217 +Node antenna is loose
218 +
219 +
220 +Solution:
221 +
222 +Please check whether the antenna interface and module interface are detached
223 +
224 +[[image:image-20250429114526-1.png||height="429" width="303"]]
225 +
226 +
227 +
228 +3) (% style="color:blue" %)**Gateway antenna problem**
229 +
230 +Reason:
231 +Gateway uses antenna with wrong frequency band
232 +
233 +For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
234 +
235 +
236 +Solution:
237 +
238 +Please check whether the silk screen on the antenna conflicts with the frequency you set.
239 +
240 +[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
241 +
242 +
243 +4) (% style="color:blue" %)**Gateway module problem**
244 +
245 +Reason:
246 +
247 +Gateway uses module with wrong frequency band
248 +For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
249 +
250 +
251 +Solution:
252 +
253 +Please check whether the silkscreen of the module conflicts with the frequency you set.
254 +
255 +[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
256 +
257 +
258 +== **2. Frequency point problem** ==
259 +
260 +The frequency point of the gateway or server is wrong or missing.
261 +
262 +
263 +== **3. Frequency band problem** ==
264 +
265 +When there are multiple gateways, the node cannot lock the frequency band.
266 +
267 +
268 +
269 += 5. Transmision on ABP Mode =
270 +
271 +
169 169  (((
170 170  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
171 171  )))
... ... @@ -185,15 +185,20 @@
185 185  Disable Frame Counter Check in ABP Mode
186 186  
187 187  
188 -= 5. Downstream Debug =
291 += 6. Downstream Debug =
189 189  
190 -== 5.1 How it work ==
293 +== 6.1 How it work ==
191 191  
192 192  
193 193  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
194 194  
195 195  (((
196 -Depends on Class A or Class C, the receive windows will be a little difference.
299 +Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
300 +
301 +* **Class A** : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
302 +* **Class C**: End node can receive downlink immediately but have higher power consumption.
303 +
304 +
197 197  )))
198 198  
199 199  [[image:image-20220531161828-1.png]]
... ... @@ -213,7 +213,7 @@
213 213  
214 214  * 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.**
215 215  
216 -== 5.2 See Debug Info ==
324 +== 6.2 See Debug Info ==
217 217  
218 218  
219 219  (((
... ... @@ -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  
346 +(% 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  
348 +
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.
350 +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
356 +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:
366 +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]]
369 +[[image:image-20240129154321-9.png]]
261 261  
262 262  (((
263 263  Gateway Sent out this packet
... ... @@ -317,7 +317,7 @@
317 317   1:0012345678}}}
318 318  
319 319  
320 -== 5.3 If problem doesn't solve ==
429 +== 6.3 If problem doesn't solve ==
321 321  
322 322  
323 323  (% 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:**
... ... @@ -330,11 +330,11 @@
330 330  
331 331  * End Node traffic (from server UI) to shows end node activity in server.
332 332  
333 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
442 += 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
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.
446 +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  (((
... ... @@ -356,62 +356,83 @@
356 356  )))
357 357  
358 358  
359 -= 7. Decrypt a LoRaWAN Packet =
468 += 8. Decrypt a LoRaWAN Packet =
360 360  
361 361  
362 -(% style="color:blue" %)**1. LHT65 End device configure:**
471 +(% 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**
475 +**Change to fix frequency:  ​​​​AT+CHE=1**
367 367  
368 -**Change to fix DR:  AT+DR=0**
369 369  
478 +**AT+CFG(Print configuration):**
370 370  
371 -[[image:image-20220526165525-16.png]]
480 +[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
372 372  
373 373  
374 374  
375 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
484 +**Configuration: **
376 376  
377 -[[image:image-20220526165612-17.png]]
486 +[[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]]
490 +(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
383 383  
492 +[[image:image-20240129164326-5.png||height="506" width="1114"]]
384 384  
385 385  
386 -(% style="color:blue" %)**3. Decode the info in web**
495 +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/]]
497 +[[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)
501 +(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
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)
503 +LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
397 397  
505 +Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
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]]
400 400  
401 -[[image:image-20220526171029-20.png]]
508 +**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
402 402  
403 -(((
404 - The FRMPayload is the device payload.
405 -)))
510 +[[image:image-20240129190752-17.png||height="338" width="901"]]
406 406  
512 +[[image:image-20240129191937-21.png||height="450" width="901"]]
407 407  
408 -= 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
409 409  
515 +**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
410 410  
517 +[[image:image-20240129192239-22.png||height="416" width="902"]]
518 +
519 +[[image:image-20240129192549-23.png||height="459" width="898"]]
520 +
521 +
522 +**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
523 +
524 +
525 +
526 +
527 +[[image:image-20240129192908-24.png||height="477" width="907"]]
528 +
529 +
530 +[[image:image-20240129192954-25.png||height="485" width="916"]]
531 +
532 +
533 +
534 +
535 +
536 +
537 +
538 += 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
539 +
540 +
411 411  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
412 412  
413 413  
414 -= 9. Why do I see a "MIC Mismatch" error message from the server? =
544 += 10. Why do I see a "MIC Mismatch" error message from the server? =
415 415  
416 416  
417 417  (((
... ... @@ -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~=~="? =
582 += 11. Why I got the payload only with "0x00" or "AA~=~="? =
453 453  
454 454  
455 455  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -483,7 +483,7 @@
483 483  Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
484 484  
485 485  
486 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
616 += 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
487 487  
488 488  
489 489  (((
... ... @@ -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? =
677 += 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
548 548  )))
549 549  
550 550  
... ... @@ -551,7 +551,7 @@
551 551  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
552 552  
553 553  
554 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
684 += 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
555 555  
556 556  
557 557  In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
... ... @@ -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-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
image-20240129175037-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129190752-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +62.4 KB
Content
image-20250429114526-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +3.2 MB
Content
image-20250429115124-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +193.2 KB
Content
image-20250429115159-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1014.1 KB
Content
image-20250429115942-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429133640-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content