Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.27
edited by Xiaoling
on 2024/01/19 17:55
Change comment: There is no comment for this version
To version 101.1
edited by David Huang
on 2022/09/08 17:52
Change comment: Uploaded new attachment "image-20220908175246-1.png", version {1}

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