Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.4 >
edited by Xiaoling
on 2022/05/11 14:42
To version < 14.2 >
edited by Xiaoling
on 2022/05/26 16:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,9 @@
1 1  **~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
... ... @@ -19,7 +19,7 @@
19 19  * If the device is sending join request to server?
20 20  * What frequency the device is sending?
21 21  
22 -[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
26 +[[image:image-20220526163523-1.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
... ... @@ -29,7 +29,7 @@
29 29  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
30 30  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
31 31  
32 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
36 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
... ... @@ -40,7 +40,7 @@
40 40  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
41 41  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
47 +[[image:image-20220526163633-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
... ... @@ -49,11 +49,11 @@
49 49  
50 50  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
51 51  
52 -[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
56 +[[image:image-20220526163704-4.png]]
53 53  
54 54  The data for the end device set in server
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
60 +[[image:image-20220526163732-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
... ... @@ -94,11 +94,11 @@
94 94  Here are the freuqency tables for these bands as reference:
95 95  )))
96 96  
97 -[[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
101 +[[image:image-20220526163801-6.png]]
98 98  
99 99  US915 Channels
100 100  
101 -[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
105 +[[image:https://wiki.dragino.com/images/8/8a/AU915_FRE_BAND-1.png]]
102 102  
103 103  AU915 Channels
104 104  
... ... @@ -195,15 +195,23 @@
195 195  
196 196  == 5.2 See Debug Info ==
197 197  
202 +(((
198 198  **For LoRaWAN Server**
204 +)))
199 199  
206 +(((
200 200  We can check if there is downlink message for this end node, use TTN for example:
208 +)))
201 201  
210 +(((
202 202  Configure a downstream to the end device
212 +)))
203 203  
204 204  [[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
205 205  
216 +(((
206 206  Set a downstream in TTN and see it is sent
218 +)))
207 207  
208 208  
209 209  (((
... ... @@ -212,10 +212,14 @@
212 212  
213 213  [[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
214 214  
227 +(((
215 215  Gateway Traffic can see this downstream info
229 +)))
216 216  
217 217  
232 +(((
218 218  **For LoRaWAN Gateway**
234 +)))
219 219  
220 220  (((
221 221  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:
... ... @@ -223,61 +223,64 @@
223 223  
224 224  [[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
225 225  
242 +(((
226 226  Gateway Sent out this packet
244 +)))
227 227  
228 228  
247 +(((
229 229  **For End Node**
249 +)))
230 230  
231 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 -
233 -(% class="box infomessage" %)
234 234  (((
235 - AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
252 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
236 236  )))
237 237  
238 -(% class="box infomessage" %)
239 239  (((
240 - AT+RX2DR=3 ~-~--> The RX2 DataRate
256 +
241 241  )))
242 242  
259 +(((
243 243  (% class="box infomessage" %)
244 244  (((
245 - AT+RX1DL=1000 ~-~--> Receive Delay 1
262 +AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
263 +AT+RX2DR=3      ~-~--> The RX2 DataRate
264 +AT+RX1DL=1000   ~-~--> Receive Delay 1
265 +AT+RX2DL=2000   ~-~--> Receive Delay 2
246 246  )))
267 +)))
247 247  
248 -(% class="box infomessage" %)
249 249  (((
250 - AT+RX2DL=2000 ~-~--> Receive Delay 2
270 +**when the device running, we can see below info:**
251 251  )))
252 252  
253 -when the device running, we can see below info:
273 +{{{ [12502]***** UpLinkCounter= 0 *****
274 + [12503]TX on freq 868500000 Hz at DR 0
275 + [13992]txDone
276 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
277 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
278 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
279 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
254 254  
255 -(% class="box" %)
256 256  (((
257 - [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
258 - [12503]TX on freq 868500000 Hz at DR 0
259 - [13992]txDone
260 - [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
261 - [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
262 - [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
263 - [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
282 +
264 264  )))
265 265  
266 -(% class="box" %)
267 267  (((
268 - Another message:
269 - [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
270 - [12503]TX on freq 868100000 Hz at DR 0
271 - [13992]txDone
272 - [15022]RX on freq 868100000 Hz at DR 0
273 - [15222]rxTimeOut
274 - [15987]RX on freq 869525000 Hz at DR 3
275 - [16185]rxDone                              ~-~-> We have got the downstream packet.
276 - Rssi= -64
277 - Receive data
278 - 1:0012345678
286 +**Another message:**
279 279  )))
280 280  
289 +{{{ [12502]***** UpLinkCounter= 0 *****
290 + [12503]TX on freq 868100000 Hz at DR 0
291 + [13992]txDone
292 + [15022]RX on freq 868100000 Hz at DR 0
293 + [15222]rxTimeOut
294 + [15987]RX on freq 869525000 Hz at DR 3
295 + [16185]rxDone --> We have got the downstream packet.
296 + Rssi= -64
297 + Receive data
298 + 1:0012345678}}}
299 +
281 281  == 5.3 If problem doesn’t solve ==
282 282  
283 283  **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:**
... ... @@ -289,14 +289,27 @@
289 289  
290 290  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
291 291  
311 +(((
292 292  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.
313 +)))
293 293  
315 +(((
316 +
317 +)))
318 +
319 +(((
294 294  So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below:
321 +)))
295 295  
296 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
297 -}}}
323 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
298 298  
325 +(((
326 +
327 +)))
328 +
329 +(((
299 299  In this case, please double check the gateway frequency and the server frequency band.
331 +)))
300 300  
301 301  
302 302  = 7. Decrypt a LoRaWAN Packet =
... ... @@ -344,7 +344,9 @@
344 344  
345 345  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
346 346  
347 -The FRMPayload is the device payload.
379 +(((
380 + The FRMPayload is the device payload.
381 +)))
348 348  
349 349  
350 350  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -353,32 +353,83 @@
353 353  
354 354  = 9. Why do I see a "MIC Mismatch" error message from the server? =
355 355  
390 +(((
356 356  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
392 +)))
357 357  
394 +(((
358 358  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
396 +)))
359 359  
360 -* Please note the distinction between "APPKEY" and "APPSKEY".
398 +* (((
399 +Please note the distinction between "APPKEY" and "APPSKEY".
400 +)))
361 361  
402 +(((
362 362  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
404 +)))
363 363  
406 +(((
364 364  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
408 +)))
365 365  
366 -* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
410 +* (((
411 +If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
367 367  
413 +
414 +)))
415 +
368 368  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
369 369  
370 370  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
371 371  
420 +(((
372 372  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
422 +)))
373 373  
374 -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,
424 +(((
425 +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,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 uplink packet, and an additional 00 data packet.
426 +)))
375 375  
376 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
428 +* (((
429 +Solution: Use the decoder to filter out this 00 packet.
430 +)))
431 +* (((
432 +Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
377 377  
378 -so it will send a normal uplink packet, and an additional 00 data packet.
379 379  
380 -* Solution: Use the decoder to filter out this 00 packet.
381 -* Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
435 +
436 +)))
382 382  
383 -(% class="wikigeneratedid" id="H" %)
438 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439 +
440 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
441 +
442 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
443 +
444 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
445 +
446 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 +
448 +AT+APPEUI=00 00 00 00 00 00 00 00
449 +
450 +
451 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
452 +
453 +You can rewrites the keys by running commands in AT Console
454 +
455 +For example：
456 +
457 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
458 +
459 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
460 +
461 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
462 +
463 +AT+APPEUI=2C 45 47 E3 24 12 23 24
464 +
465 +(Any combination of 16 bit codes can be used）
466 +
467 +
468 +(% class="wikigeneratedid" %)
384 384  
image-20220526163523-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content

Applications

Navigation

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