Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.16 >
edited by Xiaoling
on 2022/07/09 11:52
To version < 108.9 >
edited by Xiaoling
on 2023/04/04 12:01
>
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  )))
... ... @@ -86,12 +86,12 @@
86 86  
87 87  (% style="color:#037691" %)**NB-IoT Spec:**
88 88  
89 -* - B1 @H-FDD: 2100MHz
90 -* - B3 @H-FDD: 1800MHz
91 -* - B8 @H-FDD: 900MHz
92 -* - B5 @H-FDD: 850MHz
93 -* - B20 @H-FDD: 800MHz
94 -* - B28 @H-FDD: 700MHz
85 +* B1 @H-FDD: 2100MHz
86 +* B3 @H-FDD: 1800MHz
87 +* B8 @H-FDD: 900MHz
88 +* B5 @H-FDD: 850MHz
89 +* B20 @H-FDD: 800MHz
90 +* B28 @H-FDD: 700MHz
95 95  
96 96  (% style="color:#037691" %)**Battery:**
97 97  
... ... @@ -109,6 +109,7 @@
109 109  
110 110  == ​1.4  Applications ==
111 111  
108 +
112 112  * Smart Buildings & Home Automation
113 113  * Logistics and Supply Chain Management
114 114  * Smart Metering
... ... @@ -120,6 +120,7 @@
120 120  ​
121 121  
122 122  
120 +
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  
130 +
132 132  == 2.1  How it works ==
133 133  
133 +
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  
159 +
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.
165 +* 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
169 +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  
179 +
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  
195 +
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,15 +198,16 @@
198 198  
199 199  [[image:image-20220709092052-2.png]]
200 200  
201 -**Connection:**
202 202  
203 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
205 +(% style="color:blue" %)**Connection:**
204 204  
205 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
207 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
206 206  
207 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
209 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
208 208  
211 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
209 209  
213 +
210 210  In the PC, use below serial tool settings:
211 211  
212 212  * Baud:  (% style="color:green" %)**9600**
... ... @@ -221,8 +221,9 @@
221 221  
222 222  [[image:1657329814315-101.png]]
223 223  
228 +
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/]]
230 +(% 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  
238 +(% 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  
240 +
235 235  (((
236 236  **Use below commands:**
237 237  )))
... ... @@ -240,21 +240,29 @@
240 240  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
241 241  )))
242 242  * (((
243 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
249 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
244 244  )))
245 245  * (((
246 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
252 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
253 +
254 +
255 +
247 247  )))
248 248  
249 249  (((
250 250  For parameter description, please refer to AT command set
260 +
261 +
251 251  )))
252 252  
253 253  [[image:1657330452568-615.png]]
254 254  
255 255  
267 +
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.
270 +
271 +
258 258  )))
259 259  
260 260  [[image:1657330472797-498.png]]
... ... @@ -264,9 +264,9 @@
264 264  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
265 265  
266 266  
267 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
268 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
269 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
281 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
282 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
283 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
270 270  
271 271  [[image:1657330501006-241.png]]
272 272  
... ... @@ -278,13 +278,13 @@
278 278  === 2.2.6 Use MQTT protocol to uplink data ===
279 279  
280 280  
281 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
282 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
283 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
284 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
285 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
286 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
287 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
295 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
296 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
297 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
298 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
299 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
300 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
301 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
288 288  
289 289  [[image:1657249978444-674.png]]
290 290  
... ... @@ -301,8 +301,8 @@
301 301  === 2.2.7 Use TCP protocol to uplink data ===
302 302  
303 303  
304 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
305 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
318 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
319 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
306 306  
307 307  [[image:image-20220709093918-1.png]]
308 308  
... ... @@ -313,25 +313,34 @@
313 313  
314 314  === 2.2.8 Change Update Interval ===
315 315  
330 +
316 316  User can use below command to change the (% style="color:green" %)**uplink interval**.
317 317  
318 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
319 319  
320 320  (((
336 +
337 +
338 +
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.
341 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
342 +
343 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
326 326  )))
327 327  
346 +(% 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  
349 +
330 330  == 2.3  Uplink Payload ==
331 331  
332 -In this mode, uplink payload includes in total 14 bytes
333 333  
353 +=== 2.3.1  Before Firmware v1.3.2 ===
334 334  
355 +
356 +In this mode, uplink payload includes in total 14 bytes
357 +
335 335  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
336 336  |=(% style="width: 60px;" %)(((
337 337  **Size(bytes)**
... ... @@ -339,49 +339,81 @@
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  (((
342 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
343 343  )))
344 344  
345 345  
346 346  [[image:1657331036973-987.png]]
347 347  
348 -(((
371 +
372 +
373 +The payload is **ASCII** string, representative same HEX:
374 +
375 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
376 +
377 +**where :**
378 +
379 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
380 +
381 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
382 +
383 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
384 +
385 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
386 +
387 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
388 +
389 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
390 +
391 +
392 +=== 2.3.2  Since firmware v1.3.2 ===
393 +
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 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
400 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
401 +|=(% 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.......
402 +
403 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
404 +
405 +[[image:image-20220908175246-1.png]]
406 +
407 +
349 349  The payload is ASCII string, representative same HEX:
350 -)))
351 351  
352 -(((
353 -0x72403155615900640c6c19029200 where:
354 -)))
410 +**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
355 355  
356 -* (((
357 -Device ID: 0x724031556159 = 724031556159
358 -)))
359 -* (((
360 -Version: 0x0064=100=1.0.0
361 -)))
412 +**where:**
362 362  
363 -* (((
364 -BAT: 0x0c6c = 3180 mV = 3.180V
365 -)))
366 -* (((
367 -Signal: 0x19 = 25
368 -)))
369 -* (((
370 -Distance: 0x0292= 658 mm
371 -)))
372 -* (((
373 -Interrupt: 0x00 = 0
414 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
374 374  
416 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
375 375  
418 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
376 376  
377 -
378 -)))
420 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
379 379  
422 +* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
423 +
424 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
425 +
426 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
427 +
428 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
429 +
430 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
431 +
432 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
433 +
380 380  == 2.4  Payload Explanation and Sensor Interface ==
381 381  
382 382  
383 383  === 2.4.1  Device ID ===
384 384  
439 +
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
446 +
447 +
391 391  )))
392 392  
393 393  (((
394 -**Example:**
451 +(% 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.
459 +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  
463 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
406 406  
465 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
466 +
467 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
468 +
469 +
470 +(% style="color:blue" %)**Example :**
471 +
472 +AT+DEUI=868411056754138
473 +
474 +
475 +
407 407  === 2.4.2  Version Info ===
408 408  
478 +
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  
491 +
421 421  (((
422 422  Ex1: 0x0B45 = 2885mV
423 423  )))
... ... @@ -430,6 +430,7 @@
430 430  
431 431  === 2.4.4  Signal Strength ===
432 432  
504 +
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  
537 +
465 465  Get the distance. Flat object range 280mm - 7500mm.
466 466  
540 +(((
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
542 +)))
468 468  
469 469  (((
470 470  (((
... ... @@ -482,6 +482,7 @@
482 482  
483 483  === 2.4.6  Digital Interrupt ===
484 484  
560 +
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  )))
... ... @@ -491,7 +491,7 @@
491 491  )))
492 492  
493 493  (((
494 -(% 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]])**.**
570 +(% 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]])**.**
495 495  )))
496 496  
497 497  
... ... @@ -516,6 +516,7 @@
516 516  
517 517  === 2.4.7  ​+5V Output ===
518 518  
595 +
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.
603 +
604 +
526 526  )))
527 527  
528 528  (((
529 529  (% style="color:blue" %)**AT+5VT=1000**
609 +
610 +
530 530  )))
531 531  
532 532  (((
... ... @@ -537,6 +537,7 @@
537 537  
538 538  == 2.5  Downlink Payload ==
539 539  
621 +
540 540  By default, NDDS75 prints the downlink payload to console port.
541 541  
542 542  [[image:image-20220709100028-1.png]]
... ... @@ -587,120 +587,96 @@
587 587  
588 588  
589 589  
590 -== 2.6  ​LED Indicator ==
672 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
591 591  
592 592  
593 -The NDDS75 has an internal LED which is to show the status of different state.
675 +(% style="color:blue" %)** ➢ AT Command:**
594 594  
677 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
595 595  
596 -* 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)
597 -* Then the LED will be on for 1 second means device is boot normally.
598 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
599 -* For each uplink probe, LED will be on for 500ms.
679 +² When min=0, and max≠0, Alarm higher than max
600 600  
601 -(((
602 -
603 -)))
681 +² When min≠0, and max=0, Alarm lower than min
604 604  
683 +² When min≠0 and max≠0, Alarm higher than max or lower than min
605 605  
606 606  
607 -== 2.7  ​Firmware Change Log ==
686 +(% style="color:blue" %)** Example:**
608 608  
688 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
609 609  
610 -Download URL & Firmware Change log
611 611  
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/]]
614 -)))
615 615  
692 +== 2.7  Set the number of data to be uploaded and the recording time ==
616 616  
617 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
618 618  
695 +(% style="color:blue" %)** ➢ AT Command:**
619 619  
697 +* (% 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)
698 +* (% 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.
620 620  
621 -== 2.8  ​Battery Analysis ==
700 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
622 622  
623 -=== 2.8.1  ​Battery Type ===
702 +[[image:image-20221009001114-1.png||height="687" width="955"]]
624 624  
625 625  
626 -(((
627 -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.
628 -)))
629 629  
630 -(((
631 -The battery is designed to last for several years depends on the actually use environment and update interval. 
632 -)))
706 +== 2.8  Read or Clear cached data ==
633 633  
634 -(((
635 -The battery related documents as below:
636 -)))
637 637  
638 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
639 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
709 +(% style="color:blue" %)** ➢ AT Command:**
641 641  
642 -(((
643 -[[image:image-20220709101450-2.png]]
644 -)))
711 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
712 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
645 645  
714 +[[image:image-20220908175333-2.png]]
646 646  
647 647  
648 -=== 2.8.2  Power consumption Analyze ===
649 649  
650 -(((
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 -)))
718 +== 2.9  ​LED Indicator ==
653 653  
654 654  
655 -(((
656 -Instruction to use as below:
657 -)))
721 +The NDDS75 has an internal LED which is to show the status of different state.
658 658  
659 -(((
660 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
661 -)))
662 662  
724 +* 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)
725 +* Then the LED will be on for 1 second means device is boot normally.
726 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
727 +* For each uplink probe, LED will be on for 500ms.
663 663  
664 664  (((
665 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
730 +
666 666  )))
667 667  
668 -* (((
669 -Product Model
670 -)))
671 -* (((
672 -Uplink Interval
673 -)))
674 -* (((
675 -Working Mode
676 -)))
677 677  
678 -(((
679 -And the Life expectation in difference case will be shown on the right.
680 -)))
681 681  
682 -[[image:image-20220709110451-3.png]]
735 +== 2.10  ​Firmware Change Log ==
683 683  
684 684  
738 +(((
739 +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]]
740 +)))
685 685  
686 -=== 2.8.3  ​Battery Note ===
742 +(((
743 +
744 +)))
687 687  
688 688  (((
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.
747 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
690 690  )))
691 691  
692 692  
693 693  
694 -=== 2.8.4  Replace the battery ===
752 +== 2.11 Battery & Power Consumption ==
695 695  
696 -(((
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 -)))
699 699  
755 +PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
700 700  
757 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
701 701  
702 702  = 3. ​ Access NB-IoT Module =
703 703  
761 +
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/]] 
768 +
769 +
710 710  )))
711 711  
712 712  [[image:1657333200519-600.png]]
... ... @@ -715,84 +715,103 @@
715 715  
716 716  = 4.  Using the AT Commands =
717 717  
778 +
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  
782 +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  
723 -AT+<CMD>?  : Help on <CMD>
724 724  
725 -AT+<CMD>         : Run <CMD>
785 +AT+<CMD>?  :  Help on <CMD>
726 726  
727 -AT+<CMD>=<value> : Set the value
787 +AT+<CMD>         :  Run <CMD>
728 728  
729 -AT+<CMD>=?  : Get the value
789 +AT+<CMD>=<value> :  Set the value
730 730  
791 +AT+<CMD>=?  :  Get the value
731 731  
793 +
732 732  (% style="color:#037691" %)**General Commands**(%%)      
733 733  
734 -AT  : Attention       
796 +AT  :  Attention       
735 735  
736 -AT?  : Short Help     
798 +AT?  :  Short Help     
737 737  
738 -ATZ  : MCU Reset    
800 +ATZ  :  MCU Reset    
739 739  
740 -AT+TDC  : Application Data Transmission Interval
802 +AT+TDC  :  Application Data Transmission Interval
741 741  
742 -AT+CFG  : Print all configurations
804 +AT+CFG  :  Print all configurations
743 743  
744 -AT+CFGMOD           : Working mode selection
806 +AT+CFGMOD           :  Working mode selection
745 745  
746 -AT+INTMOD            : Set the trigger interrupt mode
808 +AT+INTMOD            :  Set the trigger interrupt mode
747 747  
748 -AT+5VT  : Set extend the time of 5V power  
810 +AT+5VT  :  Set extend the time of 5V power  
749 749  
750 -AT+PRO  : Choose agreement
812 +AT+PRO  :  Choose agreement
751 751  
752 -AT+WEIGRE  : Get weight or set weight to 0
814 +AT+WEIGRE  :  Get weight or set weight to 0
753 753  
754 -AT+WEIGAP  : Get or Set the GapValue of weight
816 +AT+WEIGAP  :  Get or Set the GapValue of weight
755 755  
756 -AT+RXDL  : Extend the sending and receiving time
818 +AT+RXDL  :  Extend the sending and receiving time
757 757  
758 -AT+CNTFAC  : Get or set counting parameters
820 +AT+CNTFAC  :  Get or set counting parameters
759 759  
760 -AT+SERVADDR  : Server Address
822 +AT+SERVADDR  :  Server Address
761 761  
824 +AT+TR  :  Get or Set record time"
762 762  
826 +AT+APN     :  Get or set the APN
827 +
828 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
829 +
830 +AT+DNSCFG  : Get or Set DNS Server
831 +
832 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
833 +
834 +AT+NOUD  :  Get or Set the number of data to be uploaded
835 +
836 +AT+CDP     :  Read or Clear cached data
837 +
838 +AT+LDDSALARM :  Get or Set alarm of distance
839 +
840 +
763 763  (% style="color:#037691" %)**COAP Management**      
764 764  
765 -AT+URI            : Resource parameters
843 +AT+URI            :  Resource parameters
766 766  
767 767  
768 768  (% style="color:#037691" %)**UDP Management**
769 769  
770 -AT+CFM          : Upload confirmation mode (only valid for UDP)
848 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
771 771  
772 772  
773 773  (% style="color:#037691" %)**MQTT Management**
774 774  
775 -AT+CLIENT               : Get or Set MQTT client
853 +AT+CLIENT  :  Get or Set MQTT client
776 776  
777 -AT+UNAME  : Get or Set MQTT Username
855 +AT+UNAME  :  Get or Set MQTT Username
778 778  
779 -AT+PWD                  : Get or Set MQTT password
857 +AT+PWD  :  Get or Set MQTT password
780 780  
781 -AT+PUBTOPIC  : Get or Set MQTT publish topic
859 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
782 782  
783 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
861 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
784 784  
785 785  
786 786  (% style="color:#037691" %)**Information**          
787 787  
788 -AT+FDR  : Factory Data Reset
866 +AT+FDR  :  Factory Data Reset
789 789  
790 -AT+PWORD  : Serial Access Password
868 +AT+PWORD  :  Serial Access Password
791 791  
792 792  
793 793  
794 794  = ​5.  FAQ =
795 795  
874 +
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.
887 +(% 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  
894 +
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  
910 +
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
936 +* 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  
943 +
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  
961 +
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
image-20221009001114-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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