Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.22 >
edited by Xiaoling
on 2023/12/14 17:30
To version < 97.15 >
edited by Xiaoling
on 2022/07/09 11:51
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 -- NB-IoT Distance Detect Sensor User Manual
1 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Content
... ... @@ -27,22 +27,27 @@
27 27  )))
28 28  
29 29  (((
30 +
30 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 31  )))
32 32  
33 33  (((
35 +
34 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 35  )))
36 36  
37 37  (((
40 +
38 38  NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
39 39  )))
40 40  
41 41  (((
45 +
42 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 43  )))
44 44  
45 45  (((
50 +
46 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 47  )))
48 48  )))
... ... @@ -53,6 +53,7 @@
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
61 +
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -80,12 +80,12 @@
80 80  
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 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 +* - B1 @H-FDD: 2100MHz
90 +* - B3 @H-FDD: 1800MHz
91 +* - B8 @H-FDD: 900MHz
92 +* - B5 @H-FDD: 850MHz
93 +* - B20 @H-FDD: 800MHz
94 +* - B28 @H-FDD: 700MHz
89 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
... ... @@ -103,7 +103,6 @@
103 103  
104 104  == ​1.4  Applications ==
105 105  
106 -
107 107  * Smart Buildings & Home Automation
108 108  * Logistics and Supply Chain Management
109 109  * Smart Metering
... ... @@ -121,11 +121,11 @@
121 121  [[image:1657328609906-564.png]]
122 122  
123 123  
129 +
124 124  = 2.  Use NDDS75 to communicate with IoT Server =
125 125  
126 126  == 2.1  How it works ==
127 127  
128 -
129 129  (((
130 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 131  )))
... ... @@ -145,21 +145,22 @@
145 145  
146 146  )))
147 147  
153 +
148 148  == 2.2 ​ Configure the NDDS75 ==
149 149  
156 +
150 150  === 2.2.1 Test Requirement ===
151 151  
152 -
153 153  (((
154 154  To use NDDS75 in your city, make sure meet below requirements:
155 155  )))
156 156  
157 157  * Your local operator has already distributed a NB-IoT Network there.
158 -* The local NB-IoT network used the band that NDDS75 supports.
164 +* The local NB-IoT network used the band that NSE01 supports.
159 159  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
160 160  
161 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.
168 +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 163  )))
164 164  
165 165  
... ... @@ -166,9 +166,9 @@
166 166  [[image:1657328756309-230.png]]
167 167  
168 168  
175 +
169 169  === 2.2.2 Insert SIM card ===
170 170  
171 -
172 172  (((
173 173  Insert the NB-IoT Card get from your provider.
174 174  )))
... ... @@ -181,9 +181,9 @@
181 181  [[image:1657328884227-504.png]]
182 182  
183 183  
190 +
184 184  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
185 185  
186 -
187 187  (((
188 188  (((
189 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.
... ... @@ -192,16 +192,15 @@
192 192  
193 193  [[image:image-20220709092052-2.png]]
194 194  
201 +**Connection:**
195 195  
196 -(% style="color:blue" %)**Connection:**
203 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
197 197  
198 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
205 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
207 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
203 203  
204 -
205 205  In the PC, use below serial tool settings:
206 206  
207 207  * Baud:  (% style="color:green" %)**9600**
... ... @@ -216,18 +216,17 @@
216 216  
217 217  [[image:1657329814315-101.png]]
218 218  
219 -
220 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]]**
225 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
222 222  )))
223 223  
224 224  
229 +
225 225  === 2.2.4 Use CoAP protocol to uplink data ===
226 226  
232 +(% 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/]]
227 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 229  
230 -
231 231  (((
232 232  **Use below commands:**
233 233  )))
... ... @@ -236,39 +236,33 @@
236 236  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
237 237  )))
238 238  * (((
239 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
243 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
240 240  )))
241 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 -
246 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
245 245  )))
246 246  
247 247  (((
248 248  For parameter description, please refer to AT command set
249 -
250 -
251 251  )))
252 252  
253 253  [[image:1657330452568-615.png]]
254 254  
255 255  
256 -
257 257  (((
258 258  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.
259 -
260 -
261 261  )))
262 262  
263 263  [[image:1657330472797-498.png]]
264 264  
265 265  
263 +
266 266  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
267 267  
268 268  
269 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
270 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
271 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
267 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
268 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
269 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
272 272  
273 273  [[image:1657330501006-241.png]]
274 274  
... ... @@ -276,16 +276,17 @@
276 276  [[image:1657330533775-472.png]]
277 277  
278 278  
277 +
279 279  === 2.2.6 Use MQTT protocol to uplink data ===
280 280  
281 281  
282 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
283 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
284 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
285 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
286 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
287 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
288 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
281 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
282 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
283 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
284 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
285 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
286 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
287 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
289 289  
290 290  [[image:1657249978444-674.png]]
291 291  
... ... @@ -298,11 +298,12 @@
298 298  )))
299 299  
300 300  
300 +
301 301  === 2.2.7 Use TCP protocol to uplink data ===
302 302  
303 303  
304 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
305 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
304 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
305 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
306 306  
307 307  [[image:image-20220709093918-1.png]]
308 308  
... ... @@ -310,114 +310,78 @@
310 310  [[image:image-20220709093918-2.png]]
311 311  
312 312  
313 +
313 313  === 2.2.8 Change Update Interval ===
314 314  
315 -
316 316  User can use below command to change the (% style="color:green" %)**uplink interval**.
317 317  
318 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
318 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
319 319  
320 320  (((
321 -
322 -
323 323  (% style="color:red" %)**NOTE:**
322 +)))
324 324  
325 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
326 -
327 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
324 +(((
325 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
328 328  )))
329 329  
330 -(% 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).**
331 331  
332 332  
333 333  == 2.3  Uplink Payload ==
334 334  
335 -=== 2.3.1  Before Firmware v1.3.2 ===
336 -
337 -
338 338  In this mode, uplink payload includes in total 14 bytes
339 339  
340 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
341 -|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)(((
334 +
335 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:450px" %)
336 +|=(% style="width: 60px;" %)(((
342 342  **Size(bytes)**
343 -)))|=(% style="width: 61px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 37px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 82px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 102px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
338 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
344 344  |(% 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"]]
345 345  
346 346  (((
347 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
342 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
348 348  )))
349 349  
350 350  
351 351  [[image:1657331036973-987.png]]
352 352  
353 -
354 -The payload is **ASCII** string, representative same HEX:
355 -
356 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
357 -
358 -**where :**
359 -
360 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
361 -
362 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
363 -
364 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
365 -
366 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
367 -
368 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
369 -
370 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
371 -
372 -
373 -=== 2.3.2  Since firmware v1.3.2 ===
374 -
375 -
376 -In this mode, uplink payload includes 69 bytes in total by default.
377 -
378 -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.
379 -
380 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:490px" %)
381 -|(% style="background-color:#d9e2f3; color:#0070c0; width:60px" %)**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**
382 -|(% 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.......
383 -
384 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
385 -
386 -[[image:image-20220908175246-1.png]]
387 -
388 -
348 +(((
389 389  The payload is ASCII string, representative same HEX:
350 +)))
390 390  
391 -**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 (%%)**
352 +(((
353 +0x72403155615900640c6c19029200 where:
354 +)))
392 392  
393 -**where:**
356 +* (((
357 +Device ID: 0x724031556159 = 724031556159
358 +)))
359 +* (((
360 +Version: 0x0064=100=1.0.0
361 +)))
394 394  
395 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
363 +* (((
364 +BAT: 0x0c6c = 3180 mV = 3.180V
365 +)))
366 +* (((
367 +Signal: 0x19 = 25
368 +)))
369 +* (((
370 +Distance: 0x0292= 658 mm
371 +)))
372 +* (((
373 +Interrupt: 0x00 = 0
396 396  
397 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
398 398  
399 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
400 400  
401 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
377 +
378 +)))
402 402  
403 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
404 -
405 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
406 -
407 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
408 -
409 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
410 -
411 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
412 -
413 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
414 -
415 -
416 416  == 2.4  Payload Explanation and Sensor Interface ==
417 417  
382 +
418 418  === 2.4.1  Device ID ===
419 419  
420 -
421 421  (((
422 422  By default, the Device ID equal to the last 6 bytes of IMEI.
423 423  )))
... ... @@ -424,12 +424,10 @@
424 424  
425 425  (((
426 426  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
427 -
428 -
429 429  )))
430 430  
431 431  (((
432 -(% style="color:blue" %)**Example :**
394 +**Example:**
433 433  )))
434 434  
435 435  (((
... ... @@ -437,25 +437,13 @@
437 437  )))
438 438  
439 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.
402 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
441 441  )))
442 442  
443 443  
444 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
445 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 456  === 2.4.2  Version Info ===
457 457  
458 -
459 459  (((
460 460  Specify the software version: 0x64=100, means firmware version 1.00.
461 461  )))
... ... @@ -465,9 +465,9 @@
465 465  )))
466 466  
467 467  
418 +
468 468  === 2.4.3  Battery Info ===
469 469  
470 -
471 471  (((
472 472  Ex1: 0x0B45 = 2885mV
473 473  )))
... ... @@ -477,9 +477,9 @@
477 477  )))
478 478  
479 479  
430 +
480 480  === 2.4.4  Signal Strength ===
481 481  
482 -
483 483  (((
484 484  NB-IoT Network signal Strength.
485 485  )))
... ... @@ -509,22 +509,29 @@
509 509  )))
510 510  
511 511  
462 +
512 512  === 2.4.5  Distance ===
513 513  
514 -
515 515  Get the distance. Flat object range 280mm - 7500mm.
516 516  
467 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
468 +
517 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(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
470 +(((
471 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
519 519  )))
473 +)))
520 520  
521 521  (((
522 522  
523 523  )))
524 524  
479 +(((
480 +
481 +)))
482 +
525 525  === 2.4.6  Digital Interrupt ===
526 526  
527 -
528 528  (((
529 529  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.
530 530  )))
... ... @@ -534,7 +534,7 @@
534 534  )))
535 535  
536 536  (((
537 -(% 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]])**.**
494 +(% 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]])**.**
538 538  )))
539 539  
540 540  
... ... @@ -542,8 +542,9 @@
542 542  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.
543 543  )))
544 544  
502 +
545 545  (((
546 -**Example:**
504 +Example:
547 547  )))
548 548  
549 549  (((
... ... @@ -555,13 +555,14 @@
555 555  )))
556 556  
557 557  
516 +
558 558  === 2.4.7  ​+5V Output ===
559 559  
560 -
561 561  (((
562 562  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
563 563  )))
564 564  
523 +
565 565  (((
566 566  The 5V output time can be controlled by AT Command.
567 567  )))
... ... @@ -575,17 +575,14 @@
575 575  )))
576 576  
577 577  
537 +
578 578  == 2.5  Downlink Payload ==
579 579  
580 -
581 581  By default, NDDS75 prints the downlink payload to console port.
582 582  
583 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
584 -|(% 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)**
585 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
586 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
587 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
542 +[[image:image-20220709100028-1.png]]
588 588  
544 +
589 589  (((
590 590  (% style="color:blue" %)**Examples:**
591 591  )))
... ... @@ -630,88 +630,121 @@
630 630  )))
631 631  
632 632  
633 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
634 634  
590 +== 2.6  ​LED Indicator ==
635 635  
636 -(% style="color:blue" %)** ➢ AT Command:**
637 637  
638 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
593 +The NDDS75 has an internal LED which is to show the status of different state.
639 639  
640 -² When min=0, and max≠0, Alarm higher than max
641 641  
642 -² When min≠0, and max=0, Alarm lower than min
596 +* 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)
597 +* Then the LED will be on for 1 second means device is boot normally.
598 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
599 +* For each uplink probe, LED will be on for 500ms.
643 643  
644 -² When min≠0 and max≠0, Alarm higher than max or lower than min
601 +(((
602 +
603 +)))
645 645  
646 646  
647 -(% style="color:blue" %)** Example:**
648 648  
649 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
607 +== 2.7  ​Firmware Change Log ==
650 650  
651 651  
652 -== 2.7  Set the number of data to be uploaded and the recording time ==
610 +Download URL & Firmware Change log
653 653  
612 +(((
613 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
614 +)))
654 654  
655 -(% style="color:blue" %)** ➢ AT Command:**
656 656  
657 -* (% 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)
658 -* (% 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.
617 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
659 659  
660 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
661 661  
662 -[[image:image-20221009001114-1.png||height="687" width="955"]]
663 663  
621 +== 2.8  ​Battery Analysis ==
664 664  
665 -== 2.8  Read or Clear cached data ==
623 +=== 2.8.1  ​Battery Type ===
666 666  
667 667  
668 -(% style="color:blue" %)** ➢ AT Command:**
626 +(((
627 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
628 +)))
669 669  
670 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
671 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
630 +(((
631 +The battery is designed to last for several years depends on the actually use environment and update interval. 
632 +)))
672 672  
673 -[[image:image-20220908175333-2.png]]
634 +(((
635 +The battery related documents as below:
636 +)))
674 674  
638 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
639 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
675 675  
676 -== 2.9  ​LED Indicator ==
642 +(((
643 +[[image:image-20220709101450-2.png]]
644 +)))
677 677  
678 678  
679 -The NDDS75 has an internal LED which is to show the status of different state.
680 680  
648 +=== 2.8.2  Power consumption Analyze ===
681 681  
682 -* 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)
683 -* Then the LED will be on for 1 second means device is boot normally.
684 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
685 -* For each uplink probe, LED will be on for 500ms.
650 +(((
651 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
652 +)))
686 686  
654 +
687 687  (((
688 -
656 +Instruction to use as below:
689 689  )))
690 690  
659 +(((
660 +(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
661 +)))
691 691  
692 -== 2.10  ​Firmware Change Log ==
693 693  
664 +(((
665 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
666 +)))
694 694  
668 +* (((
669 +Product Model
670 +)))
671 +* (((
672 +Uplink Interval
673 +)))
674 +* (((
675 +Working Mode
676 +)))
677 +
695 695  (((
696 -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]]
679 +And the Life expectation in difference case will be shown on the right.
697 697  )))
698 698  
682 +[[image:image-20220709110451-3.png]]
683 +
684 +
685 +
686 +=== 2.8.3  ​Battery Note ===
687 +
699 699  (((
700 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
689 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
701 701  )))
702 702  
703 703  
704 -== 2.11 Battery & Power Consumption ==
705 705  
694 +=== 2.8.4  Replace the battery ===
706 706  
707 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
696 +(((
697 +The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
698 +)))
708 708  
709 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
710 710  
711 711  
712 712  = 3. ​ Access NB-IoT Module =
713 713  
714 -
715 715  (((
716 716  Users can directly access the AT command set of the NB-IoT module.
717 717  )))
... ... @@ -718,107 +718,90 @@
718 718  
719 719  (((
720 720  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/]] 
721 -
722 -
723 723  )))
724 724  
725 725  [[image:1657333200519-600.png]]
726 726  
727 727  
715 +
728 728  = 4.  Using the AT Commands =
729 729  
730 730  == 4.1  Access AT Commands ==
731 731  
720 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
732 732  
733 -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]]
734 734  
723 +AT+<CMD>?  : Help on <CMD>
735 735  
736 -AT+<CMD>?  :  Help on <CMD>
725 +AT+<CMD>         : Run <CMD>
737 737  
738 -AT+<CMD>         :  Run <CMD>
727 +AT+<CMD>=<value> : Set the value
739 739  
740 -AT+<CMD>=<value> :  Set the value
729 +AT+<CMD>=?  : Get the value
741 741  
742 -AT+<CMD>=?  :  Get the value
743 743  
744 -
745 745  (% style="color:#037691" %)**General Commands**(%%)      
746 746  
747 -AT  :  Attention       
734 +AT  : Attention       
748 748  
749 -AT?  :  Short Help     
736 +AT?  : Short Help     
750 750  
751 -ATZ  :  MCU Reset    
738 +ATZ  : MCU Reset    
752 752  
753 -AT+TDC  :  Application Data Transmission Interval
740 +AT+TDC  : Application Data Transmission Interval
754 754  
755 -AT+CFG  :  Print all configurations
742 +AT+CFG  : Print all configurations
756 756  
757 -AT+CFGMOD           :  Working mode selection
744 +AT+CFGMOD           : Working mode selection
758 758  
759 -AT+INTMOD            :  Set the trigger interrupt mode
746 +AT+INTMOD            : Set the trigger interrupt mode
760 760  
761 -AT+5VT  :  Set extend the time of 5V power  
748 +AT+5VT  : Set extend the time of 5V power  
762 762  
763 -AT+PRO  :  Choose agreement
750 +AT+PRO  : Choose agreement
764 764  
765 -AT+WEIGRE  :  Get weight or set weight to 0
752 +AT+WEIGRE  : Get weight or set weight to 0
766 766  
767 -AT+WEIGAP  :  Get or Set the GapValue of weight
754 +AT+WEIGAP  : Get or Set the GapValue of weight
768 768  
769 -AT+RXDL  :  Extend the sending and receiving time
756 +AT+RXDL  : Extend the sending and receiving time
770 770  
771 -AT+CNTFAC  :  Get or set counting parameters
758 +AT+CNTFAC  : Get or set counting parameters
772 772  
773 -AT+SERVADDR  :  Server Address
760 +AT+SERVADDR  : Server Address
774 774  
775 -AT+TR  :  Get or Set record time"
776 776  
777 -AT+APN     :  Get or set the APN
778 -
779 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
780 -
781 -AT+DNSCFG  : Get or Set DNS Server
782 -
783 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
784 -
785 -AT+NOUD  :  Get or Set the number of data to be uploaded
786 -
787 -AT+CDP     :  Read or Clear cached data
788 -
789 -AT+LDDSALARM :  Get or Set alarm of distance
790 -
791 -
792 792  (% style="color:#037691" %)**COAP Management**      
793 793  
794 -AT+URI            :  Resource parameters
765 +AT+URI            : Resource parameters
795 795  
796 796  
797 797  (% style="color:#037691" %)**UDP Management**
798 798  
799 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
770 +AT+CFM          : Upload confirmation mode (only valid for UDP)
800 800  
801 801  
802 802  (% style="color:#037691" %)**MQTT Management**
803 803  
804 -AT+CLIENT  :  Get or Set MQTT client
775 +AT+CLIENT               : Get or Set MQTT client
805 805  
806 -AT+UNAME  :  Get or Set MQTT Username
777 +AT+UNAME  : Get or Set MQTT Username
807 807  
808 -AT+PWD  :  Get or Set MQTT password
779 +AT+PWD                  : Get or Set MQTT password
809 809  
810 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
781 +AT+PUBTOPIC  : Get or Set MQTT publish topic
811 811  
812 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
783 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
813 813  
814 814  
815 815  (% style="color:#037691" %)**Information**          
816 816  
817 -AT+FDR  :  Factory Data Reset
788 +AT+FDR  : Factory Data Reset
818 818  
819 -AT+PWORD  :  Serial Access Password
790 +AT+PWORD  : Serial Access Password
820 820  
821 821  
793 +
822 822  = ​5.  FAQ =
823 823  
824 824  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -833,10 +833,11 @@
833 833  )))
834 834  
835 835  (((
836 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
808 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
837 837  )))
838 838  
839 839  
812 +
840 840  = 6.  Trouble Shooting =
841 841  
842 842  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -851,20 +851,16 @@
851 851  
852 852  )))
853 853  
827 +
854 854  == 6.2  AT Command input doesn't work ==
855 855  
856 -
857 857  (((
858 858  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.
832 +
833 +
859 859  )))
860 860  
861 861  
862 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
863 -
864 -
865 -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]]//**.
866 -
867 -
868 868  = 7. ​ Order Info =
869 869  
870 870  
... ... @@ -871,6 +871,11 @@
871 871  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
872 872  
873 873  
843 +(% class="wikigeneratedid" %)
844 +(((
845 +
846 +)))
847 +
874 874  = 8.  Packing Info =
875 875  
876 876  (((
... ... @@ -878,7 +878,7 @@
878 878  
879 879  (% style="color:#037691" %)**Package Includes**:
880 880  
881 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
855 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
882 882  * External antenna x 1
883 883  )))
884 884  
... ... @@ -887,6 +887,7 @@
887 887  
888 888  (% style="color:#037691" %)**Dimension and weight**:
889 889  
864 +
890 890  * Device Size: 13.0 x 5 x 4.5 cm
891 891  * Device Weight: 150g
892 892  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -896,12 +896,11 @@
896 896  (((
897 897  
898 898  
874 +
899 899  
900 900  )))
901 901  
902 902  = 9.  Support =
903 903  
904 -
905 905  * 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.
906 -
907 907  * 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]]
image-20220908175246-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -55.7 KB
Content
image-20220908175333-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -31.1 KB
Content
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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