Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.1 >
edited by Xiaoling
on 2022/05/11 14:26
To version < 22.2 >
edited by Xiaoling
on 2022/05/26 16:48
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,9 @@
1 1  **~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
... ... @@ -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"]]
26 +[[image:image-20220526163523-1.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"]]
36 +[[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"]]
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  
... ... @@ -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"]]
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,37 +60,67 @@
60 60  
61 61  = 2. Notice of US915/CN470/AU915 Frequency band =
62 62  
67 +(((
63 63  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
69 +)))
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 ?
71 +* (((
72 +What **sub-band** the server support ?
73 +)))
74 +* (((
75 +What is the **sub-band** the gateway support ?
76 +)))
77 +* (((
78 +What is the **sub-band** the end node is using ?
79 +)))
68 68  
81 +(((
69 69  All of above should match so End Node can properly Join the server and don't have packet lost.
83 +)))
70 70  
85 +(((
86 +
87 +)))
88 +
89 +(((
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.
91 +)))
72 72  
93 +(((
94 +
95 +)))
96 +
97 +(((
73 73  Here are the freuqency tables for these bands as reference:
99 +)))
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"]]
101 +[[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"]]
105 +[[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"]]
109 +[[image:image-20220526163941-8.png]]
84 84  
111 +(((
85 85  CN470 Channels
113 +)))
86 86  
115 +(((
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.
117 +)))
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"]]
119 +[[image:image-20220526164052-9.png]]
90 90  
121 +(((
91 91  TTN FREQUENCY PLAN
123 +)))
92 92  
125 +(((
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. )
127 +)))
94 94  
95 95  
96 96  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
... ... @@ -101,20 +101,42 @@
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  
138 +(((
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.
140 +)))
105 105  
142 +(((
143 +
144 +)))
145 +
146 +(((
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.
148 +)))
107 107  
108 108  
109 109  = 4. Transmision on ABP Mode =
110 110  
153 +(((
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.
155 +)))
112 112  
157 +(((
158 +
159 +)))
160 +
161 +(((
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.
163 +)))
114 114  
165 +(((
166 +
167 +)))
168 +
169 +(((
115 115  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
171 +)))
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]]
173 +[[image:image-20220526164508-10.png]]
118 118  
119 119  Disable Frame Counter Check in ABP Mode
120 120  
... ... @@ -125,9 +125,11 @@
125 125  
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  
184 +(((
128 128  Depends on Class A or Class C, the receive windows will be a little difference,
186 +)))
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"]]
188 +[[image:image-20220526164547-11.png]]
131 131  
132 132  receive windows for Class A and Class C
133 133  
... ... @@ -139,82 +139,109 @@
139 139  * This packet must match the frequency of the RX1 or RX2 window.
140 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.**
141 141  
200 +
142 142  == 5.2 See Debug Info ==
143 143  
203 +(((
144 144  **For LoRaWAN Server**
205 +)))
145 145  
207 +(((
146 146  We can check if there is downlink message for this end node, use TTN for example:
209 +)))
147 147  
211 +(((
148 148  Configure a downstream to the end device
213 +)))
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"]]
215 +[[image:image-20220526164623-12.png]]
151 151  
217 +(((
152 152  Set a downstream in TTN and see it is sent
219 +)))
153 153  
154 154  
222 +(((
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
224 +)))
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"]]
226 +[[image:image-20220526164650-13.png]]
158 158  
228 +(((
159 159  Gateway Traffic can see this downstream info
230 +)))
160 160  
161 161  
233 +(((
162 162  **For LoRaWAN Gateway**
235 +)))
163 163  
237 +(((
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:
239 +)))
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"]]
241 +[[image:image-20220526164734-14.png]]
167 167  
243 +(((
168 168  Gateway Sent out this packet
245 +)))
169 169  
170 170  
248 +(((
171 171  **For End Node**
250 +)))
172 172  
252 +(((
173 173  we can use AT Command (AT+CFG) to check the RX1 configure and RX2 configure. as below:
254 +)))
174 174  
175 -(% class="box infomessage" %)
176 176  (((
177 -AT+RX2FQ=869525000 ~-~--> The RX2 Window frequency
257 +
178 178  )))
179 179  
260 +(((
180 180  (% class="box infomessage" %)
181 181  (((
182 -AT+RX2DR=3 ~-~--> The RX2 DataRate
263 +AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
264 +AT+RX2DR=3      ~-~--> The RX2 DataRate
265 +AT+RX1DL=1000   ~-~--> Receive Delay 1
266 +AT+RX2DL=2000   ~-~--> Receive Delay 2
183 183  )))
268 +)))
184 184  
185 -(% class="box infomessage" %)
186 186  (((
187 -AT+RX1DL=1000 ~-~--> Receive Delay 1
271 +**when the device running, we can see below info:**
188 188  )))
189 189  
190 -(% class="box infomessage" %)
274 +{{{ [12502]***** UpLinkCounter= 0 *****
275 + [12503]TX on freq 868500000 Hz at DR 0
276 + [13992]txDone
277 + [15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
278 + [15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
279 + [15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
280 + [16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)}}}
281 +
191 191  (((
192 -AT+RX2DL=2000 ~-~--> Receive Delay 2
283 +
193 193  )))
194 194  
195 -when the device running, we can see below info:
286 +(((
287 +**Another message:**
288 +)))
196 196  
197 -{{{[12502]***** UpLinkCounter= 0 *****
198 -[12503]TX on freq 868500000 Hz at DR 0
199 -[13992]txDone
200 -[15022]RX on freq 868500000 Hz at DR 0 --> RX1 window open at frequency: 868500000, DR0, after 15022-13992= 1030ms of txdone
201 -[15222]rxTimeOut --> no packet arrive in RX1 window. (duration: 200ms)
202 -[15987]RX on freq 869525000 Hz at DR 3 --> RX2 window open at frequency: 869525000, DR3, after 15987-13992= 1995ms of txdone
203 -[16027]rxTimeOut --> no packet arrive in RX2 window. (duration: 40 ms)
204 -}}}
290 +{{{ [12502]***** UpLinkCounter= 0 *****
291 + [12503]TX on freq 868100000 Hz at DR 0
292 + [13992]txDone
293 + [15022]RX on freq 868100000 Hz at DR 0
294 + [15222]rxTimeOut
295 + [15987]RX on freq 869525000 Hz at DR 3
296 + [16185]rxDone --> We have got the downstream packet.
297 + Rssi= -64
298 + Receive data
299 + 1:0012345678}}}
205 205  
206 -{{{Another message:
207 -[12502]***** UpLinkCounter= 0 *****
208 -[12503]TX on freq 868100000 Hz at DR 0
209 -[13992]txDone
210 -[15022]RX on freq 868100000 Hz at DR 0
211 -[15222]rxTimeOut
212 -[15987]RX on freq 869525000 Hz at DR 3
213 -[16185]rxDone --> We have got the downstream packet.
214 -Rssi= -64
215 -Receive data
216 -1:0012345678
217 -}}}
301 +(% class="wikigeneratedid" %)
302 +​​​​​​​
218 218  
219 219  == 5.3 If problem doesn’t solve ==
220 220  
... ... @@ -227,14 +227,27 @@
227 227  
228 228  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
229 229  
315 +(((
230 230  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.
317 +)))
231 231  
319 +(((
320 +
321 +)))
322 +
323 +(((
232 232  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:
325 +)))
233 233  
234 -{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)
235 -}}}
327 +{{{Sat Nov 21 08:04:17 2020 daemon.info lora_pkt_fwd[1680]: ERROR~ Packet REJECTED, unsupported frequency - 923200000 (min:865000000,max:867000000)}}}
236 236  
329 +(((
330 +
331 +)))
332 +
333 +(((
237 237  In this case, please double check the gateway frequency and the server frequency band.
335 +)))
238 238  
239 239  
240 240  = 7. Decrypt a LoRaWAN Packet =
... ... @@ -282,7 +282,9 @@
282 282  
283 283  [[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
284 284  
285 -The FRMPayload is the device payload.
383 +(((
384 + The FRMPayload is the device payload.
385 +)))
286 286  
287 287  
288 288  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
... ... @@ -291,32 +291,83 @@
291 291  
292 292  = 9. Why do I see a "MIC Mismatch" error message from the server? =
293 293  
394 +(((
294 294  1)If the user receives a "MIC Mismatch" message after registering the node on the server.
396 +)))
295 295  
398 +(((
296 296  It is likely that the user filled in the wrong APPKEY when registering the node. Many users fill in "APPSKEY".
400 +)))
297 297  
298 -* Please note the distinction between "APPKEY" and "APPSKEY".
402 +* (((
403 +Please note the distinction between "APPKEY" and "APPSKEY".
404 +)))
299 299  
406 +(((
300 300  2）If the node works on the server for a period of time, the device stops working and receives a "MIC Mismatch" message.
408 +)))
301 301  
410 +(((
302 302  The user needs a USB-TTL adapter to connect the serial port to modify the node APPKEY.
412 +)))
303 303  
304 -* If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
414 +* (((
415 +If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
305 305  
417 +
418 +)))
419 +
306 306  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
307 307  
308 308  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
309 309  
424 +(((
310 310  When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
426 +)))
311 311  
312 -When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,
428 +(((
429 +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.
430 +)))
313 313  
314 -and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
432 +* (((
433 +Solution: Use the decoder to filter out this 00 packet.
434 +)))
435 +* (((
436 +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]]
315 315  
316 -so it will send a normal uplink packet, and an additional 00 data packet.
317 317  
318 -* Solution: Use the decoder to filter out this 00 packet.
319 -* Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
439 +
440 +)))
320 320  
321 -(% class="wikigeneratedid" id="H" %)
442 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 +
444 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
445 +
446 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 +
448 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449 +
450 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
451 +
452 +AT+APPEUI=00 00 00 00 00 00 00 00
453 +
454 +
455 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
456 +
457 +You can rewrites the keys by running commands in AT Console
458 +
459 +For example：
460 +
461 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
462 +
463 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
464 +
465 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
466 +
467 +AT+APPEUI=2C 45 47 E3 24 12 23 24
468 +
469 +(Any combination of 16 bit codes can be used）
470 +
471 +
472 +(% class="wikigeneratedid" %)
322 322  
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

Applications

Navigation

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