Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.22 >
edited by Xiaoling
on 2023/12/14 17:30
To version < 100.5 >
edited by Xiaoling
on 2022/08/22 14:39
>
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
Content
... ... @@ -16,6 +16,7 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 +
19 19  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 21  (((
... ... @@ -53,6 +53,7 @@
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
57 +
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -70,6 +70,8 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
75 +
76 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -78,15 +78,17 @@
78 78  * Supply Voltage: 2.1v ~~ 3.6v
79 79  * Operating Temperature: -40 ~~ 85°C
80 80  
85 +
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 -* B1 @H-FDD: 2100MHz
84 -* B3 @H-FDD: 1800MHz
85 -* B8 @H-FDD: 900MHz
86 -* B5 @H-FDD: 850MHz
87 -* B20 @H-FDD: 800MHz
88 -* B28 @H-FDD: 700MHz
88 +* - B1 @H-FDD: 2100MHz
89 +* - B3 @H-FDD: 1800MHz
90 +* - B8 @H-FDD: 900MHz
91 +* - B5 @H-FDD: 850MHz
92 +* - B20 @H-FDD: 800MHz
93 +* - B28 @H-FDD: 700MHz
89 89  
95 +
90 90  (% style="color:#037691" %)**Battery:**
91 91  
92 92  * Li/SOCI2 un-chargeable battery
... ... @@ -95,6 +95,7 @@
95 95  * Max continuously current: 130mA
96 96  * Max boost current: 2A, 1 second
97 97  
104 +
98 98  (% style="color:#037691" %)**Power Consumption**
99 99  
100 100  * STOP Mode: 10uA @ 3.3v
... ... @@ -101,6 +101,8 @@
101 101  * Max transmit power: 350mA@3.3v
102 102  
103 103  
111 +
112 +
104 104  == ​1.4  Applications ==
105 105  
106 106  
... ... @@ -115,6 +115,8 @@
115 115  ​
116 116  
117 117  
127 +
128 +
118 118  == 1.5  Pin Definitions ==
119 119  
120 120  
... ... @@ -121,8 +121,10 @@
121 121  [[image:1657328609906-564.png]]
122 122  
123 123  
135 +
124 124  = 2.  Use NDDS75 to communicate with IoT Server =
125 125  
138 +
126 126  == 2.1  How it works ==
127 127  
128 128  
... ... @@ -145,8 +145,10 @@
145 145  
146 146  )))
147 147  
161 +
148 148  == 2.2 ​ Configure the NDDS75 ==
149 149  
164 +
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  
184 +
169 169  === 2.2.2 Insert SIM card ===
170 170  
171 171  
... ... @@ -181,6 +181,7 @@
181 181  [[image:1657328884227-504.png]]
182 182  
183 183  
200 +
184 184  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
185 185  
186 186  
... ... @@ -193,13 +193,13 @@
193 193  [[image:image-20220709092052-2.png]]
194 194  
195 195  
196 -(% style="color:blue" %)**Connection:**
213 +**Connection:**
197 197  
198 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
215 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
217 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
219 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
203 203  
204 204  
205 205  In the PC, use below serial tool settings:
... ... @@ -222,6 +222,7 @@
222 222  )))
223 223  
224 224  
242 +
225 225  === 2.2.4 Use CoAP protocol to uplink data ===
226 226  
227 227  
... ... @@ -236,18 +236,14 @@
236 236  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
237 237  )))
238 238  * (((
239 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
257 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
240 240  )))
241 241  * (((
242 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
243 -
244 -
260 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
245 245  )))
246 246  
247 247  (((
248 248  For parameter description, please refer to AT command set
249 -
250 -
251 251  )))
252 252  
253 253  [[image:1657330452568-615.png]]
... ... @@ -256,20 +256,20 @@
256 256  
257 257  (((
258 258  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
259 -
260 -
261 261  )))
262 262  
263 263  [[image:1657330472797-498.png]]
264 264  
265 265  
278 +
266 266  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
267 267  
268 268  
269 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
270 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
271 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
282 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
283 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
284 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
272 272  
286 +
273 273  [[image:1657330501006-241.png]]
274 274  
275 275  
... ... @@ -276,17 +276,19 @@
276 276  [[image:1657330533775-472.png]]
277 277  
278 278  
293 +
279 279  === 2.2.6 Use MQTT protocol to uplink data ===
280 280  
281 281  
282 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
283 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
284 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
285 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
286 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
287 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
288 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
297 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
299 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
300 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
301 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
302 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
303 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
289 289  
305 +
290 290  [[image:1657249978444-674.png]]
291 291  
292 292  
... ... @@ -298,12 +298,14 @@
298 298  )))
299 299  
300 300  
317 +
301 301  === 2.2.7 Use TCP protocol to uplink data ===
302 302  
303 303  
304 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
305 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
321 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
322 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
306 306  
324 +
307 307  [[image:image-20220709093918-1.png]]
308 308  
309 309  
... ... @@ -310,41 +310,38 @@
310 310  [[image:image-20220709093918-2.png]]
311 311  
312 312  
331 +
313 313  === 2.2.8 Change Update Interval ===
314 314  
315 315  
316 316  User can use below command to change the (% style="color:green" %)**uplink interval**.
317 317  
318 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
337 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
319 319  
320 320  (((
321 -
322 -
323 323  (% style="color:red" %)**NOTE:**
341 +)))
324 324  
343 +(((
325 325  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
326 -
327 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
328 328  )))
329 329  
330 -(% 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).**
331 331  
332 332  
333 333  == 2.3  Uplink Payload ==
334 334  
335 -=== 2.3.1  Before Firmware v1.3.2 ===
336 336  
337 -
338 338  In this mode, uplink payload includes in total 14 bytes
339 339  
340 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
341 -|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)(((
354 +
355 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
356 +|=(% style="width: 60px;" %)(((
342 342  **Size(bytes)**
343 -)))|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 82px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 102px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
358 +)))|=(% 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 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"]]
345 345  
346 346  (((
347 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
362 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
348 348  )))
349 349  
350 350  
... ... @@ -351,70 +351,41 @@
351 351  [[image:1657331036973-987.png]]
352 352  
353 353  
354 -The payload is **ASCII** string, representative same HEX:
355 -
356 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
357 -
358 -**where :**
359 -
360 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
361 -
362 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
363 -
364 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
365 -
366 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
367 -
368 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
369 -
370 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
371 -
372 -
373 -=== 2.3.2  Since firmware v1.3.2 ===
374 -
375 -
376 -In this mode, uplink payload includes 69 bytes in total by default.
377 -
378 -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.
379 -
380 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:490px" %)
381 -|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**Size(bytes)**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**8**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:25px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**1**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:70px" %)**4**|(% style="background-color:#d9e2f3; color:#0070c0; width:40px" %)**2**|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**4**
382 -|(% 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.......
383 -
384 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
385 -
386 -[[image:image-20220908175246-1.png]]
387 -
388 -
369 +(((
389 389  The payload is ASCII string, representative same HEX:
371 +)))
390 390  
391 -**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 (%%)**
373 +(((
374 +0x72403155615900640c6c19029200 where:
375 +)))
392 392  
393 -**where:**
377 +* (((
378 +Device ID: 0x724031556159 = 724031556159
379 +)))
380 +* (((
381 +Version: 0x0064=100=1.0.0
382 +)))
394 394  
395 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
384 +* (((
385 +BAT: 0x0c6c = 3180 mV = 3.180V
386 +)))
387 +* (((
388 +Signal: 0x19 = 25
389 +)))
390 +* (((
391 +Distance: 0x0292= 658 mm
392 +)))
393 +* (((
394 +Interrupt: 0x00 = 0
396 396  
397 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
398 398  
399 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
400 400  
401 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
398 +
399 +)))
402 402  
403 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
404 -
405 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
406 -
407 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
408 -
409 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
410 -
411 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
412 -
413 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
414 -
415 -
416 416  == 2.4  Payload Explanation and Sensor Interface ==
417 417  
403 +
418 418  === 2.4.1  Device ID ===
419 419  
420 420  
... ... @@ -429,7 +429,7 @@
429 429  )))
430 430  
431 431  (((
432 -(% style="color:blue" %)**Example :**
418 +**Example:**
433 433  )))
434 434  
435 435  (((
... ... @@ -437,22 +437,11 @@
437 437  )))
438 438  
439 439  (((
440 -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.
426 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
441 441  )))
442 442  
443 443  
444 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
445 445  
446 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
447 -
448 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
449 -
450 -
451 -(% style="color:blue" %)**Example :**
452 -
453 -AT+DEUI=868411056754138
454 -
455 -
456 456  === 2.4.2  Version Info ===
457 457  
458 458  
... ... @@ -465,6 +465,7 @@
465 465  )))
466 466  
467 467  
443 +
468 468  === 2.4.3  Battery Info ===
469 469  
470 470  
... ... @@ -477,6 +477,7 @@
477 477  )))
478 478  
479 479  
456 +
480 480  === 2.4.4  Signal Strength ===
481 481  
482 482  
... ... @@ -509,6 +509,7 @@
509 509  )))
510 510  
511 511  
489 +
512 512  === 2.4.5  Distance ===
513 513  
514 514  
... ... @@ -515,13 +515,23 @@
515 515  Get the distance. Flat object range 280mm - 7500mm.
516 516  
517 517  (((
518 -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.**
496 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
519 519  )))
520 520  
521 521  (((
500 +(((
501 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
502 +)))
503 +)))
504 +
505 +(((
522 522  
523 523  )))
524 524  
509 +(((
510 +
511 +)))
512 +
525 525  === 2.4.6  Digital Interrupt ===
526 526  
527 527  
... ... @@ -534,7 +534,7 @@
534 534  )))
535 535  
536 536  (((
537 -(% 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]])**.**
525 +(% 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]])**.**
538 538  )))
539 539  
540 540  
... ... @@ -542,8 +542,9 @@
542 542  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.
543 543  )))
544 544  
533 +
545 545  (((
546 -**Example:**
535 +Example:
547 547  )))
548 548  
549 549  (((
... ... @@ -555,6 +555,7 @@
555 555  )))
556 556  
557 557  
547 +
558 558  === 2.4.7  ​+5V Output ===
559 559  
560 560  
... ... @@ -562,12 +562,17 @@
562 562  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
563 563  )))
564 564  
555 +
565 565  (((
566 566  The 5V output time can be controlled by AT Command.
558 +
559 +
567 567  )))
568 568  
569 569  (((
570 570  (% style="color:blue" %)**AT+5VT=1000**
564 +
565 +
571 571  )))
572 572  
573 573  (((
... ... @@ -575,17 +575,15 @@
575 575  )))
576 576  
577 577  
573 +
578 578  == 2.5  Downlink Payload ==
579 579  
580 580  
581 581  By default, NDDS75 prints the downlink payload to console port.
582 582  
583 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
584 -|(% style="background-color:#d9e2f3; color:#0070c0; width:208px" %)**Downlink Control Type**|(% style="background-color:#d9e2f3; color:#0070c0; width:56px" %)**FPort**|(% style="background-color:#d9e2f3; color:#0070c0; width:100px" %)**Type Code**|(% style="background-color:#d9e2f3; color:#0070c0; width:154px" %)**Downlink payload size(bytes)**
585 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
586 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
587 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
579 +[[image:image-20220709100028-1.png]]
588 588  
581 +
589 589  (((
590 590  (% style="color:blue" %)**Examples:**
591 591  )))
... ... @@ -630,85 +630,126 @@
630 630  )))
631 631  
632 632  
633 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
634 634  
627 +== 2.6  ​LED Indicator ==
635 635  
636 -(% style="color:blue" %)** ➢ AT Command:**
637 637  
638 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
630 +The NDDS75 has an internal LED which is to show the status of different state.
639 639  
640 -² When min=0, and max≠0, Alarm higher than max
641 641  
642 -² When min≠0, and max=0, Alarm lower than min
633 +* 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)
634 +* Then the LED will be on for 1 second means device is boot normally.
635 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
636 +* For each uplink probe, LED will be on for 500ms.
643 643  
644 -² When min≠0 and max≠0, Alarm higher than max or lower than min
638 +(((
639 +
640 +)))
645 645  
646 646  
647 -(% style="color:blue" %)** Example:**
648 648  
649 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
644 +== 2.7  ​Firmware Change Log ==
650 650  
651 651  
652 -== 2.7  Set the number of data to be uploaded and the recording time ==
647 +(((
648 +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]]
649 +)))
653 653  
651 +(((
652 +
653 +)))
654 654  
655 -(% style="color:blue" %)** ➢ AT Command:**
655 +(((
656 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
657 +)))
656 656  
657 -* (% 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)
658 -* (% 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.
659 659  
660 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
661 661  
662 -[[image:image-20221009001114-1.png||height="687" width="955"]]
661 +== 2.8  ​Battery Analysis ==
663 663  
664 664  
665 -== 2.8  Read or Clear cached data ==
664 +=== 2.8.1  ​Battery Type ===
666 666  
667 667  
668 -(% style="color:blue" %)** ➢ AT Command:**
667 +(((
668 +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.
669 +)))
669 669  
670 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
671 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
671 +(((
672 +The battery is designed to last for several years depends on the actually use environment and update interval. 
673 +)))
672 672  
673 -[[image:image-20220908175333-2.png]]
675 +(((
676 +The battery related documents as below:
677 +)))
674 674  
679 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
680 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
681 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
675 675  
676 -== 2.9  ​LED Indicator ==
683 +(((
684 +[[image:image-20220709101450-2.png]]
685 +)))
677 677  
678 678  
679 -The NDDS75 has an internal LED which is to show the status of different state.
680 680  
689 +=== 2.8.2  Power consumption Analyze ===
681 681  
682 -* 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)
683 -* Then the LED will be on for 1 second means device is boot normally.
684 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
685 -* For each uplink probe, LED will be on for 500ms.
686 686  
687 687  (((
688 -
693 +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.
689 689  )))
690 690  
691 691  
692 -== 2.10  ​Firmware Change Log ==
697 +(((
698 +Instruction to use as below:
699 +)))
693 693  
701 +(((
702 +(% 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/]]
703 +)))
694 694  
705 +
695 695  (((
696 -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]]
707 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
697 697  )))
698 698  
710 +* (((
711 +Product Model
712 +)))
713 +* (((
714 +Uplink Interval
715 +)))
716 +* (((
717 +Working Mode
718 +)))
719 +
699 699  (((
700 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
721 +And the Life expectation in difference case will be shown on the right.
701 701  )))
702 702  
724 +[[image:image-20220709110451-3.png]]
703 703  
704 -== 2.11 Battery & Power Consumption ==
705 705  
706 706  
707 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
728 +=== 2.8.3  ​Battery Note ===
708 708  
709 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
710 710  
731 +(((
732 +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.
733 +)))
711 711  
735 +
736 +
737 +=== 2.8.4  Replace the battery ===
738 +
739 +
740 +(((
741 +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).
742 +)))
743 +
744 +
745 +
712 712  = 3. ​ Access NB-IoT Module =
713 713  
714 714  
... ... @@ -725,8 +725,10 @@
725 725  [[image:1657333200519-600.png]]
726 726  
727 727  
762 +
728 728  = 4.  Using the AT Commands =
729 729  
765 +
730 730  == 4.1  Access AT Commands ==
731 731  
732 732  
... ... @@ -733,94 +733,80 @@
733 733  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]]
734 734  
735 735  
736 -AT+<CMD>?  :  Help on <CMD>
772 +AT+<CMD>?  : Help on <CMD>
737 737  
738 -AT+<CMD>         :  Run <CMD>
774 +AT+<CMD>         : Run <CMD>
739 739  
740 -AT+<CMD>=<value> :  Set the value
776 +AT+<CMD>=<value> : Set the value
741 741  
742 -AT+<CMD>=?  :  Get the value
778 +AT+<CMD>=?  : Get the value
743 743  
744 744  
745 745  (% style="color:#037691" %)**General Commands**(%%)      
746 746  
747 -AT  :  Attention       
783 +AT  : Attention       
748 748  
749 -AT?  :  Short Help     
785 +AT?  : Short Help     
750 750  
751 -ATZ  :  MCU Reset    
787 +ATZ  : MCU Reset    
752 752  
753 -AT+TDC  :  Application Data Transmission Interval
789 +AT+TDC  : Application Data Transmission Interval
754 754  
755 -AT+CFG  :  Print all configurations
791 +AT+CFG  : Print all configurations
756 756  
757 -AT+CFGMOD           :  Working mode selection
793 +AT+CFGMOD           : Working mode selection
758 758  
759 -AT+INTMOD            :  Set the trigger interrupt mode
795 +AT+INTMOD            : Set the trigger interrupt mode
760 760  
761 -AT+5VT  :  Set extend the time of 5V power  
797 +AT+5VT  : Set extend the time of 5V power  
762 762  
763 -AT+PRO  :  Choose agreement
799 +AT+PRO  : Choose agreement
764 764  
765 -AT+WEIGRE  :  Get weight or set weight to 0
801 +AT+WEIGRE  : Get weight or set weight to 0
766 766  
767 -AT+WEIGAP  :  Get or Set the GapValue of weight
803 +AT+WEIGAP  : Get or Set the GapValue of weight
768 768  
769 -AT+RXDL  :  Extend the sending and receiving time
805 +AT+RXDL  : Extend the sending and receiving time
770 770  
771 -AT+CNTFAC  :  Get or set counting parameters
807 +AT+CNTFAC  : Get or set counting parameters
772 772  
773 -AT+SERVADDR  :  Server Address
809 +AT+SERVADDR  : Server Address
774 774  
775 -AT+TR  :  Get or Set record time"
776 776  
777 -AT+APN     :  Get or set the APN
778 -
779 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
780 -
781 -AT+DNSCFG  : Get or Set DNS Server
782 -
783 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
784 -
785 -AT+NOUD  :  Get or Set the number of data to be uploaded
786 -
787 -AT+CDP     :  Read or Clear cached data
788 -
789 -AT+LDDSALARM :  Get or Set alarm of distance
790 -
791 -
792 792  (% style="color:#037691" %)**COAP Management**      
793 793  
794 -AT+URI            :  Resource parameters
814 +AT+URI            : Resource parameters
795 795  
796 796  
797 797  (% style="color:#037691" %)**UDP Management**
798 798  
799 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
819 +AT+CFM          : Upload confirmation mode (only valid for UDP)
800 800  
801 801  
802 802  (% style="color:#037691" %)**MQTT Management**
803 803  
804 -AT+CLIENT  :  Get or Set MQTT client
824 +AT+CLIENT               : Get or Set MQTT client
805 805  
806 -AT+UNAME  :  Get or Set MQTT Username
826 +AT+UNAME  : Get or Set MQTT Username
807 807  
808 -AT+PWD  :  Get or Set MQTT password
828 +AT+PWD                  : Get or Set MQTT password
809 809  
810 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
830 +AT+PUBTOPIC  : Get or Set MQTT publish topic
811 811  
812 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
832 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
813 813  
814 814  
815 815  (% style="color:#037691" %)**Information**          
816 816  
817 -AT+FDR  :  Factory Data Reset
837 +AT+FDR  : Factory Data Reset
818 818  
819 -AT+PWORD  :  Serial Access Password
839 +AT+PWORD  : Serial Access Password
820 820  
821 821  
842 +
822 822  = ​5.  FAQ =
823 823  
845 +
824 824  == 5.1 ​ How to Upgrade Firmware ==
825 825  
826 826  
... ... @@ -837,8 +837,10 @@
837 837  )))
838 838  
839 839  
862 +
840 840  = 6.  Trouble Shooting =
841 841  
865 +
842 842  == 6.1  ​Connection problem when uploading firmware ==
843 843  
844 844  
... ... @@ -851,20 +851,17 @@
851 851  
852 852  )))
853 853  
878 +
854 854  == 6.2  AT Command input doesn't work ==
855 855  
856 856  
857 857  (((
858 858  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.
884 +
885 +
859 859  )))
860 860  
861 861  
862 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
863 -
864 -
865 -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]]//**.
866 -
867 -
868 868  = 7. ​ Order Info =
869 869  
870 870  
... ... @@ -871,6 +871,11 @@
871 871  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
872 872  
873 873  
895 +(% class="wikigeneratedid" %)
896 +(((
897 +
898 +)))
899 +
874 874  = 8.  Packing Info =
875 875  
876 876  (((
... ... @@ -896,6 +896,7 @@
896 896  (((
897 897  
898 898  
925 +
899 899  
900 900  )))
901 901  
... ... @@ -903,5 +903,6 @@
903 903  
904 904  
905 905  * 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.
906 -
907 907  * 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]]
934 +
935 +
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

Applications

Navigation

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