Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 104.7 >
edited by Xiaoling
on 2022/09/15 15:02
To version < 99.1 >
edited by Xiaoling
on 2022/07/11 14:10
>
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
... ... @@ -72,10 +72,8 @@
72 72  * 8500mAh Battery for long term use
73 73  
74 74  
75 -
76 76  == 1.3  Specification ==
77 77  
78 -
79 79  (% style="color:#037691" %)**Common DC Characteristics:**
80 80  
81 81  * Supply Voltage: 2.1v ~~ 3.6v
... ... @@ -104,10 +104,8 @@
104 104  * Max transmit power: 350mA@3.3v
105 105  
106 106  
107 -
108 108  == ​1.4  Applications ==
109 109  
110 -
111 111  * Smart Buildings & Home Automation
112 112  * Logistics and Supply Chain Management
113 113  * Smart Metering
... ... @@ -119,8 +119,6 @@
119 119  ​
120 120  
121 121  
122 -
123 -
124 124  == 1.5  Pin Definitions ==
125 125  
126 126  
... ... @@ -130,10 +130,8 @@
130 130  
131 131  = 2.  Use NDDS75 to communicate with IoT Server =
132 132  
133 -
134 134  == 2.1  How it works ==
135 135  
136 -
137 137  (((
138 138  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.
139 139  )))
... ... @@ -159,7 +159,6 @@
159 159  
160 160  === 2.2.1 Test Requirement ===
161 161  
162 -
163 163  (((
164 164  To use NDDS75 in your city, make sure meet below requirements:
165 165  )))
... ... @@ -169,7 +169,7 @@
169 169  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
170 170  
171 171  (((
172 -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.
161 +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
173 173  )))
174 174  
175 175  
... ... @@ -179,7 +179,6 @@
179 179  
180 180  === 2.2.2 Insert SIM card ===
181 181  
182 -
183 183  (((
184 184  Insert the NB-IoT Card get from your provider.
185 185  )))
... ... @@ -195,7 +195,6 @@
195 195  
196 196  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
197 197  
198 -
199 199  (((
200 200  (((
201 201  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.
... ... @@ -204,16 +204,15 @@
204 204  
205 205  [[image:image-20220709092052-2.png]]
206 206  
194 +**Connection:**
207 207  
208 -(% style="color:blue" %)**Connection:**
196 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
209 209  
210 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
198 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
211 211  
212 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
200 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
213 213  
214 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
215 215  
216 -
217 217  In the PC, use below serial tool settings:
218 218  
219 219  * Baud:  (% style="color:green" %)**9600**
... ... @@ -228,9 +228,8 @@
228 228  
229 229  [[image:1657329814315-101.png]]
230 230  
231 -
232 232  (((
233 -(% 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]]**
218 +(% 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/]]
234 234  )))
235 235  
236 236  
... ... @@ -237,10 +237,9 @@
237 237  
238 238  === 2.2.4 Use CoAP protocol to uplink data ===
239 239  
225 +(% 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/]]
240 240  
241 -(% 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/]]**
242 242  
243 -
244 244  (((
245 245  **Use below commands:**
246 246  )))
... ... @@ -249,29 +249,21 @@
249 249  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
250 250  )))
251 251  * (((
252 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
236 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
253 253  )))
254 254  * (((
255 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
256 -
257 -
258 -
239 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
259 259  )))
260 260  
261 261  (((
262 262  For parameter description, please refer to AT command set
263 -
264 -
265 265  )))
266 266  
267 267  [[image:1657330452568-615.png]]
268 268  
269 269  
270 -
271 271  (((
272 272  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.
273 -
274 -
275 275  )))
276 276  
277 277  [[image:1657330472797-498.png]]
... ... @@ -281,12 +281,10 @@
281 281  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
282 282  
283 283  
284 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
285 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
286 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
260 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
261 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
262 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
287 287  
288 -
289 -
290 290  [[image:1657330501006-241.png]]
291 291  
292 292  
... ... @@ -297,13 +297,13 @@
297 297  === 2.2.6 Use MQTT protocol to uplink data ===
298 298  
299 299  
300 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
301 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
302 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
303 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
304 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
305 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
306 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
274 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
275 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
276 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
277 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
278 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
279 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
280 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
307 307  
308 308  [[image:1657249978444-674.png]]
309 309  
... ... @@ -320,8 +320,8 @@
320 320  === 2.2.7 Use TCP protocol to uplink data ===
321 321  
322 322  
323 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
324 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
297 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
325 325  
326 326  [[image:image-20220709093918-1.png]]
327 327  
... ... @@ -332,34 +332,25 @@
332 332  
333 333  === 2.2.8 Change Update Interval ===
334 334  
335 -
336 336  User can use below command to change the (% style="color:green" %)**uplink interval**.
337 337  
338 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
311 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
339 339  
340 340  (((
341 -
342 -
343 -
344 344  (% style="color:red" %)**NOTE:**
315 +)))
345 345  
346 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
347 -
348 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
317 +(((
318 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
349 349  )))
350 350  
351 -(% 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).**
352 352  
353 353  
354 -
355 355  == 2.3  Uplink Payload ==
356 356  
357 -
358 -=== 2.3.1  Before Firmware v1.3.2 ===
359 -
360 -
361 361  In this mode, uplink payload includes in total 14 bytes
362 362  
327 +
363 363  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
364 364  |=(% style="width: 60px;" %)(((
365 365  **Size(bytes)**
... ... @@ -373,9 +373,8 @@
373 373  
374 374  [[image:1657331036973-987.png]]
375 375  
376 -
377 377  (((
378 -The payload is **ASCII** string, representative same HEX:
342 +The payload is ASCII string, representative same HEX:
379 379  )))
380 380  
381 381  (((
... ... @@ -386,11 +386,11 @@
386 386  Device ID: 0x724031556159 = 724031556159
387 387  )))
388 388  * (((
389 -Version:  0x0064=100=1.0.0
353 +Version: 0x0064=100=1.0.0
390 390  )))
391 391  
392 392  * (((
393 -BAT:  0x0c6c = 3180 mV = 3.180V
357 +BAT: 0x0c6c = 3180 mV = 3.180V
394 394  )))
395 395  * (((
396 396  Signal: 0x19 = 25
... ... @@ -403,49 +403,14 @@
403 403  
404 404  
405 405  
406 -
407 407  
408 408  )))
409 409  
410 -=== **2.3.2  Since firmware v1.3.2** ===
411 -
412 -
413 -In this mode, uplink payload includes 69 bytes in total by default.
414 -
415 -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.
416 -
417 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
418 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
419 -|(% 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.......
420 -
421 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
422 -
423 -[[image:image-20220908175246-1.png]]
424 -
425 -
426 -The payload is ASCII string, representative same HEX:
427 -
428 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
429 -
430 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
431 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
432 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
433 -* (% style="color:blue" %)Singal: 0x1e = 30
434 -* (% style="color:red" %)Mod: 0x01 = 1
435 -* Interrupt: 0x00= 0
436 -* Distance: 0x0039= 57 = 57
437 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
438 -* Distance,Time stamp : 00396319baf0
439 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
440 -
441 -
442 -
443 443  == 2.4  Payload Explanation and Sensor Interface ==
444 444  
445 445  
446 446  === 2.4.1  Device ID ===
447 447  
448 -
449 449  (((
450 450  By default, the Device ID equal to the last 6 bytes of IMEI.
451 451  )))
... ... @@ -452,12 +452,10 @@
452 452  
453 453  (((
454 454  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 -
456 -
457 457  )))
458 458  
459 459  (((
460 -(% style="color:blue" %)**Example :**
387 +**Example:**
461 461  )))
462 462  
463 463  (((
... ... @@ -465,26 +465,13 @@
465 465  )))
466 466  
467 467  (((
468 -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.
395 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
469 469  )))
470 470  
471 471  
472 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
473 473  
474 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
475 -
476 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
477 -
478 -
479 -(% style="color:blue" %)**Example :**
480 -
481 -AT+DEUI=868411056754138
482 -
483 -
484 -
485 485  === 2.4.2  Version Info ===
486 486  
487 -
488 488  (((
489 489  Specify the software version: 0x64=100, means firmware version 1.00.
490 490  )))
... ... @@ -497,7 +497,6 @@
497 497  
498 498  === 2.4.3  Battery Info ===
499 499  
500 -
501 501  (((
502 502  Ex1: 0x0B45 = 2885mV
503 503  )))
... ... @@ -510,7 +510,6 @@
510 510  
511 511  === 2.4.4  Signal Strength ===
512 512  
513 -
514 514  (((
515 515  NB-IoT Network signal Strength.
516 516  )))
... ... @@ -543,7 +543,6 @@
543 543  
544 544  === 2.4.5  Distance ===
545 545  
546 -
547 547  Get the distance. Flat object range 280mm - 7500mm.
548 548  
549 549  (((
... ... @@ -566,7 +566,6 @@
566 566  
567 567  === 2.4.6  Digital Interrupt ===
568 568  
569 -
570 570  (((
571 571  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.
572 572  )))
... ... @@ -576,7 +576,7 @@
576 576  )))
577 577  
578 578  (((
579 -(% 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]])**.**
489 +(% 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]])**.**
580 580  )))
581 581  
582 582  
... ... @@ -601,7 +601,6 @@
601 601  
602 602  === 2.4.7  ​+5V Output ===
603 603  
604 -
605 605  (((
606 606  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
607 607  )))
... ... @@ -609,14 +609,10 @@
609 609  
610 610  (((
611 611  The 5V output time can be controlled by AT Command.
612 -
613 -
614 614  )))
615 615  
616 616  (((
617 617  (% style="color:blue" %)**AT+5VT=1000**
618 -
619 -
620 620  )))
621 621  
622 622  (((
... ... @@ -627,7 +627,6 @@
627 627  
628 628  == 2.5  Downlink Payload ==
629 629  
630 -
631 631  By default, NDDS75 prints the downlink payload to console port.
632 632  
633 633  [[image:image-20220709100028-1.png]]
... ... @@ -678,52 +678,9 @@
678 678  
679 679  
680 680  
681 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
585 +== 2.6  ​LED Indicator ==
682 682  
683 683  
684 -(% style="color:blue" %)** ➢ AT Command:**
685 -
686 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
687 -
688 -² When min=0, and max≠0, Alarm higher than max
689 -
690 -² When min≠0, and max=0, Alarm lower than min
691 -
692 -² When min≠0 and max≠0, Alarm higher than max or lower than min
693 -
694 -
695 -(% style="color:blue" %)** Example:**
696 -
697 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
698 -
699 -
700 -
701 -== 2.7  Set the number of data to be uploaded and the recording time ==
702 -
703 -
704 -(% style="color:blue" %)** ➢ AT Command:**
705 -
706 -* (% 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)
707 -* (% 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.
708 -
709 -
710 -
711 -
712 -== 2.8  Read or Clear cached data ==
713 -
714 -
715 -(% style="color:blue" %)** ➢ AT Command:**
716 -
717 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
718 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
719 -
720 -[[image:image-20220908175333-2.png]]
721 -
722 -
723 -
724 -== 2.9  ​LED Indicator ==
725 -
726 -
727 727  The NDDS75 has an internal LED which is to show the status of different state.
728 728  
729 729  
... ... @@ -738,29 +738,29 @@
738 738  
739 739  
740 740  
741 -== 2.10  ​Firmware Change Log ==
602 +== 2.7  ​Firmware Change Log ==
742 742  
743 743  
744 744  (((
745 -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]]
606 +Download URL & Firmware Change log
746 746  )))
747 747  
748 748  (((
749 -
610 +[[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/]]
750 750  )))
751 751  
613 +
752 752  (((
753 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
615 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
754 754  )))
755 755  
756 756  
757 757  
758 -== 2.11  ​Battery Analysis ==
620 +== 2.8  ​Battery Analysis ==
759 759  
622 +=== 2.8.1  ​Battery Type ===
760 760  
761 -=== 2.11.1  ​Battery Type ===
762 762  
763 -
764 764  (((
765 765  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.
766 766  )))
... ... @@ -783,9 +783,8 @@
783 783  
784 784  
785 785  
786 -=== 2.11.2  Power consumption Analyze ===
647 +=== 2.8.2  Power consumption Analyze ===
787 787  
788 -
789 789  (((
790 790  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.
791 791  )))
... ... @@ -822,9 +822,8 @@
822 822  
823 823  
824 824  
825 -=== 2.11.3  ​Battery Note ===
685 +=== 2.8.3  ​Battery Note ===
826 826  
827 -
828 828  (((
829 829  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.
830 830  )))
... ... @@ -831,9 +831,8 @@
831 831  
832 832  
833 833  
834 -=== 2.11.4  Replace the battery ===
693 +=== 2.8.4  Replace the battery ===
835 835  
836 -
837 837  (((
838 838  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).
839 839  )))
... ... @@ -842,7 +842,6 @@
842 842  
843 843  = 3. ​ Access NB-IoT Module =
844 844  
845 -
846 846  (((
847 847  Users can directly access the AT command set of the NB-IoT module.
848 848  )))
... ... @@ -849,8 +849,6 @@
849 849  
850 850  (((
851 851  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/]] 
852 -
853 -
854 854  )))
855 855  
856 856  [[image:1657333200519-600.png]]
... ... @@ -859,103 +859,84 @@
859 859  
860 860  = 4.  Using the AT Commands =
861 861  
862 -
863 863  == 4.1  Access AT Commands ==
864 864  
719 +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/]]
865 865  
866 -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]]
867 867  
722 +AT+<CMD>?  : Help on <CMD>
868 868  
869 -AT+<CMD>?  :  Help on <CMD>
724 +AT+<CMD>         : Run <CMD>
870 870  
871 -AT+<CMD>         :  Run <CMD>
726 +AT+<CMD>=<value> : Set the value
872 872  
873 -AT+<CMD>=<value> :  Set the value
728 +AT+<CMD>=?  : Get the value
874 874  
875 -AT+<CMD>=?  :  Get the value
876 876  
877 -
878 878  (% style="color:#037691" %)**General Commands**(%%)      
879 879  
880 -AT  :  Attention       
733 +AT  : Attention       
881 881  
882 -AT?  :  Short Help     
735 +AT?  : Short Help     
883 883  
884 -ATZ  :  MCU Reset    
737 +ATZ  : MCU Reset    
885 885  
886 -AT+TDC  :  Application Data Transmission Interval
739 +AT+TDC  : Application Data Transmission Interval
887 887  
888 -AT+CFG  :  Print all configurations
741 +AT+CFG  : Print all configurations
889 889  
890 -AT+CFGMOD           :  Working mode selection
743 +AT+CFGMOD           : Working mode selection
891 891  
892 -AT+INTMOD            :  Set the trigger interrupt mode
745 +AT+INTMOD            : Set the trigger interrupt mode
893 893  
894 -AT+5VT  :  Set extend the time of 5V power  
747 +AT+5VT  : Set extend the time of 5V power  
895 895  
896 -AT+PRO  :  Choose agreement
749 +AT+PRO  : Choose agreement
897 897  
898 -AT+WEIGRE  :  Get weight or set weight to 0
751 +AT+WEIGRE  : Get weight or set weight to 0
899 899  
900 -AT+WEIGAP  :  Get or Set the GapValue of weight
753 +AT+WEIGAP  : Get or Set the GapValue of weight
901 901  
902 -AT+RXDL  :  Extend the sending and receiving time
755 +AT+RXDL  : Extend the sending and receiving time
903 903  
904 -AT+CNTFAC  :  Get or set counting parameters
757 +AT+CNTFAC  : Get or set counting parameters
905 905  
906 -AT+SERVADDR  :  Server Address
759 +AT+SERVADDR  : Server Address
907 907  
908 -AT+TR  :  Get or Set record time"
909 909  
910 -AT+APN     :  Get or set the APN
911 -
912 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
913 -
914 -AT+DNSCFG  : Get or Set DNS Server
915 -
916 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
917 -
918 -AT+NOUD  :  Get or Set the number of data to be uploaded
919 -
920 -AT+CDP     :  Read or Clear cached data
921 -
922 -AT+LDDSALARM :  Get or Set alarm of distance
923 -
924 -
925 925  (% style="color:#037691" %)**COAP Management**      
926 926  
927 -AT+URI            :  Resource parameters
764 +AT+URI            : Resource parameters
928 928  
929 929  
930 930  (% style="color:#037691" %)**UDP Management**
931 931  
932 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
769 +AT+CFM          : Upload confirmation mode (only valid for UDP)
933 933  
934 934  
935 935  (% style="color:#037691" %)**MQTT Management**
936 936  
937 -AT+CLIENT  :  Get or Set MQTT client
774 +AT+CLIENT               : Get or Set MQTT client
938 938  
939 -AT+UNAME  :  Get or Set MQTT Username
776 +AT+UNAME  : Get or Set MQTT Username
940 940  
941 -AT+PWD  :  Get or Set MQTT password
778 +AT+PWD                  : Get or Set MQTT password
942 942  
943 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
780 +AT+PUBTOPIC  : Get or Set MQTT publish topic
944 944  
945 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
782 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
946 946  
947 947  
948 948  (% style="color:#037691" %)**Information**          
949 949  
950 -AT+FDR  :  Factory Data Reset
787 +AT+FDR  : Factory Data Reset
951 951  
952 -AT+PWORD  :  Serial Access Password
789 +AT+PWORD  : Serial Access Password
953 953  
954 954  
955 955  
956 956  = ​5.  FAQ =
957 957  
958 -
959 959  == 5.1 ​ How to Upgrade Firmware ==
960 960  
961 961  
... ... @@ -968,7 +968,7 @@
968 968  )))
969 969  
970 970  (((
971 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
807 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
972 972  )))
973 973  
974 974  
... ... @@ -975,7 +975,6 @@
975 975  
976 976  = 6.  Trouble Shooting =
977 977  
978 -
979 979  == 6.1  ​Connection problem when uploading firmware ==
980 980  
981 981  
... ... @@ -991,7 +991,6 @@
991 991  
992 992  == 6.2  AT Command input doesn't work ==
993 993  
994 -
995 995  (((
996 996  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.
997 997  
... ... @@ -1024,7 +1024,6 @@
1024 1024  (((
1025 1025  
1026 1026  
1027 -
1028 1028  (% style="color:#037691" %)**Dimension and weight**:
1029 1029  
1030 1030  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -1042,6 +1042,5 @@
1042 1042  
1043 1043  = 9.  Support =
1044 1044  
1045 -
1046 1046  * 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.
1047 1047  * 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

Applications

Navigation

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