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