Last modified by Bei Jinggeng on 2025/04/29 13:57
<
From version < 4.2 >
edited by Xiaoling
on 2022/05/11 14:30
To version < 32.14 >
edited by Xiaoling
on 2022/07/13 15:24
>
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  
... ... @@ -14,46 +14,48 @@
14 14  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
15 15  * 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)
16 16  
17 -**~1. End Device Join Screen shot, we can check:**
18 18  
20 +
21 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
22 +
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"]]
26 +[[image:image-20220526164956-15.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
26 26  
27 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
31 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
28 28  
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"]]
36 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
36 36  
37 -**3. Gateway Traffic Page in LoRaWAN Server**
41 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
38 38  
39 39  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
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"]]
47 +[[image:image-20220526163633-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
47 47  
48 -**4. Data Page in LoRaWAN server**
52 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
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"]]
56 +[[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"]]
60 +[[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  
67 +
63 63  (((
64 64  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
65 65  )))
... ... @@ -94,29 +94,43 @@
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"]]
102 +[[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"]]
106 +[[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  
111 +[[image:image-20220526163941-8.png]]
112 +
113 +(((
107 107  CN470 Channels
108 108  
116 +
117 +)))
118 +
119 +(((
109 109  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
121 +)))
110 110  
111 -[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
123 +[[image:image-20220526164052-9.png]]
112 112  
125 +(((
113 113  TTN FREQUENCY PLAN
114 114  
128 +
129 +)))
130 +
131 +(((
115 115  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
133 +)))
116 116  
117 117  
118 118  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
119 119  
138 +
120 120  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:
121 121  
122 122  * **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.
... ... @@ -123,20 +123,43 @@
123 123  * **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
124 124  * **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
125 125  
145 +(((
126 126  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
147 +)))
127 127  
149 +(((
150 +
151 +)))
152 +
153 +(((
128 128  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
155 +)))
129 129  
130 130  
131 131  = 4. Transmision on ABP Mode =
132 132  
160 +
161 +(((
133 133  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
163 +)))
134 134  
165 +(((
166 +
167 +)))
168 +
169 +(((
135 135  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
171 +)))
136 136  
173 +(((
174 +
175 +)))
176 +
177 +(((
137 137  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
179 +)))
138 138  
139 -[[~[~[image:https://wiki.dragino.com/images/thumb/1/19/ABP_Issue-1.jpg/600px-ABP_Issue-1.jpg~|~|height="340" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:ABP_Issue-1.jpg]]
181 +[[image:image-20220526164508-10.png]]
140 140  
141 141  Disable Frame Counter Check in ABP Mode
142 142  
... ... @@ -145,14 +145,18 @@
145 145  
146 146  == 5.1 How it work ==
147 147  
190 +
148 148  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
149 149  
193 +(((
150 150  Depends on Class A or Class C, the receive windows will be a little difference,
195 +)))
151 151  
152 -[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
197 +[[image:image-20220531161828-1.png]]
153 153  
154 154  receive windows for Class A and Class C
155 155  
201 +
156 156  Below are the requirement for the End Device to receive the packets.
157 157  
158 158  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -159,88 +159,109 @@
159 159  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
160 160  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
161 161  * This packet must match the frequency of the RX1 or RX2 window.
162 -* 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.**
208 +* 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.**
163 163  
164 164  == 5.2 See Debug Info ==
165 165  
166 -**For LoRaWAN Server**
167 167  
213 +(((
214 +(% style="color:blue" %)**For LoRaWAN Server**
215 +)))
216 +
217 +(((
168 168  We can check if there is downlink message for this end node, use TTN for example:
219 +)))
169 169  
221 +(((
170 170  Configure a downstream to the end device
223 +)))
171 171  
172 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
225 +[[image:image-20220526164623-12.png]]
173 173  
227 +(((
174 174  Set a downstream in TTN and see it is sent
229 +)))
175 175  
176 176  
232 +(((
177 177  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
234 +)))
178 178  
179 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
236 +[[image:image-20220526164650-13.png]]
180 180  
238 +(((
181 181  Gateway Traffic can see this downstream info
240 +)))
182 182  
183 183  
184 -**For LoRaWAN Gateway**
243 +(((
244 +(% style="color:blue" %)**For LoRaWAN Gateway**
245 +)))
185 185  
247 +(((
186 186  When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
249 +)))
187 187  
188 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
251 +[[image:image-20220526164734-14.png]]
189 189  
253 +(((
190 190  Gateway Sent out this packet
255 +)))
191 191  
192 192  
193 -**For End Node**
258 +(((
259 +(% style="color:blue" %)**For End Node**
260 +)))
194 194  
262 +(((
195 195  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
264 +)))
196 196  
197 -(% class="box infomessage" %)
198 198  (((
199 -AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
267 +(% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
268 +(% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
269 +(% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
270 +(% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
271 +
272 +
200 200  )))
201 201  
202 -(% class="box infomessage" %)
203 203  (((
204 -AT+RX2DR=3 ~-~--> The RX2 DataRate
276 +(% style="color:blue" %)**when the device running, we can see below info:**
205 205  )))
206 206  
207 -(% class="box infomessage" %)
279 +{{{ [12502]***** UpLinkCounter= 0 *****
280 + [12503]TX on freq 868500000 Hz at DR 0
281 + [13992]txDone
282 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
283 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
284 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
285 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
286 +
208 208  (((
209 -AT+RX1DL=1000 ~-~--> Receive Delay 1
288 +
210 210  )))
211 211  
212 -(% class="box infomessage" %)
213 213  (((
214 -AT+RX2DL=2000 ~-~--> Receive Delay 2
292 +(% style="color:blue" %)**Another message:**
215 215  )))
216 216  
217 -when the device running, we can see below info:
295 +{{{ [12502]***** UpLinkCounter= 0 *****
296 + [12503]TX on freq 868100000 Hz at DR 0
297 + [13992]txDone
298 + [15022]RX on freq 868100000 Hz at DR 0
299 + [15222]rxTimeOut
300 + [15987]RX on freq 869525000 Hz at DR 3
301 + [16185]rxDone --> We have got the downstream packet.
302 + Rssi= -64
303 + Receive data
304 + 1:0012345678}}}
218 218  
219 -{{{[12502]***** UpLinkCounter= 0 *****
220 -[12503]TX on freq 868500000 Hz at DR 0
221 -[13992]txDone
222 -[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
223 -[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
224 -[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
225 -[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
226 -}}}
227 227  
228 -{{{Another message:
229 -[12502]***** UpLinkCounter= 0 *****
230 -[12503]TX on freq 868100000 Hz at DR 0
231 -[13992]txDone
232 -[15022]RX on freq 868100000 Hz at DR 0
233 -[15222]rxTimeOut
234 -[15987]RX on freq 869525000 Hz at DR 3
235 -[16185]rxDone --> We have got the downstream packet.
236 -Rssi= -64
237 -Receive data
238 -1:0012345678
239 -}}}
307 +== 5.3 If problem doesn't solve ==
240 240  
241 -== 5.3 If problem doesn’t solve ==
242 242  
243 -**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:**
310 +(% 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:**
244 244  
245 245  * End node console to show the transmit freuqency and DR.
246 246  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -247,49 +247,59 @@
247 247  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
248 248  * End Node traffic (from server UI) to shows end node activity in server.
249 249  
317 +
318 +
250 250  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
251 251  
321 +
322 +(((
252 252  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.
324 +)))
253 253  
326 +(((
327 +
328 +)))
329 +
330 +(((
254 254  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:
332 +)))
255 255  
256 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
257 -}}}
334 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
258 258  
336 +(((
337 +
338 +)))
339 +
340 +(((
259 259  In this case, please double check the gateway frequency and the server frequency band.
342 +)))
260 260  
261 261  
262 262  = 7. Decrypt a LoRaWAN Packet =
263 263  
264 -~1. LHT65 End device configure:
265 265  
266 -(% class="box infomessage" %)
267 -(((
268 -Change to ABP Mode: AT+NJM=0
269 -)))
348 +(% style="color:blue" %)**1. LHT65 End device configure:**
270 270  
271 -(% class="box infomessage" %)
272 -(((
273 -Change to fix frequency: AT+CHS=904900000
274 -)))
350 +**Change to ABP Mode:  AT+NJM=0**
351 +**Change to fix frequency:  AT+CHS=904900000**
352 +**Change to fix DR:  AT+DR=0**
275 275  
276 -(% class="box infomessage" %)
277 -(((
278 -Change to fix DR: AT+DR=0
279 -)))
280 280  
281 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
355 +[[image:image-20220526165525-16.png]]
282 282  
283 -2. In LG02 , configure to receive above message
284 284  
285 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
358 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
286 286  
360 +[[image:image-20220526165612-17.png]]
361 +
362 +
287 287  In LG02 console, we can see the hex receive are:
288 288  
289 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
365 +[[image:image-20220526171112-21.png]]
290 290  
291 -3. Decode the info in web
292 292  
368 +(% style="color:blue" %)**3. Decode the info in web**
369 +
293 293  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
294 294  
295 295  Need these three fields:
... ... @@ -300,45 +300,145 @@
300 300  
301 301  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
302 302  
380 +
303 303  [[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]]
304 304  
305 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
383 +[[image:image-20220526171029-20.png]]
306 306  
307 -The FRMPayload is the device payload.
385 +(((
386 + The FRMPayload is the device payload.
387 +)))
308 308  
309 309  
310 310  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
311 311  
392 +
312 312  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.
313 313  
395 +
314 314  = 9. Why do I see a "MIC Mismatch" error message from the server? =
315 315  
316 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
317 317  
399 +(((
400 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
401 +)))
402 +
403 +(((
318 318  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
405 +)))
319 319  
320 -* Please note the distinction between "APPKEY" and "APPSKEY".
407 +* (((
408 +Please note the distinction between "APPKEY" and "APPSKEY".
409 +)))
321 321  
411 +(((
322 322  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
413 +)))
323 323  
415 +(((
324 324  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
417 +)))
325 325  
326 -* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
419 +* (((
420 +If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
327 327  
422 +
423 +
424 +
425 +)))
426 +
328 328  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
329 329  
429 +
330 330  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
331 331  
432 +(((
332 332  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
434 +)))
333 333  
334 -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,
436 +(((
437 +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.
438 +)))
335 335  
336 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
440 +* (((
441 +Solution: Use the decoder to filter out this 00 packet.
442 +)))
443 +* (((
444 +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]]
337 337  
338 -so it will send a normal uplink packet, and an additional 00 data packet.
339 339  
340 -* Solution: Use the decoder to filter out this 00 packet.
341 -* 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
342 342  
343 -(% class="wikigeneratedid" id="H" %)
344 344  
449 +)))
450 +
451 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
452 +
453 +
454 +(((
455 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
456 +)))
457 +
458 +(((
459 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
460 +)))
461 +
462 +(((
463 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
464 +)))
465 +
466 +(((
467 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
468 +)))
469 +
470 +(((
471 +AT+APPEUI=00 00 00 00 00 00 00 00
472 +)))
473 +
474 +(((
475 +
476 +)))
477 +
478 +(((
479 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
480 +)))
481 +
482 +(((
483 +You can rewrites the keys by running commands in AT Console
484 +
485 +
486 +)))
487 +
488 +(((
489 +**For example：**
490 +)))
491 +
492 +(((
493 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
494 +)))
495 +
496 +(((
497 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
498 +)))
499 +
500 +(((
501 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
502 +)))
503 +
504 +(((
505 +AT+APPEUI=2C 45 47 E3 24 12 23 24
506 +)))
507 +
508 +(((
509 +(Any combination of 16 bit codes can be used）
510 +
511 +
512 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
513 +)))
514 +
515 +
516 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
517 +
518 +
519 +
520 +(% class="wikigeneratedid" %)
521 +
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