Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 134.1 >
edited by Mengting Qiu
on 2024/10/18 15:41
To version < 126.1 >
edited by Mengting Qiu
on 2024/09/03 10:44
>
Change comment: Uploaded new attachment "image-20240903104431-10.png", version {1}

Summary

Details

Page properties
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.
... ... @@ -235,21 +235,18 @@
235 235  
236 236  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
237 237  
238 -* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
224 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
239 239  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
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"]]
... ... @@ -311,7 +311,6 @@
311 311  
312 312  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
313 313  
314 -
315 315  [[image:image-20240819174033-5.png]]
316 316  
317 317  [[image:image-20240819174209-6.png]]
... ... @@ -328,12 +328,10 @@
328 328  
329 329  [[image:image-20240819174314-7.png||height="469" width="785"]]
330 330  
331 -
332 332  === 3.3.3 Configure NB-IoT Sensor for connection ===
333 333  
334 334  ==== 3.3.3.1 AT Commands: ====
335 335  
336 -
337 337  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
338 338  
339 339  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -350,7 +350,6 @@
350 350  
351 351  ==== 3.3.3.2 Uplink Examples ====
352 352  
353 -
354 354  [[image:image-20240819174540-8.png]]
355 355  
356 356  For SE01-NB
... ... @@ -375,10 +375,8 @@
375 375  
376 376  For SN50V3-NB
377 377  
378 -
379 379  ==== 3.3.3.3 Map fields to sensor value ====
380 380  
381 -
382 382  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.
383 383  
384 384  [[image:image-20240819174610-9.png]]
... ... @@ -387,25 +387,25 @@
387 387  
388 388  Below is the NB-IoT Product Table show the mapping.
389 389  
390 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
391 -|(% 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
392 -|(% 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" %)
393 -|(% 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" %)
394 -|(% 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" %)
395 -|(% 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" %)
396 -|(% 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" %)
397 -|(% 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" %)
398 -|(% 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" %)
399 -|(% 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" %)
400 -|(% 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" %)
401 -|(% 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" %)
402 -|(% 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
403 -|(% 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" %)
404 -|(% 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" %)
405 -|(% 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" %)
406 -|(% 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" %)
407 -|(% 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" %)
408 -|(% 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" %)
409 409  
410 410  == 3.4 [[Datacake>>https://datacake.co/]] ==
411 411  
... ... @@ -423,7 +423,6 @@
423 423  
424 424  ==== 3.4.1.1 Create Device ====
425 425  
426 -
427 427  (% style="color:blue" %)**Add Device**(%%) in DataCake.
428 428  
429 429  [[image:image-20240820110003-1.png]]
... ... @@ -442,12 +442,10 @@
442 442  
443 443  [[image:image-20240820110114-6.png]]
444 444  
445 -
446 446  === 3.4.2 For Device already registered in DataCake before shipped ===
447 447  
448 448  ==== 3.4.2.1 Scan QR Code to get the device info ====
449 449  
450 -
451 451  Users can use their phones or computers to scan QR codes to obtain device data information.
452 452  
453 453  [[image:image-20240820110129-7.png]]
... ... @@ -454,40 +454,32 @@
454 454  
455 455  [[image:image-20240820110218-9.png]]
456 456  
457 -
458 458  ==== 3.4.2.2 Claim Device to User Account ====
459 459  
460 460  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
461 461  
462 -
463 463  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
464 464  
465 -
466 466  **Step1: Add a device**
467 467  
468 468  [[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
469 469  
470 -
471 471  **Step2: Choose your device type,please select dragino NB-IOT device**
472 472  
473 473  [[image:image-20240820110247-11.png]]
474 474  
475 -
476 476  **Step3: Choose to create a new device**
477 477  
478 478  [[image:image-20240820111016-12.png]]
479 479  
480 -
481 481  **Step4: Fill in the device ID of your NB device**
482 482  
483 483  [[image:image-20240820111101-13.png]]
484 484  
485 -
486 486  **Step5: Please select your device plan according to your needs and complete the creation of the device**
487 487  
488 488  [[image:image-20240820111113-14.png]]
489 489  
490 -
491 491  **Step6: Please add the decoder at the payload decoder of the device configuration.**
492 492  
493 493  **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]]
... ... @@ -496,12 +496,10 @@
496 496  
497 497  [[image:image-20240820111248-16.png]]
498 498  
499 -
500 500  **Step7: Add the output of the decoder as a field**
501 501  
502 502  [[image:image-20240820111259-17.png]]
503 503  
504 -
505 505  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
506 506  
507 507  [[image:image-20240820111312-18.png]]
... ... @@ -510,10 +510,8 @@
510 510  
511 511  [[image:image-20240820111333-20.png]]
512 512  
513 -
514 514  === 3.4.4 For device have not configured to connect to DataCake ===
515 515  
516 -
517 517  (% class="lead" %)
518 518  Use AT command for connecting to DataCake
519 519  
... ... @@ -521,12 +521,10 @@
521 521  
522 522  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
523 523  
524 -
525 525  == 3.5 Node-Red (via MQTT) ==
526 526  
527 527  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
528 528  
529 -
530 530  Take S31-NB UDP protocol as an example.
531 531  
532 532  Dragino provides input flow examples for the sensors.
... ... @@ -557,10 +557,8 @@
557 557  
558 558  [[image:image-20240820111448-26.png]]
559 559  
560 -
561 561  === 3.5.2 Simulate Connection ===
562 562  
563 -
564 564  We have completed the configuration of UDP. We can try sending packets to node red.
565 565  
566 566  [[image:image-20240820111504-27.png]]
... ... @@ -567,10 +567,8 @@
567 567  
568 568  [[image:image-20240820111515-28.png]]
569 569  
570 -
571 571  === 3.5.3 Configure NB-IoT Sensors ===
572 572  
573 -
574 574  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
575 575  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
576 576  * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
... ... @@ -584,15 +584,12 @@
584 584  
585 585  ==== 3.6.1.1 Create Device ====
586 586  
587 -
588 588  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
589 589  
590 590  [[image:image-20240820112210-29.png]]
591 591  
592 -
593 593  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
594 594  
595 -
596 596  (% style="color:blue" %)**Uplink Converter**
597 597  
598 598  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.
... ... @@ -609,10 +609,8 @@
609 609  
610 610  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
611 611  
612 -
613 613  ==== 3.6.1.3 MQTT Integration Setup ====
614 614  
615 -
616 616  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**;
617 617  
618 618  [[image:image-20240820112247-32.png]]
... ... @@ -631,7 +631,6 @@
631 631  
632 632  [[image:image-20240820112330-35.png]]
633 633  
634 -
635 635  === 3.6.2 Simulate with MQTT.fx ===
636 636  
637 637  [[image:image-20240820112340-36.png]]
... ... @@ -638,10 +638,8 @@
638 638  
639 639  [[image:image-20240820112351-37.png]]
640 640  
641 -
642 642  === 3.6.3 Configure NB-IoT Sensor ===
643 643  
644 -
645 645  (% style="color:blue" %)**AT Commands**
646 646  
647 647  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -664,83 +664,10 @@
664 664  
665 665  [[image:image-20240820112426-40.png]]
666 666  
611 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
667 667  
613 +=== 3.7.1 Create device & Get Credentials ===
668 668  
669 -== 3.7 ThingsBoard.Cloud (via COAP) ==
670 -
671 -=== 3.7.1 Configure ThingsBoard ===
672 -
673 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
674 -
675 -
676 -(% style="color:blue" %)**Uplink Converter**
677 -
678 -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.
679 -
680 -To create an uplink converter go to the (% style="color:blue" %)**Integrations center**(%%) -> (% style="color:blue" %)**Data converters**(%%) page and click (% style="color:blue" %)**“plus”** (%%)button. Name it (% style="color:blue" %)**“COAP Uplink Converter”**(%%) and select type (% style="color:blue" %)"**Uplink"**(%%). Use debug mode for now.
681 -
682 -[[image:https://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-20240729141300-1.png?width=1115&height=552&rev=1.1||alt="image-20240729141300-1.png" height="579" width="1168"]]
683 -
684 -
685 -(% style="color:blue" %)**Downlink Converter**
686 -
687 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
688 -
689 -[[image:https://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-20240729142505-3.png?width=1023&height=507&rev=1.1||alt="image-20240729142505-3.png" height="579" width="1168"]]
690 -
691 -
692 -==== 3.7.1.2 COAP Integration Setup ====
693 -
694 -
695 -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" %)**“CoAP Integration”**(%%), select type **COAP    **(% style="color:blue" %);
696 -
697 -[[image:https://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-20240729144058-4.png?width=1021&height=506&rev=1.1||alt="image-20240729144058-4.png" height="583" width="1176"]]
698 -
699 -
700 -The next steps is to add the recently created uplink converters;
701 -
702 -[[image:https://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-20240729150142-5.png?width=1023&height=507&rev=1.1||alt="image-20240729150142-5.png" height="591" width="1193"]]
703 -
704 -
705 -==== 3.7.1.3 Add COAP Integration ====
706 -
707 -[[image:https://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-20240729161543-9.png?width=1009&height=500&rev=1.1||alt="image-20240729161543-9.png" height="590" width="1191"]]
708 -
709 -
710 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
711 -
712 -==== 3.7.2.1 Instruction Description ====
713 -
714 -
715 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
716 -* AT+SERVADDR=COAP Server Address,5683
717 -
718 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
719 -
720 -[[image:https://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-20240729172305-12.png?width=624&height=361&rev=1.1||alt="image-20240729172305-12.png" height="417" width="721"]]
721 -
722 -Note:The port for the COAP protocol has been fixed to 5683
723 -
724 -
725 -* AT+URL1=11,"i"
726 -* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
727 -*
728 -
729 --CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
730 -
731 -e.g.
732 -
733 -* AT+URL1=11, "i"
734 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
735 -
736 -[[image:https://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-20240729172500-14.png?width=700&height=403&rev=1.1||alt="image-20240729172500-14.png" height="413" width="718"]]
737 -
738 -
739 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
740 -
741 -=== 3.8.1 Create device & Get Credentials ===
742 -
743 -
744 744  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.
745 745  
746 746  [[image:image-20240820112516-41.png]]
... ... @@ -787,9 +787,8 @@
787 787  
788 788  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
789 789  
790 -=== 3.8.2 Simulate with MQTT.fx ===
661 +=== 3.7.2 Simulate with MQTT.fx ===
791 791  
792 -
793 793  [[image:image-20240820112552-44.png]]
794 794  
795 795  [[image:image-20240820112604-45.png]]
... ... @@ -800,18 +800,14 @@
800 800  
801 801  [[image:image-20240820112626-47.png]]
802 802  
673 +=== 3.7.3 tago data ===
803 803  
804 -=== 3.8.3 tago data ===
805 -
806 -
807 807  [[image:image-20240820112637-48.png]]
808 808  
809 809  [[image:image-20240820112647-49.png]]
810 810  
679 +== 3.8 TCP Connection ==
811 811  
812 -== 3.9 TCP Connection ==
813 -
814 -
815 815  (% style="color:blue" %)**AT command:**
816 816  
817 817  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
... ... @@ -828,18 +828,16 @@
828 828  
829 829  [[image:image-20240820112716-51.png]]
830 830  
697 +== 3.9 AWS Connection ==
831 831  
832 -== 3.10 AWS Connection ==
833 -
834 -
835 835  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]]
836 836  
701 += =
837 837  
838 838  = 4. COAP/UDP/MQTT/TCP downlink =
839 839  
840 840  == 4.1 MQTT (via MQTT.fx) ==
841 841  
842 -
843 843  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
844 844  
845 845  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -862,12 +862,10 @@
862 862  
863 863  [[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
864 864  
865 -
866 866  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
867 867  
868 868  [[image:image-20240820112813-54.png]]
869 869  
870 -
871 871  **3. **The downlink command can be successfully sent only when the downlink port is open.
872 872  
873 873   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -883,7 +883,6 @@
883 883  
884 884  == 4.2 UDP (via Thingseye) ==
885 885  
886 -
887 887  (% 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/]])
888 888  
889 889  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)
... ... @@ -913,30 +913,26 @@
913 913  
914 914  = 5. GPS positioning function =
915 915  
916 -== 1. Turn on GPS function ==
777 +=== 1. Turn on GPS function ===
917 917  
918 -
919 919  (% class="wikigeneratedid" %)
920 -AT+GPS=1 or 0  ~/~/ GPS function on or off
780 +AT+GPS=1 or 0  ~/~/GPS function on or off
921 921  
922 922  
923 -== 2. Extend the time to turn on GNSS ==
783 +=== 2.Extend the time to turn on GNSS ===
924 924  
785 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
925 925  
926 -AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
927 927  
788 +=== 3.Get or set GPS positioning interval in units of hour ===
928 928  
929 -== 3. Get or set GPS positioning interval in units of hour ==
790 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
930 930  
931 931  
932 -AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
793 += 5. FAQ =
933 933  
795 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
934 934  
935 -= 6. FAQ =
936 -
937 -== 6.1 What is the usage of Multi Sampling and One Uplink? ==
938 -
939 -
940 940  The NB series has the feature for Multi Sampling and one uplink. See one of them
941 941  
942 942  [[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]]
... ... @@ -951,9 +951,8 @@
951 951  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
952 952  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.
953 953  
954 -== 6.2 Why the uplink JSON format is not standard? ==
811 +== 5.2 Why the uplink JSON format is not standard? ==
955 955  
956 -
957 957  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.
958 958  
959 959  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -960,12 +960,10 @@
960 960  
961 961  [[image:image-20240820112848-57.png]]
962 962  
819 += 6. Trouble Shooting: =
963 963  
964 -= 7. Trouble Shooting: =
821 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
965 965  
966 -== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
967 -
968 -
969 969  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.
970 970  
971 971  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -988,16 +988,14 @@
988 988  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.
989 989  
990 990  
991 -== (% 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?(%%) ==
992 992  
993 -
994 994  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.
995 995  
996 996  [[image:image-20240820113015-60.png]]
997 997  
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
998 998  
999 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1000 -
1001 1001  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1002 1002  === UDP: ===
1003 1003  
... ... @@ -1007,7 +1007,6 @@
1007 1007  
1008 1008  {AT+TDC=300}
1009 1009  
1010 -
1011 1011  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1012 1012  === MQTT: ===
1013 1013  
... ... @@ -1050,7 +1050,7 @@
1050 1050  [[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/]]
1051 1051  
1052 1052  
1053 -== 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? ==
1054 1054  
1055 1055  
1056 1056  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.
... ... @@ -1063,9 +1063,9 @@
1063 1063  
1064 1064  (% style="color:blue" %)**AT Command: AT+GDNS**
1065 1065  
1066 -**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.
1067 1067  
1068 -**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.
1069 1069  
1070 1070  (% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
1071 1071  
... ... @@ -1074,20 +1074,17 @@
1074 1074  [[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1075 1075  
1076 1076  
1077 -== 7.5 GPS debugging ==
928 +== 6.5 GPS debugging ==
1078 1078  
1079 1079  
1080 1080  Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1081 1081  
1082 -[[image:image-20240903104250-9.png||height="275" width="614"]]
933 +[[image:image-20240903100832-4.png||height="268" width="580"]]
1083 1083  
1084 1084  
1085 -[[image:image-20240903104431-10.png||height="291" width="621"]]
936 +=== 6.5.1 GPS commands ===
1086 1086  
1087 1087  
1088 -=== 7.5.1 GPS commands ===
1089 -
1090 -
1091 1091  The following are three related AT commands that introduce GPS functions.
1092 1092  
1093 1093  * **Turn on/off GPS**
... ... @@ -1134,10 +1134,10 @@
1134 1134  
1135 1135  Example: 24 hours:  24(D)=0x18(H)
1136 1136  
1137 -Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
985 + Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1138 1138  
1139 1139  
1140 -=== 7.5.2 GPS workflow ===
988 +=== 6.5.2 GPS workflow ===
1141 1141  
1142 1142  
1143 1143  The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
... ... @@ -1155,15 +1155,11 @@
1155 1155   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.
1156 1156  
1157 1157  
1158 -=== 7.5.3 GPS debugging methods ===
1006 +=== 6.5.3 GPS debugging methods ===
1159 1159  
1160 1160  
1161 -In summary, we can deduce the methods of debugging GPS:
1009 +In summary, we can deduce the method of debugging GPS:
1162 1162  
1163 -* **Check whether the GPS function is enabled.**
1164 -
1165 -[[image:image-20240903102327-5.png||height="271" width="529"]]
1166 -
1167 1167  * **Check whether the GPS antenna is loose**.
1168 1168  
1169 1169  If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
... ... @@ -1176,7 +1176,6 @@
1176 1176  
1177 1177  If the location fails, users can extend the location time.
1178 1178  
1179 -[[image:image-20240903102641-8.png||height="303" width="600"]]
1180 1180  
1181 1181  
1182 1182  

Applications

Navigation

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