Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 118.3 >
edited by Xiaoling
on 2022/07/12 17:19
To version < 107.1 >
edited by Xiaoling
on 2022/07/09 15:36
>
Change comment: Uploaded new attachment "1657352185396-303.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -9,7 +9,6 @@
9 9  
10 10  **Table of Contents:**
11 11  
12 -{{toc/}}
13 13  
14 14  
15 15  
... ... @@ -22,29 +22,16 @@
22 22  (((
23 23  
24 24  
25 -(((
26 26  The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
27 -)))
28 28  
29 -(((
30 30  The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
31 -)))
32 32  
33 -(((
34 34  N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 -)))
36 36  
37 -(((
38 38  N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
39 -)))
40 40  
41 -(((
42 -
43 -)))
44 44  
45 -(((
46 46  ~* make sure you have NB-IoT coverage locally.
47 -)))
48 48  
49 49  
50 50  )))
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
44 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -87,6 +87,7 @@
87 87  
88 88  (% style="color:#037691" %)**Battery:**
89 89  
77 +
90 90  * Li/SOCI2 un-chargeable battery
91 91  * Capacity: 8500mAh
92 92  * Self Discharge: <1% / Year @ 25°C
... ... @@ -108,7 +108,7 @@
108 108  ​
109 109  
110 110  
111 -== 1.5  Pin Definitions & Switch ==
99 +== 1.5  Pin Definitions ==
112 112  
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
... ... @@ -123,13 +123,9 @@
123 123  
124 124  === 1.5.2 BOOT MODE / SW1 ===
125 125  
126 -(((
127 127  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
128 -)))
129 129  
130 -(((
131 131  2) Flash: work mode, device starts to work and send out console output for further debug
132 -)))
133 133  
134 134  
135 135  
... ... @@ -147,6 +147,8 @@
147 147  1. Send an uplink packet
148 148  
149 149  
134 +
135 +
150 150  = 2.  Use N95S31B to communicate with IoT Server =
151 151  
152 152  == 2.1  How it works ==
... ... @@ -165,7 +165,7 @@
165 165  
166 166  )))
167 167  
168 -[[image:1657520100595-569.png]]
154 +[[image:1657350248151-650.png]]
169 169  
170 170  (((
171 171  
... ... @@ -184,45 +184,24 @@
184 184  === 2.2.1 Test Requirement ===
185 185  
186 186  
187 -(((
188 188  To use N95S31B in your city, make sure meet below requirements:
189 -)))
190 190  
191 -* (((
192 -Your local operator has already distributed a NB-IoT Network there.
193 -)))
194 -* (((
195 -The local NB-IoT network used the band that N95S31B supports.
196 -)))
197 -* (((
198 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 -)))
175 +* Your local operator has already distributed a NB-IoT Network there.
176 +* The local NB-IoT network used the band that N95S31B supports.
177 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
200 200  
201 -(((
179 +
202 202  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
203 -)))
204 204  
205 -(((
206 206  N95S31B supports different communication protocol such as :
207 -)))
208 208  
209 209  (((
210 -* (((
211 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
212 -)))
213 -* (((
214 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
215 -)))
216 -* (((
217 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
218 -)))
219 -* (((
220 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
221 -)))
185 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
222 222  
223 -(((
224 224  We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
225 -)))
226 226  
227 227  
228 228  )))
... ... @@ -246,7 +246,7 @@
246 246  
247 247  
248 248  
249 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
214 +=== 2.2.3 Connect USB – TTL to N95S31B to configure it ===
250 250  
251 251  (((
252 252  (((
... ... @@ -285,7 +285,7 @@
285 285  
286 286  
287 287  
288 -=== 2.2.5  Use CoAP protocol to uplink data ===
253 +=== 2.2.4 Use CoAP protocol to uplink data ===
289 289  
290 290  (% 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/]]
291 291  
... ... @@ -305,12 +305,10 @@
305 305  )))
306 306  
307 307  (((
308 -
309 -
310 310  For parameter description, please refer to AT command set
311 311  )))
312 312  
313 -[[image:1657352146020-183.png]]
276 +[[image:1657330452568-615.png]]
314 314  
315 315  
316 316  (((
... ... @@ -317,11 +317,11 @@
317 317  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.
318 318  )))
319 319  
320 -[[image:1657352185396-303.png]]
283 +[[image:1657330472797-498.png]]
321 321  
322 322  
323 323  
324 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
325 325  
326 326  
327 327  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -328,16 +328,15 @@
328 328  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
329 329  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
330 330  
331 -[[image:1657352391268-297.png]]
294 +[[image:1657330501006-241.png]]
332 332  
333 333  
334 -[[image:1657352403317-397.png]]
297 +[[image:1657330533775-472.png]]
335 335  
336 336  
337 337  
338 -=== 2.2.7  Use MQTT protocol to uplink data ===
301 +=== 2.2.6 Use MQTT protocol to uplink data ===
339 339  
340 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
341 341  
342 342  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
343 343  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -344,40 +344,35 @@
344 344  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
345 345  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
346 346  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
347 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
348 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
309 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
310 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
349 349  
350 -[[image:1657352634421-276.png]]
312 +[[image:1657249978444-674.png]]
351 351  
352 352  
353 -[[image:1657352645687-385.png]]
315 +[[image:1657330723006-866.png]]
354 354  
355 -(((
356 -To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
357 -)))
358 358  
359 -
360 360  (((
361 -MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
319 +MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
362 362  )))
363 363  
364 364  
365 365  
366 -=== 2.2.8  Use TCP protocol to uplink data ===
324 +=== 2.2.7 Use TCP protocol to uplink data ===
367 367  
368 -This feature is supported since firmware version v110
369 369  
370 370  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
371 371  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
372 372  
373 -[[image:1657352898400-901.png]]
330 +[[image:image-20220709093918-1.png]]
374 374  
375 375  
376 -[[image:1657352914475-252.png]]
333 +[[image:image-20220709093918-2.png]]
377 377  
378 378  
379 379  
380 -=== 2.2.9  Change Update Interval ===
337 +=== 2.2.8 Change Update Interval ===
381 381  
382 382  User can use below command to change the (% style="color:green" %)**uplink interval**.
383 383  
... ... @@ -384,155 +384,164 @@
384 384  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
385 385  
386 386  (((
387 -
344 +(% style="color:red" %)**NOTE:**
388 388  )))
389 389  
347 +(((
348 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
349 +)))
390 390  
391 391  
352 +
392 392  == 2.3  Uplink Payload ==
393 393  
355 +In this mode, uplink payload includes in total 14 bytes
394 394  
395 -(((
396 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
397 -)))
398 398  
358 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
359 +|=(% style="width: 60px;" %)(((
360 +**Size(bytes)**
361 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
362 +|(% 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"]]
399 399  
400 400  (((
401 -For example:
365 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
402 402  )))
403 403  
404 -(((
405 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
406 -)))
407 407  
369 +[[image:1657331036973-987.png]]
408 408  
409 409  (((
410 -The uplink payloads are composed in  ASCII String. For example:
372 +The payload is ASCII string, representative same HEX:
411 411  )))
412 412  
413 413  (((
414 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
376 +0x72403155615900640c6c19029200 where:
415 415  )))
416 416  
417 -(((
418 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
379 +* (((
380 +Device ID: 0x724031556159 = 724031556159
419 419  )))
420 -
421 -
422 -(((
423 -(% style="color:red" %)**NOTE:**
382 +* (((
383 +Version: 0x0064=100=1.0.0
424 424  )))
425 425  
426 -(% style="color:red" %)
427 -1. (((
428 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
386 +* (((
387 +BAT: 0x0c6c = 3180 mV = 3.180V
429 429  )))
430 -1. (((
431 -By default, the device will send an uplink message every 1 hour.
389 +* (((
390 +Signal: 0x19 = 25
432 432  )))
392 +* (((
393 +Distance: 0x0292= 658 mm
394 +)))
395 +* (((
396 +Interrupt: 0x00 = 0
433 433  
434 -=== 2.3.1  Payload Analyze ===
435 435  
436 -N95S31B uplink payload includes in total 21 bytes
437 437  
400 +
401 +)))
438 438  
439 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
440 -|=(% style="width: 60px;" %)(((
441 -**Size(bytes)**
442 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
443 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
403 +== 2.4  Payload Explanation and Sensor Interface ==
404 +
405 +
406 +=== 2.4.1  Device ID ===
407 +
444 444  (((
445 -Reserve/ Same as NBSN95 CFGMOD=1
409 +By default, the Device ID equal to the last 6 bytes of IMEI.
446 446  )))
447 447  
448 448  (((
449 -No function here.
413 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
450 450  )))
451 -)))|(% style="width:77px" %)(((
415 +
452 452  (((
453 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
417 +**Example:**
454 454  )))
455 455  
456 456  (((
457 -By SHT31
421 +AT+DEUI=A84041F15612
458 458  )))
459 -)))|(% style="width:80px" %)(((
423 +
460 460  (((
461 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
425 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
462 462  )))
463 463  
428 +
429 +
430 +=== 2.4.2  Version Info ===
431 +
464 464  (((
465 -By SHT31
433 +Specify the software version: 0x64=100, means firmware version 1.00.
466 466  )))
467 -)))
468 468  
469 469  (((
470 -(((
471 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
437 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
472 472  )))
473 -)))
474 474  
475 475  
476 -[[image:1657354294009-643.png]]
477 477  
442 +=== 2.4.3  Battery Info ===
478 478  
479 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
444 +(((
445 +Ex1: 0x0B45 = 2885mV
446 +)))
480 480  
481 -* Device ID: 0x724031607457 = 724031607457
482 -* Version: 0x006e=110=1.1.0
448 +(((
449 +Ex2: 0x0B49 = 2889mV
450 +)))
483 483  
484 -* BAT: 0x0ccd = 3277 mV = 3.277V
485 -* Signal: 0x1b = 27
486 -* Model: 0x01 = 1
487 -* 0x00dc000ccc= reserve, ignore in N95S31B
488 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
489 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
490 490  
453 +
454 +=== 2.4.4  Signal Strength ===
455 +
491 491  (((
492 -
457 +NB-IoT Network signal Strength.
493 493  )))
494 494  
495 495  (((
496 -
461 +**Ex1: 0x1d = 29**
497 497  )))
498 498  
499 -
500 -=== 2.3.2  Device ID ===
501 -
502 502  (((
503 -By default, the Device ID equal to the last 6 bytes of IMEI.
465 +(% style="color:blue" %)**0**(%%)  -113dBm or less
504 504  )))
505 505  
506 506  (((
507 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
469 +(% style="color:blue" %)**1**(%%)  -111dBm
508 508  )))
509 509  
510 510  (((
511 -**Example:**
473 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
512 512  )))
513 513  
514 514  (((
515 -AT+DEUI=A84041F15612
477 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
516 516  )))
517 517  
518 518  (((
519 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
481 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
520 520  )))
521 521  
522 522  
523 523  
524 -=== 2.3.3  Version Info ===
486 +=== 2.4.5  Distance ===
525 525  
488 +Get the distance. Flat object range 280mm - 7500mm.
489 +
526 526  (((
527 -These bytes include the hardware and software version.
491 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
528 528  )))
529 529  
530 530  (((
531 -Higher byte: Specify hardware version: always 0x00 for N95S31B
495 +(((
496 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
532 532  )))
498 +)))
533 533  
534 534  (((
535 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
501 +
536 536  )))
537 537  
538 538  (((
... ... @@ -539,79 +539,63 @@
539 539  
540 540  )))
541 541  
508 +=== 2.4.6  Digital Interrupt ===
509 +
542 542  (((
543 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
511 +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.
544 544  )))
545 545  
546 546  (((
547 -
515 +The command is:
548 548  )))
549 549  
550 -
551 -=== 2.3.4  Battery Info ===
552 -
553 553  (((
554 -Ex1: 0x0B45 = 2885mV
519 +(% 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]])**.**
555 555  )))
556 556  
522 +
557 557  (((
558 -Ex2: 0x0B49 = 2889mV
524 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
559 559  )))
560 560  
561 561  
562 -
563 -=== 2.3.5  Signal Strength ===
564 -
565 565  (((
566 -NB-IoT Network signal Strength.
529 +Example:
567 567  )))
568 568  
569 569  (((
570 -**Ex1: 0x1d = 29**
533 +0x(00): Normal uplink packet.
571 571  )))
572 572  
573 573  (((
574 -(% style="color:blue" %)**0**(%%)  -113dBm or less
537 +0x(01): Interrupt Uplink Packet.
575 575  )))
576 576  
540 +
541 +
542 +=== 2.4.7  ​+5V Output ===
543 +
577 577  (((
578 -(% style="color:blue" %)**1**(%%)  -111dBm
545 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
579 579  )))
580 580  
548 +
581 581  (((
582 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
550 +The 5V output time can be controlled by AT Command.
583 583  )))
584 584  
585 585  (((
586 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
554 +(% style="color:blue" %)**AT+5VT=1000**
587 587  )))
588 588  
589 589  (((
590 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
558 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
591 591  )))
592 592  
593 593  
594 594  
595 -=== 2.3.6  Temperature & Humidity ===
563 +== 2.5  Downlink Payload ==
596 596  
597 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
598 -
599 -[[image:image-20220709161741-3.png]]
600 -
601 -
602 -Convert the read byte to decimal and divide it by ten.
603 -
604 -
605 -**Example:**
606 -
607 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
608 -
609 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
610 -
611 -
612 -
613 -== 2.4  Downlink Payload ==
614 -
615 615  By default, NDDS75 prints the downlink payload to console port.
616 616  
617 617  [[image:image-20220709100028-1.png]]
... ... @@ -662,16 +662,51 @@
662 662  
663 663  
664 664  
665 -== 2.5  ​Battery Analysis ==
615 +== 2.6  ​LED Indicator ==
666 666  
667 -=== 2.5.1  ​Battery Type ===
668 668  
618 +The NDDS75 has an internal LED which is to show the status of different state.
669 669  
620 +
621 +* 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)
622 +* Then the LED will be on for 1 second means device is boot normally.
623 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
624 +* For each uplink probe, LED will be on for 500ms.
625 +
670 670  (((
671 -The N95S31B 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.
627 +
672 672  )))
673 673  
630 +
631 +
632 +== 2.7  ​Firmware Change Log ==
633 +
634 +
674 674  (((
636 +Download URL & Firmware Change log
637 +)))
638 +
639 +(((
640 +[[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/]]
641 +)))
642 +
643 +
644 +(((
645 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
646 +)))
647 +
648 +
649 +
650 +== 2.8  ​Battery Analysis ==
651 +
652 +=== 2.8.1  ​Battery Type ===
653 +
654 +
655 +(((
656 +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.
657 +)))
658 +
659 +(((
675 675  The battery is designed to last for several years depends on the actually use environment and update interval. 
676 676  )))
677 677  
... ... @@ -689,35 +689,56 @@
689 689  
690 690  
691 691  
692 -=== 2.5.2  Power consumption Analyze ===
677 +=== 2.8.2  Power consumption Analyze ===
693 693  
694 694  (((
695 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
680 +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.
696 696  )))
697 697  
683 +
698 698  (((
699 -
685 +Instruction to use as below:
700 700  )))
701 701  
688 +(((
689 +(% 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/]]
690 +)))
702 702  
703 -=== 2.5.3  ​Battery Note ===
704 704  
705 705  (((
706 -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 uplink data, then the battery life may be decreased.
694 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
707 707  )))
708 708  
697 +* (((
698 +Product Model
699 +)))
700 +* (((
701 +Uplink Interval
702 +)))
703 +* (((
704 +Working Mode
705 +)))
709 709  
707 +(((
708 +And the Life expectation in difference case will be shown on the right.
709 +)))
710 710  
711 -=== 2.5.4  Replace the battery ===
711 +[[image:image-20220709110451-3.png]]
712 712  
713 713  
714 +
715 +=== 2.8.3  ​Battery Note ===
716 +
714 714  (((
715 -You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
718 +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.
716 716  )))
717 717  
718 718  
722 +
723 +=== 2.8.4  Replace the battery ===
724 +
719 719  (((
720 -The default battery pack of N95S31B 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).
726 +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).
721 721  )))
722 722  
723 723  
... ... @@ -740,7 +740,7 @@
740 740  
741 741  == 4.1  Access AT Commands ==
742 742  
743 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
749 +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 745  
746 746  AT+<CMD>?  : Help on <CMD>
... ... @@ -828,12 +828,8 @@
828 828  )))
829 829  
830 830  (((
831 -
832 -
833 -(((
834 -(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
837 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
835 835  )))
836 -)))
837 837  
838 838  
839 839  
... ... @@ -864,7 +864,7 @@
864 864  = 7. ​ Order Info =
865 865  
866 866  
867 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
869 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
868 868  
869 869  
870 870  (% class="wikigeneratedid" %)
... ... @@ -879,7 +879,7 @@
879 879  
880 880  (% style="color:#037691" %)**Package Includes**:
881 881  
882 -* N95S31B NB-IoT Temperature and Humidity Sensor
884 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
883 883  * External antenna x 1
884 884  )))
885 885  
... ... @@ -888,10 +888,11 @@
888 888  
889 889  (% style="color:#037691" %)**Dimension and weight**:
890 890  
893 +
891 891  * Device Size: 13.0 x 5 x 4.5 cm
892 892  * Device Weight: 150g
893 -* Package Size / pcs : 14.0 x 8x 5 cm
894 -* Weight / pcs : 180g
896 +* Package Size / pcs : 15 x 12x 5.5 cm
897 +* Weight / pcs : 220g
895 895  )))
896 896  
897 897  (((
1657352391268-297.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 KB
Content
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content

Applications

Navigation

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