Summary

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

Details

Page properties

Content

...	...	@@ -205,7 +205,6 @@
205	205	* This packet must match the frequency of the RX1 or RX2 window.
206	206	* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
207	207
208		-
209	209	== 5.2 See Debug Info ==
210	210
211	211
...	...	@@ -263,20 +263,15 @@
263	263	)))
264	264
265	265	(((
	265	+(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	266	+(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
	267	+(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	268	+(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	269	+
266	266
267	267	)))
268	268
269	269	(((
270		-(% class="box infomessage" %)
271		-(((
272		-AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
273		-AT+RX2DR=3      ~-~--> The RX2 DataRate
274		-AT+RX1DL=1000   ~-~--> Receive Delay 1
275		-AT+RX2DL=2000   ~-~--> Receive Delay 2
276		-)))
277		-)))
278		-
279		-(((
280	280	(% style="color:blue" %)**when the device running, we can see below info:**
281	281	)))
282	282
...	...	@@ -308,8 +308,9 @@
308	308	1:0012345678}}}
309	309
310	310
311		-== 5.3 If problem doesn’t solve ==
	305	+== 5.3 If problem doesn't solve ==
312	312
	307	+
313	313	(% style="color:red" %)**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:**
314	314
315	315	* End node console to show the transmit freuqency and DR.
...	...	@@ -317,8 +317,12 @@
317	317	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
318	318	* End Node traffic (from server UI) to shows end node activity in server.
319	319
	315	+
	316	+
	317	+
320	320	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
321	321
	320	+
322	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	324	)))
...	...	@@ -344,19 +344,17 @@
344	344
345	345	= 7. Decrypt a LoRaWAN Packet =
346	346
347		-~1. LHT65 End device configure:
348	348
349		-(% class="box infomessage" %)
350		-(((
351		-**Change to ABP Mode: AT+NJM=0**
352		-**Change to fix frequency: AT+CHS=904900000**
353		-**Change to fix DR: AT+DR=0**
354		-)))
	347	+(% style="color:blue" %)**1. LHT65 End device configure:**
355	355
	349	+**Change to ABP Mode:  AT+NJM=0**
	350	+**Change to fix frequency:  AT+CHS=904900000**
	351	+**Change to fix DR:  AT+DR=0**
	352	+
356	356	[[image:image-20220526165525-16.png]]
357	357
358	358
359		-2. In LG02 , configure to receive above message
	356	+(% style="color:blue" %)**2. In LG02 , configure to receive above message**
360	360
361	361	[[image:image-20220526165612-17.png]]
362	362
...	...	@@ -366,7 +366,7 @@
366	366	[[image:image-20220526171112-21.png]]
367	367
368	368
369		-3. Decode the info in web
	366	+(% style="color:blue" %)**3. Decode the info in web**
370	370
371	371	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
372	372
...	...	@@ -378,6 +378,7 @@
378	378
379	379	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
380	380
	378	+
381	381	[[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]]
382	382
383	383	[[image:image-20220526171029-20.png]]
...	...	@@ -389,13 +389,15 @@
389	389
390	390	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
391	391
	390	+
392	392	Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
393	393
394	394
395	395	= 9. Why do I see a "MIC Mismatch" error message from the server? =
396	396
	396	+
397	397	(((
398		-1)If the user receives a "MIC Mismatch" message after registering the node on the server.
	398	+1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
399	399	)))
400	400
401	401	(((
...	...	@@ -417,11 +417,14 @@
417	417	* (((
418	418	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
419	419
	420	+
	421	+
420	420
421	421	)))
422	422
423	423	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
424	424
	427	+
425	425	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
426	426
427	427	(((
...	...	@@ -438,11 +438,14 @@
438	438	* (((
439	439	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>>mailto:david.huang@dragino.cc]]
440	440
	444	+
	445	+
441	441
442	442	)))
443	443
444	444	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
445	445
	451	+
446	446	(((
447	447	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
448	448	)))
...	...	@@ -473,6 +473,8 @@
473	473
474	474	(((
475	475	You can rewrites the keys by running commands in AT Console
	482	+
	483	+
476	476	)))
477	477
478	478	(((