Summary

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

Details

Page properties

Content

...	...	@@ -4,7 +4,7 @@
4	4
5	5
6	6
7		-= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
	7	+= z =
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 Traffic Page in LoRaWAN Server**
	47	+(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
48	48
49		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	49	+* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
50	50
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.
	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.
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-20220526163704-4.png]]
	65	+[[image:image-20240123150720-1.png||height="459" width="1182"]]
66	66
67	67	The data for the end device set in server
68	68
69	69
70		-[[image:image-20220526163732-5.png]]
	70	+[[image:image-20240123150943-2.png||height="556" width="1179"]]
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-20220526164052-9.png]]
	134	+[[image:image-20240123151225-3.png||height="434" width="902"]]
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/unperiocially uplink data? Even the signal strength is good =
	148	+= 3. Why I see data lost/ is not periodically uplink？ 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,9 +179,11 @@
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"]]
182	182	)))
183	183
184		-[[image:image-20220526164508-10.png]]
	186	+[[image:image-20240123161853-6.png||height="599" width="771"]]
185	185
186	186	Disable Frame Counter Check in ABP Mode
187	187
...	...	@@ -194,7 +194,7 @@
194	194	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.
195	195
196	196	(((
197		-Depends on Class A or Class C, the receive windows will be a little difference,
	199	+Depends on Class A or Class C, the receive windows will be a little difference.
198	198	)))
199	199
200	200	[[image:image-20220531161828-1.png]]
...	...	@@ -214,6 +214,9 @@
214	214
215	215	* 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.**
216	216
	219	+(% class="wikigeneratedid" %)
	220	+== ==
	221	+
217	217	== 5.2 See Debug Info ==
218	218
219	219
...	...	@@ -226,10 +226,10 @@
226	226	)))
227	227
228	228	(((
229		-Configure a downstream to the end device
	234	+Configure a downlink to the end device
230	230	)))
231	231
232		-[[image:image-20220526164623-12.png]]
	237	+[[image:image-20240123163307-7.png||height="330" width="1125"]]
233	233
234	234	(((
235	235	Set a downstream in TTN and see it is sent