Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.14 >
edited by Xiaoling
on 2023/05/17 18:16
To version < 100.6 >
edited by Xiaoling
on 2022/09/06 17:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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,19 @@
78 78  * Supply Voltage: 2.1v ~~ 3.6v
79 79  * Operating Temperature: -40 ~~ 85°C
80 80  
85 +
86 +
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
89 +* - B1 @H-FDD: 2100MHz
90 +* - B3 @H-FDD: 1800MHz
91 +* - B8 @H-FDD: 900MHz
92 +* - B5 @H-FDD: 850MHz
93 +* - B20 @H-FDD: 800MHz
94 +* - B28 @H-FDD: 700MHz
89 89  
96 +
97 +
90 90  (% style="color:#037691" %)**Battery:**
91 91  
92 92  * Li/SOCI2 un-chargeable battery
... ... @@ -95,6 +95,8 @@
95 95  * Max continuously current: 130mA
96 96  * Max boost current: 2A, 1 second
97 97  
106 +
107 +
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  
114 +
115 +
104 104  == ​1.4  Applications ==
105 105  
106 106  
... ... @@ -115,6 +115,8 @@
115 115  ​
116 116  
117 117  
130 +
131 +
118 118  == 1.5  Pin Definitions ==
119 119  
120 120  
... ... @@ -121,8 +121,10 @@
121 121  [[image:1657328609906-564.png]]
122 122  
123 123  
138 +
124 124  = 2.  Use NDDS75 to communicate with IoT Server =
125 125  
141 +
126 126  == 2.1  How it works ==
127 127  
128 128  
... ... @@ -145,8 +145,10 @@
145 145  
146 146  )))
147 147  
164 +
148 148  == 2.2 ​ Configure the NDDS75 ==
149 149  
167 +
150 150  === 2.2.1 Test Requirement ===
151 151  
152 152  
... ... @@ -158,6 +158,8 @@
158 158  * The local NB-IoT network used the band that NDDS75 supports.
159 159  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
160 160  
179 +
180 +
161 161  (((
162 162  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
163 163  )))
... ... @@ -166,6 +166,7 @@
166 166  [[image:1657328756309-230.png]]
167 167  
168 168  
189 +
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  
205 +
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:**
218 +**Connection:**
197 197  
198 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
220 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
222 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
224 + (% 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  
247 +
225 225  === 2.2.4 Use CoAP protocol to uplink data ===
226 226  
227 227  
... ... @@ -236,10 +236,10 @@
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
262 +(% 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
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
243 243  
244 244  
245 245  
... ... @@ -247,8 +247,6 @@
247 247  
248 248  (((
249 249  For parameter description, please refer to AT command set
250 -
251 -
252 252  )))
253 253  
254 254  [[image:1657330452568-615.png]]
... ... @@ -257,20 +257,21 @@
257 257  
258 258  (((
259 259  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.
260 -
261 -
262 262  )))
263 263  
264 264  [[image:1657330472797-498.png]]
265 265  
266 266  
286 +
267 267  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
268 268  
269 269  
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
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
291 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
273 273  
294 +
295 +
274 274  [[image:1657330501006-241.png]]
275 275  
276 276  
... ... @@ -277,17 +277,20 @@
277 277  [[image:1657330533775-472.png]]
278 278  
279 279  
302 +
280 280  === 2.2.6 Use MQTT protocol to uplink data ===
281 281  
282 282  
283 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
285 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
286 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
287 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
288 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
289 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
306 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
308 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
290 290  
314 +
315 +
291 291  [[image:1657249978444-674.png]]
292 292  
293 293  
... ... @@ -299,12 +299,15 @@
299 299  )))
300 300  
301 301  
327 +
302 302  === 2.2.7 Use TCP protocol to uplink data ===
303 303  
304 304  
305 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
306 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
331 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
307 307  
334 +
335 +
308 308  [[image:image-20220709093918-1.png]]
309 309  
310 310  
... ... @@ -311,42 +311,36 @@
311 311  [[image:image-20220709093918-2.png]]
312 312  
313 313  
342 +
314 314  === 2.2.8 Change Update Interval ===
315 315  
316 316  
317 317  User can use below command to change the (% style="color:green" %)**uplink interval**.
318 318  
319 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
348 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
320 320  
321 -(((
322 -
323 323  
324 324  
325 -(% style="color:red" %)**NOTE:**
326 -
327 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
328 -
329 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
352 +(((
353 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
330 330  )))
331 331  
332 -(% 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).**
333 333  
334 334  
335 335  == 2.3  Uplink Payload ==
336 336  
337 -=== 2.3.1  Before Firmware v1.3.2 ===
338 338  
339 -
340 340  In this mode, uplink payload includes in total 14 bytes
341 341  
342 -(% border="1" cellspacing="10" style="background-color:#f2f2f2; width:440px" %)
343 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
363 +
364 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
365 +|=(% style="width: 60px;" %)(((
344 344  **Size(bytes)**
345 -)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
367 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
346 346  |(% 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"]]
347 347  
348 348  (((
349 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
371 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
350 350  )))
351 351  
352 352  
... ... @@ -353,68 +353,41 @@
353 353  [[image:1657331036973-987.png]]
354 354  
355 355  
356 -The payload is **ASCII** string, representative same HEX:
357 -
358 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
359 -
360 -**where :**
361 -
362 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
363 -
364 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
365 -
366 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
367 -
368 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
369 -
370 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
371 -
372 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
373 -
374 -=== 2.3.2  Since firmware v1.3.2 ===
375 -
376 -
377 -In this mode, uplink payload includes 69 bytes in total by default.
378 -
379 -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.
380 -
381 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
382 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:70px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**4**
383 -|=(% 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.......
384 -
385 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
386 -
387 -[[image:image-20220908175246-1.png]]
388 -
389 -
378 +(((
390 390  The payload is ASCII string, representative same HEX:
380 +)))
391 391  
392 -**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 (%%)**
382 +(((
383 +0x72403155615900640c6c19029200 where:
384 +)))
393 393  
394 -**where:**
386 +* (((
387 +Device ID: 0x724031556159 = 724031556159
388 +)))
389 +* (((
390 +Version: 0x0064=100=1.0.0
391 +)))
395 395  
396 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
393 +* (((
394 +BAT: 0x0c6c = 3180 mV = 3.180V
395 +)))
396 +* (((
397 +Signal: 0x19 = 25
398 +)))
399 +* (((
400 +Distance: 0x0292= 658 mm
401 +)))
402 +* (((
403 +Interrupt: 0x00 = 0
397 397  
398 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
399 399  
400 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
401 401  
402 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
407 +
408 +)))
403 403  
404 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
405 -
406 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
407 -
408 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
409 -
410 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
411 -
412 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
413 -
414 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
415 -
416 416  == 2.4  Payload Explanation and Sensor Interface ==
417 417  
412 +
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 :**
427 +**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.
435 +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  
452 +
468 468  === 2.4.3  Battery Info ===
469 469  
470 470  
... ... @@ -477,6 +477,7 @@
477 477  )))
478 478  
479 479  
465 +
480 480  === 2.4.4  Signal Strength ===
481 481  
482 482  
... ... @@ -509,6 +509,7 @@
509 509  )))
510 510  
511 511  
498 +
512 512  === 2.4.5  Distance ===
513 513  
514 514  
... ... @@ -528,6 +528,10 @@
528 528  
529 529  )))
530 530  
518 +(((
519 +
520 +)))
521 +
531 531  === 2.4.6  Digital Interrupt ===
532 532  
533 533  
... ... @@ -540,7 +540,7 @@
540 540  )))
541 541  
542 542  (((
543 -(% 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]])**.**
534 +(% 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]])**.**
544 544  )))
545 545  
546 546  
... ... @@ -562,6 +562,7 @@
562 562  )))
563 563  
564 564  
556 +
565 565  === 2.4.7  ​+5V Output ===
566 566  
567 567  
... ... @@ -587,6 +587,7 @@
587 587  )))
588 588  
589 589  
582 +
590 590  == 2.5  Downlink Payload ==
591 591  
592 592  
... ... @@ -639,85 +639,126 @@
639 639  )))
640 640  
641 641  
642 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
643 643  
636 +== 2.6  ​LED Indicator ==
644 644  
645 -(% style="color:blue" %)** ➢ AT Command:**
646 646  
647 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
639 +The NDDS75 has an internal LED which is to show the status of different state.
648 648  
649 -² When min=0, and max≠0, Alarm higher than max
650 650  
651 -² When min≠0, and max=0, Alarm lower than min
642 +* 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)
643 +* Then the LED will be on for 1 second means device is boot normally.
644 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
645 +* For each uplink probe, LED will be on for 500ms.
652 652  
653 -² When min≠0 and max≠0, Alarm higher than max or lower than min
647 +(((
648 +
649 +)))
654 654  
655 655  
656 -(% style="color:blue" %)** Example:**
657 657  
658 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
653 +== 2.7  ​Firmware Change Log ==
659 659  
660 660  
661 -== 2.7  Set the number of data to be uploaded and the recording time ==
656 +(((
657 +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]]
658 +)))
662 662  
660 +(((
661 +
662 +)))
663 663  
664 -(% style="color:blue" %)** ➢ AT Command:**
664 +(((
665 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
666 +)))
665 665  
666 -* (% 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)
667 -* (% 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.
668 668  
669 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
670 670  
671 -[[image:image-20221009001114-1.png||height="687" width="955"]]
670 +== 2.8  ​Battery Analysis ==
672 672  
673 673  
674 -== 2.8  Read or Clear cached data ==
673 +=== 2.8.1  ​Battery Type ===
675 675  
676 676  
677 -(% style="color:blue" %)** ➢ AT Command:**
676 +(((
677 +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.
678 +)))
678 678  
679 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
680 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
680 +(((
681 +The battery is designed to last for several years depends on the actually use environment and update interval. 
682 +)))
681 681  
682 -[[image:image-20220908175333-2.png]]
684 +(((
685 +The battery related documents as below:
686 +)))
683 683  
688 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
689 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
690 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
684 684  
685 -== 2.9  ​LED Indicator ==
692 +(((
693 +[[image:image-20220709101450-2.png]]
694 +)))
686 686  
687 687  
688 -The NDDS75 has an internal LED which is to show the status of different state.
689 689  
698 +=== 2.8.2  Power consumption Analyze ===
690 690  
691 -* 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)
692 -* Then the LED will be on for 1 second means device is boot normally.
693 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
694 -* For each uplink probe, LED will be on for 500ms.
695 695  
696 696  (((
697 -
702 +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.
698 698  )))
699 699  
700 700  
701 -== 2.10  ​Firmware Change Log ==
706 +(((
707 +Instruction to use as below:
708 +)))
702 702  
710 +(((
711 +(% 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/]]
712 +)))
703 703  
714 +
704 704  (((
705 -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]]
716 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
706 706  )))
707 707  
719 +* (((
720 +Product Model
721 +)))
722 +* (((
723 +Uplink Interval
724 +)))
725 +* (((
726 +Working Mode
727 +)))
728 +
708 708  (((
709 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
730 +And the Life expectation in difference case will be shown on the right.
710 710  )))
711 711  
733 +[[image:image-20220709110451-3.png]]
712 712  
713 -== 2.11 Battery & Power Consumption ==
714 714  
715 715  
716 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
737 +=== 2.8.3  ​Battery Note ===
717 717  
718 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
719 719  
740 +(((
741 +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.
742 +)))
720 720  
744 +
745 +
746 +=== 2.8.4  Replace the battery ===
747 +
748 +
749 +(((
750 +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).
751 +)))
752 +
753 +
754 +
721 721  = 3. ​ Access NB-IoT Module =
722 722  
723 723  
... ... @@ -734,8 +734,10 @@
734 734  [[image:1657333200519-600.png]]
735 735  
736 736  
771 +
737 737  = 4.  Using the AT Commands =
738 738  
774 +
739 739  == 4.1  Access AT Commands ==
740 740  
741 741  
... ... @@ -742,94 +742,80 @@
742 742  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]]
743 743  
744 744  
745 -AT+<CMD>?  :  Help on <CMD>
781 +AT+<CMD>?  : Help on <CMD>
746 746  
747 -AT+<CMD>         :  Run <CMD>
783 +AT+<CMD>         : Run <CMD>
748 748  
749 -AT+<CMD>=<value> :  Set the value
785 +AT+<CMD>=<value> : Set the value
750 750  
751 -AT+<CMD>=?  :  Get the value
787 +AT+<CMD>=?  : Get the value
752 752  
753 753  
754 754  (% style="color:#037691" %)**General Commands**(%%)      
755 755  
756 -AT  :  Attention       
792 +AT  : Attention       
757 757  
758 -AT?  :  Short Help     
794 +AT?  : Short Help     
759 759  
760 -ATZ  :  MCU Reset    
796 +ATZ  : MCU Reset    
761 761  
762 -AT+TDC  :  Application Data Transmission Interval
798 +AT+TDC  : Application Data Transmission Interval
763 763  
764 -AT+CFG  :  Print all configurations
800 +AT+CFG  : Print all configurations
765 765  
766 -AT+CFGMOD           :  Working mode selection
802 +AT+CFGMOD           : Working mode selection
767 767  
768 -AT+INTMOD            :  Set the trigger interrupt mode
804 +AT+INTMOD            : Set the trigger interrupt mode
769 769  
770 -AT+5VT  :  Set extend the time of 5V power  
806 +AT+5VT  : Set extend the time of 5V power  
771 771  
772 -AT+PRO  :  Choose agreement
808 +AT+PRO  : Choose agreement
773 773  
774 -AT+WEIGRE  :  Get weight or set weight to 0
810 +AT+WEIGRE  : Get weight or set weight to 0
775 775  
776 -AT+WEIGAP  :  Get or Set the GapValue of weight
812 +AT+WEIGAP  : Get or Set the GapValue of weight
777 777  
778 -AT+RXDL  :  Extend the sending and receiving time
814 +AT+RXDL  : Extend the sending and receiving time
779 779  
780 -AT+CNTFAC  :  Get or set counting parameters
816 +AT+CNTFAC  : Get or set counting parameters
781 781  
782 -AT+SERVADDR  :  Server Address
818 +AT+SERVADDR  : Server Address
783 783  
784 -AT+TR  :  Get or Set record time"
785 785  
786 -AT+APN     :  Get or set the APN
787 -
788 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
789 -
790 -AT+DNSCFG  : Get or Set DNS Server
791 -
792 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
793 -
794 -AT+NOUD  :  Get or Set the number of data to be uploaded
795 -
796 -AT+CDP     :  Read or Clear cached data
797 -
798 -AT+LDDSALARM :  Get or Set alarm of distance
799 -
800 -
801 801  (% style="color:#037691" %)**COAP Management**      
802 802  
803 -AT+URI            :  Resource parameters
823 +AT+URI            : Resource parameters
804 804  
805 805  
806 806  (% style="color:#037691" %)**UDP Management**
807 807  
808 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
828 +AT+CFM          : Upload confirmation mode (only valid for UDP)
809 809  
810 810  
811 811  (% style="color:#037691" %)**MQTT Management**
812 812  
813 -AT+CLIENT  :  Get or Set MQTT client
833 +AT+CLIENT               : Get or Set MQTT client
814 814  
815 -AT+UNAME  :  Get or Set MQTT Username
835 +AT+UNAME  : Get or Set MQTT Username
816 816  
817 -AT+PWD  :  Get or Set MQTT password
837 +AT+PWD                  : Get or Set MQTT password
818 818  
819 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
839 +AT+PUBTOPIC  : Get or Set MQTT publish topic
820 820  
821 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
841 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
822 822  
823 823  
824 824  (% style="color:#037691" %)**Information**          
825 825  
826 -AT+FDR  :  Factory Data Reset
846 +AT+FDR  : Factory Data Reset
827 827  
828 -AT+PWORD  :  Serial Access Password
848 +AT+PWORD  : Serial Access Password
829 829  
830 830  
851 +
831 831  = ​5.  FAQ =
832 832  
854 +
833 833  == 5.1 ​ How to Upgrade Firmware ==
834 834  
835 835  
... ... @@ -846,8 +846,10 @@
846 846  )))
847 847  
848 848  
871 +
849 849  = 6.  Trouble Shooting =
850 850  
874 +
851 851  == 6.1  ​Connection problem when uploading firmware ==
852 852  
853 853  
... ... @@ -860,20 +860,17 @@
860 860  
861 861  )))
862 862  
887 +
863 863  == 6.2  AT Command input doesn't work ==
864 864  
865 865  
866 866  (((
867 867  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.
893 +
894 +
868 868  )))
869 869  
870 870  
871 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
872 -
873 -
874 -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]]//**.
875 -
876 -
877 877  = 7. ​ Order Info =
878 878  
879 879  
... ... @@ -880,6 +880,11 @@
880 880  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
881 881  
882 882  
904 +(% class="wikigeneratedid" %)
905 +(((
906 +
907 +)))
908 +
883 883  = 8.  Packing Info =
884 884  
885 885  (((
... ... @@ -894,6 +894,7 @@
894 894  (((
895 895  
896 896  
923 +
897 897  (% style="color:#037691" %)**Dimension and weight**:
898 898  
899 899  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -905,6 +905,7 @@
905 905  (((
906 906  
907 907  
935 +
908 908  
909 909  )))
910 910  
... ... @@ -912,5 +912,6 @@
912 912  
913 913  
914 914  * 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.
915 -
916 916  * 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]]
944 +
945 +
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