Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 7 removed)
  • image-20240123150720-1.png
  • image-20240123150943-2.png
  • image-20240123151225-3.png
  • image-20240123161737-4.png
  • image-20240123161806-5.png
  • image-20240123161853-6.png
  • image-20240123163307-7.png

Details

Page properties

Author

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

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5
6	6
7		-= z =
	7	+= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
8	8
9	9
10	10	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.
...	...	@@ -44,17 +44,17 @@
44	44
45	45
46	46
47		-(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
	47	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48	48
49		-* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
	49	+* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50	50
51		-* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
	51	+* 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.
52	52
53	53	* 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.
54	54
55	55	[[image:image-20220526163633-3.png]]
56	56
57		-The Traffic for the End node in the server, use TTN as example.
	57	+The Traffic for the End node in the server, use TTN as example
58	58
59	59
60	60
...	...	@@ -62,14 +62,14 @@
62	62
63	63	* 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.
64	64
65		-[[image:image-20240123150720-1.png||height="459" width="1182"]]
	65	+[[image:image-20220526163704-4.png]]
66	66
67	67	The data for the end device set in server
68	68
69	69
70		-[[image:image-20240123150943-2.png||height="556" width="1179"]]
	70	+[[image:image-20220526163732-5.png]]
71	71
72		-Check if OTAA Keys match the keys in device.
	72	+Check if OTAA Keys match the keys in device
73	73
74	74
75	75	= 2. Notice of US915/CN470/AU915 Frequency band =
...	...	@@ -131,7 +131,7 @@
131	131	If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
132	132	)))
133	133
134		-[[image:image-20240123151225-3.png||height="434" width="902"]]
	134	+[[image:image-20220526164052-9.png]]
135	135
136	136	(((
137	137	TTN FREQUENCY PLAN
...	...	@@ -145,7 +145,7 @@
145	145
146	146	(% style="display:none" %) (%%)
147	147
148		-= 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
	148	+= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
149	149
150	150
151	151	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:
...	...	@@ -179,11 +179,9 @@
179	179
180	180	(((
181	181	To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
182		-
183		-[[image:image-20240123161737-4.png||height="395" width="763"]]
184	184	)))
185	185
186		-[[image:image-20240123161853-6.png||height="599" width="771"]]
	184	+[[image:image-20220526164508-10.png]]
187	187
188	188	Disable Frame Counter Check in ABP Mode
189	189
...	...	@@ -196,7 +196,7 @@
196	196	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.
197	197
198	198	(((
199		-Depends on Class A or Class C, the receive windows will be a little difference.
	197	+Depends on Class A or Class C, the receive windows will be a little difference,
200	200	)))
201	201
202	202	[[image:image-20220531161828-1.png]]
...	...	@@ -216,9 +216,8 @@
216	216
217	217	* 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.**
218	218
219		-(% class="wikigeneratedid" %)
220		-== ==
221	221
	218	+
222	222	== 5.2 See Debug Info ==
223	223
224	224
...	...	@@ -231,10 +231,10 @@
231	231	)))
232	232
233	233	(((
234		-Configure a downlink to the end device
	231	+Configure a downstream to the end device
235	235	)))
236	236
237		-[[image:image-20240123163307-7.png||height="330" width="1125"]]
	234	+[[image:image-20220526164623-12.png]]
238	238
239	239	(((
240	240	Set a downstream in TTN and see it is sent
...	...	@@ -334,6 +334,8 @@
334	334
335	335	* End Node traffic (from server UI) to shows end node activity in server.
336	336
	334	+
	335	+
337	337	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
338	338
339	339
...	...	@@ -456,34 +456,19 @@
456	456	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
457	457
458	458
459		-(% style="color:blue" %)**Why sensor sends 0x00?**
	458	+(% style="color:blue" %)**Why this happen:**
460	460
461		-For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
	460	+For US915, AU915 or AS923 frequencies.It is possible because: .
462	462
463		-**Possible Case 1**:
	462	+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.
464	464
465		-Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
	464	+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.
466	466
467	467
468		-**Possible Case 2:**
469		-
470		-For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
471		-
472		-
473	473	(% style="color:blue" %)**How to solve:**
474	474
475		-Solution:
	469	+Solution: Use the decoder to filter out this 0x00 packet.
476	476
477		-~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
478		-
479		-2. Data rate changed from DR3 to DR5, increasing upload byte length
480		-AT+ADR=0
481		-AT+DR=3
482		-
483		-Downlink：
484		-
485		-[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
486		-
487	487	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]]
488	488
489	489

image-20240123150720-1.png

Author

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

Size

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

Content

image-20240123150943-2.png

Author

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

Size

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

Content

image-20240123151225-3.png

Author

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

Size

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

Content

image-20240123161737-4.png

Author

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

Size

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

Content

image-20240123161806-5.png

Author

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

Size

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

Content

image-20240123161853-6.png

Author

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

Size

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

Content

image-20240123163307-7.png

Author

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

Size

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

Content