Summary

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

Details

Page properties

Content

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