Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 102.1
edited by Xiaoling
on 2025/05/05 08:51
Change comment: There is no comment for this version
To version 100.1
edited by Bei Jinggeng
on 2025/04/29 13:36
Change comment: Uploaded new attachment "image-20250429133640-7.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -63,6 +63,7 @@
63 63  
64 64  The data for the end device set in server
65 65  
66 +
66 66  [[image:image-20240129142631-4.png||height="637" width="1256"]]
67 67  
68 68  Check if OTAA Keys match the keys in device.
... ... @@ -167,15 +167,15 @@
167 167  == **1. Signal problem** ==
168 168  
169 169  
170 -(% style="color:blue" %)**1)**(%%)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
171 +1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
171 171  
172 -**Reason:**
173 +Reason:
173 173  
174 174  When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
175 175  At this time, the server is at risk of losing uplink.
176 176  
177 177  
178 -**Solution:**
179 +Solution:
179 179  
180 180  Users can manually fix the DR value.
181 181  
... ... @@ -209,14 +209,14 @@
209 209  (% style="display:none" %) (%%)
210 210  
211 211  
212 -(% style="color:blue" %)**2)**(%%)  (% style="color:blue" %)**Node antenna problem**
213 +2)  (% style="color:blue" %)**Node antenna problem**
213 213  
214 -**Reason:**
215 +Reason:
215 215  
216 216  Node antenna is loose
217 217  
218 218  
219 -**Solution:**
220 +Solution:
220 220  
221 221  Please check whether the antenna interface and module interface are detached
222 222  
... ... @@ -224,15 +224,15 @@
224 224  
225 225  
226 226  
227 -(% style="color:blue" %)**3) **(%%) (% style="color:blue" %)**Gateway antenna problem**
228 +3) (% style="color:blue" %)**Gateway antenna problem**
228 228  
229 -**Reason:**
230 +Reason:
230 230  Gateway uses antenna with wrong frequency band
231 231  
232 232  For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
233 233  
234 234  
235 -**Solution:**
236 +Solution:
236 236  
237 237  Please check whether the silk screen on the antenna conflicts with the frequency you set.
238 238  
... ... @@ -239,124 +239,32 @@
239 239  [[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
240 240  
241 241  
242 -(% style="color:blue" %)**4) **(%%) (% style="color:blue" %)**Gateway module problem**
243 +4) (% style="color:blue" %)**Gateway module problem**
243 243  
244 -**Reason:**
245 +Reason:
245 245  
246 246  Gateway uses module with wrong frequency band
247 247  For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
248 248  
249 249  
250 -**Solution:**
251 +Solution:
251 251  
252 252  Please check whether the silkscreen of the module conflicts with the frequency you set.
253 253  
254 -[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429133640-7.png||height="284" width="378"]]
255 +[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
255 255  
256 256  
257 257  == **2. Frequency point problem** ==
258 258  
259 -
260 -**Reason:**
261 -
262 -There are multiple frequency configurations in AS923/US915/AU915/CN470.
263 -
264 264  The frequency point of the gateway or server is wrong or missing.
265 265  
266 266  
267 -**Solution:**
268 -
269 -Users need to check whether the server or gateway configuration is missing or has an incorrect frequency.
270 -
271 -The frequency range used in the dragino node is as follows
272 -
273 -
274 274  == **3. Frequency band problem** ==
275 275  
276 -
277 -**Reason:**
278 -
279 279  When there are multiple gateways, the node cannot lock the frequency band.
280 280  
281 281  
282 -**Solution:**
283 283  
284 -(((
285 -By default, the frequency bands US915, AU915, CN470 work in 72 frequencies. Many gateways are 8 channel gateways, and in this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies.
286 -)))
287 -
288 -(((
289 -You can configure the end node to work in 8 channel mode by using the AT+CHE command. The 500kHz channels are always included for OTAA.
290 -)))
291 -
292 -(((
293 -
294 -)))
295 -
296 -(((
297 -For example, in (% style="color:blue" %)**US915**(%%) band, the frequency table is as below. By default, the end node will use all channels (0~~71) for OTAA Join process. After the OTAA Join, the end node will use these all channels (0~~71) to send uplink packets.
298 -)))
299 -
300 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220627160940-13.png?rev=1.1||alt="image-20220627160940-13.png"]]
301 -
302 -
303 -(((
304 -When you use the TTN V3 network, the US915 frequency bands use are:
305 -)))
306 -
307 -* (((
308 -903.9 - SF7BW125 to SF10BW125
309 -)))
310 -* (((
311 -904.1 - SF7BW125 to SF10BW125
312 -)))
313 -* (((
314 -904.3 - SF7BW125 to SF10BW125
315 -)))
316 -* (((
317 -904.5 - SF7BW125 to SF10BW125
318 -)))
319 -* (((
320 -904.7 - SF7BW125 to SF10BW125
321 -)))
322 -* (((
323 -904.9 - SF7BW125 to SF10BW125
324 -)))
325 -* (((
326 -905.1 - SF7BW125 to SF10BW125
327 -)))
328 -* (((
329 -905.3 - SF7BW125 to SF10BW125
330 -)))
331 -* (((
332 -904.6 - SF8BW500
333 -)))
334 -
335 -(((
336 -Because the end node is now hopping in 72 frequency, it makes it difficult for the devices to Join the TTN V3 network and uplink data. To solve this issue, you can access the device via the AT commands and run:
337 -)))
338 -
339 -(((
340 -(% style="color:blue" %)**AT+CHE=2**
341 -)))
342 -
343 -(((
344 -(% style="color:blue" %)**ATZ**
345 -)))
346 -
347 -
348 -(((
349 -to set the end node to work in 8 channel mode. The device will work in Channel 8-15 & 64-71 for OTAA, and channel 8-15 for Uplink.
350 -)))
351 -
352 -(((
353 -The (% style="color:blue" %)**AU915**(%%) band is similar. Below are the AU915 Uplink Channels.
354 -
355 -[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LSN50%20%26%20LSN50-V2%20-%20LoRaWAN%20Sensor%20Node%20User%20Manual/WebHome/image-20220627161124-14.png?rev=1.1||alt="image-20220627161124-14.png"]]
356 -
357 -
358 -)))
359 -
360 360  = 5. Transmision on ABP Mode =
361 361  
362 362  
... ... @@ -571,6 +571,7 @@
571 571  [[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
572 572  
573 573  
483 +
574 574  **Configuration: **
575 575  
576 576  [[image:image-20240129164219-4.png||height="612" width="440"]]
... ... @@ -587,6 +587,7 @@
587 587  [[image:image-20240129170137-6.png||height="459" width="1116"]]
588 588  
589 589  
500 +
590 590  (% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
591 591  
592 592  LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
... ... @@ -610,11 +610,20 @@
610 610  
611 611  **Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
612 612  
524 +
525 +
526 +
613 613  [[image:image-20240129192908-24.png||height="477" width="907"]]
614 614  
529 +
615 615  [[image:image-20240129192954-25.png||height="485" width="916"]]
616 616  
617 617  
533 +
534 +
535 +
536 +
537 +
618 618  = 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
619 619  
620 620