<
From version < 104.2 >
edited by Xiaoling
on 2022/09/09 10:26
To version < 100.6 >
edited by Xiaoling
on 2022/09/06 17:42
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -72,6 +72,8 @@
72 72  * 8500mAh Battery for long term use
73 73  
74 74  
75 +
76 +
75 75  == 1.3  Specification ==
76 76  
77 77  
... ... @@ -80,6 +80,8 @@
80 80  * Supply Voltage: 2.1v ~~ 3.6v
81 81  * Operating Temperature: -40 ~~ 85°C
82 82  
85 +
86 +
83 83  (% style="color:#037691" %)**NB-IoT Spec:**
84 84  
85 85  * - B1 @H-FDD: 2100MHz
... ... @@ -89,6 +89,8 @@
89 89  * - B20 @H-FDD: 800MHz
90 90  * - B28 @H-FDD: 700MHz
91 91  
96 +
97 +
92 92  (% style="color:#037691" %)**Battery:**
93 93  
94 94  * Li/SOCI2 un-chargeable battery
... ... @@ -97,6 +97,8 @@
97 97  * Max continuously current: 130mA
98 98  * Max boost current: 2A, 1 second
99 99  
106 +
107 +
100 100  (% style="color:#037691" %)**Power Consumption**
101 101  
102 102  * STOP Mode: 10uA @ 3.3v
... ... @@ -103,6 +103,8 @@
103 103  * Max transmit power: 350mA@3.3v
104 104  
105 105  
114 +
115 +
106 106  == ​1.4  Applications ==
107 107  
108 108  
... ... @@ -166,6 +166,8 @@
166 166  * The local NB-IoT network used the band that NDDS75 supports.
167 167  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
168 168  
179 +
180 +
169 169  (((
170 170  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.
171 171  )))
... ... @@ -258,8 +258,6 @@
258 258  
259 259  (((
260 260  For parameter description, please refer to AT command set
261 -
262 -
263 263  )))
264 264  
265 265  [[image:1657330452568-615.png]]
... ... @@ -268,8 +268,6 @@
268 268  
269 269  (((
270 270  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.
271 -
272 -
273 273  )))
274 274  
275 275  [[image:1657330472797-498.png]]
... ... @@ -283,6 +283,8 @@
283 283  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
284 284  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
285 285  
294 +
295 +
286 286  [[image:1657330501006-241.png]]
287 287  
288 288  
... ... @@ -301,6 +301,8 @@
301 301  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
302 302  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
303 303  
314 +
315 +
304 304  [[image:1657249978444-674.png]]
305 305  
306 306  
... ... @@ -319,6 +319,8 @@
319 319  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
320 320  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
321 321  
334 +
335 +
322 322  [[image:image-20220709093918-1.png]]
323 323  
324 324  
... ... @@ -333,26 +333,20 @@
333 333  
334 334  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
335 335  
336 -(((
337 -(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
338 338  
339 -
351 +
352 +(((
353 +(% style="color:red" %)**NOTE: By default, the device will send an uplink message every 1 hour.**
340 340  )))
341 341  
342 -(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
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 -
347 -
348 348  == 2.3  Uplink Payload ==
349 349  
350 350  
351 -=== 2.3.1  Before Firmware 1.3.2 ===
352 -
353 -
354 354  In this mode, uplink payload includes in total 14 bytes
355 355  
363 +
356 356  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
357 357  |=(% style="width: 60px;" %)(((
358 358  **Size(bytes)**
... ... @@ -368,7 +368,7 @@
368 368  
369 369  
370 370  (((
371 -The payload is **ASCII** string, representative same HEX:
379 +The payload is ASCII string, representative same HEX:
372 372  )))
373 373  
374 374  (((
... ... @@ -379,11 +379,11 @@
379 379  Device ID: 0x724031556159 = 724031556159
380 380  )))
381 381  * (((
382 -Version:  0x0064=100=1.0.0
390 +Version: 0x0064=100=1.0.0
383 383  )))
384 384  
385 385  * (((
386 -BAT:  0x0c6c = 3180 mV = 3.180V
394 +BAT: 0x0c6c = 3180 mV = 3.180V
387 387  )))
388 388  * (((
389 389  Signal: 0x19 = 25
... ... @@ -396,42 +396,9 @@
396 396  
397 397  
398 398  
399 -
400 400  
401 401  )))
402 402  
403 -=== **2.3.2  Since firmware v1.3.2** ===
404 -
405 -
406 -In this mode, uplink payload includes 69 bytes in total by default.
407 -
408 -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.
409 -
410 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
411 -|(% 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
412 -|(% 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.......
413 -
414 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
415 -
416 -[[image:image-20220908175246-1.png]]
417 -
418 -
419 -The payload is ASCII string, representative same HEX:
420 -
421 -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:
422 -
423 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
424 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
425 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
426 -* (% style="color:blue" %)Singal: 0x1e = 30
427 -* (% style="color:red" %)Mod: 0x01 = 1
428 -* Interrupt: 0x00= 0
429 -* Distance: 0x0039= 57 = 57
430 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
431 -* Distance,Time stamp : 00396319baf0
432 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
433 -
434 -
435 435  == 2.4  Payload Explanation and Sensor Interface ==
436 436  
437 437  
... ... @@ -449,7 +449,7 @@
449 449  )))
450 450  
451 451  (((
452 -(% style="color:blue" %)**Example :**
427 +**Example:**
453 453  )))
454 454  
455 455  (((
... ... @@ -457,23 +457,11 @@
457 457  )))
458 458  
459 459  (((
460 -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.
435 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
461 461  )))
462 462  
463 463  
464 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
465 465  
466 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
467 -
468 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
469 -
470 -
471 -(% style="color:blue" %)**Example :**
472 -
473 -AT+DEUI=868411056754138
474 -
475 -
476 -
477 477  === 2.4.2  Version Info ===
478 478  
479 479  
... ... @@ -670,55 +670,9 @@
670 670  
671 671  
672 672  
673 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
636 +== 2.6  ​LED Indicator ==
674 674  
675 675  
676 -(% style="color:blue" %)** ➢ AT Command:**
677 -
678 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
679 -
680 -² When min=0, and max≠0, Alarm higher than max
681 -
682 -² When min≠0, and max=0, Alarm lower than min
683 -
684 -² When min≠0 and max≠0, Alarm higher than max or lower than min
685 -
686 -
687 -(% style="color:blue" %)** Example:**
688 -
689 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
690 -
691 -
692 -
693 -== 2.7  Set the number of data to be uploaded and the recording time ==
694 -
695 -
696 -(% style="color:blue" %)** ➢ AT Command:**
697 -
698 -(% 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)
699 -
700 -(% 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.
701 -
702 -
703 -
704 -== 2.8  Read or Clear cached data ==
705 -
706 -
707 -(% style="color:blue" %)** ➢ AT Command:**
708 -
709 -(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
710 -
711 -
712 -[[image:image-20220908175333-2.png]]
713 -
714 -
715 -(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
716 -
717 -
718 -
719 -== 2.9  ​LED Indicator ==
720 -
721 -
722 722  The NDDS75 has an internal LED which is to show the status of different state.
723 723  
724 724  
... ... @@ -733,7 +733,7 @@
733 733  
734 734  
735 735  
736 -== 2.10  ​Firmware Change Log ==
653 +== 2.7  ​Firmware Change Log ==
737 737  
738 738  
739 739  (((
... ... @@ -750,10 +750,10 @@
750 750  
751 751  
752 752  
753 -== 2.11  ​Battery Analysis ==
670 +== 2.8  ​Battery Analysis ==
754 754  
755 755  
756 -=== 2.11.1  ​Battery Type ===
673 +=== 2.8.1  ​Battery Type ===
757 757  
758 758  
759 759  (((
... ... @@ -778,7 +778,7 @@
778 778  
779 779  
780 780  
781 -=== 2.11.2  Power consumption Analyze ===
698 +=== 2.8.2  Power consumption Analyze ===
782 782  
783 783  
784 784  (((
... ... @@ -817,7 +817,7 @@
817 817  
818 818  
819 819  
820 -=== 2.11.3  ​Battery Note ===
737 +=== 2.8.3  ​Battery Note ===
821 821  
822 822  
823 823  (((
... ... @@ -826,7 +826,7 @@
826 826  
827 827  
828 828  
829 -=== 2.11.4  Replace the battery ===
746 +=== 2.8.4  Replace the battery ===
830 830  
831 831  
832 832  (((
... ... @@ -900,23 +900,7 @@
900 900  
901 901  AT+SERVADDR  : Server Address
902 902  
903 -AT+TR      : Get or Set record time"
904 904  
905 -AT+APN     : Get or set the APN
906 -
907 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
908 -
909 -AT+DNSCFG  : Get or Set DNS Server
910 -
911 -AT+GETSENSORVALUE   : Returns the current sensor measurement
912 -
913 -AT+NOUD      : Get or Set the number of data to be uploaded
914 -
915 -AT+CDP     : Read or Clear cached data
916 -
917 -AT+LDDSALARM : Get or Set alarm of distance
918 -
919 -
920 920  (% style="color:#037691" %)**COAP Management**      
921 921  
922 922  AT+URI            : Resource parameters
... ... @@ -1040,3 +1040,5 @@
1040 1040  
1041 1041  * 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.
1042 1042  * 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]]
944 +
945 +
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
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0