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