Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.11 >
edited by Xiaoling
on 2023/04/04 13:39
To version < 99.1 >
edited by Xiaoling
on 2022/07/11 14:10
>
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 +
56 56  == 1.2 ​ Features ==
57 57  
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
... ... @@ -70,10 +70,8 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
73 -
74 74  == 1.3  Specification ==
75 75  
76 -
77 77  (% style="color:#037691" %)**Common DC Characteristics:**
78 78  
79 79  * Supply Voltage: 2.1v ~~ 3.6v
... ... @@ -81,12 +81,12 @@
81 81  
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
82 +* - B1 @H-FDD: 2100MHz
83 +* - B3 @H-FDD: 1800MHz
84 +* - B8 @H-FDD: 900MHz
85 +* - B5 @H-FDD: 850MHz
86 +* - B20 @H-FDD: 800MHz
87 +* - B28 @H-FDD: 700MHz
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -99,13 +99,11 @@
99 99  (% style="color:#037691" %)**Power Consumption**
100 100  
101 101  * STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
100 +* Max transmit power: 350mA@3.3v
103 103  
104 104  
105 -
106 106  == ​1.4  Applications ==
107 107  
108 -
109 109  * Smart Buildings & Home Automation
110 110  * Logistics and Supply Chain Management
111 111  * Smart Metering
... ... @@ -123,11 +123,11 @@
123 123  [[image:1657328609906-564.png]]
124 124  
125 125  
122 +
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
127 127  
128 128  == 2.1  How it works ==
129 129  
130 -
131 131  (((
132 132  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.
133 133  )))
... ... @@ -147,11 +147,12 @@
147 147  
148 148  )))
149 149  
146 +
150 150  == 2.2 ​ Configure the NDDS75 ==
151 151  
149 +
152 152  === 2.2.1 Test Requirement ===
153 153  
154 -
155 155  (((
156 156  To use NDDS75 in your city, make sure meet below requirements:
157 157  )))
... ... @@ -161,7 +161,7 @@
161 161  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162 162  
163 163  (((
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.
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
165 165  )))
166 166  
167 167  
... ... @@ -168,9 +168,9 @@
168 168  [[image:1657328756309-230.png]]
169 169  
170 170  
168 +
171 171  === 2.2.2 Insert SIM card ===
172 172  
173 -
174 174  (((
175 175  Insert the NB-IoT Card get from your provider.
176 176  )))
... ... @@ -183,9 +183,9 @@
183 183  [[image:1657328884227-504.png]]
184 184  
185 185  
183 +
186 186  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187 187  
188 -
189 189  (((
190 190  (((
191 191  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.
... ... @@ -194,16 +194,15 @@
194 194  
195 195  [[image:image-20220709092052-2.png]]
196 196  
194 +**Connection:**
197 197  
198 -(% style="color:blue" %)**Connection:**
196 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 199  
200 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
198 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
200 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
203 203  
204 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
205 205  
206 -
207 207  In the PC, use below serial tool settings:
208 208  
209 209  * Baud:  (% style="color:green" %)**9600**
... ... @@ -218,18 +218,17 @@
218 218  
219 219  [[image:1657329814315-101.png]]
220 220  
221 -
222 222  (((
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]]**
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/]]
224 224  )))
225 225  
226 226  
222 +
227 227  === 2.2.4 Use CoAP protocol to uplink data ===
228 228  
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/]]
229 229  
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/]]**
231 231  
232 -
233 233  (((
234 234  **Use below commands:**
235 235  )))
... ... @@ -238,40 +238,33 @@
238 238  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
239 239  )))
240 240  * (((
241 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
236 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
242 242  )))
243 243  * (((
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 -
239 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
248 248  )))
249 249  
250 250  (((
251 251  For parameter description, please refer to AT command set
252 -
253 -
254 254  )))
255 255  
256 256  [[image:1657330452568-615.png]]
257 257  
258 258  
259 -
260 260  (((
261 261  After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
262 -
263 -
264 264  )))
265 265  
266 266  [[image:1657330472797-498.png]]
267 267  
268 268  
256 +
269 269  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
270 270  
271 271  
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
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
275 275  
276 276  [[image:1657330501006-241.png]]
277 277  
... ... @@ -279,16 +279,17 @@
279 279  [[image:1657330533775-472.png]]
280 280  
281 281  
270 +
282 282  === 2.2.6 Use MQTT protocol to uplink data ===
283 283  
284 284  
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
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
292 292  
293 293  [[image:1657249978444-674.png]]
294 294  
... ... @@ -301,11 +301,12 @@
301 301  )))
302 302  
303 303  
293 +
304 304  === 2.2.7 Use TCP protocol to uplink data ===
305 305  
306 306  
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
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
309 309  
310 310  [[image:image-20220709093918-1.png]]
311 311  
... ... @@ -313,34 +313,28 @@
313 313  [[image:image-20220709093918-2.png]]
314 314  
315 315  
306 +
316 316  === 2.2.8 Change Update Interval ===
317 317  
318 -
319 319  User can use below command to change the (% style="color:green" %)**uplink interval**.
320 320  
321 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
311 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322 322  
323 323  (((
324 -
325 -
326 -
327 327  (% style="color:red" %)**NOTE:**
315 +)))
328 328  
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:**
317 +(((
318 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
332 332  )))
333 333  
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).**
335 335  
336 336  
337 337  == 2.3  Uplink Payload ==
338 338  
339 -=== 2.3.1  Before Firmware v1.3.2 ===
340 -
341 -
342 342  In this mode, uplink payload includes in total 14 bytes
343 343  
327 +
344 344  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
345 345  |=(% style="width: 60px;" %)(((
346 346  **Size(bytes)**
... ... @@ -348,82 +348,49 @@
348 348  |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
349 349  
350 350  (((
351 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
335 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
352 352  )))
353 353  
354 354  
355 355  [[image:1657331036973-987.png]]
356 356  
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 -
341 +(((
394 394  The payload is ASCII string, representative same HEX:
343 +)))
395 395  
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 (%%)**
345 +(((
346 +0x72403155615900640c6c19029200 where:
347 +)))
397 397  
398 -**where:**
349 +* (((
350 +Device ID: 0x724031556159 = 724031556159
351 +)))
352 +* (((
353 +Version: 0x0064=100=1.0.0
354 +)))
399 399  
400 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
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
401 401  
402 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
403 403  
404 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
405 405  
406 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
370 +
371 +)))
407 407  
408 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
409 -
410 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
411 -
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 422  == 2.4  Payload Explanation and Sensor Interface ==
423 423  
375 +
424 424  === 2.4.1  Device ID ===
425 425  
426 -
427 427  (((
428 428  By default, the Device ID equal to the last 6 bytes of IMEI.
429 429  )))
... ... @@ -430,12 +430,10 @@
430 430  
431 431  (((
432 432  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
433 -
434 -
435 435  )))
436 436  
437 437  (((
438 -(% style="color:blue" %)**Example :**
387 +**Example:**
439 439  )))
440 440  
441 441  (((
... ... @@ -443,25 +443,13 @@
443 443  )))
444 444  
445 445  (((
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.
395 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
447 447  )))
448 448  
449 449  
450 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
451 451  
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 -
462 462  === 2.4.2  Version Info ===
463 463  
464 -
465 465  (((
466 466  Specify the software version: 0x64=100, means firmware version 1.00.
467 467  )))
... ... @@ -471,9 +471,9 @@
471 471  )))
472 472  
473 473  
411 +
474 474  === 2.4.3  Battery Info ===
475 475  
476 -
477 477  (((
478 478  Ex1: 0x0B45 = 2885mV
479 479  )))
... ... @@ -483,9 +483,9 @@
483 483  )))
484 484  
485 485  
423 +
486 486  === 2.4.4  Signal Strength ===
487 487  
488 -
489 489  (((
490 490  NB-IoT Network signal Strength.
491 491  )))
... ... @@ -515,9 +515,9 @@
515 515  )))
516 516  
517 517  
455 +
518 518  === 2.4.5  Distance ===
519 519  
520 -
521 521  Get the distance. Flat object range 280mm - 7500mm.
522 522  
523 523  (((
... ... @@ -534,9 +534,12 @@
534 534  
535 535  )))
536 536  
474 +(((
475 +
476 +)))
477 +
537 537  === 2.4.6  Digital Interrupt ===
538 538  
539 -
540 540  (((
541 541  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.
542 542  )))
... ... @@ -546,7 +546,7 @@
546 546  )))
547 547  
548 548  (((
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]])**.**
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]])**.**
550 550  )))
551 551  
552 552  
... ... @@ -568,9 +568,9 @@
568 568  )))
569 569  
570 570  
511 +
571 571  === 2.4.7  ​+5V Output ===
572 572  
573 -
574 574  (((
575 575  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
576 576  )))
... ... @@ -578,14 +578,10 @@
578 578  
579 579  (((
580 580  The 5V output time can be controlled by AT Command.
581 -
582 -
583 583  )))
584 584  
585 585  (((
586 586  (% style="color:blue" %)**AT+5VT=1000**
587 -
588 -
589 589  )))
590 590  
591 591  (((
... ... @@ -593,9 +593,9 @@
593 593  )))
594 594  
595 595  
532 +
596 596  == 2.5  Downlink Payload ==
597 597  
598 -
599 599  By default, NDDS75 prints the downlink payload to console port.
600 600  
601 601  [[image:image-20220709100028-1.png]]
... ... @@ -645,88 +645,125 @@
645 645  )))
646 646  
647 647  
648 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
649 649  
585 +== 2.6  ​LED Indicator ==
650 650  
651 -(% style="color:blue" %)** ➢ AT Command:**
652 652  
653 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
588 +The NDDS75 has an internal LED which is to show the status of different state.
654 654  
655 -² When min=0, and max≠0, Alarm higher than max
656 656  
657 -² When min≠0, and max=0, Alarm lower than min
591 +* 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)
592 +* Then the LED will be on for 1 second means device is boot normally.
593 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
594 +* For each uplink probe, LED will be on for 500ms.
658 658  
659 -² When min≠0 and max≠0, Alarm higher than max or lower than min
596 +(((
597 +
598 +)))
660 660  
661 661  
662 -(% style="color:blue" %)** Example:**
663 663  
664 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
602 +== 2.7  ​Firmware Change Log ==
665 665  
666 666  
667 -== 2.7  Set the number of data to be uploaded and the recording time ==
605 +(((
606 +Download URL & Firmware Change log
607 +)))
668 668  
609 +(((
610 +[[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/]]
611 +)))
669 669  
670 -(% style="color:blue" %)** ➢ AT Command:**
671 671  
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.
614 +(((
615 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
616 +)))
674 674  
675 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
676 676  
677 -[[image:image-20221009001114-1.png||height="687" width="955"]]
678 678  
620 +== 2.8  ​Battery Analysis ==
679 679  
680 -== 2.8  Read or Clear cached data ==
622 +=== 2.8.1  ​Battery Type ===
681 681  
682 682  
683 -(% style="color:blue" %)** ➢ AT Command:**
625 +(((
626 +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.
627 +)))
684 684  
685 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
686 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
629 +(((
630 +The battery is designed to last for several years depends on the actually use environment and update interval. 
631 +)))
687 687  
688 -[[image:image-20220908175333-2.png]]
633 +(((
634 +The battery related documents as below:
635 +)))
689 689  
637 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
638 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
639 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
690 690  
691 -== 2.9  ​LED Indicator ==
641 +(((
642 +[[image:image-20220709101450-2.png]]
643 +)))
692 692  
693 693  
694 -The NDDS75 has an internal LED which is to show the status of different state.
695 695  
647 +=== 2.8.2  Power consumption Analyze ===
696 696  
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.
649 +(((
650 +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.
651 +)))
701 701  
653 +
702 702  (((
703 -
655 +Instruction to use as below:
704 704  )))
705 705  
658 +(((
659 +(% 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/]]
660 +)))
706 706  
707 -== 2.10  ​Firmware Change Log ==
708 708  
663 +(((
664 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
665 +)))
709 709  
667 +* (((
668 +Product Model
669 +)))
670 +* (((
671 +Uplink Interval
672 +)))
673 +* (((
674 +Working Mode
675 +)))
676 +
710 710  (((
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]]
678 +And the Life expectation in difference case will be shown on the right.
712 712  )))
713 713  
681 +[[image:image-20220709110451-3.png]]
682 +
683 +
684 +
685 +=== 2.8.3  ​Battery Note ===
686 +
714 714  (((
715 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
688 +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.
716 716  )))
717 717  
718 718  
719 -== 2.11 Battery & Power Consumption ==
720 720  
693 +=== 2.8.4  Replace the battery ===
721 721  
722 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
695 +(((
696 +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).
697 +)))
723 723  
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/]] .
725 725  
726 726  
727 727  = 3. ​ Access NB-IoT Module =
728 728  
729 -
730 730  (((
731 731  Users can directly access the AT command set of the NB-IoT module.
732 732  )))
... ... @@ -733,107 +733,90 @@
733 733  
734 734  (((
735 735  The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
736 -
737 -
738 738  )))
739 739  
740 740  [[image:1657333200519-600.png]]
741 741  
742 742  
714 +
743 743  = 4.  Using the AT Commands =
744 744  
745 745  == 4.1  Access AT Commands ==
746 746  
719 +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/]]
747 747  
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]]
749 749  
722 +AT+<CMD>?  : Help on <CMD>
750 750  
751 -AT+<CMD>?  :  Help on <CMD>
724 +AT+<CMD>         : Run <CMD>
752 752  
753 -AT+<CMD>         :  Run <CMD>
726 +AT+<CMD>=<value> : Set the value
754 754  
755 -AT+<CMD>=<value> :  Set the value
728 +AT+<CMD>=?  : Get the value
756 756  
757 -AT+<CMD>=?  :  Get the value
758 758  
759 -
760 760  (% style="color:#037691" %)**General Commands**(%%)      
761 761  
762 -AT  :  Attention       
733 +AT  : Attention       
763 763  
764 -AT?  :  Short Help     
735 +AT?  : Short Help     
765 765  
766 -ATZ  :  MCU Reset    
737 +ATZ  : MCU Reset    
767 767  
768 -AT+TDC  :  Application Data Transmission Interval
739 +AT+TDC  : Application Data Transmission Interval
769 769  
770 -AT+CFG  :  Print all configurations
741 +AT+CFG  : Print all configurations
771 771  
772 -AT+CFGMOD           :  Working mode selection
743 +AT+CFGMOD           : Working mode selection
773 773  
774 -AT+INTMOD            :  Set the trigger interrupt mode
745 +AT+INTMOD            : Set the trigger interrupt mode
775 775  
776 -AT+5VT  :  Set extend the time of 5V power  
747 +AT+5VT  : Set extend the time of 5V power  
777 777  
778 -AT+PRO  :  Choose agreement
749 +AT+PRO  : Choose agreement
779 779  
780 -AT+WEIGRE  :  Get weight or set weight to 0
751 +AT+WEIGRE  : Get weight or set weight to 0
781 781  
782 -AT+WEIGAP  :  Get or Set the GapValue of weight
753 +AT+WEIGAP  : Get or Set the GapValue of weight
783 783  
784 -AT+RXDL  :  Extend the sending and receiving time
755 +AT+RXDL  : Extend the sending and receiving time
785 785  
786 -AT+CNTFAC  :  Get or set counting parameters
757 +AT+CNTFAC  : Get or set counting parameters
787 787  
788 -AT+SERVADDR  :  Server Address
759 +AT+SERVADDR  : Server Address
789 789  
790 -AT+TR  :  Get or Set record time"
791 791  
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 -
807 807  (% style="color:#037691" %)**COAP Management**      
808 808  
809 -AT+URI            :  Resource parameters
764 +AT+URI            : Resource parameters
810 810  
811 811  
812 812  (% style="color:#037691" %)**UDP Management**
813 813  
814 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
769 +AT+CFM          : Upload confirmation mode (only valid for UDP)
815 815  
816 816  
817 817  (% style="color:#037691" %)**MQTT Management**
818 818  
819 -AT+CLIENT  :  Get or Set MQTT client
774 +AT+CLIENT               : Get or Set MQTT client
820 820  
821 -AT+UNAME  :  Get or Set MQTT Username
776 +AT+UNAME  : Get or Set MQTT Username
822 822  
823 -AT+PWD  :  Get or Set MQTT password
778 +AT+PWD                  : Get or Set MQTT password
824 824  
825 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
780 +AT+PUBTOPIC  : Get or Set MQTT publish topic
826 826  
827 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
782 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
828 828  
829 829  
830 830  (% style="color:#037691" %)**Information**          
831 831  
832 -AT+FDR  :  Factory Data Reset
787 +AT+FDR  : Factory Data Reset
833 833  
834 -AT+PWORD  :  Serial Access Password
789 +AT+PWORD  : Serial Access Password
835 835  
836 836  
792 +
837 837  = ​5.  FAQ =
838 838  
839 839  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -848,10 +848,11 @@
848 848  )))
849 849  
850 850  (((
851 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
807 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
852 852  )))
853 853  
854 854  
811 +
855 855  = 6.  Trouble Shooting =
856 856  
857 857  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -866,11 +866,13 @@
866 866  
867 867  )))
868 868  
826 +
869 869  == 6.2  AT Command input doesn't work ==
870 870  
871 -
872 872  (((
873 873  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.
831 +
832 +
874 874  )))
875 875  
876 876  
... ... @@ -880,6 +880,11 @@
880 880  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
881 881  
882 882  
842 +(% class="wikigeneratedid" %)
843 +(((
844 +
845 +)))
846 +
883 883  = 8.  Packing Info =
884 884  
885 885  (((
... ... @@ -905,11 +905,11 @@
905 905  (((
906 906  
907 907  
872 +
908 908  
909 909  )))
910 910  
911 911  = 9.  Support =
912 912  
913 -
914 914  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
915 915  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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