Version 104.7 by Xiaoling on 2022/09/15 15:02
Show last authors
1 (% style="text-align:center" %)
2 [[image:image-20220709085040-1.png||height="542" width="524"]]
3
4
5
6
7
8 **Table of Contents:**
9
10 {{toc/}}
11
12
13
14
15
16
17 = 1.  Introduction =
18
19
20 == 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21
22 (((
23
24
25 (((
26 (((
27 The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
28 )))
29
30 (((
31 The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
32 )))
33
34 (((
35 NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
36 )))
37
38 (((
39 NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
40 )))
41
42 (((
43 NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
44 )))
45
46 (((
47 To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
48 )))
49 )))
50
51
52 )))
53
54 [[image:1657327959271-447.png]]
55
56
57
58 == 1.2 ​ Features ==
59
60
61 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 * Ultra low power consumption
63 * Distance Detection by Ultrasonic technology
64 * Flat object range 280mm - 7500mm
65 * Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 * Cable Length: 25cm
67 * AT Commands to change parameters
68 * Uplink on periodically
69 * Downlink to change configure
70 * IP66 Waterproof Enclosure
71 * Micro SIM card slot for NB-IoT SIM
72 * 8500mAh Battery for long term use
73
74
75
76 == 1.3  Specification ==
77
78
79 (% style="color:#037691" %)**Common DC Characteristics:**
80
81 * Supply Voltage: 2.1v ~~ 3.6v
82 * Operating Temperature: -40 ~~ 85°C
83
84 (% style="color:#037691" %)**NB-IoT Spec:**
85
86 * - B1 @H-FDD: 2100MHz
87 * - B3 @H-FDD: 1800MHz
88 * - B8 @H-FDD: 900MHz
89 * - B5 @H-FDD: 850MHz
90 * - B20 @H-FDD: 800MHz
91 * - B28 @H-FDD: 700MHz
92
93 (% style="color:#037691" %)**Battery:**
94
95 * Li/SOCI2 un-chargeable battery
96 * Capacity: 8500mAh
97 * Self Discharge: <1% / Year @ 25°C
98 * Max continuously current: 130mA
99 * Max boost current: 2A, 1 second
100
101 (% style="color:#037691" %)**Power Consumption**
102
103 * STOP Mode: 10uA @ 3.3v
104 * Max transmit power: 350mA@3.3v
105
106
107
108 == ​1.4  Applications ==
109
110
111 * Smart Buildings & Home Automation
112 * Logistics and Supply Chain Management
113 * Smart Metering
114 * Smart Agriculture
115 * Smart Cities
116 * Smart Factory
117
118 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
119 ​
120
121
122
123
124 == 1.5  Pin Definitions ==
125
126
127 [[image:1657328609906-564.png]]
128
129
130
131 = 2.  Use NDDS75 to communicate with IoT Server =
132
133
134 == 2.1  How it works ==
135
136
137 (((
138 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.
139 )))
140
141
142 (((
143 The diagram below shows the working flow in default firmware of NDDS75:
144 )))
145
146 (((
147
148 )))
149
150 [[image:1657328659945-416.png]]
151
152 (((
153
154 )))
155
156
157 == 2.2 ​ Configure the NDDS75 ==
158
159
160 === 2.2.1 Test Requirement ===
161
162
163 (((
164 To use NDDS75 in your city, make sure meet below requirements:
165 )))
166
167 * Your local operator has already distributed a NB-IoT Network there.
168 * The local NB-IoT network used the band that NDDS75 supports.
169 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
170
171 (((
172 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.
173 )))
174
175
176 [[image:1657328756309-230.png]]
177
178
179
180 === 2.2.2 Insert SIM card ===
181
182
183 (((
184 Insert the NB-IoT Card get from your provider.
185 )))
186
187 (((
188 User need to take out the NB-IoT module and insert the SIM card like below:
189 )))
190
191
192 [[image:1657328884227-504.png]]
193
194
195
196 === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
197
198
199 (((
200 (((
201 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.
202 )))
203 )))
204
205 [[image:image-20220709092052-2.png]]
206
207
208 (% style="color:blue" %)**Connection:**
209
210 (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
211
212 **~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
213
214 **~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
215
216
217 In the PC, use below serial tool settings:
218
219 * Baud:  (% style="color:green" %)**9600**
220 * Data bits:** (% style="color:green" %)8(%%)**
221 * Stop bits: (% style="color:green" %)**1**
222 * Parity:  (% style="color:green" %)**None**
223 * Flow Control: (% style="color:green" %)**None**
224
225 (((
226 Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
227 )))
228
229 [[image:1657329814315-101.png]]
230
231
232 (((
233 (% 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]]**
234 )))
235
236
237
238 === 2.2.4 Use CoAP protocol to uplink data ===
239
240
241 (% 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/]]**
242
243
244 (((
245 **Use below commands:**
246 )))
247
248 * (((
249 (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
250 )))
251 * (((
252 (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
253 )))
254 * (((
255 (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
256
257
258
259 )))
260
261 (((
262 For parameter description, please refer to AT command set
263
264
265 )))
266
267 [[image:1657330452568-615.png]]
268
269
270
271 (((
272 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.
273
274
275 )))
276
277 [[image:1657330472797-498.png]]
278
279
280
281 === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
282
283
284 * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
285 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
286 * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
287
288
289
290 [[image:1657330501006-241.png]]
291
292
293 [[image:1657330533775-472.png]]
294
295
296
297 === 2.2.6 Use MQTT protocol to uplink data ===
298
299
300 * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
301 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
302 * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
303 * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
304 * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
305 * (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
306 * (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
307
308 [[image:1657249978444-674.png]]
309
310
311 [[image:1657330723006-866.png]]
312
313
314 (((
315 MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
316 )))
317
318
319
320 === 2.2.7 Use TCP protocol to uplink data ===
321
322
323 * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
324 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
325
326 [[image:image-20220709093918-1.png]]
327
328
329 [[image:image-20220709093918-2.png]]
330
331
332
333 === 2.2.8 Change Update Interval ===
334
335
336 User can use below command to change the (% style="color:green" %)**uplink interval**.
337
338 * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
339
340 (((
341
342
343
344 (% style="color:red" %)**NOTE:**
345
346 (% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
347
348 (% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
349 )))
350
351 (% 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).**
352
353
354
355 == 2.3  Uplink Payload ==
356
357
358 === 2.3.1  Before Firmware v1.3.2 ===
359
360
361 In this mode, uplink payload includes in total 14 bytes
362
363 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
364 |=(% style="width: 60px;" %)(((
365 **Size(bytes)**
366 )))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
367 |(% 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"]]
368
369 (((
370 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
371 )))
372
373
374 [[image:1657331036973-987.png]]
375
376
377 (((
378 The payload is **ASCII** string, representative same HEX:
379 )))
380
381 (((
382 0x72403155615900640c6c19029200 where:
383 )))
384
385 * (((
386 Device ID: 0x724031556159 = 724031556159
387 )))
388 * (((
389 Version:  0x0064=100=1.0.0
390 )))
391
392 * (((
393 BAT:  0x0c6c = 3180 mV = 3.180V
394 )))
395 * (((
396 Signal: 0x19 = 25
397 )))
398 * (((
399 Distance: 0x0292= 658 mm
400 )))
401 * (((
402 Interrupt: 0x00 = 0
403
404
405
406
407
408 )))
409
410 === **2.3.2  Since firmware v1.3.2** ===
411
412
413 In this mode, uplink payload includes 69 bytes in total by default.
414
415 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.
416
417 (% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
418 |(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
419 |(% 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.......
420
421 If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
422
423 [[image:image-20220908175246-1.png]]
424
425
426 The payload is ASCII string, representative same HEX:
427
428 0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
429
430 * (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
431 * (% style="color:red" %)Version: 0x0084=132=1.3.2
432 * (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
433 * (% style="color:blue" %)Singal: 0x1e = 30
434 * (% style="color:red" %)Mod: 0x01 = 1
435 * Interrupt: 0x00= 0
436 * Distance: 0x0039= 57 = 57
437 * Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
438 * Distance,Time stamp : 00396319baf0
439 * (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
440
441
442
443 == 2.4  Payload Explanation and Sensor Interface ==
444
445
446 === 2.4.1  Device ID ===
447
448
449 (((
450 By default, the Device ID equal to the last 6 bytes of IMEI.
451 )))
452
453 (((
454 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455
456
457 )))
458
459 (((
460 (% style="color:blue" %)**Example :**
461 )))
462
463 (((
464 AT+DEUI=A84041F15612
465 )))
466
467 (((
468 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.
469 )))
470
471
472 (% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
473
474 (% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
475
476 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
477
478
479 (% style="color:blue" %)**Example :**
480
481 AT+DEUI=868411056754138
482
483
484
485 === 2.4.2  Version Info ===
486
487
488 (((
489 Specify the software version: 0x64=100, means firmware version 1.00.
490 )))
491
492 (((
493 For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
494 )))
495
496
497
498 === 2.4.3  Battery Info ===
499
500
501 (((
502 Ex1: 0x0B45 = 2885mV
503 )))
504
505 (((
506 Ex2: 0x0B49 = 2889mV
507 )))
508
509
510
511 === 2.4.4  Signal Strength ===
512
513
514 (((
515 NB-IoT Network signal Strength.
516 )))
517
518 (((
519 **Ex1: 0x1d = 29**
520 )))
521
522 (((
523 (% style="color:blue" %)**0**(%%)  -113dBm or less
524 )))
525
526 (((
527 (% style="color:blue" %)**1**(%%)  -111dBm
528 )))
529
530 (((
531 (% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
532 )))
533
534 (((
535 (% style="color:blue" %)**31**  (%%) -51dBm or greater
536 )))
537
538 (((
539 (% style="color:blue" %)**99**   (%%) Not known or not detectable
540 )))
541
542
543
544 === 2.4.5  Distance ===
545
546
547 Get the distance. Flat object range 280mm - 7500mm.
548
549 (((
550 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
551 )))
552
553 (((
554 (((
555 (% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
556 )))
557 )))
558
559 (((
560
561 )))
562
563 (((
564
565 )))
566
567 === 2.4.6  Digital Interrupt ===
568
569
570 (((
571 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.
572 )))
573
574 (((
575 The command is:
576 )))
577
578 (((
579 (% 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]])**.**
580 )))
581
582
583 (((
584 The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
585 )))
586
587
588 (((
589 Example:
590 )))
591
592 (((
593 0x(00): Normal uplink packet.
594 )))
595
596 (((
597 0x(01): Interrupt Uplink Packet.
598 )))
599
600
601
602 === 2.4.7  ​+5V Output ===
603
604
605 (((
606 NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
607 )))
608
609
610 (((
611 The 5V output time can be controlled by AT Command.
612
613
614 )))
615
616 (((
617 (% style="color:blue" %)**AT+5VT=1000**
618
619
620 )))
621
622 (((
623 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
624 )))
625
626
627
628 == 2.5  Downlink Payload ==
629
630
631 By default, NDDS75 prints the downlink payload to console port.
632
633 [[image:image-20220709100028-1.png]]
634
635
636 (((
637 (% style="color:blue" %)**Examples:**
638 )))
639
640 (((
641
642 )))
643
644 * (((
645 (% style="color:blue" %)**Set TDC**
646 )))
647
648 (((
649 If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
650 )))
651
652 (((
653 Payload:    01 00 00 1E    TDC=30S
654 )))
655
656 (((
657 Payload:    01 00 00 3C    TDC=60S
658 )))
659
660 (((
661
662 )))
663
664 * (((
665 (% style="color:blue" %)**Reset**
666 )))
667
668 (((
669 If payload = 0x04FF, it will reset the NDDS75
670 )))
671
672
673 * (% style="color:blue" %)**INTMOD**
674
675 (((
676 Downlink Payload: 06000003, Set AT+INTMOD=3
677 )))
678
679
680
681 == 2.6  Distance alarm function(Since firmware v1.3.2) ==
682
683
684 (% style="color:blue" %)** ➢ AT Command:**
685
686 (% style="color:#037691" %)** AT+ LDDSALARM=min,max**
687
688 ² When min=0, and max≠0, Alarm higher than max
689
690 ² When min≠0, and max=0, Alarm lower than min
691
692 ² When min≠0 and max≠0, Alarm higher than max or lower than min
693
694
695 (% style="color:blue" %)** Example:**
696
697 **AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
698
699
700
701 == 2.7  Set the number of data to be uploaded and the recording time ==
702
703
704 (% style="color:blue" %)** ➢ AT Command:**
705
706 * (% 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)
707 * (% 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.
708
709
710
711
712 == 2.8  Read or Clear cached data ==
713
714
715 (% style="color:blue" %)** ➢ AT Command:**
716
717 * (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
718 * (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
719
720 [[image:image-20220908175333-2.png]]
721
722
723
724 == 2.9  ​LED Indicator ==
725
726
727 The NDDS75 has an internal LED which is to show the status of different state.
728
729
730 * 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)
731 * Then the LED will be on for 1 second means device is boot normally.
732 * After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
733 * For each uplink probe, LED will be on for 500ms.
734
735 (((
736
737 )))
738
739
740
741 == 2.10  ​Firmware Change Log ==
742
743
744 (((
745 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]]
746 )))
747
748 (((
749
750 )))
751
752 (((
753 Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
754 )))
755
756
757
758 == 2.11  ​Battery Analysis ==
759
760
761 === 2.11.1  ​Battery Type ===
762
763
764 (((
765 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.
766 )))
767
768 (((
769 The battery is designed to last for several years depends on the actually use environment and update interval. 
770 )))
771
772 (((
773 The battery related documents as below:
774 )))
775
776 * [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
777 * [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
778 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
779
780 (((
781 [[image:image-20220709101450-2.png]]
782 )))
783
784
785
786 === 2.11.2  Power consumption Analyze ===
787
788
789 (((
790 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.
791 )))
792
793
794 (((
795 Instruction to use as below:
796 )))
797
798 (((
799 (% 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/]]
800 )))
801
802
803 (((
804 (% style="color:blue" %)**Step 2: **(%%) Open it and choose
805 )))
806
807 * (((
808 Product Model
809 )))
810 * (((
811 Uplink Interval
812 )))
813 * (((
814 Working Mode
815 )))
816
817 (((
818 And the Life expectation in difference case will be shown on the right.
819 )))
820
821 [[image:image-20220709110451-3.png]]
822
823
824
825 === 2.11.3  ​Battery Note ===
826
827
828 (((
829 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.
830 )))
831
832
833
834 === 2.11.4  Replace the battery ===
835
836
837 (((
838 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).
839 )))
840
841
842
843 = 3. ​ Access NB-IoT Module =
844
845
846 (((
847 Users can directly access the AT command set of the NB-IoT module.
848 )))
849
850 (((
851 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/]] 
852
853
854 )))
855
856 [[image:1657333200519-600.png]]
857
858
859
860 = 4.  Using the AT Commands =
861
862
863 == 4.1  Access AT Commands ==
864
865
866 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]]
867
868
869 AT+<CMD>?  :  Help on <CMD>
870
871 AT+<CMD>         :  Run <CMD>
872
873 AT+<CMD>=<value> :  Set the value
874
875 AT+<CMD>=?  :  Get the value
876
877
878 (% style="color:#037691" %)**General Commands**(%%)      
879
880 AT  :  Attention       
881
882 AT?  :  Short Help     
883
884 ATZ  :  MCU Reset    
885
886 AT+TDC  :  Application Data Transmission Interval
887
888 AT+CFG  :  Print all configurations
889
890 AT+CFGMOD           :  Working mode selection
891
892 AT+INTMOD            :  Set the trigger interrupt mode
893
894 AT+5VT  :  Set extend the time of 5V power  
895
896 AT+PRO  :  Choose agreement
897
898 AT+WEIGRE  :  Get weight or set weight to 0
899
900 AT+WEIGAP  :  Get or Set the GapValue of weight
901
902 AT+RXDL  :  Extend the sending and receiving time
903
904 AT+CNTFAC  :  Get or set counting parameters
905
906 AT+SERVADDR  :  Server Address
907
908 AT+TR  :  Get or Set record time"
909
910 AT+APN     :  Get or set the APN
911
912 AT+FBAND  :  Get or Set whether to automatically modify the frequency band
913
914 AT+DNSCFG  : Get or Set DNS Server
915
916 AT+GETSENSORVALUE   :  Returns the current sensor measurement
917
918 AT+NOUD  :  Get or Set the number of data to be uploaded
919
920 AT+CDP     :  Read or Clear cached data
921
922 AT+LDDSALARM :  Get or Set alarm of distance
923
924
925 (% style="color:#037691" %)**COAP Management**      
926
927 AT+URI            :  Resource parameters
928
929
930 (% style="color:#037691" %)**UDP Management**
931
932 AT+CFM          :  Upload confirmation mode (only valid for UDP)
933
934
935 (% style="color:#037691" %)**MQTT Management**
936
937 AT+CLIENT  :  Get or Set MQTT client
938
939 AT+UNAME  :  Get or Set MQTT Username
940
941 AT+PWD  :  Get or Set MQTT password
942
943 AT+PUBTOPIC  :  Get or Set MQTT publish topic
944
945 AT+SUBTOPIC  :  Get or Set MQTT subscription topic
946
947
948 (% style="color:#037691" %)**Information**          
949
950 AT+FDR  :  Factory Data Reset
951
952 AT+PWORD  :  Serial Access Password
953
954
955
956 = ​5.  FAQ =
957
958
959 == 5.1 ​ How to Upgrade Firmware ==
960
961
962 (((
963 User can upgrade the firmware for 1) bug fix, 2) new feature release.
964 )))
965
966 (((
967 Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
968 )))
969
970 (((
971 (% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
972 )))
973
974
975
976 = 6.  Trouble Shooting =
977
978
979 == 6.1  ​Connection problem when uploading firmware ==
980
981
982 (((
983 **Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
984 )))
985
986 (% class="wikigeneratedid" %)
987 (((
988
989 )))
990
991
992 == 6.2  AT Command input doesn't work ==
993
994
995 (((
996 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.
997
998
999 )))
1000
1001
1002 = 7. ​ Order Info =
1003
1004
1005 Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1006
1007
1008 (% class="wikigeneratedid" %)
1009 (((
1010
1011 )))
1012
1013 = 8.  Packing Info =
1014
1015 (((
1016
1017
1018 (% style="color:#037691" %)**Package Includes**:
1019
1020 * NDDS75 NB-IoT Distance Detect Sensor Node x 1
1021 * External antenna x 1
1022 )))
1023
1024 (((
1025
1026
1027
1028 (% style="color:#037691" %)**Dimension and weight**:
1029
1030 * Device Size: 13.0 x 5 x 4.5 cm
1031 * Device Weight: 150g
1032 * Package Size / pcs : 15 x 12x 5.5 cm
1033 * Weight / pcs : 220g
1034 )))
1035
1036 (((
1037
1038
1039
1040
1041 )))
1042
1043 = 9.  Support =
1044
1045
1046 * 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.
1047 * 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]]

Applications

Navigation

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