Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 2.1
edited by Xiaoling
on 2022/05/11 14:19
Change comment: There is no comment for this version
To version 4.2
edited by Xiaoling
on 2022/05/11 14:30
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,4 +1,4 @@
1 -
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
... ... @@ -60,17 +60,39 @@
60 60  
61 61  = 2. Notice of US915/CN470/AU915 Frequency band =
62 62  
63 +(((
63 63  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
65 +)))
64 64  
65 -* What **sub-band** the server support ?
66 -* What is the **sub-band** the gateway support ?
67 -* What is the **sub-band** the end node is using ?
67 +* (((
68 +What **sub-band** the server support ?
69 +)))
70 +* (((
71 +What is the **sub-band** the gateway support ?
72 +)))
73 +* (((
74 +What is the **sub-band** the end node is using ?
75 +)))
68 68  
77 +(((
69 69  All of above should match so End Node can properly Join the server and don't have packet lost.
79 +)))
70 70  
81 +(((
82 +
83 +)))
84 +
85 +(((
71 71  In LoRaWAN protocol, the frequency bands US915, AU915, CN470 each includes at least 72 frequencies. Many gateways support only 8 or 16 frequencies, and server might support 8 frequency only. In this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies, because the end node will send data in many frequency that the gateway or server doesn,t support.
87 +)))
72 72  
89 +(((
90 +
91 +)))
92 +
93 +(((
73 73  Here are the freuqency tables for these bands as reference:
95 +)))
74 74  
75 75  [[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
76 76  
... ... @@ -172,17 +172,26 @@
172 172  
173 173  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
174 174  
197 +(% class="box infomessage" %)
175 175  (((
176 -{{info}}
177 -{{{AT+RX2FQ=869525000 ---> The RX2 Window frequency
178 -AT+RX2DR=3 ---> The RX2 DataRate
179 -AT+RX1DL=1000 ---> Receive Delay 1
180 -AT+RX2DL=2000 ---> Receive Delay 2}}}
181 -{{/info}}
199 +AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
200 +)))
182 182  
183 -
202 +(% class="box infomessage" %)
203 +(((
204 +AT+RX2DR=3 ~-~--> The RX2 DataRate
184 184  )))
185 185  
207 +(% class="box infomessage" %)
208 +(((
209 +AT+RX1DL=1000 ~-~--> Receive Delay 1
210 +)))
211 +
212 +(% class="box infomessage" %)
213 +(((
214 +AT+RX2DL=2000 ~-~--> Receive Delay 2
215 +)))
216 +
186 186  when the device running, we can see below info:
187 187  
188 188  {{{[12502]***** UpLinkCounter= 0 *****
... ... @@ -216,7 +216,6 @@
216 216  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
217 217  * End Node traffic (from server UI) to shows end node activity in server.
218 218  
219 -
220 220  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
221 221  
222 222  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
... ... @@ -310,4 +310,5 @@
310 310  * Solution: Use the decoder to filter out this 00 packet.
311 311  * Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
312 312  
313 -== ==
343 +(% class="wikigeneratedid" id="H" %)
344 +