Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.2 >
edited by Xiaoling
on 2022/05/11 14:30
To version < 4.3 >
edited by Xiaoling
on 2022/05/11 14:35
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -106,13 +106,17 @@
106 106  
107 107  CN470 Channels
108 108  
109 +(((
109 109  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.
111 +)))
110 110  
111 111  [[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
112 112  
113 113  TTN FREQUENCY PLAN
114 114  
117 +(((
115 115  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
119 +)))
116 116  
117 117  
118 118  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
... ... @@ -123,18 +123,40 @@
123 123  * **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
124 124  * **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
125 125  
130 +(((
126 126  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
132 +)))
127 127  
134 +(((
135 +
136 +)))
137 +
138 +(((
128 128  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
140 +)))
129 129  
130 130  
131 131  = 4. Transmision on ABP Mode =
132 132  
145 +(((
133 133  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
147 +)))
134 134  
149 +(((
150 +
151 +)))
152 +
153 +(((
135 135  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
155 +)))
136 136  
157 +(((
158 +
159 +)))
160 +
161 +(((
137 137  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
163 +)))
138 138  
139 139  [[~[~[image:https://wiki.dragino.com/images/thumb/1/19/ABP_Issue-1.jpg/600px-ABP_Issue-1.jpg~|~|height="340" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:ABP_Issue-1.jpg]]
140 140  
... ... @@ -147,7 +147,9 @@
147 147  
148 148  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.
149 149  
176 +(((
150 150  Depends on Class A or Class C, the receive windows will be a little difference,
178 +)))
151 151  
152 152  [[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
153 153  
... ... @@ -174,7 +174,9 @@
174 174  Set a downstream in TTN and see it is sent
175 175  
176 176  
205 +(((
177 177  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
207 +)))
178 178  
179 179  [[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
180 180  
... ... @@ -183,7 +183,9 @@
183 183  
184 184  **For LoRaWAN Gateway**
185 185  
216 +(((
186 186  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
218 +)))
187 187  
188 188  [[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
189 189  
... ... @@ -196,35 +196,41 @@
196 196  
197 197  (% class="box infomessage" %)
198 198  (((
199 -AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
231 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
200 200  )))
201 201  
202 202  (% class="box infomessage" %)
203 203  (((
204 -AT+RX2DR=3 ~-~--> The RX2 DataRate
236 + AT+RX2DR=3 ~-~--> The RX2 DataRate
205 205  )))
206 206  
207 207  (% class="box infomessage" %)
208 208  (((
209 -AT+RX1DL=1000 ~-~--> Receive Delay 1
241 + AT+RX1DL=1000 ~-~--> Receive Delay 1
210 210  )))
211 211  
212 212  (% class="box infomessage" %)
213 213  (((
214 -AT+RX2DL=2000 ~-~--> Receive Delay 2
246 + AT+RX2DL=2000 ~-~--> Receive Delay 2
215 215  )))
216 216  
217 217  when the device running, we can see below info:
218 218  
219 -{{{[12502]***** UpLinkCounter= 0 *****
251 +(% class="box" %)
252 +(((
253 +[12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
220 220  [12503]TX on freq 868500000 Hz at DR 0
221 221  [13992]txDone
222 -[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
223 -[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
224 -[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
225 -[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
226 -}}}
256 +[15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
257 +[15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
258 +[15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
259 +[16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
260 +)))
227 227  
262 +(((
263 +
264 +)))
265 +
228 228  {{{Another message:
229 229  [12502]***** UpLinkCounter= 0 *****
230 230  [12503]TX on freq 868100000 Hz at DR 0

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0