<
From version < 4.9 >
edited by Xiaoling
on 2022/05/11 15:20
To version < 4.4 >
edited by Xiaoling
on 2022/05/11 14:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -195,23 +195,15 @@
195 195  
196 196  == 5.2 See Debug Info ==
197 197  
198 -(((
199 199  **For LoRaWAN Server**
200 -)))
201 201  
202 -(((
203 203  We can check if there is downlink message for this end node, use TTN for example:
204 -)))
205 205  
206 -(((
207 207  Configure a downstream to the end device
208 -)))
209 209  
210 210  [[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
211 211  
212 -(((
213 213  Set a downstream in TTN and see it is sent
214 -)))
215 215  
216 216  
217 217  (((
... ... @@ -220,14 +220,10 @@
220 220  
221 221  [[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
222 222  
223 -(((
224 224  Gateway Traffic can see this downstream info
225 -)))
226 226  
227 227  
228 -(((
229 229  **For LoRaWAN Gateway**
230 -)))
231 231  
232 232  (((
233 233  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:
... ... @@ -235,79 +235,61 @@
235 235  
236 236  [[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
237 237  
238 -(((
239 239  Gateway Sent out this packet
240 -)))
241 241  
242 242  
243 -(((
244 244  **For End Node**
245 -)))
246 246  
247 -(((
248 248  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
249 -)))
250 250  
251 -(((
252 -
253 -)))
254 -
255 -(((
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
235 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
262 262  )))
263 -)))
264 264  
265 265  (% class="box infomessage" %)
266 266  (((
267 -AT+RX2DR=3 ~-~--> The RX2 DataRate
240 + AT+RX2DR=3 ~-~--> The RX2 DataRate
268 268  )))
269 269  
270 270  (% class="box infomessage" %)
271 271  (((
272 - AT+RX1DL=1000 ~-~--> Receive Delay 1
245 + AT+RX1DL=1000 ~-~--> Receive Delay 1
273 273  )))
274 274  
275 275  (% class="box infomessage" %)
276 276  (((
277 - AT+RX2DL=2000 ~-~--> Receive Delay 2
250 + AT+RX2DL=2000 ~-~--> Receive Delay 2
278 278  )))
279 279  
280 -(((
281 -**when the device running, we can see below info:**
282 -)))
253 +when the device running, we can see below info:
283 283  
284 -{{{ [12502]***** UpLinkCounter= 0 *****
285 - [12503]TX on freq 868500000 Hz at DR 0
286 - [13992]txDone
287 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
288 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
289 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
290 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
291 -
255 +(% class="box" %)
292 292  (((
293 -
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)
294 294  )))
295 295  
266 +(% class="box" %)
296 296  (((
297 -**Another message:**
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
298 298  )))
299 299  
300 -{{{ [12502]***** UpLinkCounter= 0 *****
301 - [12503]TX on freq 868100000 Hz at DR 0
302 - [13992]txDone
303 - [15022]RX on freq 868100000 Hz at DR 0
304 - [15222]rxTimeOut
305 - [15987]RX on freq 869525000 Hz at DR 3
306 - [16185]rxDone --> We have got the downstream packet.
307 - Rssi= -64
308 - Receive data
309 - 1:0012345678}}}
310 -
311 311  == 5.3 If problem doesn’t solve ==
312 312  
313 313  **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:**
... ... @@ -319,27 +319,14 @@
319 319  
320 320  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
321 321  
322 -(((
323 323  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.
324 -)))
325 325  
326 -(((
327 -
328 -)))
329 -
330 -(((
331 331  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:
332 -)))
333 333  
334 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
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 +}}}
335 335  
336 -(((
337 -
338 -)))
339 -
340 -(((
341 341  In this case, please double check the gateway frequency and the server frequency band.
342 -)))
343 343  
344 344  
345 345  = 7. Decrypt a LoRaWAN Packet =
... ... @@ -383,9 +383,7 @@
383 383  
384 384  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
385 385  
386 -(((
387 387  [[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]]
388 -)))
389 389  
390 390  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
391 391  
... ... @@ -398,58 +398,32 @@
398 398  
399 399  = 9. Why do I see a "MIC Mismatch" error message from the server? =
400 400  
401 -(((
402 402  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
403 -)))
404 404  
405 -(((
406 406  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
407 -)))
408 408  
409 -* (((
410 -Please note the distinction between "APPKEY" and "APPSKEY".
411 -)))
360 +* Please note the distinction between "APPKEY" and "APPSKEY".
412 412  
413 -(((
414 414  2)If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
415 -)))
416 416  
417 -(((
418 418  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
419 -)))
420 420  
421 -* (((
422 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
423 -)))
366 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
424 424  
425 425  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
426 426  
427 -* (((
428 -If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
429 -)))
370 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
430 430  
431 -(((
432 432  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
433 -)))
434 434  
435 -(((
436 436  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,
437 -)))
438 438  
439 -(((
440 440  and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
441 -)))
442 442  
443 -(((
444 444  so it will send a normal uplink packet, and an additional 00 data packet.
445 -)))
446 446  
447 -* (((
448 -Solution: Use the decoder to filter out this 00 packet.
449 -)))
450 -* (((
451 -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
452 -)))
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
453 453  
454 454  (% class="wikigeneratedid" id="H" %)
455 455  
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0