Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 2.1
edited by Xiaoling
on 2022/05/11 14:19
Change comment: There is no comment for this version
To version 32.13
edited by Xiaoling
on 2022/07/13 15:21
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -
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,41 +60,78 @@
60 60  
61 61  = 2. Notice of US915/CN470/AU915 Frequency band =
62 62  
65 +
66 +(((
63 63  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
68 +)))
64 64  
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 ?
70 +* (((
71 +What **sub-band** the server support ?
72 +)))
73 +* (((
74 +What is the **sub-band** the gateway support ?
75 +)))
76 +* (((
77 +What is the **sub-band** the end node is using ?
78 +)))
68 68  
80 +(((
69 69  All of above should match so End Node can properly Join the server and don't have packet lost.
82 +)))
70 70  
84 +(((
85 +
86 +)))
87 +
88 +(((
71 71  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.
90 +)))
72 72  
92 +(((
93 +
94 +)))
95 +
96 +(((
73 73  Here are the freuqency tables for these bands as reference:
98 +)))
74 74  
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"]]
100 +[[image:image-20220526163801-6.png]]
76 76  
77 77  US915 Channels
78 78  
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"]]
104 +[[image:image-20220526163926-7.png]]
80 80  
81 81  AU915 Channels
82 82  
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"]]
84 84  
109 +[[image:image-20220526163941-8.png]]
110 +
111 +(((
85 85  CN470 Channels
86 86  
114 +
115 +)))
116 +
117 +(((
87 87  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.
119 +)))
88 88  
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"]]
121 +[[image:image-20220526164052-9.png]]
90 90  
123 +(((
91 91  TTN FREQUENCY PLAN
92 92  
126 +
127 +)))
128 +
129 +(((
93 93  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. )
131 +)))
94 94  
95 95  
96 96  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
97 97  
136 +
98 98  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:
99 99  
100 100  * **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.
... ... @@ -101,20 +101,43 @@
101 101  * **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
102 102  * **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.
103 103  
143 +(((
104 104  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.
145 +)))
105 105  
147 +(((
148 +
149 +)))
150 +
151 +(((
106 106  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.
153 +)))
107 107  
108 108  
109 109  = 4. Transmision on ABP Mode =
110 110  
158 +
159 +(((
111 111  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.
161 +)))
112 112  
163 +(((
164 +
165 +)))
166 +
167 +(((
113 113  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.
169 +)))
114 114  
171 +(((
172 +
173 +)))
174 +
175 +(((
115 115  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
177 +)))
116 116  
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]]
179 +[[image:image-20220526164508-10.png]]
118 118  
119 119  Disable Frame Counter Check in ABP Mode
120 120  
... ... @@ -123,14 +123,18 @@
123 123  
124 124  == 5.1 How it work ==
125 125  
188 +
126 126  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.
127 127  
191 +(((
128 128  Depends on Class A or Class C, the receive windows will be a little difference,
193 +)))
129 129  
130 -[[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]]
131 131  
132 132  receive windows for Class A and Class C
133 133  
199 +
134 134  Below are the requirement for the End Device to receive the packets.
135 135  
136 136  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -137,80 +137,110 @@
137 137  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
138 138  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
139 139  * This packet must match the frequency of the RX1 or RX2 window.
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.**
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.**
141 141  
142 142  == 5.2 See Debug Info ==
143 143  
144 -**For LoRaWAN Server**
145 145  
211 +(((
212 +(% style="color:blue" %)**For LoRaWAN Server**
213 +)))
214 +
215 +(((
146 146  We can check if there is downlink message for this end node, use TTN for example:
217 +)))
147 147  
219 +(((
148 148  Configure a downstream to the end device
221 +)))
149 149  
150 -[[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]]
151 151  
225 +(((
152 152  Set a downstream in TTN and see it is sent
227 +)))
153 153  
154 154  
230 +(((
155 155  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
232 +)))
156 156  
157 -[[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]]
158 158  
236 +(((
159 159  Gateway Traffic can see this downstream info
238 +)))
160 160  
161 161  
162 -**For LoRaWAN Gateway**
241 +(((
242 +(% style="color:blue" %)**For LoRaWAN Gateway**
243 +)))
163 163  
245 +(((
164 164  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:
247 +)))
165 165  
166 -[[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]]
167 167  
251 +(((
168 168  Gateway Sent out this packet
253 +)))
169 169  
170 170  
171 -**For End Node**
256 +(((
257 +(% style="color:blue" %)**For End Node**
258 +)))
172 172  
260 +(((
173 173  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
262 +)))
174 174  
175 175  (((
176 -{{info}}
177 -{{{AT+RX2FQ=869525000 ---> The RX2 Window frequency
178 -AT+RX2DR=3 ---> The RX2 DataRate
179 -AT+RX1DL=1000 ---> Receive Delay 1
180 -AT+RX2DL=2000 ---> Receive Delay 2}}}
181 -{{/info}}
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
182 182  
183 183  
184 184  )))
185 185  
186 -when the device running, we can see below info:
273 +(((
274 +(% style="color:blue" %)**when the device running, we can see below info:**
275 +)))
187 187  
188 -{{{[12502]***** UpLinkCounter= 0 *****
189 -[12503]TX on freq 868500000 Hz at DR 0
190 -[13992]txDone
191 -[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
192 -[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
193 -[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
194 -[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
195 -}}}
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)}}}
196 196  
197 -{{{Another message:
198 -[12502]***** UpLinkCounter= 0 *****
199 -[12503]TX on freq 868100000 Hz at DR 0
200 -[13992]txDone
201 -[15022]RX on freq 868100000 Hz at DR 0
202 -[15222]rxTimeOut
203 -[15987]RX on freq 869525000 Hz at DR 3
204 -[16185]rxDone --> We have got the downstream packet.
205 -Rssi= -64
206 -Receive data
207 -1:0012345678
208 -}}}
285 +(((
286 +
287 +)))
209 209  
210 -== 5.3 If problem doesn’t solve ==
289 +(((
290 +(% style="color:blue" %)**Another message:**
291 +)))
211 211  
212 -**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:**
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}}}
213 213  
304 +
305 +== 5.3 If problem doesn't solve ==
306 +
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 +
214 214  * End node console to show the transmit freuqency and DR.
215 215  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
216 216  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
... ... @@ -217,49 +217,59 @@
217 217  * End Node traffic (from server UI) to shows end node activity in server.
218 218  
219 219  
316 +
317 +
220 220  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
221 221  
320 +
321 +(((
222 222  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 +)))
223 223  
325 +(((
326 +
327 +)))
328 +
329 +(((
224 224  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:
331 +)))
225 225  
226 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
227 -}}}
333 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
228 228  
335 +(((
336 +
337 +)))
338 +
339 +(((
229 229  In this case, please double check the gateway frequency and the server frequency band.
341 +)))
230 230  
231 231  
232 232  = 7. Decrypt a LoRaWAN Packet =
233 233  
234 -~1. LHT65 End device configure:
235 235  
236 -(% class="box infomessage" %)
237 -(((
238 -Change to ABP Mode: AT+NJM=0
239 -)))
347 +(% style="color:blue" %)**1. LHT65 End device configure:**
240 240  
241 -(% class="box infomessage" %)
242 -(((
243 -Change to fix frequency: AT+CHS=904900000
244 -)))
349 +**Change to ABP Mode:  AT+NJM=0**
350 +**Change to fix frequency:  AT+CHS=904900000**
351 +**Change to fix DR:  AT+DR=0**
245 245  
246 -(% class="box infomessage" %)
247 -(((
248 -Change to fix DR: AT+DR=0
249 -)))
250 250  
251 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
354 +[[image:image-20220526165525-16.png]]
252 252  
253 -2. In LG02 , configure to receive above message
254 254  
255 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
357 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
256 256  
359 +[[image:image-20220526165612-17.png]]
360 +
361 +
257 257  In LG02 console, we can see the hex receive are:
258 258  
259 -[[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]]
260 260  
261 -3. Decode the info in web
262 262  
367 +(% style="color:blue" %)**3. Decode the info in web**
368 +
263 263  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
264 264  
265 265  Need these three fields:
... ... @@ -270,44 +270,145 @@
270 270  
271 271  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
272 272  
379 +
273 273  [[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]]
274 274  
275 -[[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]]
276 276  
277 -The FRMPayload is the device payload.
384 +(((
385 + The FRMPayload is the device payload.
386 +)))
278 278  
279 279  
280 280  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
281 281  
391 +
282 282  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.
283 283  
394 +
284 284  = 9. Why do I see a "MIC Mismatch" error message from the server? =
285 285  
286 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
287 287  
398 +(((
399 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
400 +)))
401 +
402 +(((
288 288  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
404 +)))
289 289  
290 -* Please note the distinction between "APPKEY" and "APPSKEY".
406 +* (((
407 +Please note the distinction between "APPKEY" and "APPSKEY".
408 +)))
291 291  
410 +(((
292 292  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
412 +)))
293 293  
414 +(((
294 294  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
416 +)))
295 295  
296 -* 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.
297 297  
421 +
422 +
423 +
424 +)))
425 +
298 298  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
299 299  
428 +
300 300  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
301 301  
431 +(((
302 302  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
433 +)))
303 303  
304 -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 +)))
305 305  
306 -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]]
307 307  
308 -so it will send a normal uplink packet, and an additional 00 data packet.
309 309  
310 -* Solution: Use the decoder to filter out this 00 packet.
311 -* 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
312 312  
313 -== ==
447 +
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