Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.17 >
edited by Xiaoling
on 2023/05/17 18:20
To version < 97.17 >
edited by Xiaoling
on 2022/07/09 11:53
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -53,6 +53,7 @@
53 53  [[image:1657327959271-447.png]]
54 54  
55 55  
56 +
56 56  == 1.2 ​ Features ==
57 57  
58 58  
... ... @@ -79,12 +79,12 @@
79 79  
80 80  (% style="color:#037691" %)**NB-IoT Spec:**
81 81  
82 -* B1 @H-FDD: 2100MHz
83 -* B3 @H-FDD: 1800MHz
84 -* B8 @H-FDD: 900MHz
85 -* B5 @H-FDD: 850MHz
86 -* B20 @H-FDD: 800MHz
87 -* B28 @H-FDD: 700MHz
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
88 88  
89 89  (% style="color:#037691" %)**Battery:**
90 90  
... ... @@ -101,7 +101,6 @@
101 101  
102 102  == ​1.4  Applications ==
103 103  
104 -
105 105  * Smart Buildings & Home Automation
106 106  * Logistics and Supply Chain Management
107 107  * Smart Metering
... ... @@ -119,11 +119,11 @@
119 119  [[image:1657328609906-564.png]]
120 120  
121 121  
122 +
122 122  = 2.  Use NDDS75 to communicate with IoT Server =
123 123  
124 124  == 2.1  How it works ==
125 125  
126 -
127 127  (((
128 128  The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
129 129  )))
... ... @@ -143,21 +143,22 @@
143 143  
144 144  )))
145 145  
146 +
146 146  == 2.2 ​ Configure the NDDS75 ==
147 147  
149 +
148 148  === 2.2.1 Test Requirement ===
149 149  
150 -
151 151  (((
152 152  To use NDDS75 in your city, make sure meet below requirements:
153 153  )))
154 154  
155 155  * Your local operator has already distributed a NB-IoT Network there.
156 -* The local NB-IoT network used the band that NDDS75 supports.
157 +* The local NB-IoT network used the band that NSE01 supports.
157 157  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
158 158  
159 159  (((
160 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
161 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
161 161  )))
162 162  
163 163  
... ... @@ -164,9 +164,9 @@
164 164  [[image:1657328756309-230.png]]
165 165  
166 166  
168 +
167 167  === 2.2.2 Insert SIM card ===
168 168  
169 -
170 170  (((
171 171  Insert the NB-IoT Card get from your provider.
172 172  )))
... ... @@ -179,9 +179,9 @@
179 179  [[image:1657328884227-504.png]]
180 180  
181 181  
183 +
182 182  === 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
183 183  
184 -
185 185  (((
186 186  (((
187 187  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.
... ... @@ -190,16 +190,15 @@
190 190  
191 191  [[image:image-20220709092052-2.png]]
192 192  
194 +**Connection:**
193 193  
194 -(% style="color:blue" %)**Connection:**
196 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
195 195  
196 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
198 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
197 197  
198 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
200 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
201 201  
202 -
203 203  In the PC, use below serial tool settings:
204 204  
205 205  * Baud:  (% style="color:green" %)**9600**
... ... @@ -214,18 +214,17 @@
214 214  
215 215  [[image:1657329814315-101.png]]
216 216  
217 -
218 218  (((
219 -(% 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]]**
218 +(% 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/]]
220 220  )))
221 221  
222 222  
222 +
223 223  === 2.2.4 Use CoAP protocol to uplink data ===
224 224  
225 +(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
225 225  
226 -(% 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 -
229 229  (((
230 230  **Use below commands:**
231 231  )))
... ... @@ -234,40 +234,33 @@
234 234  (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
235 235  )))
236 236  * (((
237 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
236 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
238 238  )))
239 239  * (((
240 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
241 -
242 -
243 -
239 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
244 244  )))
245 245  
246 246  (((
247 247  For parameter description, please refer to AT command set
248 -
249 -
250 250  )))
251 251  
252 252  [[image:1657330452568-615.png]]
253 253  
254 254  
255 -
256 256  (((
257 257  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.
258 -
259 -
260 260  )))
261 261  
262 262  [[image:1657330472797-498.png]]
263 263  
264 264  
256 +
265 265  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
266 266  
267 267  
268 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
269 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
270 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
260 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
261 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
262 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
271 271  
272 272  [[image:1657330501006-241.png]]
273 273  
... ... @@ -275,16 +275,17 @@
275 275  [[image:1657330533775-472.png]]
276 276  
277 277  
270 +
278 278  === 2.2.6 Use MQTT protocol to uplink data ===
279 279  
280 280  
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
274 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
275 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
276 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
277 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
278 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
279 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
280 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
288 288  
289 289  [[image:1657249978444-674.png]]
290 290  
... ... @@ -297,11 +297,12 @@
297 297  )))
298 298  
299 299  
293 +
300 300  === 2.2.7 Use TCP protocol to uplink data ===
301 301  
302 302  
303 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
304 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
297 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
298 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
305 305  
306 306  [[image:image-20220709093918-1.png]]
307 307  
... ... @@ -309,113 +309,78 @@
309 309  [[image:image-20220709093918-2.png]]
310 310  
311 311  
306 +
312 312  === 2.2.8 Change Update Interval ===
313 313  
314 -
315 315  User can use below command to change the (% style="color:green" %)**uplink interval**.
316 316  
317 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
311 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
318 318  
319 319  (((
320 -
321 -
322 -
323 323  (% style="color:red" %)**NOTE:**
315 +)))
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:**
317 +(((
318 +(% 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: 60px;background-color:#D9E2F3;color:#0070C0" %)(((
327 +
328 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
329 +|=(% style="width: 60px;" %)(((
342 342  **Size(bytes)**
343 -)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width: 35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width: 100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**1**
331 +)))|=(% 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.
335 +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 -=== 2.3.2  Since firmware v1.3.2 ===
373 -
374 -
375 -In this mode, uplink payload includes 69 bytes in total by default.
376 -
377 -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.
378 -
379 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:490px" %)
380 -|=(% 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**
381 -|=(% 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.......
382 -
383 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
384 -
385 -[[image:image-20220908175246-1.png]]
386 -
387 -
341 +(((
388 388  The payload is ASCII string, representative same HEX:
343 +)))
389 389  
390 -**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 (%%)**
345 +(((
346 +0x72403155615900640c6c19029200 where:
347 +)))
391 391  
392 -**where:**
349 +* (((
350 +Device ID: 0x724031556159 = 724031556159
351 +)))
352 +* (((
353 +Version: 0x0064=100=1.0.0
354 +)))
393 393  
394 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
356 +* (((
357 +BAT: 0x0c6c = 3180 mV = 3.180V
358 +)))
359 +* (((
360 +Signal: 0x19 = 25
361 +)))
362 +* (((
363 +Distance: 0x0292= 658 mm
364 +)))
365 +* (((
366 +Interrupt: 0x00 = 0
395 395  
396 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
397 397  
398 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
399 399  
400 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
370 +
371 +)))
401 401  
402 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
403 -
404 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
405 -
406 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
407 -
408 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
409 -
410 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
411 -
412 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
413 -
414 414  == 2.4  Payload Explanation and Sensor Interface ==
415 415  
375 +
416 416  === 2.4.1  Device ID ===
417 417  
418 -
419 419  (((
420 420  By default, the Device ID equal to the last 6 bytes of IMEI.
421 421  )))
... ... @@ -422,12 +422,10 @@
422 422  
423 423  (((
424 424  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
425 -
426 -
427 427  )))
428 428  
429 429  (((
430 -(% style="color:blue" %)**Example :**
387 +**Example:**
431 431  )))
432 432  
433 433  (((
... ... @@ -435,25 +435,13 @@
435 435  )))
436 436  
437 437  (((
438 -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.
395 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
439 439  )))
440 440  
441 441  
442 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
443 443  
444 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
445 -
446 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
447 -
448 -
449 -(% style="color:blue" %)**Example :**
450 -
451 -AT+DEUI=868411056754138
452 -
453 -
454 454  === 2.4.2  Version Info ===
455 455  
456 -
457 457  (((
458 458  Specify the software version: 0x64=100, means firmware version 1.00.
459 459  )))
... ... @@ -463,9 +463,9 @@
463 463  )))
464 464  
465 465  
411 +
466 466  === 2.4.3  Battery Info ===
467 467  
468 -
469 469  (((
470 470  Ex1: 0x0B45 = 2885mV
471 471  )))
... ... @@ -475,9 +475,9 @@
475 475  )))
476 476  
477 477  
423 +
478 478  === 2.4.4  Signal Strength ===
479 479  
480 -
481 481  (((
482 482  NB-IoT Network signal Strength.
483 483  )))
... ... @@ -507,9 +507,9 @@
507 507  )))
508 508  
509 509  
455 +
510 510  === 2.4.5  Distance ===
511 511  
512 -
513 513  Get the distance. Flat object range 280mm - 7500mm.
514 514  
515 515  (((
... ... @@ -526,9 +526,12 @@
526 526  
527 527  )))
528 528  
474 +(((
475 +
476 +)))
477 +
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]])**.**
489 +(% 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  
... ... @@ -560,9 +560,9 @@
560 560  )))
561 561  
562 562  
511 +
563 563  === 2.4.7  ​+5V Output ===
564 564  
565 -
566 566  (((
567 567  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
568 568  )))
... ... @@ -570,14 +570,10 @@
570 570  
571 571  (((
572 572  The 5V output time can be controlled by AT Command.
573 -
574 -
575 575  )))
576 576  
577 577  (((
578 578  (% style="color:blue" %)**AT+5VT=1000**
579 -
580 -
581 581  )))
582 582  
583 583  (((
... ... @@ -585,19 +585,14 @@
585 585  )))
586 586  
587 587  
532 +
588 588  == 2.5  Downlink Payload ==
589 589  
590 -
591 591  By default, NDDS75 prints the downlink payload to console port.
592 592  
593 -(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:520px" %)
594 -|(% style="width:208px;background-color:#D9E2F3;color:#0070C0" %)**Downlink Control Type**|(% style="width:56px;background-color:#D9E2F3;color:#0070C0" %)**FPort**|(% style="width:100px;background-color:#D9E2F3;color:#0070C0" %)**Type Code**|(% style="width:154px;background-color:#D9E2F3;color:#0070C0" %)**Downlink payload size(bytes)**
595 -|(% style="width:208px" %)TDC (Transmit Time Interval)|(% style="width:56px" %)Any|(% style="width:100px" %)01|(% style="width:154px" %)4
596 -|(% style="width:208px" %)RESET|(% style="width:56px" %)Any|(% style="width:100px" %)04|(% style="width:154px" %)2
597 -|(% style="width:208px" %)INTMOD|(% style="width:56px" %)Any|(% style="width:100px" %)06|(% style="width:154px" %)4
537 +[[image:image-20220709100028-1.png]]
598 598  
599 599  
600 -
601 601  (((
602 602  (% style="color:blue" %)**Examples:**
603 603  )))
... ... @@ -642,88 +642,121 @@
642 642  )))
643 643  
644 644  
645 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
646 646  
585 +== 2.6  ​LED Indicator ==
647 647  
648 -(% style="color:blue" %)** ➢ AT Command:**
649 649  
650 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
588 +The NDDS75 has an internal LED which is to show the status of different state.
651 651  
652 -² When min=0, and max≠0, Alarm higher than max
653 653  
654 -² When min≠0, and max=0, Alarm lower than min
591 +* 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)
592 +* Then the LED will be on for 1 second means device is boot normally.
593 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
594 +* For each uplink probe, LED will be on for 500ms.
655 655  
656 -² When min≠0 and max≠0, Alarm higher than max or lower than min
596 +(((
597 +
598 +)))
657 657  
658 658  
659 -(% style="color:blue" %)** Example:**
660 660  
661 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
602 +== 2.7  ​Firmware Change Log ==
662 662  
663 663  
664 -== 2.7  Set the number of data to be uploaded and the recording time ==
605 +Download URL & Firmware Change log
665 665  
607 +(((
608 +[[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/]]
609 +)))
666 666  
667 -(% style="color:blue" %)** ➢ AT Command:**
668 668  
669 -* (% 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)
670 -* (% 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.
612 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
671 671  
672 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
673 673  
674 -[[image:image-20221009001114-1.png||height="687" width="955"]]
675 675  
616 +== 2.8  ​Battery Analysis ==
676 676  
677 -== 2.8  Read or Clear cached data ==
618 +=== 2.8.1  ​Battery Type ===
678 678  
679 679  
680 -(% style="color:blue" %)** ➢ AT Command:**
621 +(((
622 +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.
623 +)))
681 681  
682 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
683 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
625 +(((
626 +The battery is designed to last for several years depends on the actually use environment and update interval. 
627 +)))
684 684  
685 -[[image:image-20220908175333-2.png]]
629 +(((
630 +The battery related documents as below:
631 +)))
686 686  
633 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
634 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
635 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
687 687  
688 -== 2.9  ​LED Indicator ==
637 +(((
638 +[[image:image-20220709101450-2.png]]
639 +)))
689 689  
690 690  
691 -The NDDS75 has an internal LED which is to show the status of different state.
692 692  
643 +=== 2.8.2  Power consumption Analyze ===
693 693  
694 -* 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)
695 -* Then the LED will be on for 1 second means device is boot normally.
696 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
697 -* For each uplink probe, LED will be on for 500ms.
645 +(((
646 +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.
647 +)))
698 698  
649 +
699 699  (((
700 -
651 +Instruction to use as below:
701 701  )))
702 702  
654 +(((
655 +(% 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/]]
656 +)))
703 703  
704 -== 2.10  ​Firmware Change Log ==
705 705  
659 +(((
660 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
661 +)))
706 706  
663 +* (((
664 +Product Model
665 +)))
666 +* (((
667 +Uplink Interval
668 +)))
669 +* (((
670 +Working Mode
671 +)))
672 +
707 707  (((
708 -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]]
674 +And the Life expectation in difference case will be shown on the right.
709 709  )))
710 710  
677 +[[image:image-20220709110451-3.png]]
678 +
679 +
680 +
681 +=== 2.8.3  ​Battery Note ===
682 +
711 711  (((
712 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
684 +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.
713 713  )))
714 714  
715 715  
716 -== 2.11 Battery & Power Consumption ==
717 717  
689 +=== 2.8.4  Replace the battery ===
718 718  
719 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace.
691 +(((
692 +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).
693 +)))
720 720  
721 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
722 722  
723 723  
724 724  = 3. ​ Access NB-IoT Module =
725 725  
726 -
727 727  (((
728 728  Users can directly access the AT command set of the NB-IoT module.
729 729  )))
... ... @@ -730,107 +730,90 @@
730 730  
731 731  (((
732 732  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/]] 
733 -
734 -
735 735  )))
736 736  
737 737  [[image:1657333200519-600.png]]
738 738  
739 739  
710 +
740 740  = 4.  Using the AT Commands =
741 741  
742 742  == 4.1  Access AT Commands ==
743 743  
715 +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/]]
744 744  
745 -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]]
746 746  
718 +AT+<CMD>?  : Help on <CMD>
747 747  
748 -AT+<CMD>?  :  Help on <CMD>
720 +AT+<CMD>         : Run <CMD>
749 749  
750 -AT+<CMD>         :  Run <CMD>
722 +AT+<CMD>=<value> : Set the value
751 751  
752 -AT+<CMD>=<value> :  Set the value
724 +AT+<CMD>=?  : Get the value
753 753  
754 -AT+<CMD>=?  :  Get the value
755 755  
756 -
757 757  (% style="color:#037691" %)**General Commands**(%%)      
758 758  
759 -AT  :  Attention       
729 +AT  : Attention       
760 760  
761 -AT?  :  Short Help     
731 +AT?  : Short Help     
762 762  
763 -ATZ  :  MCU Reset    
733 +ATZ  : MCU Reset    
764 764  
765 -AT+TDC  :  Application Data Transmission Interval
735 +AT+TDC  : Application Data Transmission Interval
766 766  
767 -AT+CFG  :  Print all configurations
737 +AT+CFG  : Print all configurations
768 768  
769 -AT+CFGMOD           :  Working mode selection
739 +AT+CFGMOD           : Working mode selection
770 770  
771 -AT+INTMOD            :  Set the trigger interrupt mode
741 +AT+INTMOD            : Set the trigger interrupt mode
772 772  
773 -AT+5VT  :  Set extend the time of 5V power  
743 +AT+5VT  : Set extend the time of 5V power  
774 774  
775 -AT+PRO  :  Choose agreement
745 +AT+PRO  : Choose agreement
776 776  
777 -AT+WEIGRE  :  Get weight or set weight to 0
747 +AT+WEIGRE  : Get weight or set weight to 0
778 778  
779 -AT+WEIGAP  :  Get or Set the GapValue of weight
749 +AT+WEIGAP  : Get or Set the GapValue of weight
780 780  
781 -AT+RXDL  :  Extend the sending and receiving time
751 +AT+RXDL  : Extend the sending and receiving time
782 782  
783 -AT+CNTFAC  :  Get or set counting parameters
753 +AT+CNTFAC  : Get or set counting parameters
784 784  
785 -AT+SERVADDR  :  Server Address
755 +AT+SERVADDR  : Server Address
786 786  
787 -AT+TR  :  Get or Set record time"
788 788  
789 -AT+APN     :  Get or set the APN
790 -
791 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
792 -
793 -AT+DNSCFG  : Get or Set DNS Server
794 -
795 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
796 -
797 -AT+NOUD  :  Get or Set the number of data to be uploaded
798 -
799 -AT+CDP     :  Read or Clear cached data
800 -
801 -AT+LDDSALARM :  Get or Set alarm of distance
802 -
803 -
804 804  (% style="color:#037691" %)**COAP Management**      
805 805  
806 -AT+URI            :  Resource parameters
760 +AT+URI            : Resource parameters
807 807  
808 808  
809 809  (% style="color:#037691" %)**UDP Management**
810 810  
811 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
765 +AT+CFM          : Upload confirmation mode (only valid for UDP)
812 812  
813 813  
814 814  (% style="color:#037691" %)**MQTT Management**
815 815  
816 -AT+CLIENT  :  Get or Set MQTT client
770 +AT+CLIENT               : Get or Set MQTT client
817 817  
818 -AT+UNAME  :  Get or Set MQTT Username
772 +AT+UNAME  : Get or Set MQTT Username
819 819  
820 -AT+PWD  :  Get or Set MQTT password
774 +AT+PWD                  : Get or Set MQTT password
821 821  
822 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
776 +AT+PUBTOPIC  : Get or Set MQTT publish topic
823 823  
824 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
778 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
825 825  
826 826  
827 827  (% style="color:#037691" %)**Information**          
828 828  
829 -AT+FDR  :  Factory Data Reset
783 +AT+FDR  : Factory Data Reset
830 830  
831 -AT+PWORD  :  Serial Access Password
785 +AT+PWORD  : Serial Access Password
832 832  
833 833  
788 +
834 834  = ​5.  FAQ =
835 835  
836 836  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -845,10 +845,11 @@
845 845  )))
846 846  
847 847  (((
848 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
803 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
849 849  )))
850 850  
851 851  
807 +
852 852  = 6.  Trouble Shooting =
853 853  
854 854  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -863,20 +863,16 @@
863 863  
864 864  )))
865 865  
822 +
866 866  == 6.2  AT Command input doesn't work ==
867 867  
868 -
869 869  (((
870 870  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.
827 +
828 +
871 871  )))
872 872  
873 873  
874 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
875 -
876 -
877 -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]]//**.
878 -
879 -
880 880  = 7. ​ Order Info =
881 881  
882 882  
... ... @@ -883,6 +883,11 @@
883 883  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
884 884  
885 885  
838 +(% class="wikigeneratedid" %)
839 +(((
840 +
841 +)))
842 +
886 886  = 8.  Packing Info =
887 887  
888 888  (((
... ... @@ -890,7 +890,7 @@
890 890  
891 891  (% style="color:#037691" %)**Package Includes**:
892 892  
893 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
850 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
894 894  * External antenna x 1
895 895  )))
896 896  
... ... @@ -899,6 +899,7 @@
899 899  
900 900  (% style="color:#037691" %)**Dimension and weight**:
901 901  
859 +
902 902  * Device Size: 13.0 x 5 x 4.5 cm
903 903  * Device Weight: 150g
904 904  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -908,12 +908,11 @@
908 908  (((
909 909  
910 910  
869 +
911 911  
912 912  )))
913 913  
914 914  = 9.  Support =
915 915  
916 -
917 917  * 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.
918 -
919 919  * 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