Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,4 +1,4 @@
1		-**~ Table of Contents:**
	1	+**~ Contents:**
2	2
3	3	{{toc/}}
4	4
...	...	@@ -6,7 +6,6 @@
6	6
7	7	= 1. OTAA Join Process Debug =
8	8
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.
11	11	\\**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:**
12	12
...	...	@@ -62,7 +62,6 @@
62	62
63	63	= 2. Notice of US915/CN470/AU915 Frequency band =
64	64
65		-
66	66	(((
67	67	If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
68	68	)))
...	...	@@ -105,13 +105,10 @@
105	105
106	106	AU915 Channels
107	107
108		-
109	109	[[image:image-20220526163941-8.png]]
110	110
111	111	(((
112	112	CN470 Channels
113		-
114		-
115	115	)))
116	116
117	117	(((
...	...	@@ -122,8 +122,6 @@
122	122
123	123	(((
124	124	TTN FREQUENCY PLAN
125		-
126		-
127	127	)))
128	128
129	129	(((
...	...	@@ -133,7 +133,6 @@
133	133
134	134	= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
135	135
136		-
137	137	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:
138	138
139	139	* **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.
...	...	@@ -155,7 +155,6 @@
155	155
156	156	= 4. Transmision on ABP Mode =
157	157
158		-
159	159	(((
160	160	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.
161	161	)))
...	...	@@ -185,7 +185,6 @@
185	185
186	186	== 5.1 How it work ==
187	187
188		-
189	189	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.
190	190
191	191	(((
...	...	@@ -196,7 +196,6 @@
196	196
197	197	receive windows for Class A and Class C
198	198
199		-
200	200	Below are the requirement for the End Device to receive the packets.
201	201
202	202	* The End Device must open the receive windows: RX1 or RX2
...	...	@@ -203,13 +203,13 @@
203	203	* The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
204	204	* This downstream packet must arrive to the end node while RX1 or RX2 is open.
205	205	* This packet must match the frequency of the RX1 or RX2 window.
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.**
	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.**
207	207
	197	+
208	208	== 5.2 See Debug Info ==
209	209
210		-
211	211	(((
212		-(% style="color:blue" %)**For LoRaWAN Server**
	201	+**For LoRaWAN Server**
213	213	)))
214	214
215	215	(((
...	...	@@ -239,7 +239,7 @@
239	239
240	240
241	241	(((
242		-(% style="color:blue" %)**For LoRaWAN Gateway**
	231	+**For LoRaWAN Gateway**
243	243	)))
244	244
245	245	(((
...	...	@@ -254,7 +254,7 @@
254	254
255	255
256	256	(((
257		-(% style="color:blue" %)**For End Node**
	246	+**For End Node**
258	258	)))
259	259
260	260	(((
...	...	@@ -262,18 +262,23 @@
262	262	)))
263	263
264	264	(((
265		-(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
266		-(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
267		-(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
268		-(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
269		-
270	270
271	271	)))
272	272
273	273	(((
274		-(% style="color:blue" %)**when the device running, we can see below info:**
	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
275	275	)))
	265	+)))
276	276
	267	+(((
	268	+**when the device running, we can see below info:**
	269	+)))
	270	+
277	277	{{{ [12502]***** UpLinkCounter= 0 *****
278	278	[12503]TX on freq 868500000 Hz at DR 0
279	279	[13992]txDone
...	...	@@ -287,7 +287,7 @@
287	287	)))
288	288
289	289	(((
290		-(% style="color:blue" %)**Another message:**
	284	+**Another message:**
291	291	)))
292	292
293	293	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -311,6 +311,7 @@
311	311	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
312	312	* End Node traffic (from server UI) to shows end node activity in server.
313	313
	308	+
314	314	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
315	315
316	316	(((