Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.2 >
edited by Xiaoling
on 2022/10/15 09:58
To version < 97.18 >
edited by Xiaoling
on 2022/07/09 11:54
>
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  (((
... ... @@ -103,7 +103,6 @@
103 103  
104 104  == ​1.4  Applications ==
105 105  
106 -
107 107  * Smart Buildings & Home Automation
108 108  * Logistics and Supply Chain Management
109 109  * Smart Metering
... ... @@ -115,8 +115,6 @@
115 115  ​
116 116  
117 117  
118 -
119 -
120 120  == 1.5  Pin Definitions ==
121 121  
122 122  
... ... @@ -126,10 +126,8 @@
126 126  
127 127  = 2.  Use NDDS75 to communicate with IoT Server =
128 128  
129 -
130 130  == 2.1  How it works ==
131 131  
132 -
133 133  (((
134 134  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.
135 135  )))
... ... @@ -155,17 +155,16 @@
155 155  
156 156  === 2.2.1 Test Requirement ===
157 157  
158 -
159 159  (((
160 160  To use NDDS75 in your city, make sure meet below requirements:
161 161  )))
162 162  
163 163  * Your local operator has already distributed a NB-IoT Network there.
164 -* The local NB-IoT network used the band that NDDS75 supports.
157 +* The local NB-IoT network used the band that NSE01 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
167 167  (((
168 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
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
169 169  )))
170 170  
171 171  
... ... @@ -175,7 +175,6 @@
175 175  
176 176  === 2.2.2 Insert SIM card ===
177 177  
178 -
179 179  (((
180 180  Insert the NB-IoT Card get from your provider.
181 181  )))
... ... @@ -191,7 +191,6 @@
191 191  
192 192  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
193 193  
194 -
195 195  (((
196 196  (((
197 197  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.
... ... @@ -200,16 +200,15 @@
200 200  
201 201  [[image:image-20220709092052-2.png]]
202 202  
194 +**Connection:**
203 203  
204 -(% style="color:blue" %)**Connection:**
196 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
205 205  
206 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
198 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
207 207  
208 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
200 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
209 209  
210 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
211 211  
212 -
213 213  In the PC, use below serial tool settings:
214 214  
215 215  * Baud:  (% style="color:green" %)**9600**
... ... @@ -224,9 +224,8 @@
224 224  
225 225  [[image:1657329814315-101.png]]
226 226  
227 -
228 228  (((
229 -(% 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/]]
230 230  )))
231 231  
232 232  
... ... @@ -233,10 +233,9 @@
233 233  
234 234  === 2.2.4 Use CoAP protocol to uplink data ===
235 235  
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/]]
236 236  
237 -(% 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/]]**
238 238  
239 -
240 240  (((
241 241  **Use below commands:**
242 242  )))
... ... @@ -245,29 +245,21 @@
245 245  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
246 246  )))
247 247  * (((
248 -(% 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
249 249  )))
250 250  * (((
251 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
252 -
253 -
254 -
239 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
255 255  )))
256 256  
257 257  (((
258 258  For parameter description, please refer to AT command set
259 -
260 -
261 261  )))
262 262  
263 263  [[image:1657330452568-615.png]]
264 264  
265 265  
266 -
267 267  (((
268 268  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.
269 -
270 -
271 271  )))
272 272  
273 273  [[image:1657330472797-498.png]]
... ... @@ -277,9 +277,9 @@
277 277  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
278 278  
279 279  
280 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
281 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
282 -* (% 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
283 283  
284 284  [[image:1657330501006-241.png]]
285 285  
... ... @@ -291,13 +291,13 @@
291 291  === 2.2.6 Use MQTT protocol to uplink data ===
292 292  
293 293  
294 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
295 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
296 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
297 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
298 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
299 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
300 -* (% 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
301 301  
302 302  [[image:1657249978444-674.png]]
303 303  
... ... @@ -314,8 +314,8 @@
314 314  === 2.2.7 Use TCP protocol to uplink data ===
315 315  
316 316  
317 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
318 -* (% 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
319 319  
320 320  [[image:image-20220709093918-1.png]]
321 321  
... ... @@ -326,34 +326,25 @@
326 326  
327 327  === 2.2.8 Change Update Interval ===
328 328  
329 -
330 330  User can use below command to change the (% style="color:green" %)**uplink interval**.
331 331  
332 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
311 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 333  
334 334  (((
335 -
336 -
337 -
338 338  (% style="color:red" %)**NOTE:**
315 +)))
339 339  
340 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
341 -
342 -(% 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.
343 343  )))
344 344  
345 -(% 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).**
346 346  
347 347  
348 -
349 349  == 2.3  Uplink Payload ==
350 350  
351 -
352 -=== 2.3.1  Before Firmware v1.3.2 ===
353 -
354 -
355 355  In this mode, uplink payload includes in total 14 bytes
356 356  
327 +
357 357  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
358 358  |=(% style="width: 60px;" %)(((
359 359  **Size(bytes)**
... ... @@ -367,80 +367,43 @@
367 367  
368 368  [[image:1657331036973-987.png]]
369 369  
370 -
371 -
372 -The payload is **ASCII** string, representative same HEX:
373 -
374 -(% style="background-color:yellow" %)**0x724031556159 0064 0c6c 19 0292 00 **
375 -
376 -**where :**
377 -
378 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
379 -
380 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
381 -
382 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
383 -
384 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
385 -
386 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
387 -
388 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
389 -
390 -
391 -
392 -
393 -=== **2.3.2  Since firmware v1.3.2** ===
394 -
395 -
396 -In this mode, uplink payload includes 69 bytes in total by default.
397 -
398 -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.
399 -
400 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
401 -|(% 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
402 -|(% 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.......
403 -
404 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
405 -
406 -[[image:image-20220908175246-1.png]]
407 -
408 -
341 +(((
409 409  The payload is ASCII string, representative same HEX:
343 +)))
410 410  
411 -**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 (%%)**
345 +(((
346 +0x72403155615900640c6c19029200 where:
347 +)))
412 412  
413 -**where:**
349 +* (((
350 +Device ID: 0x724031556159 = 724031556159
351 +)))
352 +* (((
353 +Version: 0x0064=100=1.0.0
354 +)))
414 414  
415 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
356 +* (((
357 +BAT: 0x0c6c = 3180 mV = 3.180V
358 +)))
359 +* (((
360 +Signal: 0x19 = 25
361 +)))
362 +* (((
363 +Distance: 0x0292= 658 mm
364 +)))
365 +* (((
366 +Interrupt: 0x00 = 0
416 416  
417 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
418 418  
419 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
420 420  
421 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
370 +
371 +)))
422 422  
423 -* (% style="color:#037691" %)**Mod:**(%%)**  **0x01 = 1
424 -
425 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
426 -
427 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
428 -
429 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
430 -
431 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
432 -
433 -* (% style="color:#037691" %) **8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
434 -
435 -
436 -
437 -
438 438  == 2.4  Payload Explanation and Sensor Interface ==
439 439  
440 440  
441 441  === 2.4.1  Device ID ===
442 442  
443 -
444 444  (((
445 445  By default, the Device ID equal to the last 6 bytes of IMEI.
446 446  )))
... ... @@ -447,12 +447,10 @@
447 447  
448 448  (((
449 449  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
450 -
451 -
452 452  )))
453 453  
454 454  (((
455 -(% style="color:blue" %)**Example :**
387 +**Example:**
456 456  )))
457 457  
458 458  (((
... ... @@ -460,26 +460,13 @@
460 460  )))
461 461  
462 462  (((
463 -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.
464 464  )))
465 465  
466 466  
467 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
468 468  
469 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
470 -
471 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
472 -
473 -
474 -(% style="color:blue" %)**Example :**
475 -
476 -AT+DEUI=868411056754138
477 -
478 -
479 -
480 480  === 2.4.2  Version Info ===
481 481  
482 -
483 483  (((
484 484  Specify the software version: 0x64=100, means firmware version 1.00.
485 485  )))
... ... @@ -492,7 +492,6 @@
492 492  
493 493  === 2.4.3  Battery Info ===
494 494  
495 -
496 496  (((
497 497  Ex1: 0x0B45 = 2885mV
498 498  )))
... ... @@ -505,7 +505,6 @@
505 505  
506 506  === 2.4.4  Signal Strength ===
507 507  
508 -
509 509  (((
510 510  NB-IoT Network signal Strength.
511 511  )))
... ... @@ -538,7 +538,6 @@
538 538  
539 539  === 2.4.5  Distance ===
540 540  
541 -
542 542  Get the distance. Flat object range 280mm - 7500mm.
543 543  
544 544  (((
... ... @@ -561,7 +561,6 @@
561 561  
562 562  === 2.4.6  Digital Interrupt ===
563 563  
564 -
565 565  (((
566 566  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.
567 567  )))
... ... @@ -571,7 +571,7 @@
571 571  )))
572 572  
573 573  (((
574 -(% 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]])**.**
575 575  )))
576 576  
577 577  
... ... @@ -596,7 +596,6 @@
596 596  
597 597  === 2.4.7  ​+5V Output ===
598 598  
599 -
600 600  (((
601 601  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
602 602  )))
... ... @@ -604,14 +604,10 @@
604 604  
605 605  (((
606 606  The 5V output time can be controlled by AT Command.
607 -
608 -
609 609  )))
610 610  
611 611  (((
612 612  (% style="color:blue" %)**AT+5VT=1000**
613 -
614 -
615 615  )))
616 616  
617 617  (((
... ... @@ -622,7 +622,6 @@
622 622  
623 623  == 2.5  Downlink Payload ==
624 624  
625 -
626 626  By default, NDDS75 prints the downlink payload to console port.
627 627  
628 628  [[image:image-20220709100028-1.png]]
... ... @@ -673,55 +673,9 @@
673 673  
674 674  
675 675  
676 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
585 +== 2.6  ​LED Indicator ==
677 677  
678 678  
679 -(% style="color:blue" %)** ➢ AT Command:**
680 -
681 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
682 -
683 -² When min=0, and max≠0, Alarm higher than max
684 -
685 -² When min≠0, and max=0, Alarm lower than min
686 -
687 -² When min≠0 and max≠0, Alarm higher than max or lower than min
688 -
689 -
690 -(% style="color:blue" %)** Example:**
691 -
692 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
693 -
694 -
695 -
696 -== 2.7  Set the number of data to be uploaded and the recording time ==
697 -
698 -
699 -(% style="color:blue" %)** ➢ AT Command:**
700 -
701 -* (% 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)
702 -* (% 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.
703 -
704 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
705 -
706 -[[image:image-20221009001114-1.png||height="687" width="955"]]
707 -
708 -
709 -
710 -== 2.8  Read or Clear cached data ==
711 -
712 -
713 -(% style="color:blue" %)** ➢ AT Command:**
714 -
715 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
716 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
717 -
718 -[[image:image-20220908175333-2.png]]
719 -
720 -
721 -
722 -== 2.9  ​LED Indicator ==
723 -
724 -
725 725  The NDDS75 has an internal LED which is to show the status of different state.
726 726  
727 727  
... ... @@ -736,29 +736,29 @@
736 736  
737 737  
738 738  
739 -== 2.10  ​Firmware Change Log ==
602 +== 2.7  ​Firmware Change Log ==
740 740  
741 741  
742 742  (((
743 -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
744 744  )))
745 745  
746 746  (((
747 -
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/]]
748 748  )))
749 749  
613 +
750 750  (((
751 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
615 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
752 752  )))
753 753  
754 754  
755 755  
756 -== 2.11  ​Battery Analysis ==
620 +== 2.8  ​Battery Analysis ==
757 757  
622 +=== 2.8.1  ​Battery Type ===
758 758  
759 -=== 2.11.1  ​Battery Type ===
760 760  
761 -
762 762  (((
763 763  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.
764 764  )))
... ... @@ -781,9 +781,8 @@
781 781  
782 782  
783 783  
784 -=== 2.11.2  Power consumption Analyze ===
647 +=== 2.8.2  Power consumption Analyze ===
785 785  
786 -
787 787  (((
788 788  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.
789 789  )))
... ... @@ -820,9 +820,8 @@
820 820  
821 821  
822 822  
823 -=== 2.11.3  ​Battery Note ===
685 +=== 2.8.3  ​Battery Note ===
824 824  
825 -
826 826  (((
827 827  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.
828 828  )))
... ... @@ -829,9 +829,8 @@
829 829  
830 830  
831 831  
832 -=== 2.11.4  Replace the battery ===
693 +=== 2.8.4  Replace the battery ===
833 833  
834 -
835 835  (((
836 836  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).
837 837  )))
... ... @@ -840,7 +840,6 @@
840 840  
841 841  = 3. ​ Access NB-IoT Module =
842 842  
843 -
844 844  (((
845 845  Users can directly access the AT command set of the NB-IoT module.
846 846  )))
... ... @@ -847,8 +847,6 @@
847 847  
848 848  (((
849 849  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/]] 
850 -
851 -
852 852  )))
853 853  
854 854  [[image:1657333200519-600.png]]
... ... @@ -857,103 +857,84 @@
857 857  
858 858  = 4.  Using the AT Commands =
859 859  
860 -
861 861  == 4.1  Access AT Commands ==
862 862  
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/]]
863 863  
864 -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]]
865 865  
722 +AT+<CMD>?  : Help on <CMD>
866 866  
867 -AT+<CMD>?  :  Help on <CMD>
724 +AT+<CMD>         : Run <CMD>
868 868  
869 -AT+<CMD>         :  Run <CMD>
726 +AT+<CMD>=<value> : Set the value
870 870  
871 -AT+<CMD>=<value> :  Set the value
728 +AT+<CMD>=?  : Get the value
872 872  
873 -AT+<CMD>=?  :  Get the value
874 874  
875 -
876 876  (% style="color:#037691" %)**General Commands**(%%)      
877 877  
878 -AT  :  Attention       
733 +AT  : Attention       
879 879  
880 -AT?  :  Short Help     
735 +AT?  : Short Help     
881 881  
882 -ATZ  :  MCU Reset    
737 +ATZ  : MCU Reset    
883 883  
884 -AT+TDC  :  Application Data Transmission Interval
739 +AT+TDC  : Application Data Transmission Interval
885 885  
886 -AT+CFG  :  Print all configurations
741 +AT+CFG  : Print all configurations
887 887  
888 -AT+CFGMOD           :  Working mode selection
743 +AT+CFGMOD           : Working mode selection
889 889  
890 -AT+INTMOD            :  Set the trigger interrupt mode
745 +AT+INTMOD            : Set the trigger interrupt mode
891 891  
892 -AT+5VT  :  Set extend the time of 5V power  
747 +AT+5VT  : Set extend the time of 5V power  
893 893  
894 -AT+PRO  :  Choose agreement
749 +AT+PRO  : Choose agreement
895 895  
896 -AT+WEIGRE  :  Get weight or set weight to 0
751 +AT+WEIGRE  : Get weight or set weight to 0
897 897  
898 -AT+WEIGAP  :  Get or Set the GapValue of weight
753 +AT+WEIGAP  : Get or Set the GapValue of weight
899 899  
900 -AT+RXDL  :  Extend the sending and receiving time
755 +AT+RXDL  : Extend the sending and receiving time
901 901  
902 -AT+CNTFAC  :  Get or set counting parameters
757 +AT+CNTFAC  : Get or set counting parameters
903 903  
904 -AT+SERVADDR  :  Server Address
759 +AT+SERVADDR  : Server Address
905 905  
906 -AT+TR  :  Get or Set record time"
907 907  
908 -AT+APN     :  Get or set the APN
909 -
910 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
911 -
912 -AT+DNSCFG  : Get or Set DNS Server
913 -
914 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
915 -
916 -AT+NOUD  :  Get or Set the number of data to be uploaded
917 -
918 -AT+CDP     :  Read or Clear cached data
919 -
920 -AT+LDDSALARM :  Get or Set alarm of distance
921 -
922 -
923 923  (% style="color:#037691" %)**COAP Management**      
924 924  
925 -AT+URI            :  Resource parameters
764 +AT+URI            : Resource parameters
926 926  
927 927  
928 928  (% style="color:#037691" %)**UDP Management**
929 929  
930 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
769 +AT+CFM          : Upload confirmation mode (only valid for UDP)
931 931  
932 932  
933 933  (% style="color:#037691" %)**MQTT Management**
934 934  
935 -AT+CLIENT  :  Get or Set MQTT client
774 +AT+CLIENT               : Get or Set MQTT client
936 936  
937 -AT+UNAME  :  Get or Set MQTT Username
776 +AT+UNAME  : Get or Set MQTT Username
938 938  
939 -AT+PWD  :  Get or Set MQTT password
778 +AT+PWD                  : Get or Set MQTT password
940 940  
941 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
780 +AT+PUBTOPIC  : Get or Set MQTT publish topic
942 942  
943 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
782 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
944 944  
945 945  
946 946  (% style="color:#037691" %)**Information**          
947 947  
948 -AT+FDR  :  Factory Data Reset
787 +AT+FDR  : Factory Data Reset
949 949  
950 -AT+PWORD  :  Serial Access Password
789 +AT+PWORD  : Serial Access Password
951 951  
952 952  
953 953  
954 954  = ​5.  FAQ =
955 955  
956 -
957 957  == 5.1 ​ How to Upgrade Firmware ==
958 958  
959 959  
... ... @@ -966,7 +966,7 @@
966 966  )))
967 967  
968 968  (((
969 -(% 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.
970 970  )))
971 971  
972 972  
... ... @@ -973,7 +973,6 @@
973 973  
974 974  = 6.  Trouble Shooting =
975 975  
976 -
977 977  == 6.1  ​Connection problem when uploading firmware ==
978 978  
979 979  
... ... @@ -989,7 +989,6 @@
989 989  
990 990  == 6.2  AT Command input doesn't work ==
991 991  
992 -
993 993  (((
994 994  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.
995 995  
... ... @@ -1015,7 +1015,7 @@
1015 1015  
1016 1016  (% style="color:#037691" %)**Package Includes**:
1017 1017  
1018 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
854 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
1019 1019  * External antenna x 1
1020 1020  )))
1021 1021  
... ... @@ -1022,9 +1022,9 @@
1022 1022  (((
1023 1023  
1024 1024  
1025 -
1026 1026  (% style="color:#037691" %)**Dimension and weight**:
1027 1027  
863 +
1028 1028  * Device Size: 13.0 x 5 x 4.5 cm
1029 1029  * Device Weight: 150g
1030 1030  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -1040,6 +1040,5 @@
1040 1040  
1041 1041  = 9.  Support =
1042 1042  
1043 -
1044 1044  * 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.
1045 1045  * 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