Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 108.14 >
edited by Xiaoling
on 2023/05/17 18:16
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  
... ... @@ -69,7 +69,6 @@
69 69  * Micro SIM card slot for NB-IoT SIM
70 70  * 8500mAh Battery for long term use
71 71  
72 -
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
83 +* - B1 @H-FDD: 2100MHz
84 +* - B3 @H-FDD: 1800MHz
85 +* - B8 @H-FDD: 900MHz
86 +* - B5 @H-FDD: 850MHz
87 +* - B20 @H-FDD: 800MHz
88 +* - B28 @H-FDD: 700MHz
89 89  
90 90  (% style="color:#037691" %)**Battery:**
91 91  
... ... @@ -100,10 +100,8 @@
100 100  * STOP Mode: 10uA @ 3.3v
101 101  * Max transmit power: 350mA@3.3v
102 102  
103 -
104 104  == ​1.4  Applications ==
105 105  
106 -
107 107  * Smart Buildings & Home Automation
108 108  * Logistics and Supply Chain Management
109 109  * Smart Metering
... ... @@ -121,11 +121,11 @@
121 121  [[image:1657328609906-564.png]]
122 122  
123 123  
122 +
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  
146 +
148 148  == 2.2 ​ Configure the NDDS75 ==
149 149  
149 +
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.
157 +* 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.
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
163 163  )))
164 164  
165 165  
... ... @@ -166,9 +166,9 @@
166 166  [[image:1657328756309-230.png]]
167 167  
168 168  
168 +
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  
183 +
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  
194 +**Connection:**
195 195  
196 -(% style="color:blue" %)**Connection:**
196 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
197 197  
198 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
198 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
199 199  
200 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
200 + (% 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]]**
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/]]
222 222  )))
223 223  
224 224  
222 +
225 225  === 2.2.4 Use CoAP protocol to uplink data ===
226 226  
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/]]
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
236 +(% 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 -
239 +(% 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  
256 +
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
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
273 273  
274 274  [[image:1657330501006-241.png]]
275 275  
... ... @@ -277,16 +277,17 @@
277 277  [[image:1657330533775-472.png]]
278 278  
279 279  
270 +
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
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
290 290  
291 291  [[image:1657249978444-674.png]]
292 292  
... ... @@ -299,11 +299,12 @@
299 299  )))
300 300  
301 301  
293 +
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
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
307 307  
308 308  [[image:image-20220709093918-1.png]]
309 309  
... ... @@ -311,113 +311,78 @@
311 311  [[image:image-20220709093918-2.png]]
312 312  
313 313  
306 +
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
311 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
320 320  
321 321  (((
322 -
323 -
324 -
325 325  (% style="color:red" %)**NOTE:**
315 +)))
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:**
317 +(((
318 +(% 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="10" style="background-color:#f2f2f2; width:440px" %)
343 -|=(% 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;" %)(((
344 344  **Size(bytes)**
345 -)))|=(% 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**
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.
335 +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 -=== 2.3.2  Since firmware v1.3.2 ===
375 -
376 -
377 -In this mode, uplink payload includes 69 bytes in total by default.
378 -
379 -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.
380 -
381 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %)
382 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:70px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**4**
383 -|=(% 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.......
384 -
385 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
386 -
387 -[[image:image-20220908175246-1.png]]
388 -
389 -
341 +(((
390 390  The payload is ASCII string, representative same HEX:
343 +)))
391 391  
392 -**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 +)))
393 393  
394 -**where:**
349 +* (((
350 +Device ID: 0x724031556159 = 724031556159
351 +)))
352 +* (((
353 +Version: 0x0064=100=1.0.0
354 +)))
395 395  
396 -* (% 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
397 397  
398 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
399 399  
400 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
401 401  
402 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
370 +
371 +)))
403 403  
404 -* (% style="color:#037691" %)**Mod:**(%%)**     **0x01 = 1
405 -
406 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
407 -
408 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
409 -
410 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
411 -
412 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
413 -
414 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
415 -
416 416  == 2.4  Payload Explanation and Sensor Interface ==
417 417  
375 +
418 418  === 2.4.1  Device ID ===
419 419  
420 -
421 421  (((
422 422  By default, the Device ID equal to the last 6 bytes of IMEI.
423 423  )))
... ... @@ -424,12 +424,10 @@
424 424  
425 425  (((
426 426  User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
427 -
428 -
429 429  )))
430 430  
431 431  (((
432 -(% style="color:blue" %)**Example :**
387 +**Example:**
433 433  )))
434 434  
435 435  (((
... ... @@ -437,25 +437,13 @@
437 437  )))
438 438  
439 439  (((
440 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
395 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
441 441  )))
442 442  
443 443  
444 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
445 445  
446 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
447 -
448 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
449 -
450 -
451 -(% style="color:blue" %)**Example :**
452 -
453 -AT+DEUI=868411056754138
454 -
455 -
456 456  === 2.4.2  Version Info ===
457 457  
458 -
459 459  (((
460 460  Specify the software version: 0x64=100, means firmware version 1.00.
461 461  )))
... ... @@ -465,9 +465,9 @@
465 465  )))
466 466  
467 467  
411 +
468 468  === 2.4.3  Battery Info ===
469 469  
470 -
471 471  (((
472 472  Ex1: 0x0B45 = 2885mV
473 473  )))
... ... @@ -477,9 +477,9 @@
477 477  )))
478 478  
479 479  
423 +
480 480  === 2.4.4  Signal Strength ===
481 481  
482 -
483 483  (((
484 484  NB-IoT Network signal Strength.
485 485  )))
... ... @@ -509,9 +509,9 @@
509 509  )))
510 510  
511 511  
455 +
512 512  === 2.4.5  Distance ===
513 513  
514 -
515 515  Get the distance. Flat object range 280mm - 7500mm.
516 516  
517 517  (((
... ... @@ -528,9 +528,12 @@
528 528  
529 529  )))
530 530  
474 +(((
475 +
476 +)))
477 +
531 531  === 2.4.6  Digital Interrupt ===
532 532  
533 -
534 534  (((
535 535  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.
536 536  )))
... ... @@ -540,7 +540,7 @@
540 540  )))
541 541  
542 542  (((
543 -(% 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]])**.**
544 544  )))
545 545  
546 546  
... ... @@ -562,9 +562,9 @@
562 562  )))
563 563  
564 564  
511 +
565 565  === 2.4.7  ​+5V Output ===
566 566  
567 -
568 568  (((
569 569  NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
570 570  )))
... ... @@ -572,14 +572,10 @@
572 572  
573 573  (((
574 574  The 5V output time can be controlled by AT Command.
575 -
576 -
577 577  )))
578 578  
579 579  (((
580 580  (% style="color:blue" %)**AT+5VT=1000**
581 -
582 -
583 583  )))
584 584  
585 585  (((
... ... @@ -587,9 +587,9 @@
587 587  )))
588 588  
589 589  
532 +
590 590  == 2.5  Downlink Payload ==
591 591  
592 -
593 593  By default, NDDS75 prints the downlink payload to console port.
594 594  
595 595  [[image:image-20220709100028-1.png]]
... ... @@ -639,88 +639,121 @@
639 639  )))
640 640  
641 641  
642 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
643 643  
585 +== 2.6  ​LED Indicator ==
644 644  
645 -(% style="color:blue" %)** ➢ AT Command:**
646 646  
647 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
588 +The NDDS75 has an internal LED which is to show the status of different state.
648 648  
649 -² When min=0, and max≠0, Alarm higher than max
650 650  
651 -² 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.
652 652  
653 -² When min≠0 and max≠0, Alarm higher than max or lower than min
596 +(((
597 +
598 +)))
654 654  
655 655  
656 -(% style="color:blue" %)** Example:**
657 657  
658 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
602 +== 2.7  ​Firmware Change Log ==
659 659  
660 660  
661 -== 2.7  Set the number of data to be uploaded and the recording time ==
605 +Download URL & Firmware Change log
662 662  
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 +)))
663 663  
664 -(% style="color:blue" %)** ➢ AT Command:**
665 665  
666 -* (% 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)
667 -* (% 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"]]
668 668  
669 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
670 670  
671 -[[image:image-20221009001114-1.png||height="687" width="955"]]
672 672  
616 +== 2.8  ​Battery Analysis ==
673 673  
674 -== 2.8  Read or Clear cached data ==
618 +=== 2.8.1  ​Battery Type ===
675 675  
676 676  
677 -(% 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 +)))
678 678  
679 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
680 -* (% 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 +)))
681 681  
682 -[[image:image-20220908175333-2.png]]
629 +(((
630 +The battery related documents as below:
631 +)))
683 683  
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/]]
684 684  
685 -== 2.9  ​LED Indicator ==
637 +(((
638 +[[image:image-20220709101450-2.png]]
639 +)))
686 686  
687 687  
688 -The NDDS75 has an internal LED which is to show the status of different state.
689 689  
643 +=== 2.8.2  Power consumption Analyze ===
690 690  
691 -* 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)
692 -* Then the LED will be on for 1 second means device is boot normally.
693 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
694 -* 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 +)))
695 695  
649 +
696 696  (((
697 -
651 +Instruction to use as below:
698 698  )))
699 699  
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 +)))
700 700  
701 -== 2.10  ​Firmware Change Log ==
702 702  
659 +(((
660 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
661 +)))
703 703  
663 +* (((
664 +Product Model
665 +)))
666 +* (((
667 +Uplink Interval
668 +)))
669 +* (((
670 +Working Mode
671 +)))
672 +
704 704  (((
705 -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.
706 706  )))
707 707  
677 +[[image:image-20220709110451-3.png]]
678 +
679 +
680 +
681 +=== 2.8.3  ​Battery Note ===
682 +
708 708  (((
709 -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.
710 710  )))
711 711  
712 712  
713 -== 2.11 Battery & Power Consumption ==
714 714  
689 +=== 2.8.4  Replace the battery ===
715 715  
716 -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 +)))
717 717  
718 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
719 719  
720 720  
721 721  = 3. ​ Access NB-IoT Module =
722 722  
723 -
724 724  (((
725 725  Users can directly access the AT command set of the NB-IoT module.
726 726  )))
... ... @@ -727,107 +727,90 @@
727 727  
728 728  (((
729 729  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/]] 
730 -
731 -
732 732  )))
733 733  
734 734  [[image:1657333200519-600.png]]
735 735  
736 736  
710 +
737 737  = 4.  Using the AT Commands =
738 738  
739 739  == 4.1  Access AT Commands ==
740 740  
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/]]
741 741  
742 -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]]
743 743  
718 +AT+<CMD>?  : Help on <CMD>
744 744  
745 -AT+<CMD>?  :  Help on <CMD>
720 +AT+<CMD>         : Run <CMD>
746 746  
747 -AT+<CMD>         :  Run <CMD>
722 +AT+<CMD>=<value> : Set the value
748 748  
749 -AT+<CMD>=<value> :  Set the value
724 +AT+<CMD>=?  : Get the value
750 750  
751 -AT+<CMD>=?  :  Get the value
752 752  
753 -
754 754  (% style="color:#037691" %)**General Commands**(%%)      
755 755  
756 -AT  :  Attention       
729 +AT  : Attention       
757 757  
758 -AT?  :  Short Help     
731 +AT?  : Short Help     
759 759  
760 -ATZ  :  MCU Reset    
733 +ATZ  : MCU Reset    
761 761  
762 -AT+TDC  :  Application Data Transmission Interval
735 +AT+TDC  : Application Data Transmission Interval
763 763  
764 -AT+CFG  :  Print all configurations
737 +AT+CFG  : Print all configurations
765 765  
766 -AT+CFGMOD           :  Working mode selection
739 +AT+CFGMOD           : Working mode selection
767 767  
768 -AT+INTMOD            :  Set the trigger interrupt mode
741 +AT+INTMOD            : Set the trigger interrupt mode
769 769  
770 -AT+5VT  :  Set extend the time of 5V power  
743 +AT+5VT  : Set extend the time of 5V power  
771 771  
772 -AT+PRO  :  Choose agreement
745 +AT+PRO  : Choose agreement
773 773  
774 -AT+WEIGRE  :  Get weight or set weight to 0
747 +AT+WEIGRE  : Get weight or set weight to 0
775 775  
776 -AT+WEIGAP  :  Get or Set the GapValue of weight
749 +AT+WEIGAP  : Get or Set the GapValue of weight
777 777  
778 -AT+RXDL  :  Extend the sending and receiving time
751 +AT+RXDL  : Extend the sending and receiving time
779 779  
780 -AT+CNTFAC  :  Get or set counting parameters
753 +AT+CNTFAC  : Get or set counting parameters
781 781  
782 -AT+SERVADDR  :  Server Address
755 +AT+SERVADDR  : Server Address
783 783  
784 -AT+TR  :  Get or Set record time"
785 785  
786 -AT+APN     :  Get or set the APN
787 -
788 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
789 -
790 -AT+DNSCFG  : Get or Set DNS Server
791 -
792 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
793 -
794 -AT+NOUD  :  Get or Set the number of data to be uploaded
795 -
796 -AT+CDP     :  Read or Clear cached data
797 -
798 -AT+LDDSALARM :  Get or Set alarm of distance
799 -
800 -
801 801  (% style="color:#037691" %)**COAP Management**      
802 802  
803 -AT+URI            :  Resource parameters
760 +AT+URI            : Resource parameters
804 804  
805 805  
806 806  (% style="color:#037691" %)**UDP Management**
807 807  
808 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
765 +AT+CFM          : Upload confirmation mode (only valid for UDP)
809 809  
810 810  
811 811  (% style="color:#037691" %)**MQTT Management**
812 812  
813 -AT+CLIENT  :  Get or Set MQTT client
770 +AT+CLIENT               : Get or Set MQTT client
814 814  
815 -AT+UNAME  :  Get or Set MQTT Username
772 +AT+UNAME  : Get or Set MQTT Username
816 816  
817 -AT+PWD  :  Get or Set MQTT password
774 +AT+PWD                  : Get or Set MQTT password
818 818  
819 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
776 +AT+PUBTOPIC  : Get or Set MQTT publish topic
820 820  
821 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
778 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
822 822  
823 823  
824 824  (% style="color:#037691" %)**Information**          
825 825  
826 -AT+FDR  :  Factory Data Reset
783 +AT+FDR  : Factory Data Reset
827 827  
828 -AT+PWORD  :  Serial Access Password
785 +AT+PWORD  : Serial Access Password
829 829  
830 830  
788 +
831 831  = ​5.  FAQ =
832 832  
833 833  == 5.1 ​ How to Upgrade Firmware ==
... ... @@ -842,10 +842,11 @@
842 842  )))
843 843  
844 844  (((
845 -(% 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.
846 846  )))
847 847  
848 848  
807 +
849 849  = 6.  Trouble Shooting =
850 850  
851 851  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -860,20 +860,16 @@
860 860  
861 861  )))
862 862  
822 +
863 863  == 6.2  AT Command input doesn't work ==
864 864  
865 -
866 866  (((
867 867  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 +
868 868  )))
869 869  
870 870  
871 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". ==
872 -
873 -
874 -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]]//**.
875 -
876 -
877 877  = 7. ​ Order Info =
878 878  
879 879  
... ... @@ -880,6 +880,11 @@
880 880  Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
881 881  
882 882  
838 +(% class="wikigeneratedid" %)
839 +(((
840 +
841 +)))
842 +
883 883  = 8.  Packing Info =
884 884  
885 885  (((
... ... @@ -887,7 +887,7 @@
887 887  
888 888  (% style="color:#037691" %)**Package Includes**:
889 889  
890 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
850 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
891 891  * External antenna x 1
892 892  )))
893 893  
... ... @@ -896,6 +896,7 @@
896 896  
897 897  (% style="color:#037691" %)**Dimension and weight**:
898 898  
859 +
899 899  * Device Size: 13.0 x 5 x 4.5 cm
900 900  * Device Weight: 150g
901 901  * Package Size / pcs : 15 x 12x 5.5 cm
... ... @@ -905,12 +905,11 @@
905 905  (((
906 906  
907 907  
869 +
908 908  
909 909  )))
910 910  
911 911  = 9.  Support =
912 912  
913 -
914 914  * 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.
915 -
916 916  * 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