<
From version < 95.4 >
edited by Xiaoling
on 2022/07/09 10:46
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  (((
... ... @@ -22,20 +22,34 @@
22 22  
23 23  
24 24  (((
26 +(((
25 25  The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
26 -\\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.
27 -\\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.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\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)
30 -\\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.
31 31  )))
32 32  
33 -
30 +(((
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.
34 34  )))
35 35  
36 -[[image:1654503236291-817.png]]
34 +(((
35 +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.
36 +)))
37 37  
38 +(((
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 +)))
38 38  
42 +(((
43 +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)
44 +)))
45 +
46 +(((
47 +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.
48 +)))
49 +)))
50 +
51 +
52 +)))
53 +
39 39  [[image:1657327959271-447.png]]
40 40  
41 41  
... ... @@ -57,6 +57,8 @@
57 57  * 8500mAh Battery for long term use
58 58  
59 59  
75 +
76 +
60 60  == 1.3  Specification ==
61 61  
62 62  
... ... @@ -65,6 +65,8 @@
65 65  * Supply Voltage: 2.1v ~~ 3.6v
66 66  * Operating Temperature: -40 ~~ 85°C
67 67  
85 +
86 +
68 68  (% style="color:#037691" %)**NB-IoT Spec:**
69 69  
70 70  * - B1 @H-FDD: 2100MHz
... ... @@ -74,6 +74,8 @@
74 74  * - B20 @H-FDD: 800MHz
75 75  * - B28 @H-FDD: 700MHz
76 76  
96 +
97 +
77 77  (% style="color:#037691" %)**Battery:**
78 78  
79 79  * Li/SOCI2 un-chargeable battery
... ... @@ -82,15 +82,19 @@
82 82  * Max continuously current: 130mA
83 83  * Max boost current: 2A, 1 second
84 84  
106 +
107 +
85 85  (% style="color:#037691" %)**Power Consumption**
86 86  
87 87  * STOP Mode: 10uA @ 3.3v
88 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
111 +* Max transmit power: 350mA@3.3v
89 89  
90 90  
91 91  
115 +
92 92  == ​1.4  Applications ==
93 93  
118 +
94 94  * Smart Buildings & Home Automation
95 95  * Logistics and Supply Chain Management
96 96  * Smart Metering
... ... @@ -103,6 +103,7 @@
103 103  
104 104  
105 105  
131 +
106 106  == 1.5  Pin Definitions ==
107 107  
108 108  
... ... @@ -112,8 +112,10 @@
112 112  
113 113  = 2.  Use NDDS75 to communicate with IoT Server =
114 114  
141 +
115 115  == 2.1  How it works ==
116 116  
144 +
117 117  (((
118 118  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.
119 119  )))
... ... @@ -139,16 +139,19 @@
139 139  
140 140  === 2.2.1 Test Requirement ===
141 141  
170 +
142 142  (((
143 143  To use NDDS75 in your city, make sure meet below requirements:
144 144  )))
145 145  
146 146  * Your local operator has already distributed a NB-IoT Network there.
147 -* The local NB-IoT network used the band that NSE01 supports.
176 +* The local NB-IoT network used the band that NDDS75 supports.
148 148  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
149 149  
179 +
180 +
150 150  (((
151 -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
182 +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.
152 152  )))
153 153  
154 154  
... ... @@ -158,6 +158,7 @@
158 158  
159 159  === 2.2.2 Insert SIM card ===
160 160  
192 +
161 161  (((
162 162  Insert the NB-IoT Card get from your provider.
163 163  )))
... ... @@ -173,6 +173,7 @@
173 173  
174 174  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
175 175  
208 +
176 176  (((
177 177  (((
178 178  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.
... ... @@ -181,6 +181,7 @@
181 181  
182 182  [[image:image-20220709092052-2.png]]
183 183  
217 +
184 184  **Connection:**
185 185  
186 186   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -204,8 +204,9 @@
204 204  
205 205  [[image:1657329814315-101.png]]
206 206  
241 +
207 207  (((
208 -(% 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/]]
243 +(% 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]]**
209 209  )))
210 210  
211 211  
... ... @@ -212,21 +212,38 @@
212 212  
213 213  === 2.2.4 Use CoAP protocol to uplink data ===
214 214  
215 -(% 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/]]
216 216  
251 +(% 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/]]**
217 217  
253 +
254 +(((
218 218  **Use below commands:**
256 +)))
219 219  
220 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
221 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
222 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
258 +* (((
259 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
260 +)))
261 +* (((
262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
263 +)))
264 +* (((
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
223 223  
267 +
268 +
269 +)))
270 +
271 +(((
224 224  For parameter description, please refer to AT command set
273 +)))
225 225  
226 226  [[image:1657330452568-615.png]]
227 227  
228 228  
278 +
279 +(((
229 229  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.
281 +)))
230 230  
231 231  [[image:1657330472797-498.png]]
232 232  
... ... @@ -235,10 +235,12 @@
235 235  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
236 236  
237 237  
238 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
239 239  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
240 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
241 241  
294 +
295 +
242 242  [[image:1657330501006-241.png]]
243 243  
244 244  
... ... @@ -249,14 +249,16 @@
249 249  === 2.2.6 Use MQTT protocol to uplink data ===
250 250  
251 251  
252 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
253 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
254 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
255 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
256 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password 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
257 257  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
258 258  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
259 259  
314 +
315 +
260 260  [[image:1657249978444-674.png]]
261 261  
262 262  
... ... @@ -275,6 +275,8 @@
275 275  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
276 276  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
277 277  
334 +
335 +
278 278  [[image:image-20220709093918-1.png]]
279 279  
280 280  
... ... @@ -284,16 +284,15 @@
284 284  
285 285  === 2.2.8 Change Update Interval ===
286 286  
345 +
287 287  User can use below command to change the (% style="color:green" %)**uplink interval**.
288 288  
289 289  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
290 290  
291 -(((
292 -(% style="color:red" %)**NOTE:**
293 -)))
294 294  
351 +
295 295  (((
296 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
353 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
297 297  )))
298 298  
299 299  
... ... @@ -300,14 +300,15 @@
300 300  
301 301  == 2.3  Uplink Payload ==
302 302  
360 +
303 303  In this mode, uplink payload includes in total 14 bytes
304 304  
305 305  
306 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
307 -|=(% style="width: 80px;" %)(((
364 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
365 +|=(% style="width: 60px;" %)(((
308 308  **Size(bytes)**
309 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1**
310 -|(% 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.8A0DigitalInterrupt"]]
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**
368 +|(% 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"]]
311 311  
312 312  (((
313 313  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
... ... @@ -316,6 +316,7 @@
316 316  
317 317  [[image:1657331036973-987.png]]
318 318  
377 +
319 319  (((
320 320  The payload is ASCII string, representative same HEX:
321 321  )))
... ... @@ -342,14 +342,18 @@
342 342  )))
343 343  * (((
344 344  Interrupt: 0x00 = 0
345 -)))
346 346  
347 347  
406 +
407 +
408 +)))
409 +
348 348  == 2.4  Payload Explanation and Sensor Interface ==
349 349  
350 350  
351 351  === 2.4.1  Device ID ===
352 352  
415 +
353 353  (((
354 354  By default, the Device ID equal to the last 6 bytes of IMEI.
355 355  )))
... ... @@ -356,6 +356,8 @@
356 356  
357 357  (((
358 358  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
422 +
423 +
359 359  )))
360 360  
361 361  (((
... ... @@ -374,6 +374,7 @@
374 374  
375 375  === 2.4.2  Version Info ===
376 376  
442 +
377 377  (((
378 378  Specify the software version: 0x64=100, means firmware version 1.00.
379 379  )))
... ... @@ -386,9 +386,6 @@
386 386  
387 387  === 2.4.3  Battery Info ===
388 388  
389 -(((
390 -Check the battery voltage for LSE01.
391 -)))
392 392  
393 393  (((
394 394  Ex1: 0x0B45 = 2885mV
... ... @@ -402,6 +402,7 @@
402 402  
403 403  === 2.4.4  Signal Strength ===
404 404  
468 +
405 405  (((
406 406  NB-IoT Network signal Strength.
407 407  )))
... ... @@ -434,9 +434,12 @@
434 434  
435 435  === 2.4.5  Distance ===
436 436  
501 +
437 437  Get the distance. Flat object range 280mm - 7500mm.
438 438  
504 +(((
439 439  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
506 +)))
440 440  
441 441  (((
442 442  (((
... ... @@ -454,6 +454,7 @@
454 454  
455 455  === 2.4.6  Digital Interrupt ===
456 456  
524 +
457 457  (((
458 458  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.
459 459  )))
... ... @@ -488,6 +488,7 @@
488 488  
489 489  === 2.4.7  ​+5V Output ===
490 490  
559 +
491 491  (((
492 492  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
493 493  )))
... ... @@ -495,10 +495,14 @@
495 495  
496 496  (((
497 497  The 5V output time can be controlled by AT Command.
567 +
568 +
498 498  )))
499 499  
500 500  (((
501 501  (% style="color:blue" %)**AT+5VT=1000**
573 +
574 +
502 502  )))
503 503  
504 504  (((
... ... @@ -509,6 +509,7 @@
509 509  
510 510  == 2.5  Downlink Payload ==
511 511  
585 +
512 512  By default, NDDS75 prints the downlink payload to console port.
513 513  
514 514  [[image:image-20220709100028-1.png]]
... ... @@ -579,19 +579,23 @@
579 579  == 2.7  ​Firmware Change Log ==
580 580  
581 581  
582 -Download URL & Firmware Change log
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 +)))
583 583  
584 584  (((
585 -[[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/]]
661 +
586 586  )))
587 587  
664 +(((
665 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
666 +)))
588 588  
589 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
590 590  
591 591  
592 -
593 593  == 2.8  ​Battery Analysis ==
594 594  
672 +
595 595  === 2.8.1  ​Battery Type ===
596 596  
597 597  
... ... @@ -619,6 +619,7 @@
619 619  
620 620  === 2.8.2  Power consumption Analyze ===
621 621  
700 +
622 622  (((
623 623  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.
624 624  )))
... ... @@ -651,12 +651,13 @@
651 651  And the Life expectation in difference case will be shown on the right.
652 652  )))
653 653  
654 -[[image:image-20220708141352-7.jpeg]]
733 +[[image:image-20220709110451-3.png]]
655 655  
656 656  
657 657  
658 658  === 2.8.3  ​Battery Note ===
659 659  
739 +
660 660  (((
661 661  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.
662 662  )))
... ... @@ -665,6 +665,7 @@
665 665  
666 666  === 2.8.4  Replace the battery ===
667 667  
748 +
668 668  (((
669 669  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).
670 670  )))
... ... @@ -673,6 +673,7 @@
673 673  
674 674  = 3. ​ Access NB-IoT Module =
675 675  
757 +
676 676  (((
677 677  Users can directly access the AT command set of the NB-IoT module.
678 678  )))
... ... @@ -679,6 +679,8 @@
679 679  
680 680  (((
681 681  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/]] 
764 +
765 +
682 682  )))
683 683  
684 684  [[image:1657333200519-600.png]]
... ... @@ -687,11 +687,13 @@
687 687  
688 688  = 4.  Using the AT Commands =
689 689  
774 +
690 690  == 4.1  Access AT Commands ==
691 691  
692 -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/]]
693 693  
778 +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]]
694 694  
780 +
695 695  AT+<CMD>?  : Help on <CMD>
696 696  
697 697  AT+<CMD>         : Run <CMD>
... ... @@ -765,6 +765,7 @@
765 765  
766 766  = ​5.  FAQ =
767 767  
854 +
768 768  == 5.1 ​ How to Upgrade Firmware ==
769 769  
770 770  
... ... @@ -777,7 +777,7 @@
777 777  )))
778 778  
779 779  (((
780 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
867 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
781 781  )))
782 782  
783 783  
... ... @@ -784,6 +784,7 @@
784 784  
785 785  = 6.  Trouble Shooting =
786 786  
874 +
787 787  == 6.1  ​Connection problem when uploading firmware ==
788 788  
789 789  
... ... @@ -799,6 +799,7 @@
799 799  
800 800  == 6.2  AT Command input doesn't work ==
801 801  
890 +
802 802  (((
803 803  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.
804 804  
... ... @@ -824,7 +824,7 @@
824 824  
825 825  (% style="color:#037691" %)**Package Includes**:
826 826  
827 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
916 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
828 828  * External antenna x 1
829 829  )))
830 830  
... ... @@ -831,9 +831,9 @@
831 831  (((
832 832  
833 833  
923 +
834 834  (% style="color:#037691" %)**Dimension and weight**:
835 835  
836 -
837 837  * Device Size: 13.0 x 5 x 4.5 cm
838 838  * Device Weight: 150g
839 839  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -849,5 +849,8 @@
849 849  
850 850  = 9.  Support =
851 851  
941 +
852 852  * 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.
853 853  * 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-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0