Summary

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

Details

Page properties

Content

...	...	@@ -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
...	...	@@ -61,6 +61,7 @@
61	61
62	62	= 2. Notice of US915/CN470/AU915 Frequency band =
63	63
	65	+
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
	108	+
106	106	[[image:image-20220526163941-8.png]]
107	107
108	108	(((
109	109	CN470 Channels
	113	+
	114	+
110	110	)))
111	111
112	112	(((
...	...	@@ -117,6 +117,8 @@
117	117
118	118	(((
119	119	TTN FREQUENCY PLAN
	125	+
	126	+
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
	136	+
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
	158	+
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
	188	+
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
	199	+
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,12 +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.**
	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.**
196	196
	208	+
197	197	== 5.2 See Debug Info ==
198	198
	211	+
199	199	(((
200		-**For LoRaWAN Server**
	213	+(% style="color:blue" %)**For LoRaWAN Server**
201	201	)))
202	202
203	203	(((
...	...	@@ -227,7 +227,7 @@
227	227
228	228
229	229	(((
230		-**For LoRaWAN Gateway**
	243	+(% style="color:blue" %)**For LoRaWAN Gateway**
231	231	)))
232	232
233	233	(((
...	...	@@ -242,7 +242,7 @@
242	242
243	243
244	244	(((
245		-**For End Node**
	258	+(% style="color:blue" %)**For End Node**
246	246	)))
247	247
248	248	(((
...	...	@@ -264,7 +264,7 @@
264	264	)))
265	265
266	266	(((
267		-**when the device running, we can see below info:**
	280	+(% style="color:blue" %)**when the device running, we can see below info:**
268	268	)))
269	269
270	270	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -280,7 +280,7 @@
280	280	)))
281	281
282	282	(((
283		-**Another message:**
	296	+(% style="color:blue" %)**Another message:**
284	284	)))
285	285
286	286	{{{ [12502]***** UpLinkCounter= 0 *****