Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 35.1
edited by Edwin Chen
on 2022/10/19 23:15
Change comment: There is no comment for this version
To version 4.1
edited by Xiaoling
on 2022/05/11 14:26
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,12 +1,10 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 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  
... ... @@ -16,127 +16,87 @@
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
17 17  * 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)
18 18  
19 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
17 +**~1. End Device Join Screen shot, we can check:**
20 20  
21 21  * If the device is sending join request to server?
22 22  * What frequency the device is sending?
23 23  
24 -[[image:image-20220526164956-15.png]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
25 25  
26 26  Console Output from End device to see the transmit frequency
27 27  
28 28  
27 +**2. Gateway packet traffic in gateway web or ssh. we can check:**
29 29  
30 -(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 -
32 32  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
33 33  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
34 34  
35 -[[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"]]
36 36  
37 37  Console Output from Gateway to see packets between end node and server.
38 38  
39 39  
40 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
37 +**3. Gateway Traffic Page in LoRaWAN Server**
41 41  
42 42  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
43 43  * 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.
44 44  * 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.
45 45  
46 -[[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"]]
47 47  
48 48  The Traffic for the End node in the server, use TTN as example
49 49  
50 50  
51 -(% style="color:blue" %)**4. Data Page in LoRaWAN server**
48 +**4. Data Page in LoRaWAN server**
52 52  
53 53  * 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.
54 54  
55 -[[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"]]
56 56  
57 57  The data for the end device set in server
58 58  
59 -[[image:image-20220526163732-5.png]]
56 +[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
60 60  
61 61  Check if OTAA Keys match the keys in device
62 62  
63 63  
64 -
65 65  = 2. Notice of US915/CN470/AU915 Frequency band =
66 66  
67 -
68 -(((
69 69  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
70 -)))
71 71  
72 -* (((
73 -What **sub-band** the server support ?
74 -)))
75 -* (((
76 -What is the **sub-band** the gateway support ?
77 -)))
78 -* (((
79 -What is the **sub-band** the end node is using ?
80 -)))
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 ?
81 81  
82 -(((
83 83  All of above should match so End Node can properly Join the server and don't have packet lost.
84 -)))
85 85  
86 -(((
87 -
88 -)))
89 -
90 -(((
91 91  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.
92 -)))
93 93  
94 -(((
95 -
96 -)))
97 -
98 -(((
99 99  Here are the freuqency tables for these bands as reference:
100 -)))
101 101  
102 -[[image:image-20220526163801-6.png]]
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"]]
103 103  
104 104  US915 Channels
105 105  
106 -[[image:image-20220526163926-7.png]]
79 +[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
107 107  
108 108  AU915 Channels
109 109  
83 +[[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png||height="205" width="600"]]
110 110  
111 -[[image:image-20220526163941-8.png]]
112 -
113 -(((
114 114  CN470 Channels
115 115  
116 -
117 -)))
118 -
119 -(((
120 120  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.
121 -)))
122 122  
123 -[[image:image-20220526164052-9.png]]
89 +[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
124 124  
125 -(((
126 126  TTN FREQUENCY PLAN
127 127  
128 -
129 -)))
130 -
131 -(((
132 132  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. )
133 -)))
134 134  
135 135  
136 -
137 137  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
138 138  
139 -
140 140  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:
141 141  
142 142  * **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.
... ... @@ -143,65 +143,36 @@
143 143  * **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
144 144  * **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.
145 145  
146 -(((
147 147  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.
148 -)))
149 149  
150 -(((
151 -
152 -)))
153 -
154 -(((
155 155  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.
156 -)))
157 157  
158 158  
159 -
160 160  = 4. Transmision on ABP Mode =
161 161  
162 -
163 -(((
164 164  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.
165 -)))
166 166  
167 -(((
168 -
169 -)))
170 -
171 -(((
172 172  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.
173 -)))
174 174  
175 -(((
176 -
177 -)))
178 -
179 -(((
180 180  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
181 -)))
182 182  
183 -[[image:image-20220526164508-10.png]]
117 +[[~[~[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]]
184 184  
185 185  Disable Frame Counter Check in ABP Mode
186 186  
187 187  
188 -
189 189  = 5. Downstream Debug =
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 -(((
197 197  Depends on Class A or Class C, the receive windows will be a little difference,
198 -)))
199 199  
200 -[[image:image-20220531161828-1.png]]
130 +[[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,116 +208,89 @@
208 208  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
209 209  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
210 210  * This packet must match the frequency of the RX1 or RX2 window.
211 -* 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.**
140 +* 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.**
212 212  
213 213  == 5.2 See Debug Info ==
214 214  
144 +**For LoRaWAN Server**
215 215  
216 -(((
217 -(% style="color:blue" %)**For LoRaWAN Server**
218 -)))
219 -
220 -(((
221 221  We can check if there is downlink message for this end node, use TTN for example:
222 -)))
223 223  
224 -(((
225 225  Configure a downstream to the end device
226 -)))
227 227  
228 -[[image:image-20220526164623-12.png]]
150 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
229 229  
230 -(((
231 231  Set a downstream in TTN and see it is sent
232 -)))
233 233  
234 234  
235 -(((
236 236  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
237 -)))
238 238  
239 -[[image:image-20220526164650-13.png]]
157 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
240 240  
241 -(((
242 242  Gateway Traffic can see this downstream info
243 -)))
244 244  
245 245  
162 +**For LoRaWAN Gateway**
246 246  
247 -(((
248 -(% style="color:blue" %)**For LoRaWAN Gateway**
249 -)))
250 -
251 -(((
252 252  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:
253 -)))
254 254  
255 -[[image:image-20220526164734-14.png]]
166 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
256 256  
257 -(((
258 258  Gateway Sent out this packet
259 -)))
260 260  
261 261  
171 +**For End Node**
262 262  
263 -(((
264 -(% style="color:blue" %)**For End Node**
265 -)))
266 -
267 -(((
268 268  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
269 -)))
270 270  
175 +(% class="box infomessage" %)
271 271  (((
272 -(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
273 -(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
274 -(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
275 -(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
276 -
277 -
278 -
177 +AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
279 279  )))
280 280  
180 +(% class="box infomessage" %)
281 281  (((
282 -(% style="color:blue" %)**when the device running, we can see below info:**
182 +AT+RX2DR=3 ~-~--> The RX2 DataRate
283 283  )))
284 284  
285 -{{{ [12502]***** UpLinkCounter= 0 *****
286 - [12503]TX on freq 868500000 Hz at DR 0
287 - [13992]txDone
288 - [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
289 - [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
290 - [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
291 - [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
292 -
185 +(% class="box infomessage" %)
293 293  (((
294 -
295 -
296 -
187 +AT+RX1DL=1000 ~-~--> Receive Delay 1
297 297  )))
298 298  
190 +(% class="box infomessage" %)
299 299  (((
300 -(% style="color:blue" %)**Another message:**
192 +AT+RX2DL=2000 ~-~--> Receive Delay 2
301 301  )))
302 302  
303 -{{{ [12502]***** UpLinkCounter= 0 *****
304 - [12503]TX on freq 868100000 Hz at DR 0
305 - [13992]txDone
306 - [15022]RX on freq 868100000 Hz at DR 0
307 - [15222]rxTimeOut
308 - [15987]RX on freq 869525000 Hz at DR 3
309 - [16185]rxDone --> We have got the downstream packet.
310 - Rssi= -64
311 - Receive data
312 - 1:0012345678}}}
195 +when the device running, we can see below info:
313 313  
197 +{{{[12502]***** UpLinkCounter= 0 *****
198 +[12503]TX on freq 868500000 Hz at DR 0
199 +[13992]txDone
200 +[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
201 +[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
202 +[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
203 +[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
204 +}}}
314 314  
206 +{{{Another message:
207 +[12502]***** UpLinkCounter= 0 *****
208 +[12503]TX on freq 868100000 Hz at DR 0
209 +[13992]txDone
210 +[15022]RX on freq 868100000 Hz at DR 0
211 +[15222]rxTimeOut
212 +[15987]RX on freq 869525000 Hz at DR 3
213 +[16185]rxDone --> We have got the downstream packet.
214 +Rssi= -64
215 +Receive data
216 +1:0012345678
217 +}}}
315 315  
316 -== 5.3 If problem doesn't solve ==
219 +== 5.3 If problem doesn’t solve ==
317 317  
221 +**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:**
318 318  
319 -(% 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:**
320 -
321 321  * End node console to show the transmit freuqency and DR.
322 322  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
323 323  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
... ... @@ -325,58 +325,47 @@
325 325  
326 326  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
327 327  
328 -
329 -(((
330 330  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.
331 -)))
332 332  
333 -(((
334 -
335 -)))
336 -
337 -(((
338 338  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:
339 -)))
340 340  
341 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
234 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
235 +}}}
342 342  
343 -(((
344 -
345 -)))
346 -
347 -(((
348 348  In this case, please double check the gateway frequency and the server frequency band.
349 -)))
350 350  
351 351  
352 -
353 353  = 7. Decrypt a LoRaWAN Packet =
354 354  
242 +~1. LHT65 End device configure:
355 355  
356 -(% style="color:blue" %)**1. LHT65 End device configure:**
244 +(% class="box infomessage" %)
245 +(((
246 +Change to ABP Mode: AT+NJM=0
247 +)))
357 357  
358 -**Change to ABP Mode:  AT+NJM=0**
359 -**Change to fix frequency:  AT+CHS=904900000**
360 -**Change to fix DR:  AT+DR=0**
249 +(% class="box infomessage" %)
250 +(((
251 +Change to fix frequency: AT+CHS=904900000
252 +)))
361 361  
254 +(% class="box infomessage" %)
255 +(((
256 +Change to fix DR: AT+DR=0
257 +)))
362 362  
363 -[[image:image-20220526165525-16.png]]
259 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
364 364  
261 +2. In LG02 , configure to receive above message
365 365  
263 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
366 366  
367 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
368 -
369 -[[image:image-20220526165612-17.png]]
370 -
371 -
372 372  In LG02 console, we can see the hex receive are:
373 373  
374 -[[image:image-20220526171112-21.png]]
267 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
375 375  
269 +3. Decode the info in web
376 376  
377 -
378 -(% style="color:blue" %)**3. Decode the info in web**
379 -
380 380  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
381 381  
382 382  Need these three fields:
... ... @@ -387,144 +387,45 @@
387 387  
388 388  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
389 389  
390 -
391 391  [[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]]
392 392  
393 -[[image:image-20220526171029-20.png]]
283 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
394 394  
395 -(((
396 - The FRMPayload is the device payload.
397 -)))
285 +The FRMPayload is the device payload.
398 398  
399 399  
400 -
401 401  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
402 402  
403 -
404 404  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.
405 405  
406 -
407 -
408 408  = 9. Why do I see a "MIC Mismatch" error message from the server? =
409 409  
294 +1)If the user receives a "MIC Mismatch" message after registering the node on the server.
410 410  
411 -(((
412 -1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
413 -)))
414 -
415 -(((
416 416  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
417 -)))
418 418  
419 -* (((
420 -Please note the distinction between "APPKEY" and "APPSKEY".
421 -)))
298 +* Please note the distinction between "APPKEY" and "APPSKEY".
422 422  
423 -(((
424 424  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
425 -)))
426 426  
427 -(((
428 428  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
429 -)))
430 430  
431 -* (((
432 -If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
304 +* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
433 433  
434 -
435 -
436 -
437 -)))
438 -
439 439  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
440 440  
308 +* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
441 441  
442 -**Why this happen:**
310 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
443 443  
444 -For US915, AU915 or AS923 frequencies.It is possible because: .
312 +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,
445 445  
446 -When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
314 +and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
447 447  
448 -When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, so it will send a normal uplink packet, and following an additional 00 data packet to handle this MAC command response.
316 +so it will send a normal uplink packet, and an additional 00 data packet.
449 449  
318 +* Solution: Use the decoder to filter out this 00 packet.
319 +* 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
450 450  
451 -**How to solve:**
452 -
453 -Solution: Use the decoder to filter out this 0x00 packet.
454 -
455 -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]]
456 -
457 -
458 -
459 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
460 -
461 -
462 -(((
463 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
464 -)))
465 -
466 -(((
467 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
468 -)))
469 -
470 -(((
471 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
472 -)))
473 -
474 -(((
475 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
476 -)))
477 -
478 -(((
479 -AT+APPEUI=00 00 00 00 00 00 00 00
480 -)))
481 -
482 -(((
321 +(% class="wikigeneratedid" id="H" %)
483 483  
484 -)))
485 -
486 -(((
487 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
488 -)))
489 -
490 -(((
491 -You can rewrites the keys by running commands in AT Console
492 -
493 -
494 -)))
495 -
496 -(((
497 -**For example：**
498 -)))
499 -
500 -(((
501 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
502 -)))
503 -
504 -(((
505 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
506 -)))
507 -
508 -(((
509 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
510 -)))
511 -
512 -(((
513 -AT+APPEUI=2C 45 47 E3 24 12 23 24
514 -)))
515 -
516 -(((
517 -(Any combination of 16 bit codes can be used）
518 -
519 -
520 -
521 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
522 -)))
523 -
524 -
525 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
526 -
527 -
528 -
529 -(% class="wikigeneratedid" %)
530 -
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