Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 41.1
edited by Edwin Chen
on 2023/04/23 14:14
Change comment: There is no comment for this version
To version 4.5
edited by Xiaoling
on 2022/05/11 14:46
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,80 +1,65 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 += 1. OTAA Join Process Debug =
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
8 -
9 -
10 10  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
11 11  \\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
12 12  
13 13  * End node console to show the Join freuqency and DR. (If possible)
14 -
15 15  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 -
17 17  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 -
19 19  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 -
21 21  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
22 22  
23 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
17 +**~1. End Device Join Screen shot, we can check:**
24 24  
25 25  * If the device is sending join request to server?
26 -
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
30 30  
31 31  Console Output from End device to see the transmit frequency
32 32  
33 33  
27 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
34 34  
35 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 -
37 37  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
38 -
39 39  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
40 40  
41 -[[image:image-20220526163608-2.png]]
32 +[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
42 42  
43 43  Console Output from Gateway to see packets between end node and server.
44 44  
45 45  
37 +**3. Gateway Traffic Page in LoRaWAN Server**
46 46  
47 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48 -
49 49  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50 -
51 51  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
52 -
53 53  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
54 54  
55 -[[image:image-20220526163633-3.png]]
43 +[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
56 56  
57 57  The Traffic for the End node in the server, use TTN as example
58 58  
59 59  
48 +**4. Data Page in LoRaWAN server**
60 60  
61 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 -
63 63  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
64 64  
65 -[[image:image-20220526163704-4.png]]
52 +[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
66 66  
67 67  The data for the end device set in server
68 68  
56 +[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
69 69  
70 -[[image:image-20220526163732-5.png]]
71 -
72 72  Check if OTAA Keys match the keys in device
73 73  
74 74  
75 75  = 2. Notice of US915/CN470/AU915 Frequency band =
76 76  
77 -
78 78  (((
79 79  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
80 80  )))
... ... @@ -109,22 +109,18 @@
109 109  Here are the freuqency tables for these bands as reference:
110 110  )))
111 111  
112 -[[image:image-20220526163801-6.png]]
97 +[[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
113 113  
114 114  US915 Channels
115 115  
101 +[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
116 116  
117 -[[image:image-20220526163926-7.png]]
118 -
119 119  AU915 Channels
120 120  
105 +[[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png||height="205" width="600"]]
121 121  
122 -[[image:image-20220526163941-8.png]]
123 -
124 124  (((
125 125  CN470 Channels
126 -
127 -
128 128  )))
129 129  
130 130  (((
... ... @@ -131,12 +131,10 @@
131 131  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.
132 132  )))
133 133  
134 -[[image:image-20220526164052-9.png]]
115 +[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
135 135  
136 136  (((
137 137  TTN FREQUENCY PLAN
138 -
139 -(% style="display:none" %) (%%)
140 140  )))
141 141  
142 142  (((
... ... @@ -143,23 +143,22 @@
143 143  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. )
144 144  )))
145 145  
146 -(% style="display:none" %) (%%)
147 147  
148 148  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
149 149  
150 -
151 151  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
152 152  
153 -* (% style="color:blue" %)**End node** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
130 +* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
131 +* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
132 +* **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.
154 154  
155 -* (% style="color:blue" %)**Gateway** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
156 -
157 -* (% style="color:blue" %)**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.
158 -
159 159  (((
160 160  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.
161 161  )))
162 162  
138 +(((
139 +
140 +)))
163 163  
164 164  (((
165 165  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.
... ... @@ -168,20 +168,27 @@
168 168  
169 169  = 4. Transmision on ABP Mode =
170 170  
171 -
172 172  (((
173 173  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.
174 174  )))
175 175  
176 176  (((
154 +
155 +)))
156 +
157 +(((
177 177  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.
178 178  )))
179 179  
180 180  (((
162 +
163 +)))
164 +
165 +(((
181 181  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
182 182  )))
183 183  
184 -[[image:image-20220526164508-10.png]]
169 +[[~[~[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]]
185 185  
186 186  Disable Frame Counter Check in ABP Mode
187 187  
... ... @@ -190,7 +190,6 @@
190 190  
191 191  == 5.1 How it work ==
192 192  
193 -
194 194  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.
195 195  
196 196  (((
... ... @@ -197,43 +197,29 @@
197 197  Depends on Class A or Class C, the receive windows will be a little difference,
198 198  )))
199 199  
200 -[[image:image-20220531161828-1.png]]
184 +[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
201 201  
202 202  receive windows for Class A and Class C
203 203  
204 -
205 205  Below are the requirement for the End Device to receive the packets.
206 206  
207 207  * The End Device must open the receive windows: RX1 or RX2
208 -
209 209  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
210 -
211 211  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 -
213 213  * This packet must match the frequency of the RX1 or RX2 window.
194 +* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
214 214  
215 -* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
216 -
217 217  == 5.2 See Debug Info ==
218 218  
198 +**For LoRaWAN Server**
219 219  
220 -(((
221 -(% style="color:blue" %)**For LoRaWAN Server**
222 -)))
223 -
224 -(((
225 225  We can check if there is downlink message for this end node, use TTN for example:
226 -)))
227 227  
228 -(((
229 229  Configure a downstream to the end device
230 -)))
231 231  
232 -[[image:image-20220526164623-12.png]]
204 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
233 233  
234 -(((
235 235  Set a downstream in TTN and see it is sent
236 -)))
237 237  
238 238  
239 239  (((
... ... @@ -240,98 +240,96 @@
240 240  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
241 241  )))
242 242  
243 -[[image:image-20220526164650-13.png]]
213 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
244 244  
245 -(((
246 246  Gateway Traffic can see this downstream info
247 -)))
248 248  
249 249  
218 +**For LoRaWAN Gateway**
250 250  
251 251  (((
252 -(% style="color:blue" %)**For LoRaWAN Gateway**
253 -)))
254 -
255 -(((
256 256  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:
257 257  )))
258 258  
259 -[[image:image-20220526164734-14.png]]
224 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
260 260  
261 -(((
262 262  Gateway Sent out this packet
263 -)))
264 264  
265 265  
229 +**For End Node**
266 266  
231 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
232 +
233 +(% class="box infomessage" %)
267 267  (((
268 -(% style="color:blue" %)**For End Node**
235 + AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
269 269  )))
270 270  
238 +(% class="box infomessage" %)
271 271  (((
272 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
240 + AT+RX2DR=3 ~-~--> The RX2 DataRate
273 273  )))
274 274  
243 +(% class="box infomessage" %)
275 275  (((
276 -* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
245 + AT+RX1DL=1000 ~-~--> Receive Delay 1
246 +)))
277 277  
278 -* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
248 +(% class="box infomessage" %)
249 +(((
250 + AT+RX2DL=2000 ~-~--> Receive Delay 2
251 +)))
279 279  
280 -* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
253 +(((
254 +**when the device running, we can see below info:**
255 +)))
281 281  
282 -* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
257 +(((
258 +
283 283  )))
284 284  
261 +(% class="box" %)
285 285  (((
286 -(% style="color:blue" %)**when the device running, we can see below info:**
263 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
264 + [12503]TX on freq 868500000 Hz at DR 0
265 + [13992]txDone
266 + [15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
267 + [15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
268 + [15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
269 + [16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
287 287  )))
288 288  
289 -{{{ [12502]***** UpLinkCounter= 0 *****
290 - [12503]TX on freq 868500000 Hz at DR 0
291 - [13992]txDone
292 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
293 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
294 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
295 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
296 -
297 297  (((
298 298  
299 -
300 -
301 301  )))
302 302  
303 303  (((
304 -(% style="color:blue" %)**Another message:**
277 +**Another message:**
305 305  )))
306 306  
307 -{{{ [12502]***** UpLinkCounter= 0 *****
308 - [12503]TX on freq 868100000 Hz at DR 0
309 - [13992]txDone
310 - [15022]RX on freq 868100000 Hz at DR 0
311 - [15222]rxTimeOut
312 - [15987]RX on freq 869525000 Hz at DR 3
313 - [16185]rxDone --> We have got the downstream packet.
314 - Rssi= -64
315 - Receive data
316 - 1:0012345678}}}
317 317  
281 + [12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
282 + [12503]TX on freq 868100000 Hz at DR 0
283 + [13992]txDone
284 + [15022]RX on freq 868100000 Hz at DR 0
285 + [15222]rxTimeOut
286 + [15987]RX on freq 869525000 Hz at DR 3
287 + [16185]rxDone                              ~-~-> We have got the downstream packet.
288 + Rssi= -64
289 + Receive data
290 + 1:0012345678
318 318  
319 -== 5.3 If problem doesn't solve ==
292 +== 5.3 If problem doesn’t solve ==
320 320  
294 +**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
321 321  
322 -(% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
323 -
324 324  * End node console to show the transmit freuqency and DR.
325 -
326 326  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
327 -
328 328  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
329 -
330 330  * End Node traffic (from server UI) to shows end node activity in server.
331 331  
332 332  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
333 333  
334 -
335 335  (((
336 336  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.
337 337  )))
... ... @@ -344,10 +344,8 @@
344 344  So if the LoRaWAN server is an AS923 server which ask the gateway to transmit at 923.2Mhz frequency, but the gateway is IN868 frequency band (support 865~~867Mhz to transmit). In the gateway log it will show something like below:
345 345  )))
346 346  
347 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
348 -
349 349  (((
350 -
316 +Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
351 351  )))
352 352  
353 353  (((
... ... @@ -357,33 +357,35 @@
357 357  
358 358  = 7. Decrypt a LoRaWAN Packet =
359 359  
326 +~1. LHT65 End device configure:
360 360  
361 -(% style="color:blue" %)**1. LHT65 End device configure:**
328 +(% class="box infomessage" %)
329 +(((
330 +Change to ABP Mode: AT+NJM=0
331 +)))
362 362  
363 -**Change to ABP Mode:  AT+NJM=0**
333 +(% class="box infomessage" %)
334 +(((
335 +Change to fix frequency: AT+CHS=904900000
336 +)))
364 364  
365 -**Change to fix frequency:  AT+CHS=904900000**
338 +(% class="box infomessage" %)
339 +(((
340 +Change to fix DR: AT+DR=0
341 +)))
366 366  
367 -**Change to fix DR:  AT+DR=0**
343 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
368 368  
345 +2. In LG02 , configure to receive above message
369 369  
370 -[[image:image-20220526165525-16.png]]
347 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
371 371  
372 -
373 -
374 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
375 -
376 -[[image:image-20220526165612-17.png]]
377 -
378 -
379 379  In LG02 console, we can see the hex receive are:
380 380  
381 -[[image:image-20220526171112-21.png]]
351 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
382 382  
353 +3. Decode the info in web
383 383  
384 -
385 -(% style="color:blue" %)**3. Decode the info in web**
386 -
387 387  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
388 388  
389 389  Need these three fields:
... ... @@ -394,186 +394,45 @@
394 394  
395 395  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
396 396  
397 -
398 398  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
399 399  
400 -[[image:image-20220526171029-20.png]]
367 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
401 401  
402 -(((
403 - The FRMPayload is the device payload.
404 -)))
369 +The FRMPayload is the device payload.
405 405  
406 406  
407 407  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
408 408  
409 -
410 410  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
411 411  
412 -
413 413  = 9. Why do I see a "MIC Mismatch" error message from the server? =
414 414  
378 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
415 415  
416 -(((
417 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
418 -)))
419 -
420 -(((
421 421  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
422 -)))
423 423  
424 -* (((
425 -Please note the distinction between "APPKEY" and "APPSKEY".
426 -)))
382 +* Please note the distinction between "APPKEY" and "APPSKEY".
427 427  
428 -(((
429 429  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
430 -)))
431 431  
432 -(((
433 433  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
434 -)))
435 435  
436 -* (((
437 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
438 -)))
388 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
439 439  
440 -(% class="wikigeneratedid" %)
441 -3）Wrong Regional Parameters version selected
442 - We generally use versions above 1.0.2
443 -
444 -(% class="wikigeneratedid" %)
445 -[[image:image-20230322163227-1.png]]
446 -
447 -(% class="wikigeneratedid" %)
448 -4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
449 -
450 -
451 451  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
452 452  
392 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
453 453  
454 -(% style="color:blue" %)**Why sensor sends 0x00?**
394 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
455 455  
456 -For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
396 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,
457 457  
458 -**Possible Case 1**:
398 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
459 459  
460 -Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
400 +so it will send a normal uplink packet, and an additional 00 data packet.
461 461  
402 +* Solution: Use the decoder to filter out this 00 packet.
403 +* 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
462 462  
463 -**Possible Case 2:**
464 -
465 -For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
466 -
467 -
468 -(% style="color:blue" %)**How to solve:**
469 -
470 -Solution:
471 -
472 -~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
473 -
474 -2. Data rate changed from DR3 to DR5, increasing upload byte length
475 -AT+ADR=0
476 -AT+DR=3
477 -
478 -Downlink：
479 -
480 -[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
481 -
482 -Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
483 -
484 -
485 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
486 -
487 -
488 -(((
489 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
490 -)))
491 -
492 -(((
493 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
494 -)))
495 -
496 -(((
497 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
498 -)))
499 -
500 -(((
501 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
502 -)))
503 -
504 -(((
505 -AT+APPEUI=00 00 00 00 00 00 00 00
506 -)))
507 -
508 -(((
405 +(% class="wikigeneratedid" id="H" %)
509 509  
510 -)))
511 -
512 -(((
513 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
514 -)))
515 -
516 -(((
517 -You can rewrites the keys by running commands in AT Console
518 -
519 -
520 -)))
521 -
522 -(((
523 -**For example：**
524 -)))
525 -
526 -(((
527 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
528 -)))
529 -
530 -(((
531 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
532 -)))
533 -
534 -(((
535 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
536 -)))
537 -
538 -(((
539 -AT+APPEUI=2C 45 47 E3 24 12 23 24
540 -)))
541 -
542 -(((
543 -(Any combination of 16 bit codes can be used）
544 -
545 -
546 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
547 -)))
548 -
549 -
550 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
551 -
552 -
553 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
554 -
555 -
556 -In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
557 -
558 -
559 -In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
560 -
561 -We have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
562 -
563 -* (((
564 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
565 -)))
566 -* (((
567 -Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
568 -)))
569 -
570 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
571 -
572 -
573 -Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
574 -
575 -
576 -[[image:image-20221215223215-1.png||height="584" width="1280"]]
577 -
578 -(% class="wikigeneratedid" %)
579 -
image-20220526163523-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content
image-20221215223215-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -183.6 KB
Content
image-20230322163227-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -43.1 KB
Content