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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Bei
1 +XWiki.Xiaoling
Content
... ... @@ -63,7 +63,6 @@
63 63  
64 64  The data for the end device set in server
65 65  
66 -
67 67  [[image:image-20240129142631-4.png||height="637" width="1256"]]
68 68  
69 69  Check if OTAA Keys match the keys in device.
... ... @@ -168,15 +168,15 @@
168 168  == **1. Signal problem** ==
169 169  
170 170  
171 -1)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
170 +(% style="color:blue" %)**1)**(%%)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
172 172  
173 -Reason:
172 +**Reason:**
174 174  
175 175  When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
176 176  At this time, the server is at risk of losing uplink.
177 177  
178 178  
179 -Solution:
178 +**Solution:**
180 180  
181 181  Users can manually fix the DR value.
182 182  
... ... @@ -210,14 +210,14 @@
210 210  (% style="display:none" %) (%%)
211 211  
212 212  
213 -2)  (% style="color:blue" %)**Node antenna problem**
212 +(% style="color:blue" %)**2)**(%%)  (% style="color:blue" %)**Node antenna problem**
214 214  
215 -Reason:
214 +**Reason:**
216 216  
217 217  Node antenna is loose
218 218  
219 219  
220 -Solution:
219 +**Solution:**
221 221  
222 222  Please check whether the antenna interface and module interface are detached
223 223  
... ... @@ -225,15 +225,15 @@
225 225  
226 226  
227 227  
228 -3) (% style="color:blue" %)**Gateway antenna problem**
227 +(% style="color:blue" %)**3) **(%%) (% style="color:blue" %)**Gateway antenna problem**
229 229  
230 -Reason:
229 +**Reason:**
231 231  Gateway uses antenna with wrong frequency band
232 232  
233 233  For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
234 234  
235 235  
236 -Solution:
235 +**Solution:**
237 237  
238 238  Please check whether the silk screen on the antenna conflicts with the frequency you set.
239 239  
... ... @@ -240,32 +240,124 @@
240 240  [[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
241 241  
242 242  
243 -4) (% style="color:blue" %)**Gateway module problem**
242 +(% style="color:blue" %)**4) **(%%) (% style="color:blue" %)**Gateway module problem**
244 244  
245 -Reason:
244 +**Reason:**
246 246  
247 247  Gateway uses module with wrong frequency band
248 248  For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
249 249  
250 250  
251 -Solution:
250 +**Solution:**
252 252  
253 253  Please check whether the silkscreen of the module conflicts with the frequency you set.
254 254  
255 -[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429120030-6.png||height="284" width="378"]]
254 +[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429133640-7.png||height="284" width="378"]]
256 256  
257 257  
258 258  == **2. Frequency point problem** ==
259 259  
259 +
260 +**Reason:**
261 +
262 +There are multiple frequency configurations in AS923/US915/AU915/CN470.
263 +
260 260  The frequency point of the gateway or server is wrong or missing.
261 261  
262 262  
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 +
263 263  == **3. Frequency band problem** ==
264 264  
276 +
277 +**Reason:**
278 +
265 265  When there are multiple gateways, the node cannot lock the frequency band.
266 266  
267 267  
282 +**Solution:**
268 268  
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 +
269 269  = 5. Transmision on ABP Mode =
270 270  
271 271  
... ... @@ -480,7 +480,6 @@
480 480  [[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
481 481  
482 482  
483 -
484 484  **Configuration: **
485 485  
486 486  [[image:image-20240129164219-4.png||height="612" width="440"]]
... ... @@ -497,7 +497,6 @@
497 497  [[image:image-20240129170137-6.png||height="459" width="1116"]]
498 498  
499 499  
500 -
501 501  (% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
502 502  
503 503  LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
... ... @@ -521,20 +521,11 @@
521 521  
522 522  **Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
523 523  
524 -
525 -
526 -
527 527  [[image:image-20240129192908-24.png||height="477" width="907"]]
528 528  
529 -
530 530  [[image:image-20240129192954-25.png||height="485" width="916"]]
531 531  
532 532  
533 -
534 -
535 -
536 -
537 -
538 538  = 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
539 539  
540 540