Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.23 >
edited by Xiaoling
on 2024/01/19 17:49
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
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 -- NB-IoT Distance Detect Sensor User Manual
1 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Content
... ... @@ -16,6 +16,7 @@
16 16  
17 17  = 1.  Introduction =
18 18  
19 +
19 19  == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 21  (((
... ... @@ -53,6 +53,7 @@
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
57 +
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -69,6 +69,9 @@
69 69  * Micro SIM card slot for NB-IoT SIM
70 70  * 8500mAh Battery for long term use
71 71  
74 +
75 +
76 +
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -77,15 +77,19 @@
77 77  * Supply Voltage: 2.1v ~~ 3.6v
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
85 +
86 +
80 80  (% style="color:#037691" %)**NB-IoT Spec:**
81 81  
82 -* B1 @H-FDD: 2100MHz
83 -* B3 @H-FDD: 1800MHz
84 -* B8 @H-FDD: 900MHz
85 -* B5 @H-FDD: 850MHz
86 -* B20 @H-FDD: 800MHz
87 -* B28 @H-FDD: 700MHz
89 +* - B1 @H-FDD: 2100MHz
90 +* - B3 @H-FDD: 1800MHz
91 +* - B8 @H-FDD: 900MHz
92 +* - B5 @H-FDD: 850MHz
93 +* - B20 @H-FDD: 800MHz
94 +* - B28 @H-FDD: 700MHz
88 88  
96 +
97 +
89 89  (% style="color:#037691" %)**Battery:**
90 90  
91 91  * Li/SOCI2 un-chargeable battery
... ... @@ -94,11 +94,16 @@
94 94  * Max continuously current: 130mA
95 95  * Max boost current: 2A, 1 second
96 96  
106 +
107 +
97 97  (% style="color:#037691" %)**Power Consumption**
98 98  
99 99  * STOP Mode: 10uA @ 3.3v
100 100  * Max transmit power: 350mA@3.3v
101 101  
113 +
114 +
115 +
102 102  == ​1.4  Applications ==
103 103  
104 104  
... ... @@ -113,6 +113,8 @@
113 113  ​
114 114  
115 115  
130 +
131 +
116 116  == 1.5  Pin Definitions ==
117 117  
118 118  
... ... @@ -119,8 +119,10 @@
119 119  [[image:1657328609906-564.png]]
120 120  
121 121  
138 +
122 122  = 2.  Use NDDS75 to communicate with IoT Server =
123 123  
141 +
124 124  == 2.1  How it works ==
125 125  
126 126  
... ... @@ -143,8 +143,10 @@
143 143  
144 144  )))
145 145  
164 +
146 146  == 2.2 ​ Configure the NDDS75 ==
147 147  
167 +
148 148  === 2.2.1 Test Requirement ===
149 149  
150 150  
... ... @@ -156,6 +156,8 @@
156 156  * The local NB-IoT network used the band that NDDS75 supports.
157 157  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
158 158  
179 +
180 +
159 159  (((
160 160  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 161  )))
... ... @@ -164,6 +164,7 @@
164 164  [[image:1657328756309-230.png]]
165 165  
166 166  
189 +
167 167  === 2.2.2 Insert SIM card ===
168 168  
169 169  
... ... @@ -175,9 +175,11 @@
175 175  User need to take out the NB-IoT module and insert the SIM card like below:
176 176  )))
177 177  
201 +
178 178  [[image:1657328884227-504.png]]
179 179  
180 180  
205 +
181 181  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
182 182  
183 183  
... ... @@ -190,13 +190,13 @@
190 190  [[image:image-20220709092052-2.png]]
191 191  
192 192  
193 -(% style="color:blue" %)**Connection:**
218 +**Connection:**
194 194  
195 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
220 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
196 196  
197 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
222 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
198 198  
199 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
224 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
200 200  
201 201  
202 202  In the PC, use below serial tool settings:
... ... @@ -219,6 +219,7 @@
219 219  )))
220 220  
221 221  
247 +
222 222  === 2.2.4 Use CoAP protocol to uplink data ===
223 223  
224 224  
... ... @@ -233,23 +233,23 @@
233 233  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
234 234  )))
235 235  * (((
236 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
237 237  )))
238 238  * (((
239 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
240 240  
267 +
241 241  
242 242  )))
243 243  
244 244  (((
245 245  For parameter description, please refer to AT command set
246 -
247 -
248 248  )))
249 249  
250 250  [[image:1657330452568-615.png]]
251 251  
252 252  
278 +
253 253  (((
254 254  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.
255 255  )))
... ... @@ -257,13 +257,16 @@
257 257  [[image:1657330472797-498.png]]
258 258  
259 259  
286 +
260 260  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
261 261  
262 262  
263 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
264 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
265 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
290 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
291 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
292 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
266 266  
294 +
295 +
267 267  [[image:1657330501006-241.png]]
268 268  
269 269  
... ... @@ -270,17 +270,20 @@
270 270  [[image:1657330533775-472.png]]
271 271  
272 272  
302 +
273 273  === 2.2.6 Use MQTT protocol to uplink data ===
274 274  
275 275  
276 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
277 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
278 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
279 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
280 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
281 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
282 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
306 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
307 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
308 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
309 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
310 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
311 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
312 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
283 283  
314 +
315 +
284 284  [[image:1657249978444-674.png]]
285 285  
286 286  
... ... @@ -292,12 +292,15 @@
292 292  )))
293 293  
294 294  
327 +
295 295  === 2.2.7 Use TCP protocol to uplink data ===
296 296  
297 297  
298 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
299 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
331 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
300 300  
334 +
335 +
301 301  [[image:image-20220709093918-1.png]]
302 302  
303 303  
... ... @@ -304,41 +304,36 @@
304 304  [[image:image-20220709093918-2.png]]
305 305  
306 306  
342 +
307 307  === 2.2.8 Change Update Interval ===
308 308  
309 309  
310 310  User can use below command to change the (% style="color:green" %)**uplink interval**.
311 311  
312 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
348 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
313 313  
314 -(((
315 -
316 316  
317 -(% style="color:red" %)**NOTE:**
318 318  
319 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
320 -
321 -(% 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.**
322 322  )))
323 323  
324 -(% 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).**
325 325  
326 326  
327 327  == 2.3  Uplink Payload ==
328 328  
329 -=== 2.3.1  Before Firmware v1.3.2 ===
330 330  
331 -
332 332  In this mode, uplink payload includes in total 14 bytes
333 333  
334 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:440px" %)
335 -|=(% style="width: 61px;background-color:#4F81BD;color:white" %)(((
363 +
364 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
365 +|=(% style="width: 60px;" %)(((
336 336  **Size(bytes)**
337 -)))|=(% 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**
338 -|(% 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"]]
367 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
368 +|(% 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"]]
339 339  
340 340  (((
341 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
371 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
342 342  )))
343 343  
344 344  
... ... @@ -345,68 +345,41 @@
345 345  [[image:1657331036973-987.png]]
346 346  
347 347  
348 -The payload is **ASCII** string, representative same HEX:
349 -
350 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
351 -
352 -**where :**
353 -
354 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
355 -
356 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
357 -
358 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
359 -
360 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
361 -
362 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
363 -
364 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
365 -
366 -=== 2.3.2  Since firmware v1.3.2 ===
367 -
368 -
369 -In this mode, uplink payload includes 69 bytes in total by default.
370 -
371 -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.
372 -
373 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:490px" %)
374 -|(% 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:60px" %)**4**
375 -|(% 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.......
376 -
377 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
378 -
379 -[[image:image-20220908175246-1.png]]
380 -
381 -
378 +(((
382 382  The payload is ASCII string, representative same HEX:
380 +)))
383 383  
384 -**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 (%%)**
382 +(((
383 +0x72403155615900640c6c19029200 where:
384 +)))
385 385  
386 -**where:**
386 +* (((
387 +Device ID: 0x724031556159 = 724031556159
388 +)))
389 +* (((
390 +Version: 0x0064=100=1.0.0
391 +)))
387 387  
388 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
393 +* (((
394 +BAT: 0x0c6c = 3180 mV = 3.180V
395 +)))
396 +* (((
397 +Signal: 0x19 = 25
398 +)))
399 +* (((
400 +Distance: 0x0292= 658 mm
401 +)))
402 +* (((
403 +Interrupt: 0x00 = 0
389 389  
390 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
391 391  
392 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
393 393  
394 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
407 +
408 +)))
395 395  
396 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
397 -
398 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
399 -
400 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
401 -
402 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
403 -
404 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
405 -
406 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
407 -
408 408  == 2.4  Payload Explanation and Sensor Interface ==
409 409  
412 +
410 410  === 2.4.1  Device ID ===
411 411  
412 412  
... ... @@ -421,7 +421,7 @@
421 421  )))
422 422  
423 423  (((
424 -(% style="color:blue" %)**Example :**
427 +**Example:**
425 425  )))
426 426  
427 427  (((
... ... @@ -429,22 +429,11 @@
429 429  )))
430 430  
431 431  (((
432 -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.
433 433  )))
434 434  
435 435  
436 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
437 437  
438 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
439 -
440 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
441 -
442 -
443 -(% style="color:blue" %)**Example :**
444 -
445 -AT+DEUI=868411056754138
446 -
447 -
448 448  === 2.4.2  Version Info ===
449 449  
450 450  
... ... @@ -457,6 +457,7 @@
457 457  )))
458 458  
459 459  
452 +
460 460  === 2.4.3  Battery Info ===
461 461  
462 462  
... ... @@ -469,6 +469,7 @@
469 469  )))
470 470  
471 471  
465 +
472 472  === 2.4.4  Signal Strength ===
473 473  
474 474  
... ... @@ -501,6 +501,7 @@
501 501  )))
502 502  
503 503  
498 +
504 504  === 2.4.5  Distance ===
505 505  
506 506  
... ... @@ -507,13 +507,23 @@
507 507  Get the distance. Flat object range 280mm - 7500mm.
508 508  
509 509  (((
510 -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.**
505 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
511 511  )))
512 512  
513 513  (((
509 +(((
510 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
511 +)))
512 +)))
513 +
514 +(((
514 514  
515 515  )))
516 516  
518 +(((
519 +
520 +)))
521 +
517 517  === 2.4.6  Digital Interrupt ===
518 518  
519 519  
... ... @@ -526,7 +526,7 @@
526 526  )))
527 527  
528 528  (((
529 -(% 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]])**.**
534 +(% 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]])**.**
530 530  )))
531 531  
532 532  
... ... @@ -534,8 +534,9 @@
534 534  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.
535 535  )))
536 536  
542 +
537 537  (((
538 -**Example:**
544 +Example:
539 539  )))
540 540  
541 541  (((
... ... @@ -547,6 +547,7 @@
547 547  )))
548 548  
549 549  
556 +
550 550  === 2.4.7  ​+5V Output ===
551 551  
552 552  
... ... @@ -554,12 +554,17 @@
554 554  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
555 555  )))
556 556  
564 +
557 557  (((
558 558  The 5V output time can be controlled by AT Command.
567 +
568 +
559 559  )))
560 560  
561 561  (((
562 562  (% style="color:blue" %)**AT+5VT=1000**
573 +
574 +
563 563  )))
564 564  
565 565  (((
... ... @@ -567,17 +567,15 @@
567 567  )))
568 568  
569 569  
582 +
570 570  == 2.5  Downlink Payload ==
571 571  
572 572  
573 573  By default, NDDS75 prints the downlink payload to console port.
574 574  
575 -(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:520px" %)
576 -|(% 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:154px" %)**Downlink payload size(bytes)**
577 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
578 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
579 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
588 +[[image:image-20220709100028-1.png]]
580 580  
590 +
581 581  (((
582 582  (% style="color:blue" %)**Examples:**
583 583  )))
... ... @@ -622,85 +622,126 @@
622 622  )))
623 623  
624 624  
625 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
626 626  
636 +== 2.6  ​LED Indicator ==
627 627  
628 -(% style="color:blue" %)** ➢ AT Command:**
629 629  
630 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
639 +The NDDS75 has an internal LED which is to show the status of different state.
631 631  
632 -² When min=0, and max≠0, Alarm higher than max
633 633  
634 -² When min≠0, and max=0, Alarm lower than min
642 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
643 +* Then the LED will be on for 1 second means device is boot normally.
644 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
645 +* For each uplink probe, LED will be on for 500ms.
635 635  
636 -² When min≠0 and max≠0, Alarm higher than max or lower than min
647 +(((
648 +
649 +)))
637 637  
638 638  
639 -(% style="color:blue" %)** Example:**
640 640  
641 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
653 +== 2.7  ​Firmware Change Log ==
642 642  
643 643  
644 -== 2.7  Set the number of data to be uploaded and the recording time ==
656 +(((
657 +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]]
658 +)))
645 645  
660 +(((
661 +
662 +)))
646 646  
647 -(% style="color:blue" %)** ➢ AT Command:**
664 +(((
665 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
666 +)))
648 648  
649 -* (% 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)
650 -* (% 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.
651 651  
652 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
653 653  
654 -[[image:image-20221009001114-1.png||height="687" width="955"]]
670 +== 2.8  ​Battery Analysis ==
655 655  
656 656  
657 -== 2.8  Read or Clear cached data ==
673 +=== 2.8.1  ​Battery Type ===
658 658  
659 659  
660 -(% style="color:blue" %)** ➢ AT Command:**
676 +(((
677 +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.
678 +)))
661 661  
662 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
663 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
680 +(((
681 +The battery is designed to last for several years depends on the actually use environment and update interval. 
682 +)))
664 664  
665 -[[image:image-20220908175333-2.png]]
684 +(((
685 +The battery related documents as below:
686 +)))
666 666  
688 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
689 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
690 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
667 667  
668 -== 2.9  ​LED Indicator ==
692 +(((
693 +[[image:image-20220709101450-2.png]]
694 +)))
669 669  
670 670  
671 -The NDDS75 has an internal LED which is to show the status of different state.
672 672  
698 +=== 2.8.2  Power consumption Analyze ===
673 673  
674 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
675 -* Then the LED will be on for 1 second means device is boot normally.
676 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
677 -* For each uplink probe, LED will be on for 500ms.
678 678  
679 679  (((
680 -
702 +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.
681 681  )))
682 682  
683 683  
684 -== 2.10  ​Firmware Change Log ==
706 +(((
707 +Instruction to use as below:
708 +)))
685 685  
710 +(((
711 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
712 +)))
686 686  
714 +
687 687  (((
688 -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]]
716 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
689 689  )))
690 690  
719 +* (((
720 +Product Model
721 +)))
722 +* (((
723 +Uplink Interval
724 +)))
725 +* (((
726 +Working Mode
727 +)))
728 +
691 691  (((
692 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
730 +And the Life expectation in difference case will be shown on the right.
693 693  )))
694 694  
733 +[[image:image-20220709110451-3.png]]
695 695  
696 -== 2.11 Battery & Power Consumption ==
697 697  
698 698  
699 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
737 +=== 2.8.3  ​Battery Note ===
700 700  
701 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
702 702  
740 +(((
741 +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.
742 +)))
703 703  
744 +
745 +
746 +=== 2.8.4  Replace the battery ===
747 +
748 +
749 +(((
750 +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).
751 +)))
752 +
753 +
754 +
704 704  = 3. ​ Access NB-IoT Module =
705 705  
706 706  
... ... @@ -717,8 +717,10 @@
717 717  [[image:1657333200519-600.png]]
718 718  
719 719  
771 +
720 720  = 4.  Using the AT Commands =
721 721  
774 +
722 722  == 4.1  Access AT Commands ==
723 723  
724 724  
... ... @@ -725,94 +725,80 @@
725 725  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]]
726 726  
727 727  
728 -AT+<CMD>?  :  Help on <CMD>
781 +AT+<CMD>?  : Help on <CMD>
729 729  
730 -AT+<CMD>         :  Run <CMD>
783 +AT+<CMD>         : Run <CMD>
731 731  
732 -AT+<CMD>=<value> :  Set the value
785 +AT+<CMD>=<value> : Set the value
733 733  
734 -AT+<CMD>=?  :  Get the value
787 +AT+<CMD>=?  : Get the value
735 735  
736 736  
737 737  (% style="color:#037691" %)**General Commands**(%%)      
738 738  
739 -AT  :  Attention       
792 +AT  : Attention       
740 740  
741 -AT?  :  Short Help     
794 +AT?  : Short Help     
742 742  
743 -ATZ  :  MCU Reset    
796 +ATZ  : MCU Reset    
744 744  
745 -AT+TDC  :  Application Data Transmission Interval
798 +AT+TDC  : Application Data Transmission Interval
746 746  
747 -AT+CFG  :  Print all configurations
800 +AT+CFG  : Print all configurations
748 748  
749 -AT+CFGMOD           :  Working mode selection
802 +AT+CFGMOD           : Working mode selection
750 750  
751 -AT+INTMOD            :  Set the trigger interrupt mode
804 +AT+INTMOD            : Set the trigger interrupt mode
752 752  
753 -AT+5VT  :  Set extend the time of 5V power  
806 +AT+5VT  : Set extend the time of 5V power  
754 754  
755 -AT+PRO  :  Choose agreement
808 +AT+PRO  : Choose agreement
756 756  
757 -AT+WEIGRE  :  Get weight or set weight to 0
810 +AT+WEIGRE  : Get weight or set weight to 0
758 758  
759 -AT+WEIGAP  :  Get or Set the GapValue of weight
812 +AT+WEIGAP  : Get or Set the GapValue of weight
760 760  
761 -AT+RXDL  :  Extend the sending and receiving time
814 +AT+RXDL  : Extend the sending and receiving time
762 762  
763 -AT+CNTFAC  :  Get or set counting parameters
816 +AT+CNTFAC  : Get or set counting parameters
764 764  
765 -AT+SERVADDR  :  Server Address
818 +AT+SERVADDR  : Server Address
766 766  
767 -AT+TR  :  Get or Set record time"
768 768  
769 -AT+APN     :  Get or set the APN
770 -
771 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
772 -
773 -AT+DNSCFG  : Get or Set DNS Server
774 -
775 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
776 -
777 -AT+NOUD  :  Get or Set the number of data to be uploaded
778 -
779 -AT+CDP     :  Read or Clear cached data
780 -
781 -AT+LDDSALARM :  Get or Set alarm of distance
782 -
783 -
784 784  (% style="color:#037691" %)**COAP Management**      
785 785  
786 -AT+URI            :  Resource parameters
823 +AT+URI            : Resource parameters
787 787  
788 788  
789 789  (% style="color:#037691" %)**UDP Management**
790 790  
791 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
828 +AT+CFM          : Upload confirmation mode (only valid for UDP)
792 792  
793 793  
794 794  (% style="color:#037691" %)**MQTT Management**
795 795  
796 -AT+CLIENT  :  Get or Set MQTT client
833 +AT+CLIENT               : Get or Set MQTT client
797 797  
798 -AT+UNAME  :  Get or Set MQTT Username
835 +AT+UNAME  : Get or Set MQTT Username
799 799  
800 -AT+PWD  :  Get or Set MQTT password
837 +AT+PWD                  : Get or Set MQTT password
801 801  
802 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
839 +AT+PUBTOPIC  : Get or Set MQTT publish topic
803 803  
804 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
841 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
805 805  
806 806  
807 807  (% style="color:#037691" %)**Information**          
808 808  
809 -AT+FDR  :  Factory Data Reset
846 +AT+FDR  : Factory Data Reset
810 810  
811 -AT+PWORD  :  Serial Access Password
848 +AT+PWORD  : Serial Access Password
812 812  
813 813  
851 +
814 814  = ​5.  FAQ =
815 815  
854 +
816 816  == 5.1 ​ How to Upgrade Firmware ==
817 817  
818 818  
... ... @@ -829,8 +829,10 @@
829 829  )))
830 830  
831 831  
871 +
832 832  = 6.  Trouble Shooting =
833 833  
874 +
834 834  == 6.1  ​Connection problem when uploading firmware ==
835 835  
836 836  
... ... @@ -843,20 +843,17 @@
843 843  
844 844  )))
845 845  
887 +
846 846  == 6.2  AT Command input doesn't work ==
847 847  
848 848  
849 849  (((
850 850  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.
893 +
894 +
851 851  )))
852 852  
853 853  
854 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
855 -
856 -
857 -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]]//**.
858 -
859 -
860 860  = 7. ​ Order Info =
861 861  
862 862  
... ... @@ -863,6 +863,11 @@
863 863  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
864 864  
865 865  
904 +(% class="wikigeneratedid" %)
905 +(((
906 +
907 +)))
908 +
866 866  = 8.  Packing Info =
867 867  
868 868  (((
... ... @@ -877,6 +877,7 @@
877 877  (((
878 878  
879 879  
923 +
880 880  (% style="color:#037691" %)**Dimension and weight**:
881 881  
882 882  * Device Size: 13.0 x 5 x 4.5 cm
... ... @@ -888,6 +888,7 @@
888 888  (((
889 889  
890 890  
935 +
891 891  
892 892  )))
893 893  
... ... @@ -895,5 +895,6 @@
895 895  
896 896  
897 897  * 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.
898 -
899 899  * 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
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