Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.13 >
edited by Xiaoling
on 2023/04/24 10:07
To version < 100.1 >
edited by Xiaoling
on 2022/07/11 14:11
>
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
... ... @@ -73,7 +73,6 @@
73 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
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
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -105,7 +105,6 @@
105 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  
124 +
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  
148 +
150 150  == 2.2 ​ Configure the NDDS75 ==
151 151  
151 +
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.
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
165 165  )))
166 166  
167 167  
... ... @@ -168,9 +168,9 @@
168 168  [[image:1657328756309-230.png]]
169 169  
170 170  
170 +
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  
185 +
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  
196 +**Connection:**
197 197  
198 -(% style="color:blue" %)**Connection:**
198 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 199  
200 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
200 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
202 + (% 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]]**
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/]]
224 224  )))
225 225  
226 226  
224 +
227 227  === 2.2.4 Use CoAP protocol to uplink data ===
228 228  
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/]]
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
238 +(% 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 -
241 +(% 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  
258 +
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
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
275 275  
276 276  [[image:1657330501006-241.png]]
277 277  
... ... @@ -279,16 +279,17 @@
279 279  [[image:1657330533775-472.png]]
280 280  
281 281  
272 +
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
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
292 292  
293 293  [[image:1657249978444-674.png]]
294 294  
... ... @@ -301,11 +301,12 @@
301 301  )))
302 302  
303 303  
295 +
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
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
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  
308 +
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
313 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
322 322  
323 323  (((
324 -
325 -
326 -
327 327  (% style="color:red" %)**NOTE:**
317 +)))
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:**
319 +(((
320 +(% 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  
329 +
344 344  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
345 345  |=(% style="width: 60px;" %)(((
346 346  **Size(bytes)**
... ... @@ -348,78 +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.
337 +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 -=== 2.3.2  Since firmware v1.3.2 ===
377 -
378 -
379 -In this mode, uplink payload includes 69 bytes in total by default.
380 -
381 -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.
382 -
383 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
384 -|=(% 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**
385 -|=(% 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.......
386 -
387 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
388 -
389 -[[image:image-20220908175246-1.png]]
390 -
391 -
343 +(((
392 392  The payload is ASCII string, representative same HEX:
345 +)))
393 393  
394 -**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 (%%)**
347 +(((
348 +0x72403155615900640c6c19029200 where:
349 +)))
395 395  
396 -**where:**
351 +* (((
352 +Device ID: 0x724031556159 = 724031556159
353 +)))
354 +* (((
355 +Version: 0x0064=100=1.0.0
356 +)))
397 397  
398 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
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
399 399  
400 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
401 401  
402 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
403 403  
404 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
372 +
373 +)))
405 405  
406 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
407 -
408 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
409 -
410 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
411 -
412 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
413 -
414 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
415 -
416 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
417 -
418 418  == 2.4  Payload Explanation and Sensor Interface ==
419 419  
377 +
420 420  === 2.4.1  Device ID ===
421 421  
422 -
423 423  (((
424 424  By default, the Device ID equal to the last 6 bytes of IMEI.
425 425  )))
... ... @@ -426,12 +426,10 @@
426 426  
427 427  (((
428 428  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
429 -
430 -
431 431  )))
432 432  
433 433  (((
434 -(% style="color:blue" %)**Example :**
389 +**Example:**
435 435  )))
436 436  
437 437  (((
... ... @@ -439,25 +439,13 @@
439 439  )))
440 440  
441 441  (((
442 -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.
397 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
443 443  )))
444 444  
445 445  
446 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
447 447  
448 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
449 -
450 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 -
452 -
453 -(% style="color:blue" %)**Example :**
454 -
455 -AT+DEUI=868411056754138
456 -
457 -
458 458  === 2.4.2  Version Info ===
459 459  
460 -
461 461  (((
462 462  Specify the software version: 0x64=100, means firmware version 1.00.
463 463  )))
... ... @@ -467,9 +467,9 @@
467 467  )))
468 468  
469 469  
413 +
470 470  === 2.4.3  Battery Info ===
471 471  
472 -
473 473  (((
474 474  Ex1: 0x0B45 = 2885mV
475 475  )))
... ... @@ -479,9 +479,9 @@
479 479  )))
480 480  
481 481  
425 +
482 482  === 2.4.4  Signal Strength ===
483 483  
484 -
485 485  (((
486 486  NB-IoT Network signal Strength.
487 487  )))
... ... @@ -511,9 +511,9 @@
511 511  )))
512 512  
513 513  
457 +
514 514  === 2.4.5  Distance ===
515 515  
516 -
517 517  Get the distance. Flat object range 280mm - 7500mm.
518 518  
519 519  (((
... ... @@ -530,9 +530,12 @@
530 530  
531 531  )))
532 532  
476 +(((
477 +
478 +)))
479 +
533 533  === 2.4.6  Digital Interrupt ===
534 534  
535 -
536 536  (((
537 537  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.
538 538  )))
... ... @@ -542,7 +542,7 @@
542 542  )))
543 543  
544 544  (((
545 -(% 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]])**.**
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]])**.**
546 546  )))
547 547  
548 548  
... ... @@ -564,9 +564,9 @@
564 564  )))
565 565  
566 566  
513 +
567 567  === 2.4.7  ​+5V Output ===
568 568  
569 -
570 570  (((
571 571  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
572 572  )))
... ... @@ -574,14 +574,10 @@
574 574  
575 575  (((
576 576  The 5V output time can be controlled by AT Command.
577 -
578 -
579 579  )))
580 580  
581 581  (((
582 582  (% style="color:blue" %)**AT+5VT=1000**
583 -
584 -
585 585  )))
586 586  
587 587  (((
... ... @@ -589,9 +589,9 @@
589 589  )))
590 590  
591 591  
534 +
592 592  == 2.5  Downlink Payload ==
593 593  
594 -
595 595  By default, NDDS75 prints the downlink payload to console port.
596 596  
597 597  [[image:image-20220709100028-1.png]]
... ... @@ -641,88 +641,125 @@
641 641  )))
642 642  
643 643  
644 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
645 645  
587 +== 2.6  ​LED Indicator ==
646 646  
647 -(% style="color:blue" %)** ➢ AT Command:**
648 648  
649 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
590 +The NDDS75 has an internal LED which is to show the status of different state.
650 650  
651 -² When min=0, and max≠0, Alarm higher than max
652 652  
653 -² When min≠0, and max=0, Alarm lower than min
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.
654 654  
655 -² When min≠0 and max≠0, Alarm higher than max or lower than min
598 +(((
599 +
600 +)))
656 656  
657 657  
658 -(% style="color:blue" %)** Example:**
659 659  
660 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
604 +== 2.7  ​Firmware Change Log ==
661 661  
662 662  
663 -== 2.7  Set the number of data to be uploaded and the recording time ==
607 +(((
608 +Download URL & Firmware Change log
609 +)))
664 664  
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 +)))
665 665  
666 -(% style="color:blue" %)** ➢ AT Command:**
667 667  
668 -* (% 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)
669 -* (% 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.
616 +(((
617 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
618 +)))
670 670  
671 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
672 672  
673 -[[image:image-20221009001114-1.png||height="687" width="955"]]
674 674  
622 +== 2.8  ​Battery Analysis ==
675 675  
676 -== 2.8  Read or Clear cached data ==
624 +=== 2.8.1  ​Battery Type ===
677 677  
678 678  
679 -(% style="color:blue" %)** ➢ AT Command:**
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 +)))
680 680  
681 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
682 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
631 +(((
632 +The battery is designed to last for several years depends on the actually use environment and update interval. 
633 +)))
683 683  
684 -[[image:image-20220908175333-2.png]]
635 +(((
636 +The battery related documents as below:
637 +)))
685 685  
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/]]
686 686  
687 -== 2.9  ​LED Indicator ==
643 +(((
644 +[[image:image-20220709101450-2.png]]
645 +)))
688 688  
689 689  
690 -The NDDS75 has an internal LED which is to show the status of different state.
691 691  
649 +=== 2.8.2  Power consumption Analyze ===
692 692  
693 -* 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)
694 -* Then the LED will be on for 1 second means device is boot normally.
695 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
696 -* For each uplink probe, LED will be on for 500ms.
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 697  
655 +
698 698  (((
699 -
657 +Instruction to use as below:
700 700  )))
701 701  
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 +)))
702 702  
703 -== 2.10  ​Firmware Change Log ==
704 704  
665 +(((
666 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
667 +)))
705 705  
669 +* (((
670 +Product Model
671 +)))
672 +* (((
673 +Uplink Interval
674 +)))
675 +* (((
676 +Working Mode
677 +)))
678 +
706 706  (((
707 -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]]
680 +And the Life expectation in difference case will be shown on the right.
708 708  )))
709 709  
683 +[[image:image-20220709110451-3.png]]
684 +
685 +
686 +
687 +=== 2.8.3  ​Battery Note ===
688 +
710 710  (((
711 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
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.
712 712  )))
713 713  
714 714  
715 -== 2.11 Battery & Power Consumption ==
716 716  
695 +=== 2.8.4  Replace the battery ===
717 717  
718 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
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 +)))
719 719  
720 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
721 721  
722 722  
723 723  = 3. ​ Access NB-IoT Module =
724 724  
725 -
726 726  (((
727 727  Users can directly access the AT command set of the NB-IoT module.
728 728  )))
... ... @@ -729,107 +729,90 @@
729 729  
730 730  (((
731 731  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/]] 
732 -
733 -
734 734  )))
735 735  
736 736  [[image:1657333200519-600.png]]
737 737  
738 738  
716 +
739 739  = 4.  Using the AT Commands =
740 740  
741 741  == 4.1  Access AT Commands ==
742 742  
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/]]
743 743  
744 -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]]
745 745  
724 +AT+<CMD>?  : Help on <CMD>
746 746  
747 -AT+<CMD>?  :  Help on <CMD>
726 +AT+<CMD>         : Run <CMD>
748 748  
749 -AT+<CMD>         :  Run <CMD>
728 +AT+<CMD>=<value> : Set the value
750 750  
751 -AT+<CMD>=<value> :  Set the value
730 +AT+<CMD>=?  : Get the value
752 752  
753 -AT+<CMD>=?  :  Get the value
754 754  
755 -
756 756  (% style="color:#037691" %)**General Commands**(%%)      
757 757  
758 -AT  :  Attention       
735 +AT  : Attention       
759 759  
760 -AT?  :  Short Help     
737 +AT?  : Short Help     
761 761  
762 -ATZ  :  MCU Reset    
739 +ATZ  : MCU Reset    
763 763  
764 -AT+TDC  :  Application Data Transmission Interval
741 +AT+TDC  : Application Data Transmission Interval
765 765  
766 -AT+CFG  :  Print all configurations
743 +AT+CFG  : Print all configurations
767 767  
768 -AT+CFGMOD           :  Working mode selection
745 +AT+CFGMOD           : Working mode selection
769 769  
770 -AT+INTMOD            :  Set the trigger interrupt mode
747 +AT+INTMOD            : Set the trigger interrupt mode
771 771  
772 -AT+5VT  :  Set extend the time of 5V power  
749 +AT+5VT  : Set extend the time of 5V power  
773 773  
774 -AT+PRO  :  Choose agreement
751 +AT+PRO  : Choose agreement
775 775  
776 -AT+WEIGRE  :  Get weight or set weight to 0
753 +AT+WEIGRE  : Get weight or set weight to 0
777 777  
778 -AT+WEIGAP  :  Get or Set the GapValue of weight
755 +AT+WEIGAP  : Get or Set the GapValue of weight
779 779  
780 -AT+RXDL  :  Extend the sending and receiving time
757 +AT+RXDL  : Extend the sending and receiving time
781 781  
782 -AT+CNTFAC  :  Get or set counting parameters
759 +AT+CNTFAC  : Get or set counting parameters
783 783  
784 -AT+SERVADDR  :  Server Address
761 +AT+SERVADDR  : Server Address
785 785  
786 -AT+TR  :  Get or Set record time"
787 787  
788 -AT+APN     :  Get or set the APN
789 -
790 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
791 -
792 -AT+DNSCFG  : Get or Set DNS Server
793 -
794 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
795 -
796 -AT+NOUD  :  Get or Set the number of data to be uploaded
797 -
798 -AT+CDP     :  Read or Clear cached data
799 -
800 -AT+LDDSALARM :  Get or Set alarm of distance
801 -
802 -
803 803  (% style="color:#037691" %)**COAP Management**      
804 804  
805 -AT+URI            :  Resource parameters
766 +AT+URI            : Resource parameters
806 806  
807 807  
808 808  (% style="color:#037691" %)**UDP Management**
809 809  
810 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
771 +AT+CFM          : Upload confirmation mode (only valid for UDP)
811 811  
812 812  
813 813  (% style="color:#037691" %)**MQTT Management**
814 814  
815 -AT+CLIENT  :  Get or Set MQTT client
776 +AT+CLIENT               : Get or Set MQTT client
816 816  
817 -AT+UNAME  :  Get or Set MQTT Username
778 +AT+UNAME  : Get or Set MQTT Username
818 818  
819 -AT+PWD  :  Get or Set MQTT password
780 +AT+PWD                  : Get or Set MQTT password
820 820  
821 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
782 +AT+PUBTOPIC  : Get or Set MQTT publish topic
822 822  
823 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
784 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
824 824  
825 825  
826 826  (% style="color:#037691" %)**Information**          
827 827  
828 -AT+FDR  :  Factory Data Reset
789 +AT+FDR  : Factory Data Reset
829 829  
830 -AT+PWORD  :  Serial Access Password
791 +AT+PWORD  : Serial Access Password
831 831  
832 832  
794 +
833 833  = ​5.  FAQ =
834 834  
835 835  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -844,10 +844,11 @@
844 844  )))
845 845  
846 846  (((
847 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
809 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
848 848  )))
849 849  
850 850  
813 +
851 851  = 6.  Trouble Shooting =
852 852  
853 853  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -862,20 +862,16 @@
862 862  
863 863  )))
864 864  
828 +
865 865  == 6.2  AT Command input doesn't work ==
866 866  
867 -
868 868  (((
869 869  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 +
870 870  )))
871 871  
872 872  
873 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
874 -
875 -
876 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**.
877 -
878 -
879 879  = 7. ​ Order Info =
880 880  
881 881  
... ... @@ -882,6 +882,11 @@
882 882  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
883 883  
884 884  
844 +(% class="wikigeneratedid" %)
845 +(((
846 +
847 +)))
848 +
885 885  = 8.  Packing Info =
886 886  
887 887  (((
... ... @@ -907,12 +907,11 @@
907 907  (((
908 908  
909 909  
874 +
910 910  
911 911  )))
912 912  
913 913  = 9.  Support =
914 914  
915 -
916 916  * 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.
917 -
918 918  * 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