Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 4.4
edited by Xiaoling
on 2022/05/11 14:42
Change comment: There is no comment for this version
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
... ... @@ -195,15 +195,23 @@
195 195  
196 196  == 5.2 See Debug Info ==
197 197  
198 +(((
198 198  **For LoRaWAN Server**
200 +)))
199 199  
202 +(((
200 200  We can check if there is downlink message for this end node, use TTN for example:
204 +)))
201 201  
206 +(((
202 202  Configure a downstream to the end device
208 +)))
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  
212 +(((
206 206  Set a downstream in TTN and see it is sent
214 +)))
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  
223 +(((
215 215  Gateway Traffic can see this downstream info
225 +)))
216 216  
217 217  
228 +(((
218 218  **For LoRaWAN Gateway**
230 +)))
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,10 +223,14 @@
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  
238 +(((
226 226  Gateway Sent out this packet
240 +)))
227 227  
228 228  
243 +(((
229 229  **For End Node**
245 +)))
230 230  
231 231  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 232  
... ... @@ -237,47 +237,54 @@
237 237  
238 238  (% class="box infomessage" %)
239 239  (((
240 - AT+RX2DR=3 ~-~--> The RX2 DataRate
256 + AT+RX2DR=3 ~-~--> The RX2 DataRate
241 241  )))
242 242  
243 243  (% class="box infomessage" %)
244 244  (((
245 - AT+RX1DL=1000 ~-~--> Receive Delay 1
261 + AT+RX1DL=1000 ~-~--> Receive Delay 1
246 246  )))
247 247  
248 248  (% class="box infomessage" %)
249 249  (((
250 - AT+RX2DL=2000 ~-~--> Receive Delay 2
266 + AT+RX2DL=2000 ~-~--> Receive Delay 2
251 251  )))
252 252  
253 -when the device running, we can see below info:
269 +(((
270 +**when the device running, we can see below info:**
271 +)))
254 254  
255 -(% class="box" %)
256 256  (((
257 - [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
274 +
275 +)))
276 +
277 +{{{ [12502]***** UpLinkCounter= 0 *****
258 258   [12503]TX on freq 868500000 Hz at DR 0
259 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)
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 +
285 +(((
286 +
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
290 +**Another message:**
279 279  )))
280 280  
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}}}
303 +
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  
315 +(((
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.
317 +)))
293 293  
319 +(((
320 +
321 +)))
322 +
323 +(((
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:
325 +)))
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 -}}}
327 +{{{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  
329 +(((
330 +
331 +)))
332 +
333 +(((
299 299  In this case, please double check the gateway frequency and the server frequency band.
335 +)))
300 300  
301 301  
302 302  = 7. Decrypt a LoRaWAN Packet =
... ... @@ -340,7 +340,9 @@
340 340  
341 341  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
342 342  
379 +(((
343 343  [[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 +)))
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  
... ... @@ -353,32 +353,58 @@
353 353  
354 354  = 9. Why do I see a "MIC Mismatch" error message from the server? =
355 355  
394 +(((
356 356  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
396 +)))
357 357  
398 +(((
358 358  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
400 +)))
359 359  
360 -* Please note the distinction between "APPKEY" and "APPSKEY".
402 +* (((
403 +Please note the distinction between "APPKEY" and "APPSKEY".
404 +)))
361 361  
406 +(((
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.
408 +)))
363 363  
410 +(((
364 364  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
412 +)))
365 365  
366 -* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
414 +* (((
415 +If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
416 +)))
367 367  
368 368  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
369 369  
370 -* 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 +)))
371 371  
424 +(((
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.
426 +)))
373 373  
428 +(((
374 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,
430 +)))
375 375  
432 +(((
376 376  and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
434 +)))
377 377  
436 +(((
378 378  so it will send a normal uplink packet, and an additional 00 data packet.
438 +)))
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
440 +* (((
441 +Solution: Use the decoder to filter out this 00 packet.
442 +)))
443 +* (((
444 +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
445 +)))
382 382  
383 383  (% class="wikigeneratedid" id="H" %)
384 384