Last modified by Mengting Qiu on 2025/03/08 11:35
<
From version < 140.1
edited by Mengting Qiu
on 2025/03/08 11:35
To version < 125.1 >
edited by Mengting Qiu
on 2024/09/03 10:42
Change comment: Uploaded new attachment "image-20240903104250-9.png", version {1}

Summary

Details

Page properties
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 .
... ... @@ -56,7 +56,6 @@
56 56  
57 57  == 2.2 Speed Up Network Attach time ==
58 58  
59 -
60 60  **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**.
61 61  
62 62  **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.
... ... @@ -63,7 +63,7 @@
63 63  
64 64  Attache to 1NCE card for Australia use:
65 65  
66 -* AT+COPS=1,2,"50501",8                                                 
62 +* AT+COPS=1,2,"50501",8
67 67  * AT+QCFG="band",0,0x8000000,0x8000000,1
68 68  
69 69  After connection is successful, user can use (% style="color:#037691" %)**AT+QENG="servingcell"**(%%) to check which band is actually in used.
... ... @@ -75,11 +75,11 @@
75 75  
76 76  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/]]**
77 77  
78 -=== **1. Configure Frequency Band** ===
74 +=== **1.Configure Frequency Band** ===
79 79  
80 80  AT+QCFG="band"[,<GSM_bandval>,<eMTC_bandval>,<NB-IoT_bandval>[,<effect>]]
81 81  
82 -**<GSM_bandval>:**
78 +<GSM_bandval>:
83 83  
84 84  0 No change 
85 85  0x1 EGSM900
... ... @@ -88,7 +88,7 @@
88 88  0x8 PCS1900 
89 89  0xF All of the supported bands above
90 90  
91 -**<eMTC_bandval>:**
87 +<eMTC_bandval>:
92 92  
93 93  0 No change 
94 94  0x1  LTE B1
... ... @@ -112,7 +112,7 @@
112 112  0x1000000000000000000  LTE B73 
113 113  0x1000000000000000000000  LTE B85
114 114  
115 -**<NB-IoT_bandval>:**
111 +<NB-IoT_bandval>:
116 116  
117 117  0 No change 
118 118  0x1  LTE B1
... ... @@ -145,7 +145,7 @@
145 145  AT+QCFG="band",0xF,0x100002000000000f0e189f,0x10004200000000090e189f,1
146 146  
147 147  
148 -=== **2. Configure search network sequence** ===
144 +=== **2.Configure search network sequence** ===
149 149  
150 150  AT+QCFG="nwscanseq",<scanseq>,1
151 151  
... ... @@ -158,9 +158,8 @@
158 158  
159 159  AT+QCFG="nwscanseq",02,1  ~/~/Priority search for eMTC
160 160  
157 +=== **3.Configure Network Category to be Searched for under LTE RAT** ===
161 161  
162 -=== **3. Configure Network Category to be Searched for under LTE RAT** ===
163 -
164 164  AT+QCFG="iotopmode",mode,1
165 165  
166 166  0 eMTC 
... ... @@ -167,9 +167,8 @@
167 167  1 NB-IoT 
168 168  2 eMTC and NB-IoT
169 169  
165 +=== **4.AT command to set frequency band and network category** ===
170 170  
171 -=== **4. AT command to set frequency band and network category** ===
172 -
173 173  AT+QBAND=0x100002000000000f0e189f,0x10004200000000090e189f  ~/~/<eMTC_bandval>,<NB-IoT_bandval>
174 174  
175 175  AT+IOTMOD=0  ~/~/ 0 eMTC  1 NB-IoT  2 eMTC and NB-IoT
... ... @@ -191,23 +191,18 @@
191 191  
192 192  == 3.1 General UDP Connection ==
193 193  
194 -
195 195  The NB-IoT Sensor can send packet to server use UDP protocol.
196 196  
197 -
198 198  === 3.1.1 Simulate UDP Connection by PC tool ===
199 199  
200 -
201 201  We can use PC tool to simulate UDP connection to make sure server works ok.
202 202  
203 -[[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"]]
204 204  
205 -
206 206  === 3.1.2 Configure NB-IoT Sensor ===
207 207  
208 208  ==== 3.1.2.1 AT Commands ====
209 209  
210 -
211 211  (% style="color:blue" %)**AT Commands:**
212 212  
213 213  * (% style="color:#037691" %)**AT+PRO=2,0**  (%%) ~/~/ Set to use UDP protocol to uplink ,Payload Type select Hex payload
... ... @@ -216,16 +216,12 @@
216 216  
217 217  [[image:image-20240819102802-1.png]]
218 218  
219 -
220 220  ==== 3.1.2.2 Uplink Example ====
221 221  
210 +[[image:image-20240819105418-8.png||height="671" width="1414"]]
222 222  
223 -[[image:image-20240819105418-8.png||height="611" width="1287"]]
224 -
225 -
226 226  == 3.2 General COAP Connection ==
227 227  
228 -
229 229  The NB-IoT Sensor can send packet to server use COAP protocol.
230 230  
231 231  Below are the commands.
... ... @@ -236,21 +236,18 @@
236 236  
237 237  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5683** (%%) ~/~/ Set COAP server address and port
238 238  
239 -* (% style="color:#037691" %)**AT+URI1=11,"i"**  (%%) ~/~/  Configure CoAP Message Options
224 +* (% style="color:#037691" %)**AT+URI1=11,"I"**  (%%) ~/~/  Configure CoAP Message Options
240 240  * (% style="color:#037691" %)**AT+URI2=11,"aaa05e26-4d6d-f01b-660e-1d8de4a3bfe1"**    (%%) ~/~/ Configure CoAP Message Options
241 241  
242 242  [[image:image-20240819103212-2.png]]
243 243  
244 -
245 245  === 3.2.1 Uplink Example ===
246 246  
247 -
248 248  [[image:image-20240819103909-4.png||height="453" width="955"]]
249 249  
250 250  
251 251  == 3.2 General MQTT Connection ==
252 252  
253 -
254 254  The NB-IoT Sensor can send packet to server use MQTT protocol.
255 255  
256 256  Below are the commands.
... ... @@ -278,12 +278,10 @@
278 278  
279 279  (% 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.**
280 280  
281 -
282 282  == 3.3 [[ThingSpeak>>url:https://thingspeak.com/]] (via MQTT) ==
283 283  
284 284  === 3.3.1 Get MQTT Credentials ===
285 285  
286 -
287 287  [[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.
288 288  
289 289  [[image:image-20240819173602-1.png||height="401" width="743"]]
... ... @@ -290,12 +290,10 @@
290 290  
291 291  [[image:image-20240819173706-3.png||height="595" width="597"]]
292 292  
293 -
294 294  === 3.3.2 Simulate with MQTT.fx ===
295 295  
296 296  ==== 3.3.2.1 Establish MQTT Connection ====
297 297  
298 -
299 299  After we got MQTT Credentials, we can first simulate with PC tool MQTT.fx tool to see if the Credentials and settings are fine.
300 300  
301 301  [[image:image-20240819173826-4.png||height="534" width="734"]]
... ... @@ -312,7 +312,6 @@
312 312  
313 313  ==== 3.3.2.2 Publish Data to ThingSpeak Channel ====
314 314  
315 -
316 316  [[image:image-20240819174033-5.png]]
317 317  
318 318  [[image:image-20240819174209-6.png]]
... ... @@ -329,12 +329,10 @@
329 329  
330 330  [[image:image-20240819174314-7.png||height="469" width="785"]]
331 331  
332 -
333 333  === 3.3.3 Configure NB-IoT Sensor for connection ===
334 334  
335 335  ==== 3.3.3.1 AT Commands: ====
336 336  
337 -
338 338  In the NB-IoT, we can run below commands so to publish the channels like MQTT.fx
339 339  
340 340  * (% style="color:blue" %)**AT+PRO=3,1** (%%) ~/~/ Set to use ThingSpeak Server and Related Payload
... ... @@ -351,7 +351,6 @@
351 351  
352 352  ==== 3.3.3.2 Uplink Examples ====
353 353  
354 -
355 355  [[image:image-20240819174540-8.png]]
356 356  
357 357  For SE01-NB
... ... @@ -376,10 +376,8 @@
376 376  
377 377  For SN50V3-NB
378 378  
379 -
380 380  ==== 3.3.3.3 Map fields to sensor value ====
381 381  
382 -
383 383  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.
384 384  
385 385  [[image:image-20240819174610-9.png]]
... ... @@ -388,25 +388,25 @@
388 388  
389 389  Below is the NB-IoT Product Table show the mapping.
390 390  
391 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:1353.82px" %)
392 -|(% 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
393 -|(% 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" %)
394 -|(% 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" %)
395 -|(% 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" %)
396 -|(% 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" %)
397 -|(% 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" %)
398 -|(% 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" %)
399 -|(% 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" %)
400 -|(% 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" %)
401 -|(% 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" %)
402 -|(% 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" %)
403 -|(% 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
404 -|(% 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" %)
405 -|(% 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" %)
406 -|(% 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" %)
407 -|(% 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" %)
408 -|(% 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" %)
409 -|(% 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" %)
410 410  
411 411  == 3.4 [[Datacake>>https://datacake.co/]] ==
412 412  
... ... @@ -424,7 +424,6 @@
424 424  
425 425  ==== 3.4.1.1 Create Device ====
426 426  
427 -
428 428  (% style="color:blue" %)**Add Device**(%%) in DataCake.
429 429  
430 430  [[image:image-20240820110003-1.png]]
... ... @@ -443,12 +443,10 @@
443 443  
444 444  [[image:image-20240820110114-6.png]]
445 445  
446 -
447 447  === 3.4.2 For Device already registered in DataCake before shipped ===
448 448  
449 449  ==== 3.4.2.1 Scan QR Code to get the device info ====
450 450  
451 -
452 452  Users can use their phones or computers to scan QR codes to obtain device data information.
453 453  
454 454  [[image:image-20240820110129-7.png]]
... ... @@ -455,41 +455,32 @@
455 455  
456 456  [[image:image-20240820110218-9.png]]
457 457  
458 -
459 459  ==== 3.4.2.2 Claim Device to User Account ====
460 460  
461 -
462 462  By Default, the device is registered in Dragino's DataCake Account. User can Claim it to his account.
463 463  
464 -
465 465  === 3.4.3 Manual Add Decoder in DataCake ( don't use the template in DataCake) ===
466 466  
467 -
468 468  **Step1: Add a device**
469 469  
470 470  [[image:image-20240820110235-10.png]][[image:image-20240129170024-1.png||height="330" width="900"]]
471 471  
472 -
473 473  **Step2: Choose your device type,please select dragino NB-IOT device**
474 474  
475 475  [[image:image-20240820110247-11.png]]
476 476  
477 -
478 478  **Step3: Choose to create a new device**
479 479  
480 480  [[image:image-20240820111016-12.png]]
481 481  
482 -
483 483  **Step4: Fill in the device ID of your NB device**
484 484  
485 485  [[image:image-20240820111101-13.png]]
486 486  
487 -
488 488  **Step5: Please select your device plan according to your needs and complete the creation of the device**
489 489  
490 490  [[image:image-20240820111113-14.png]]
491 491  
492 -
493 493  **Step6: Please add the decoder at the payload decoder of the device configuration.**
494 494  
495 495  **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]]
... ... @@ -498,12 +498,10 @@
498 498  
499 499  [[image:image-20240820111248-16.png]]
500 500  
501 -
502 502  **Step7: Add the output of the decoder as a field**
503 503  
504 504  [[image:image-20240820111259-17.png]]
505 505  
506 -
507 507  **Step8: Customize the dashboard and use fields as parameters of the dashboard**
508 508  
509 509  [[image:image-20240820111312-18.png]]
... ... @@ -512,10 +512,8 @@
512 512  
513 513  [[image:image-20240820111333-20.png]]
514 514  
515 -
516 516  === 3.4.4 For device have not configured to connect to DataCake ===
517 517  
518 -
519 519  (% class="lead" %)
520 520  Use AT command for connecting to DataCake
521 521  
... ... @@ -523,12 +523,10 @@
523 523  
524 524  (% style="color:blue" %)**AT+SERVADDR=67.207.76.90,4445**
525 525  
526 -
527 527  == 3.5 Node-Red (via MQTT) ==
528 528  
529 529  === 3.5.1 Configure [[Node-Red>>http://wiki.dragino.com/xwiki/bin/view/Main/Node-RED/]] ===
530 530  
531 -
532 532  Take S31-NB UDP protocol as an example.
533 533  
534 534  Dragino provides input flow examples for the sensors.
... ... @@ -559,10 +559,8 @@
559 559  
560 560  [[image:image-20240820111448-26.png]]
561 561  
562 -
563 563  === 3.5.2 Simulate Connection ===
564 564  
565 -
566 566  We have completed the configuration of UDP. We can try sending packets to node red.
567 567  
568 568  [[image:image-20240820111504-27.png]]
... ... @@ -569,10 +569,8 @@
569 569  
570 570  [[image:image-20240820111515-28.png]]
571 571  
572 -
573 573  === 3.5.3 Configure NB-IoT Sensors ===
574 574  
575 -
576 576  * (% style="color:#037691" %)**AT+PRO=3,0 or 3,5 ** (%%) **~/~/ hex format or json format**
577 577  * (% style="color:#037691" %)**AT+SUBTOPIC=<device name>or User Defined**
578 578  * (% style="color:#037691" %)**AT+PUBTOPIC=<device name>or User Defined**
... ... @@ -586,15 +586,12 @@
586 586  
587 587  ==== 3.6.1.1 Create Device ====
588 588  
589 -
590 590  Create a New Device in [[ThingsBoard>>url:https://thingsboard.cloud/]]. Record Device Name which is used for MQTT connection.
591 591  
592 592  [[image:image-20240820112210-29.png]]
593 593  
594 -
595 595  ==== 3.6.1.2 Create Uplink & Downlink Converter ====
596 596  
597 -
598 598  (% style="color:blue" %)**Uplink Converter**
599 599  
600 600  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.
... ... @@ -611,10 +611,8 @@
611 611  
612 612  (% style="color:red" %)**Note: Our device payload is already human readable data. Therefore, users do not need to write decoders. Simply create by default.**
613 613  
614 -
615 615  ==== 3.6.1.3 MQTT Integration Setup ====
616 616  
617 -
618 618  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**;
619 619  
620 620  [[image:image-20240820112247-32.png]]
... ... @@ -633,7 +633,6 @@
633 633  
634 634  [[image:image-20240820112330-35.png]]
635 635  
636 -
637 637  === 3.6.2 Simulate with MQTT.fx ===
638 638  
639 639  [[image:image-20240820112340-36.png]]
... ... @@ -640,10 +640,8 @@
640 640  
641 641  [[image:image-20240820112351-37.png]]
642 642  
643 -
644 644  === 3.6.3 Configure NB-IoT Sensor ===
645 645  
646 -
647 647  (% style="color:blue" %)**AT Commands**
648 648  
649 649  * (% style="color:#037691" %)**AT+PRO=3,3  **(%%)** **~/~/ Use MQTT to connect to ThingsBoard. Payload Type set to 3.
... ... @@ -666,82 +666,10 @@
666 666  
667 667  [[image:image-20240820112426-40.png]]
668 668  
611 +== 3.7 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
669 669  
670 -== 3.7 ThingsBoard.Cloud (via COAP) ==
613 +=== 3.7.1 Create device & Get Credentials ===
671 671  
672 -=== 3.7.1 Configure ThingsBoard ===
673 -
674 -==== 3.7.1.1 Create Uplink & Downlink Converter ====
675 -
676 -
677 -(% style="color:blue" %)**Uplink Converter**
678 -
679 -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.
680 -
681 -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.
682 -
683 -[[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"]]
684 -
685 -
686 -(% style="color:blue" %)**Downlink Converter**
687 -
688 -The Downlink converter transforming outgoing RPC message and then the Integration sends it to external COAP broker.
689 -
690 -[[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"]]
691 -
692 -
693 -==== 3.7.1.2 COAP Integration Setup ====
694 -
695 -
696 -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" %);
697 -
698 -[[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"]]
699 -
700 -
701 -The next steps is to add the recently created uplink converters;
702 -
703 -[[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"]]
704 -
705 -
706 -==== 3.7.1.3 Add COAP Integration ====
707 -
708 -[[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"]]
709 -
710 -
711 -=== 3.7.2 Node Configuration(Example: Connecting to the Thingsboard platform) ===
712 -
713 -==== 3.7.2.1 Instruction Description ====
714 -
715 -
716 -* AT+PRO=1,0(HEX format uplink)  &AT+PRO=1,5(JSON format uplink)
717 -* AT+SERVADDR=COAP Server Address,5683
718 -
719 -Example: AT+SERVADDR=int.thingsboard.cloud,5683(The address is automatically generated when the COAP integration is created)
720 -
721 -[[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"]]
722 -
723 -Note:The port for the COAP protocol has been fixed to 5683
724 -
725 -
726 -* AT+URI1=11,"i"
727 -* AT+URI2=11,"Needs to be consistent with the CoAP endpoint URL in the platform"
728 -*
729 -
730 --CB devices using a (% style="color:red" %)**BG95-M2**(%%) module, you need to configure (% style="color:red" %)**TWO**(%%) URL commands,
731 -
732 -e.g.
733 -
734 -* AT+URI1=11, "i"
735 -* AT+URI2=11,"faaaa241f-af4a-b780-4468-c671bb574858"
736 -
737 -[[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"]]
738 -
739 -
740 -== 3.8 [[Tago.io>>url:https://admin.tago.io/]] (via MQTT) ==
741 -
742 -=== 3.8.1 Create device & Get Credentials ===
743 -
744 -
745 745  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.
746 746  
747 747  [[image:image-20240820112516-41.png]]
... ... @@ -788,9 +788,8 @@
788 788  
789 789  * (% style="color:#037691" %)**AT+PWD=“Your device token”**
790 790  
791 -=== 3.8.2 Simulate with MQTT.fx ===
661 +=== 3.7.2 Simulate with MQTT.fx ===
792 792  
793 -
794 794  [[image:image-20240820112552-44.png]]
795 795  
796 796  [[image:image-20240820112604-45.png]]
... ... @@ -801,23 +801,19 @@
801 801  
802 802  [[image:image-20240820112626-47.png]]
803 803  
673 +=== 3.7.3 tago data ===
804 804  
805 -=== 3.8.3 tago data ===
806 -
807 -
808 808  [[image:image-20240820112637-48.png]]
809 809  
810 810  [[image:image-20240820112647-49.png]]
811 811  
679 +== 3.8 TCP Connection ==
812 812  
813 -== 3.9 TCP Connection ==
814 -
815 -
816 816  (% style="color:blue" %)**AT command:**
817 817  
818 818  * (% style="color:#037691" %)**AT+PRO=4,0   ** (%%) ~/~/ Set to use TCP protocol to uplink(HEX format)
819 819  
820 -* (% 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)
821 821  
822 822  * (% style="color:#037691" %)**AT+SERVADDR=120.24.4.116,5600 ** (%%) ~/~/ to set TCP server address and port
823 823  
... ... @@ -829,18 +829,16 @@
829 829  
830 830  [[image:image-20240820112716-51.png]]
831 831  
697 +== 3.9 AWS Connection ==
832 832  
833 -== 3.10 AWS Connection ==
834 -
835 -
836 836  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]]
837 837  
701 += =
838 838  
839 839  = 4. COAP/UDP/MQTT/TCP downlink =
840 840  
841 841  == 4.1 MQTT (via MQTT.fx) ==
842 842  
843 -
844 844  Configure MQTT connections properly and send downlink commands to configure nodes through the Publish function of MQTT.fx//.//
845 845  
846 846  **1.** Configure node MQTT connection (via MQTT.fx):
... ... @@ -863,12 +863,10 @@
863 863  
864 864  [[image:image-20240820112732-52.png]][[image:image-20240820112758-53.png]]
865 865  
866 -
867 867  **2. **When the node uplink packets, we can observe the data in MQTT.fx.
868 868  
869 869  [[image:image-20240820112813-54.png]]
870 870  
871 -
872 872  **3. **The downlink command can be successfully sent only when the downlink port is open.
873 873  
874 874   The downlink port is opened for about 3 seconds after uplink packets are sent.
... ... @@ -884,7 +884,6 @@
884 884  
885 885  == 4.2 UDP (via Thingseye) ==
886 886  
887 -
888 888  (% 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/]])
889 889  
890 890  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)
... ... @@ -914,30 +914,26 @@
914 914  
915 915  = 5. GPS positioning function =
916 916  
917 -== 1. Turn on GPS function ==
777 +=== 1. Turn on GPS function ===
918 918  
919 -
920 920  (% class="wikigeneratedid" %)
921 -AT+GPS=1 or 0  ~/~/ GPS function on or off
780 +AT+GPS=1 or 0  ~/~/GPS function on or off
922 922  
923 923  
924 -== 2. Extend the time to turn on GNSS ==
783 +=== 2.Extend the time to turn on GNSS ===
925 925  
785 +AT+GNSST=30  ~/~/GPS search for positioning information for 30 seconds
926 926  
927 -AT+GNSST=30  ~/~/ GPS search for positioning information for 30 seconds
928 928  
788 +=== 3.Get or set GPS positioning interval in units of hour ===
929 929  
930 -== 3. Get or set GPS positioning interval in units of hour ==
790 +AT+GTDC=24  ~/~/The device will activate GPS positioning every 24 hours
931 931  
932 932  
933 -AT+GTDC=24  ~/~/ The device will activate GPS positioning every 24 hours
793 += 5. FAQ =
934 934  
795 +== 5.1 What is the usage of Multi Sampling and One Uplink? ==
935 935  
936 -= 6. FAQ =
937 -
938 -== 6.1 What is the usage of Multi Sampling and One Uplink? ==
939 -
940 -
941 941  The NB series has the feature for Multi Sampling and one uplink. See one of them
942 942  
943 943  [[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]]
... ... @@ -952,9 +952,8 @@
952 952  1*. **AT+TDC=7200** ~/~/ Uplink every 2 hours.
953 953  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.
954 954  
955 -== 6.2 Why the uplink JSON format is not standard? ==
811 +== 5.2 Why the uplink JSON format is not standard? ==
956 956  
957 -
958 958  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.
959 959  
960 960  The firmware version released after 2024, Mar will use change back to use Json format. Detail please check changelog.
... ... @@ -961,12 +961,10 @@
961 961  
962 962  [[image:image-20240820112848-57.png]]
963 963  
819 += 6. Trouble Shooting: =
964 964  
965 -= 7. Trouble Shooting: =
821 +== 6.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
966 966  
967 -== 7.1 Checklist for debuging Network Connection issue. Signal Strenght:99 issue. ==
968 -
969 -
970 970  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.
971 971  
972 972  If end device successfully attached NB-IoT Network, User can normally see the signal strengh as below (between 0~~31)
... ... @@ -989,16 +989,14 @@
989 989  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.
990 990  
991 991  
992 -== (% 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?(%%) ==
993 993  
994 -
995 995  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.
996 996  
997 997  [[image:image-20240820113015-60.png]]
998 998  
851 +== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)6.3 What is the Downlink Command by the -CB device?(%%) ==
999 999  
1000 -== (% data-sider-select-id="765eceff-93b1-40ee-800b-b7b7d022ef8a" %)7.3 What is the Downlink Command by the -CB device?(%%) ==
1001 -
1002 1002  (% data-sider-select-id="bb6e9353-0c3f-473c-938d-4b416c9a03e6" %)
1003 1003  === UDP: ===
1004 1004  
... ... @@ -1008,7 +1008,6 @@
1008 1008  
1009 1009  {AT+TDC=300}
1010 1010  
1011 -
1012 1012  (% data-sider-select-id="90b80f1a-e924-4c8a-afc5-4429e019a657" %)
1013 1013  === MQTT: ===
1014 1014  
... ... @@ -1051,7 +1051,7 @@
1051 1051  [[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/]]
1052 1052  
1053 1053  
1054 -== 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? ==
1055 1055  
1056 1056  
1057 1057  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.
... ... @@ -1064,31 +1064,28 @@
1064 1064  
1065 1065  (% style="color:blue" %)**AT Command: AT+GDNS**
1066 1066  
1067 -**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.
1068 1068  
1069 -**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.
1070 1070  
1071 1071  (% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
1072 1072  
1073 1073  Example:
1074 1074  
1075 -[[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"]]
1076 1076  
1077 1077  
1078 -== 7.5 GPS debugging ==
928 +== 6.5 GPS debugging ==
1079 1079  
1080 1080  
1081 1081  Indoor GPS signal is very weak, **outdoor** positioning is generally recommended.
1082 1082  
1083 -[[image:image-20240903104250-9.png||height="275" width="614"]]
933 +[[image:image-20240903100832-4.png||height="268" width="580"]]
1084 1084  
1085 1085  
1086 -[[image:image-20240903104431-10.png||height="291" width="621"]]
936 +=== 6.5.1 GPS commands ===
1087 1087  
1088 1088  
1089 -=== 7.5.1 GPS commands ===
1090 -
1091 -
1092 1092  The following are three related AT commands that introduce GPS functions.
1093 1093  
1094 1094  * **Turn on/off GPS**
... ... @@ -1135,10 +1135,10 @@
1135 1135  
1136 1136  Example: 24 hours:  24(D)=0x18(H)
1137 1137  
1138 -Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
985 + Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
1139 1139  
1140 1140  
1141 -=== 7.5.2 GPS workflow ===
988 +=== 6.5.2 GPS workflow ===
1142 1142  
1143 1143  
1144 1144  The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
... ... @@ -1156,15 +1156,11 @@
1156 1156   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.
1157 1157  
1158 1158  
1159 -=== 7.5.3 GPS debugging methods ===
1006 +=== 6.5.3 GPS debugging methods ===
1160 1160  
1161 1161  
1162 -In summary, we can deduce the methods of debugging GPS:
1009 +In summary, we can deduce the method of debugging GPS:
1163 1163  
1164 -* **Check whether the GPS function is enabled.**
1165 -
1166 -[[image:image-20240903102327-5.png||height="271" width="529"]]
1167 -
1168 1168  * **Check whether the GPS antenna is loose**.
1169 1169  
1170 1170  If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
... ... @@ -1177,24 +1177,8 @@
1177 1177  
1178 1178  If the location fails, users can extend the location time.
1179 1179  
1180 -[[image:image-20240903102641-8.png||height="303" width="600"]]
1181 1181  
1182 1182  
1183 -== 7.6 CB device configuration TCP/IP failed ==
1184 1184  
1185 -[[image:image-20250113103816-1.png]]
1186 1186  
1187 -**Use AT+IPTYPE=? to check the IPTYPE configuration.
1188 -AT+IPTYPE can only be configured as 1 or 2.
1189 -If it is configured otherwise, this error will occur**
1190 -
1191 -
1192 -== 7.7 How to get the debug log for further analyze? ==
1193 -
1194 -
1195 -CB model use the same debug instruction as NB model. Please check this link:
1196 -
1197 -**[[How to Get Full Log>>https://wiki.dragino.com/xwiki/bin/view/Main/General%20Configure%20to%20Connect%20to%20IoT%20server%20for%20-NB%20%26%20-NS%20NB-IoT%20models/#H6.6Howtogetthedebuglogforfurtheranalyze3F]]**?
1198 -
1199 -
1200 1200  
image-20240903104431-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -49.2 KB
Content
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