Summary

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

Details

Page properties

Content

...	...	@@ -16,8 +16,10 @@
16	16	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17	17	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
18	18
19		-**~1. End Device Join Screen shot, we can check:**
20	20
	20	+
	21	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	22	+
21	21	* If the device is sending join request to server?
22	22	* What frequency the device is sending?
23	23
...	...	@@ -26,7 +26,7 @@
26	26	Console Output from End device to see the transmit frequency
27	27
28	28
29		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
	31	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
30	30
31	31	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
32	32	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
...	...	@@ -36,7 +36,7 @@
36	36	Console Output from Gateway to see packets between end node and server.
37	37
38	38
39		-**3. Gateway Traffic Page in LoRaWAN Server**
	41	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
40	40
41	41	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
42	42	* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
...	...	@@ -47,7 +47,7 @@
47	47	The Traffic for the End node in the server, use TTN as example
48	48
49	49
50		-**4. Data Page in LoRaWAN server**
	52	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
51	51
52	52	* If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
53	53
...	...	@@ -302,8 +302,9 @@
302	302	1:0012345678}}}
303	303
304	304
305		-== 5.3 If problem doesn’t solve ==
	307	+== 5.3 If problem doesn't solve ==
306	306
	309	+
307	307	(% 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:**
308	308
309	309	* End node console to show the transmit freuqency and DR.
...	...	@@ -311,8 +311,11 @@
311	311	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
312	312	* End Node traffic (from server UI) to shows end node activity in server.
313	313
	317	+
	318	+
314	314	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
315	315
	321	+
316	316	(((
317	317	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.
318	318	)))
...	...	@@ -338,19 +338,18 @@
338	338
339	339	= 7. Decrypt a LoRaWAN Packet =
340	340
341		-~1. LHT65 End device configure:
342	342
343		-(% class="box infomessage" %)
344		-(((
345		-**Change to ABP Mode: AT+NJM=0**
346		-**Change to fix frequency: AT+CHS=904900000**
347		-**Change to fix DR: AT+DR=0**
348		-)))
	348	+(% style="color:blue" %)**1. LHT65 End device configure:**
349	349
	350	+**Change to ABP Mode:  AT+NJM=0**
	351	+**Change to fix frequency:  AT+CHS=904900000**
	352	+**Change to fix DR:  AT+DR=0**
	353	+
	354	+
350	350	[[image:image-20220526165525-16.png]]
351	351
352	352
353		-2. In LG02 , configure to receive above message
	358	+(% style="color:blue" %)**2. In LG02 , configure to receive above message**
354	354
355	355	[[image:image-20220526165612-17.png]]
356	356
...	...	@@ -360,7 +360,7 @@
360	360	[[image:image-20220526171112-21.png]]
361	361
362	362
363		-3. Decode the info in web
	368	+(% style="color:blue" %)**3. Decode the info in web**
364	364
365	365	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
366	366
...	...	@@ -372,6 +372,7 @@
372	372
373	373	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
374	374
	380	+
375	375	[[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]]
376	376
377	377	[[image:image-20220526171029-20.png]]
...	...	@@ -383,13 +383,15 @@
383	383
384	384	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
385	385
	392	+
386	386	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.
387	387
388	388
389	389	= 9. Why do I see a "MIC Mismatch" error message from the server? =
390	390
	398	+
391	391	(((
392		-1)If the user receives a "MIC Mismatch" message after registering the node on the server.
	400	+1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
393	393	)))
394	394
395	395	(((
...	...	@@ -411,11 +411,14 @@
411	411	* (((
412	412	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
413	413
	422	+
	423	+
414	414
415	415	)))
416	416
417	417	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
418	418
	429	+
419	419	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
420	420
421	421	(((
...	...	@@ -432,11 +432,14 @@
432	432	* (((
433	433	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]]
434	434
	446	+
	447	+
435	435
436	436	)))
437	437
438	438	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439	439
	453	+
440	440	(((
441	441	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
442	442	)))
...	...	@@ -467,6 +467,8 @@
467	467
468	468	(((
469	469	You can rewrites the keys by running commands in AT Console
	484	+
	485	+
470	470	)))
471	471
472	472	(((