Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.12 >
edited by Xiaoling
on 2023/04/04 13:41
To version < 111.1
edited by Bei Jinggeng
on 2024/05/31 09:53
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -1,5 +1,7 @@
1 +
2 +
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
4 +[[image:image-20220709085040-1.png||_mstalt="429481" height="542" width="524"]]
3 3  
4 4  
5 5  
... ... @@ -50,7 +50,7 @@
50 50  
51 51  )))
52 52  
53 -[[image:1657327959271-447.png]]
55 +[[image:1657327959271-447.png||_mstalt="297700"]]
54 54  
55 55  
56 56  == 1.2 ​ Features ==
... ... @@ -69,8 +69,6 @@
69 69  * Micro SIM card slot for NB-IoT SIM
70 70  * 8500mAh Battery for long term use
71 71  
72 -
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -99,10 +99,8 @@
99 99  (% style="color:#037691" %)**Power Consumption**
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
102 +* Max transmit power: 350mA@3.3v
103 103  
104 -
105 -
106 106  == ​1.4  Applications ==
107 107  
108 108  
... ... @@ -120,7 +120,7 @@
120 120  == 1.5  Pin Definitions ==
121 121  
122 122  
123 -[[image:1657328609906-564.png]]
121 +[[image:1657328609906-564.png||_mstalt="297440"]]
124 124  
125 125  
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
... ... @@ -141,7 +141,7 @@
141 141  
142 142  )))
143 143  
144 -[[image:1657328659945-416.png]]
142 +[[image:1657328659945-416.png||_mstalt="297999"]]
145 145  
146 146  (((
147 147  
... ... @@ -165,7 +165,7 @@
165 165  )))
166 166  
167 167  
168 -[[image:1657328756309-230.png]]
166 +[[image:1657328756309-230.png||_mstalt="294515"]]
169 169  
170 170  
171 171  === 2.2.2 Insert SIM card ===
... ... @@ -179,10 +179,9 @@
179 179  User need to take out the NB-IoT module and insert the SIM card like below:
180 180  )))
181 181  
180 +[[image:1657328884227-504.png||_mstalt="295776"]]
182 182  
183 -[[image:1657328884227-504.png]]
184 184  
185 -
186 186  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187 187  
188 188  
... ... @@ -192,7 +192,7 @@
192 192  )))
193 193  )))
194 194  
195 -[[image:image-20220709092052-2.png]]
192 +[[image:image-20220709092052-2.png||_mstalt="430235"]]
196 196  
197 197  
198 198  (% style="color:blue" %)**Connection:**
... ... @@ -216,7 +216,7 @@
216 216  Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
217 217  )))
218 218  
219 -[[image:1657329814315-101.png]]
216 +[[image:1657329814315-101.png||_mstalt="292084"]]
220 220  
221 221  
222 222  (((
... ... @@ -243,7 +243,6 @@
243 243  * (((
244 244  (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
245 245  
246 -
247 247  
248 248  )))
249 249  
... ... @@ -253,17 +253,14 @@
253 253  
254 254  )))
255 255  
256 -[[image:1657330452568-615.png]]
252 +[[image:1657330452568-615.png||_mstalt="295555"]]
257 257  
258 258  
259 -
260 260  (((
261 261  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.
262 -
263 -
264 264  )))
265 265  
266 -[[image:1657330472797-498.png]]
259 +[[image:1657330472797-498.png||_mstalt="299481"]]
267 267  
268 268  
269 269  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
... ... @@ -271,12 +271,11 @@
271 271  
272 272  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
273 273  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
274 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
275 275  
276 -[[image:1657330501006-241.png]]
268 +[[image:1657330501006-241.png||_mstalt="290121"]]
277 277  
278 278  
279 -[[image:1657330533775-472.png]]
271 +[[image:1657330533775-472.png||_mstalt="295763"]]
280 280  
281 281  
282 282  === 2.2.6 Use MQTT protocol to uplink data ===
... ... @@ -290,10 +290,10 @@
290 290  * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
291 291  * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
292 292  
293 -[[image:1657249978444-674.png]]
285 +[[image:1657249978444-674.png||_mstalt="299377"]]
294 294  
295 295  
296 -[[image:1657330723006-866.png]]
288 +[[image:1657330723006-866.png||_mstalt="294996"]]
297 297  
298 298  
299 299  (((
... ... @@ -307,10 +307,10 @@
307 307  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
308 308  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
309 309  
310 -[[image:image-20220709093918-1.png]]
302 +[[image:image-20220709093918-1.png||_mstalt="433706"]]
311 311  
312 312  
313 -[[image:image-20220709093918-2.png]]
305 +[[image:image-20220709093918-2.png||_mstalt="434070"]]
314 314  
315 315  
316 316  === 2.2.8 Change Update Interval ===
... ... @@ -323,7 +323,6 @@
323 323  (((
324 324  
325 325  
326 -
327 327  (% style="color:red" %)**NOTE:**
328 328  
329 329  (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
... ... @@ -341,11 +341,11 @@
341 341  
342 342  In this mode, uplink payload includes in total 14 bytes
343 343  
344 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
345 -|=(% style="width: 60px;" %)(((
335 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
336 +|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
346 346  **Size(bytes)**
347 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
348 -|(% 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"]]
338 +)))|=(% style="width: 61px;background-color:#4F81BD;color:white" %)**6**|=(% style="width: 37px;background-color:#4F81BD;color:white" %)2|=(% style="width: 37px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 82px;background-color:#4F81BD;color:white" %)**1**|=(% style="width: 102px;background-color:#4F81BD;color:white" %)**2**|=(% style="width: 60px;background-color:#4F81BD;color:white" %)**1**
339 +|(% 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"]]
349 349  
350 350  (((
351 351  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
... ... @@ -352,7 +352,7 @@
352 352  )))
353 353  
354 354  
355 -[[image:1657331036973-987.png]]
346 +[[image:1657331036973-987.png||_mstalt="298740"]]
356 356  
357 357  
358 358  The payload is **ASCII** string, representative same HEX:
... ... @@ -373,8 +373,6 @@
373 373  
374 374  * (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
375 375  
376 -
377 -
378 378  === 2.3.2  Since firmware v1.3.2 ===
379 379  
380 380  
... ... @@ -382,13 +382,13 @@
382 382  
383 383  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.
384 384  
385 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
386 -|=(% 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**
387 -|=(% 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.......
374 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
375 +|(% style="background-color:#4f81bd; color:white; width:60px" %)**Size(bytes)**|(% style="background-color:#4f81bd; color:white; width:40px" %)**8**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:25px" %)**2**|(% style="background-color:#4f81bd; color:white; width:60px" %)**1**|(% style="background-color:#4f81bd; color:white; width:25px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**1**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:70px" %)**4**|(% style="background-color:#4f81bd; color:white; width:40px" %)**2**|(% style="background-color:#4f81bd; color:white; width:65px" %)**4**
376 +|(% 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.......
388 388  
389 389  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
390 390  
391 -[[image:image-20220908175246-1.png]]
380 +[[image:image-20220908175246-1.png||_mstalt="432328"]]
392 392  
393 393  
394 394  The payload is ASCII string, representative same HEX:
... ... @@ -411,14 +411,12 @@
411 411  
412 412  * (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
413 413  
414 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
403 +* (% _mstmutation="1" style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/||_mstmutation="1"]])
415 415  
416 416  * (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
417 417  
418 418  * (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
419 419  
420 -
421 -
422 422  == 2.4  Payload Explanation and Sensor Interface ==
423 423  
424 424  === 2.4.1  Device ID ===
... ... @@ -521,16 +521,10 @@
521 521  Get the distance. Flat object range 280mm - 7500mm.
522 522  
523 523  (((
524 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
511 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
525 525  )))
526 526  
527 527  (((
528 -(((
529 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
530 -)))
531 -)))
532 -
533 -(((
534 534  
535 535  )))
536 536  
... ... @@ -554,9 +554,8 @@
554 554  The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
555 555  )))
556 556  
557 -
558 558  (((
559 -Example:
539 +**Example:**
560 560  )))
561 561  
562 562  (((
... ... @@ -575,17 +575,12 @@
575 575  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
576 576  )))
577 577  
578 -
579 579  (((
580 580  The 5V output time can be controlled by AT Command.
581 -
582 -
583 583  )))
584 584  
585 585  (((
586 586  (% style="color:blue" %)**AT+5VT=1000**
587 -
588 -
589 589  )))
590 590  
591 591  (((
... ... @@ -598,9 +598,12 @@
598 598  
599 599  By default, NDDS75 prints the downlink payload to console port.
600 600  
601 -[[image:image-20220709100028-1.png]]
576 +(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
577 +|(% style="background-color:#4f81bd; color:white; width:208px" %)**Downlink Control Type**|(% style="background-color:#4f81bd; color:white; width:56px" %)**FPort**|(% style="background-color:#4f81bd; color:white; width:100px" %)**Type Code**|(% style="background-color:#4f81bd; color:white; width:151px" %)**Downlink payload size(bytes)**
578 +|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
579 +|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
580 +|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
602 602  
603 -
604 604  (((
605 605  (% style="color:blue" %)**Examples:**
606 606  )))
... ... @@ -674,7 +674,7 @@
674 674  
675 675   The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
676 676  
677 -[[image:image-20221009001114-1.png||height="687" width="955"]]
655 +[[image:image-20221009001114-1.png||_mstalt="425269" height="687" width="955"]]
678 678  
679 679  
680 680  == 2.8  Read or Clear cached data ==
... ... @@ -685,7 +685,7 @@
685 685  * (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
686 686  * (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
687 687  
688 -[[image:image-20220908175333-2.png]]
666 +[[image:image-20220908175333-2.png||_mstalt="431665"]]
689 689  
690 690  
691 691  == 2.9  ​LED Indicator ==
... ... @@ -732,12 +732,12 @@
732 732  )))
733 733  
734 734  (((
735 -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/]] 
713 +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/||_mstmutation="1"]] 
736 736  
737 737  
738 738  )))
739 739  
740 -[[image:1657333200519-600.png]]
718 +[[image:1657333200519-600.png||_mstalt="291603"]]
741 741  
742 742  
743 743  = 4.  Using the AT Commands =
... ... @@ -809,11 +809,7 @@
809 809  AT+URI            :  Resource parameters
810 810  
811 811  
812 -(% style="color:#037691" %)**UDP Management**
813 813  
814 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
815 -
816 -
817 817  (% style="color:#037691" %)**MQTT Management**
818 818  
819 819  AT+CLIENT  :  Get or Set MQTT client
... ... @@ -874,6 +874,33 @@
874 874  )))
875 875  
876 876  
851 +== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
852 +
853 +
854 +This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
855 +
856 +
857 +== 6.4 Why does the DDS75 sensor keep flashing blue? ==
858 +
859 +This is caused by the incompatibility between the latest firmware and the hardware.
860 +
861 +Please check your hardware production date
862 +
863 +The first two digits are the week of the year, and the last two digits are the year.
864 +
865 +The number 3322 is the first batch we changed the power IC.
866 +
867 +As shown below:
868 +
869 + [[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDDS75%20-%20LoRaWAN%20Distance%20Detection%20Sensor%20User%20Manual/WebHome/image-20240531090837-1.png?rev=1.1||_mstalt="431418" alt="image-20240531090837-1.png"]]
870 +
871 +Have you updated the Lora ST's firmware? Please send downline 26 01 to check the version number.
872 +
873 +If it is v1.4.1 version, please modify a value according to the above four digits, the AT command is AT+POWERIC. The date after 3322 is AT+POWERIC=1, and the date before it is AT+POWERIC=0.
874 +
875 +Downlink is FF 01(AT+POWERIC=1);FF 00(AT+POWERIC=0).
876 +
877 +
877 877  = 7. ​ Order Info =
878 878  
879 879  
... ... @@ -912,4 +912,5 @@
912 912  
913 913  
914 914  * 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.
916 +
915 915  * 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]]

Applications

Navigation

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