Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Edwin
	1	+XWiki.Xiaoling

Content

...	...	@@ -16,7 +16,7 @@
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		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	19	+**~1. End Device Join Screen shot, we can check:**
20	20
21	21	* If the device is sending join request to server?
22	22	* What frequency the device is sending?
...	...	@@ -26,9 +26,8 @@
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:**
29	29
30		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31		-
32	32	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
33	33	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
34	34
...	...	@@ -37,7 +37,7 @@
37	37	Console Output from Gateway to see packets between end node and server.
38	38
39	39
40		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	39	+**3. Gateway Traffic Page in LoRaWAN Server**
41	41
42	42	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
43	43	* 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.
...	...	@@ -48,7 +48,7 @@
48	48	The Traffic for the End node in the server, use TTN as example
49	49
50	50
51		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	50	+**4. Data Page in LoRaWAN server**
52	52
53	53	* 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.
54	54
...	...	@@ -61,7 +61,6 @@
61	61	Check if OTAA Keys match the keys in device
62	62
63	63
64		-
65	65	= 2. Notice of US915/CN470/AU915 Frequency band =
66	66
67	67
...	...	@@ -133,7 +133,6 @@
133	133	)))
134	134
135	135
136		-
137	137	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
138	138
139	139
...	...	@@ -156,7 +156,6 @@
156	156	)))
157	157
158	158
159		-
160	160	= 4. Transmision on ABP Mode =
161	161
162	162
...	...	@@ -185,7 +185,6 @@
185	185	Disable Frame Counter Check in ABP Mode
186	186
187	187
188		-
189	189	= 5. Downstream Debug =
190	190
191	191	== 5.1 How it work ==
...	...	@@ -210,7 +210,6 @@
210	210	* This packet must match the frequency of the RX1 or RX2 window.
211	211	* 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.**
212	212
213		-
214	214	== 5.2 See Debug Info ==
215	215
216	216
...	...	@@ -244,7 +244,6 @@
244	244	)))
245	245
246	246
247		-
248	248	(((
249	249	(% style="color:blue" %)**For LoRaWAN Gateway**
250	250	)))
...	...	@@ -260,7 +260,6 @@
260	260	)))
261	261
262	262
263		-
264	264	(((
265	265	(% style="color:blue" %)**For End Node**
266	266	)))
...	...	@@ -275,7 +275,6 @@
275	275	(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
276	276	(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
277	277
278		-
279	279
280	280	)))
281	281
...	...	@@ -293,8 +293,6 @@
293	293
294	294	(((
295	295
296		-
297		-
298	298	)))
299	299
300	300	(((
...	...	@@ -313,7 +313,6 @@
313	313	1:0012345678}}}
314	314
315	315
316		-
317	317	== 5.3 If problem doesn't solve ==
318	318
319	319
...	...	@@ -325,6 +325,8 @@
325	325	* End Node traffic (from server UI) to shows end node activity in server.
326	326
327	327
	316	+
	317	+
328	328	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
329	329
330	330
...	...	@@ -351,7 +351,6 @@
351	351	)))
352	352
353	353
354		-
355	355	= 7. Decrypt a LoRaWAN Packet =
356	356
357	357
...	...	@@ -361,11 +361,9 @@
361	361	**Change to fix frequency:  AT+CHS=904900000**
362	362	**Change to fix DR:  AT+DR=0**
363	363
364		-
365	365	[[image:image-20220526165525-16.png]]
366	366
367	367
368		-
369	369	(% style="color:blue" %)**2. In LG02 , configure to receive above message**
370	370
371	371	[[image:image-20220526165612-17.png]]
...	...	@@ -376,7 +376,6 @@
376	376	[[image:image-20220526171112-21.png]]
377	377
378	378
379		-
380	380	(% style="color:blue" %)**3. Decode the info in web**
381	381
382	382	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
...	...	@@ -399,7 +399,6 @@
399	399	)))
400	400
401	401
402		-
403	403	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
404	404
405	405
...	...	@@ -406,7 +406,6 @@
406	406	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.
407	407
408	408
409		-
410	410	= 9. Why do I see a "MIC Mismatch" error message from the server? =
411	411
412	412
...	...	@@ -441,17 +441,26 @@
441	441	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
442	442
443	443
444		-For US915, AU915 or AS923 frequencies.It is possible because: .
	428	+* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
445	445
446		-When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
	430	+(((
	431	+When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
	432	+)))
447	447
448		-When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, so it will send a normal uplink packet, and following an additional 00 data packet to handle this MAC command response.
	434	+(((
	435	+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,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
	436	+)))
449	449
	438	+* (((
450	450	Solution: Use the decoder to filter out this 00 packet.
	440	+)))
	441	+* (((
	442	+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]]
451	451
452		-Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
453	453
454	454
	446	+
	447	+)))
455	455
456	456	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
457	457
...	...	@@ -514,7 +514,6 @@
514	514	(Any combination of 16 bit codes can be used）
515	515
516	516
517		-
518	518	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
519	519	)))
520	520