Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 104.4 >
edited by Xiaoling
on 2022/09/09 11:53
To version < 102.1 >
edited by David Huang
on 2022/09/08 17:53
>
Change comment: Uploaded new attachment "image-20220908175333-2.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.David
Content
... ... @@ -71,6 +71,9 @@
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
74 +
75 +
76 +
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -79,6 +79,8 @@
79 79  * Supply Voltage: 2.1v ~~ 3.6v
80 80  * Operating Temperature: -40 ~~ 85°C
81 81  
85 +
86 +
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 83  
84 84  * - B1 @H-FDD: 2100MHz
... ... @@ -88,6 +88,8 @@
88 88  * - B20 @H-FDD: 800MHz
89 89  * - B28 @H-FDD: 700MHz
90 90  
96 +
97 +
91 91  (% style="color:#037691" %)**Battery:**
92 92  
93 93  * Li/SOCI2 un-chargeable battery
... ... @@ -96,11 +96,16 @@
96 96  * Max continuously current: 130mA
97 97  * Max boost current: 2A, 1 second
98 98  
106 +
107 +
99 99  (% style="color:#037691" %)**Power Consumption**
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 102  * Max transmit power: 350mA@3.3v
103 103  
113 +
114 +
115 +
104 104  == ​1.4  Applications ==
105 105  
106 106  
... ... @@ -164,6 +164,8 @@
164 164  * The local NB-IoT network used the band that NDDS75 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
179 +
180 +
167 167  (((
168 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.
169 169  )))
... ... @@ -256,8 +256,6 @@
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]]
... ... @@ -266,8 +266,6 @@
266 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]]
... ... @@ -281,6 +281,8 @@
281 281  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
282 282  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
283 283  
294 +
295 +
284 284  [[image:1657330501006-241.png]]
285 285  
286 286  
... ... @@ -299,6 +299,8 @@
299 299  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
300 300  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
301 301  
314 +
315 +
302 302  [[image:1657249978444-674.png]]
303 303  
304 304  
... ... @@ -317,6 +317,8 @@
317 317  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
318 318  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
319 319  
334 +
335 +
320 320  [[image:image-20220709093918-1.png]]
321 321  
322 322  
... ... @@ -331,29 +331,20 @@
331 331  
332 332  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 333  
334 -(((
335 -
336 336  
337 337  
338 -(% style="color:red" %)**NOTE:**
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:**
352 +(((
353 +(% style="color:red" %)**NOTE: 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 351  
352 -=== 2.3.1  Before Firmware 1.3.2 ===
353 -
354 -
355 355  In this mode, uplink payload includes in total 14 bytes
356 356  
363 +
357 357  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
358 358  |=(% style="width: 60px;" %)(((
359 359  **Size(bytes)**
... ... @@ -369,7 +369,7 @@
369 369  
370 370  
371 371  (((
372 -The payload is **ASCII** string, representative same HEX:
379 +The payload is ASCII string, representative same HEX:
373 373  )))
374 374  
375 375  (((
... ... @@ -380,11 +380,11 @@
380 380  Device ID: 0x724031556159 = 724031556159
381 381  )))
382 382  * (((
383 -Version:  0x0064=100=1.0.0
390 +Version: 0x0064=100=1.0.0
384 384  )))
385 385  
386 386  * (((
387 -BAT:  0x0c6c = 3180 mV = 3.180V
394 +BAT: 0x0c6c = 3180 mV = 3.180V
388 388  )))
389 389  * (((
390 390  Signal: 0x19 = 25
... ... @@ -397,45 +397,9 @@
397 397  
398 398  
399 399  
400 -
401 401  
402 402  )))
403 403  
404 -=== **2.3.2  Since firmware v1.3.2** ===
405 -
406 -
407 -In this mode, uplink payload includes 69 bytes in total by default.
408 -
409 -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.
410 -
411 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
412 -|(% 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
413 -|(% 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.......
414 -
415 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
416 -
417 -[[image:image-20220908175246-1.png]]
418 -
419 -
420 -The payload is ASCII string, representative same HEX:
421 -
422 -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:
423 -
424 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
425 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
426 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
427 -* (% style="color:blue" %)Singal: 0x1e = 30
428 -* (% style="color:red" %)Mod: 0x01 = 1
429 -* Interrupt: 0x00= 0
430 -* Distance: 0x0039= 57 = 57
431 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 -* Distance,Time stamp : 00396319baf0
433 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
434 -
435 -
436 -
437 -
438 -
439 439  == 2.4  Payload Explanation and Sensor Interface ==
440 440  
441 441  
... ... @@ -453,7 +453,7 @@
453 453  )))
454 454  
455 455  (((
456 -(% style="color:blue" %)**Example :**
427 +**Example:**
457 457  )))
458 458  
459 459  (((
... ... @@ -461,23 +461,11 @@
461 461  )))
462 462  
463 463  (((
464 -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.
465 465  )))
466 466  
467 467  
468 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
469 469  
470 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
471 -
472 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
473 -
474 -
475 -(% style="color:blue" %)**Example :**
476 -
477 -AT+DEUI=868411056754138
478 -
479 -
480 -
481 481  === 2.4.2  Version Info ===
482 482  
483 483  
... ... @@ -674,55 +674,9 @@
674 674  
675 675  
676 676  
677 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
636 +== 2.6  ​LED Indicator ==
678 678  
679 679  
680 -(% style="color:blue" %)** ➢ AT Command:**
681 -
682 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
683 -
684 -² When min=0, and max≠0, Alarm higher than max
685 -
686 -² When min≠0, and max=0, Alarm lower than min
687 -
688 -² When min≠0 and max≠0, Alarm higher than max or lower than min
689 -
690 -
691 -(% style="color:blue" %)** Example:**
692 -
693 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
694 -
695 -
696 -
697 -== 2.7  Set the number of data to be uploaded and the recording time ==
698 -
699 -
700 -(% style="color:blue" %)** ➢ AT Command:**
701 -
702 -(% 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)
703 -
704 -(% 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.
705 -
706 -
707 -
708 -== 2.8  Read or Clear cached data ==
709 -
710 -
711 -(% style="color:blue" %)** ➢ AT Command:**
712 -
713 -(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
714 -
715 -
716 -[[image:image-20220908175333-2.png]]
717 -
718 -
719 -(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
720 -
721 -
722 -
723 -== 2.9  ​LED Indicator ==
724 -
725 -
726 726  The NDDS75 has an internal LED which is to show the status of different state.
727 727  
728 728  
... ... @@ -737,7 +737,7 @@
737 737  
738 738  
739 739  
740 -== 2.10  ​Firmware Change Log ==
653 +== 2.7  ​Firmware Change Log ==
741 741  
742 742  
743 743  (((
... ... @@ -754,10 +754,10 @@
754 754  
755 755  
756 756  
757 -== 2.11  ​Battery Analysis ==
670 +== 2.8  ​Battery Analysis ==
758 758  
759 759  
760 -=== 2.11.1  ​Battery Type ===
673 +=== 2.8.1  ​Battery Type ===
761 761  
762 762  
763 763  (((
... ... @@ -782,7 +782,7 @@
782 782  
783 783  
784 784  
785 -=== 2.11.2  Power consumption Analyze ===
698 +=== 2.8.2  Power consumption Analyze ===
786 786  
787 787  
788 788  (((
... ... @@ -821,7 +821,7 @@
821 821  
822 822  
823 823  
824 -=== 2.11.3  ​Battery Note ===
737 +=== 2.8.3  ​Battery Note ===
825 825  
826 826  
827 827  (((
... ... @@ -830,7 +830,7 @@
830 830  
831 831  
832 832  
833 -=== 2.11.4  Replace the battery ===
746 +=== 2.8.4  Replace the battery ===
834 834  
835 835  
836 836  (((
... ... @@ -904,23 +904,7 @@
904 904  
905 905  AT+SERVADDR  : Server Address
906 906  
907 -AT+TR      : Get or Set record time"
908 908  
909 -AT+APN     : Get or set the APN
910 -
911 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
912 -
913 -AT+DNSCFG  : Get or Set DNS Server
914 -
915 -AT+GETSENSORVALUE   : Returns the current sensor measurement
916 -
917 -AT+NOUD      : Get or Set the number of data to be uploaded
918 -
919 -AT+CDP     : Read or Clear cached data
920 -
921 -AT+LDDSALARM : Get or Set alarm of distance
922 -
923 -
924 924  (% style="color:#037691" %)**COAP Management**      
925 925  
926 926  AT+URI            : Resource parameters
... ... @@ -1044,3 +1044,5 @@
1044 1044  
1045 1045  * 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.
1046 1046  * 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 +

Applications

Navigation

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