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 101.1
edited by Bei Jinggeng
on 2025/04/29 13:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -252,20 +252,110 @@
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"]]
255 +[[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  
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 +Reason:
277 +
265 265  When there are multiple gateways, the node cannot lock the frequency band.
266 266  
267 267  
281 +Solution:
268 268  
283 +(((
284 +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.
285 +)))
286 +
287 +(((
288 +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.
289 +)))
290 +
291 +(((
292 +
293 +)))
294 +
295 +(((
296 +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.
297 +)))
298 +
299 +[[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"]]
300 +
301 +
302 +(((
303 +When you use the TTN V3 network, the US915 frequency bands use are:
304 +)))
305 +
306 +* (((
307 +903.9 - SF7BW125 to SF10BW125
308 +)))
309 +* (((
310 +904.1 - SF7BW125 to SF10BW125
311 +)))
312 +* (((
313 +904.3 - SF7BW125 to SF10BW125
314 +)))
315 +* (((
316 +904.5 - SF7BW125 to SF10BW125
317 +)))
318 +* (((
319 +904.7 - SF7BW125 to SF10BW125
320 +)))
321 +* (((
322 +904.9 - SF7BW125 to SF10BW125
323 +)))
324 +* (((
325 +905.1 - SF7BW125 to SF10BW125
326 +)))
327 +* (((
328 +905.3 - SF7BW125 to SF10BW125
329 +)))
330 +* (((
331 +904.6 - SF8BW500
332 +)))
333 +
334 +(((
335 +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:
336 +)))
337 +
338 +(((
339 +(% style="color:blue" %)**AT+CHE=2**
340 +)))
341 +
342 +(((
343 +(% style="color:blue" %)**ATZ**
344 +)))
345 +
346 +
347 +(((
348 +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.
349 +)))
350 +
351 +(((
352 +The (% style="color:blue" %)**AU915**(%%) band is similar. Below are the AU915 Uplink Channels.
353 +
354 +[[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"]]
355 +
356 +
357 +)))
358 +
269 269  = 5. Transmision on ABP Mode =
270 270  
271 271