Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 138.1 >
edited by Xiaoling
on 2025/01/13 11:31
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.ting
Content
... ... @@ -1,15 +1,13 @@
1 -​**Table of Contents:**
1 +​
2 2  
3 -{{toc/}}
4 4  
4 +(% class="wikigeneratedid" id="HTableofContents:" %)
5 +**Table of Contents:**
5 5  
7 +{{toc/}}
6 6  
7 -
8 -
9 -
10 10  = 1. The use of this guideline =
11 11  
12 -
13 13  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.
14 14  
15 15  
... ... @@ -17,7 +17,6 @@
17 17  
18 18  == 2.1 General Configure to attach network ==
19 19  
20 -
21 21  To attache end nodes to NB-IoT or LTE-M Network, You need to:
22 22  
23 23  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)
... ... @@ -29,7 +29,7 @@
29 29  [[image:image-20240602220856-1.png]]
30 30  
31 31  
32 -[[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 +放一张如何插卡图片。
33 33  
34 34  
35 35  After doing above, the end nodes should be able to attach to NB-IoT network .
... ... @@ -54,10 +54,8 @@
54 54  |(% style="width:117px" %)China Mobile|(% style="width:151px" %)No need configure|(% style="width:406px" %)China Mainland, HongKong|(% style="width:351px" %) |(% style="width:120px" %)
55 55  |(% style="width:117px" %)China Telecom|(% style="width:151px" %)ctnb|(% style="width:406px" %)China Mainland|(% style="width:351px" %) |(% style="width:120px" %)
56 56  
57 -
58 58  == 2.2 Speed Up Network Attach time ==
59 59  
60 -
61 61  **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**.
62 62  
63 63  **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.
... ... @@ -64,7 +64,7 @@
64 64  
65 65  Attache to 1NCE card for Australia use:
66 66  
67 -* AT+COPS=1,2,"50501",8                                                 
62 +* AT+COPS=1,2,"50501",8
68 68  * AT+QCFG="band",0,0x8000000,0x8000000,1
69 69  
70 70  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
... ... @@ -76,11 +76,11 @@
76 76  
77 77  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/]]**
78 78  
79 -=== **1. Configure Frequency Band** ===
74 +=== **1.Configure Frequency Band** ===
80 80  
81 81  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
82 82  
83 -**<GSM_bandval>:**
78 +<GSM_bandval>:
84 84  
85 85  0 No change 
86 86  0x1 EGSM900
... ... @@ -89,7 +89,7 @@
89 89  0x8 PCS1900 
90 90  0xF All of the supported bands above
91 91  
92 -**<eMTC_bandval>:**
87 +<eMTC_bandval>:
93 93  
94 94  0 No change 
95 95  0x1  LTE B1
... ... @@ -113,7 +113,7 @@
113 113  0x1000000000000000000  LTE B73 
114 114  0x1000000000000000000000  LTE B85
115 115  
116 -**<NB-IoT_bandval>:**
111 +<NB-IoT_bandval>:
117 117  
118 118  0 No change 
119 119  0x1  LTE B1
... ... @@ -146,7 +146,7 @@
146 146  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
147 147  
148 148  
149 -=== **2. Configure search network sequence** ===
144 +=== **2.Configure search network sequence** ===
150 150  
151 151  AT+QCFG="nwscanseq",<scanseq>,1
152 152  
... ... @@ -159,9 +159,8 @@
159 159  
160 160  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
161 161  
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
162 162  
163 -=== **3. Configure Network Category to be Searched for under LTE RAT** ===
164 -
165 165  AT+QCFG="iotopmode",mode,1
166 166  
167 167  0 eMTC 
... ... @@ -168,9 +168,8 @@
168 168  1 NB-IoT 
169 169  2 eMTC and NB-IoT
170 170  
165 +=== **4.AT command to set frequency band and network category** ===
171 171  
172 -=== **4. AT command to set frequency band and network category** ===
173 -
174 174  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
175 175  
176 176  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -192,23 +192,18 @@
192 192  
193 193  == 3.1 General UDP Connection ==
194 194  
195 -
196 196  The NB-IoT Sensor can send packet to server use UDP protocol.
197 197  
198 -
199 199  === 3.1.1 Simulate UDP Connection by PC tool ===
200 200  
201 -
202 202  We can use PC tool to simulate UDP connection to make sure server works ok.
203 203  
204 -[[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"]]
205 205  
206 -
207 207  === 3.1.2 Configure NB-IoT Sensor ===
208 208  
209 209  ==== 3.1.2.1 AT Commands ====
210 210  
211 -
212 212  (% style="color:blue" %)**AT Commands:**
213 213  
214 214  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
... ... @@ -217,16 +217,12 @@
217 217  
218 218  [[image:image-20240819102802-1.png]]
219 219  
220 -
221 221  ==== 3.1.2.2 Uplink Example ====
222 222  
210 +[[image:image-20240819105418-8.png||height="671" width="1414"]]
223 223  
224 -[[image:image-20240819105418-8.png||height="611" width="1287"]]
225 -
226 -
227 227  == 3.2 General COAP Connection ==
228 228  
229 -
230 230  The NB-IoT Sensor can send packet to server use COAP protocol.
231 231  
232 232  Below are the commands.
... ... @@ -237,21 +237,18 @@
237 237  
238 238  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
239 239  
240 -* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
224 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
241 241  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
242 242  
243 243  [[image:image-20240819103212-2.png]]
244 244  
245 -
246 246  === 3.2.1 Uplink Example ===
247 247  
248 -
249 249  [[image:image-20240819103909-4.png||height="453" width="955"]]
250 250  
251 251  
252 252  == 3.2 General MQTT Connection ==
253 253  
254 -
255 255  The NB-IoT Sensor can send packet to server use MQTT protocol.
256 256  
257 257  Below are the commands.
... ... @@ -279,12 +279,10 @@
279 279  
280 280  (% 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.**
281 281  
282 -
283 283  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
284 284  
285 285  === 3.3.1 Get MQTT Credentials ===
286 286  
287 -
288 288  [[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.
289 289  
290 290  [[image:image-20240819173602-1.png||height="401" width="743"]]
... ... @@ -291,12 +291,10 @@
291 291  
292 292  [[image:image-20240819173706-3.png||height="595" width="597"]]
293 293  
294 -
295 295  === 3.3.2 Simulate with MQTT.fx ===
296 296  
297 297  ==== 3.3.2.1 Establish MQTT Connection ====
298 298  
299 -
300 300  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
301 301  
302 302  [[image:image-20240819173826-4.png||height="534" width="734"]]
... ... @@ -313,7 +313,6 @@
313 313  
314 314  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
315 315  
316 -
317 317  [[image:image-20240819174033-5.png]]
318 318  
319 319  [[image:image-20240819174209-6.png]]
... ... @@ -330,12 +330,10 @@
330 330  
331 331  [[image:image-20240819174314-7.png||height="469" width="785"]]
332 332  
333 -
334 334  === 3.3.3 Configure NB-IoT Sensor for connection ===
335 335  
336 336  ==== 3.3.3.1 AT Commands: ====
337 337  
338 -
339 339  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
340 340  
341 341  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -352,7 +352,6 @@
352 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:150px" %)Field3|(% style="background-color:#4f81bd; color:white; width:141px" %)Field4|(% style="background-color:#4f81bd; color:white; width:138px" %)Field5|(% style="background-color:#4f81bd; color:white; width:135px" %)Field6|(% style="background-color:#4f81bd; color:white; width:134px" %)Field7|(% style="background-color:#4f81bd; color:white; width:138px" %)Field8|(% style="background-color:#4f81bd; color:white; width:85px" %)Field9|(% style="background-color:#4f81bd; color:white; width:80px" %)Field10
394 -|(% style="background-color:#4f81bd; color:white; width:143px" %)S31x-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:150px" %)Battery|(% style="width:141px" %)RSSI|(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
395 -|(% style="background-color:#4f81bd; color:white; width:143px" %)SE01-NB|(% style="width:103px" %)Temperature |(% style="width:102px" %)Humidity|(% style="width:150px" %)conduct|(% style="width:141px" %)dielectric_constant|(% style="width:138px" %)Battery|(% style="width:135px" %)RSSI|(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
396 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS20-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:150px" %)RSSI|(% style="width:141px" %) |(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
397 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS45-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:150px" %)RSSI|(% style="width:141px" %) |(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
398 -|(% style="background-color:#4f81bd; color:white; width:143px" %)DDS75-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:150px" %)RSSI|(% style="width:141px" %) |(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
399 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS120-NB|(% style="width:103px" %)distance|(% style="width:102px" %)Battery|(% style="width:150px" %)RSSI|(% style="width:141px" %) |(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
400 -|(% rowspan="1" style="background-color:#4f81bd; color:white; width:143px" %)SPH01-NB|(% style="width:103px" %)ph|(% style="width:102px" %)Temperature|(% style="width:150px" %)Battery|(% style="width:141px" %)RSSI|(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% colspan="1" rowspan="1" style="width:80px" %)
401 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NLM01-NB|(% style="width:103px" %)Humidity|(% style="width:102px" %)Temperature|(% style="width:150px" %)Battery|(% style="width:141px" %)RSSI|(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
402 -|(% style="background-color:#4f81bd; color:white; width:143px" %)NMDS200-NB|(% style="width:103px" %)distance1|(% style="width:102px" %)distance2|(% style="width:150px" %)Battery|(% style="width:141px" %)RSSI|(% style="width:138px" %) |(% style="width:135px" %) |(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
403 -|(% style="background-color:#4f81bd; color:white; width:143px" %)CPN01-NB|(% style="width:103px" %)alarm|(% style="width:102px" %)count|(% style="width:150px" %)door open duration|(% style="width:141px" %)calc flag|(% style="width:138px" %)Battery|(% style="width:135px" %)RSSI|(% style="width:134px" %) |(% style="width:138px" %) |(% style="width:85px" %) |(% style="width:80px" %)
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:150px" %)pb14door open num|(% colspan="1" rowspan="1" style="width:141px" %)pb14 last open time|(% colspan="1" rowspan="1" style="width:138px" %)pb15 level status|(% colspan="1" rowspan="1" style="width:135px" %)pb15 alarm status|(% colspan="1" rowspan="1" style="width:134px" %)pb15 door open num|(% colspan="1" rowspan="1" style="width:138px" %)pb15 last open time|(% colspan="1" rowspan="1" style="width:85px" %)Battery|(% colspan="1" rowspan="1" style="width:80px" %)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:150px" %)RSSI|(% colspan="1" rowspan="1" style="width:141px" %)DS18B20 Temp|(% colspan="1" rowspan="1" style="width:138px" %)exit_state/input PA4|(% colspan="1" rowspan="1" style="width:135px" %)adc0|(% colspan="1" rowspan="1" style="width:134px" %)Temperature |(% colspan="1" rowspan="1" style="width:138px" %)Humidity|(% colspan="1" rowspan="1" style="width:85px" %) |(% colspan="1" rowspan="1" style="width:80px" %)
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:150px" %)RSSI|(% colspan="1" style="width:141px" %)DS18B20 Temp|(% colspan="1" style="width:138px" %)exit_state/input PA4|(% colspan="1" style="width:135px" %)adc0|(% colspan="1" style="width:134px" %)distance|(% colspan="1" style="width:138px" %) |(% colspan="1" style="width:85px" %) |(% colspan="1" style="width:80px" %)
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:150px" %)RSSI|(% colspan="1" style="width:141px" %)adc0|(% colspan="1" style="width:138px" %)exit_state/input PA4|(% colspan="1" style="width:135px" %)adc1|(% colspan="1" style="width:134px" %)Temperature|(% colspan="1" style="width:138px" %)Humidity|(% colspan="1" style="width:85px" %)adc4|(% colspan="1" style="width:80px" %)
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:150px" %)RSSI|(% colspan="1" style="width:141px" %)DS18B20 Temp|(% colspan="1" style="width:138px" %)adc0|(% colspan="1" style="width:135px" %)exit_state/input PA4|(% colspan="1" style="width:134px" %)DS18B20 Temp2|(% colspan="1" style="width:138px" %)DS18B20 Temp3|(% colspan="1" style="width:85px" %) |(% colspan="1" style="width:80px" %)
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:150px" %)RSSI|(% colspan="1" style="width:141px" %)DS18B20 Temp|(% colspan="1" style="width:138px" %)adc0|(% colspan="1" style="width:135px" %)exit_state/input PA4|(% colspan="1" style="width:134px" %)Weight|(% colspan="1" style="width:138px" %) |(% colspan="1" style="width:85px" %) |(% colspan="1" style="width:80px" %)
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:150px" %)RSSI|(% colspan="1" style="width:141px" %)count|(% colspan="1" style="width:138px" %) |(% colspan="1" style="width:135px" %) |(% colspan="1" style="width:134px" %) |(% colspan="1" style="width:138px" %) |(% colspan="1" style="width:85px" %) |(% colspan="1" style="width:80px" %)
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  
... ... @@ -425,7 +425,6 @@
425 425  
426 426  ==== 3.4.1.1 Create Device ====
427 427  
428 -
429 429  (% style="color:blue" %)**Add Device**(%%) in DataCake.
430 430  
431 431  [[image:image-20240820110003-1.png]]
... ... @@ -444,12 +444,10 @@
444 444  
445 445  [[image:image-20240820110114-6.png]]
446 446  
447 -
448 448  === 3.4.2 For Device already registered in DataCake before shipped ===
449 449  
450 450  ==== 3.4.2.1 Scan QR Code to get the device info ====
451 451  
452 -
453 453  Users can use their phones or computers to scan QR codes to obtain device data information.
454 454  
455 455  [[image:image-20240820110129-7.png]]
... ... @@ -456,41 +456,32 @@
456 456  
457 457  [[image:image-20240820110218-9.png]]
458 458  
459 -
460 460  ==== 3.4.2.2 Claim Device to User Account ====
461 461  
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**
... ... @@ -587,15 +587,12 @@
587 587  
588 588  ==== 3.6.1.1 Create Device ====
589 589  
590 -
591 591  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
592 592  
593 593  [[image:image-20240820112210-29.png]]
594 594  
595 -
596 596  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
597 597  
598 -
599 599  (% style="color:blue" %)**Uplink Converter**
600 600  
601 601  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.
... ... @@ -612,10 +612,8 @@
612 612  
613 613  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
614 614  
615 -
616 616  ==== 3.6.1.3 MQTT Integration Setup ====
617 617  
618 -
619 619  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**;
620 620  
621 621  [[image:image-20240820112247-32.png]]
... ... @@ -634,7 +634,6 @@
634 634  
635 635  [[image:image-20240820112330-35.png]]
636 636  
637 -
638 638  === 3.6.2 Simulate with MQTT.fx ===
639 639  
640 640  [[image:image-20240820112340-36.png]]
... ... @@ -641,10 +641,8 @@
641 641  
642 642  [[image:image-20240820112351-37.png]]
643 643  
644 -
645 645  === 3.6.3 Configure NB-IoT Sensor ===
646 646  
647 -
648 648  (% style="color:blue" %)**AT Commands**
649 649  
650 650  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -667,82 +667,10 @@
667 667  
668 668  [[image:image-20240820112426-40.png]]
669 669  
611 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
670 670  
671 -== 3.7 ThingsBoard.Cloud (via COAP) ==
613 +=== 3.7.1 Create device & Get Credentials ===
672 672  
673 -=== 3.7.1 Configure ThingsBoard ===
674 -
675 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
676 -
677 -
678 -(% style="color:blue" %)**Uplink Converter**
679 -
680 -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.
681 -
682 -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.
683 -
684 -[[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"]]
685 -
686 -
687 -(% style="color:blue" %)**Downlink Converter**
688 -
689 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
690 -
691 -[[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"]]
692 -
693 -
694 -==== 3.7.1.2 COAP Integration Setup ====
695 -
696 -
697 -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" %);
698 -
699 -[[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"]]
700 -
701 -
702 -The next steps is to add the recently created uplink converters;
703 -
704 -[[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"]]
705 -
706 -
707 -==== 3.7.1.3 Add COAP Integration ====
708 -
709 -[[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"]]
710 -
711 -
712 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
713 -
714 -==== 3.7.2.1 Instruction Description ====
715 -
716 -
717 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
718 -* AT+SERVADDR=COAP Server Address,5683
719 -
720 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
721 -
722 -[[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"]]
723 -
724 -Note:The port for the COAP protocol has been fixed to 5683
725 -
726 -
727 -* AT+URL1=11,"i"
728 -* AT+URL2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
729 -*
730 -
731 --CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
732 -
733 -e.g.
734 -
735 -* AT+URL1=11, "i"
736 -* AT+URL2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
737 -
738 -[[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"]]
739 -
740 -
741 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
742 -
743 -=== 3.8.1 Create device & Get Credentials ===
744 -
745 -
746 746  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.
747 747  
748 748  [[image:image-20240820112516-41.png]]
... ... @@ -789,9 +789,8 @@
789 789  
790 790  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
791 791  
792 -=== 3.8.2 Simulate with MQTT.fx ===
661 +=== 3.7.2 Simulate with MQTT.fx ===
793 793  
794 -
795 795  [[image:image-20240820112552-44.png]]
796 796  
797 797  [[image:image-20240820112604-45.png]]
... ... @@ -802,23 +802,19 @@
802 802  
803 803  [[image:image-20240820112626-47.png]]
804 804  
673 +=== 3.7.3 tago data ===
805 805  
806 -=== 3.8.3 tago data ===
807 -
808 -
809 809  [[image:image-20240820112637-48.png]]
810 810  
811 811  [[image:image-20240820112647-49.png]]
812 812  
679 +== 3.8 TCP Connection ==
813 813  
814 -== 3.9 TCP Connection ==
815 -
816 -
817 817  (% style="color:blue" %)**AT command:**
818 818  
819 819  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
820 820  
821 -* (% style="color:#037691" %)**AT+PRO=4,5   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
685 +* (% style="color:#037691" %)**AT+PRO=4,1   ** (%%) ~/~/ Set to use TCP protocol to uplink(JSON format)
822 822  
823 823  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
824 824  
... ... @@ -830,18 +830,16 @@
830 830  
831 831  [[image:image-20240820112716-51.png]]
832 832  
697 +== 3.9 AWS Connection ==
833 833  
834 -== 3.10 AWS Connection ==
835 -
836 -
837 837  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]]
838 838  
701 += =
839 839  
840 840  = 4. COAP/UDP/MQTT/TCP downlink =
841 841  
842 842  == 4.1 MQTT (via MQTT.fx) ==
843 843  
844 -
845 845  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
846 846  
847 847  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -864,12 +864,10 @@
864 864  
865 865  [[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
866 866  
867 -
868 868  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
869 869  
870 870  [[image:image-20240820112813-54.png]]
871 871  
872 -
873 873  **3. **The downlink command can be successfully sent only when the downlink port is open.
874 874  
875 875   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -885,7 +885,6 @@
885 885  
886 886  == 4.2 UDP (via Thingseye) ==
887 887  
888 -
889 889  (% 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/]])
890 890  
891 891  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)
... ... @@ -915,30 +915,26 @@
915 915  
916 916  = 5. GPS positioning function =
917 917  
918 -== 1. Turn on GPS function ==
777 +=== 1. Turn on GPS function ===
919 919  
920 -
921 921  (% class="wikigeneratedid" %)
922 -AT+GPS=1 or 0  ~/~/ GPS function on or off
780 +AT+GPS=1 or 0  ~/~/GPS function on or off
923 923  
924 924  
925 -== 2. Extend the time to turn on GNSS ==
783 +=== 2.Extend the time to turn on GNSS ===
926 926  
785 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
927 927  
928 -AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
929 929  
788 +=== 3.Get or set GPS positioning interval in units of hour ===
930 930  
931 -== 3. Get or set GPS positioning interval in units of hour ==
790 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
932 932  
933 933  
934 -AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
793 += 5. FAQ =
935 935  
795 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
936 936  
937 -= 6. FAQ =
938 -
939 -== 6.1 What is the usage of Multi Sampling and One Uplink? ==
940 -
941 -
942 942  The NB series has the feature for Multi Sampling and one uplink. See one of them
943 943  
944 944  [[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]]
... ... @@ -953,9 +953,8 @@
953 953  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
954 954  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.
955 955  
956 -== 6.2 Why the uplink JSON format is not standard? ==
811 +== 5.2 Why the uplink JSON format is not standard? ==
957 957  
958 -
959 959  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.
960 960  
961 961  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -962,12 +962,10 @@
962 962  
963 963  [[image:image-20240820112848-57.png]]
964 964  
819 += 6. Trouble Shooting: =
965 965  
966 -= 7. Trouble Shooting: =
821 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
967 967  
968 -== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
969 -
970 -
971 971  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.
972 972  
973 973  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -990,16 +990,14 @@
990 990  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.
991 991  
992 992  
993 -== (% 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?(%%) ==
994 994  
995 -
996 996  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.
997 997  
998 998  [[image:image-20240820113015-60.png]]
999 999  
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
1000 1000  
1001 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1002 -
1003 1003  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1004 1004  === UDP: ===
1005 1005  
... ... @@ -1009,7 +1009,6 @@
1009 1009  
1010 1010  {AT+TDC=300}
1011 1011  
1012 -
1013 1013  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1014 1014  === MQTT: ===
1015 1015  
... ... @@ -1052,7 +1052,7 @@
1052 1052  [[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/]]
1053 1053  
1054 1054  
1055 -== 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? ==
1056 1056  
1057 1057  
1058 1058  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.
... ... @@ -1065,31 +1065,28 @@
1065 1065  
1066 1066  (% style="color:blue" %)**AT Command: AT+GDNS**
1067 1067  
1068 -**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.
1069 1069  
1070 -**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.
1071 1071  
1072 1072  (% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
1073 1073  
1074 1074  Example:
1075 1075  
1076 -[[image:image-20240827150121-5.png||height="473" width="676"]][[image:image-20240827145055-4.png||height="474" width="665"]]
925 +[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
1077 1077  
1078 1078  
1079 -== 7.5 GPS debugging ==
928 +== 6.5 GPS debugging ==
1080 1080  
1081 1081  
1082 1082  Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1083 1083  
1084 -[[image:image-20240903104250-9.png||height="275" width="614"]]
933 +[[image:image-20240903100832-4.png||height="268" width="580"]]
1085 1085  
1086 1086  
1087 -[[image:image-20240903104431-10.png||height="291" width="621"]]
936 +=== 6.5.1 GPS commands ===
1088 1088  
1089 1089  
1090 -=== 7.5.1 GPS commands ===
1091 -
1092 -
1093 1093  The following are three related AT commands that introduce GPS functions.
1094 1094  
1095 1095  * **Turn on/off GPS**
... ... @@ -1136,10 +1136,10 @@
1136 1136  
1137 1137  Example: 24 hours:  24(D)=0x18(H)
1138 1138  
1139 -Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
985 + Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1140 1140  
1141 1141  
1142 -=== 7.5.2 GPS workflow ===
988 +=== 6.5.2 GPS workflow ===
1143 1143  
1144 1144  
1145 1145  The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
... ... @@ -1157,15 +1157,11 @@
1157 1157   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.
1158 1158  
1159 1159  
1160 -=== 7.5.3 GPS debugging methods ===
1006 +=== 6.5.3 GPS debugging methods ===
1161 1161  
1162 1162  
1163 -In summary, we can deduce the methods of debugging GPS:
1009 +In summary, we can deduce the method of debugging GPS:
1164 1164  
1165 -* **Check whether the GPS function is enabled.**
1166 -
1167 -[[image:image-20240903102327-5.png||height="271" width="529"]]
1168 -
1169 1169  * **Check whether the GPS antenna is loose**.
1170 1170  
1171 1171  If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
... ... @@ -1178,15 +1178,8 @@
1178 1178  
1179 1179  If the location fails, users can extend the location time.
1180 1180  
1181 -[[image:image-20240903102641-8.png||height="303" width="600"]]
1182 1182  
1183 1183  
1184 -== 7.6 CB device configuration TCP/IP failed ==
1185 1185  
1186 -[[image:image-20250113103816-1.png]]
1187 1187  
1188 -**Use AT+IPTYPE=? to check the IPTYPE configuration.
1189 -AT+IPTYPE can only be configured as 1 or 2.
1190 -If it is configured otherwise, this error will occur**
1191 -
1192 1192  
image-20250113103816-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Bei
Size
... ... @@ -1,1 +1,0 @@
1 -13.6 KB
Content

Applications

Navigation

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