Summary

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

Details

Page properties

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	(((
...	...	@@ -192,11 +192,10 @@
192	192	Depends on Class A or Class C, the receive windows will be a little difference,
193	193	)))
194	194
195		-[[image:image-20220531161828-1.png]]
	185	+[[image:image-20220526164547-11.png]]
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,14 +203,14 @@
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
208	208
	198	+
209	209	== 5.2 See Debug Info ==
210	210
211		-
212	212	(((
213		-(% style="color:blue" %)**For LoRaWAN Server**
	202	+**For LoRaWAN Server**
214	214	)))
215	215
216	216	(((
...	...	@@ -240,7 +240,7 @@
240	240
241	241
242	242	(((
243		-(% style="color:blue" %)**For LoRaWAN Gateway**
	232	+**For LoRaWAN Gateway**
244	244	)))
245	245
246	246	(((
...	...	@@ -255,7 +255,7 @@
255	255
256	256
257	257	(((
258		-(% style="color:blue" %)**For End Node**
	247	+**For End Node**
259	259	)))
260	260
261	261	(((
...	...	@@ -277,7 +277,7 @@
277	277	)))
278	278
279	279	(((
280		-(% style="color:blue" %)**when the device running, we can see below info:**
	269	+**when the device running, we can see below info:**
281	281	)))
282	282
283	283	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -293,7 +293,7 @@
293	293	)))
294	294
295	295	(((
296		-(% style="color:blue" %)**Another message:**
	285	+**Another message:**
297	297	)))
298	298
299	299	{{{ [12502]***** UpLinkCounter= 0 *****
...	...	@@ -317,6 +317,8 @@
317	317	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
318	318	* End Node traffic (from server UI) to shows end node activity in server.
319	319
	309	+
	310	+
320	320	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
321	321
322	322	(((
...	...	@@ -349,7 +349,15 @@
349	349	(% class="box infomessage" %)
350	350	(((
351	351	**Change to ABP Mode: AT+NJM=0**
	343	+)))
	344	+
	345	+(% class="box infomessage" %)
	346	+(((
352	352	**Change to fix frequency: AT+CHS=904900000**
	348	+)))
	349	+
	350	+(% class="box infomessage" %)
	351	+(((
353	353	**Change to fix DR: AT+DR=0**
354	354	)))
355	355
...	...	@@ -497,15 +497,8 @@
497	497
498	498	(((
499	499	(Any combination of 16 bit codes can be used）
500		-
501		-
502		-= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
503	503	)))
504	504
505	505
506		-Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
507		-
508		-
509		-
510	510	(% class="wikigeneratedid" %)
511	511