Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 99.2 >
edited by Xiaoling
on 2022/07/09 14:37
To version < 115.8 >
edited by Xiaoling
on 2022/07/09 17:35
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -42,18 +42,19 @@
42 42  == 1.2 ​ Features ==
43 43  
44 44  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
45 -* Ultra low power consumption
46 -* Distance Detection by Ultrasonic technology
47 -* Flat object range 280mm - 7500mm
48 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
49 -* Cable Length: 25cm
45 +* Monitor Temperature & Humidity via SHT31
50 50  * AT Commands to change parameters
51 51  * Uplink on periodically
52 52  * Downlink to change configure
53 53  * IP66 Waterproof Enclosure
50 +* Ultra-Low Power consumption
51 +* AT Commands to change parameters
54 54  * Micro SIM card slot for NB-IoT SIM
55 55  * 8500mAh Battery for long term use
56 56  
55 +
56 +
57 +
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -73,6 +73,7 @@
73 73  
74 74  (% style="color:#037691" %)**Battery:**
75 75  
77 +
76 76  * Li/SOCI2 un-chargeable battery
77 77  * Capacity: 8500mAh
78 78  * Self Discharge: <1% / Year @ 25°C
... ... @@ -79,11 +79,9 @@
79 79  * Max continuously current: 130mA
80 80  * Max boost current: 2A, 1 second
81 81  
82 -(% style="color:#037691" %)**Power Consumption**
83 83  
84 -* STOP Mode: 10uA @ 3.3v
85 -* Max transmit power: 350mA@3.3v
86 86  
86 +
87 87  == ​1.4  Applications ==
88 88  
89 89  * Smart Buildings & Home Automation
... ... @@ -99,22 +99,51 @@
99 99  
100 100  == 1.5  Pin Definitions ==
101 101  
102 +N95S31B use the mother board from NBSN95 which as below.
102 102  
103 -[[image:1657328609906-564.png]]
104 +[[image:image-20220709144723-1.png]]
104 104  
105 105  
107 +=== 1.5.1 Jumper JP2 ===
106 106  
107 -= 2.  Use NDDS75 to communicate with IoT Server =
109 +Power on Device when put this jumper.
108 108  
111 +
112 +
113 +=== 1.5.2 BOOT MODE / SW1 ===
114 +
115 +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.
116 +
117 +2) Flash: work mode, device starts to work and send out console output for further debug
118 +
119 +
120 +
121 +=== 1.5.3 Reset Button ===
122 +
123 +Press to reboot the device.
124 +
125 +
126 +
127 +=== 1.5.4 LED ===
128 +
129 +It will flash:
130 +
131 +1. When boot the device in flash mode
132 +1. Send an uplink packet
133 +
134 +
135 += 2.  Use N95S31B to communicate with IoT Server =
136 +
109 109  == 2.1  How it works ==
110 110  
139 +
111 111  (((
112 -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.
141 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B.
113 113  )))
114 114  
115 115  
116 116  (((
117 -The diagram below shows the working flow in default firmware of NDDS75:
146 +The diagram below shows the working flow in default firmware of N95S31B:
118 118  )))
119 119  
120 120  (((
... ... @@ -121,7 +121,7 @@
121 121  
122 122  )))
123 123  
124 -[[image:1657328659945-416.png]]
153 +[[image:1657350248151-650.png]]
125 125  
126 126  (((
127 127  
... ... @@ -128,30 +128,45 @@
128 128  )))
129 129  
130 130  
131 -== 2.2 ​ Configure the NDDS75 ==
160 +== 2.2 ​ Configure the N95S31B ==
132 132  
133 133  
163 +=== 2.2.1  Power On N95S31B ===
164 +
165 +
166 +[[image:image-20220709150546-2.png]]
167 +
168 +
134 134  === 2.2.1 Test Requirement ===
135 135  
136 -(((
137 -To use NDDS75 in your city, make sure meet below requirements:
138 -)))
139 139  
172 +To use N95S31B in your city, make sure meet below requirements:
173 +
140 140  * Your local operator has already distributed a NB-IoT Network there.
141 -* The local NB-IoT network used the band that NSE01 supports.
175 +* The local NB-IoT network used the band that N95S31B supports.
142 142  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
143 143  
178 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
179 +
180 +N95S31B supports different communication protocol such as :
181 +
144 144  (((
145 -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
146 -)))
183 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
184 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
185 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
186 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
147 147  
188 +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.
148 148  
149 -[[image:1657328756309-230.png]]
190 +
191 +)))
150 150  
193 +[[image:1657350625843-586.png]]
151 151  
152 152  
153 -=== 2.2.2 Insert SIM card ===
154 154  
197 +=== 2.2.3  Insert SIM card ===
198 +
155 155  (((
156 156  Insert the NB-IoT Card get from your provider.
157 157  )))
... ... @@ -161,19 +161,19 @@
161 161  )))
162 162  
163 163  
164 -[[image:1657328884227-504.png]]
208 +[[image:1657351240556-536.png]]
165 165  
166 166  
167 167  
168 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
212 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
169 169  
170 170  (((
171 171  (((
172 -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.
216 +User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
173 173  )))
174 174  )))
175 175  
176 -[[image:image-20220709092052-2.png]]
220 +[[image:1657351312545-300.png]]
177 177  
178 178  **Connection:**
179 179  
... ... @@ -193,18 +193,18 @@
193 193  * Flow Control: (% style="color:green" %)**None**
194 194  
195 195  (((
196 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
240 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
197 197  )))
198 198  
199 199  [[image:1657329814315-101.png]]
200 200  
201 201  (((
202 -(% 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/]]
246 +(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
203 203  )))
204 204  
205 205  
206 206  
207 -=== 2.2.4 Use CoAP protocol to uplink data ===
251 +=== 2.2.5  Use CoAP protocol to uplink data ===
208 208  
209 209  (% 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/]]
210 210  
... ... @@ -224,10 +224,12 @@
224 224  )))
225 225  
226 226  (((
271 +
272 +
227 227  For parameter description, please refer to AT command set
228 228  )))
229 229  
230 -[[image:1657330452568-615.png]]
276 +[[image:1657352146020-183.png]]
231 231  
232 232  
233 233  (((
... ... @@ -234,11 +234,11 @@
234 234  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.
235 235  )))
236 236  
237 -[[image:1657330472797-498.png]]
283 +[[image:1657352185396-303.png]]
238 238  
239 239  
240 240  
241 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
287 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
242 242  
243 243  
244 244  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -245,15 +245,16 @@
245 245  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
246 246  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
247 247  
248 -[[image:1657330501006-241.png]]
294 +[[image:1657352391268-297.png]]
249 249  
250 250  
251 -[[image:1657330533775-472.png]]
297 +[[image:1657352403317-397.png]]
252 252  
253 253  
254 254  
255 -=== 2.2.6 Use MQTT protocol to uplink data ===
301 +=== 2.2.7  Use MQTT protocol to uplink data ===
256 256  
303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
257 257  
258 258  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
259 259  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -260,35 +260,40 @@
260 260  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
261 261  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
262 262  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
263 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
264 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
265 265  
266 -[[image:1657249978444-674.png]]
313 +[[image:1657352634421-276.png]]
267 267  
268 268  
269 -[[image:1657330723006-866.png]]
316 +[[image:1657352645687-385.png]]
270 270  
318 +(((
319 +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.
320 +)))
271 271  
322 +
272 272  (((
273 -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.
324 +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.
274 274  )))
275 275  
276 276  
277 277  
278 -=== 2.2.7 Use TCP protocol to uplink data ===
329 +=== 2.2.8  Use TCP protocol to uplink data ===
279 279  
331 +This feature is supported since firmware version v110
280 280  
281 281  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
282 282  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
283 283  
284 -[[image:image-20220709093918-1.png]]
336 +[[image:1657352898400-901.png]]
285 285  
286 286  
287 -[[image:image-20220709093918-2.png]]
339 +[[image:1657352914475-252.png]]
288 288  
289 289  
290 290  
291 -=== 2.2.8 Change Update Interval ===
343 +=== 2.2.9  Change Update Interval ===
292 292  
293 293  User can use below command to change the (% style="color:green" %)**uplink interval**.
294 294  
... ... @@ -295,69 +295,92 @@
295 295  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
296 296  
297 297  (((
298 -(% style="color:red" %)**NOTE:**
350 +
299 299  )))
300 300  
301 -(((
302 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
303 -)))
304 304  
305 305  
306 -
307 307  == 2.3  Uplink Payload ==
308 308  
309 -In this mode, uplink payload includes in total 14 bytes
310 310  
358 +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.
311 311  
360 +
361 +For example:
362 +
363 + (% 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.
364 +
365 +
366 +The uplink payloads are composed in  ASCII String. For example:
367 +
368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
369 +
370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
371 +
372 +
373 +(% style="color:red" %)**NOTE:**
374 +
375 +(% style="color:red" %)
376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
377 +1. By default, the device will send an uplink message every 1 hour.
378 +
379 +
380 +
381 +=== 2.3.1  Payload Analyze ===
382 +
383 +N95S31B uplink payload includes in total 21 bytes
384 +
385 +
312 312  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
313 313  |=(% style="width: 60px;" %)(((
314 314  **Size(bytes)**
315 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
316 -|(% 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"]]
389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
390 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
391 +Reserve/ Same as NBSN95 CFGMOD=1
317 317  
318 -(((
319 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
320 -)))
393 +No function here.
394 +)))|(% style="width:77px" %)(((
395 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
321 321  
397 +By SHT31
398 +)))|(% style="width:80px" %)(((
399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
322 322  
323 -[[image:1657331036973-987.png]]
324 -
325 -(((
326 -The payload is ASCII string, representative same HEX:
401 +By SHT31
327 327  )))
328 328  
329 329  (((
330 -0x72403155615900640c6c19029200 where:
405 +(((
406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
331 331  )))
332 -
333 -* (((
334 -Device ID: 0x724031556159 = 724031556159
335 335  )))
336 -* (((
337 -Version: 0x0064=100=1.0.0
338 -)))
339 339  
340 -* (((
341 -BAT: 0x0c6c = 3180 mV = 3.180V
342 -)))
343 -* (((
344 -Signal: 0x19 = 25
345 -)))
346 -* (((
347 -Distance: 0x0292= 658 mm
348 -)))
349 -* (((
350 -Interrupt: 0x00 = 0
351 351  
411 +[[image:1657354294009-643.png]]
352 352  
353 353  
414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
415 +
416 +* Device ID: 0x724031607457 = 724031607457
417 +* Version: 0x006e=110=1.1.0
418 +
419 +* BAT: 0x0ccd = 3277 mV = 3.277V
420 +* Signal: 0x1b = 27
421 +* Model: 0x01 = 1
422 +* 0x00dc000ccc= reserve, ignore in N95S31B
423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
425 +
426 +(((
354 354  
355 355  )))
356 356  
357 -== 2.4  Payload Explanation and Sensor Interface ==
430 +(((
431 +
432 +)))
358 358  
359 359  
360 -=== 2.4.1  Device ID ===
435 +=== 2.3.2  Device ID ===
361 361  
362 362  (((
363 363  By default, the Device ID equal to the last 6 bytes of IMEI.
... ... @@ -381,20 +381,25 @@
381 381  
382 382  
383 383  
384 -=== 2.4.2  Version Info ===
459 +=== 2.3.3  Version Info ===
385 385  
386 -(((
387 -Specify the software version: 0x64=100, means firmware version 1.00.
388 -)))
389 389  
462 +These bytes include the hardware and software version.
463 +
464 +Higher byte: Specify hardware version: always 0x00 for N95S31B
465 +
466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
467 +
468 +
469 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
470 +
390 390  (((
391 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
472 +
392 392  )))
393 393  
394 394  
476 +=== 2.3.4  Battery Info ===
395 395  
396 -=== 2.4.3  Battery Info ===
397 -
398 398  (((
399 399  Ex1: 0x0B45 = 2885mV
400 400  )))
... ... @@ -405,7 +405,7 @@
405 405  
406 406  
407 407  
408 -=== 2.4.4  Signal Strength ===
488 +=== 2.3.5  Signal Strength ===
409 409  
410 410  (((
411 411  NB-IoT Network signal Strength.
... ... @@ -437,83 +437,24 @@
437 437  
438 438  
439 439  
440 -=== 2.4.5  Distance ===
520 +=== 2.3.6  Temperature & Humidity ===
441 441  
442 -Get the distance. Flat object range 280mm - 7500mm.
522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
443 443  
444 -(((
445 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
446 -)))
524 +[[image:image-20220709161741-3.png]]
447 447  
448 -(((
449 -(((
450 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
451 -)))
452 -)))
453 453  
454 -(((
455 -
456 -)))
527 +Convert the read byte to decimal and divide it by ten.
457 457  
458 -(((
459 -
460 -)))
461 461  
462 -=== 2.4.6  Digital Interrupt ===
530 +**Example:**
463 463  
464 -(((
465 -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.
466 -)))
532 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
467 467  
468 -(((
469 -The command is:
470 -)))
534 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
471 471  
472 -(((
473 -(% 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]])**.**
474 -)))
475 475  
476 476  
477 -(((
478 -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.
479 -)))
480 -
481 -
482 -(((
483 -Example:
484 -)))
485 -
486 -(((
487 -0x(00): Normal uplink packet.
488 -)))
489 -
490 -(((
491 -0x(01): Interrupt Uplink Packet.
492 -)))
493 -
494 -
495 -
496 -=== 2.4.7  ​+5V Output ===
497 -
498 -(((
499 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
500 -)))
501 -
502 -
503 -(((
504 -The 5V output time can be controlled by AT Command.
505 -)))
506 -
507 -(((
508 -(% style="color:blue" %)**AT+5VT=1000**
509 -)))
510 -
511 -(((
512 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
513 -)))
514 -
515 -
516 -
517 517  == 2.5  Downlink Payload ==
518 518  
519 519  By default, NDDS75 prints the downlink payload to console port.
... ... @@ -566,51 +566,16 @@
566 566  
567 567  
568 568  
569 -== 2.6  ​LED Indicator ==
590 +== 2.5  ​Battery Analysis ==
570 570  
592 +=== 2.5.1  ​Battery Type ===
571 571  
572 -The NDDS75 has an internal LED which is to show the status of different state.
573 573  
574 -
575 -* 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)
576 -* Then the LED will be on for 1 second means device is boot normally.
577 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
578 -* For each uplink probe, LED will be on for 500ms.
579 -
580 580  (((
581 -
596 +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.
582 582  )))
583 583  
584 -
585 -
586 -== 2.7  ​Firmware Change Log ==
587 -
588 -
589 589  (((
590 -Download URL & Firmware Change log
591 -)))
592 -
593 -(((
594 -[[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/]]
595 -)))
596 -
597 -
598 -(((
599 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
600 -)))
601 -
602 -
603 -
604 -== 2.8  ​Battery Analysis ==
605 -
606 -=== 2.8.1  ​Battery Type ===
607 -
608 -
609 -(((
610 -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.
611 -)))
612 -
613 -(((
614 614  The battery is designed to last for several years depends on the actually use environment and update interval. 
615 615  )))
616 616  
... ... @@ -628,56 +628,35 @@
628 628  
629 629  
630 630  
631 -=== 2.8.2  Power consumption Analyze ===
617 +=== 2.5.2  Power consumption Analyze ===
632 632  
633 633  (((
634 -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.
620 +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.
635 635  )))
636 636  
637 -
638 638  (((
639 -Instruction to use as below:
624 +
640 640  )))
641 641  
642 -(((
643 -(% 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/]]
644 -)))
645 645  
628 +=== 2.5.3  ​Battery Note ===
646 646  
647 647  (((
648 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
631 +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.
649 649  )))
650 650  
651 -* (((
652 -Product Model
653 -)))
654 -* (((
655 -Uplink Interval
656 -)))
657 -* (((
658 -Working Mode
659 -)))
660 660  
661 -(((
662 -And the Life expectation in difference case will be shown on the right.
663 -)))
664 664  
665 -[[image:image-20220709110451-3.png]]
636 +=== 2.5.4  Replace the battery ===
666 666  
667 667  
668 -
669 -=== 2.8.3  ​Battery Note ===
670 -
671 671  (((
672 -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.
640 +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.
673 673  )))
674 674  
675 675  
676 -
677 -=== 2.8.4  Replace the battery ===
678 -
679 679  (((
680 -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).
645 +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).
681 681  )))
682 682  
683 683  
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content

Applications

Navigation

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