Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.3 >
edited by Xiaoling
on 2022/10/15 10:00
To version < 97.21 >
edited by Xiaoling
on 2022/07/09 17:50
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,6 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -
20 20  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 21  
22 22  (((
... ... @@ -57,7 +57,6 @@
57 57  
58 58  == 1.2 ​ Features ==
59 59  
60 -
61 61  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 62  * Ultra low power consumption
63 63  * Distance Detection by Ultrasonic technology
... ... @@ -72,7 +72,6 @@
72 72  * 8500mAh Battery for long term use
73 73  
74 74  
75 -
76 76  == 1.3  Specification ==
77 77  
78 78  
... ... @@ -104,10 +104,8 @@
104 104  * Max transmit power: 350mA@3.3v
105 105  
106 106  
107 -
108 108  == ​1.4  Applications ==
109 109  
110 -
111 111  * Smart Buildings & Home Automation
112 112  * Logistics and Supply Chain Management
113 113  * Smart Metering
... ... @@ -119,7 +119,6 @@
119 119  ​
120 120  
121 121  
122 -
123 123  == 1.5  Pin Definitions ==
124 124  
125 125  
... ... @@ -129,10 +129,8 @@
129 129  
130 130  = 2.  Use NDDS75 to communicate with IoT Server =
131 131  
132 -
133 133  == 2.1  How it works ==
134 134  
135 -
136 136  (((
137 137  The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
138 138  )))
... ... @@ -158,17 +158,16 @@
158 158  
159 159  === 2.2.1 Test Requirement ===
160 160  
161 -
162 162  (((
163 163  To use NDDS75 in your city, make sure meet below requirements:
164 164  )))
165 165  
166 166  * Your local operator has already distributed a NB-IoT Network there.
167 -* The local NB-IoT network used the band that NDDS75 supports.
158 +* The local NB-IoT network used the band that NSE01 supports.
168 168  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
169 169  
170 170  (((
171 -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.
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
172 172  )))
173 173  
174 174  
... ... @@ -178,7 +178,6 @@
178 178  
179 179  === 2.2.2 Insert SIM card ===
180 180  
181 -
182 182  (((
183 183  Insert the NB-IoT Card get from your provider.
184 184  )))
... ... @@ -194,7 +194,6 @@
194 194  
195 195  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
196 196  
197 -
198 198  (((
199 199  (((
200 200  User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
... ... @@ -203,16 +203,15 @@
203 203  
204 204  [[image:image-20220709092052-2.png]]
205 205  
195 +**Connection:**
206 206  
207 -(% style="color:blue" %)**Connection:**
197 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
208 208  
209 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
199 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
210 210  
211 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
201 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
212 212  
213 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
214 214  
215 -
216 216  In the PC, use below serial tool settings:
217 217  
218 218  * Baud:  (% style="color:green" %)**9600**
... ... @@ -227,9 +227,8 @@
227 227  
228 228  [[image:1657329814315-101.png]]
229 229  
230 -
231 231  (((
232 -(% 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]]**
219 +(% 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/]]
233 233  )))
234 234  
235 235  
... ... @@ -236,10 +236,9 @@
236 236  
237 237  === 2.2.4 Use CoAP protocol to uplink data ===
238 238  
226 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
239 239  
240 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
241 241  
242 -
243 243  (((
244 244  **Use below commands:**
245 245  )))
... ... @@ -248,29 +248,21 @@
248 248  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
249 249  )))
250 250  * (((
251 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
237 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
252 252  )))
253 253  * (((
254 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
255 -
256 -
257 -
240 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
258 258  )))
259 259  
260 260  (((
261 261  For parameter description, please refer to AT command set
262 -
263 -
264 264  )))
265 265  
266 266  [[image:1657330452568-615.png]]
267 267  
268 268  
269 -
270 270  (((
271 271  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.
272 -
273 -
274 274  )))
275 275  
276 276  [[image:1657330472797-498.png]]
... ... @@ -280,9 +280,9 @@
280 280  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
281 281  
282 282  
283 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
285 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
261 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
262 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
263 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
286 286  
287 287  [[image:1657330501006-241.png]]
288 288  
... ... @@ -294,13 +294,13 @@
294 294  === 2.2.6 Use MQTT protocol to uplink data ===
295 295  
296 296  
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
275 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
276 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
277 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
278 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
279 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
280 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
281 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
304 304  
305 305  [[image:1657249978444-674.png]]
306 306  
... ... @@ -317,8 +317,8 @@
317 317  === 2.2.7 Use TCP protocol to uplink data ===
318 318  
319 319  
320 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
321 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
298 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
299 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
322 322  
323 323  [[image:image-20220709093918-1.png]]
324 324  
... ... @@ -329,34 +329,25 @@
329 329  
330 330  === 2.2.8 Change Update Interval ===
331 331  
332 -
333 333  User can use below command to change the (% style="color:green" %)**uplink interval**.
334 334  
335 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
312 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
336 336  
337 337  (((
338 -
339 -
340 -
341 341  (% style="color:red" %)**NOTE:**
316 +)))
342 342  
343 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
344 -
345 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
318 +(((
319 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
346 346  )))
347 347  
348 -(% 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).**
349 349  
350 350  
351 -
352 352  == 2.3  Uplink Payload ==
353 353  
354 -
355 -=== 2.3.1  Before Firmware v1.3.2 ===
356 -
357 -
358 358  In this mode, uplink payload includes in total 14 bytes
359 359  
328 +
360 360  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
361 361  |=(% style="width: 60px;" %)(((
362 362  **Size(bytes)**
... ... @@ -370,78 +370,43 @@
370 370  
371 371  [[image:1657331036973-987.png]]
372 372  
373 -
374 -
375 -The payload is **ASCII** string, representative same HEX:
376 -
377 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
378 -
379 -**where :**
380 -
381 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
382 -
383 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
384 -
385 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
386 -
387 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
388 -
389 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
390 -
391 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
392 -
393 -
394 -
395 -=== **2.3.2  Since firmware v1.3.2** ===
396 -
397 -
398 -In this mode, uplink payload includes 69 bytes in total by default.
399 -
400 -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.
401 -
402 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
403 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
404 -|(% 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.......
405 -
406 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
407 -
408 -[[image:image-20220908175246-1.png]]
409 -
410 -
342 +(((
411 411  The payload is ASCII string, representative same HEX:
344 +)))
412 412  
413 -**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 (%%)**
346 +(((
347 +0x72403155615900640c6c19029200 where:
348 +)))
414 414  
415 -**where:**
350 +* (((
351 +Device ID: 0x724031556159 = 724031556159
352 +)))
353 +* (((
354 +Version: 0x0064=100=1.0.0
355 +)))
416 416  
417 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
357 +* (((
358 +BAT: 0x0c6c = 3180 mV = 3.180V
359 +)))
360 +* (((
361 +Signal: 0x19 = 25
362 +)))
363 +* (((
364 +Distance: 0x0292= 658 mm
365 +)))
366 +* (((
367 +Interrupt: 0x00 = 0
418 418  
419 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
420 420  
421 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
422 422  
423 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
371 +
372 +)))
424 424  
425 -* (% style="color:#037691" %)**Mod:**(%%)**  **0x01 = 1
426 -
427 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
428 -
429 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
430 -
431 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 -
433 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
434 -
435 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
436 -
437 -
438 -
439 439  == 2.4  Payload Explanation and Sensor Interface ==
440 440  
441 441  
442 442  === 2.4.1  Device ID ===
443 443  
444 -
445 445  (((
446 446  By default, the Device ID equal to the last 6 bytes of IMEI.
447 447  )))
... ... @@ -448,12 +448,10 @@
448 448  
449 449  (((
450 450  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 -
452 -
453 453  )))
454 454  
455 455  (((
456 -(% style="color:blue" %)**Example :**
388 +**Example:**
457 457  )))
458 458  
459 459  (((
... ... @@ -461,26 +461,13 @@
461 461  )))
462 462  
463 463  (((
464 -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.
396 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
465 465  )))
466 466  
467 467  
468 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
469 469  
470 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
471 -
472 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
473 -
474 -
475 -(% style="color:blue" %)**Example :**
476 -
477 -AT+DEUI=868411056754138
478 -
479 -
480 -
481 481  === 2.4.2  Version Info ===
482 482  
483 -
484 484  (((
485 485  Specify the software version: 0x64=100, means firmware version 1.00.
486 486  )))
... ... @@ -493,7 +493,6 @@
493 493  
494 494  === 2.4.3  Battery Info ===
495 495  
496 -
497 497  (((
498 498  Ex1: 0x0B45 = 2885mV
499 499  )))
... ... @@ -506,7 +506,6 @@
506 506  
507 507  === 2.4.4  Signal Strength ===
508 508  
509 -
510 510  (((
511 511  NB-IoT Network signal Strength.
512 512  )))
... ... @@ -539,7 +539,6 @@
539 539  
540 540  === 2.4.5  Distance ===
541 541  
542 -
543 543  Get the distance. Flat object range 280mm - 7500mm.
544 544  
545 545  (((
... ... @@ -562,7 +562,6 @@
562 562  
563 563  === 2.4.6  Digital Interrupt ===
564 564  
565 -
566 566  (((
567 567  Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
568 568  )))
... ... @@ -572,7 +572,7 @@
572 572  )))
573 573  
574 574  (((
575 -(% 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]])**.**
490 +(% 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]])**.**
576 576  )))
577 577  
578 578  
... ... @@ -597,7 +597,6 @@
597 597  
598 598  === 2.4.7  ​+5V Output ===
599 599  
600 -
601 601  (((
602 602  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
603 603  )))
... ... @@ -605,14 +605,10 @@
605 605  
606 606  (((
607 607  The 5V output time can be controlled by AT Command.
608 -
609 -
610 610  )))
611 611  
612 612  (((
613 613  (% style="color:blue" %)**AT+5VT=1000**
614 -
615 -
616 616  )))
617 617  
618 618  (((
... ... @@ -623,7 +623,6 @@
623 623  
624 624  == 2.5  Downlink Payload ==
625 625  
626 -
627 627  By default, NDDS75 prints the downlink payload to console port.
628 628  
629 629  [[image:image-20220709100028-1.png]]
... ... @@ -674,55 +674,9 @@
674 674  
675 675  
676 676  
677 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
586 +== 2.6  ​LED Indicator ==
678 678  
679 679  
680 -(% style="color:blue" %)** ➢ AT Command:**
681 -
682 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
683 -
684 -² When min=0, and max≠0, Alarm higher than max
685 -
686 -² When min≠0, and max=0, Alarm lower than min
687 -
688 -² When min≠0 and max≠0, Alarm higher than max or lower than min
689 -
690 -
691 -(% style="color:blue" %)** Example:**
692 -
693 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
694 -
695 -
696 -
697 -== 2.7  Set the number of data to be uploaded and the recording time ==
698 -
699 -
700 -(% style="color:blue" %)** ➢ AT Command:**
701 -
702 -* (% 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)
703 -* (% 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.
704 -
705 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
706 -
707 -[[image:image-20221009001114-1.png||height="687" width="955"]]
708 -
709 -
710 -
711 -== 2.8  Read or Clear cached data ==
712 -
713 -
714 -(% style="color:blue" %)** ➢ AT Command:**
715 -
716 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
717 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
718 -
719 -[[image:image-20220908175333-2.png]]
720 -
721 -
722 -
723 -== 2.9  ​LED Indicator ==
724 -
725 -
726 726  The NDDS75 has an internal LED which is to show the status of different state.
727 727  
728 728  
... ... @@ -737,29 +737,29 @@
737 737  
738 738  
739 739  
740 -== 2.10  ​Firmware Change Log ==
603 +== 2.7  ​Firmware Change Log ==
741 741  
742 742  
743 743  (((
744 -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]]
607 +Download URL & Firmware Change log
745 745  )))
746 746  
747 747  (((
748 -
611 +[[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/]]
749 749  )))
750 750  
614 +
751 751  (((
752 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
616 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
753 753  )))
754 754  
755 755  
756 756  
757 -== 2.11  ​Battery Analysis ==
621 +== 2.8  ​Battery Analysis ==
758 758  
623 +=== 2.8.1  ​Battery Type ===
759 759  
760 -=== 2.11.1  ​Battery Type ===
761 761  
762 -
763 763  (((
764 764  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.
765 765  )))
... ... @@ -782,9 +782,8 @@
782 782  
783 783  
784 784  
785 -=== 2.11.2  Power consumption Analyze ===
648 +=== 2.8.2  Power consumption Analyze ===
786 786  
787 -
788 788  (((
789 789  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.
790 790  )))
... ... @@ -821,9 +821,8 @@
821 821  
822 822  
823 823  
824 -=== 2.11.3  ​Battery Note ===
686 +=== 2.8.3  ​Battery Note ===
825 825  
826 -
827 827  (((
828 828  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.
829 829  )))
... ... @@ -830,9 +830,8 @@
830 830  
831 831  
832 832  
833 -=== 2.11.4  Replace the battery ===
694 +=== 2.8.4  Replace the battery ===
834 834  
835 -
836 836  (((
837 837  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).
838 838  )))
... ... @@ -841,7 +841,6 @@
841 841  
842 842  = 3. ​ Access NB-IoT Module =
843 843  
844 -
845 845  (((
846 846  Users can directly access the AT command set of the NB-IoT module.
847 847  )))
... ... @@ -848,8 +848,6 @@
848 848  
849 849  (((
850 850  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/]] 
851 -
852 -
853 853  )))
854 854  
855 855  [[image:1657333200519-600.png]]
... ... @@ -858,103 +858,84 @@
858 858  
859 859  = 4.  Using the AT Commands =
860 860  
861 -
862 862  == 4.1  Access AT Commands ==
863 863  
720 +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/]]
864 864  
865 -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]]
866 866  
723 +AT+<CMD>?  : Help on <CMD>
867 867  
868 -AT+<CMD>?  :  Help on <CMD>
725 +AT+<CMD>         : Run <CMD>
869 869  
870 -AT+<CMD>         :  Run <CMD>
727 +AT+<CMD>=<value> : Set the value
871 871  
872 -AT+<CMD>=<value> :  Set the value
729 +AT+<CMD>=?  : Get the value
873 873  
874 -AT+<CMD>=?  :  Get the value
875 875  
876 -
877 877  (% style="color:#037691" %)**General Commands**(%%)      
878 878  
879 -AT  :  Attention       
734 +AT  : Attention       
880 880  
881 -AT?  :  Short Help     
736 +AT?  : Short Help     
882 882  
883 -ATZ  :  MCU Reset    
738 +ATZ  : MCU Reset    
884 884  
885 -AT+TDC  :  Application Data Transmission Interval
740 +AT+TDC  : Application Data Transmission Interval
886 886  
887 -AT+CFG  :  Print all configurations
742 +AT+CFG  : Print all configurations
888 888  
889 -AT+CFGMOD           :  Working mode selection
744 +AT+CFGMOD           : Working mode selection
890 890  
891 -AT+INTMOD            :  Set the trigger interrupt mode
746 +AT+INTMOD            : Set the trigger interrupt mode
892 892  
893 -AT+5VT  :  Set extend the time of 5V power  
748 +AT+5VT  : Set extend the time of 5V power  
894 894  
895 -AT+PRO  :  Choose agreement
750 +AT+PRO  : Choose agreement
896 896  
897 -AT+WEIGRE  :  Get weight or set weight to 0
752 +AT+WEIGRE  : Get weight or set weight to 0
898 898  
899 -AT+WEIGAP  :  Get or Set the GapValue of weight
754 +AT+WEIGAP  : Get or Set the GapValue of weight
900 900  
901 -AT+RXDL  :  Extend the sending and receiving time
756 +AT+RXDL  : Extend the sending and receiving time
902 902  
903 -AT+CNTFAC  :  Get or set counting parameters
758 +AT+CNTFAC  : Get or set counting parameters
904 904  
905 -AT+SERVADDR  :  Server Address
760 +AT+SERVADDR  : Server Address
906 906  
907 -AT+TR  :  Get or Set record time"
908 908  
909 -AT+APN     :  Get or set the APN
910 -
911 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
912 -
913 -AT+DNSCFG  : Get or Set DNS Server
914 -
915 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
916 -
917 -AT+NOUD  :  Get or Set the number of data to be uploaded
918 -
919 -AT+CDP     :  Read or Clear cached data
920 -
921 -AT+LDDSALARM :  Get or Set alarm of distance
922 -
923 -
924 924  (% style="color:#037691" %)**COAP Management**      
925 925  
926 -AT+URI            :  Resource parameters
765 +AT+URI            : Resource parameters
927 927  
928 928  
929 929  (% style="color:#037691" %)**UDP Management**
930 930  
931 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
770 +AT+CFM          : Upload confirmation mode (only valid for UDP)
932 932  
933 933  
934 934  (% style="color:#037691" %)**MQTT Management**
935 935  
936 -AT+CLIENT  :  Get or Set MQTT client
775 +AT+CLIENT               : Get or Set MQTT client
937 937  
938 -AT+UNAME  :  Get or Set MQTT Username
777 +AT+UNAME  : Get or Set MQTT Username
939 939  
940 -AT+PWD  :  Get or Set MQTT password
779 +AT+PWD                  : Get or Set MQTT password
941 941  
942 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
781 +AT+PUBTOPIC  : Get or Set MQTT publish topic
943 943  
944 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
783 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
945 945  
946 946  
947 947  (% style="color:#037691" %)**Information**          
948 948  
949 -AT+FDR  :  Factory Data Reset
788 +AT+FDR  : Factory Data Reset
950 950  
951 -AT+PWORD  :  Serial Access Password
790 +AT+PWORD  : Serial Access Password
952 952  
953 953  
954 954  
955 955  = ​5.  FAQ =
956 956  
957 -
958 958  == 5.1 ​ How to Upgrade Firmware ==
959 959  
960 960  
... ... @@ -967,7 +967,7 @@
967 967  )))
968 968  
969 969  (((
970 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
808 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
971 971  )))
972 972  
973 973  
... ... @@ -974,7 +974,6 @@
974 974  
975 975  = 6.  Trouble Shooting =
976 976  
977 -
978 978  == 6.1  ​Connection problem when uploading firmware ==
979 979  
980 980  
... ... @@ -990,7 +990,6 @@
990 990  
991 991  == 6.2  AT Command input doesn't work ==
992 992  
993 -
994 994  (((
995 995  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.
996 996  
... ... @@ -1023,7 +1023,6 @@
1023 1023  (((
1024 1024  
1025 1025  
1026 -
1027 1027  (% style="color:#037691" %)**Dimension and weight**:
1028 1028  
1029 1029  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -1041,6 +1041,5 @@
1041 1041  
1042 1042  = 9.  Support =
1043 1043  
1044 -
1045 1045  * 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.
1046 1046  * 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

Applications

Navigation

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