Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,4 +1,4 @@
1		-**~ Contents:**
	1	+**~ Table of Contents:**
2	2
3	3	{{toc/}}
4	4
...	...	@@ -6,6 +6,7 @@
6	6
7	7	= 1. OTAA Join Process Debug =
8	8
	9	+
9	9	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
10	10	\\**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:**
11	11
...	...	@@ -15,8 +15,10 @@
15	15	* End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
16	16	* 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)
17	17
18		-**~1. End Device Join Screen shot, we can check:**
19	19
	20	+
	21	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	22	+
20	20	* If the device is sending join request to server?
21	21	* What frequency the device is sending?
22	22
...	...	@@ -25,7 +25,7 @@
25	25	Console Output from End device to see the transmit frequency
26	26
27	27
28		-**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:**
29	29
30	30	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
31	31	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
...	...	@@ -35,7 +35,7 @@
35	35	Console Output from Gateway to see packets between end node and server.
36	36
37	37
38		-**3. Gateway Traffic Page in LoRaWAN Server**
	41	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
39	39
40	40	* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
41	41	* 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.
...	...	@@ -46,7 +46,7 @@
46	46	The Traffic for the End node in the server, use TTN as example
47	47
48	48
49		-**4. Data Page in LoRaWAN server**
	52	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
50	50
51	51	* 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.
52	52
...	...	@@ -61,6 +61,7 @@
61	61
62	62	= 2. Notice of US915/CN470/AU915 Frequency band =
63	63
	67	+
64	64	(((
65	65	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
66	66	)))
...	...	@@ -103,10 +103,13 @@
103	103
104	104	AU915 Channels
105	105
	110	+
106	106	[[image:image-20220526163941-8.png]]
107	107
108	108	(((
109	109	CN470 Channels
	115	+
	116	+
110	110	)))
111	111
112	112	(((
...	...	@@ -117,6 +117,8 @@
117	117
118	118	(((
119	119	TTN FREQUENCY PLAN
	127	+
	128	+
120	120	)))
121	121
122	122	(((
...	...	@@ -126,6 +126,7 @@
126	126
127	127	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
128	128
	138	+
129	129	In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
130	130
131	131	* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
...	...	@@ -147,6 +147,7 @@
147	147
148	148	= 4. Transmision on ABP Mode =
149	149
	160	+
150	150	(((
151	151	In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
152	152	)))
...	...	@@ -176,6 +176,7 @@
176	176
177	177	== 5.1 How it work ==
178	178
	190	+
179	179	LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
180	180
181	181	(((
...	...	@@ -186,6 +186,7 @@
186	186
187	187	receive windows for Class A and Class C
188	188
	201	+
189	189	Below are the requirement for the End Device to receive the packets.
190	190
191	191	* The End Device must open the receive windows: RX1 or RX2
...	...	@@ -192,13 +192,13 @@
192	192	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
193	193	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
194	194	* This packet must match the frequency of the RX1 or RX2 window.
195		-* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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.**
	208	+* 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.**
196	196
197		-
198	198	== 5.2 See Debug Info ==
199	199
	212	+
200	200	(((
201		-**For LoRaWAN Server**
	214	+(% style="color:blue" %)**For LoRaWAN Server**
202	202	)))
203	203
204	204	(((
...	...	@@ -228,7 +228,7 @@
228	228
229	229
230	230	(((
231		-**For LoRaWAN Gateway**
	244	+(% style="color:blue" %)**For LoRaWAN Gateway**
232	232	)))
233	233
234	234	(((
...	...	@@ -243,7 +243,7 @@
243	243
244	244
245	245	(((
246		-**For End Node**
	259	+(% style="color:blue" %)**For End Node**
247	247	)))
248	248
249	249	(((
...	...	@@ -251,23 +251,18 @@
251	251	)))
252	252
253	253	(((
	267	+(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	268	+(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
	269	+(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	270	+(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	271	+
254	254
255	255	)))
256	256
257	257	(((
258		-(% class="box infomessage" %)
259		-(((
260		-AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
261		-AT+RX2DR=3      ~-~--> The RX2 DataRate
262		-AT+RX1DL=1000   ~-~--> Receive Delay 1
263		-AT+RX2DL=2000   ~-~--> Receive Delay 2
	276	+(% style="color:blue" %)**when the device running, we can see below info:**
264	264	)))
265		-)))
266	266
267		-(((
268		-**when the device running, we can see below info:**
269		-)))
270		-
271	271	{{{ [12502]***** UpLinkCounter= 0 *****
272	272	[12503]TX on freq 868500000 Hz at DR 0
273	273	[13992]txDone
...	...	@@ -281,7 +281,7 @@
281	281	)))
282	282
283	283	(((
284		-**Another message:**
	292	+(% style="color:blue" %)**Another message:**
285	285	)))
286	286
287	287	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -296,8 +296,9 @@
296	296	1:0012345678}}}
297	297
298	298
299		-== 5.3 If problem doesn’t solve ==
	307	+== 5.3 If problem doesn't solve ==
300	300
	309	+
301	301	(% 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:**
302	302
303	303	* End node console to show the transmit freuqency and DR.
...	...	@@ -306,8 +306,10 @@
306	306	* End Node traffic (from server UI) to shows end node activity in server.
307	307
308	308
	318	+
309	309	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310	310
	321	+
311	311	(((
312	312	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.
313	313	)))
...	...	@@ -333,19 +333,18 @@
333	333
334	334	= 7. Decrypt a LoRaWAN Packet =
335	335
336		-~1. LHT65 End device configure:
337	337
338		-(% class="box infomessage" %)
339		-(((
340		-**Change to ABP Mode: AT+NJM=0**
341		-**Change to fix frequency: AT+CHS=904900000**
342		-**Change to fix DR: AT+DR=0**
343		-)))
	348	+(% style="color:blue" %)**1. LHT65 End device configure:**
344	344
	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	+
345	345	[[image:image-20220526165525-16.png]]
346	346
347	347
348		-2. In LG02 , configure to receive above message
	358	+(% style="color:blue" %)**2. In LG02 , configure to receive above message**
349	349
350	350	[[image:image-20220526165612-17.png]]
351	351
...	...	@@ -355,7 +355,7 @@
355	355	[[image:image-20220526171112-21.png]]
356	356
357	357
358		-3. Decode the info in web
	368	+(% style="color:blue" %)**3. Decode the info in web**
359	359
360	360	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
361	361
...	...	@@ -367,6 +367,7 @@
367	367
368	368	AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
369	369
	380	+
370	370	[[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]]
371	371
372	372	[[image:image-20220526171029-20.png]]
...	...	@@ -378,13 +378,15 @@
378	378
379	379	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
380	380
	392	+
381	381	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.
382	382
383	383
384	384	= 9. Why do I see a "MIC Mismatch" error message from the server? =
385	385
	398	+
386	386	(((
387		-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.
388	388	)))
389	389
390	390	(((
...	...	@@ -406,11 +406,14 @@
406	406	* (((
407	407	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
408	408
	422	+
	423	+
409	409
410	410	)))
411	411
412	412	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
413	413
	429	+
414	414	* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
415	415
416	416	(((
...	...	@@ -427,11 +427,14 @@
427	427	* (((
428	428	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]]
429	429
	446	+
	447	+
430	430
431	431	)))
432	432
433	433	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
434	434
	453	+
435	435	(((
436	436	It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
437	437	)))
...	...	@@ -462,6 +462,8 @@
462	462
463	463	(((
464	464	You can rewrites the keys by running commands in AT Console
	484	+
	485	+
465	465	)))
466	466
467	467	(((