Last modified by Bei Jinggeng on 2024/05/31 09:53

From version 109.1
edited by Mengting Qiu
on 2024/04/02 16:59
Change comment: There is no comment for this version
To version 100.3
edited by Xiaoling
on 2022/08/08 16:07
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 -- NB-IoT Distance Detect Sensor User Manual
1 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.ting
1 +XWiki.Xiaoling
Content
... ... @@ -1,5 +3,3 @@
1 -
2 -
3 3  (% style="text-align:center" %)
4 4  [[image:image-20220709085040-1.png||height="542" width="524"]]
5 5  
... ... @@ -55,6 +55,7 @@
55 55  [[image:1657327959271-447.png]]
56 56  
57 57  
56 +
58 58  == 1.2 ​ Features ==
59 59  
60 60  
... ... @@ -71,6 +71,8 @@
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
73 +
74 +
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -81,12 +81,12 @@
81 81  
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
84 -* B1 @H-FDD: 2100MHz
85 -* B3 @H-FDD: 1800MHz
86 -* B8 @H-FDD: 900MHz
87 -* B5 @H-FDD: 850MHz
88 -* B20 @H-FDD: 800MHz
89 -* B28 @H-FDD: 700MHz
85 +* - B1 @H-FDD: 2100MHz
86 +* - B3 @H-FDD: 1800MHz
87 +* - B8 @H-FDD: 900MHz
88 +* - B5 @H-FDD: 850MHz
89 +* - B20 @H-FDD: 800MHz
90 +* - B28 @H-FDD: 700MHz
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -101,6 +101,8 @@
101 101  * STOP Mode: 10uA @ 3.3v
102 102  * Max transmit power: 350mA@3.3v
103 103  
105 +
106 +
104 104  == ​1.4  Applications ==
105 105  
106 106  
... ... @@ -121,6 +121,7 @@
121 121  [[image:1657328609906-564.png]]
122 122  
123 123  
127 +
124 124  = 2.  Use NDDS75 to communicate with IoT Server =
125 125  
126 126  == 2.1  How it works ==
... ... @@ -145,8 +145,10 @@
145 145  
146 146  )))
147 147  
152 +
148 148  == 2.2 ​ Configure the NDDS75 ==
149 149  
155 +
150 150  === 2.2.1 Test Requirement ===
151 151  
152 152  
... ... @@ -166,6 +166,7 @@
166 166  [[image:1657328756309-230.png]]
167 167  
168 168  
175 +
169 169  === 2.2.2 Insert SIM card ===
170 170  
171 171  
... ... @@ -177,9 +177,11 @@
177 177  User need to take out the NB-IoT module and insert the SIM card like below:
178 178  )))
179 179  
187 +
180 180  [[image:1657328884227-504.png]]
181 181  
182 182  
191 +
183 183  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
184 184  
185 185  
... ... @@ -191,16 +191,15 @@
191 191  
192 192  [[image:image-20220709092052-2.png]]
193 193  
203 +**Connection:**
194 194  
195 -(% style="color:blue" %)**Connection:**
205 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
196 196  
197 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
207 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
198 198  
199 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
209 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
200 200  
201 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
202 202  
203 -
204 204  In the PC, use below serial tool settings:
205 205  
206 206  * Baud:  (% style="color:green" %)**9600**
... ... @@ -215,12 +215,12 @@
215 215  
216 216  [[image:1657329814315-101.png]]
217 217  
218 -
219 219  (((
220 -(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
227 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
221 221  )))
222 222  
223 223  
231 +
224 224  === 2.2.4 Use CoAP protocol to uplink data ===
225 225  
226 226  
... ... @@ -235,18 +235,14 @@
235 235  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
236 236  )))
237 237  * (((
238 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
246 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
239 239  )))
240 240  * (((
241 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
242 -
243 -
249 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
244 244  )))
245 245  
246 246  (((
247 247  For parameter description, please refer to AT command set
248 -
249 -
250 250  )))
251 251  
252 252  [[image:1657330452568-615.png]]
... ... @@ -259,11 +259,13 @@
259 259  [[image:1657330472797-498.png]]
260 260  
261 261  
266 +
262 262  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
263 263  
264 264  
265 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
266 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
270 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
271 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
272 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
267 267  
268 268  [[image:1657330501006-241.png]]
269 269  
... ... @@ -271,16 +271,17 @@
271 271  [[image:1657330533775-472.png]]
272 272  
273 273  
280 +
274 274  === 2.2.6 Use MQTT protocol to uplink data ===
275 275  
276 276  
277 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
278 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
279 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
280 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
281 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
282 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
283 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
284 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
285 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
286 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
287 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
288 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
289 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
290 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
284 284  
285 285  [[image:1657249978444-674.png]]
286 286  
... ... @@ -293,11 +293,12 @@
293 293  )))
294 294  
295 295  
303 +
296 296  === 2.2.7 Use TCP protocol to uplink data ===
297 297  
298 298  
299 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
300 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
307 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
301 301  
302 302  [[image:image-20220709093918-1.png]]
303 303  
... ... @@ -305,109 +305,78 @@
305 305  [[image:image-20220709093918-2.png]]
306 306  
307 307  
316 +
308 308  === 2.2.8 Change Update Interval ===
309 309  
310 310  
311 311  User can use below command to change the (% style="color:green" %)**uplink interval**.
312 312  
313 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
322 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
314 314  
315 315  (((
316 -
317 -
318 318  (% style="color:red" %)**NOTE:**
326 +)))
319 319  
328 +(((
320 320  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
321 -
322 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
323 323  )))
324 324  
325 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
326 326  
327 327  
328 328  == 2.3  Uplink Payload ==
329 329  
330 -=== 2.3.1  Before Firmware v1.3.2 ===
331 331  
332 -
333 333  In this mode, uplink payload includes in total 14 bytes
334 334  
335 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
336 -|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
339 +
340 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
341 +|=(% style="width: 60px;" %)(((
337 337  **Size(bytes)**
338 -)))|=(% style="width: 61px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**
339 -|(% style="width:97px" %)Value|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
343 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
344 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
340 340  
341 341  (((
342 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
347 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
343 343  )))
344 344  
345 345  
346 346  [[image:1657331036973-987.png]]
347 347  
348 -
349 -The payload is **ASCII** string, representative same HEX:
350 -
351 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
352 -
353 -**where :**
354 -
355 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
356 -
357 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
358 -
359 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
360 -
361 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
362 -
363 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
364 -
365 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
366 -
367 -=== 2.3.2  Since firmware v1.3.2 ===
368 -
369 -
370 -In this mode, uplink payload includes 69 bytes in total by default.
371 -
372 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
373 -
374 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
375 -|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:25px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:70px" %)**4**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:65px" %)**4**
376 -|(% style="width:95px" %)Value|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
377 -
378 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
379 -
380 -[[image:image-20220908175246-1.png]]
381 -
382 -
353 +(((
383 383  The payload is ASCII string, representative same HEX:
355 +)))
384 384  
385 -**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
357 +(((
358 +0x72403155615900640c6c19029200 where:
359 +)))
386 386  
387 -**where:**
361 +* (((
362 +Device ID: 0x724031556159 = 724031556159
363 +)))
364 +* (((
365 +Version: 0x0064=100=1.0.0
366 +)))
388 388  
389 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
368 +* (((
369 +BAT: 0x0c6c = 3180 mV = 3.180V
370 +)))
371 +* (((
372 +Signal: 0x19 = 25
373 +)))
374 +* (((
375 +Distance: 0x0292= 658 mm
376 +)))
377 +* (((
378 +Interrupt: 0x00 = 0
390 390  
391 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
392 392  
393 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
394 394  
395 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
382 +
383 +)))
396 396  
397 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
398 -
399 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
400 -
401 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
402 -
403 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
404 -
405 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
406 -
407 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
408 -
409 409  == 2.4  Payload Explanation and Sensor Interface ==
410 410  
387 +
411 411  === 2.4.1  Device ID ===
412 412  
413 413  
... ... @@ -417,12 +417,10 @@
417 417  
418 418  (((
419 419  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
420 -
421 -
422 422  )))
423 423  
424 424  (((
425 -(% style="color:blue" %)**Example :**
400 +**Example:**
426 426  )))
427 427  
428 428  (((
... ... @@ -430,22 +430,11 @@
430 430  )))
431 431  
432 432  (((
433 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
408 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
434 434  )))
435 435  
436 436  
437 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
438 438  
439 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
440 -
441 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
442 -
443 -
444 -(% style="color:blue" %)**Example :**
445 -
446 -AT+DEUI=868411056754138
447 -
448 -
449 449  === 2.4.2  Version Info ===
450 450  
451 451  
... ... @@ -458,6 +458,7 @@
458 458  )))
459 459  
460 460  
425 +
461 461  === 2.4.3  Battery Info ===
462 462  
463 463  
... ... @@ -470,6 +470,7 @@
470 470  )))
471 471  
472 472  
438 +
473 473  === 2.4.4  Signal Strength ===
474 474  
475 475  
... ... @@ -502,6 +502,7 @@
502 502  )))
503 503  
504 504  
471 +
505 505  === 2.4.5  Distance ===
506 506  
507 507  
... ... @@ -508,13 +508,23 @@
508 508  Get the distance. Flat object range 280mm - 7500mm.
509 509  
510 510  (((
511 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
478 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
512 512  )))
513 513  
514 514  (((
482 +(((
483 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
484 +)))
485 +)))
486 +
487 +(((
515 515  
516 516  )))
517 517  
491 +(((
492 +
493 +)))
494 +
518 518  === 2.4.6  Digital Interrupt ===
519 519  
520 520  
... ... @@ -527,7 +527,7 @@
527 527  )))
528 528  
529 529  (((
530 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/  (more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
507 +(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
531 531  )))
532 532  
533 533  
... ... @@ -535,8 +535,9 @@
535 535  The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
536 536  )))
537 537  
515 +
538 538  (((
539 -**Example:**
517 +Example:
540 540  )))
541 541  
542 542  (((
... ... @@ -548,6 +548,7 @@
548 548  )))
549 549  
550 550  
529 +
551 551  === 2.4.7  ​+5V Output ===
552 552  
553 553  
... ... @@ -555,6 +555,7 @@
555 555  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
556 556  )))
557 557  
537 +
558 558  (((
559 559  The 5V output time can be controlled by AT Command.
560 560  )))
... ... @@ -568,17 +568,15 @@
568 568  )))
569 569  
570 570  
551 +
571 571  == 2.5  Downlink Payload ==
572 572  
573 573  
574 574  By default, NDDS75 prints the downlink payload to console port.
575 575  
576 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
577 -|(% style="background-color:#4f81bd; color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:56px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:151px" %)**Downlink payload size(bytes)**
578 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
579 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
580 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
557 +[[image:image-20220709100028-1.png]]
581 581  
559 +
582 582  (((
583 583  (% style="color:blue" %)**Examples:**
584 584  )))
... ... @@ -623,85 +623,126 @@
623 623  )))
624 624  
625 625  
626 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
627 627  
605 +== 2.6  ​LED Indicator ==
628 628  
629 -(% style="color:blue" %)** ➢ AT Command:**
630 630  
631 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
608 +The NDDS75 has an internal LED which is to show the status of different state.
632 632  
633 -² When min=0, and max≠0, Alarm higher than max
634 634  
635 -² When min≠0, and max=0, Alarm lower than min
611 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
612 +* Then the LED will be on for 1 second means device is boot normally.
613 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
614 +* For each uplink probe, LED will be on for 500ms.
636 636  
637 -² When min≠0 and max≠0, Alarm higher than max or lower than min
616 +(((
617 +
618 +)))
638 638  
639 639  
640 -(% style="color:blue" %)** Example:**
641 641  
642 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
622 +== 2.7  ​Firmware Change Log ==
643 643  
644 644  
645 -== 2.7  Set the number of data to be uploaded and the recording time ==
625 +(((
626 +Download URL & Firmware Change log
627 +)))
646 646  
629 +(((
630 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
631 +)))
647 647  
648 -(% style="color:blue" %)** ➢ AT Command:**
649 649  
650 -* (% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
651 -* (% style="color:#037691" %)** AT+NOUD=8**             (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
634 +(((
635 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
636 +)))
652 652  
653 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
654 654  
655 -[[image:image-20221009001114-1.png||height="687" width="955"]]
656 656  
640 +== 2.8  ​Battery Analysis ==
657 657  
658 -== 2.8  Read or Clear cached data ==
642 +=== 2.8.1  ​Battery Type ===
659 659  
660 660  
661 -(% style="color:blue" %)** ➢ AT Command:**
645 +(((
646 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
647 +)))
662 662  
663 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
664 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
649 +(((
650 +The battery is designed to last for several years depends on the actually use environment and update interval. 
651 +)))
665 665  
666 -[[image:image-20220908175333-2.png]]
653 +(((
654 +The battery related documents as below:
655 +)))
667 667  
657 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
658 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
659 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
668 668  
669 -== 2.9  ​LED Indicator ==
661 +(((
662 +[[image:image-20220709101450-2.png]]
663 +)))
670 670  
671 671  
672 -The NDDS75 has an internal LED which is to show the status of different state.
673 673  
667 +=== 2.8.2  Power consumption Analyze ===
674 674  
675 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
676 -* Then the LED will be on for 1 second means device is boot normally.
677 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
678 -* For each uplink probe, LED will be on for 500ms.
679 679  
680 680  (((
681 -
671 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
682 682  )))
683 683  
684 684  
685 -== 2.10  ​Firmware Change Log ==
675 +(((
676 +Instruction to use as below:
677 +)))
686 686  
679 +(((
680 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
681 +)))
687 687  
683 +
688 688  (((
689 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
685 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
690 690  )))
691 691  
688 +* (((
689 +Product Model
690 +)))
691 +* (((
692 +Uplink Interval
693 +)))
694 +* (((
695 +Working Mode
696 +)))
697 +
692 692  (((
693 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
699 +And the Life expectation in difference case will be shown on the right.
694 694  )))
695 695  
702 +[[image:image-20220709110451-3.png]]
696 696  
697 -== 2.11 Battery & Power Consumption ==
698 698  
699 699  
700 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
706 +=== 2.8.3  ​Battery Note ===
701 701  
702 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
703 703  
709 +(((
710 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
711 +)))
704 704  
713 +
714 +
715 +=== 2.8.4  Replace the battery ===
716 +
717 +
718 +(((
719 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
720 +)))
721 +
722 +
723 +
705 705  = 3. ​ Access NB-IoT Module =
706 706  
707 707  
... ... @@ -711,103 +711,91 @@
711 711  
712 712  (((
713 713  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
714 -
715 -
716 716  )))
717 717  
718 718  [[image:1657333200519-600.png]]
719 719  
720 720  
738 +
721 721  = 4.  Using the AT Commands =
722 722  
723 723  == 4.1  Access AT Commands ==
724 724  
725 725  
726 -See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
744 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
727 727  
728 728  
729 -AT+<CMD>?  :  Help on <CMD>
747 +AT+<CMD>?  : Help on <CMD>
730 730  
731 -AT+<CMD>         :  Run <CMD>
749 +AT+<CMD>         : Run <CMD>
732 732  
733 -AT+<CMD>=<value> :  Set the value
751 +AT+<CMD>=<value> : Set the value
734 734  
735 -AT+<CMD>=?  :  Get the value
753 +AT+<CMD>=?  : Get the value
736 736  
737 737  
738 738  (% style="color:#037691" %)**General Commands**(%%)      
739 739  
740 -AT  :  Attention       
758 +AT  : Attention       
741 741  
742 -AT?  :  Short Help     
760 +AT?  : Short Help     
743 743  
744 -ATZ  :  MCU Reset    
762 +ATZ  : MCU Reset    
745 745  
746 -AT+TDC  :  Application Data Transmission Interval
764 +AT+TDC  : Application Data Transmission Interval
747 747  
748 -AT+CFG  :  Print all configurations
766 +AT+CFG  : Print all configurations
749 749  
750 -AT+CFGMOD           :  Working mode selection
768 +AT+CFGMOD           : Working mode selection
751 751  
752 -AT+INTMOD            :  Set the trigger interrupt mode
770 +AT+INTMOD            : Set the trigger interrupt mode
753 753  
754 -AT+5VT  :  Set extend the time of 5V power  
772 +AT+5VT  : Set extend the time of 5V power  
755 755  
756 -AT+PRO  :  Choose agreement
774 +AT+PRO  : Choose agreement
757 757  
758 -AT+WEIGRE  :  Get weight or set weight to 0
776 +AT+WEIGRE  : Get weight or set weight to 0
759 759  
760 -AT+WEIGAP  :  Get or Set the GapValue of weight
778 +AT+WEIGAP  : Get or Set the GapValue of weight
761 761  
762 -AT+RXDL  :  Extend the sending and receiving time
780 +AT+RXDL  : Extend the sending and receiving time
763 763  
764 -AT+CNTFAC  :  Get or set counting parameters
782 +AT+CNTFAC  : Get or set counting parameters
765 765  
766 -AT+SERVADDR  :  Server Address
784 +AT+SERVADDR  : Server Address
767 767  
768 -AT+TR  :  Get or Set record time"
769 769  
770 -AT+APN     :  Get or set the APN
787 +(% style="color:#037691" %)**COAP Management**      
771 771  
772 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
789 +AT+URI            : Resource parameters
773 773  
774 -AT+DNSCFG  : Get or Set DNS Server
775 775  
776 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
792 +(% style="color:#037691" %)**UDP Management**
777 777  
778 -AT+NOUD  :  Get or Set the number of data to be uploaded
794 +AT+CFM          : Upload confirmation mode (only valid for UDP)
779 779  
780 -AT+CDP     :  Read or Clear cached data
781 781  
782 -AT+LDDSALARM :  Get or Set alarm of distance
783 -
784 -
785 -(% style="color:#037691" %)**COAP Management**      
786 -
787 -AT+URI            :  Resource parameters
788 -
789 -
790 -
791 791  (% style="color:#037691" %)**MQTT Management**
792 792  
793 -AT+CLIENT  :  Get or Set MQTT client
799 +AT+CLIENT               : Get or Set MQTT client
794 794  
795 -AT+UNAME  Get or Set MQTT Username
801 +AT+UNAME  : Get or Set MQTT Username
796 796  
797 -AT+PWD  :  Get or Set MQTT password
803 +AT+PWD                  : Get or Set MQTT password
798 798  
799 -AT+PUBTOPIC  Get or Set MQTT publish topic
805 +AT+PUBTOPIC  : Get or Set MQTT publish topic
800 800  
801 -AT+SUBTOPIC  Get or Set MQTT subscription topic
807 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
802 802  
803 803  
804 804  (% style="color:#037691" %)**Information**          
805 805  
806 -AT+FDR  :  Factory Data Reset
812 +AT+FDR  : Factory Data Reset
807 807  
808 -AT+PWORD  :  Serial Access Password
814 +AT+PWORD  : Serial Access Password
809 809  
810 810  
817 +
811 811  = ​5.  FAQ =
812 812  
813 813  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -826,6 +826,7 @@
826 826  )))
827 827  
828 828  
836 +
829 829  = 6.  Trouble Shooting =
830 830  
831 831  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -840,20 +840,17 @@
840 840  
841 841  )))
842 842  
851 +
843 843  == 6.2  AT Command input doesn't work ==
844 844  
845 845  
846 846  (((
847 847  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
857 +
858 +
848 848  )))
849 849  
850 850  
851 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
852 -
853 -
854 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
855 -
856 -
857 857  = 7. ​ Order Info =
858 858  
859 859  
... ... @@ -860,6 +860,11 @@
860 860  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
861 861  
862 862  
868 +(% class="wikigeneratedid" %)
869 +(((
870 +
871 +)))
872 +
863 863  = 8.  Packing Info =
864 864  
865 865  (((
... ... @@ -885,6 +885,7 @@
885 885  (((
886 886  
887 887  
898 +
888 888  
889 889  )))
890 890  
... ... @@ -892,5 +892,4 @@
892 892  
893 893  
894 894  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
895 -
896 896  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content