Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.14 >
edited by Xiaoling
on 2022/07/09 11:47
To version < 104.5 >
edited by Xiaoling
on 2022/09/09 12:00
>
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  (((
... ... @@ -27,27 +27,22 @@
27 27  )))
28 28  
29 29  (((
30 -
31 31  The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 32  )))
33 33  
34 34  (((
35 -
36 36  NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
37 37  )))
38 38  
39 39  (((
40 -
41 41  NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
42 42  )))
43 43  
44 44  (((
45 -
46 46  NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
47 47  )))
48 48  
49 49  (((
50 -
51 51  To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
52 52  )))
53 53  )))
... ... @@ -76,6 +76,9 @@
76 76  * 8500mAh Battery for long term use
77 77  
78 78  
75 +
76 +
77 +
79 79  == 1.3  Specification ==
80 80  
81 81  
... ... @@ -107,8 +107,12 @@
107 107  * Max transmit power: 350mA@3.3v
108 108  
109 109  
109 +
110 +
111 +
110 110  == ​1.4  Applications ==
111 111  
114 +
112 112  * Smart Buildings & Home Automation
113 113  * Logistics and Supply Chain Management
114 114  * Smart Metering
... ... @@ -120,6 +120,8 @@
120 120  ​
121 121  
122 122  
126 +
127 +
123 123  == 1.5  Pin Definitions ==
124 124  
125 125  
... ... @@ -129,8 +129,10 @@
129 129  
130 130  = 2.  Use NDDS75 to communicate with IoT Server =
131 131  
137 +
132 132  == 2.1  How it works ==
133 133  
140 +
134 134  (((
135 135  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.
136 136  )))
... ... @@ -156,16 +156,17 @@
156 156  
157 157  === 2.2.1 Test Requirement ===
158 158  
166 +
159 159  (((
160 160  To use NDDS75 in your city, make sure meet below requirements:
161 161  )))
162 162  
163 163  * Your local operator has already distributed a NB-IoT Network there.
164 -* The local NB-IoT network used the band that NSE01 supports.
172 +* The local NB-IoT network used the band that NDDS75 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
167 167  (((
168 -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
176 +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.
169 169  )))
170 170  
171 171  
... ... @@ -175,6 +175,7 @@
175 175  
176 176  === 2.2.2 Insert SIM card ===
177 177  
186 +
178 178  (((
179 179  Insert the NB-IoT Card get from your provider.
180 180  )))
... ... @@ -190,6 +190,7 @@
190 190  
191 191  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
192 192  
202 +
193 193  (((
194 194  (((
195 195  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.
... ... @@ -198,6 +198,7 @@
198 198  
199 199  [[image:image-20220709092052-2.png]]
200 200  
211 +
201 201  **Connection:**
202 202  
203 203   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -221,8 +221,9 @@
221 221  
222 222  [[image:1657329814315-101.png]]
223 223  
235 +
224 224  (((
225 -(% 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/]]
237 +(% 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]]**
226 226  )))
227 227  
228 228  
... ... @@ -229,9 +229,10 @@
229 229  
230 230  === 2.2.4 Use CoAP protocol to uplink data ===
231 231  
232 -(% 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/]]
233 233  
245 +(% 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/]]**
234 234  
247 +
235 235  (((
236 236  **Use below commands:**
237 237  )))
... ... @@ -244,17 +244,25 @@
244 244  )))
245 245  * (((
246 246  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
260 +
261 +
262 +
247 247  )))
248 248  
249 249  (((
250 250  For parameter description, please refer to AT command set
267 +
268 +
251 251  )))
252 252  
253 253  [[image:1657330452568-615.png]]
254 254  
255 255  
274 +
256 256  (((
257 257  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.
277 +
278 +
258 258  )))
259 259  
260 260  [[image:1657330472797-498.png]]
... ... @@ -313,29 +313,38 @@
313 313  
314 314  === 2.2.8 Change Update Interval ===
315 315  
337 +
316 316  User can use below command to change the (% style="color:green" %)**uplink interval**.
317 317  
318 318  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
319 319  
320 320  (((
343 +
344 +
345 +
321 321  (% style="color:red" %)**NOTE:**
322 -)))
323 323  
324 -(((
325 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
348 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
349 +
350 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
326 326  )))
327 327  
353 +(% 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).**
328 328  
329 329  
356 +
330 330  == 2.3  Uplink Payload ==
331 331  
332 -In this mode, uplink payload includes in total 14 bytes
333 333  
360 +=== 2.3.1  Before Firmware 1.3.2 ===
334 334  
335 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
362 +
363 +In this mode, uplink payload includes in total 14 bytes
364 +
365 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
336 336  |=(% style="width: 60px;" %)(((
337 337  **Size(bytes)**
338 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 60px;" %)**1**
368 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
339 339  |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
340 340  
341 341  (((
... ... @@ -345,8 +345,9 @@
345 345  
346 346  [[image:1657331036973-987.png]]
347 347  
378 +
348 348  (((
349 -The payload is ASCII string, representative same HEX:
380 +The payload is **ASCII** string, representative same HEX:
350 350  )))
351 351  
352 352  (((
... ... @@ -357,11 +357,11 @@
357 357  Device ID: 0x724031556159 = 724031556159
358 358  )))
359 359  * (((
360 -Version: 0x0064=100=1.0.0
391 +Version:  0x0064=100=1.0.0
361 361  )))
362 362  
363 363  * (((
364 -BAT: 0x0c6c = 3180 mV = 3.180V
395 +BAT:  0x0c6c = 3180 mV = 3.180V
365 365  )))
366 366  * (((
367 367  Signal: 0x19 = 25
... ... @@ -374,14 +374,51 @@
374 374  
375 375  
376 376  
408 +
377 377  
378 378  )))
379 379  
412 +=== **2.3.2  Since firmware v1.3.2** ===
413 +
414 +
415 +In this mode, uplink payload includes 69 bytes in total by default.
416 +
417 +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.
418 +
419 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
420 +|(% 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
421 +|(% 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.......
422 +
423 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
424 +
425 +[[image:image-20220908175246-1.png]]
426 +
427 +
428 +The payload is ASCII string, representative same HEX:
429 +
430 +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:
431 +
432 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
433 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
434 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
435 +* (% style="color:blue" %)Singal: 0x1e = 30
436 +* (% style="color:red" %)Mod: 0x01 = 1
437 +* Interrupt: 0x00= 0
438 +* Distance: 0x0039= 57 = 57
439 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
440 +* Distance,Time stamp : 00396319baf0
441 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
442 +
443 +
444 +
445 +
446 +
380 380  == 2.4  Payload Explanation and Sensor Interface ==
381 381  
382 382  
383 383  === 2.4.1  Device ID ===
384 384  
452 +
385 385  (((
386 386  By default, the Device ID equal to the last 6 bytes of IMEI.
387 387  )))
... ... @@ -388,10 +388,12 @@
388 388  
389 389  (((
390 390  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
459 +
460 +
391 391  )))
392 392  
393 393  (((
394 -**Example:**
464 +(% style="color:blue" %)**Example :**
395 395  )))
396 396  
397 397  (((
... ... @@ -399,13 +399,26 @@
399 399  )))
400 400  
401 401  (((
402 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
472 +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.
403 403  )))
404 404  
405 405  
476 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
406 406  
478 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
479 +
480 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
481 +
482 +
483 +(% style="color:blue" %)**Example :**
484 +
485 +AT+DEUI=868411056754138
486 +
487 +
488 +
407 407  === 2.4.2  Version Info ===
408 408  
491 +
409 409  (((
410 410  Specify the software version: 0x64=100, means firmware version 1.00.
411 411  )))
... ... @@ -418,6 +418,7 @@
418 418  
419 419  === 2.4.3  Battery Info ===
420 420  
504 +
421 421  (((
422 422  Ex1: 0x0B45 = 2885mV
423 423  )))
... ... @@ -430,6 +430,7 @@
430 430  
431 431  === 2.4.4  Signal Strength ===
432 432  
517 +
433 433  (((
434 434  NB-IoT Network signal Strength.
435 435  )))
... ... @@ -462,9 +462,12 @@
462 462  
463 463  === 2.4.5  Distance ===
464 464  
550 +
465 465  Get the distance. Flat object range 280mm - 7500mm.
466 466  
553 +(((
467 467  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
555 +)))
468 468  
469 469  (((
470 470  (((
... ... @@ -482,6 +482,7 @@
482 482  
483 483  === 2.4.6  Digital Interrupt ===
484 484  
573 +
485 485  (((
486 486  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.
487 487  )))
... ... @@ -516,6 +516,7 @@
516 516  
517 517  === 2.4.7  ​+5V Output ===
518 518  
608 +
519 519  (((
520 520  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
521 521  )))
... ... @@ -523,10 +523,14 @@
523 523  
524 524  (((
525 525  The 5V output time can be controlled by AT Command.
616 +
617 +
526 526  )))
527 527  
528 528  (((
529 529  (% style="color:blue" %)**AT+5VT=1000**
622 +
623 +
530 530  )))
531 531  
532 532  (((
... ... @@ -537,6 +537,7 @@
537 537  
538 538  == 2.5  Downlink Payload ==
539 539  
634 +
540 540  By default, NDDS75 prints the downlink payload to console port.
541 541  
542 542  [[image:image-20220709100028-1.png]]
... ... @@ -587,9 +587,54 @@
587 587  
588 588  
589 589  
590 -== 2.6  ​LED Indicator ==
685 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
591 591  
592 592  
688 +(% style="color:blue" %)** ➢ AT Command:**
689 +
690 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
691 +
692 +² When min=0, and max≠0, Alarm higher than max
693 +
694 +² When min≠0, and max=0, Alarm lower than min
695 +
696 +² When min≠0 and max≠0, Alarm higher than max or lower than min
697 +
698 +
699 +(% style="color:blue" %)** Example:**
700 +
701 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
702 +
703 +
704 +
705 +== 2.7  Set the number of data to be uploaded and the recording time ==
706 +
707 +
708 +(% style="color:blue" %)** ➢ AT Command:**
709 +
710 +* (% 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)
711 +* (% 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.
712 +
713 +
714 +
715 +
716 +== 2.8  Read or Clear cached data ==
717 +
718 +
719 +(% style="color:blue" %)** ➢ AT Command:**
720 +
721 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
722 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
723 +
724 +
725 +
726 +[[image:image-20220908175333-2.png]]
727 +
728 +
729 +
730 +== 2.9  ​LED Indicator ==
731 +
732 +
593 593  The NDDS75 has an internal LED which is to show the status of different state.
594 594  
595 595  
... ... @@ -604,23 +604,27 @@
604 604  
605 605  
606 606  
607 -== 2.7  ​Firmware Change Log ==
747 +== 2.10  ​Firmware Change Log ==
608 608  
609 609  
610 -Download URL & Firmware Change log
750 +(((
751 +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]]
752 +)))
611 611  
612 612  (((
613 -[[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/]]
755 +
614 614  )))
615 615  
758 +(((
759 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
760 +)))
616 616  
617 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
618 618  
619 619  
764 +== 2.11  ​Battery Analysis ==
620 620  
621 -== 2.8  ​Battery Analysis ==
622 622  
623 -=== 2.8.1  ​Battery Type ===
767 +=== 2.11.1  ​Battery Type ===
624 624  
625 625  
626 626  (((
... ... @@ -645,8 +645,9 @@
645 645  
646 646  
647 647  
648 -=== 2.8.2  Power consumption Analyze ===
792 +=== 2.11.2  Power consumption Analyze ===
649 649  
794 +
650 650  (((
651 651  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.
652 652  )))
... ... @@ -683,8 +683,9 @@
683 683  
684 684  
685 685  
686 -=== 2.8.3  ​Battery Note ===
831 +=== 2.11.3  ​Battery Note ===
687 687  
833 +
688 688  (((
689 689  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.
690 690  )))
... ... @@ -691,8 +691,9 @@
691 691  
692 692  
693 693  
694 -=== 2.8.4  Replace the battery ===
840 +=== 2.11.4  Replace the battery ===
695 695  
842 +
696 696  (((
697 697  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).
698 698  )))
... ... @@ -701,6 +701,7 @@
701 701  
702 702  = 3. ​ Access NB-IoT Module =
703 703  
851 +
704 704  (((
705 705  Users can directly access the AT command set of the NB-IoT module.
706 706  )))
... ... @@ -707,6 +707,8 @@
707 707  
708 708  (((
709 709  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/]] 
858 +
859 +
710 710  )))
711 711  
712 712  [[image:1657333200519-600.png]]
... ... @@ -715,11 +715,13 @@
715 715  
716 716  = 4.  Using the AT Commands =
717 717  
868 +
718 718  == 4.1  Access AT Commands ==
719 719  
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/]]
721 721  
872 +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]]
722 722  
874 +
723 723  AT+<CMD>?  : Help on <CMD>
724 724  
725 725  AT+<CMD>         : Run <CMD>
... ... @@ -759,7 +759,23 @@
759 759  
760 760  AT+SERVADDR  : Server Address
761 761  
914 +AT+TR      : Get or Set record time"
762 762  
916 +AT+APN     : Get or set the APN
917 +
918 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
919 +
920 +AT+DNSCFG  : Get or Set DNS Server
921 +
922 +AT+GETSENSORVALUE   : Returns the current sensor measurement
923 +
924 +AT+NOUD      : Get or Set the number of data to be uploaded
925 +
926 +AT+CDP     : Read or Clear cached data
927 +
928 +AT+LDDSALARM : Get or Set alarm of distance
929 +
930 +
763 763  (% style="color:#037691" %)**COAP Management**      
764 764  
765 765  AT+URI            : Resource parameters
... ... @@ -793,6 +793,7 @@
793 793  
794 794  = ​5.  FAQ =
795 795  
964 +
796 796  == 5.1 ​ How to Upgrade Firmware ==
797 797  
798 798  
... ... @@ -805,7 +805,7 @@
805 805  )))
806 806  
807 807  (((
808 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
977 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
809 809  )))
810 810  
811 811  
... ... @@ -812,6 +812,7 @@
812 812  
813 813  = 6.  Trouble Shooting =
814 814  
984 +
815 815  == 6.1  ​Connection problem when uploading firmware ==
816 816  
817 817  
... ... @@ -827,6 +827,7 @@
827 827  
828 828  == 6.2  AT Command input doesn't work ==
829 829  
1000 +
830 830  (((
831 831  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.
832 832  
... ... @@ -852,7 +852,7 @@
852 852  
853 853  (% style="color:#037691" %)**Package Includes**:
854 854  
855 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1026 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
856 856  * External antenna x 1
857 857  )))
858 858  
... ... @@ -859,9 +859,9 @@
859 859  (((
860 860  
861 861  
1033 +
862 862  (% style="color:#037691" %)**Dimension and weight**:
863 863  
864 -
865 865  * Device Size: 13.0 x 5 x 4.5 cm
866 866  * Device Weight: 150g
867 867  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -877,5 +877,6 @@
877 877  
878 878  = 9.  Support =
879 879  
1051 +
880 880  * 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.
881 881  * 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