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
...	...	@@ -349,6 +349,7 @@
349	349	**Change to fix frequency:  AT+CHS=904900000**
350	350	**Change to fix DR:  AT+DR=0**
351	351
	354	+
352	352	[[image:image-20220526165525-16.png]]
353	353
354	354
...	...	@@ -374,6 +374,7 @@
374	374
375	375	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
376	376
	380	+
377	377	[[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]]
378	378
379	379	[[image:image-20220526171029-20.png]]
...	...	@@ -385,13 +385,15 @@
385	385
386	386	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
387	387
	392	+
388	388	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.
389	389
390	390
391	391	= 9. Why do I see a "MIC Mismatch" error message from the server? =
392	392
	398	+
393	393	(((
394		-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.
395	395	)))
396	396
397	397	(((
...	...	@@ -413,11 +413,14 @@
413	413	* (((
414	414	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
415	415
	422	+
	423	+
416	416
417	417	)))
418	418
419	419	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
420	420
	429	+
421	421	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
422	422
423	423	(((
...	...	@@ -434,11 +434,14 @@
434	434	* (((
435	435	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]]
436	436
	446	+
	447	+
437	437
438	438	)))
439	439
440	440	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
441	441
	453	+
442	442	(((
443	443	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
444	444	)))
...	...	@@ -469,6 +469,8 @@
469	469
470	470	(((
471	471	You can rewrites the keys by running commands in AT Console
	484	+
	485	+
472	472	)))
473	473
474	474	(((