Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.17 >
edited by Xiaoling
on 2022/07/09 11:53
To version < 103.1 >
edited by David Huang
on 2022/09/08 18:02
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
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  (((
... ... @@ -70,6 +70,7 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long term use
72 72  
74 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -100,8 +100,10 @@
100 100  * STOP Mode: 10uA @ 3.3v
101 101  * Max transmit power: 350mA@3.3v
102 102  
105 +
103 103  == ​1.4  Applications ==
104 104  
108 +
105 105  * Smart Buildings & Home Automation
106 106  * Logistics and Supply Chain Management
107 107  * Smart Metering
... ... @@ -113,6 +113,8 @@
113 113  ​
114 114  
115 115  
120 +
121 +
116 116  == 1.5  Pin Definitions ==
117 117  
118 118  
... ... @@ -122,8 +122,10 @@
122 122  
123 123  = 2.  Use NDDS75 to communicate with IoT Server =
124 124  
131 +
125 125  == 2.1  How it works ==
126 126  
134 +
127 127  (((
128 128  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.
129 129  )))
... ... @@ -149,16 +149,17 @@
149 149  
150 150  === 2.2.1 Test Requirement ===
151 151  
160 +
152 152  (((
153 153  To use NDDS75 in your city, make sure meet below requirements:
154 154  )))
155 155  
156 156  * Your local operator has already distributed a NB-IoT Network there.
157 -* The local NB-IoT network used the band that NSE01 supports.
166 +* The local NB-IoT network used the band that NDDS75 supports.
158 158  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
159 159  
160 160  (((
161 -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
170 +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 162  )))
163 163  
164 164  
... ... @@ -168,6 +168,7 @@
168 168  
169 169  === 2.2.2 Insert SIM card ===
170 170  
180 +
171 171  (((
172 172  Insert the NB-IoT Card get from your provider.
173 173  )))
... ... @@ -183,6 +183,7 @@
183 183  
184 184  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
185 185  
196 +
186 186  (((
187 187  (((
188 188  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.
... ... @@ -191,6 +191,7 @@
191 191  
192 192  [[image:image-20220709092052-2.png]]
193 193  
205 +
194 194  **Connection:**
195 195  
196 196   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -214,8 +214,9 @@
214 214  
215 215  [[image:1657329814315-101.png]]
216 216  
229 +
217 217  (((
218 -(% 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/]]
231 +(% 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 219  )))
220 220  
221 221  
... ... @@ -222,9 +222,10 @@
222 222  
223 223  === 2.2.4 Use CoAP protocol to uplink data ===
224 224  
225 -(% 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/]]
226 226  
239 +(% 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/]]**
227 227  
241 +
228 228  (((
229 229  **Use below commands:**
230 230  )))
... ... @@ -237,6 +237,9 @@
237 237  )))
238 238  * (((
239 239  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
254 +
255 +
256 +
240 240  )))
241 241  
242 242  (((
... ... @@ -246,6 +246,7 @@
246 246  [[image:1657330452568-615.png]]
247 247  
248 248  
266 +
249 249  (((
250 250  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.
251 251  )))
... ... @@ -306,22 +306,25 @@
306 306  
307 307  === 2.2.8 Change Update Interval ===
308 308  
327 +
309 309  User can use below command to change the (% style="color:green" %)**uplink interval**.
310 310  
311 311  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
312 312  
313 313  (((
314 -(% style="color:red" %)**NOTE:**
315 -)))
333 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
316 316  
317 -(((
318 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
335 +
319 319  )))
320 320  
338 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
321 321  
340 +**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).**
322 322  
342 +
323 323  == 2.3  Uplink Payload ==
324 324  
345 +
325 325  In this mode, uplink payload includes in total 14 bytes
326 326  
327 327  
... ... @@ -338,6 +338,7 @@
338 338  
339 339  [[image:1657331036973-987.png]]
340 340  
362 +
341 341  (((
342 342  The payload is ASCII string, representative same HEX:
343 343  )))
... ... @@ -365,16 +365,43 @@
365 365  * (((
366 366  Interrupt: 0x00 = 0
367 367  
368 -
369 -
370 370  
371 371  )))
372 372  
393 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
394 +
395 +In this mode, uplink payload includes 69 bytes in total by default.
396 +
397 +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.
398 +
399 +|**Size(bytes)**|**8**|2|2|1|1|1|2|4|2|4
400 +|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|Interrupt|Distance|Timestamp|Distance|Timestamp.......
401 +
402 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
403 +
404 +[[image:image-20220908175246-1.png]]
405 +
406 +The payload is ASCII string, representative same HEX:
407 +
408 +0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
409 +
410 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
411 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
412 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
413 +* (% style="color:blue" %)Singal: 0x1e = 30
414 +* (% style="color:red" %)Mod: 0x01 = 1
415 +* Interrupt: 0x00= 0
416 +* Distance: 0x0039= 57 = 57
417 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
418 +* Distance,Time stamp : 00396319baf0
419 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
420 +
373 373  == 2.4  Payload Explanation and Sensor Interface ==
374 374  
375 375  
376 376  === 2.4.1  Device ID ===
377 377  
426 +
378 378  (((
379 379  By default, the Device ID equal to the last 6 bytes of IMEI.
380 380  )))
... ... @@ -381,6 +381,8 @@
381 381  
382 382  (((
383 383  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
433 +
434 +
384 384  )))
385 385  
386 386  (((
... ... @@ -396,9 +396,19 @@
396 396  )))
397 397  
398 398  
450 +**NOTE:When the firmware version is v1.3.2 and later firmware:**
399 399  
452 +By default, the Device ID equal to the last 15 bits of IMEI.
453 +
454 +User can use **AT+DEUI** to set Device ID
455 +
456 +**Example:**
457 +
458 +AT+DEUI=868411056754138
459 +
400 400  === 2.4.2  Version Info ===
401 401  
462 +
402 402  (((
403 403  Specify the software version: 0x64=100, means firmware version 1.00.
404 404  )))
... ... @@ -411,6 +411,7 @@
411 411  
412 412  === 2.4.3  Battery Info ===
413 413  
475 +
414 414  (((
415 415  Ex1: 0x0B45 = 2885mV
416 416  )))
... ... @@ -423,6 +423,7 @@
423 423  
424 424  === 2.4.4  Signal Strength ===
425 425  
488 +
426 426  (((
427 427  NB-IoT Network signal Strength.
428 428  )))
... ... @@ -455,6 +455,7 @@
455 455  
456 456  === 2.4.5  Distance ===
457 457  
521 +
458 458  Get the distance. Flat object range 280mm - 7500mm.
459 459  
460 460  (((
... ... @@ -477,6 +477,7 @@
477 477  
478 478  === 2.4.6  Digital Interrupt ===
479 479  
544 +
480 480  (((
481 481  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.
482 482  )))
... ... @@ -511,6 +511,7 @@
511 511  
512 512  === 2.4.7  ​+5V Output ===
513 513  
579 +
514 514  (((
515 515  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
516 516  )))
... ... @@ -518,10 +518,14 @@
518 518  
519 519  (((
520 520  The 5V output time can be controlled by AT Command.
587 +
588 +
521 521  )))
522 522  
523 523  (((
524 524  (% style="color:blue" %)**AT+5VT=1000**
593 +
594 +
525 525  )))
526 526  
527 527  (((
... ... @@ -532,6 +532,7 @@
532 532  
533 533  == 2.5  Downlink Payload ==
534 534  
605 +
535 535  By default, NDDS75 prints the downlink payload to console port.
536 536  
537 537  [[image:image-20220709100028-1.png]]
... ... @@ -581,10 +581,44 @@
581 581  )))
582 582  
583 583  
655 +== 2.6 Distance alarm function ==
584 584  
585 -== 2.6  ​LED Indicator ==
657 +➢ AT Command:
586 586  
659 +AT+ LDDSALARM=min,max
587 587  
661 +² When min=0, and max≠0, Alarm higher than max
662 +
663 +² When min≠0, and max=0, Alarm lower than min
664 +
665 +² When min≠0 and max≠0, Alarm higher than max or lower than min
666 +
667 +Example:
668 +
669 +AT+ LDDSALARM=260,2000 ~/~/ Alarm when distance lower than 260.
670 +
671 +
672 +== 2.7 Set the number of data to be uploaded and the recording time ==
673 +
674 +➢ AT Command:
675 +
676 +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)
677 +
678 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
679 +
680 +== 2.8 Read or Clear cached data ==
681 +
682 +➢ AT Command:
683 +
684 +AT+CDP ~/~/ Read cached data
685 +
686 +[[image:image-20220908175333-2.png]]
687 +
688 +AT+CDP=0 ~/~/ Clear cached data
689 +
690 +== 2.9  ​LED Indicator ==
691 +
692 +
588 588  The NDDS75 has an internal LED which is to show the status of different state.
589 589  
590 590  
... ... @@ -599,23 +599,27 @@
599 599  
600 600  
601 601  
602 -== 2.7  ​Firmware Change Log ==
707 +== 2.10  ​Firmware Change Log ==
603 603  
604 604  
605 -Download URL & Firmware Change log
710 +(((
711 +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]]
712 +)))
606 606  
607 607  (((
608 -[[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/]]
715 +
609 609  )))
610 610  
718 +(((
719 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
720 +)))
611 611  
612 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
613 613  
614 614  
724 +== 2.11  ​Battery Analysis ==
615 615  
616 -== 2.8  ​Battery Analysis ==
617 617  
618 -=== 2.8.1  ​Battery Type ===
727 +=== 2.11.1  ​Battery Type ===
619 619  
620 620  
621 621  (((
... ... @@ -640,8 +640,9 @@
640 640  
641 641  
642 642  
643 -=== 2.8.2  Power consumption Analyze ===
752 +=== 2.11.2  Power consumption Analyze ===
644 644  
754 +
645 645  (((
646 646  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.
647 647  )))
... ... @@ -678,8 +678,9 @@
678 678  
679 679  
680 680  
681 -=== 2.8.3  ​Battery Note ===
791 +=== 2.11.3  ​Battery Note ===
682 682  
793 +
683 683  (((
684 684  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.
685 685  )))
... ... @@ -686,8 +686,9 @@
686 686  
687 687  
688 688  
689 -=== 2.8.4  Replace the battery ===
800 +=== 2.11.4  Replace the battery ===
690 690  
802 +
691 691  (((
692 692  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).
693 693  )))
... ... @@ -696,6 +696,7 @@
696 696  
697 697  = 3. ​ Access NB-IoT Module =
698 698  
811 +
699 699  (((
700 700  Users can directly access the AT command set of the NB-IoT module.
701 701  )))
... ... @@ -702,6 +702,8 @@
702 702  
703 703  (((
704 704  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/]] 
818 +
819 +
705 705  )))
706 706  
707 707  [[image:1657333200519-600.png]]
... ... @@ -710,11 +710,13 @@
710 710  
711 711  = 4.  Using the AT Commands =
712 712  
828 +
713 713  == 4.1  Access AT Commands ==
714 714  
715 -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/]]
716 716  
832 +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]]
717 717  
834 +
718 718  AT+<CMD>?  : Help on <CMD>
719 719  
720 720  AT+<CMD>         : Run <CMD>
... ... @@ -754,7 +754,23 @@
754 754  
755 755  AT+SERVADDR  : Server Address
756 756  
874 +AT+TR      : Get or Set record time"
757 757  
876 +AT+APN     : Get or set the APN
877 +
878 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
879 +
880 +AT+DNSCFG  : Get or Set DNS Server
881 +
882 +AT+GETSENSORVALUE   : Returns the current sensor measurement
883 +
884 +AT+NOUD      : Get or Set the number of data to be uploaded
885 +
886 +AT+CDP     : Read or Clear cached data
887 +
888 +AT+LDDSALARM : Get or Set alarm of distance
889 +
890 +
758 758  (% style="color:#037691" %)**COAP Management**      
759 759  
760 760  AT+URI            : Resource parameters
... ... @@ -788,6 +788,7 @@
788 788  
789 789  = ​5.  FAQ =
790 790  
924 +
791 791  == 5.1 ​ How to Upgrade Firmware ==
792 792  
793 793  
... ... @@ -800,7 +800,7 @@
800 800  )))
801 801  
802 802  (((
803 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
937 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
804 804  )))
805 805  
806 806  
... ... @@ -807,6 +807,7 @@
807 807  
808 808  = 6.  Trouble Shooting =
809 809  
944 +
810 810  == 6.1  ​Connection problem when uploading firmware ==
811 811  
812 812  
... ... @@ -822,6 +822,7 @@
822 822  
823 823  == 6.2  AT Command input doesn't work ==
824 824  
960 +
825 825  (((
826 826  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.
827 827  
... ... @@ -847,7 +847,7 @@
847 847  
848 848  (% style="color:#037691" %)**Package Includes**:
849 849  
850 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
986 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
851 851  * External antenna x 1
852 852  )))
853 853  
... ... @@ -854,9 +854,9 @@
854 854  (((
855 855  
856 856  
993 +
857 857  (% style="color:#037691" %)**Dimension and weight**:
858 858  
859 -
860 860  * Device Size: 13.0 x 5 x 4.5 cm
861 861  * Device Weight: 150g
862 862  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -872,5 +872,6 @@
872 872  
873 873  = 9.  Support =
874 874  
1011 +
875 875  * 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.
876 876  * 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,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content

Applications

Navigation

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