Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.10 >
edited by Xiaoling
on 2023/04/04 12:01
To version < 100.1 >
edited by Xiaoling
on 2022/07/11 14:11
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,6 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 -
20 20  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 21  
22 22  (((
... ... @@ -57,7 +57,6 @@
57 57  
58 58  == 1.2 ​ Features ==
59 59  
60 -
61 61  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 62  * Ultra low power consumption
63 63  * Distance Detection by Ultrasonic technology
... ... @@ -71,9 +71,10 @@
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
74 -== 1.3  Specification ==
75 75  
76 76  
74 +== 1.3  Specification ==
75 +
77 77  (% style="color:#037691" %)**Common DC Characteristics:**
78 78  
79 79  * Supply Voltage: 2.1v ~~ 3.6v
... ... @@ -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
83 +* - B1 @H-FDD: 2100MHz
84 +* - B3 @H-FDD: 1800MHz
85 +* - B8 @H-FDD: 900MHz
86 +* - B5 @H-FDD: 850MHz
87 +* - B20 @H-FDD: 800MHz
88 +* - B28 @H-FDD: 700MHz
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -101,9 +101,10 @@
101 101  * STOP Mode: 10uA @ 3.3v
102 102  * Max transmit power: 350mA@3.3v
103 103  
104 -== ​1.4  Applications ==
105 105  
106 106  
105 +== ​1.4  Applications ==
106 +
107 107  * Smart Buildings & Home Automation
108 108  * Logistics and Supply Chain Management
109 109  * Smart Metering
... ... @@ -115,7 +115,6 @@
115 115  ​
116 116  
117 117  
118 -
119 119  == 1.5  Pin Definitions ==
120 120  
121 121  
... ... @@ -125,10 +125,8 @@
125 125  
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
127 127  
128 -
129 129  == 2.1  How it works ==
130 130  
131 -
132 132  (((
133 133  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.
134 134  )))
... ... @@ -154,7 +154,6 @@
154 154  
155 155  === 2.2.1 Test Requirement ===
156 156  
157 -
158 158  (((
159 159  To use NDDS75 in your city, make sure meet below requirements:
160 160  )))
... ... @@ -164,7 +164,7 @@
164 164  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
165 165  
166 166  (((
167 -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.
163 +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
168 168  )))
169 169  
170 170  
... ... @@ -174,7 +174,6 @@
174 174  
175 175  === 2.2.2 Insert SIM card ===
176 176  
177 -
178 178  (((
179 179  Insert the NB-IoT Card get from your provider.
180 180  )))
... ... @@ -190,7 +190,6 @@
190 190  
191 191  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
192 192  
193 -
194 194  (((
195 195  (((
196 196  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.
... ... @@ -199,16 +199,15 @@
199 199  
200 200  [[image:image-20220709092052-2.png]]
201 201  
196 +**Connection:**
202 202  
203 -(% style="color:blue" %)**Connection:**
198 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
204 204  
205 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
200 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
206 206  
207 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
202 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
208 208  
209 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
210 210  
211 -
212 212  In the PC, use below serial tool settings:
213 213  
214 214  * Baud:  (% style="color:green" %)**9600**
... ... @@ -223,9 +223,8 @@
223 223  
224 224  [[image:1657329814315-101.png]]
225 225  
226 -
227 227  (((
228 -(% 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]]**
220 +(% 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/]]
229 229  )))
230 230  
231 231  
... ... @@ -232,10 +232,9 @@
232 232  
233 233  === 2.2.4 Use CoAP protocol to uplink data ===
234 234  
227 +(% 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/]]
235 235  
236 -(% 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/]]**
237 237  
238 -
239 239  (((
240 240  **Use below commands:**
241 241  )))
... ... @@ -244,29 +244,21 @@
244 244  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
245 245  )))
246 246  * (((
247 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
238 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
248 248  )))
249 249  * (((
250 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
251 -
252 -
253 -
241 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
254 254  )))
255 255  
256 256  (((
257 257  For parameter description, please refer to AT command set
258 -
259 -
260 260  )))
261 261  
262 262  [[image:1657330452568-615.png]]
263 263  
264 264  
265 -
266 266  (((
267 267  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.
268 -
269 -
270 270  )))
271 271  
272 272  [[image:1657330472797-498.png]]
... ... @@ -276,9 +276,9 @@
276 276  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
277 277  
278 278  
279 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
280 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
281 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
262 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
263 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
264 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
282 282  
283 283  [[image:1657330501006-241.png]]
284 284  
... ... @@ -290,13 +290,13 @@
290 290  === 2.2.6 Use MQTT protocol to uplink data ===
291 291  
292 292  
293 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
294 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
295 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
296 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
297 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
298 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
299 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
276 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
277 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
278 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
279 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
280 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
281 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
282 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
300 300  
301 301  [[image:1657249978444-674.png]]
302 302  
... ... @@ -313,8 +313,8 @@
313 313  === 2.2.7 Use TCP protocol to uplink data ===
314 314  
315 315  
316 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
317 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
299 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
300 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
318 318  
319 319  [[image:image-20220709093918-1.png]]
320 320  
... ... @@ -325,34 +325,25 @@
325 325  
326 326  === 2.2.8 Change Update Interval ===
327 327  
328 -
329 329  User can use below command to change the (% style="color:green" %)**uplink interval**.
330 330  
331 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
313 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
332 332  
333 333  (((
334 -
335 -
336 -
337 337  (% style="color:red" %)**NOTE:**
317 +)))
338 338  
339 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
340 -
341 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
319 +(((
320 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
342 342  )))
343 343  
344 -(% 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).**
345 345  
346 346  
347 -
348 348  == 2.3  Uplink Payload ==
349 349  
350 -
351 -=== 2.3.1  Before Firmware v1.3.2 ===
352 -
353 -
354 354  In this mode, uplink payload includes in total 14 bytes
355 355  
329 +
356 356  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
357 357  |=(% style="width: 60px;" %)(((
358 358  **Size(bytes)**
... ... @@ -360,80 +360,49 @@
360 360  |(% 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"]]
361 361  
362 362  (((
363 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
337 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
364 364  )))
365 365  
366 366  
367 367  [[image:1657331036973-987.png]]
368 368  
369 -
370 -
371 -The payload is **ASCII** string, representative same HEX:
372 -
373 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
374 -
375 -**where :**
376 -
377 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
378 -
379 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
380 -
381 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
382 -
383 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
384 -
385 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
386 -
387 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
388 -
389 -=== 2.3.2  Since firmware v1.3.2 ===
390 -
391 -
392 -In this mode, uplink payload includes 69 bytes in total by default.
393 -
394 -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.
395 -
396 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
397 -|=(% 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**
398 -|=(% 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.......
399 -
400 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
401 -
402 -[[image:image-20220908175246-1.png]]
403 -
404 -
343 +(((
405 405  The payload is ASCII string, representative same HEX:
345 +)))
406 406  
407 -**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 (%%)**
347 +(((
348 +0x72403155615900640c6c19029200 where:
349 +)))
408 408  
409 -**where:**
351 +* (((
352 +Device ID: 0x724031556159 = 724031556159
353 +)))
354 +* (((
355 +Version: 0x0064=100=1.0.0
356 +)))
410 410  
411 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
358 +* (((
359 +BAT: 0x0c6c = 3180 mV = 3.180V
360 +)))
361 +* (((
362 +Signal: 0x19 = 25
363 +)))
364 +* (((
365 +Distance: 0x0292= 658 mm
366 +)))
367 +* (((
368 +Interrupt: 0x00 = 0
412 412  
413 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
414 414  
415 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
416 416  
417 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
372 +
373 +)))
418 418  
419 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
420 -
421 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
422 -
423 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
424 -
425 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
426 -
427 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
428 -
429 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
430 -
431 431  == 2.4  Payload Explanation and Sensor Interface ==
432 432  
433 433  
434 434  === 2.4.1  Device ID ===
435 435  
436 -
437 437  (((
438 438  By default, the Device ID equal to the last 6 bytes of IMEI.
439 439  )))
... ... @@ -440,12 +440,10 @@
440 440  
441 441  (((
442 442  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
443 -
444 -
445 445  )))
446 446  
447 447  (((
448 -(% style="color:blue" %)**Example :**
389 +**Example:**
449 449  )))
450 450  
451 451  (((
... ... @@ -453,26 +453,13 @@
453 453  )))
454 454  
455 455  (((
456 -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.
397 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
457 457  )))
458 458  
459 459  
460 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
461 461  
462 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
463 -
464 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
465 -
466 -
467 -(% style="color:blue" %)**Example :**
468 -
469 -AT+DEUI=868411056754138
470 -
471 -
472 -
473 473  === 2.4.2  Version Info ===
474 474  
475 -
476 476  (((
477 477  Specify the software version: 0x64=100, means firmware version 1.00.
478 478  )))
... ... @@ -485,7 +485,6 @@
485 485  
486 486  === 2.4.3  Battery Info ===
487 487  
488 -
489 489  (((
490 490  Ex1: 0x0B45 = 2885mV
491 491  )))
... ... @@ -498,7 +498,6 @@
498 498  
499 499  === 2.4.4  Signal Strength ===
500 500  
501 -
502 502  (((
503 503  NB-IoT Network signal Strength.
504 504  )))
... ... @@ -531,7 +531,6 @@
531 531  
532 532  === 2.4.5  Distance ===
533 533  
534 -
535 535  Get the distance. Flat object range 280mm - 7500mm.
536 536  
537 537  (((
... ... @@ -554,7 +554,6 @@
554 554  
555 555  === 2.4.6  Digital Interrupt ===
556 556  
557 -
558 558  (((
559 559  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.
560 560  )))
... ... @@ -564,7 +564,7 @@
564 564  )))
565 565  
566 566  (((
567 -(% 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]])**.**
491 +(% 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]])**.**
568 568  )))
569 569  
570 570  
... ... @@ -589,7 +589,6 @@
589 589  
590 590  === 2.4.7  ​+5V Output ===
591 591  
592 -
593 593  (((
594 594  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
595 595  )))
... ... @@ -597,14 +597,10 @@
597 597  
598 598  (((
599 599  The 5V output time can be controlled by AT Command.
600 -
601 -
602 602  )))
603 603  
604 604  (((
605 605  (% style="color:blue" %)**AT+5VT=1000**
606 -
607 -
608 608  )))
609 609  
610 610  (((
... ... @@ -615,7 +615,6 @@
615 615  
616 616  == 2.5  Downlink Payload ==
617 617  
618 -
619 619  By default, NDDS75 prints the downlink payload to console port.
620 620  
621 621  [[image:image-20220709100028-1.png]]
... ... @@ -666,96 +666,124 @@
666 666  
667 667  
668 668  
669 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
587 +== 2.6  ​LED Indicator ==
670 670  
671 671  
672 -(% style="color:blue" %)** ➢ AT Command:**
590 +The NDDS75 has an internal LED which is to show the status of different state.
673 673  
674 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
675 675  
676 -² When min=0, and max≠0, Alarm higher than max
593 +* 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)
594 +* Then the LED will be on for 1 second means device is boot normally.
595 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
596 +* For each uplink probe, LED will be on for 500ms.
677 677  
678 -² When min≠0, and max=0, Alarm lower than min
598 +(((
599 +
600 +)))
679 679  
680 -² When min≠0 and max≠0, Alarm higher than max or lower than min
681 681  
682 682  
683 -(% style="color:blue" %)** Example:**
604 +== 2.7  ​Firmware Change Log ==
684 684  
685 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
686 686  
607 +(((
608 +Download URL & Firmware Change log
609 +)))
687 687  
611 +(((
612 +[[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/]]
613 +)))
688 688  
689 -== 2.7  Set the number of data to be uploaded and the recording time ==
690 690  
616 +(((
617 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
618 +)))
691 691  
692 -(% style="color:blue" %)** ➢ AT Command:**
693 693  
694 -* (% 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)
695 -* (% 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.
696 696  
697 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
622 +== 2.8  ​Battery Analysis ==
698 698  
699 -[[image:image-20221009001114-1.png||height="687" width="955"]]
624 +=== 2.8.1  ​Battery Type ===
700 700  
701 701  
627 +(((
628 +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.
629 +)))
702 702  
703 -== 2.8  Read or Clear cached data ==
631 +(((
632 +The battery is designed to last for several years depends on the actually use environment and update interval. 
633 +)))
704 704  
635 +(((
636 +The battery related documents as below:
637 +)))
705 705  
706 -(% style="color:blue" %)** ➢ AT Command:**
639 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
641 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
707 707  
708 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
709 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
643 +(((
644 +[[image:image-20220709101450-2.png]]
645 +)))
710 710  
711 -[[image:image-20220908175333-2.png]]
712 712  
713 713  
649 +=== 2.8.2  Power consumption Analyze ===
714 714  
715 -== 2.9  ​LED Indicator ==
651 +(((
652 +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.
653 +)))
716 716  
717 717  
718 -The NDDS75 has an internal LED which is to show the status of different state.
656 +(((
657 +Instruction to use as below:
658 +)))
719 719  
660 +(((
661 +(% 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/]]
662 +)))
720 720  
721 -* 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)
722 -* Then the LED will be on for 1 second means device is boot normally.
723 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
724 -* For each uplink probe, LED will be on for 500ms.
725 725  
726 726  (((
727 -
666 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
728 728  )))
729 729  
669 +* (((
670 +Product Model
671 +)))
672 +* (((
673 +Uplink Interval
674 +)))
675 +* (((
676 +Working Mode
677 +)))
730 730  
679 +(((
680 +And the Life expectation in difference case will be shown on the right.
681 +)))
731 731  
732 -== 2.10  ​Firmware Change Log ==
683 +[[image:image-20220709110451-3.png]]
733 733  
734 734  
735 -(((
736 -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]]
737 -)))
738 738  
739 -(((
740 -
741 -)))
687 +=== 2.8.3  ​Battery Note ===
742 742  
743 743  (((
744 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
690 +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.
745 745  )))
746 746  
747 747  
748 748  
749 -== 2.11 Battery & Power Consumption ==
695 +=== 2.8.4  Replace the battery ===
750 750  
697 +(((
698 +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).
699 +)))
751 751  
752 -PS-LB-NA uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
753 753  
754 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
755 755  
756 756  = 3. ​ Access NB-IoT Module =
757 757  
758 -
759 759  (((
760 760  Users can directly access the AT command set of the NB-IoT module.
761 761  )))
... ... @@ -762,8 +762,6 @@
762 762  
763 763  (((
764 764  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/]] 
765 -
766 -
767 767  )))
768 768  
769 769  [[image:1657333200519-600.png]]
... ... @@ -772,103 +772,84 @@
772 772  
773 773  = 4.  Using the AT Commands =
774 774  
775 -
776 776  == 4.1  Access AT Commands ==
777 777  
721 +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/]]
778 778  
779 -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]]
780 780  
724 +AT+<CMD>?  : Help on <CMD>
781 781  
782 -AT+<CMD>?  :  Help on <CMD>
726 +AT+<CMD>         : Run <CMD>
783 783  
784 -AT+<CMD>         :  Run <CMD>
728 +AT+<CMD>=<value> : Set the value
785 785  
786 -AT+<CMD>=<value> :  Set the value
730 +AT+<CMD>=?  : Get the value
787 787  
788 -AT+<CMD>=?  :  Get the value
789 789  
790 -
791 791  (% style="color:#037691" %)**General Commands**(%%)      
792 792  
793 -AT  :  Attention       
735 +AT  : Attention       
794 794  
795 -AT?  :  Short Help     
737 +AT?  : Short Help     
796 796  
797 -ATZ  :  MCU Reset    
739 +ATZ  : MCU Reset    
798 798  
799 -AT+TDC  :  Application Data Transmission Interval
741 +AT+TDC  : Application Data Transmission Interval
800 800  
801 -AT+CFG  :  Print all configurations
743 +AT+CFG  : Print all configurations
802 802  
803 -AT+CFGMOD           :  Working mode selection
745 +AT+CFGMOD           : Working mode selection
804 804  
805 -AT+INTMOD            :  Set the trigger interrupt mode
747 +AT+INTMOD            : Set the trigger interrupt mode
806 806  
807 -AT+5VT  :  Set extend the time of 5V power  
749 +AT+5VT  : Set extend the time of 5V power  
808 808  
809 -AT+PRO  :  Choose agreement
751 +AT+PRO  : Choose agreement
810 810  
811 -AT+WEIGRE  :  Get weight or set weight to 0
753 +AT+WEIGRE  : Get weight or set weight to 0
812 812  
813 -AT+WEIGAP  :  Get or Set the GapValue of weight
755 +AT+WEIGAP  : Get or Set the GapValue of weight
814 814  
815 -AT+RXDL  :  Extend the sending and receiving time
757 +AT+RXDL  : Extend the sending and receiving time
816 816  
817 -AT+CNTFAC  :  Get or set counting parameters
759 +AT+CNTFAC  : Get or set counting parameters
818 818  
819 -AT+SERVADDR  :  Server Address
761 +AT+SERVADDR  : Server Address
820 820  
821 -AT+TR  :  Get or Set record time"
822 822  
823 -AT+APN     :  Get or set the APN
824 -
825 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
826 -
827 -AT+DNSCFG  : Get or Set DNS Server
828 -
829 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
830 -
831 -AT+NOUD  :  Get or Set the number of data to be uploaded
832 -
833 -AT+CDP     :  Read or Clear cached data
834 -
835 -AT+LDDSALARM :  Get or Set alarm of distance
836 -
837 -
838 838  (% style="color:#037691" %)**COAP Management**      
839 839  
840 -AT+URI            :  Resource parameters
766 +AT+URI            : Resource parameters
841 841  
842 842  
843 843  (% style="color:#037691" %)**UDP Management**
844 844  
845 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
771 +AT+CFM          : Upload confirmation mode (only valid for UDP)
846 846  
847 847  
848 848  (% style="color:#037691" %)**MQTT Management**
849 849  
850 -AT+CLIENT  :  Get or Set MQTT client
776 +AT+CLIENT               : Get or Set MQTT client
851 851  
852 -AT+UNAME  :  Get or Set MQTT Username
778 +AT+UNAME  : Get or Set MQTT Username
853 853  
854 -AT+PWD  :  Get or Set MQTT password
780 +AT+PWD                  : Get or Set MQTT password
855 855  
856 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
782 +AT+PUBTOPIC  : Get or Set MQTT publish topic
857 857  
858 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
784 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
859 859  
860 860  
861 861  (% style="color:#037691" %)**Information**          
862 862  
863 -AT+FDR  :  Factory Data Reset
789 +AT+FDR  : Factory Data Reset
864 864  
865 -AT+PWORD  :  Serial Access Password
791 +AT+PWORD  : Serial Access Password
866 866  
867 867  
868 868  
869 869  = ​5.  FAQ =
870 870  
871 -
872 872  == 5.1 ​ How to Upgrade Firmware ==
873 873  
874 874  
... ... @@ -881,7 +881,7 @@
881 881  )))
882 882  
883 883  (((
884 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
809 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
885 885  )))
886 886  
887 887  
... ... @@ -888,7 +888,6 @@
888 888  
889 889  = 6.  Trouble Shooting =
890 890  
891 -
892 892  == 6.1  ​Connection problem when uploading firmware ==
893 893  
894 894  
... ... @@ -904,7 +904,6 @@
904 904  
905 905  == 6.2  AT Command input doesn't work ==
906 906  
907 -
908 908  (((
909 909  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.
910 910  
... ... @@ -937,7 +937,6 @@
937 937  (((
938 938  
939 939  
940 -
941 941  (% style="color:#037691" %)**Dimension and weight**:
942 942  
943 943  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -955,6 +955,5 @@
955 955  
956 956  = 9.  Support =
957 957  
958 -
959 959  * 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.
960 960  * 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,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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