Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 1 added, 0 removed)
  • image-20221215223215-1.png

Details

Page properties

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,9 @@
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	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	21	+
20	20	* If the device is sending join request to server?
21	21	* What frequency the device is sending?
22	22
...	...	@@ -25,8 +25,9 @@
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:**
29	29
	31	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	32	+
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?
32	32
...	...	@@ -35,8 +35,9 @@
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**
39	39
	42	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	43	+
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.
42	42	* If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
...	...	@@ -46,8 +46,9 @@
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**
50	50
	54	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	55	+
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
53	53	[[image:image-20220526163704-4.png]]
...	...	@@ -54,13 +54,16 @@
54	54
55	55	The data for the end device set in server
56	56
	62	+
57	57	[[image:image-20220526163732-5.png]]
58	58
59	59	Check if OTAA Keys match the keys in device
60	60
61	61
	68	+
62	62	= 2. Notice of US915/CN470/AU915 Frequency band =
63	63
	71	+
64	64	(((
65	65	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
66	66	)))
...	...	@@ -99,14 +99,18 @@
99	99
100	100	US915 Channels
101	101
	110	+
102	102	[[image:image-20220526163926-7.png]]
103	103
104	104	AU915 Channels
105	105
	115	+
106	106	[[image:image-20220526163941-8.png]]
107	107
108	108	(((
109	109	CN470 Channels
	120	+
	121	+
110	110	)))
111	111
112	112	(((
...	...	@@ -117,6 +117,8 @@
117	117
118	118	(((
119	119	TTN FREQUENCY PLAN
	132	+
	133	+
120	120	)))
121	121
122	122	(((
...	...	@@ -124,8 +124,10 @@
124	124	)))
125	125
126	126
	141	+
127	127	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
128	128
	144	+
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.
...	...	@@ -145,8 +145,10 @@
145	145	)))
146	146
147	147
	164	+
148	148	= 4. Transmision on ABP Mode =
149	149
	167	+
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	)))
...	...	@@ -172,10 +172,12 @@
172	172	Disable Frame Counter Check in ABP Mode
173	173
174	174
	193	+
175	175	= 5. Downstream Debug =
176	176
177	177	== 5.1 How it work ==
178	178
	198	+
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
	209	+
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,14 @@
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.**
	216	+* 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	197
198	198	== 5.2 See Debug Info ==
199	199
	221	+
200	200	(((
201		-**For LoRaWAN Server**
	223	+(% style="color:blue" %)**For LoRaWAN Server**
202	202	)))
203	203
204	204	(((
...	...	@@ -227,8 +227,9 @@
227	227	)))
228	228
229	229
	252	+
230	230	(((
231		-**For LoRaWAN Gateway**
	254	+(% style="color:blue" %)**For LoRaWAN Gateway**
232	232	)))
233	233
234	234	(((
...	...	@@ -242,8 +242,9 @@
242	242	)))
243	243
244	244
	268	+
245	245	(((
246		-**For End Node**
	270	+(% style="color:blue" %)**For End Node**
247	247	)))
248	248
249	249	(((
...	...	@@ -251,23 +251,19 @@
251	251	)))
252	252
253	253	(((
	278	+(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
	279	+(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
	280	+(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
	281	+(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
	282	+
	283	+
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
	288	+(% 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
...	...	@@ -278,10 +278,12 @@
278	278
279	279	(((
280	280
	301	+
	302	+
281	281	)))
282	282
283	283	(((
284		-**Another message:**
	306	+(% style="color:blue" %)**Another message:**
285	285	)))
286	286
287	287	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -296,8 +296,10 @@
296	296	1:0012345678}}}
297	297
298	298
299		-== 5.3 If problem doesn’t solve ==
300	300
	322	+== 5.3 If problem doesn't solve ==
	323	+
	324	+
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.
...	...	@@ -308,6 +308,7 @@
308	308
309	309	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310	310
	335	+
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	)))
...	...	@@ -331,22 +331,23 @@
331	331	)))
332	332
333	333
	359	+
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		-)))
	363	+(% style="color:blue" %)**1. LHT65 End device configure:**
344	344
	365	+**Change to ABP Mode:  AT+NJM=0**
	366	+**Change to fix frequency:  AT+CHS=904900000**
	367	+**Change to fix DR:  AT+DR=0**
	368	+
	369	+
345	345	[[image:image-20220526165525-16.png]]
346	346
347	347
348		-2. In LG02 , configure to receive above message
349	349
	374	+(% style="color:blue" %)**2. In LG02 , configure to receive above message**
	375	+
350	350	[[image:image-20220526165612-17.png]]
351	351
352	352
...	...	@@ -355,8 +355,9 @@
355	355	[[image:image-20220526171112-21.png]]
356	356
357	357
358		-3. Decode the info in web
359	359
	385	+(% style="color:blue" %)**3. Decode the info in web**
	386	+
360	360	[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
361	361
362	362	Need these three fields:
...	...	@@ -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
	397	+
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]]
...	...	@@ -376,15 +376,19 @@
376	376	)))
377	377
378	378
	407	+
379	379	= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
380	380
	410	+
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
	414	+
384	384	= 9. Why do I see a "MIC Mismatch" error message from the server? =
385	385
	417	+
386	386	(((
387		-1)If the user receives a "MIC Mismatch" message after registering the node on the server.
	419	+1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
388	388	)))
389	389
390	390	(((
...	...	@@ -406,32 +406,34 @@
406	406	* (((
407	407	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
408	408
	441	+
	442	+
409	409
410	410	)))
411	411
412	412	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
413	413
414		-* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
415	415
416		-(((
417		-When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
418		-)))
	449	+**Why this happen:**
419	419
420		-(((
421		-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.
422		-)))
	451	+For US915, AU915 or AS923 frequencies.It is possible because: .
423	423
424		-* (((
425		-Solution: Use the decoder to filter out this 00 packet.
426		-)))
427		-* (((
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]]
	453	+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.
429	429
430		-
431		-)))
	455	+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.
432	432
	457	+
	458	+**How to solve:**
	459	+
	460	+Solution: Use the decoder to filter out this 0x00 packet.
	461	+
	462	+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]]
	463	+
	464	+
	465	+
433	433	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
434	434
	468	+
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
	499	+
	500	+
465	465	)))
466	466
467	467	(((
...	...	@@ -488,6 +488,7 @@
488	488	(Any combination of 16 bit codes can be used）
489	489
490	490
	527	+
491	491	= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
492	492	)))
493	493
...	...	@@ -495,6 +495,30 @@
495	495	Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
496	496
497	497
	535	+= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
498	498
	537	+
	538	+In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
	539	+
	540	+
	541	+In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
	542	+
	543	+We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
	544	+
	545	+* (((
	546	+Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
	547	+)))
	548	+* (((
	549	+Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
	550	+)))
	551	+
	552	+This change will make the activation time a littler longer but make sure the device can be used in any subband.
	553	+
	554	+
	555	+Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
	556	+
	557	+
	558	+[[image:image-20221215223215-1.png||height="584" width="1280"]]
	559	+
499	499	(% class="wikigeneratedid" %)
500	500

image-20221215223215-1.png

Author

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

Size

...	...	@@ -1,0 +1,1 @@
	1	+183.6 KB

Content