Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 37.3
edited by Xiaoling
on 2022/12/16 11:15
Change comment: There is no comment for this version
To version 102.1
edited by Xiaoling
on 2025/05/05 08:51
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
7 += 1. Join process page check =
8 8  
9 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.
... ... @@ -26,12 +26,11 @@
26 26  
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
30 30  
31 -Console Output from End device to see the transmit frequency
31 +Console Output from End device to see the transmit frequency.
32 32  
33 33  
34 -
35 35  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 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,55 +38,52 @@
38 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]]
40 +[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
42 42  
43 43  Console Output from Gateway to see packets between end node and server.
44 44  
45 45  
45 +(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
46 46  
47 -(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
47 +* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
48 48  
49 -* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
49 +* Does the server send back a Join Accept for the Join Request? If not, check that the key from the device matches the key you put into the server, or try to choose a different server route for that end device.
50 50  
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]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
56 56  
57 -The Traffic for the End node in the server, use TTN as example
55 +The Traffic for the End node in the server, use TTN as example.
58 58  
59 59  
60 -
61 61  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 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]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
66 66  
67 67  The data for the end device set in server
68 68  
66 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
69 69  
70 -[[image:image-20220526163732-5.png]]
68 +Check if OTAA Keys match the keys in device.
71 71  
72 -Check if OTAA Keys match the keys in device
73 73  
74 -
75 75  = 2. Notice of US915/CN470/AU915 Frequency band =
76 76  
77 77  
78 78  (((
79 -If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
75 +If user has problem to work with LoRaWAN server in band US915/AU915/CN470, he can check:
80 80  )))
81 81  
82 82  * (((
83 -What **sub-band** the server support ?
79 +What **sub-band** the server support?
84 84  )))
85 85  * (((
86 -What is the **sub-band** the gateway support ?
82 +What is the **sub-band** the gateway support?
87 87  )))
88 88  * (((
89 -What is the **sub-band** the end node is using ?
85 +What is the **sub-band** the end node is using?
90 90  )))
91 91  
92 92  (((
... ... @@ -98,7 +98,7 @@
98 98  )))
99 99  
100 100  (((
101 -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.
97 +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.
102 102  )))
103 103  
104 104  (((
... ... @@ -106,7 +106,7 @@
106 106  )))
107 107  
108 108  (((
109 -Here are the freuqency tables for these bands as reference:
105 +Here are the frequency tables for these bands as reference:
110 110  )))
111 111  
112 112  [[image:image-20220526163801-6.png]]
... ... @@ -131,7 +131,7 @@
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]]
130 +[[image:image-20240123151225-3.png||height="434" width="902"]]
135 135  
136 136  (((
137 137  TTN FREQUENCY PLAN
... ... @@ -145,7 +145,7 @@
145 145  
146 146  (% style="display:none" %) (%%)
147 147  
148 -= 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
144 += 3. Why I see data lost/ is not periodically uplink？ Even the signal strength is good =
149 149  
150 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:
... ... @@ -166,10 +166,205 @@
166 166  )))
167 167  
168 168  
169 -= 4. Transmision on ABP Mode =
165 += 4. Why i see packet lost =
170 170  
167 +== **1. Signal problem** ==
171 171  
169 +
170 +(% style="color:blue" %)**1)**(%%)  (% style="color:blue" %)**ADR automatic adjustment** (%%)
171 +
172 +**Reason:**
173 +
174 +When the signal is at a critical value, the server may configure the node to adjust to a lower power DR.
175 +At this time, the server is at risk of losing uplink.
176 +
177 +
178 +**Solution:**
179 +
180 +Users can manually fix the DR value.
181 +
182 +
183 +(% style="color:red" %)
184 +**Notice:**
185 +
186 +* User need to set Adaptive Data Rate(ADR)=0 first. otherwise device will respond to server's ADR command and change the DR according to server auto-adjustment.
187 +
188 +* Data Rate specifies Spreading Factor. The mapping varies in different frequency bands. User can check this link for detail. [[rp2-1.0.3-lorawan-regional-parameters.pdf>>https://lora-alliance.org/resource_hub/rp2-1-0-3-lorawan-regional-parameters/]]
189 +
190 +(% style="color:blue" %)**AT Command: AT+DR**
191 +
192 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:409px" %)
193 +|(% style="background-color:#4f81bd; color:white; width:156px" %)**Command Example**|(% style="background-color:#4f81bd; color:white; width:147px" %)**Function**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Response**
194 +|(% style="width:156px" %)AT+DR=?|(% style="width:147px" %)Get the Data Rate.|(% style="width:100px" %)5(((
195 +OK
196 +)))
197 +|(% style="width:156px" %)AT+DR=2|(% style="width:147px" %)Set the Data Rate.|(% style="width:100px" %)OK(((
198 +
199 +)))
200 +
201 +(% style="color:blue" %)**Downlink Command: 0x2200aaFF**
202 +
203 +If the downlink payload=220001FF, it means setting the data rate to 1, while type code is 22 00 aa FF.
204 +
205 +* **Example 1**: Downlink Payload: **220001FF**  ~/~/ Set AT+DR=1.
206 +
207 +* **Example 2**: Downlink Payload: **220000FF**  ~/~/ Set AT+DR=0.
208 +
209 +(% style="display:none" %) (%%)
210 +
211 +
212 +(% style="color:blue" %)**2)**(%%)  (% style="color:blue" %)**Node antenna problem**
213 +
214 +**Reason:**
215 +
216 +Node antenna is loose
217 +
218 +
219 +**Solution:**
220 +
221 +Please check whether the antenna interface and module interface are detached
222 +
223 +[[image:image-20250429114526-1.png||height="429" width="303"]]
224 +
225 +
226 +
227 +(% style="color:blue" %)**3) **(%%) (% style="color:blue" %)**Gateway antenna problem**
228 +
229 +**Reason:**
230 +Gateway uses antenna with wrong frequency band
231 +
232 +For example: 868-band gateway uses antenna with 915-band, which will cause the signal to be greatly reduced
233 +
234 +
235 +**Solution:**
236 +
237 +Please check whether the silk screen on the antenna conflicts with the frequency you set.
238 +
239 +[[image:image-20250429115124-2.png]][[image:image-20250429115159-3.png||height="550" width="224"]]
240 +
241 +
242 +(% style="color:blue" %)**4) **(%%) (% style="color:blue" %)**Gateway module problem**
243 +
244 +**Reason:**
245 +
246 +Gateway uses module with wrong frequency band
247 +For example: 868-band gateway uses module with 915-band, which will cause the signal to be greatly reduced
248 +
249 +
250 +**Solution:**
251 +
252 +Please check whether the silkscreen of the module conflicts with the frequency you set.
253 +
254 +[[image:image-20250429115951-5.png||height="288" width="384"]][[image:image-20250429133640-7.png||height="284" width="378"]]
255 +
256 +
257 +== **2. Frequency point problem** ==
258 +
259 +
260 +**Reason:**
261 +
262 +There are multiple frequency configurations in AS923/US915/AU915/CN470.
263 +
264 +The frequency point of the gateway or server is wrong or missing.
265 +
266 +
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 +
274 +== **3. Frequency band problem** ==
275 +
276 +
277 +**Reason:**
278 +
279 +When there are multiple gateways, the node cannot lock the frequency band.
280 +
281 +
282 +**Solution:**
283 +
172 172  (((
285 +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.
286 +)))
287 +
288 +(((
289 +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.
290 +)))
291 +
292 +(((
293 +
294 +)))
295 +
296 +(((
297 +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.
298 +)))
299 +
300 +[[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"]]
301 +
302 +
303 +(((
304 +When you use the TTN V3 network, the US915 frequency bands use are:
305 +)))
306 +
307 +* (((
308 +903.9 - SF7BW125 to SF10BW125
309 +)))
310 +* (((
311 +904.1 - SF7BW125 to SF10BW125
312 +)))
313 +* (((
314 +904.3 - SF7BW125 to SF10BW125
315 +)))
316 +* (((
317 +904.5 - SF7BW125 to SF10BW125
318 +)))
319 +* (((
320 +904.7 - SF7BW125 to SF10BW125
321 +)))
322 +* (((
323 +904.9 - SF7BW125 to SF10BW125
324 +)))
325 +* (((
326 +905.1 - SF7BW125 to SF10BW125
327 +)))
328 +* (((
329 +905.3 - SF7BW125 to SF10BW125
330 +)))
331 +* (((
332 +904.6 - SF8BW500
333 +)))
334 +
335 +(((
336 +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:
337 +)))
338 +
339 +(((
340 +(% style="color:blue" %)**AT+CHE=2**
341 +)))
342 +
343 +(((
344 +(% style="color:blue" %)**ATZ**
345 +)))
346 +
347 +
348 +(((
349 +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.
350 +)))
351 +
352 +(((
353 +The (% style="color:blue" %)**AU915**(%%) band is similar. Below are the AU915 Uplink Channels.
354 +
355 +[[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"]]
356 +
357 +
358 +)))
359 +
360 += 5. Transmision on ABP Mode =
361 +
362 +
363 +(((
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  
... ... @@ -179,22 +179,29 @@
179 179  
180 180  (((
181 181  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
373 +
374 +[[image:image-20240123161737-4.png||height="395" width="763"]]
182 182  )))
183 183  
184 -[[image:image-20220526164508-10.png]]
377 +[[image:image-20240123161853-6.png||height="599" width="771"]]
185 185  
186 186  Disable Frame Counter Check in ABP Mode
187 187  
188 188  
189 -= 5. Downstream Debug =
382 += 6. Downstream Debug =
190 190  
191 -== 5.1 How it work ==
384 +== 6.1 How it work ==
192 192  
193 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 -Depends on Class A or Class C, the receive windows will be a little difference,
390 +Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
391 +
392 +* **Class A** : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
393 +* **Class C**: End node can receive downlink immediately but have higher power consumption.
394 +
395 +
198 198  )))
199 199  
200 200  [[image:image-20220531161828-1.png]]
... ... @@ -214,11 +214,9 @@
214 214  
215 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 216  
415 +== 6.2 See Debug Info ==
217 217  
218 218  
219 -== 5.2 See Debug Info ==
220 -
221 -
222 222  (((
223 223  (% style="color:blue" %)**For LoRaWAN Server**
224 224  )))
... ... @@ -228,24 +228,27 @@
228 228  )))
229 229  
230 230  (((
231 -Configure a downstream to the end device
427 +Configure a downlink to the end device
428 +
429 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
232 232  )))
233 233  
234 -[[image:image-20220526164623-12.png]]
235 235  
236 236  (((
237 237  Set a downstream in TTN and see it is sent
238 238  )))
239 239  
437 +(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.**
240 240  
439 +
241 241  (((
242 -This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
441 +This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
243 243  )))
244 244  
245 -[[image:image-20220526164650-13.png]]
444 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
246 246  
247 247  (((
248 -Gateway Traffic can see this downstream info
447 +Gateway Traffic can see this downlink info
249 249  )))
250 250  
251 251  
... ... @@ -255,10 +255,10 @@
255 255  )))
256 256  
257 257  (((
258 -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:
457 +When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
259 259  )))
260 260  
261 -[[image:image-20220526164734-14.png]]
460 +[[image:image-20240129154321-9.png]]
262 262  
263 263  (((
264 264  Gateway Sent out this packet
... ... @@ -318,7 +318,7 @@
318 318   1:0012345678}}}
319 319  
320 320  
321 -== 5.3 If problem doesn't solve ==
520 +== 6.3 If problem doesn't solve ==
322 322  
323 323  
324 324  (% 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:**
... ... @@ -331,11 +331,11 @@
331 331  
332 332  * End Node traffic (from server UI) to shows end node activity in server.
333 333  
334 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
533 += 7. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335 335  
336 336  
337 337  (((
338 -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.
537 +In LoRaWAN, the gateway 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.
339 339  )))
340 340  
341 341  (((
... ... @@ -357,62 +357,72 @@
357 357  )))
358 358  
359 359  
360 -= 7. Decrypt a LoRaWAN Packet =
559 += 8. Decrypt a LoRaWAN Packet =
361 361  
362 362  
363 -(% style="color:blue" %)**1. LHT65 End device configure:**
562 +(% style="color:blue" %)**1. LHT65N End device configure:**
364 364  
365 365  **Change to ABP Mode:  AT+NJM=0**
366 366  
367 -**Change to fix frequency:  AT+CHS=904900000**
566 +**Change to fix frequency:  ​​​​AT+CHE=1**
368 368  
369 -**Change to fix DR:  AT+DR=0**
370 370  
569 +**AT+CFG(Print configuration):**
371 371  
372 -[[image:image-20220526165525-16.png]]
571 +[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
373 373  
374 374  
574 +**Configuration: **
375 375  
376 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
576 +[[image:image-20240129164219-4.png||height="612" width="440"]]
377 377  
378 -[[image:image-20220526165612-17.png]]
379 379  
380 380  
381 -In LG02 console, we can see the hex receive are:
580 +(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
382 382  
383 -[[image:image-20220526171112-21.png]]
582 +[[image:image-20240129164326-5.png||height="506" width="1114"]]
384 384  
385 385  
585 +In LPS8-v2 console, we can see the Base64 receive are:
386 386  
387 -(% style="color:blue" %)**3. Decode the info in web**
587 +[[image:image-20240129170137-6.png||height="459" width="1116"]]
388 388  
389 -[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
390 390  
391 -Need these three fields:
590 +(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
392 392  
393 -LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
592 +LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
394 394  
395 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
594 +Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
396 396  
397 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
398 398  
597 +**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
399 399  
400 -[[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]]
599 +[[image:image-20240129190752-17.png||height="338" width="901"]]
401 401  
402 -[[image:image-20220526171029-20.png]]
601 +[[image:image-20240129191937-21.png||height="450" width="901"]]
403 403  
404 -(((
405 - The FRMPayload is the device payload.
406 -)))
407 407  
604 +**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
408 408  
409 -= 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
606 +[[image:image-20240129192239-22.png||height="416" width="902"]]
410 410  
608 +[[image:image-20240129192549-23.png||height="459" width="898"]]
411 411  
610 +
611 +**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
612 +
613 +[[image:image-20240129192908-24.png||height="477" width="907"]]
614 +
615 +[[image:image-20240129192954-25.png||height="485" width="916"]]
616 +
617 +
618 += 9. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
619 +
620 +
412 412  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.
413 413  
414 414  
415 -= 9. Why do I see a "MIC Mismatch" error message from the server? =
624 += 10. Why do I see a "MIC Mismatch" error message from the server? =
416 416  
417 417  
418 418  (((
... ... @@ -437,31 +437,54 @@
437 437  
438 438  * (((
439 439  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
649 +)))
440 440  
651 +(% class="wikigeneratedid" %)
652 +3）Wrong Regional Parameters version selected
653 + We generally use versions above 1.0.2
441 441  
442 -
443 -)))
655 +(% class="wikigeneratedid" %)
656 +[[image:image-20230322163227-1.png]]
444 444  
445 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
658 +(% class="wikigeneratedid" %)
659 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
446 446  
447 447  
448 -(% style="color:blue" %)**Why this happen:**
662 += 11. Why I got the payload only with "0x00" or "AA~=~="? =
449 449  
450 -For US915, AU915 or AS923 frequencies.It is possible because: .
451 451  
452 -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.
665 +(% style="color:blue" %)**Why sensor sends 0x00?**
453 453  
454 -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.
667 +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.
455 455  
669 +**Possible Case 1**:
456 456  
671 +Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
672 +
673 +
674 +**Possible Case 2:**
675 +
676 +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.
677 +
678 +
457 457  (% style="color:blue" %)**How to solve:**
458 458  
459 -Solution: Use the decoder to filter out this 0x00 packet.
681 +Solution:
460 460  
683 +~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
684 +
685 +2. Data rate changed from DR3 to DR5, increasing upload byte length
686 +AT+ADR=0
687 +AT+DR=3
688 +
689 +Downlink：
690 +
691 +[[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]]
692 +
461 461  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]]
462 462  
463 463  
464 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
696 += 12. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
465 465  
466 466  
467 467  (((
... ... @@ -522,7 +522,7 @@
522 522  (Any combination of 16 bit codes can be used）
523 523  
524 524  
525 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
757 += 13. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
526 526  )))
527 527  
528 528  
... ... @@ -529,30 +529,27 @@
529 529  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
530 530  
531 531  
532 -= 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
764 += 14. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
533 533  
534 534  
535 -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.
767 +In US915, AU915 or CN470 frequency band, there are 8 sub-bands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Sub-band 2 in TTN. The gateway also configured to Sub-band 2 and cover eight channels in this sub-band. If the end node transfer data in Sub-band 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other sub-bands, for example sub-band 1, the packet won't arrive both gateway or LoRaWAN server.
536 536  
537 537  
538 -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:
770 +In Dragino Sensors old version firmware (before early 2022), the sub-band is fixed the sub-band 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:
539 539  
540 -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:
772 +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 sub-bands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
541 541  
542 542  * (((
543 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
775 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band.
544 544  )))
545 545  * (((
546 -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)
778 +Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message (TTN v2 doesn't include).
547 547  )))
548 548  
549 -This change will make the activation time a littler longer but make sure the device can be used in any subband.
781 +This change will make the activation time a little longer but make sure the device can be used in any sub-band.
550 550  
551 551  
552 -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.
784 +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 sub-band he uses.
553 553  
554 554  
555 555  [[image:image-20221215223215-1.png||height="584" width="1280"]]
556 -
557 -(% class="wikigeneratedid" %)
558 -
image-20230322163227-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.1 KB
Content
image-20240123150720-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +119.9 KB
Content
image-20240123150943-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +161.5 KB
Content
image-20240123151225-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +136.1 KB
Content
image-20240123161737-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +83.0 KB
Content
image-20240123161806-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.5 KB
Content
image-20240123161853-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +60.6 KB
Content
image-20240123163307-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +123.3 KB
Content
image-20240123182345-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +108.0 KB
Content
image-20240129142110-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +116.1 KB
Content
image-20240129142557-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +125.7 KB
Content
image-20240129142631-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +189.0 KB
Content
image-20240129150821-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.1 KB
Content
image-20240129175037-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129190752-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +62.4 KB
Content
image-20250429114526-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +3.2 MB
Content
image-20250429115124-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +193.2 KB
Content
image-20250429115159-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1014.1 KB
Content
image-20250429115942-4.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +435.8 KB
Content
image-20250429115951-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429120030-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content
image-20250429133640-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +1.4 MB
Content