Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.19 >
edited by Xiaoling
on 2022/07/09 13:53
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  (((
... ... @@ -56,6 +56,7 @@
56 56  
57 57  == 1.2 ​ Features ==
58 58  
60 +
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 60  * Ultra low power consumption
61 61  * Distance Detection by Ultrasonic technology
... ... @@ -70,7 +70,6 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -81,12 +81,12 @@
81 81  
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
84 -* - B1 @H-FDD: 2100MHz
85 -* - B3 @H-FDD: 1800MHz
86 -* - B8 @H-FDD: 900MHz
87 -* - B5 @H-FDD: 850MHz
88 -* - B20 @H-FDD: 800MHz
89 -* - 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
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -102,9 +102,9 @@
102 102  * Max transmit power: 350mA@3.3v
103 103  
104 104  
105 -
106 106  == ​1.4  Applications ==
107 107  
108 +
108 108  * Smart Buildings & Home Automation
109 109  * Logistics and Supply Chain Management
110 110  * Smart Metering
... ... @@ -116,6 +116,7 @@
116 116  ​
117 117  
118 118  
120 +
119 119  == 1.5  Pin Definitions ==
120 120  
121 121  
... ... @@ -125,8 +125,10 @@
125 125  
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
127 127  
130 +
128 128  == 2.1  How it works ==
129 129  
133 +
130 130  (((
131 131  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.
132 132  )))
... ... @@ -152,16 +152,17 @@
152 152  
153 153  === 2.2.1 Test Requirement ===
154 154  
159 +
155 155  (((
156 156  To use NDDS75 in your city, make sure meet below requirements:
157 157  )))
158 158  
159 159  * Your local operator has already distributed a NB-IoT Network there.
160 -* The local NB-IoT network used the band that NSE01 supports.
165 +* The local NB-IoT network used the band that NDDS75 supports.
161 161  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162 162  
163 163  (((
164 -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.
165 165  )))
166 166  
167 167  
... ... @@ -171,6 +171,7 @@
171 171  
172 172  === 2.2.2 Insert SIM card ===
173 173  
179 +
174 174  (((
175 175  Insert the NB-IoT Card get from your provider.
176 176  )))
... ... @@ -186,6 +186,7 @@
186 186  
187 187  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
188 188  
195 +
189 189  (((
190 190  (((
191 191  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.
... ... @@ -194,15 +194,16 @@
194 194  
195 195  [[image:image-20220709092052-2.png]]
196 196  
197 -**Connection:**
198 198  
199 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
205 +(% style="color:blue" %)**Connection:**
200 200  
201 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
207 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
202 202  
203 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
209 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
204 204  
211 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
205 205  
213 +
206 206  In the PC, use below serial tool settings:
207 207  
208 208  * Baud:  (% style="color:green" %)**9600**
... ... @@ -217,8 +217,9 @@
217 217  
218 218  [[image:1657329814315-101.png]]
219 219  
228 +
220 220  (((
221 -(% 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]]**
222 222  )))
223 223  
224 224  
... ... @@ -225,9 +225,10 @@
225 225  
226 226  === 2.2.4 Use CoAP protocol to uplink data ===
227 227  
228 -(% 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/]]
229 229  
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/]]**
230 230  
240 +
231 231  (((
232 232  **Use below commands:**
233 233  )))
... ... @@ -236,21 +236,29 @@
236 236  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
237 237  )))
238 238  * (((
239 -(% 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
240 240  )))
241 241  * (((
242 -(% 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 +
243 243  )))
244 244  
245 245  (((
246 246  For parameter description, please refer to AT command set
260 +
261 +
247 247  )))
248 248  
249 249  [[image:1657330452568-615.png]]
250 250  
251 251  
267 +
252 252  (((
253 253  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 +
254 254  )))
255 255  
256 256  [[image:1657330472797-498.png]]
... ... @@ -260,9 +260,9 @@
260 260  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
261 261  
262 262  
263 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
264 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
265 -* (% 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
266 266  
267 267  [[image:1657330501006-241.png]]
268 268  
... ... @@ -274,13 +274,13 @@
274 274  === 2.2.6 Use MQTT protocol to uplink data ===
275 275  
276 276  
277 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
278 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
279 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
280 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
281 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
282 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
283 -* (% 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
284 284  
285 285  [[image:1657249978444-674.png]]
286 286  
... ... @@ -297,8 +297,8 @@
297 297  === 2.2.7 Use TCP protocol to uplink data ===
298 298  
299 299  
300 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
301 -* (% 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
302 302  
303 303  [[image:image-20220709093918-1.png]]
304 304  
... ... @@ -309,25 +309,34 @@
309 309  
310 310  === 2.2.8 Change Update Interval ===
311 311  
330 +
312 312  User can use below command to change the (% style="color:green" %)**uplink interval**.
313 313  
314 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
315 315  
316 316  (((
336 +
337 +
338 +
317 317  (% style="color:red" %)**NOTE:**
318 -)))
319 319  
320 -(((
321 -(% 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:**
322 322  )))
323 323  
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).**
324 324  
325 325  
349 +
326 326  == 2.3  Uplink Payload ==
327 327  
328 -In this mode, uplink payload includes in total 14 bytes
329 329  
353 +=== 2.3.1  Before Firmware v1.3.2 ===
330 330  
355 +
356 +In this mode, uplink payload includes in total 14 bytes
357 +
331 331  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
332 332  |=(% style="width: 60px;" %)(((
333 333  **Size(bytes)**
... ... @@ -335,49 +335,81 @@
335 335  |(% 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"]]
336 336  
337 337  (((
338 -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.
339 339  )))
340 340  
341 341  
342 342  [[image:1657331036973-987.png]]
343 343  
344 -(((
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 +
345 345  The payload is ASCII string, representative same HEX:
346 -)))
347 347  
348 -(((
349 -0x72403155615900640c6c19029200 where:
350 -)))
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 (%%)**
351 351  
352 -* (((
353 -Device ID: 0x724031556159 = 724031556159
354 -)))
355 -* (((
356 -Version: 0x0064=100=1.0.0
357 -)))
412 +**where:**
358 358  
359 -* (((
360 -BAT: 0x0c6c = 3180 mV = 3.180V
361 -)))
362 -* (((
363 -Signal: 0x19 = 25
364 -)))
365 -* (((
366 -Distance: 0x0292= 658 mm
367 -)))
368 -* (((
369 -Interrupt: 0x00 = 0
414 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
370 370  
416 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
371 371  
418 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
372 372  
373 -
374 -)))
420 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
375 375  
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 +
376 376  == 2.4  Payload Explanation and Sensor Interface ==
377 377  
378 378  
379 379  === 2.4.1  Device ID ===
380 380  
439 +
381 381  (((
382 382  By default, the Device ID equal to the last 6 bytes of IMEI.
383 383  )))
... ... @@ -384,10 +384,12 @@
384 384  
385 385  (((
386 386  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
446 +
447 +
387 387  )))
388 388  
389 389  (((
390 -**Example:**
451 +(% style="color:blue" %)**Example :**
391 391  )))
392 392  
393 393  (((
... ... @@ -395,13 +395,26 @@
395 395  )))
396 396  
397 397  (((
398 -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.
399 399  )))
400 400  
401 401  
463 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
402 402  
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 +
403 403  === 2.4.2  Version Info ===
404 404  
478 +
405 405  (((
406 406  Specify the software version: 0x64=100, means firmware version 1.00.
407 407  )))
... ... @@ -414,6 +414,7 @@
414 414  
415 415  === 2.4.3  Battery Info ===
416 416  
491 +
417 417  (((
418 418  Ex1: 0x0B45 = 2885mV
419 419  )))
... ... @@ -426,6 +426,7 @@
426 426  
427 427  === 2.4.4  Signal Strength ===
428 428  
504 +
429 429  (((
430 430  NB-IoT Network signal Strength.
431 431  )))
... ... @@ -458,6 +458,7 @@
458 458  
459 459  === 2.4.5  Distance ===
460 460  
537 +
461 461  Get the distance. Flat object range 280mm - 7500mm.
462 462  
463 463  (((
... ... @@ -480,6 +480,7 @@
480 480  
481 481  === 2.4.6  Digital Interrupt ===
482 482  
560 +
483 483  (((
484 484  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.
485 485  )))
... ... @@ -489,7 +489,7 @@
489 489  )))
490 490  
491 491  (((
492 -(% 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]])**.**
493 493  )))
494 494  
495 495  
... ... @@ -514,6 +514,7 @@
514 514  
515 515  === 2.4.7  ​+5V Output ===
516 516  
595 +
517 517  (((
518 518  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
519 519  )))
... ... @@ -521,10 +521,14 @@
521 521  
522 522  (((
523 523  The 5V output time can be controlled by AT Command.
603 +
604 +
524 524  )))
525 525  
526 526  (((
527 527  (% style="color:blue" %)**AT+5VT=1000**
609 +
610 +
528 528  )))
529 529  
530 530  (((
... ... @@ -535,6 +535,7 @@
535 535  
536 536  == 2.5  Downlink Payload ==
537 537  
621 +
538 538  By default, NDDS75 prints the downlink payload to console port.
539 539  
540 540  [[image:image-20220709100028-1.png]]
... ... @@ -585,124 +585,96 @@
585 585  
586 586  
587 587  
588 -== 2.6  ​LED Indicator ==
672 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
589 589  
590 590  
591 -The NDDS75 has an internal LED which is to show the status of different state.
675 +(% style="color:blue" %)** ➢ AT Command:**
592 592  
677 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
593 593  
594 -* 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)
595 -* Then the LED will be on for 1 second means device is boot normally.
596 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
597 -* For each uplink probe, LED will be on for 500ms.
679 +² When min=0, and max≠0, Alarm higher than max
598 598  
599 -(((
600 -
601 -)))
681 +² When min≠0, and max=0, Alarm lower than min
602 602  
683 +² When min≠0 and max≠0, Alarm higher than max or lower than min
603 603  
604 604  
605 -== 2.7  ​Firmware Change Log ==
686 +(% style="color:blue" %)** Example:**
606 606  
688 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
607 607  
608 -(((
609 -Download URL & Firmware Change log
610 -)))
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 -(((
618 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
619 -)))
620 620  
695 +(% style="color:blue" %)** ➢ AT Command:**
621 621  
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.
622 622  
623 -== 2.8  ​Battery Analysis ==
700 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
624 624  
625 -=== 2.8.1  ​Battery Type ===
702 +[[image:image-20221009001114-1.png||height="687" width="955"]]
626 626  
627 627  
628 -(((
629 -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.
630 -)))
631 631  
632 -(((
633 -The battery is designed to last for several years depends on the actually use environment and update interval. 
634 -)))
706 +== 2.8  Read or Clear cached data ==
635 635  
636 -(((
637 -The battery related documents as below:
638 -)))
639 639  
640 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
641 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
642 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
709 +(% style="color:blue" %)** ➢ AT Command:**
643 643  
644 -(((
645 -[[image:image-20220709101450-2.png]]
646 -)))
711 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
712 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
647 647  
714 +[[image:image-20220908175333-2.png]]
648 648  
649 649  
650 -=== 2.8.2  Power consumption Analyze ===
651 651  
652 -(((
653 -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.
654 -)))
718 +== 2.9  ​LED Indicator ==
655 655  
656 656  
657 -(((
658 -Instruction to use as below:
659 -)))
721 +The NDDS75 has an internal LED which is to show the status of different state.
660 660  
661 -(((
662 -(% 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/]]
663 -)))
664 664  
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.
665 665  
666 666  (((
667 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
730 +
668 668  )))
669 669  
670 -* (((
671 -Product Model
672 -)))
673 -* (((
674 -Uplink Interval
675 -)))
676 -* (((
677 -Working Mode
678 -)))
679 679  
680 -(((
681 -And the Life expectation in difference case will be shown on the right.
682 -)))
683 683  
684 -[[image:image-20220709110451-3.png]]
735 +== 2.10  ​Firmware Change Log ==
685 685  
686 686  
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 +)))
687 687  
688 -=== 2.8.3  ​Battery Note ===
742 +(((
743 +
744 +)))
689 689  
690 690  (((
691 -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"]]
692 692  )))
693 693  
694 694  
695 695  
696 -=== 2.8.4  Replace the battery ===
752 +== 2.11 Battery & Power Consumption ==
697 697  
698 -(((
699 -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).
700 -)))
701 701  
755 +PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
702 702  
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/]] .
703 703  
704 704  = 3. ​ Access NB-IoT Module =
705 705  
761 +
706 706  (((
707 707  Users can directly access the AT command set of the NB-IoT module.
708 708  )))
... ... @@ -709,6 +709,8 @@
709 709  
710 710  (((
711 711  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 +
712 712  )))
713 713  
714 714  [[image:1657333200519-600.png]]
... ... @@ -717,84 +717,103 @@
717 717  
718 718  = 4.  Using the AT Commands =
719 719  
778 +
720 720  == 4.1  Access AT Commands ==
721 721  
722 -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/]]
723 723  
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]]
724 724  
725 -AT+<CMD>?  : Help on <CMD>
726 726  
727 -AT+<CMD>         : Run <CMD>
785 +AT+<CMD>?  :  Help on <CMD>
728 728  
729 -AT+<CMD>=<value> : Set the value
787 +AT+<CMD>         :  Run <CMD>
730 730  
731 -AT+<CMD>=?  : Get the value
789 +AT+<CMD>=<value> :  Set the value
732 732  
791 +AT+<CMD>=?  :  Get the value
733 733  
793 +
734 734  (% style="color:#037691" %)**General Commands**(%%)      
735 735  
736 -AT  : Attention       
796 +AT  :  Attention       
737 737  
738 -AT?  : Short Help     
798 +AT?  :  Short Help     
739 739  
740 -ATZ  : MCU Reset    
800 +ATZ  :  MCU Reset    
741 741  
742 -AT+TDC  : Application Data Transmission Interval
802 +AT+TDC  :  Application Data Transmission Interval
743 743  
744 -AT+CFG  : Print all configurations
804 +AT+CFG  :  Print all configurations
745 745  
746 -AT+CFGMOD           : Working mode selection
806 +AT+CFGMOD           :  Working mode selection
747 747  
748 -AT+INTMOD            : Set the trigger interrupt mode
808 +AT+INTMOD            :  Set the trigger interrupt mode
749 749  
750 -AT+5VT  : Set extend the time of 5V power  
810 +AT+5VT  :  Set extend the time of 5V power  
751 751  
752 -AT+PRO  : Choose agreement
812 +AT+PRO  :  Choose agreement
753 753  
754 -AT+WEIGRE  : Get weight or set weight to 0
814 +AT+WEIGRE  :  Get weight or set weight to 0
755 755  
756 -AT+WEIGAP  : Get or Set the GapValue of weight
816 +AT+WEIGAP  :  Get or Set the GapValue of weight
757 757  
758 -AT+RXDL  : Extend the sending and receiving time
818 +AT+RXDL  :  Extend the sending and receiving time
759 759  
760 -AT+CNTFAC  : Get or set counting parameters
820 +AT+CNTFAC  :  Get or set counting parameters
761 761  
762 -AT+SERVADDR  : Server Address
822 +AT+SERVADDR  :  Server Address
763 763  
824 +AT+TR  :  Get or Set record time"
764 764  
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 +
765 765  (% style="color:#037691" %)**COAP Management**      
766 766  
767 -AT+URI            : Resource parameters
843 +AT+URI            :  Resource parameters
768 768  
769 769  
770 770  (% style="color:#037691" %)**UDP Management**
771 771  
772 -AT+CFM          : Upload confirmation mode (only valid for UDP)
848 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
773 773  
774 774  
775 775  (% style="color:#037691" %)**MQTT Management**
776 776  
777 -AT+CLIENT               : Get or Set MQTT client
853 +AT+CLIENT  :  Get or Set MQTT client
778 778  
779 -AT+UNAME  : Get or Set MQTT Username
855 +AT+UNAME  :  Get or Set MQTT Username
780 780  
781 -AT+PWD                  : Get or Set MQTT password
857 +AT+PWD  :  Get or Set MQTT password
782 782  
783 -AT+PUBTOPIC  : Get or Set MQTT publish topic
859 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
784 784  
785 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
861 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
786 786  
787 787  
788 788  (% style="color:#037691" %)**Information**          
789 789  
790 -AT+FDR  : Factory Data Reset
866 +AT+FDR  :  Factory Data Reset
791 791  
792 -AT+PWORD  : Serial Access Password
868 +AT+PWORD  :  Serial Access Password
793 793  
794 794  
795 795  
796 796  = ​5.  FAQ =
797 797  
874 +
798 798  == 5.1 ​ How to Upgrade Firmware ==
799 799  
800 800  
... ... @@ -807,7 +807,7 @@
807 807  )))
808 808  
809 809  (((
810 -(% 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.**
811 811  )))
812 812  
813 813  
... ... @@ -814,6 +814,7 @@
814 814  
815 815  = 6.  Trouble Shooting =
816 816  
894 +
817 817  == 6.1  ​Connection problem when uploading firmware ==
818 818  
819 819  
... ... @@ -829,6 +829,7 @@
829 829  
830 830  == 6.2  AT Command input doesn't work ==
831 831  
910 +
832 832  (((
833 833  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.
834 834  
... ... @@ -854,7 +854,7 @@
854 854  
855 855  (% style="color:#037691" %)**Package Includes**:
856 856  
857 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
936 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
858 858  * External antenna x 1
859 859  )))
860 860  
... ... @@ -861,9 +861,9 @@
861 861  (((
862 862  
863 863  
943 +
864 864  (% style="color:#037691" %)**Dimension and weight**:
865 865  
866 -
867 867  * Device Size: 13.0 x 5 x 4.5 cm
868 868  * Device Weight: 150g
869 869  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -879,5 +879,6 @@
879 879  
880 880  = 9.  Support =
881 881  
961 +
882 882  * 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.
883 883  * 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