<
From version < 130.1 >
edited by Xiaoling
on 2024/09/14 10:55
To version < 125.1 >
edited by Mengting Qiu
on 2024/09/03 10:42
>
Change comment: Uploaded new attachment "image-20240903104250-9.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -8,7 +8,6 @@
8 8  
9 9  = 1. The use of this guideline =
10 10  
11 -
12 12  This configure instruction is for Dragino NB-IoT models with -CB or -CS suffix, for example DDS75-CB. These models use the same NB-IoT Module **[[BG95-M2>>https://www.dropbox.com/sh/3ilyaswz4odgaru/AADR86cAgL9UGlmLuEH-UZgla?st=x1ry6v5j&dl=0]]** and has the same software structure. The have the same configure instruction to different IoT servers. Use can follow the instruction here to see how to configure to connect to those servers.
13 13  
14 14  
... ... @@ -16,7 +16,6 @@
16 16  
17 17  == 2.1 General Configure to attach network ==
18 18  
19 -
20 20  To attache end nodes to NB-IoT or LTE-M Network, You need to:
21 21  
22 22  1. Get a NB-IoT or LTE-M SIM card from Service Provider. (Not the same as the SIM card we use in mobile phone)
... ... @@ -28,7 +28,7 @@
28 28  [[image:image-20240602220856-1.png]]
29 29  
30 30  
31 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230808205045-1.png?width=438&height=293&rev=1.1||alt="image-20230808205045-1.png"]]
29 +放一张如何插卡图片。
32 32  
33 33  
34 34  After doing above, the end nodes should be able to attach to NB-IoT network .
... ... @@ -55,7 +55,6 @@
55 55  
56 56  == 2.2 Speed Up Network Attach time ==
57 57  
58 -
59 59  **BG95-M2** supports multi bands (% style="color:blue" %)**in NB-IoT and LTE-M. **(%%) It will search one by one and try to attach, this will take a lot of time and even cause attach fail and show **Signal Strenght:99**.
60 60  
61 61  **Note:**Before using the NB module command, users need to power on the NB module. Run the AT+QSW command to turn on and off the NB module.Remember to shut down after using the NB module command, otherwise it will consume power.
... ... @@ -74,7 +74,7 @@
74 74  
75 75  See bands used for different provider:** [[NB-IoT Deployment , Bands, Operator list>>http://wiki.dragino.com/xwiki/bin/view/Main/NB-IoT%20Deployment%20%2C%20Bands%2C%20Operator%20list/]]**
76 76  
77 -=== **1. Configure Frequency Band** ===
74 +=== **1.Configure Frequency Band** ===
78 78  
79 79  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
80 80  
... ... @@ -144,7 +144,7 @@
144 144  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
145 145  
146 146  
147 -=== **2. Configure search network sequence** ===
144 +=== **2.Configure search network sequence** ===
148 148  
149 149  AT+QCFG="nwscanseq",<scanseq>,1
150 150  
... ... @@ -157,9 +157,8 @@
157 157  
158 158  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
159 159  
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
160 160  
161 -=== **3. Configure Network Category to be Searched for under LTE RAT** ===
162 -
163 163  AT+QCFG="iotopmode",mode,1
164 164  
165 165  0 eMTC 
... ... @@ -166,9 +166,8 @@
166 166  1 NB-IoT 
167 167  2 eMTC and NB-IoT
168 168  
165 +=== **4.AT command to set frequency band and network category** ===
169 169  
170 -=== **4. AT command to set frequency band and network category** ===
171 -
172 172  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
173 173  
174 174  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -190,23 +190,18 @@
190 190  
191 191  == 3.1 General UDP Connection ==
192 192  
193 -
194 194  The NB-IoT Sensor can send packet to server use UDP protocol.
195 195  
196 -
197 197  === 3.1.1 Simulate UDP Connection by PC tool ===
198 198  
199 -
200 200  We can use PC tool to simulate UDP connection to make sure server works ok.
201 201  
202 -[[image:http://wiki.dragino.com/xwiki/bin/download/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/WebHome/image-20230802112413-1.png?width=1024&height=468&rev=1.1||alt="image-20230802112413-1.png"]]
194 +[[image:image-20230802112413-1.png||height="468" width="1024"]]
203 203  
204 -
205 205  === 3.1.2 Configure NB-IoT Sensor ===
206 206  
207 207  ==== 3.1.2.1 AT Commands ====
208 208  
209 -
210 210  (% style="color:blue" %)**AT Commands:**
211 211  
212 212  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
... ... @@ -215,16 +215,12 @@
215 215  
216 216  [[image:image-20240819102802-1.png]]
217 217  
218 -
219 219  ==== 3.1.2.2 Uplink Example ====
220 220  
210 +[[image:image-20240819105418-8.png||height="671" width="1414"]]
221 221  
222 -[[image:image-20240819105418-8.png||height="611" width="1287"]]
223 -
224 -
225 225  == 3.2 General COAP Connection ==
226 226  
227 -
228 228  The NB-IoT Sensor can send packet to server use COAP protocol.
229 229  
230 230  Below are the commands.
... ... @@ -240,16 +240,13 @@
240 240  
241 241  [[image:image-20240819103212-2.png]]
242 242  
243 -
244 244  === 3.2.1 Uplink Example ===
245 245  
246 -
247 247  [[image:image-20240819103909-4.png||height="453" width="955"]]
248 248  
249 249  
250 250  == 3.2 General MQTT Connection ==
251 251  
252 -
253 253  The NB-IoT Sensor can send packet to server use MQTT protocol.
254 254  
255 255  Below are the commands.
... ... @@ -277,12 +277,10 @@
277 277  
278 278  (% style="color:red" %)**Notice: MQTT protocol has a much higher power consumption compare with UDP/CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.**
279 279  
280 -
281 281  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
282 282  
283 283  === 3.3.1 Get MQTT Credentials ===
284 284  
285 -
286 286  [[ThingSpeak>>url:https://thingspeak.com/]] connection uses MQTT Connection. So we need to get MQTT Credentials first. You need to point MQTT Devices to ThingSpeak Channel as well.
287 287  
288 288  [[image:image-20240819173602-1.png||height="401" width="743"]]
... ... @@ -289,12 +289,10 @@
289 289  
290 290  [[image:image-20240819173706-3.png||height="595" width="597"]]
291 291  
292 -
293 293  === 3.3.2 Simulate with MQTT.fx ===
294 294  
295 295  ==== 3.3.2.1 Establish MQTT Connection ====
296 296  
297 -
298 298  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
299 299  
300 300  [[image:image-20240819173826-4.png||height="534" width="734"]]
... ... @@ -309,10 +309,8 @@
309 309  
310 310  * (% style="color:#037691" %)**Password:**(%%) <Your ThingSpeak MQTT Password>
311 311  
312 -
313 313  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
314 314  
315 -
316 316  [[image:image-20240819174033-5.png]]
317 317  
318 318  [[image:image-20240819174209-6.png]]
... ... @@ -329,12 +329,10 @@
329 329  
330 330  [[image:image-20240819174314-7.png||height="469" width="785"]]
331 331  
332 -
333 333  === 3.3.3 Configure NB-IoT Sensor for connection ===
334 334  
335 335  ==== 3.3.3.1 AT Commands: ====
336 336  
337 -
338 338  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
339 339  
340 340  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -349,10 +349,8 @@
349 349  
350 350  * (% style="color:blue" %)**AT+SUBTOPIC=<YOUR_CHANNEL_ID>**
351 351  
352 -
353 353  ==== 3.3.3.2 Uplink Examples ====
354 354  
355 -
356 356  [[image:image-20240819174540-8.png]]
357 357  
358 358  For SE01-NB
... ... @@ -377,10 +377,8 @@
377 377  
378 378  For SN50V3-NB
379 379  
380 -
381 381  ==== 3.3.3.3 Map fields to sensor value ====
382 382  
383 -
384 384  When NB-IoT sensor upload to ThingSpeak. The payload already specify which fileds related to which sensor value. Use need to create fileds in Channels Settings. with name so to see the value correctly.
385 385  
386 386  [[image:image-20240819174610-9.png]]
... ... @@ -389,25 +389,25 @@
389 389  
390 390  Below is the NB-IoT Product Table show the mapping.
391 391  
392 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
393 -|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:139px" %)Field4|(% style="background-color:#4f81bd; color:white; width:141px" %)Field5|(% style="background-color:#4f81bd; color:white; width:142px" %)Field6|(% style="background-color:#4f81bd; color:white; width:151px" %)Field7|(% style="background-color:#4f81bd; color:white; width:137px" %)Field8|(% style="background-color:#4f81bd; color:white; width:69px" %)Field9|(% style="background-color:#4f81bd; color:white; width:65px" %)Field10
394 -|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
395 -|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:139px" %)dielectric_constant|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
396 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
397 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
398 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
399 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:139px" %) |(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
400 -|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
401 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
402 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:139px" %)RSSI|(% style="width:141px" %) |(% style="width:142px" %) |(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
403 -|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:139px" %)calc flag|(% style="width:141px" %)Battery|(% style="width:142px" %)RSSI|(% style="width:151px" %) |(% style="width:137px" %) |(% style="width:69px" %) |(% style="width:65px" %)
404 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:139px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:141px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:142px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:137px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:69px" %)Battery|(% colspan="1" rowspan="1" style="width:65px" %)RSSI
405 -|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:142px" %)adc0|(% colspan="1" rowspan="1" style="width:151px" %)Temperature |(% colspan="1" rowspan="1" style="width:137px" %)Humidity|(% colspan="1" rowspan="1" style="width:69px" %) |(% colspan="1" rowspan="1" style="width:65px" %)
406 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc0|(% colspan="1" style="width:151px" %)distance|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
407 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)adc0|(% colspan="1" style="width:141px" %)exit_state/input PA4|(% colspan="1" style="width:142px" %)adc1|(% colspan="1" style="width:151px" %)Temperature|(% colspan="1" style="width:137px" %)Humidity|(% colspan="1" style="width:69px" %)adc4|(% colspan="1" style="width:65px" %)
408 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)DS18B20 Temp2|(% colspan="1" style="width:137px" %)DS18B20 Temp3|(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
409 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)DS18B20 Temp|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:142px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)Weight|(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
410 -|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:139px" %)count|(% colspan="1" style="width:141px" %) |(% colspan="1" style="width:142px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:137px" %) |(% colspan="1" style="width:69px" %) |(% colspan="1" style="width:65px" %)
363 +(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1424px" %)
364 +|(% style="background-color:#4f81bd; width:143px" %) |(% style="background-color:#4f81bd; color:white; width:103px" %)Field1|(% style="background-color:#4f81bd; color:white; width:102px" %)Field2|(% style="background-color:#4f81bd; color:white; width:157px" %)Field3|(% style="background-color:#4f81bd; color:white; width:154px" %)Field4|(% style="background-color:#4f81bd; color:white; width:153px" %)Field5|(% style="background-color:#4f81bd; color:white; width:151px" %)Field6|(% style="background-color:#4f81bd; color:white; width:160px" %)Field7|(% style="background-color:#4f81bd; color:white; width:152px" %)Field8|(% style="background-color:#4f81bd; color:white; width:67px" %)Field9|(% style="background-color:#4f81bd; color:white; width:69px" %)Field10
365 +|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
366 +|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:157px" %)conduct|(% style="width:154px" %)dielectric_constant|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
367 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
368 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
369 +|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
370 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:157px" %)RSSI|(% style="width:154px" %) |(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
371 +|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
372 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
373 +|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:157px" %)Battery|(% style="width:154px" %)RSSI|(% style="width:153px" %) |(% style="width:151px" %) |(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
374 +|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:157px" %)door open duration|(% style="width:154px" %)calc flag|(% style="width:153px" %)Battery|(% style="width:151px" %)RSSI|(% style="width:160px" %) |(% style="width:152px" %) |(% style="width:67px" %) |(% style="width:69px" %)
375 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)DS03A-NB|(% colspan="1" rowspan="1" style="width:103px" %)level|(% colspan="1" rowspan="1" style="width:102px" %)alarm|(% colspan="1" rowspan="1" style="width:157px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:154px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:153px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:151px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:160px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:152px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:67px" %)Battery|(% colspan="1" rowspan="1" style="width:69px" %)RSSI
376 +|(% colspan="1" rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod1|(% colspan="1" rowspan="1" style="width:103px" %)mod|(% colspan="1" rowspan="1" style="width:102px" %)Battery|(% colspan="1" rowspan="1" style="width:157px" %)RSSI|(% colspan="1" rowspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:151px" %)adc0|(% colspan="1" rowspan="1" style="width:160px" %)Temperature |(% colspan="1" rowspan="1" style="width:152px" %)Humidity|(% colspan="1" rowspan="1" style="width:67px" %) |(% colspan="1" rowspan="1" style="width:69px" %)
377 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod2|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc0|(% colspan="1" style="width:160px" %)distance|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
378 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod3|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)adc0|(% colspan="1" style="width:153px" %)exit_state/input PA4|(% colspan="1" style="width:151px" %)adc1|(% colspan="1" style="width:160px" %)Temperature|(% colspan="1" style="width:152px" %)Humidity|(% colspan="1" style="width:67px" %)adc4|(% colspan="1" style="width:69px" %)
379 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod4|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)DS18B20 Temp2|(% colspan="1" style="width:152px" %)DS18B20 Temp3|(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
380 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod5|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)DS18B20 Temp|(% colspan="1" style="width:153px" %)adc0|(% colspan="1" style="width:151px" %)exit_state/input PA4|(% colspan="1" style="width:160px" %)Weight|(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
381 +|(% colspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SN50V3-NB mod6|(% colspan="1" style="width:103px" %)mod|(% colspan="1" style="width:102px" %)Battery|(% colspan="1" style="width:157px" %)RSSI|(% colspan="1" style="width:154px" %)count|(% colspan="1" style="width:153px" %) |(% colspan="1" style="width:151px" %) |(% colspan="1" style="width:160px" %) |(% colspan="1" style="width:152px" %) |(% colspan="1" style="width:67px" %) |(% colspan="1" style="width:69px" %)
411 411  
412 412  == 3.4 [[Datacake>>https://datacake.co/]] ==
413 413  
... ... @@ -421,12 +421,10 @@
421 421  
422 422  * (% style="color:blue" %)**S31B-CB-GE**(%%): This verson doesn't have pre-configure Datacake connection. User need to enter the AT Commands to connect to Datacake. See below for instruction.
423 423  
424 -
425 425  === 3.4.1 For device Already has template ===
426 426  
427 427  ==== 3.4.1.1 Create Device ====
428 428  
429 -
430 430  (% style="color:blue" %)**Add Device**(%%) in DataCake.
431 431  
432 432  [[image:image-20240820110003-1.png]]
... ... @@ -445,12 +445,10 @@
445 445  
446 446  [[image:image-20240820110114-6.png]]
447 447  
448 -
449 449  === 3.4.2 For Device already registered in DataCake before shipped ===
450 450  
451 451  ==== 3.4.2.1 Scan QR Code to get the device info ====
452 452  
453 -
454 454  Users can use their phones or computers to scan QR codes to obtain device data information.
455 455  
456 456  [[image:image-20240820110129-7.png]]
... ... @@ -457,40 +457,32 @@
457 457  
458 458  [[image:image-20240820110218-9.png]]
459 459  
460 -
461 461  ==== 3.4.2.2 Claim Device to User Account ====
462 462  
463 463  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
464 464  
465 -
466 466  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
467 467  
468 -
469 469  **Step1: Add a device**
470 470  
471 471  [[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
472 472  
473 -
474 474  **Step2: Choose your device type,please select dragino NB-IOT device**
475 475  
476 476  [[image:image-20240820110247-11.png]]
477 477  
478 -
479 479  **Step3: Choose to create a new device**
480 480  
481 481  [[image:image-20240820111016-12.png]]
482 482  
483 -
484 484  **Step4: Fill in the device ID of your NB device**
485 485  
486 486  [[image:image-20240820111101-13.png]]
487 487  
488 -
489 489  **Step5: Please select your device plan according to your needs and complete the creation of the device**
490 490  
491 491  [[image:image-20240820111113-14.png]]
492 492  
493 -
494 494  **Step6: Please add the decoder at the payload decoder of the device configuration.**
495 495  
496 496  **Decoder location:**[[dragino-end-node-decoder/Datacake-Dragino_NB at main · dragino/dragino-end-node-decoder (github.com)>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/Datacake-Dragino_NB]]
... ... @@ -499,12 +499,10 @@
499 499  
500 500  [[image:image-20240820111248-16.png]]
501 501  
502 -
503 503  **Step7: Add the output of the decoder as a field**
504 504  
505 505  [[image:image-20240820111259-17.png]]
506 506  
507 -
508 508  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
509 509  
510 510  [[image:image-20240820111312-18.png]]
... ... @@ -513,10 +513,8 @@
513 513  
514 514  [[image:image-20240820111333-20.png]]
515 515  
516 -
517 517  === 3.4.4 For device have not configured to connect to DataCake ===
518 518  
519 -
520 520  (% class="lead" %)
521 521  Use AT command for connecting to DataCake
522 522  
... ... @@ -524,12 +524,10 @@
524 524  
525 525  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
526 526  
527 -
528 528  == 3.5 Node-Red (via MQTT) ==
529 529  
530 530  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
531 531  
532 -
533 533  Take S31-NB UDP protocol as an example.
534 534  
535 535  Dragino provides input flow examples for the sensors.
... ... @@ -560,10 +560,8 @@
560 560  
561 561  [[image:image-20240820111448-26.png]]
562 562  
563 -
564 564  === 3.5.2 Simulate Connection ===
565 565  
566 -
567 567  We have completed the configuration of UDP. We can try sending packets to node red.
568 568  
569 569  [[image:image-20240820111504-27.png]]
... ... @@ -570,10 +570,8 @@
570 570  
571 571  [[image:image-20240820111515-28.png]]
572 572  
573 -
574 574  === 3.5.3 Configure NB-IoT Sensors ===
575 575  
576 -
577 577  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
578 578  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
579 579  * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
... ... @@ -581,7 +581,6 @@
581 581  * (% style="color:#037691" %)**AT+UNAME=<device name> or User Defined**
582 582  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
583 583  
584 -
585 585  == 3.6 ThingsBoard.Cloud (via MQTT) ==
586 586  
587 587  === 3.6.1 Configure ThingsBoard ===
... ... @@ -588,15 +588,12 @@
588 588  
589 589  ==== 3.6.1.1 Create Device ====
590 590  
591 -
592 592  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
593 593  
594 594  [[image:image-20240820112210-29.png]]
595 595  
596 -
597 597  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
598 598  
599 -
600 600  (% style="color:blue" %)**Uplink Converter**
601 601  
602 602  The purpose of the decoder function is to parse the incoming data and metadata to a format that ThingsBoard can consume. deviceName and deviceType are required, while attributes and telemetry are optional. Attributes and telemetry are flat key-value objects. Nested objects are not supported.
... ... @@ -613,10 +613,8 @@
613 613  
614 614  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
615 615  
616 -
617 617  ==== 3.6.1.3 MQTT Integration Setup ====
618 618  
619 -
620 620  Go to the (% style="color:blue" %)**Integrations center**(%%) **->** (% style="color:blue" %)**Integrations page**(%%) and click **“(% style="color:blue" %)plus(%%)”** icon to add a new integration. Name it (% style="color:blue" %)**“MQTT Integration”**(%%), select type (% style="color:blue" %)**MQTT**;
621 621  
622 622  [[image:image-20240820112247-32.png]]
... ... @@ -635,7 +635,6 @@
635 635  
636 636  [[image:image-20240820112330-35.png]]
637 637  
638 -
639 639  === 3.6.2 Simulate with MQTT.fx ===
640 640  
641 641  [[image:image-20240820112340-36.png]]
... ... @@ -642,10 +642,8 @@
642 642  
643 643  [[image:image-20240820112351-37.png]]
644 644  
645 -
646 646  === 3.6.3 Configure NB-IoT Sensor ===
647 647  
648 -
649 649  (% style="color:blue" %)**AT Commands**
650 650  
651 651  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -668,12 +668,10 @@
668 668  
669 669  [[image:image-20240820112426-40.png]]
670 670  
671 -
672 672  == 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
673 673  
674 674  === 3.7.1 Create device & Get Credentials ===
675 675  
676 -
677 677  We use MQTT Connection to send data to [[Tago.io>>url:https://admin.tago.io/]]. We need to Create Device and Get MQTT Credentials first.
678 678  
679 679  [[image:image-20240820112516-41.png]]
... ... @@ -720,10 +720,8 @@
720 720  
721 721  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
722 722  
723 -
724 724  === 3.7.2 Simulate with MQTT.fx ===
725 725  
726 -
727 727  [[image:image-20240820112552-44.png]]
728 728  
729 729  [[image:image-20240820112604-45.png]]
... ... @@ -734,18 +734,14 @@
734 734  
735 735  [[image:image-20240820112626-47.png]]
736 736  
737 -
738 738  === 3.7.3 tago data ===
739 739  
740 -
741 741  [[image:image-20240820112637-48.png]]
742 742  
743 743  [[image:image-20240820112647-49.png]]
744 744  
745 -
746 746  == 3.8 TCP Connection ==
747 747  
748 -
749 749  (% style="color:blue" %)**AT command:**
750 750  
751 751  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
... ... @@ -762,18 +762,16 @@
762 762  
763 763  [[image:image-20240820112716-51.png]]
764 764  
765 -
766 766  == 3.9 AWS Connection ==
767 767  
768 -
769 769  Users can refer to [[Dragino NB device connection to AWS platform instructions>>http://wiki.dragino.com/xwiki/bin/view/Dragino%20NB%20device%20connection%20to%20AWS%20platform%20instructions/#H1.LogintotheplatformandfindIoTcore]]
770 770  
701 += =
771 771  
772 772  = 4. COAP/UDP/MQTT/TCP downlink =
773 773  
774 774  == 4.1 MQTT (via MQTT.fx) ==
775 775  
776 -
777 777  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
778 778  
779 779  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -796,12 +796,10 @@
796 796  
797 797  [[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
798 798  
799 -
800 800  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
801 801  
802 802  [[image:image-20240820112813-54.png]]
803 803  
804 -
805 805  **3. **The downlink command can be successfully sent only when the downlink port is open.
806 806  
807 807   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -817,7 +817,6 @@
817 817  
818 818  == 4.2 UDP (via Thingseye) ==
819 819  
820 -
821 821  (% style="color:red" %)**Note:**(%%) The UDP service on the ThingsEye platform needs to be built by the user. (Description Link:[[UDP service building instructions>>http://www.ithingsboard.com/docs/user-guide/integrations/udp/]])
822 822  
823 823  After the node is successfully connected to the platform, you need to select the corresponding node (you can refer to the node's IMEI to find it)
... ... @@ -847,30 +847,26 @@
847 847  
848 848  = 5. GPS positioning function =
849 849  
850 -== 1. Turn on GPS function ==
777 +=== 1. Turn on GPS function ===
851 851  
852 -
853 853  (% class="wikigeneratedid" %)
854 -AT+GPS=1 or 0  ~/~/ GPS function on or off
780 +AT+GPS=1 or 0  ~/~/GPS function on or off
855 855  
856 856  
857 -== 2. Extend the time to turn on GNSS ==
783 +=== 2.Extend the time to turn on GNSS ===
858 858  
785 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
859 859  
860 -AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
861 861  
788 +=== 3.Get or set GPS positioning interval in units of hour ===
862 862  
863 -== 3. Get or set GPS positioning interval in units of hour ==
790 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
864 864  
865 865  
866 -AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
793 += 5. FAQ =
867 867  
795 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
868 868  
869 -= 6. FAQ =
870 -
871 -== 6.1 What is the usage of Multi Sampling and One Uplink? ==
872 -
873 -
874 874  The NB series has the feature for Multi Sampling and one uplink. See one of them
875 875  
876 876  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SN50v3-NB_BN-IoT_Sensor_Node_User_Manual/#H2.5Multi-SamplingsandOneuplink]]
... ... @@ -885,10 +885,8 @@
885 885  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
886 886  1*. this will mean each uplink will actually include the 6 uplink data (24 set data which cover 12 hours). So if device doesn't lost 6 continue data. There will not data lost.
887 887  
811 +== 5.2 Why the uplink JSON format is not standard? ==
888 888  
889 -== 6.2 Why the uplink JSON format is not standard? ==
890 -
891 -
892 892  The json format in uplink packet is not standard Json format. Below is the example. This is to make the payload as short as possible, due to NB-IoT transmit limition, a standard Json is not able to include 32 sets of sensors data with timestamp.
893 893  
894 894  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -895,12 +895,10 @@
895 895  
896 896  [[image:image-20240820112848-57.png]]
897 897  
819 += 6. Trouble Shooting: =
898 898  
899 -= 7. Trouble Shooting: =
821 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
900 900  
901 -== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
902 -
903 -
904 904  There are many different providers provide NB-IoT service in the world. They might use different band, different APN & different operator configuration. Which makes connection to NB-IoT network is complicate.
905 905  
906 906  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -923,16 +923,14 @@
923 923  If you have check all above and still fail. please send console log files (as many as possible) to [[support@dragino.com>>mailto:support@dragino.com]] so we can check.
924 924  
925 925  
926 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.2 Why sometime the AT Command is slow in reponse?(%%) ==
845 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.2 Why sometime the AT Command is slow in reponse?(%%) ==
927 927  
928 -
929 929  When the MCU is communicating with the NB-IoT module, the MCU response of AT Command will become slower, it might takes several seconds to response.
930 930  
931 931  [[image:image-20240820113015-60.png]]
932 932  
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
933 933  
934 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
935 -
936 936  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
937 937  === UDP: ===
938 938  
... ... @@ -942,7 +942,6 @@
942 942  
943 943  {AT+TDC=300}
944 944  
945 -
946 946  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
947 947  === MQTT: ===
948 948  
... ... @@ -985,7 +985,7 @@
985 985  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
986 986  
987 987  
988 -== 7.4 What if the signal is good but the domain name resolution fails? ==
904 +== 6.4 What if the signal is good but the domain name resolution fails? ==
989 989  
990 990  
991 991  If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
... ... @@ -998,9 +998,9 @@
998 998  
999 999  (% style="color:blue" %)**AT Command: AT+GDNS**
1000 1000  
1001 -**AT+GDNS=0**  ~/~/ Default. Automatically resolves the domain name and uses the resolved IP to communicate.
917 +**AT+GDNS=0**  ~/~/Default. Automatically resolves the domain name and uses the resolved IP to communicate.
1002 1002  
1003 -**AT+GDNS=1    **~/~/ Disabling Domain name resolution. Use the domain name directly to communicate.
919 +**AT+GDNS=1    **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
1004 1004  
1005 1005  (% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
1006 1006  
... ... @@ -1009,20 +1009,17 @@
1009 1009  [[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1010 1010  
1011 1011  
1012 -== 7.5 GPS debugging ==
928 +== 6.5 GPS debugging ==
1013 1013  
1014 1014  
1015 1015  Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1016 1016  
1017 -[[image:image-20240903104250-9.png||height="275" width="614"]]
933 +[[image:image-20240903100832-4.png||height="268" width="580"]]
1018 1018  
1019 1019  
1020 -[[image:image-20240903104431-10.png||height="291" width="621"]]
936 +=== 6.5.1 GPS commands ===
1021 1021  
1022 1022  
1023 -=== 7.5.1 GPS commands ===
1024 -
1025 -
1026 1026  The following are three related AT commands that introduce GPS functions.
1027 1027  
1028 1028  * **Turn on/off GPS**
... ... @@ -1069,10 +1069,10 @@
1069 1069  
1070 1070  Example: 24 hours:  24(D)=0x18(H)
1071 1071  
1072 -Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
985 + Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1073 1073  
1074 1074  
1075 -=== 7.5.2 GPS workflow ===
988 +=== 6.5.2 GPS workflow ===
1076 1076  
1077 1077  
1078 1078  The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
... ... @@ -1090,15 +1090,11 @@
1090 1090   Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
1091 1091  
1092 1092  
1093 -=== 7.5.3 GPS debugging methods ===
1006 +=== 6.5.3 GPS debugging methods ===
1094 1094  
1095 1095  
1096 -In summary, we can deduce the methods of debugging GPS:
1009 +In summary, we can deduce the method of debugging GPS:
1097 1097  
1098 -* **Check whether the GPS function is enabled.**
1099 -
1100 -[[image:image-20240903102327-5.png||height="271" width="529"]]
1101 -
1102 1102  * **Check whether the GPS antenna is loose**.
1103 1103  
1104 1104  If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
... ... @@ -1111,7 +1111,6 @@
1111 1111  
1112 1112  If the location fails, users can extend the location time.
1113 1113  
1114 -[[image:image-20240903102641-8.png||height="303" width="600"]]
1115 1115  
1116 1116  
1117 1117  
image-20240903104431-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -49.2 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0