Summary

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

Details

Page properties

Content

...	...	@@ -266,7 +266,9 @@
266	266	AT+RX2DL=2000 ~-~--> Receive Delay 2
267	267	)))
268	268
	269	+(((
269	269	**when the device running, we can see below info:**
	271	+)))
270	270
271	271	(((
272	272
...	...	@@ -284,10 +284,11 @@
284	284
285	285	)))
286	286
	289	+(((
287	287	**Another message:**
	291	+)))
288	288
289		-{{{
290		- [12502]***** UpLinkCounter= 0 *****
	293	+{{{ [12502]***** UpLinkCounter= 0 *****
291	291	[12503]TX on freq 868100000 Hz at DR 0
292	292	[13992]txDone
293	293	[15022]RX on freq 868100000 Hz at DR 0
...	...	@@ -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		-)))
	327	+{{{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
	379	+(((
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]]
	381	+)))
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
	394	+(((
391	391	1)If the user receives a "MIC Mismatch" message after registering the node on the server.
	396	+)))
392	392
	398	+(((
393	393	It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
	400	+)))
394	394
395		-* Please note the distinction between "APPKEY" and "APPSKEY".
	402	+* (((
	403	+Please note the distinction between "APPKEY" and "APPSKEY".
	404	+)))
396	396
	406	+(((
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.
	408	+)))
398	398
	410	+(((
399	399	The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
	412	+)))
400	400
401		-* 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	+)))
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.
	420	+* (((
	421	+If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
	422	+)))
406	406
	424	+(((
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.
	426	+)))
408	408
	428	+(((
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,
	430	+)))
410	410
	432	+(((
411	411	and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
	434	+)))
412	412
	436	+(((
413	413	so it will send a normal uplink packet, and an additional 00 data packet.
	438	+)))
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
	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	+)))
417	417
418	418	(% class="wikigeneratedid" id="H" %)
419	419