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