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