Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 97.17 >
edited by Xiaoling
on 2022/07/09 11:53
To version < 108.8 >
edited by Xiaoling
on 2022/11/04 15:36
>
Change comment: There is no comment for this version

Summary

Details

Page properties
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  (((
... ... @@ -70,6 +70,8 @@
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long term use
72 72  
74 +
75 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -80,12 +80,12 @@
80 80  
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 -* - B1 @H-FDD: 2100MHz
84 -* - B3 @H-FDD: 1800MHz
85 -* - B8 @H-FDD: 900MHz
86 -* - B5 @H-FDD: 850MHz
87 -* - B20 @H-FDD: 800MHz
88 -* - B28 @H-FDD: 700MHz
86 +* B1 @H-FDD: 2100MHz
87 +* B3 @H-FDD: 1800MHz
88 +* B8 @H-FDD: 900MHz
89 +* B5 @H-FDD: 850MHz
90 +* B20 @H-FDD: 800MHz
91 +* B28 @H-FDD: 700MHz
89 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
... ... @@ -100,8 +100,11 @@
100 100  * STOP Mode: 10uA @ 3.3v
101 101  * Max transmit power: 350mA@3.3v
102 102  
106 +
107 +
103 103  == ​1.4  Applications ==
104 104  
110 +
105 105  * Smart Buildings & Home Automation
106 106  * Logistics and Supply Chain Management
107 107  * Smart Metering
... ... @@ -113,6 +113,7 @@
113 113  ​
114 114  
115 115  
122 +
116 116  == 1.5  Pin Definitions ==
117 117  
118 118  
... ... @@ -122,8 +122,10 @@
122 122  
123 123  = 2.  Use NDDS75 to communicate with IoT Server =
124 124  
132 +
125 125  == 2.1  How it works ==
126 126  
135 +
127 127  (((
128 128  The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
129 129  )))
... ... @@ -149,16 +149,17 @@
149 149  
150 150  === 2.2.1 Test Requirement ===
151 151  
161 +
152 152  (((
153 153  To use NDDS75 in your city, make sure meet below requirements:
154 154  )))
155 155  
156 156  * Your local operator has already distributed a NB-IoT Network there.
157 -* The local NB-IoT network used the band that NSE01 supports.
167 +* The local NB-IoT network used the band that NDDS75 supports.
158 158  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
159 159  
160 160  (((
161 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
171 +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.
162 162  )))
163 163  
164 164  
... ... @@ -168,6 +168,7 @@
168 168  
169 169  === 2.2.2 Insert SIM card ===
170 170  
181 +
171 171  (((
172 172  Insert the NB-IoT Card get from your provider.
173 173  )))
... ... @@ -183,6 +183,7 @@
183 183  
184 184  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
185 185  
197 +
186 186  (((
187 187  (((
188 188  User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
... ... @@ -191,15 +191,16 @@
191 191  
192 192  [[image:image-20220709092052-2.png]]
193 193  
194 -**Connection:**
195 195  
196 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
207 +(% style="color:blue" %)**Connection:**
197 197  
198 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
209 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
199 199  
200 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
211 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
201 201  
213 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
202 202  
215 +
203 203  In the PC, use below serial tool settings:
204 204  
205 205  * Baud:  (% style="color:green" %)**9600**
... ... @@ -214,8 +214,9 @@
214 214  
215 215  [[image:1657329814315-101.png]]
216 216  
230 +
217 217  (((
218 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
232 +(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
219 219  )))
220 220  
221 221  
... ... @@ -222,9 +222,10 @@
222 222  
223 223  === 2.2.4 Use CoAP protocol to uplink data ===
224 224  
225 -(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
226 226  
240 +(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
227 227  
242 +
228 228  (((
229 229  **Use below commands:**
230 230  )))
... ... @@ -233,21 +233,29 @@
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
251 +(% 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
254 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
255 +
256 +
257 +
240 240  )))
241 241  
242 242  (((
243 243  For parameter description, please refer to AT command set
262 +
263 +
244 244  )))
245 245  
246 246  [[image:1657330452568-615.png]]
247 247  
248 248  
269 +
249 249  (((
250 250  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.
272 +
273 +
251 251  )))
252 252  
253 253  [[image:1657330472797-498.png]]
... ... @@ -257,9 +257,9 @@
257 257  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
258 258  
259 259  
260 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
261 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
262 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
283 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
284 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
285 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
263 263  
264 264  [[image:1657330501006-241.png]]
265 265  
... ... @@ -271,13 +271,13 @@
271 271  === 2.2.6 Use MQTT protocol to uplink data ===
272 272  
273 273  
274 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
275 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
276 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
277 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
278 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
279 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
280 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
297 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
299 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
300 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
301 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
302 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
303 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
281 281  
282 282  [[image:1657249978444-674.png]]
283 283  
... ... @@ -294,8 +294,8 @@
294 294  === 2.2.7 Use TCP protocol to uplink data ===
295 295  
296 296  
297 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
298 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
320 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
321 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
299 299  
300 300  [[image:image-20220709093918-1.png]]
301 301  
... ... @@ -306,25 +306,34 @@
306 306  
307 307  === 2.2.8 Change Update Interval ===
308 308  
332 +
309 309  User can use below command to change the (% style="color:green" %)**uplink interval**.
310 310  
311 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
335 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
312 312  
313 313  (((
338 +
339 +
340 +
314 314  (% style="color:red" %)**NOTE:**
315 -)))
316 316  
317 -(((
318 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
343 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
344 +
345 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
319 319  )))
320 320  
348 +(% 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).**
321 321  
322 322  
351 +
323 323  == 2.3  Uplink Payload ==
324 324  
325 -In this mode, uplink payload includes in total 14 bytes
326 326  
355 +=== 2.3.1  Before Firmware v1.3.2 ===
327 327  
357 +
358 +In this mode, uplink payload includes in total 14 bytes
359 +
328 328  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
329 329  |=(% style="width: 60px;" %)(((
330 330  **Size(bytes)**
... ... @@ -332,49 +332,83 @@
332 332  |(% 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"]]
333 333  
334 334  (((
335 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
367 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
336 336  )))
337 337  
338 338  
339 339  [[image:1657331036973-987.png]]
340 340  
341 -(((
373 +
374 +
375 +The payload is **ASCII** string, representative same HEX:
376 +
377 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
378 +
379 +**where :**
380 +
381 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
382 +
383 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
384 +
385 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
386 +
387 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
388 +
389 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
390 +
391 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
392 +
393 +
394 +
395 +=== 2.3.2  Since firmware v1.3.2 ===
396 +
397 +
398 +In this mode, uplink payload includes 69 bytes in total by default.
399 +
400 +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.
401 +
402 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
403 +|=(% 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**
404 +|=(% 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.......
405 +
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
407 +
408 +[[image:image-20220908175246-1.png]]
409 +
410 +
342 342  The payload is ASCII string, representative same HEX:
343 -)))
344 344  
345 -(((
346 -0x72403155615900640c6c19029200 where:
347 -)))
413 +**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 (%%)**
348 348  
349 -* (((
350 -Device ID: 0x724031556159 = 724031556159
351 -)))
352 -* (((
353 -Version: 0x0064=100=1.0.0
354 -)))
415 +**where:**
355 355  
356 -* (((
357 -BAT: 0x0c6c = 3180 mV = 3.180V
358 -)))
359 -* (((
360 -Signal: 0x19 = 25
361 -)))
362 -* (((
363 -Distance: 0x0292= 658 mm
364 -)))
365 -* (((
366 -Interrupt: 0x00 = 0
417 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
367 367  
419 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
368 368  
421 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
369 369  
370 -
371 -)))
423 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
372 372  
425 +* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
426 +
427 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
428 +
429 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
430 +
431 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 +
433 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
434 +
435 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
436 +
437 +
373 373  == 2.4  Payload Explanation and Sensor Interface ==
374 374  
375 375  
376 376  === 2.4.1  Device ID ===
377 377  
443 +
378 378  (((
379 379  By default, the Device ID equal to the last 6 bytes of IMEI.
380 380  )))
... ... @@ -381,10 +381,12 @@
381 381  
382 382  (((
383 383  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
450 +
451 +
384 384  )))
385 385  
386 386  (((
387 -**Example:**
455 +(% style="color:blue" %)**Example :**
388 388  )))
389 389  
390 390  (((
... ... @@ -392,13 +392,26 @@
392 392  )))
393 393  
394 394  (((
395 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
463 +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.
396 396  )))
397 397  
398 398  
467 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
399 399  
469 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
470 +
471 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
472 +
473 +
474 +(% style="color:blue" %)**Example :**
475 +
476 +AT+DEUI=868411056754138
477 +
478 +
479 +
400 400  === 2.4.2  Version Info ===
401 401  
482 +
402 402  (((
403 403  Specify the software version: 0x64=100, means firmware version 1.00.
404 404  )))
... ... @@ -411,6 +411,7 @@
411 411  
412 412  === 2.4.3  Battery Info ===
413 413  
495 +
414 414  (((
415 415  Ex1: 0x0B45 = 2885mV
416 416  )))
... ... @@ -423,6 +423,7 @@
423 423  
424 424  === 2.4.4  Signal Strength ===
425 425  
508 +
426 426  (((
427 427  NB-IoT Network signal Strength.
428 428  )))
... ... @@ -455,6 +455,7 @@
455 455  
456 456  === 2.4.5  Distance ===
457 457  
541 +
458 458  Get the distance. Flat object range 280mm - 7500mm.
459 459  
460 460  (((
... ... @@ -477,6 +477,7 @@
477 477  
478 478  === 2.4.6  Digital Interrupt ===
479 479  
564 +
480 480  (((
481 481  Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
482 482  )))
... ... @@ -486,7 +486,7 @@
486 486  )))
487 487  
488 488  (((
489 -(% 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]])**.**
574 +(% 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]])**.**
490 490  )))
491 491  
492 492  
... ... @@ -511,6 +511,7 @@
511 511  
512 512  === 2.4.7  ​+5V Output ===
513 513  
599 +
514 514  (((
515 515  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
516 516  )))
... ... @@ -518,10 +518,14 @@
518 518  
519 519  (((
520 520  The 5V output time can be controlled by AT Command.
607 +
608 +
521 521  )))
522 522  
523 523  (((
524 524  (% style="color:blue" %)**AT+5VT=1000**
613 +
614 +
525 525  )))
526 526  
527 527  (((
... ... @@ -532,6 +532,7 @@
532 532  
533 533  == 2.5  Downlink Payload ==
534 534  
625 +
535 535  By default, NDDS75 prints the downlink payload to console port.
536 536  
537 537  [[image:image-20220709100028-1.png]]
... ... @@ -582,9 +582,55 @@
582 582  
583 583  
584 584  
585 -== 2.6  ​LED Indicator ==
676 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
586 586  
587 587  
679 +(% style="color:blue" %)** ➢ AT Command:**
680 +
681 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
682 +
683 +² When min=0, and max≠0, Alarm higher than max
684 +
685 +² When min≠0, and max=0, Alarm lower than min
686 +
687 +² When min≠0 and max≠0, Alarm higher than max or lower than min
688 +
689 +
690 +(% style="color:blue" %)** Example:**
691 +
692 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
693 +
694 +
695 +
696 +== 2.7  Set the number of data to be uploaded and the recording time ==
697 +
698 +
699 +(% style="color:blue" %)** ➢ AT Command:**
700 +
701 +* (% 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)
702 +* (% 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.
703 +
704 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
705 +
706 +[[image:image-20221009001114-1.png||height="687" width="955"]]
707 +
708 +
709 +
710 +== 2.8  Read or Clear cached data ==
711 +
712 +
713 +(% style="color:blue" %)** ➢ AT Command:**
714 +
715 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
716 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
717 +
718 +[[image:image-20220908175333-2.png]]
719 +
720 +
721 +
722 +== 2.9  ​LED Indicator ==
723 +
724 +
588 588  The NDDS75 has an internal LED which is to show the status of different state.
589 589  
590 590  
... ... @@ -599,23 +599,27 @@
599 599  
600 600  
601 601  
602 -== 2.7  ​Firmware Change Log ==
739 +== 2.10  ​Firmware Change Log ==
603 603  
604 604  
605 -Download URL & Firmware Change log
742 +(((
743 +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]]
744 +)))
606 606  
607 607  (((
608 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
747 +
609 609  )))
610 610  
750 +(((
751 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
752 +)))
611 611  
612 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
613 613  
614 614  
756 +== 2.11  ​Battery Analysis ==
615 615  
616 -== 2.8  ​Battery Analysis ==
617 617  
618 -=== 2.8.1  ​Battery Type ===
759 +=== 2.11.1  ​Battery Type ===
619 619  
620 620  
621 621  (((
... ... @@ -640,8 +640,9 @@
640 640  
641 641  
642 642  
643 -=== 2.8.2  Power consumption Analyze ===
784 +=== 2.11.2  Power consumption Analyze ===
644 644  
786 +
645 645  (((
646 646  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.
647 647  )))
... ... @@ -678,8 +678,9 @@
678 678  
679 679  
680 680  
681 -=== 2.8.3  ​Battery Note ===
823 +=== 2.11.3  ​Battery Note ===
682 682  
825 +
683 683  (((
684 684  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.
685 685  )))
... ... @@ -686,8 +686,9 @@
686 686  
687 687  
688 688  
689 -=== 2.8.4  Replace the battery ===
832 +=== 2.11.4  Replace the battery ===
690 690  
834 +
691 691  (((
692 692  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).
693 693  )))
... ... @@ -696,6 +696,7 @@
696 696  
697 697  = 3. ​ Access NB-IoT Module =
698 698  
843 +
699 699  (((
700 700  Users can directly access the AT command set of the NB-IoT module.
701 701  )))
... ... @@ -702,6 +702,8 @@
702 702  
703 703  (((
704 704  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/]] 
850 +
851 +
705 705  )))
706 706  
707 707  [[image:1657333200519-600.png]]
... ... @@ -710,84 +710,103 @@
710 710  
711 711  = 4.  Using the AT Commands =
712 712  
860 +
713 713  == 4.1  Access AT Commands ==
714 714  
715 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
716 716  
864 +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]]
717 717  
718 -AT+<CMD>?  : Help on <CMD>
719 719  
720 -AT+<CMD>         : Run <CMD>
867 +AT+<CMD>?  :  Help on <CMD>
721 721  
722 -AT+<CMD>=<value> : Set the value
869 +AT+<CMD>         :  Run <CMD>
723 723  
724 -AT+<CMD>=?  : Get the value
871 +AT+<CMD>=<value> :  Set the value
725 725  
873 +AT+<CMD>=?  :  Get the value
726 726  
875 +
727 727  (% style="color:#037691" %)**General Commands**(%%)      
728 728  
729 -AT  : Attention       
878 +AT  :  Attention       
730 730  
731 -AT?  : Short Help     
880 +AT?  :  Short Help     
732 732  
733 -ATZ  : MCU Reset    
882 +ATZ  :  MCU Reset    
734 734  
735 -AT+TDC  : Application Data Transmission Interval
884 +AT+TDC  :  Application Data Transmission Interval
736 736  
737 -AT+CFG  : Print all configurations
886 +AT+CFG  :  Print all configurations
738 738  
739 -AT+CFGMOD           : Working mode selection
888 +AT+CFGMOD           :  Working mode selection
740 740  
741 -AT+INTMOD            : Set the trigger interrupt mode
890 +AT+INTMOD            :  Set the trigger interrupt mode
742 742  
743 -AT+5VT  : Set extend the time of 5V power  
892 +AT+5VT  :  Set extend the time of 5V power  
744 744  
745 -AT+PRO  : Choose agreement
894 +AT+PRO  :  Choose agreement
746 746  
747 -AT+WEIGRE  : Get weight or set weight to 0
896 +AT+WEIGRE  :  Get weight or set weight to 0
748 748  
749 -AT+WEIGAP  : Get or Set the GapValue of weight
898 +AT+WEIGAP  :  Get or Set the GapValue of weight
750 750  
751 -AT+RXDL  : Extend the sending and receiving time
900 +AT+RXDL  :  Extend the sending and receiving time
752 752  
753 -AT+CNTFAC  : Get or set counting parameters
902 +AT+CNTFAC  :  Get or set counting parameters
754 754  
755 -AT+SERVADDR  : Server Address
904 +AT+SERVADDR  :  Server Address
756 756  
906 +AT+TR  :  Get or Set record time"
757 757  
908 +AT+APN     :  Get or set the APN
909 +
910 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
911 +
912 +AT+DNSCFG  : Get or Set DNS Server
913 +
914 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
915 +
916 +AT+NOUD  :  Get or Set the number of data to be uploaded
917 +
918 +AT+CDP     :  Read or Clear cached data
919 +
920 +AT+LDDSALARM :  Get or Set alarm of distance
921 +
922 +
758 758  (% style="color:#037691" %)**COAP Management**      
759 759  
760 -AT+URI            : Resource parameters
925 +AT+URI            :  Resource parameters
761 761  
762 762  
763 763  (% style="color:#037691" %)**UDP Management**
764 764  
765 -AT+CFM          : Upload confirmation mode (only valid for UDP)
930 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
766 766  
767 767  
768 768  (% style="color:#037691" %)**MQTT Management**
769 769  
770 -AT+CLIENT               : Get or Set MQTT client
935 +AT+CLIENT  :  Get or Set MQTT client
771 771  
772 -AT+UNAME  : Get or Set MQTT Username
937 +AT+UNAME  :  Get or Set MQTT Username
773 773  
774 -AT+PWD                  : Get or Set MQTT password
939 +AT+PWD  :  Get or Set MQTT password
775 775  
776 -AT+PUBTOPIC  : Get or Set MQTT publish topic
941 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
777 777  
778 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
943 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
779 779  
780 780  
781 781  (% style="color:#037691" %)**Information**          
782 782  
783 -AT+FDR  : Factory Data Reset
948 +AT+FDR  :  Factory Data Reset
784 784  
785 -AT+PWORD  : Serial Access Password
950 +AT+PWORD  :  Serial Access Password
786 786  
787 787  
788 788  
789 789  = ​5.  FAQ =
790 790  
956 +
791 791  == 5.1 ​ How to Upgrade Firmware ==
792 792  
793 793  
... ... @@ -800,7 +800,7 @@
800 800  )))
801 801  
802 802  (((
803 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
969 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
804 804  )))
805 805  
806 806  
... ... @@ -807,6 +807,7 @@
807 807  
808 808  = 6.  Trouble Shooting =
809 809  
976 +
810 810  == 6.1  ​Connection problem when uploading firmware ==
811 811  
812 812  
... ... @@ -822,6 +822,7 @@
822 822  
823 823  == 6.2  AT Command input doesn't work ==
824 824  
992 +
825 825  (((
826 826  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.
827 827  
... ... @@ -847,7 +847,7 @@
847 847  
848 848  (% style="color:#037691" %)**Package Includes**:
849 849  
850 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
1018 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1
851 851  * External antenna x 1
852 852  )))
853 853  
... ... @@ -854,9 +854,9 @@
854 854  (((
855 855  
856 856  
1025 +
857 857  (% style="color:#037691" %)**Dimension and weight**:
858 858  
859 -
860 860  * Device Size: 13.0 x 5 x 4.5 cm
861 861  * Device Weight: 150g
862 862  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -872,5 +872,6 @@
872 872  
873 873  = 9.  Support =
874 874  
1043 +
875 875  * 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.
876 876  * 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]]
image-20220908175246-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +282.9 KB
Content

Applications

Navigation

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