Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 100.1 >
edited by Xiaoling
on 2022/07/11 14:11
To version < 108.11 >
edited by Xiaoling
on 2023/04/04 13:39
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,9 +53,9 @@
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
56 -
57 57  == 1.2 ​ Features ==
58 58  
58 +
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 60  * Ultra low power consumption
61 61  * Distance Detection by Ultrasonic technology
... ... @@ -73,6 +73,7 @@
73 73  
74 74  == 1.3  Specification ==
75 75  
76 +
76 76  (% style="color:#037691" %)**Common DC Characteristics:**
77 77  
78 78  * Supply Voltage: 2.1v ~~ 3.6v
... ... @@ -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
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 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
... ... @@ -98,12 +98,13 @@
98 98  (% style="color:#037691" %)**Power Consumption**
99 99  
100 100  * STOP Mode: 10uA @ 3.3v
101 -* Max transmit power: 350mA@3.3v
102 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
102 102  
103 103  
104 104  
105 105  == ​1.4  Applications ==
106 106  
108 +
107 107  * Smart Buildings & Home Automation
108 108  * Logistics and Supply Chain Management
109 109  * Smart Metering
... ... @@ -121,11 +121,11 @@
121 121  [[image:1657328609906-564.png]]
122 122  
123 123  
124 -
125 125  = 2.  Use NDDS75 to communicate with IoT Server =
126 126  
127 127  == 2.1  How it works ==
128 128  
130 +
129 129  (((
130 130  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.
131 131  )))
... ... @@ -145,12 +145,11 @@
145 145  
146 146  )))
147 147  
148 -
149 149  == 2.2 ​ Configure the NDDS75 ==
150 150  
151 -
152 152  === 2.2.1 Test Requirement ===
153 153  
154 +
154 154  (((
155 155  To use NDDS75 in your city, make sure meet below requirements:
156 156  )))
... ... @@ -160,7 +160,7 @@
160 160  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
161 161  
162 162  (((
163 -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
164 +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.
164 164  )))
165 165  
166 166  
... ... @@ -167,9 +167,9 @@
167 167  [[image:1657328756309-230.png]]
168 168  
169 169  
170 -
171 171  === 2.2.2 Insert SIM card ===
172 172  
173 +
173 173  (((
174 174  Insert the NB-IoT Card get from your provider.
175 175  )))
... ... @@ -182,9 +182,9 @@
182 182  [[image:1657328884227-504.png]]
183 183  
184 184  
185 -
186 186  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187 187  
188 +
188 188  (((
189 189  (((
190 190  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.
... ... @@ -193,15 +193,16 @@
193 193  
194 194  [[image:image-20220709092052-2.png]]
195 195  
196 -**Connection:**
197 197  
198 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
198 +(% style="color:blue" %)**Connection:**
199 199  
200 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
200 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
201 201  
202 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
202 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
203 203  
204 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
204 204  
206 +
205 205  In the PC, use below serial tool settings:
206 206  
207 207  * Baud:  (% style="color:green" %)**9600**
... ... @@ -216,17 +216,18 @@
216 216  
217 217  [[image:1657329814315-101.png]]
218 218  
221 +
219 219  (((
220 -(% 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/]]
223 +(% 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]]**
221 221  )))
222 222  
223 223  
224 -
225 225  === 2.2.4 Use CoAP protocol to uplink data ===
226 226  
227 -(% 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/]]
228 228  
230 +(% 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/]]**
229 229  
232 +
230 230  (((
231 231  **Use below commands:**
232 232  )))
... ... @@ -235,33 +235,40 @@
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
241 +(% 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
244 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
245 +
246 +
247 +
242 242  )))
243 243  
244 244  (((
245 245  For parameter description, please refer to AT command set
252 +
253 +
246 246  )))
247 247  
248 248  [[image:1657330452568-615.png]]
249 249  
250 250  
259 +
251 251  (((
252 252  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
262 +
263 +
253 253  )))
254 254  
255 255  [[image:1657330472797-498.png]]
256 256  
257 257  
258 -
259 259  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
260 260  
261 261  
262 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
263 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
264 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
272 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
273 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
274 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
265 265  
266 266  [[image:1657330501006-241.png]]
267 267  
... ... @@ -269,17 +269,16 @@
269 269  [[image:1657330533775-472.png]]
270 270  
271 271  
272 -
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
285 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
286 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
287 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
288 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
289 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
290 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
291 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
283 283  
284 284  [[image:1657249978444-674.png]]
285 285  
... ... @@ -292,12 +292,11 @@
292 292  )))
293 293  
294 294  
295 -
296 296  === 2.2.7 Use TCP protocol to uplink data ===
297 297  
298 298  
299 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
300 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
307 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
308 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
301 301  
302 302  [[image:image-20220709093918-1.png]]
303 303  
... ... @@ -305,28 +305,34 @@
305 305  [[image:image-20220709093918-2.png]]
306 306  
307 307  
308 -
309 309  === 2.2.8 Change Update Interval ===
310 310  
318 +
311 311  User can use below command to change the (% style="color:green" %)**uplink interval**.
312 312  
313 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
321 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
314 314  
315 315  (((
324 +
325 +
326 +
316 316  (% style="color:red" %)**NOTE:**
317 -)))
318 318  
319 -(((
320 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
329 +(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
330 +
331 +(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
321 321  )))
322 322  
334 +(% 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).**
323 323  
324 324  
325 325  == 2.3  Uplink Payload ==
326 326  
327 -In this mode, uplink payload includes in total 14 bytes
339 +=== 2.3.1  Before Firmware v1.3.2 ===
328 328  
329 329  
342 +In this mode, uplink payload includes in total 14 bytes
343 +
330 330  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
331 331  |=(% style="width: 60px;" %)(((
332 332  **Size(bytes)**
... ... @@ -334,49 +334,82 @@
334 334  |(% 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"]]
335 335  
336 336  (((
337 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
351 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
338 338  )))
339 339  
340 340  
341 341  [[image:1657331036973-987.png]]
342 342  
343 -(((
357 +
358 +The payload is **ASCII** string, representative same HEX:
359 +
360 +(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
361 +
362 +**where :**
363 +
364 +* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
365 +
366 +* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
367 +
368 +* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
369 +
370 +* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
371 +
372 +* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
373 +
374 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
375 +
376 +
377 +
378 +=== 2.3.2  Since firmware v1.3.2 ===
379 +
380 +
381 +In this mode, uplink payload includes 69 bytes in total by default.
382 +
383 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
384 +
385 +(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
386 +|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4**
387 +|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
388 +
389 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
390 +
391 +[[image:image-20220908175246-1.png]]
392 +
393 +
344 344  The payload is ASCII string, representative same HEX:
345 -)))
346 346  
347 -(((
348 -0x72403155615900640c6c19029200 where:
349 -)))
396 +**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 (%%)**
350 350  
351 -* (((
352 -Device ID: 0x724031556159 = 724031556159
353 -)))
354 -* (((
355 -Version: 0x0064=100=1.0.0
356 -)))
398 +**where:**
357 357  
358 -* (((
359 -BAT: 0x0c6c = 3180 mV = 3.180V
360 -)))
361 -* (((
362 -Signal: 0x19 = 25
363 -)))
364 -* (((
365 -Distance: 0x0292= 658 mm
366 -)))
367 -* (((
368 -Interrupt: 0x00 = 0
400 +* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
369 369  
402 +* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
370 370  
404 +* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
371 371  
372 -
373 -)))
406 +* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
374 374  
375 -== 2.4  Payload Explanation and Sensor Interface ==
408 +* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
376 376  
410 +* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
377 377  
412 +* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
413 +
414 +* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
415 +
416 +* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
417 +
418 +* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
419 +
420 +
421 +
422 +== 2.4  Payload Explanation and Sensor Interface ==
423 +
378 378  === 2.4.1  Device ID ===
379 379  
426 +
380 380  (((
381 381  By default, the Device ID equal to the last 6 bytes of IMEI.
382 382  )))
... ... @@ -383,10 +383,12 @@
383 383  
384 384  (((
385 385  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
433 +
434 +
386 386  )))
387 387  
388 388  (((
389 -**Example:**
438 +(% style="color:blue" %)**Example :**
390 390  )))
391 391  
392 392  (((
... ... @@ -394,13 +394,25 @@
394 394  )))
395 395  
396 396  (((
397 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
446 +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.
398 398  )))
399 399  
400 400  
450 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
401 401  
452 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
453 +
454 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 +
456 +
457 +(% style="color:blue" %)**Example :**
458 +
459 +AT+DEUI=868411056754138
460 +
461 +
402 402  === 2.4.2  Version Info ===
403 403  
464 +
404 404  (((
405 405  Specify the software version: 0x64=100, means firmware version 1.00.
406 406  )))
... ... @@ -410,9 +410,9 @@
410 410  )))
411 411  
412 412  
413 -
414 414  === 2.4.3  Battery Info ===
415 415  
476 +
416 416  (((
417 417  Ex1: 0x0B45 = 2885mV
418 418  )))
... ... @@ -422,9 +422,9 @@
422 422  )))
423 423  
424 424  
425 -
426 426  === 2.4.4  Signal Strength ===
427 427  
488 +
428 428  (((
429 429  NB-IoT Network signal Strength.
430 430  )))
... ... @@ -454,9 +454,9 @@
454 454  )))
455 455  
456 456  
457 -
458 458  === 2.4.5  Distance ===
459 459  
520 +
460 460  Get the distance. Flat object range 280mm - 7500mm.
461 461  
462 462  (((
... ... @@ -473,12 +473,9 @@
473 473  
474 474  )))
475 475  
476 -(((
477 -
478 -)))
479 -
480 480  === 2.4.6  Digital Interrupt ===
481 481  
539 +
482 482  (((
483 483  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.
484 484  )))
... ... @@ -488,7 +488,7 @@
488 488  )))
489 489  
490 490  (((
491 -(% 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]])**.**
549 +(% 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]])**.**
492 492  )))
493 493  
494 494  
... ... @@ -510,9 +510,9 @@
510 510  )))
511 511  
512 512  
513 -
514 514  === 2.4.7  ​+5V Output ===
515 515  
573 +
516 516  (((
517 517  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
518 518  )))
... ... @@ -520,10 +520,14 @@
520 520  
521 521  (((
522 522  The 5V output time can be controlled by AT Command.
581 +
582 +
523 523  )))
524 524  
525 525  (((
526 526  (% style="color:blue" %)**AT+5VT=1000**
587 +
588 +
527 527  )))
528 528  
529 529  (((
... ... @@ -531,9 +531,9 @@
531 531  )))
532 532  
533 533  
534 -
535 535  == 2.5  Downlink Payload ==
536 536  
598 +
537 537  By default, NDDS75 prints the downlink payload to console port.
538 538  
539 539  [[image:image-20220709100028-1.png]]
... ... @@ -583,125 +583,88 @@
583 583  )))
584 584  
585 585  
648 +== 2.6  Distance alarm function(Since firmware v1.3.2) ==
586 586  
587 -== 2.6  ​LED Indicator ==
588 588  
651 +(% style="color:blue" %)** ➢ AT Command:**
589 589  
590 -The NDDS75 has an internal LED which is to show the status of different state.
653 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
591 591  
655 +² When min=0, and max≠0, Alarm higher than max
592 592  
593 -* 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)
594 -* Then the LED will be on for 1 second means device is boot normally.
595 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
596 -* For each uplink probe, LED will be on for 500ms.
657 +² When min≠0, and max=0, Alarm lower than min
597 597  
598 -(((
599 -
600 -)))
659 +² When min≠0 and max≠0, Alarm higher than max or lower than min
601 601  
602 602  
662 +(% style="color:blue" %)** Example:**
603 603  
604 -== 2.7  ​Firmware Change Log ==
664 +**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
605 605  
606 606  
607 -(((
608 -Download URL & Firmware Change log
609 -)))
667 +== 2.7  Set the number of data to be uploaded and the recording time ==
610 610  
611 -(((
612 -[[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/]]
613 -)))
614 614  
670 +(% style="color:blue" %)** ➢ AT Command:**
615 615  
616 -(((
617 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
618 -)))
672 +* (% 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)
673 +* (% 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.
619 619  
675 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
620 620  
677 +[[image:image-20221009001114-1.png||height="687" width="955"]]
621 621  
622 -== 2.8  ​Battery Analysis ==
623 623  
624 -=== 2.8.1  ​Battery Type ===
680 +== 2.8  Read or Clear cached data ==
625 625  
626 626  
627 -(((
628 -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.
629 -)))
683 +(% style="color:blue" %)** ➢ AT Command:**
630 630  
631 -(((
632 -The battery is designed to last for several years depends on the actually use environment and update interval. 
633 -)))
685 +* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
686 +* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
634 634  
635 -(((
636 -The battery related documents as below:
637 -)))
688 +[[image:image-20220908175333-2.png]]
638 638  
639 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
641 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
642 642  
643 -(((
644 -[[image:image-20220709101450-2.png]]
645 -)))
691 +== 2.9  ​LED Indicator ==
646 646  
647 647  
694 +The NDDS75 has an internal LED which is to show the status of different state.
648 648  
649 -=== 2.8.2  Power consumption Analyze ===
650 650  
651 -(((
652 -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.
653 -)))
697 +* 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)
698 +* Then the LED will be on for 1 second means device is boot normally.
699 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
700 +* For each uplink probe, LED will be on for 500ms.
654 654  
655 -
656 656  (((
657 -Instruction to use as below:
703 +
658 658  )))
659 659  
660 -(((
661 -(% 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/]]
662 -)))
663 663  
707 +== 2.10  ​Firmware Change Log ==
664 664  
665 -(((
666 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
667 -)))
668 668  
669 -* (((
670 -Product Model
671 -)))
672 -* (((
673 -Uplink Interval
674 -)))
675 -* (((
676 -Working Mode
677 -)))
678 -
679 679  (((
680 -And the Life expectation in difference case will be shown on the right.
711 +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]]
681 681  )))
682 682  
683 -[[image:image-20220709110451-3.png]]
684 -
685 -
686 -
687 -=== 2.8.3  ​Battery Note ===
688 -
689 689  (((
690 -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.
715 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
691 691  )))
692 692  
693 693  
719 +== 2.11 Battery & Power Consumption ==
694 694  
695 -=== 2.8.4  Replace the battery ===
696 696  
697 -(((
698 -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).
699 -)))
722 +NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
700 700  
724 +[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
701 701  
702 702  
703 703  = 3. ​ Access NB-IoT Module =
704 704  
729 +
705 705  (((
706 706  Users can directly access the AT command set of the NB-IoT module.
707 707  )))
... ... @@ -708,90 +708,107 @@
708 708  
709 709  (((
710 710  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/]] 
736 +
737 +
711 711  )))
712 712  
713 713  [[image:1657333200519-600.png]]
714 714  
715 715  
716 -
717 717  = 4.  Using the AT Commands =
718 718  
719 719  == 4.1  Access AT Commands ==
720 720  
721 -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/]]
722 722  
748 +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]]
723 723  
724 -AT+<CMD>?  : Help on <CMD>
725 725  
726 -AT+<CMD>         : Run <CMD>
751 +AT+<CMD>?  :  Help on <CMD>
727 727  
728 -AT+<CMD>=<value> : Set the value
753 +AT+<CMD>         :  Run <CMD>
729 729  
730 -AT+<CMD>=?  : Get the value
755 +AT+<CMD>=<value> :  Set the value
731 731  
757 +AT+<CMD>=?  :  Get the value
732 732  
759 +
733 733  (% style="color:#037691" %)**General Commands**(%%)      
734 734  
735 -AT  : Attention       
762 +AT  :  Attention       
736 736  
737 -AT?  : Short Help     
764 +AT?  :  Short Help     
738 738  
739 -ATZ  : MCU Reset    
766 +ATZ  :  MCU Reset    
740 740  
741 -AT+TDC  : Application Data Transmission Interval
768 +AT+TDC  :  Application Data Transmission Interval
742 742  
743 -AT+CFG  : Print all configurations
770 +AT+CFG  :  Print all configurations
744 744  
745 -AT+CFGMOD           : Working mode selection
772 +AT+CFGMOD           :  Working mode selection
746 746  
747 -AT+INTMOD            : Set the trigger interrupt mode
774 +AT+INTMOD            :  Set the trigger interrupt mode
748 748  
749 -AT+5VT  : Set extend the time of 5V power  
776 +AT+5VT  :  Set extend the time of 5V power  
750 750  
751 -AT+PRO  : Choose agreement
778 +AT+PRO  :  Choose agreement
752 752  
753 -AT+WEIGRE  : Get weight or set weight to 0
780 +AT+WEIGRE  :  Get weight or set weight to 0
754 754  
755 -AT+WEIGAP  : Get or Set the GapValue of weight
782 +AT+WEIGAP  :  Get or Set the GapValue of weight
756 756  
757 -AT+RXDL  : Extend the sending and receiving time
784 +AT+RXDL  :  Extend the sending and receiving time
758 758  
759 -AT+CNTFAC  : Get or set counting parameters
786 +AT+CNTFAC  :  Get or set counting parameters
760 760  
761 -AT+SERVADDR  : Server Address
788 +AT+SERVADDR  :  Server Address
762 762  
790 +AT+TR  :  Get or Set record time"
763 763  
792 +AT+APN     :  Get or set the APN
793 +
794 +AT+FBAND  :  Get or Set whether to automatically modify the frequency band
795 +
796 +AT+DNSCFG  : Get or Set DNS Server
797 +
798 +AT+GETSENSORVALUE   :  Returns the current sensor measurement
799 +
800 +AT+NOUD  :  Get or Set the number of data to be uploaded
801 +
802 +AT+CDP     :  Read or Clear cached data
803 +
804 +AT+LDDSALARM :  Get or Set alarm of distance
805 +
806 +
764 764  (% style="color:#037691" %)**COAP Management**      
765 765  
766 -AT+URI            : Resource parameters
809 +AT+URI            :  Resource parameters
767 767  
768 768  
769 769  (% style="color:#037691" %)**UDP Management**
770 770  
771 -AT+CFM          : Upload confirmation mode (only valid for UDP)
814 +AT+CFM          :  Upload confirmation mode (only valid for UDP)
772 772  
773 773  
774 774  (% style="color:#037691" %)**MQTT Management**
775 775  
776 -AT+CLIENT               : Get or Set MQTT client
819 +AT+CLIENT  :  Get or Set MQTT client
777 777  
778 -AT+UNAME  : Get or Set MQTT Username
821 +AT+UNAME  :  Get or Set MQTT Username
779 779  
780 -AT+PWD                  : Get or Set MQTT password
823 +AT+PWD  :  Get or Set MQTT password
781 781  
782 -AT+PUBTOPIC  : Get or Set MQTT publish topic
825 +AT+PUBTOPIC  :  Get or Set MQTT publish topic
783 783  
784 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
827 +AT+SUBTOPIC  :  Get or Set MQTT subscription topic
785 785  
786 786  
787 787  (% style="color:#037691" %)**Information**          
788 788  
789 -AT+FDR  : Factory Data Reset
832 +AT+FDR  :  Factory Data Reset
790 790  
791 -AT+PWORD  : Serial Access Password
834 +AT+PWORD  :  Serial Access Password
792 792  
793 793  
794 -
795 795  = ​5.  FAQ =
796 796  
797 797  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -806,11 +806,10 @@
806 806  )))
807 807  
808 808  (((
809 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
851 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
810 810  )))
811 811  
812 812  
813 -
814 814  = 6.  Trouble Shooting =
815 815  
816 816  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -825,13 +825,11 @@
825 825  
826 826  )))
827 827  
828 -
829 829  == 6.2  AT Command input doesn't work ==
830 830  
871 +
831 831  (((
832 832  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.
833 -
834 -
835 835  )))
836 836  
837 837  
... ... @@ -841,11 +841,6 @@
841 841  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
842 842  
843 843  
844 -(% class="wikigeneratedid" %)
845 -(((
846 -
847 -)))
848 -
849 849  = 8.  Packing Info =
850 850  
851 851  (((
... ... @@ -871,11 +871,11 @@
871 871  (((
872 872  
873 873  
874 -
875 875  
876 876  )))
877 877  
878 878  = 9.  Support =
879 879  
913 +
880 880  * 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.
881 881  * 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