Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.21 >
edited by Xiaoling
on 2023/05/25 15:09
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
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  
... ... @@ -70,7 +70,6 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
73 -
74 74  == 1.3  Specification ==
75 75  
76 76  
... ... @@ -81,12 +81,12 @@
81 81  
82 82  (% style="color:#037691" %)**NB-IoT Spec:**
83 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
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
90 90  
91 91  (% style="color:#037691" %)**Battery:**
92 92  
... ... @@ -102,10 +102,8 @@
102 102  * Max transmit power: 350mA@3.3v
103 103  
104 104  
105 -
106 106  == ​1.4  Applications ==
107 107  
108 -
109 109  * Smart Buildings & Home Automation
110 110  * Logistics and Supply Chain Management
111 111  * Smart Metering
... ... @@ -123,11 +123,11 @@
123 123  [[image:1657328609906-564.png]]
124 124  
125 125  
129 +
126 126  = 2.  Use NDDS75 to communicate with IoT Server =
127 127  
128 128  == 2.1  How it works ==
129 129  
130 -
131 131  (((
132 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 133  )))
... ... @@ -147,21 +147,22 @@
147 147  
148 148  )))
149 149  
153 +
150 150  == 2.2 ​ Configure the NDDS75 ==
151 151  
156 +
152 152  === 2.2.1 Test Requirement ===
153 153  
154 -
155 155  (((
156 156  To use NDDS75 in your city, make sure meet below requirements:
157 157  )))
158 158  
159 159  * Your local operator has already distributed a NB-IoT Network there.
160 -* The local NB-IoT network used the band that NDDS75 supports.
164 +* The local NB-IoT network used the band that NSE01 supports.
161 161  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
162 162  
163 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.
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
165 165  )))
166 166  
167 167  
... ... @@ -168,9 +168,9 @@
168 168  [[image:1657328756309-230.png]]
169 169  
170 170  
175 +
171 171  === 2.2.2 Insert SIM card ===
172 172  
173 -
174 174  (((
175 175  Insert the NB-IoT Card get from your provider.
176 176  )))
... ... @@ -183,9 +183,9 @@
183 183  [[image:1657328884227-504.png]]
184 184  
185 185  
190 +
186 186  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
187 187  
188 -
189 189  (((
190 190  (((
191 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.
... ... @@ -194,16 +194,15 @@
194 194  
195 195  [[image:image-20220709092052-2.png]]
196 196  
201 +**Connection:**
197 197  
198 -(% style="color:blue" %)**Connection:**
203 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 199  
200 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
205 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 201  
202 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
207 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
203 203  
204 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
205 205  
206 -
207 207  In the PC, use below serial tool settings:
208 208  
209 209  * Baud:  (% style="color:green" %)**9600**
... ... @@ -218,18 +218,17 @@
218 218  
219 219  [[image:1657329814315-101.png]]
220 220  
221 -
222 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]]**
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/]]
224 224  )))
225 225  
226 226  
229 +
227 227  === 2.2.4 Use CoAP protocol to uplink data ===
228 228  
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/]]
229 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 231  
232 -
233 233  (((
234 234  **Use below commands:**
235 235  )))
... ... @@ -238,39 +238,33 @@
238 238  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
239 239  )))
240 240  * (((
241 -(% 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
242 242  )))
243 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 -
246 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
247 247  )))
248 248  
249 249  (((
250 250  For parameter description, please refer to AT command set
251 -
252 -
253 253  )))
254 254  
255 255  [[image:1657330452568-615.png]]
256 256  
257 257  
258 -
259 259  (((
260 260  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.
261 -
262 -
263 263  )))
264 264  
265 265  [[image:1657330472797-498.png]]
266 266  
267 267  
263 +
268 268  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
269 269  
270 270  
271 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
272 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
273 -* (% 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
274 274  
275 275  [[image:1657330501006-241.png]]
276 276  
... ... @@ -278,16 +278,17 @@
278 278  [[image:1657330533775-472.png]]
279 279  
280 280  
277 +
281 281  === 2.2.6 Use MQTT protocol to uplink data ===
282 282  
283 283  
284 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
285 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
286 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
287 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
288 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
289 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
290 -* (% 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
291 291  
292 292  [[image:1657249978444-674.png]]
293 293  
... ... @@ -300,11 +300,12 @@
300 300  )))
301 301  
302 302  
300 +
303 303  === 2.2.7 Use TCP protocol to uplink data ===
304 304  
305 305  
306 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
307 -* (% 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
308 308  
309 309  [[image:image-20220709093918-1.png]]
310 310  
... ... @@ -312,116 +312,78 @@
312 312  [[image:image-20220709093918-2.png]]
313 313  
314 314  
313 +
315 315  === 2.2.8 Change Update Interval ===
316 316  
317 -
318 318  User can use below command to change the (% style="color:green" %)**uplink interval**.
319 319  
320 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
318 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
321 321  
322 322  (((
323 -
324 -
325 325  (% style="color:red" %)**NOTE:**
322 +)))
326 326  
327 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
328 -
329 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
324 +(((
325 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
330 330  )))
331 331  
332 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
333 333  
334 334  
335 335  == 2.3  Uplink Payload ==
336 336  
337 -=== 2.3.1  Before Firmware v1.3.2 ===
338 -
339 -
340 340  In this mode, uplink payload includes in total 14 bytes
341 341  
342 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:440px" %)
343 -|=(% 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;" %)(((
344 344  **Size(bytes)**
345 -)))|=(% 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**
346 346  |(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
347 347  
348 348  (((
349 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
342 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
350 350  )))
351 351  
352 352  
353 353  [[image:1657331036973-987.png]]
354 354  
355 -
356 -The payload is **ASCII** string, representative same HEX:
357 -
358 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
359 -
360 -**where :**
361 -
362 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
363 -
364 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
365 -
366 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
367 -
368 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
369 -
370 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
371 -
372 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
373 -
374 -
375 -
376 -=== 2.3.2  Since firmware v1.3.2 ===
377 -
378 -
379 -In this mode, uplink payload includes 69 bytes in total by default.
380 -
381 -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.
382 -
383 -(% border="1" cellspacing="5" style="background-color:#f2f2f2; width:490px" %)
384 -|(% 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**
385 -|(% 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.......
386 -
387 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
388 -
389 -[[image:image-20220908175246-1.png]]
390 -
391 -
348 +(((
392 392  The payload is ASCII string, representative same HEX:
350 +)))
393 393  
394 -**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 +)))
395 395  
396 -**where:**
356 +* (((
357 +Device ID: 0x724031556159 = 724031556159
358 +)))
359 +* (((
360 +Version: 0x0064=100=1.0.0
361 +)))
397 397  
398 -* (% 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
399 399  
400 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
401 401  
402 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
403 403  
404 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
377 +
378 +)))
405 405  
406 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
407 -
408 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
409 -
410 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
411 -
412 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
413 -
414 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
415 -
416 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
417 -
418 -
419 -
420 420  == 2.4  Payload Explanation and Sensor Interface ==
421 421  
382 +
422 422  === 2.4.1  Device ID ===
423 423  
424 -
425 425  (((
426 426  By default, the Device ID equal to the last 6 bytes of IMEI.
427 427  )))
... ... @@ -428,12 +428,10 @@
428 428  
429 429  (((
430 430  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
431 -
432 -
433 433  )))
434 434  
435 435  (((
436 -(% style="color:blue" %)**Example :**
394 +**Example:**
437 437  )))
438 438  
439 439  (((
... ... @@ -441,25 +441,13 @@
441 441  )))
442 442  
443 443  (((
444 -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.
445 445  )))
446 446  
447 447  
448 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
449 449  
450 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
451 -
452 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
453 -
454 -
455 -(% style="color:blue" %)**Example :**
456 -
457 -AT+DEUI=868411056754138
458 -
459 -
460 460  === 2.4.2  Version Info ===
461 461  
462 -
463 463  (((
464 464  Specify the software version: 0x64=100, means firmware version 1.00.
465 465  )))
... ... @@ -469,9 +469,9 @@
469 469  )))
470 470  
471 471  
418 +
472 472  === 2.4.3  Battery Info ===
473 473  
474 -
475 475  (((
476 476  Ex1: 0x0B45 = 2885mV
477 477  )))
... ... @@ -481,9 +481,9 @@
481 481  )))
482 482  
483 483  
430 +
484 484  === 2.4.4  Signal Strength ===
485 485  
486 -
487 487  (((
488 488  NB-IoT Network signal Strength.
489 489  )))
... ... @@ -513,22 +513,29 @@
513 513  )))
514 514  
515 515  
462 +
516 516  === 2.4.5  Distance ===
517 517  
518 -
519 519  Get the distance. Flat object range 280mm - 7500mm.
520 520  
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 +
521 521  (((
522 -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.**
523 523  )))
473 +)))
524 524  
525 525  (((
526 526  
527 527  )))
528 528  
479 +(((
480 +
481 +)))
482 +
529 529  === 2.4.6  Digital Interrupt ===
530 530  
531 -
532 532  (((
533 533  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.
534 534  )))
... ... @@ -538,7 +538,7 @@
538 538  )))
539 539  
540 540  (((
541 -(% 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]])**.**
542 542  )))
543 543  
544 544  
... ... @@ -546,8 +546,9 @@
546 546  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.
547 547  )))
548 548  
502 +
549 549  (((
550 -**Example:**
504 +Example:
551 551  )))
552 552  
553 553  (((
... ... @@ -559,13 +559,14 @@
559 559  )))
560 560  
561 561  
516 +
562 562  === 2.4.7  ​+5V Output ===
563 563  
564 -
565 565  (((
566 566  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
567 567  )))
568 568  
523 +
569 569  (((
570 570  The 5V output time can be controlled by AT Command.
571 571  )))
... ... @@ -579,17 +579,14 @@
579 579  )))
580 580  
581 581  
537 +
582 582  == 2.5  Downlink Payload ==
583 583  
584 -
585 585  By default, NDDS75 prints the downlink payload to console port.
586 586  
587 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
588 -|(% 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)**
589 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
590 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
591 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
542 +[[image:image-20220709100028-1.png]]
592 592  
544 +
593 593  (((
594 594  (% style="color:blue" %)**Examples:**
595 595  )))
... ... @@ -634,88 +634,121 @@
634 634  )))
635 635  
636 636  
637 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
638 638  
590 +== 2.6  ​LED Indicator ==
639 639  
640 -(% style="color:blue" %)** ➢ AT Command:**
641 641  
642 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
593 +The NDDS75 has an internal LED which is to show the status of different state.
643 643  
644 -² When min=0, and max≠0, Alarm higher than max
645 645  
646 -² 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.
647 647  
648 -² When min≠0 and max≠0, Alarm higher than max or lower than min
601 +(((
602 +
603 +)))
649 649  
650 650  
651 -(% style="color:blue" %)** Example:**
652 652  
653 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
607 +== 2.7  ​Firmware Change Log ==
654 654  
655 655  
656 -== 2.7  Set the number of data to be uploaded and the recording time ==
610 +Download URL & Firmware Change log
657 657  
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 +)))
658 658  
659 -(% style="color:blue" %)** ➢ AT Command:**
660 660  
661 -* (% 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)
662 -* (% 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"]]
663 663  
664 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
665 665  
666 -[[image:image-20221009001114-1.png||height="687" width="955"]]
667 667  
621 +== 2.8  ​Battery Analysis ==
668 668  
669 -== 2.8  Read or Clear cached data ==
623 +=== 2.8.1  ​Battery Type ===
670 670  
671 671  
672 -(% 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 +)))
673 673  
674 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
675 -* (% 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 +)))
676 676  
677 -[[image:image-20220908175333-2.png]]
634 +(((
635 +The battery related documents as below:
636 +)))
678 678  
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/]]
679 679  
680 -== 2.9  ​LED Indicator ==
642 +(((
643 +[[image:image-20220709101450-2.png]]
644 +)))
681 681  
682 682  
683 -The NDDS75 has an internal LED which is to show the status of different state.
684 684  
648 +=== 2.8.2  Power consumption Analyze ===
685 685  
686 -* 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)
687 -* Then the LED will be on for 1 second means device is boot normally.
688 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
689 -* 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 +)))
690 690  
654 +
691 691  (((
692 -
656 +Instruction to use as below:
693 693  )))
694 694  
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 +)))
695 695  
696 -== 2.10  ​Firmware Change Log ==
697 697  
664 +(((
665 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
666 +)))
698 698  
668 +* (((
669 +Product Model
670 +)))
671 +* (((
672 +Uplink Interval
673 +)))
674 +* (((
675 +Working Mode
676 +)))
677 +
699 699  (((
700 -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.
701 701  )))
702 702  
682 +[[image:image-20220709110451-3.png]]
683 +
684 +
685 +
686 +=== 2.8.3  ​Battery Note ===
687 +
703 703  (((
704 -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.
705 705  )))
706 706  
707 707  
708 -== 2.11 Battery & Power Consumption ==
709 709  
694 +=== 2.8.4  Replace the battery ===
710 710  
711 -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 +)))
712 712  
713 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
714 714  
715 715  
716 716  = 3. ​ Access NB-IoT Module =
717 717  
718 -
719 719  (((
720 720  Users can directly access the AT command set of the NB-IoT module.
721 721  )))
... ... @@ -722,107 +722,90 @@
722 722  
723 723  (((
724 724  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/]] 
725 -
726 -
727 727  )))
728 728  
729 729  [[image:1657333200519-600.png]]
730 730  
731 731  
715 +
732 732  = 4.  Using the AT Commands =
733 733  
734 734  == 4.1  Access AT Commands ==
735 735  
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/]]
736 736  
737 -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]]
738 738  
723 +AT+<CMD>?  : Help on <CMD>
739 739  
740 -AT+<CMD>?  :  Help on <CMD>
725 +AT+<CMD>         : Run <CMD>
741 741  
742 -AT+<CMD>         :  Run <CMD>
727 +AT+<CMD>=<value> : Set the value
743 743  
744 -AT+<CMD>=<value> :  Set the value
729 +AT+<CMD>=?  : Get the value
745 745  
746 -AT+<CMD>=?  :  Get the value
747 747  
748 -
749 749  (% style="color:#037691" %)**General Commands**(%%)      
750 750  
751 -AT  :  Attention       
734 +AT  : Attention       
752 752  
753 -AT?  :  Short Help     
736 +AT?  : Short Help     
754 754  
755 -ATZ  :  MCU Reset    
738 +ATZ  : MCU Reset    
756 756  
757 -AT+TDC  :  Application Data Transmission Interval
740 +AT+TDC  : Application Data Transmission Interval
758 758  
759 -AT+CFG  :  Print all configurations
742 +AT+CFG  : Print all configurations
760 760  
761 -AT+CFGMOD           :  Working mode selection
744 +AT+CFGMOD           : Working mode selection
762 762  
763 -AT+INTMOD            :  Set the trigger interrupt mode
746 +AT+INTMOD            : Set the trigger interrupt mode
764 764  
765 -AT+5VT  :  Set extend the time of 5V power  
748 +AT+5VT  : Set extend the time of 5V power  
766 766  
767 -AT+PRO  :  Choose agreement
750 +AT+PRO  : Choose agreement
768 768  
769 -AT+WEIGRE  :  Get weight or set weight to 0
752 +AT+WEIGRE  : Get weight or set weight to 0
770 770  
771 -AT+WEIGAP  :  Get or Set the GapValue of weight
754 +AT+WEIGAP  : Get or Set the GapValue of weight
772 772  
773 -AT+RXDL  :  Extend the sending and receiving time
756 +AT+RXDL  : Extend the sending and receiving time
774 774  
775 -AT+CNTFAC  :  Get or set counting parameters
758 +AT+CNTFAC  : Get or set counting parameters
776 776  
777 -AT+SERVADDR  :  Server Address
760 +AT+SERVADDR  : Server Address
778 778  
779 -AT+TR  :  Get or Set record time"
780 780  
781 -AT+APN     :  Get or set the APN
782 -
783 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
784 -
785 -AT+DNSCFG  : Get or Set DNS Server
786 -
787 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
788 -
789 -AT+NOUD  :  Get or Set the number of data to be uploaded
790 -
791 -AT+CDP     :  Read or Clear cached data
792 -
793 -AT+LDDSALARM :  Get or Set alarm of distance
794 -
795 -
796 796  (% style="color:#037691" %)**COAP Management**      
797 797  
798 -AT+URI            :  Resource parameters
765 +AT+URI            : Resource parameters
799 799  
800 800  
801 801  (% style="color:#037691" %)**UDP Management**
802 802  
803 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
770 +AT+CFM          : Upload confirmation mode (only valid for UDP)
804 804  
805 805  
806 806  (% style="color:#037691" %)**MQTT Management**
807 807  
808 -AT+CLIENT  :  Get or Set MQTT client
775 +AT+CLIENT               : Get or Set MQTT client
809 809  
810 -AT+UNAME  :  Get or Set MQTT Username
777 +AT+UNAME  : Get or Set MQTT Username
811 811  
812 -AT+PWD  :  Get or Set MQTT password
779 +AT+PWD                  : Get or Set MQTT password
813 813  
814 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
781 +AT+PUBTOPIC  : Get or Set MQTT publish topic
815 815  
816 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
783 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
817 817  
818 818  
819 819  (% style="color:#037691" %)**Information**          
820 820  
821 -AT+FDR  :  Factory Data Reset
788 +AT+FDR  : Factory Data Reset
822 822  
823 -AT+PWORD  :  Serial Access Password
790 +AT+PWORD  : Serial Access Password
824 824  
825 825  
793 +
826 826  = ​5.  FAQ =
827 827  
828 828  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -837,10 +837,11 @@
837 837  )))
838 838  
839 839  (((
840 -(% 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.
841 841  )))
842 842  
843 843  
812 +
844 844  = 6.  Trouble Shooting =
845 845  
846 846  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -855,20 +855,16 @@
855 855  
856 856  )))
857 857  
827 +
858 858  == 6.2  AT Command input doesn't work ==
859 859  
860 -
861 861  (((
862 862  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 +
863 863  )))
864 864  
865 865  
866 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
867 -
868 -
869 -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]]//**.
870 -
871 -
872 872  = 7. ​ Order Info =
873 873  
874 874  
... ... @@ -875,6 +875,11 @@
875 875  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
876 876  
877 877  
843 +(% class="wikigeneratedid" %)
844 +(((
845 +
846 +)))
847 +
878 878  = 8.  Packing Info =
879 879  
880 880  (((
... ... @@ -882,7 +882,7 @@
882 882  
883 883  (% style="color:#037691" %)**Package Includes**:
884 884  
885 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
855 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
886 886  * External antenna x 1
887 887  )))
888 888  
... ... @@ -891,6 +891,7 @@
891 891  
892 892  (% style="color:#037691" %)**Dimension and weight**:
893 893  
864 +
894 894  * Device Size: 13.0 x 5 x 4.5 cm
895 895  * Device Weight: 150g
896 896  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -900,12 +900,11 @@
900 900  (((
901 901  
902 902  
874 +
903 903  
904 904  )))
905 905  
906 906  = 9.  Support =
907 907  
908 -
909 909  * 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.
910 -
911 911  * 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