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,8 +26,9 @@
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:**
30	30
	32	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	33	+
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?
33	33
...	...	@@ -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**
	42	+(% 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**
	53	+(% 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
...	...	@@ -60,6 +60,7 @@
60	60	Check if OTAA Keys match the keys in device
61	61
62	62
	66	+
63	63	= 2. Notice of US915/CN470/AU915 Frequency band =
64	64
65	65
...	...	@@ -131,6 +131,7 @@
131	131	)))
132	132
133	133
	138	+
134	134	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
135	135
136	136
...	...	@@ -153,6 +153,7 @@
153	153	)))
154	154
155	155
	161	+
156	156	= 4. Transmision on ABP Mode =
157	157
158	158
...	...	@@ -181,6 +181,7 @@
181	181	Disable Frame Counter Check in ABP Mode
182	182
183	183
	190	+
184	184	= 5. Downstream Debug =
185	185
186	186	== 5.1 How it work ==
...	...	@@ -205,6 +205,9 @@
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
	215	+
	216	+
	217	+
208	208	== 5.2 See Debug Info ==
209	209
210	210
...	...	@@ -238,6 +238,7 @@
238	238	)))
239	239
240	240
	251	+
241	241	(((
242	242	(% style="color:blue" %)**For LoRaWAN Gateway**
243	243	)))
...	...	@@ -253,6 +253,7 @@
253	253	)))
254	254
255	255
	267	+
256	256	(((
257	257	(% style="color:blue" %)**For End Node**
258	258	)))
...	...	@@ -267,6 +267,7 @@
267	267	(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
268	268	(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
269	269
	282	+
270	270
271	271	)))
272	272
...	...	@@ -284,6 +284,8 @@
284	284
285	285	(((
286	286
	300	+
	301	+
287	287	)))
288	288
289	289	(((
...	...	@@ -302,6 +302,7 @@
302	302	1:0012345678}}}
303	303
304	304
	320	+
305	305	== 5.3 If problem doesn't solve ==
306	306
307	307
...	...	@@ -314,6 +314,7 @@
314	314
315	315
316	316
	333	+
317	317	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
318	318
319	319
...	...	@@ -340,6 +340,7 @@
340	340	)))
341	341
342	342
	360	+
343	343	= 7. Decrypt a LoRaWAN Packet =
344	344
345	345
...	...	@@ -349,9 +349,11 @@
349	349	**Change to fix frequency:  AT+CHS=904900000**
350	350	**Change to fix DR:  AT+DR=0**
351	351
	370	+
352	352	[[image:image-20220526165525-16.png]]
353	353
354	354
	374	+
355	355	(% style="color:blue" %)**2. In LG02 , configure to receive above message**
356	356
357	357	[[image:image-20220526165612-17.png]]
...	...	@@ -362,6 +362,7 @@
362	362	[[image:image-20220526171112-21.png]]
363	363
364	364
	385	+
365	365	(% style="color:blue" %)**3. Decode the info in web**
366	366
367	367	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
...	...	@@ -384,6 +384,7 @@
384	384	)))
385	385
386	386
	408	+
387	387	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
388	388
389	389
...	...	@@ -390,6 +390,7 @@
390	390	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.
391	391
392	392
	415	+
393	393	= 9. Why do I see a "MIC Mismatch" error message from the server? =
394	394
395	395
...	...	@@ -506,6 +506,7 @@
506	506	(Any combination of 16 bit codes can be used）
507	507
508	508
	532	+
509	509	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
510	510	)))
511	511