Summary

• Page properties (1 modified, 0 added, 0 removed)

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,14 +235,10 @@
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	247	we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
248	248
...	...	@@ -274,13 +274,16 @@
274	274
275	275	)))
276	276
277		-{{{ [12502]***** UpLinkCounter= 0 *****
	261	+(% class="box" %)
	262	+(((
	263	+ [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
278	278	[12503]TX on freq 868500000 Hz at DR 0
279	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)}}}
	266	+ [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
	267	+ [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
	268	+ [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
	269	+ [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
	270	+)))
284	284
285	285	(((
286	286
...	...	@@ -290,17 +290,18 @@
290	290	**Another message:**
291	291	)))
292	292
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	303
	281	+ [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
	282	+ [12503]TX on freq 868100000 Hz at DR 0
	283	+ [13992]txDone
	284	+ [15022]RX on freq 868100000 Hz at DR 0
	285	+ [15222]rxTimeOut
	286	+ [15987]RX on freq 869525000 Hz at DR 3
	287	+ [16185]rxDone                              ~-~-> We have got the downstream packet.
	288	+ Rssi= -64
	289	+ Receive data
	290	+ 1:0012345678
	291	+
304	304	== 5.3 If problem doesn’t solve ==
305	305
306	306	**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:**
...	...	@@ -324,10 +324,8 @@
324	324	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	325	)))
326	326
327		-{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
328		-
329	329	(((
330		-
	316	+Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
331	331	)))
332	332
333	333	(((
...	...	@@ -376,9 +376,7 @@
376	376
377	377	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
378	378
379		-(((
380	380	[[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		-)))
382	382
383	383	[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
384	384
...	...	@@ -391,58 +391,32 @@
391	391
392	392	= 9. Why do I see a "MIC Mismatch" error message from the server? =
393	393
394		-(((
395	395	1)If the user receives a "MIC Mismatch" message after registering the node on the server.
396		-)))
397	397
398		-(((
399	399	It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
400		-)))
401	401
402		-* (((
403		-Please note the distinction between "APPKEY" and "APPSKEY".
404		-)))
	382	+* Please note the distinction between "APPKEY" and "APPSKEY".
405	405
406		-(((
407	407	2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
408		-)))
409	409
410		-(((
411	411	The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
412		-)))
413	413
414		-* (((
415		-If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
416		-)))
	388	+* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
417	417
418	418	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
419	419
420		-* (((
421		-If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
422		-)))
	392	+* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
423	423
424		-(((
425	425	When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
426		-)))
427	427
428		-(((
429	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,
430		-)))
431	431
432		-(((
433	433	and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
434		-)))
435	435
436		-(((
437	437	so it will send a normal uplink packet, and an additional 00 data packet.
438		-)))
439	439
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		-)))
	402	+* Solution: Use the decoder to filter out this 00 packet.
	403	+* 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
446	446
447	447	(% class="wikigeneratedid" id="H" %)
448	448