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

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. OTAA Join Process Debug =
7 7  
9 +
8 8  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.
9 9  \\**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:**
10 10  
... ... @@ -19,7 +19,7 @@
19 19  * If the device is sending join request to server?
20 20  * What frequency the device is sending?
21 21  
22 -[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
24 +[[image:image-20220526164956-15.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
... ... @@ -29,7 +29,7 @@
29 29  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
30 30  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
31 31  
32 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
34 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
... ... @@ -40,7 +40,7 @@
40 40  * 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.
41 41  * 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.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
45 +[[image:image-20220526163633-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
... ... @@ -49,11 +49,11 @@
49 49  
50 50  * 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.
51 51  
52 -[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
54 +[[image:image-20220526163704-4.png]]
53 53  
54 54  The data for the end device set in server
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
58 +[[image:image-20220526163732-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
... ... @@ -60,6 +60,7 @@
60 60  
61 61  = 2. Notice of US915/CN470/AU915 Frequency band =
62 62  
65 +
63 63  (((
64 64  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
65 65  )))
... ... @@ -94,26 +94,35 @@
94 94  Here are the freuqency tables for these bands as reference:
95 95  )))
96 96  
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"]]
100 +[[image:image-20220526163801-6.png]]
98 98  
99 99  US915 Channels
100 100  
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"]]
104 +[[image:image-20220526163926-7.png]]
102 102  
103 103  AU915 Channels
104 104  
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"]]
106 106  
109 +[[image:image-20220526163941-8.png]]
110 +
111 +(((
107 107  CN470 Channels
108 108  
114 +
115 +)))
116 +
109 109  (((
110 110  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
111 111  )))
112 112  
113 -[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
121 +[[image:image-20220526164052-9.png]]
114 114  
123 +(((
115 115  TTN FREQUENCY PLAN
116 116  
126 +
127 +)))
128 +
117 117  (((
118 118  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
119 119  )))
... ... @@ -121,6 +121,7 @@
121 121  
122 122  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
123 123  
136 +
124 124  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:
125 125  
126 126  * **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.
... ... @@ -142,6 +142,7 @@
142 142  
143 143  = 4. Transmision on ABP Mode =
144 144  
158 +
145 145  (((
146 146  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
147 147  )))
... ... @@ -162,7 +162,7 @@
162 162  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
163 163  )))
164 164  
165 -[[~[~[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]]
179 +[[image:image-20220526164508-10.png]]
166 166  
167 167  Disable Frame Counter Check in ABP Mode
168 168  
... ... @@ -171,6 +171,7 @@
171 171  
172 172  == 5.1 How it work ==
173 173  
188 +
174 174  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.
175 175  
176 176  (((
... ... @@ -177,10 +177,11 @@
177 177  Depends on Class A or Class C, the receive windows will be a little difference,
178 178  )))
179 179  
180 -[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
195 +[[image:image-20220531161828-1.png]]
181 181  
182 182  receive windows for Class A and Class C
183 183  
199 +
184 184  Below are the requirement for the End Device to receive the packets.
185 185  
186 186  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -187,19 +187,28 @@
187 187  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
188 188  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
189 189  * This packet must match the frequency of the RX1 or RX2 window.
190 -* 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.**
206 +* 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.**
191 191  
192 192  == 5.2 See Debug Info ==
193 193  
194 -**For LoRaWAN Server**
195 195  
211 +(((
212 +(% style="color:blue" %)**For LoRaWAN Server**
213 +)))
214 +
215 +(((
196 196  We can check if there is downlink message for this end node, use TTN for example:
217 +)))
197 197  
219 +(((
198 198  Configure a downstream to the end device
221 +)))
199 199  
200 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
223 +[[image:image-20220526164623-12.png]]
201 201  
225 +(((
202 202  Set a downstream in TTN and see it is sent
227 +)))
203 203  
204 204  
205 205  (((
... ... @@ -206,128 +206,141 @@
206 206  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
207 207  )))
208 208  
209 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
234 +[[image:image-20220526164650-13.png]]
210 210  
236 +(((
211 211  Gateway Traffic can see this downstream info
238 +)))
212 212  
213 213  
214 -**For LoRaWAN Gateway**
241 +(((
242 +(% style="color:blue" %)**For LoRaWAN Gateway**
243 +)))
215 215  
216 216  (((
217 217  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
218 218  )))
219 219  
220 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
249 +[[image:image-20220526164734-14.png]]
221 221  
251 +(((
222 222  Gateway Sent out this packet
253 +)))
223 223  
224 224  
225 -**For End Node**
226 -
227 -we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
228 -
229 -(% class="box infomessage" %)
230 230  (((
231 - AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
257 +(% style="color:blue" %)**For End Node**
232 232  )))
233 233  
234 -(% class="box infomessage" %)
235 235  (((
236 - AT+RX2DR=3 ~-~--> The RX2 DataRate
261 +we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
237 237  )))
238 238  
239 -(% class="box infomessage" %)
240 240  (((
241 - AT+RX1DL=1000 ~-~--> Receive Delay 1
265 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
266 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
267 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
268 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
269 +
270 +
242 242  )))
243 243  
244 -(% class="box infomessage" %)
245 245  (((
246 - AT+RX2DL=2000 ~-~--> Receive Delay 2
274 +(% style="color:blue" %)**when the device running, we can see below info:**
247 247  )))
248 248  
249 -when the device running, we can see below info:
277 +{{{ [12502]***** UpLinkCounter= 0 *****
278 + [12503]TX on freq 868500000 Hz at DR 0
279 + [13992]txDone
280 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
281 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
282 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
283 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
250 250  
251 -(% class="box" %)
252 252  (((
253 -[12502]~*~*~*~** UpLinkCounter= 0 ~*~*~*~**
254 -[12503]TX on freq 868500000 Hz at DR 0
255 -[13992]txDone
256 -[15022]RX on freq 868500000 Hz at DR 0     ~-~-> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
257 -[15222]rxTimeOut                           ~-~-> no packet arrive in RX1 window. (duration: 200ms)
258 -[15987]RX on freq 869525000 Hz at DR 3     ~-~-> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
259 -[16027]rxTimeOut                           ~-~-> no packet arrive in RX2 window. (duration: 40 ms)
286 +
260 260  )))
261 261  
262 262  (((
263 -
290 +(% style="color:blue" %)**Another message:**
264 264  )))
265 265  
266 -{{{Another message:
267 -[12502]***** UpLinkCounter= 0 *****
268 -[12503]TX on freq 868100000 Hz at DR 0
269 -[13992]txDone
270 -[15022]RX on freq 868100000 Hz at DR 0
271 -[15222]rxTimeOut
272 -[15987]RX on freq 869525000 Hz at DR 3
273 -[16185]rxDone --> We have got the downstream packet.
274 -Rssi= -64
275 -Receive data
276 -1:0012345678
277 -}}}
293 +{{{ [12502]***** UpLinkCounter= 0 *****
294 + [12503]TX on freq 868100000 Hz at DR 0
295 + [13992]txDone
296 + [15022]RX on freq 868100000 Hz at DR 0
297 + [15222]rxTimeOut
298 + [15987]RX on freq 869525000 Hz at DR 3
299 + [16185]rxDone --> We have got the downstream packet.
300 + Rssi= -64
301 + Receive data
302 + 1:0012345678}}}
278 278  
279 -== 5.3 If problem doesn’t solve ==
280 280  
281 -**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:**
305 +== 5.3 If problem doesn't solve ==
282 282  
307 +
308 +(% 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:**
309 +
283 283  * End node console to show the transmit freuqency and DR.
284 284  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
285 285  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
286 286  * End Node traffic (from server UI) to shows end node activity in server.
287 287  
288 -= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
289 289  
290 -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.
291 291  
292 -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:
293 293  
294 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
295 -}}}
318 += 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
296 296  
297 -In this case, please double check the gateway frequency and the server frequency band.
298 298  
321 +(((
322 +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.
323 +)))
299 299  
300 -= 7. Decrypt a LoRaWAN Packet =
325 +(((
326 +
327 +)))
301 301  
302 -~1. LHT65 End device configure:
303 -
304 -(% class="box infomessage" %)
305 305  (((
306 -Change to ABP Mode: AT+NJM=0
330 +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:
307 307  )))
308 308  
309 -(% class="box infomessage" %)
333 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
334 +
310 310  (((
311 -Change to fix frequency: AT+CHS=904900000
336 +
312 312  )))
313 313  
314 -(% class="box infomessage" %)
315 315  (((
316 -Change to fix DR: AT+DR=0
340 +In this case, please double check the gateway frequency and the server frequency band.
317 317  )))
318 318  
319 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
320 320  
321 -2. In LG02 , configure to receive above message
344 += 7. Decrypt a LoRaWAN Packet =
322 322  
323 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
324 324  
347 +(% style="color:blue" %)**1. LHT65 End device configure:**
348 +
349 +**Change to ABP Mode:  AT+NJM=0**
350 +**Change to fix frequency:  AT+CHS=904900000**
351 +**Change to fix DR:  AT+DR=0**
352 +
353 +
354 +[[image:image-20220526165525-16.png]]
355 +
356 +
357 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
358 +
359 +[[image:image-20220526165612-17.png]]
360 +
361 +
325 325  In LG02 console, we can see the hex receive are:
326 326  
327 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
364 +[[image:image-20220526171112-21.png]]
328 328  
329 -3. Decode the info in web
330 330  
367 +(% style="color:blue" %)**3. Decode the info in web**
368 +
331 331  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
332 332  
333 333  Need these three fields:
... ... @@ -338,45 +338,145 @@
338 338  
339 339  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
340 340  
379 +
341 341  [[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]]
342 342  
343 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
382 +[[image:image-20220526171029-20.png]]
344 344  
345 -The FRMPayload is the device payload.
384 +(((
385 + The FRMPayload is the device payload.
386 +)))
346 346  
347 347  
348 348  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
349 349  
391 +
350 350  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.
351 351  
394 +
352 352  = 9. Why do I see a "MIC Mismatch" error message from the server? =
353 353  
354 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
355 355  
398 +(((
399 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
400 +)))
401 +
402 +(((
356 356  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
404 +)))
357 357  
358 -* Please note the distinction between "APPKEY" and "APPSKEY".
406 +* (((
407 +Please note the distinction between "APPKEY" and "APPSKEY".
408 +)))
359 359  
410 +(((
360 360  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
412 +)))
361 361  
414 +(((
362 362  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
416 +)))
363 363  
364 -* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
418 +* (((
419 +If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
365 365  
421 +
422 +
423 +
424 +)))
425 +
366 366  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
367 367  
428 +
368 368  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
369 369  
431 +(((
370 370  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
433 +)))
371 371  
372 -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,
435 +(((
436 +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,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 an additional 00 data packet.
437 +)))
373 373  
374 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
439 +* (((
440 +Solution: Use the decoder to filter out this 00 packet.
441 +)))
442 +* (((
443 +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>>mailto:david.huang@dragino.cc]]
375 375  
376 -so it will send a normal uplink packet, and an additional 00 data packet.
377 377  
378 -* Solution: Use the decoder to filter out this 00 packet.
379 -* 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
380 380  
381 -(% class="wikigeneratedid" id="H" %)
382 382  
448 +)))
449 +
450 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
451 +
452 +
453 +(((
454 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
455 +)))
456 +
457 +(((
458 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
459 +)))
460 +
461 +(((
462 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
463 +)))
464 +
465 +(((
466 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
467 +)))
468 +
469 +(((
470 +AT+APPEUI=00 00 00 00 00 00 00 00
471 +)))
472 +
473 +(((
474 +
475 +)))
476 +
477 +(((
478 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
479 +)))
480 +
481 +(((
482 +You can rewrites the keys by running commands in AT Console
483 +
484 +
485 +)))
486 +
487 +(((
488 +**For example：**
489 +)))
490 +
491 +(((
492 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
493 +)))
494 +
495 +(((
496 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
497 +)))
498 +
499 +(((
500 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
501 +)))
502 +
503 +(((
504 +AT+APPEUI=2C 45 47 E3 24 12 23 24
505 +)))
506 +
507 +(((
508 +(Any combination of 16 bit codes can be used）
509 +
510 +
511 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
512 +)))
513 +
514 +
515 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
516 +
517 +
518 +
519 +(% class="wikigeneratedid" %)
520 +
image-20220526163523-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content

Applications

Navigation

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