Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.20 >
edited by Xiaoling
on 2023/05/25 14:59
To version < 97.19 >
edited by Xiaoling
on 2022/07/09 13:53
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,9 +53,9 @@
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
56 +
56 56  == 1.2 ​ Features ==
57 57  
58 -
59 59  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
60 60  * Ultra low power consumption
61 61  * Distance Detection by Ultrasonic technology
... ... @@ -70,6 +70,7 @@
70 70  * 8500mAh Battery for long term use
71 71  
72 72  
73 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -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
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 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
... ... @@ -101,9 +101,9 @@
101 101  * Max transmit power: 350mA@3.3v
102 102  
103 103  
105 +
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  
125 +
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  
149 +
148 148  == 2.2 ​ Configure the NDDS75 ==
149 149  
152 +
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.
160 +* 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.
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
163 163  )))
164 164  
165 165  
... ... @@ -166,9 +166,9 @@
166 166  [[image:1657328756309-230.png]]
167 167  
168 168  
171 +
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  
186 +
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  
197 +**Connection:**
195 195  
196 -(% style="color:blue" %)**Connection:**
199 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
197 197  
198 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
201 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
203 + (% 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]]**
221 +(% 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  
225 +
225 225  === 2.2.4 Use CoAP protocol to uplink data ===
226 226  
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/]]
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,40 +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
239 +(% 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 -
245 -
242 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
246 246  )))
247 247  
248 248  (((
249 249  For parameter description, please refer to AT command set
250 -
251 -
252 252  )))
253 253  
254 254  [[image:1657330452568-615.png]]
255 255  
256 256  
257 -
258 258  (((
259 259  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.
260 -
261 -
262 262  )))
263 263  
264 264  [[image:1657330472797-498.png]]
265 265  
266 266  
259 +
267 267  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
268 268  
269 269  
270 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
271 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
272 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
263 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
264 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
265 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
273 273  
274 274  [[image:1657330501006-241.png]]
275 275  
... ... @@ -277,16 +277,17 @@
277 277  [[image:1657330533775-472.png]]
278 278  
279 279  
273 +
280 280  === 2.2.6 Use MQTT protocol to uplink data ===
281 281  
282 282  
283 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
285 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
286 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
287 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
288 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
289 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
277 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
278 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
279 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
280 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
281 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
282 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
283 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
290 290  
291 291  [[image:1657249978444-674.png]]
292 292  
... ... @@ -299,11 +299,12 @@
299 299  )))
300 300  
301 301  
296 +
302 302  === 2.2.7 Use TCP protocol to uplink data ===
303 303  
304 304  
305 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
306 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
300 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
301 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
307 307  
308 308  [[image:image-20220709093918-1.png]]
309 309  
... ... @@ -311,115 +311,78 @@
311 311  [[image:image-20220709093918-2.png]]
312 312  
313 313  
309 +
314 314  === 2.2.8 Change Update Interval ===
315 315  
316 -
317 317  User can use below command to change the (% style="color:green" %)**uplink interval**.
318 318  
319 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
314 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
320 320  
321 321  (((
322 -
323 -
324 -
325 325  (% style="color:red" %)**NOTE:**
318 +)))
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:**
320 +(((
321 +(% 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" %)(((
330 +
331 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
332 +|=(% 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**
334 +)))|=(% 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.
338 +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 -=== 2.3.2  Since firmware v1.3.2 ===
376 -
377 -
378 -In this mode, uplink payload includes 69 bytes in total by default.
379 -
380 -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.
381 -
382 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)
383 -|=(% 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**
384 -|=(% 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.......
385 -
386 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
387 -
388 -[[image:image-20220908175246-1.png]]
389 -
390 -
344 +(((
391 391  The payload is ASCII string, representative same HEX:
346 +)))
392 392  
393 -**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 (%%)**
348 +(((
349 +0x72403155615900640c6c19029200 where:
350 +)))
394 394  
395 -**where:**
352 +* (((
353 +Device ID: 0x724031556159 = 724031556159
354 +)))
355 +* (((
356 +Version: 0x0064=100=1.0.0
357 +)))
396 396  
397 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
359 +* (((
360 +BAT: 0x0c6c = 3180 mV = 3.180V
361 +)))
362 +* (((
363 +Signal: 0x19 = 25
364 +)))
365 +* (((
366 +Distance: 0x0292= 658 mm
367 +)))
368 +* (((
369 +Interrupt: 0x00 = 0
398 398  
399 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
400 400  
401 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
402 402  
403 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
373 +
374 +)))
404 404  
405 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
406 -
407 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
408 -
409 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
410 -
411 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
412 -
413 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
414 -
415 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
416 -
417 -
418 418  == 2.4  Payload Explanation and Sensor Interface ==
419 419  
378 +
420 420  === 2.4.1  Device ID ===
421 421  
422 -
423 423  (((
424 424  By default, the Device ID equal to the last 6 bytes of IMEI.
425 425  )))
... ... @@ -426,12 +426,10 @@
426 426  
427 427  (((
428 428  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
429 -
430 -
431 431  )))
432 432  
433 433  (((
434 -(% style="color:blue" %)**Example :**
390 +**Example:**
435 435  )))
436 436  
437 437  (((
... ... @@ -439,25 +439,13 @@
439 439  )))
440 440  
441 441  (((
442 -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.
398 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
443 443  )))
444 444  
445 445  
446 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
447 447  
448 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
449 -
450 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
451 -
452 -
453 -(% style="color:blue" %)**Example :**
454 -
455 -AT+DEUI=868411056754138
456 -
457 -
458 458  === 2.4.2  Version Info ===
459 459  
460 -
461 461  (((
462 462  Specify the software version: 0x64=100, means firmware version 1.00.
463 463  )))
... ... @@ -467,9 +467,9 @@
467 467  )))
468 468  
469 469  
414 +
470 470  === 2.4.3  Battery Info ===
471 471  
472 -
473 473  (((
474 474  Ex1: 0x0B45 = 2885mV
475 475  )))
... ... @@ -479,9 +479,9 @@
479 479  )))
480 480  
481 481  
426 +
482 482  === 2.4.4  Signal Strength ===
483 483  
484 -
485 485  (((
486 486  NB-IoT Network signal Strength.
487 487  )))
... ... @@ -511,9 +511,9 @@
511 511  )))
512 512  
513 513  
458 +
514 514  === 2.4.5  Distance ===
515 515  
516 -
517 517  Get the distance. Flat object range 280mm - 7500mm.
518 518  
519 519  (((
... ... @@ -530,9 +530,12 @@
530 530  
531 531  )))
532 532  
477 +(((
478 +
479 +)))
480 +
533 533  === 2.4.6  Digital Interrupt ===
534 534  
535 -
536 536  (((
537 537  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.
538 538  )))
... ... @@ -542,7 +542,7 @@
542 542  )))
543 543  
544 544  (((
545 -(% 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]])**.**
492 +(% 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]])**.**
546 546  )))
547 547  
548 548  
... ... @@ -564,9 +564,9 @@
564 564  )))
565 565  
566 566  
514 +
567 567  === 2.4.7  ​+5V Output ===
568 568  
569 -
570 570  (((
571 571  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
572 572  )))
... ... @@ -574,14 +574,10 @@
574 574  
575 575  (((
576 576  The 5V output time can be controlled by AT Command.
577 -
578 -
579 579  )))
580 580  
581 581  (((
582 582  (% style="color:blue" %)**AT+5VT=1000**
583 -
584 -
585 585  )))
586 586  
587 587  (((
... ... @@ -589,17 +589,14 @@
589 589  )))
590 590  
591 591  
535 +
592 592  == 2.5  Downlink Payload ==
593 593  
594 -
595 595  By default, NDDS75 prints the downlink payload to console port.
596 596  
597 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
598 -|(% 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)**
599 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
600 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
601 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
540 +[[image:image-20220709100028-1.png]]
602 602  
542 +
603 603  (((
604 604  (% style="color:blue" %)**Examples:**
605 605  )))
... ... @@ -644,88 +644,125 @@
644 644  )))
645 645  
646 646  
647 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
648 648  
588 +== 2.6  ​LED Indicator ==
649 649  
650 -(% style="color:blue" %)** ➢ AT Command:**
651 651  
652 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
591 +The NDDS75 has an internal LED which is to show the status of different state.
653 653  
654 -² When min=0, and max≠0, Alarm higher than max
655 655  
656 -² When min≠0, and max=0, Alarm lower than min
594 +* 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)
595 +* Then the LED will be on for 1 second means device is boot normally.
596 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
597 +* For each uplink probe, LED will be on for 500ms.
657 657  
658 -² When min≠0 and max≠0, Alarm higher than max or lower than min
599 +(((
600 +
601 +)))
659 659  
660 660  
661 -(% style="color:blue" %)** Example:**
662 662  
663 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
605 +== 2.7  ​Firmware Change Log ==
664 664  
665 665  
666 -== 2.7  Set the number of data to be uploaded and the recording time ==
608 +(((
609 +Download URL & Firmware Change log
610 +)))
667 667  
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 +)))
668 668  
669 -(% style="color:blue" %)** ➢ AT Command:**
670 670  
671 -* (% 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)
672 -* (% 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 +(((
618 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
619 +)))
673 673  
674 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
675 675  
676 -[[image:image-20221009001114-1.png||height="687" width="955"]]
677 677  
623 +== 2.8  ​Battery Analysis ==
678 678  
679 -== 2.8  Read or Clear cached data ==
625 +=== 2.8.1  ​Battery Type ===
680 680  
681 681  
682 -(% style="color:blue" %)** ➢ AT Command:**
628 +(((
629 +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.
630 +)))
683 683  
684 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
685 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
632 +(((
633 +The battery is designed to last for several years depends on the actually use environment and update interval. 
634 +)))
686 686  
687 -[[image:image-20220908175333-2.png]]
636 +(((
637 +The battery related documents as below:
638 +)))
688 688  
640 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
641 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
642 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
689 689  
690 -== 2.9  ​LED Indicator ==
644 +(((
645 +[[image:image-20220709101450-2.png]]
646 +)))
691 691  
692 692  
693 -The NDDS75 has an internal LED which is to show the status of different state.
694 694  
650 +=== 2.8.2  Power consumption Analyze ===
695 695  
696 -* 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)
697 -* Then the LED will be on for 1 second means device is boot normally.
698 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
699 -* For each uplink probe, LED will be on for 500ms.
652 +(((
653 +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.
654 +)))
700 700  
656 +
701 701  (((
702 -
658 +Instruction to use as below:
703 703  )))
704 704  
661 +(((
662 +(% 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/]]
663 +)))
705 705  
706 -== 2.10  ​Firmware Change Log ==
707 707  
666 +(((
667 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
668 +)))
708 708  
670 +* (((
671 +Product Model
672 +)))
673 +* (((
674 +Uplink Interval
675 +)))
676 +* (((
677 +Working Mode
678 +)))
679 +
709 709  (((
710 -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]]
681 +And the Life expectation in difference case will be shown on the right.
711 711  )))
712 712  
684 +[[image:image-20220709110451-3.png]]
685 +
686 +
687 +
688 +=== 2.8.3  ​Battery Note ===
689 +
713 713  (((
714 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
691 +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.
715 715  )))
716 716  
717 717  
718 -== 2.11 Battery & Power Consumption ==
719 719  
696 +=== 2.8.4  Replace the battery ===
720 720  
721 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
698 +(((
699 +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).
700 +)))
722 722  
723 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
724 724  
725 725  
726 726  = 3. ​ Access NB-IoT Module =
727 727  
728 -
729 729  (((
730 730  Users can directly access the AT command set of the NB-IoT module.
731 731  )))
... ... @@ -732,107 +732,90 @@
732 732  
733 733  (((
734 734  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/]] 
735 -
736 -
737 737  )))
738 738  
739 739  [[image:1657333200519-600.png]]
740 740  
741 741  
717 +
742 742  = 4.  Using the AT Commands =
743 743  
744 744  == 4.1  Access AT Commands ==
745 745  
722 +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/]]
746 746  
747 -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]]
748 748  
725 +AT+<CMD>?  : Help on <CMD>
749 749  
750 -AT+<CMD>?  :  Help on <CMD>
727 +AT+<CMD>         : Run <CMD>
751 751  
752 -AT+<CMD>         :  Run <CMD>
729 +AT+<CMD>=<value> : Set the value
753 753  
754 -AT+<CMD>=<value> :  Set the value
731 +AT+<CMD>=?  : Get the value
755 755  
756 -AT+<CMD>=?  :  Get the value
757 757  
758 -
759 759  (% style="color:#037691" %)**General Commands**(%%)      
760 760  
761 -AT  :  Attention       
736 +AT  : Attention       
762 762  
763 -AT?  :  Short Help     
738 +AT?  : Short Help     
764 764  
765 -ATZ  :  MCU Reset    
740 +ATZ  : MCU Reset    
766 766  
767 -AT+TDC  :  Application Data Transmission Interval
742 +AT+TDC  : Application Data Transmission Interval
768 768  
769 -AT+CFG  :  Print all configurations
744 +AT+CFG  : Print all configurations
770 770  
771 -AT+CFGMOD           :  Working mode selection
746 +AT+CFGMOD           : Working mode selection
772 772  
773 -AT+INTMOD            :  Set the trigger interrupt mode
748 +AT+INTMOD            : Set the trigger interrupt mode
774 774  
775 -AT+5VT  :  Set extend the time of 5V power  
750 +AT+5VT  : Set extend the time of 5V power  
776 776  
777 -AT+PRO  :  Choose agreement
752 +AT+PRO  : Choose agreement
778 778  
779 -AT+WEIGRE  :  Get weight or set weight to 0
754 +AT+WEIGRE  : Get weight or set weight to 0
780 780  
781 -AT+WEIGAP  :  Get or Set the GapValue of weight
756 +AT+WEIGAP  : Get or Set the GapValue of weight
782 782  
783 -AT+RXDL  :  Extend the sending and receiving time
758 +AT+RXDL  : Extend the sending and receiving time
784 784  
785 -AT+CNTFAC  :  Get or set counting parameters
760 +AT+CNTFAC  : Get or set counting parameters
786 786  
787 -AT+SERVADDR  :  Server Address
762 +AT+SERVADDR  : Server Address
788 788  
789 -AT+TR  :  Get or Set record time"
790 790  
791 -AT+APN     :  Get or set the APN
792 -
793 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
794 -
795 -AT+DNSCFG  : Get or Set DNS Server
796 -
797 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
798 -
799 -AT+NOUD  :  Get or Set the number of data to be uploaded
800 -
801 -AT+CDP     :  Read or Clear cached data
802 -
803 -AT+LDDSALARM :  Get or Set alarm of distance
804 -
805 -
806 806  (% style="color:#037691" %)**COAP Management**      
807 807  
808 -AT+URI            :  Resource parameters
767 +AT+URI            : Resource parameters
809 809  
810 810  
811 811  (% style="color:#037691" %)**UDP Management**
812 812  
813 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
772 +AT+CFM          : Upload confirmation mode (only valid for UDP)
814 814  
815 815  
816 816  (% style="color:#037691" %)**MQTT Management**
817 817  
818 -AT+CLIENT  :  Get or Set MQTT client
777 +AT+CLIENT               : Get or Set MQTT client
819 819  
820 -AT+UNAME  :  Get or Set MQTT Username
779 +AT+UNAME  : Get or Set MQTT Username
821 821  
822 -AT+PWD  :  Get or Set MQTT password
781 +AT+PWD                  : Get or Set MQTT password
823 823  
824 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
783 +AT+PUBTOPIC  : Get or Set MQTT publish topic
825 825  
826 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
785 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
827 827  
828 828  
829 829  (% style="color:#037691" %)**Information**          
830 830  
831 -AT+FDR  :  Factory Data Reset
790 +AT+FDR  : Factory Data Reset
832 832  
833 -AT+PWORD  :  Serial Access Password
792 +AT+PWORD  : Serial Access Password
834 834  
835 835  
795 +
836 836  = ​5.  FAQ =
837 837  
838 838  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -847,10 +847,11 @@
847 847  )))
848 848  
849 849  (((
850 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
810 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
851 851  )))
852 852  
853 853  
814 +
854 854  = 6.  Trouble Shooting =
855 855  
856 856  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -865,20 +865,16 @@
865 865  
866 866  )))
867 867  
829 +
868 868  == 6.2  AT Command input doesn't work ==
869 869  
870 -
871 871  (((
872 872  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.
834 +
835 +
873 873  )))
874 874  
875 875  
876 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
877 -
878 -
879 -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]]//**.
880 -
881 -
882 882  = 7. ​ Order Info =
883 883  
884 884  
... ... @@ -885,6 +885,11 @@
885 885  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
886 886  
887 887  
845 +(% class="wikigeneratedid" %)
846 +(((
847 +
848 +)))
849 +
888 888  = 8.  Packing Info =
889 889  
890 890  (((
... ... @@ -892,7 +892,7 @@
892 892  
893 893  (% style="color:#037691" %)**Package Includes**:
894 894  
895 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
857 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
896 896  * External antenna x 1
897 897  )))
898 898  
... ... @@ -901,6 +901,7 @@
901 901  
902 902  (% style="color:#037691" %)**Dimension and weight**:
903 903  
866 +
904 904  * Device Size: 13.0 x 5 x 4.5 cm
905 905  * Device Weight: 150g
906 906  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -910,12 +910,11 @@
910 910  (((
911 911  
912 912  
876 +
913 913  
914 914  )))
915 915  
916 916  = 9.  Support =
917 917  
918 -
919 919  * 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.
920 -
921 921  * 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