<
From version < 91.4 >
edited by Xiaoling
on 2022/07/09 09:59
To version < 105.1 >
edited by David Huang
on 2022/10/08 11:49
>
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
... ... @@ -7,6 +7,7 @@
7 7  
8 8  **Table of Contents:**
9 9  
10 +{{toc/}}
10 10  
11 11  
12 12  
... ... @@ -15,6 +15,7 @@
15 15  
16 16  = 1.  Introduction =
17 17  
19 +
18 18  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 19  
20 20  (((
... ... @@ -21,20 +21,34 @@
21 21  
22 22  
23 23  (((
26 +(((
24 24  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.
25 -\\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.
26 -\\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.
27 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 -\\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)
29 -\\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.
30 30  )))
31 31  
32 -
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.
33 33  )))
34 34  
35 -[[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 +)))
36 36  
38 +(((
39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 +)))
37 37  
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 +
38 38  [[image:1657327959271-447.png]]
39 39  
40 40  
... ... @@ -84,12 +84,12 @@
84 84  (% style="color:#037691" %)**Power Consumption**
85 85  
86 86  * STOP Mode: 10uA @ 3.3v
87 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
103 +* Max transmit power: 350mA@3.3v
88 88  
89 89  
90 -
91 91  == ​1.4  Applications ==
92 92  
108 +
93 93  * Smart Buildings & Home Automation
94 94  * Logistics and Supply Chain Management
95 95  * Smart Metering
... ... @@ -102,6 +102,7 @@
102 102  
103 103  
104 104  
121 +
105 105  == 1.5  Pin Definitions ==
106 106  
107 107  
... ... @@ -111,8 +111,10 @@
111 111  
112 112  = 2.  Use NDDS75 to communicate with IoT Server =
113 113  
131 +
114 114  == 2.1  How it works ==
115 115  
134 +
116 116  (((
117 117  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.
118 118  )))
... ... @@ -138,16 +138,17 @@
138 138  
139 139  === 2.2.1 Test Requirement ===
140 140  
160 +
141 141  (((
142 142  To use NDDS75 in your city, make sure meet below requirements:
143 143  )))
144 144  
145 145  * Your local operator has already distributed a NB-IoT Network there.
146 -* The local NB-IoT network used the band that NSE01 supports.
166 +* The local NB-IoT network used the band that NDDS75 supports.
147 147  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
148 148  
149 149  (((
150 -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.
151 151  )))
152 152  
153 153  
... ... @@ -157,6 +157,7 @@
157 157  
158 158  === 2.2.2 Insert SIM card ===
159 159  
180 +
160 160  (((
161 161  Insert the NB-IoT Card get from your provider.
162 162  )))
... ... @@ -172,6 +172,7 @@
172 172  
173 173  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
174 174  
196 +
175 175  (((
176 176  (((
177 177  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.
... ... @@ -180,15 +180,16 @@
180 180  
181 181  [[image:image-20220709092052-2.png]]
182 182  
183 -**Connection:**
184 184  
185 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
206 +(% style="color:blue" %)**Connection:**
186 186  
187 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
208 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
188 188  
189 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
210 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
190 190  
212 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
191 191  
214 +
192 192  In the PC, use below serial tool settings:
193 193  
194 194  * Baud:  (% style="color:green" %)**9600**
... ... @@ -203,8 +203,9 @@
203 203  
204 204  [[image:1657329814315-101.png]]
205 205  
229 +
206 206  (((
207 -(% 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]]**
208 208  )))
209 209  
210 210  
... ... @@ -211,22 +211,43 @@
211 211  
212 212  === 2.2.4 Use CoAP protocol to uplink data ===
213 213  
214 -(% 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/]]
215 215  
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/]]**
216 216  
241 +
242 +(((
217 217  **Use below commands:**
244 +)))
218 218  
219 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
220 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
221 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
246 +* (((
247 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
248 +)))
249 +* (((
250 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
251 +)))
252 +* (((
253 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
222 222  
255 +
256 +
257 +)))
258 +
259 +(((
223 223  For parameter description, please refer to AT command set
224 224  
262 +
263 +)))
264 +
225 225  [[image:1657330452568-615.png]]
226 226  
227 227  
268 +
269 +(((
228 228  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.
229 229  
272 +
273 +)))
274 +
230 230  [[image:1657330472797-498.png]]
231 231  
232 232  
... ... @@ -234,10 +234,11 @@
234 234  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
235 235  
236 236  
237 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
238 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
239 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
282 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
283 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
284 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
240 240  
286 +
241 241  [[image:1657330501006-241.png]]
242 242  
243 243  
... ... @@ -248,13 +248,13 @@
248 248  === 2.2.6 Use MQTT protocol to uplink data ===
249 249  
250 250  
251 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
256 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
257 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
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
258 258  
259 259  [[image:1657249978444-674.png]]
260 260  
... ... @@ -271,8 +271,8 @@
271 271  === 2.2.7 Use TCP protocol to uplink data ===
272 272  
273 273  
274 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
275 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
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
276 276  
277 277  [[image:image-20220709093918-1.png]]
278 278  
... ... @@ -283,30 +283,39 @@
283 283  
284 284  === 2.2.8 Change Update Interval ===
285 285  
332 +
286 286  User can use below command to change the (% style="color:green" %)**uplink interval**.
287 287  
288 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
335 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
289 289  
290 290  (((
338 +
339 +
340 +
291 291  (% style="color:red" %)**NOTE:**
292 -)))
293 293  
294 -(((
295 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
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:**
296 296  )))
297 297  
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).**
298 298  
299 299  
351 +
300 300  == 2.3  Uplink Payload ==
301 301  
302 -In this mode, uplink payload includes in total 14 bytes
303 303  
355 +=== 2.3.1  Before Firmware v1.3.2 ===
304 304  
305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
357 +
358 +In this mode, uplink payload includes in total 14 bytes
359 +
360 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
306 306  |=(% style="width: 60px;" %)(((
307 307  **Size(bytes)**
308 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
309 -|(% 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
363 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
364 +|(% 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"]]
310 310  
311 311  (((
312 312  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
... ... @@ -315,8 +315,9 @@
315 315  
316 316  [[image:1657331036973-987.png]]
317 317  
373 +
318 318  (((
319 -The payload is ASCII string, representative same HEX:
375 +The payload is **ASCII** string, representative same HEX:
320 320  )))
321 321  
322 322  (((
... ... @@ -327,11 +327,11 @@
327 327  Device ID: 0x724031556159 = 724031556159
328 328  )))
329 329  * (((
330 -Version: 0x0064=100=1.0.0
386 +Version:  0x0064=100=1.0.0
331 331  )))
332 332  
333 333  * (((
334 -BAT: 0x0c6c = 3180 mV = 3.180V
390 +BAT:  0x0c6c = 3180 mV = 3.180V
335 335  )))
336 336  * (((
337 337  Signal: 0x19 = 25
... ... @@ -341,14 +341,51 @@
341 341  )))
342 342  * (((
343 343  Interrupt: 0x00 = 0
400 +
401 +
402 +
403 +
404 +
344 344  )))
345 345  
407 +=== **2.3.2  Since firmware v1.3.2** ===
346 346  
409 +
410 +In this mode, uplink payload includes 69 bytes in total by default.
411 +
412 +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.
413 +
414 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
415 +|(% 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
416 +|(% 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.......
417 +
418 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
419 +
420 +[[image:image-20220908175246-1.png]]
421 +
422 +
423 +The payload is ASCII string, representative same HEX:
424 +
425 +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:
426 +
427 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
428 +* (% style="color:red" %)Version: 0x0084=132=1.3.2
429 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
430 +* (% style="color:blue" %)Singal: 0x1e = 30
431 +* (% style="color:red" %)Mod: 0x01 = 1
432 +* Interrupt: 0x00= 0
433 +* Distance: 0x0039= 57 = 57
434 +* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
435 +* Distance,Time stamp : 00396319baf0
436 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
437 +
438 +
347 347  == 2.4  Payload Explanation and Sensor Interface ==
348 348  
349 349  
350 350  === 2.4.1  Device ID ===
351 351  
444 +
352 352  (((
353 353  By default, the Device ID equal to the last 6 bytes of IMEI.
354 354  )))
... ... @@ -355,10 +355,12 @@
355 355  
356 356  (((
357 357  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 +
452 +
358 358  )))
359 359  
360 360  (((
361 -**Example:**
456 +(% style="color:blue" %)**Example :**
362 362  )))
363 363  
364 364  (((
... ... @@ -366,13 +366,26 @@
366 366  )))
367 367  
368 368  (((
369 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
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.
370 370  )))
371 371  
372 372  
468 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
373 373  
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 +
374 374  === 2.4.2  Version Info ===
375 375  
483 +
376 376  (((
377 377  Specify the software version: 0x64=100, means firmware version 1.00.
378 378  )))
... ... @@ -385,9 +385,6 @@
385 385  
386 386  === 2.4.3  Battery Info ===
387 387  
388 -(((
389 -Check the battery voltage for LSE01.
390 -)))
391 391  
392 392  (((
393 393  Ex1: 0x0B45 = 2885mV
... ... @@ -401,6 +401,7 @@
401 401  
402 402  === 2.4.4  Signal Strength ===
403 403  
509 +
404 404  (((
405 405  NB-IoT Network signal Strength.
406 406  )))
... ... @@ -431,11 +431,14 @@
431 431  
432 432  
433 433  
434 -=== 2.4.5  Soil Moisture ===
540 +=== 2.4.5  Distance ===
435 435  
542 +
436 436  Get the distance. Flat object range 280mm - 7500mm.
437 437  
545 +(((
438 438  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
547 +)))
439 439  
440 440  (((
441 441  (((
... ... @@ -453,6 +453,7 @@
453 453  
454 454  === 2.4.6  Digital Interrupt ===
455 455  
565 +
456 456  (((
457 457  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.
458 458  )))
... ... @@ -462,7 +462,7 @@
462 462  )))
463 463  
464 464  (((
465 -(% 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]])**.**
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]])**.**
466 466  )))
467 467  
468 468  
... ... @@ -487,6 +487,7 @@
487 487  
488 488  === 2.4.7  ​+5V Output ===
489 489  
600 +
490 490  (((
491 491  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
492 492  )))
... ... @@ -494,10 +494,14 @@
494 494  
495 495  (((
496 496  The 5V output time can be controlled by AT Command.
608 +
609 +
497 497  )))
498 498  
499 499  (((
500 500  (% style="color:blue" %)**AT+5VT=1000**
614 +
615 +
501 501  )))
502 502  
503 503  (((
... ... @@ -508,11 +508,12 @@
508 508  
509 509  == 2.5  Downlink Payload ==
510 510  
511 -By default, NSE01 prints the downlink payload to console port.
512 512  
513 -[[image:image-20220708133731-5.png]]
627 +By default, NDDS75 prints the downlink payload to console port.
514 514  
629 +[[image:image-20220709100028-1.png]]
515 515  
631 +
516 516  (((
517 517  (% style="color:blue" %)**Examples:**
518 518  )))
... ... @@ -546,7 +546,7 @@
546 546  )))
547 547  
548 548  (((
549 -If payload = 0x04FF, it will reset the NSE01
665 +If payload = 0x04FF, it will reset the NDDS75
550 550  )))
551 551  
552 552  
... ... @@ -558,78 +558,96 @@
558 558  
559 559  
560 560  
561 -== 2.6  ​LED Indicator ==
677 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
562 562  
563 -(((
564 -The NSE01 has an internal LED which is to show the status of different state.
565 565  
680 +(% style="color:blue" %)** ➢ AT Command:**
566 566  
567 -* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
568 -* Then the LED will be on for 1 second means device is boot normally.
569 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
570 -* For each uplink probe, LED will be on for 500ms.
571 -)))
682 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
572 572  
684 +² When min=0, and max≠0, Alarm higher than max
573 573  
686 +² When min≠0, and max=0, Alarm lower than min
574 574  
688 +² When min≠0 and max≠0, Alarm higher than max or lower than min
575 575  
576 -== 2.7  Installation in Soil ==
577 577  
578 -__**Measurement the soil surface**__
691 +(% style="color:blue" %)** Example:**
579 579  
580 -(((
581 -Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
582 -)))
693 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
583 583  
584 -[[image:1657259653666-883.png]] ​
585 585  
586 586  
587 -(((
588 -
697 +== 2.7  Set the number of data to be uploaded and the recording time ==
589 589  
590 -(((
591 -Dig a hole with diameter > 20CM.
592 -)))
593 593  
594 -(((
595 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
596 -)))
597 -)))
700 +(% style="color:blue" %)** ➢ AT Command:**
598 598  
599 -[[image:1654506665940-119.png]]
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.
600 600  
705 +This link explains the relationship between TR, NOUD and TDC more clearly **: **[[https:~~/~~/www.processon.com/view/link/6340e606e401fd390891af87>>url:https://www.processon.com/view/link/6340e606e401fd390891af87]]
706 +
707 +== 2.8  Read or Clear cached data ==
708 +
709 +
710 +(% style="color:blue" %)** ➢ AT Command:**
711 +
712 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
713 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
714 +
715 +[[image:image-20220908175333-2.png]]
716 +
717 +
718 +
719 +== 2.9  ​LED Indicator ==
720 +
721 +
722 +The NDDS75 has an internal LED which is to show the status of different state.
723 +
724 +
725 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
726 +* Then the LED will be on for 1 second means device is boot normally.
727 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
728 +* For each uplink probe, LED will be on for 500ms.
729 +
601 601  (((
602 602  
603 603  )))
604 604  
605 605  
606 -== 2.8  ​Firmware Change Log ==
607 607  
736 +== 2.10  ​Firmware Change Log ==
608 608  
609 -Download URL & Firmware Change log
610 610  
611 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
739 +(((
740 +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]]
741 +)))
612 612  
743 +(((
744 +
745 +)))
613 613  
614 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
747 +(((
748 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
749 +)))
615 615  
616 616  
617 617  
618 -== 2.9  ​Battery Analysis ==
753 +== 2.11  ​Battery Analysis ==
619 619  
620 -=== 2.9.1  ​Battery Type ===
621 621  
756 +=== 2.11.1  ​Battery Type ===
622 622  
758 +
623 623  (((
624 -The NSE01 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.
760 +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.
625 625  )))
626 626  
627 -
628 628  (((
629 629  The battery is designed to last for several years depends on the actually use environment and update interval. 
630 630  )))
631 631  
632 -
633 633  (((
634 634  The battery related documents as below:
635 635  )))
... ... @@ -639,13 +639,14 @@
639 639  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 640  
641 641  (((
642 -[[image:image-20220708140453-6.png]]
776 +[[image:image-20220709101450-2.png]]
643 643  )))
644 644  
645 645  
646 646  
647 -=== 2.9.2  Power consumption Analyze ===
781 +=== 2.11.2  Power consumption Analyze ===
648 648  
783 +
649 649  (((
650 650  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.
651 651  )))
... ... @@ -678,12 +678,13 @@
678 678  And the Life expectation in difference case will be shown on the right.
679 679  )))
680 680  
681 -[[image:image-20220708141352-7.jpeg]]
816 +[[image:image-20220709110451-3.png]]
682 682  
683 683  
684 684  
685 -=== 2.9.3  ​Battery Note ===
820 +=== 2.11.3  ​Battery Note ===
686 686  
822 +
687 687  (((
688 688  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.
689 689  )))
... ... @@ -690,10 +690,11 @@
690 690  
691 691  
692 692  
693 -=== 2.9.4  Replace the battery ===
829 +=== 2.11.4  Replace the battery ===
694 694  
831 +
695 695  (((
696 -The default battery pack of NSE01 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).
833 +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).
697 697  )))
698 698  
699 699  
... ... @@ -700,6 +700,7 @@
700 700  
701 701  = 3. ​ Access NB-IoT Module =
702 702  
840 +
703 703  (((
704 704  Users can directly access the AT command set of the NB-IoT module.
705 705  )))
... ... @@ -706,92 +706,113 @@
706 706  
707 707  (((
708 708  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/]] 
847 +
848 +
709 709  )))
710 710  
711 -[[image:1657261278785-153.png]]
851 +[[image:1657333200519-600.png]]
712 712  
713 713  
714 714  
715 715  = 4.  Using the AT Commands =
716 716  
857 +
717 717  == 4.1  Access AT Commands ==
718 718  
719 -See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
720 720  
861 +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]]
721 721  
722 -AT+<CMD>?  : Help on <CMD>
723 723  
724 -AT+<CMD>         : Run <CMD>
864 +AT+<CMD>?  :  Help on <CMD>
725 725  
726 -AT+<CMD>=<value> : Set the value
866 +AT+<CMD>         :  Run <CMD>
727 727  
728 -AT+<CMD>= : Get the value
868 +AT+<CMD>=<value> :  Set the value
729 729  
870 +AT+<CMD>=?  :  Get the value
730 730  
872 +
731 731  (% style="color:#037691" %)**General Commands**(%%)      
732 732  
733 -AT  : Attention       
875 +AT  :  Attention       
734 734  
735 -AT?  : Short Help     
877 +AT?  :  Short Help     
736 736  
737 -ATZ  : MCU Reset    
879 +ATZ  :  MCU Reset    
738 738  
739 -AT+TDC  : Application Data Transmission Interval
881 +AT+TDC  :  Application Data Transmission Interval
740 740  
741 -AT+CFG  : Print all configurations
883 +AT+CFG  :  Print all configurations
742 742  
743 -AT+CFGMOD           : Working mode selection
885 +AT+CFGMOD           :  Working mode selection
744 744  
745 -AT+INTMOD            : Set the trigger interrupt mode
887 +AT+INTMOD            :  Set the trigger interrupt mode
746 746  
747 -AT+5VT  : Set extend the time of 5V power  
889 +AT+5VT  :  Set extend the time of 5V power  
748 748  
749 -AT+PRO  : Choose agreement
891 +AT+PRO  :  Choose agreement
750 750  
751 -AT+WEIGRE  : Get weight or set weight to 0
893 +AT+WEIGRE  :  Get weight or set weight to 0
752 752  
753 -AT+WEIGAP  : Get or Set the GapValue of weight
895 +AT+WEIGAP  :  Get or Set the GapValue of weight
754 754  
755 -AT+RXDL  : Extend the sending and receiving time
897 +AT+RXDL  :  Extend the sending and receiving time
756 756  
757 -AT+CNTFAC  : Get or set counting parameters
899 +AT+CNTFAC  :  Get or set counting parameters
758 758  
759 -AT+SERVADDR  : Server Address
901 +AT+SERVADDR  :  Server Address
760 760  
903 +AT+TR  :  Get or Set record time"
761 761  
905 +AT+APN     :  Get or set the APN
906 +
907 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
908 +
909 +AT+DNSCFG  : Get or Set DNS Server
910 +
911 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
912 +
913 +AT+NOUD  :  Get or Set the number of data to be uploaded
914 +
915 +AT+CDP     :  Read or Clear cached data
916 +
917 +AT+LDDSALARM :  Get or Set alarm of distance
918 +
919 +
762 762  (% style="color:#037691" %)**COAP Management**      
763 763  
764 -AT+URI            : Resource parameters
922 +AT+URI            :  Resource parameters
765 765  
766 766  
767 767  (% style="color:#037691" %)**UDP Management**
768 768  
769 -AT+CFM          : Upload confirmation mode (only valid for UDP)
927 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
770 770  
771 771  
772 772  (% style="color:#037691" %)**MQTT Management**
773 773  
774 -AT+CLIENT               : Get or Set MQTT client
932 +AT+CLIENT  :  Get or Set MQTT client
775 775  
776 -AT+UNAME  : Get or Set MQTT Username
934 +AT+UNAME  :  Get or Set MQTT Username
777 777  
778 -AT+PWD                  : Get or Set MQTT password
936 +AT+PWD  :  Get or Set MQTT password
779 779  
780 -AT+PUBTOPIC  : Get or Set MQTT publish topic
938 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
781 781  
782 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
940 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
783 783  
784 784  
785 785  (% style="color:#037691" %)**Information**          
786 786  
787 -AT+FDR  : Factory Data Reset
945 +AT+FDR  :  Factory Data Reset
788 788  
789 -AT+PWORD  : Serial Access Password
947 +AT+PWORD  :  Serial Access Password
790 790  
791 791  
792 792  
793 793  = ​5.  FAQ =
794 794  
953 +
795 795  == 5.1 ​ How to Upgrade Firmware ==
796 796  
797 797  
... ... @@ -804,20 +804,14 @@
804 804  )))
805 805  
806 806  (((
807 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
966 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
808 808  )))
809 809  
810 810  
811 811  
812 -== 5.2  Can I calibrate NSE01 to different soil types? ==
813 -
814 -(((
815 -NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
816 -)))
817 -
818 -
819 819  = 6.  Trouble Shooting =
820 820  
973 +
821 821  == 6.1  ​Connection problem when uploading firmware ==
822 822  
823 823  
... ... @@ -833,6 +833,7 @@
833 833  
834 834  == 6.2  AT Command input doesn't work ==
835 835  
989 +
836 836  (((
837 837  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.
838 838  
... ... @@ -843,7 +843,7 @@
843 843  = 7. ​ Order Info =
844 844  
845 845  
846 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1000 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
847 847  
848 848  
849 849  (% class="wikigeneratedid" %)
... ... @@ -858,7 +858,7 @@
858 858  
859 859  (% style="color:#037691" %)**Package Includes**:
860 860  
861 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1015 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
862 862  * External antenna x 1
863 863  )))
864 864  
... ... @@ -865,10 +865,13 @@
865 865  (((
866 866  
867 867  
1022 +
868 868  (% style="color:#037691" %)**Dimension and weight**:
869 869  
870 -* Size: 195 x 125 x 55 mm
871 -* Weight:   420g
1025 +* Device Size: 13.0 x 5 x 4.5 cm
1026 +* Device Weight: 150g
1027 +* Package Size / pcs : 15 x 12x 5.5 cm
1028 +* Weight / pcs : 220g
872 872  )))
873 873  
874 874  (((
... ... @@ -880,5 +880,6 @@
880 880  
881 881  = 9.  Support =
882 882  
1040 +
883 883  * 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.
884 884  * 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]]
1657332990863-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0