Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 113.2
edited by Xiaoling
on 2022/07/09 15:50
Change comment: There is no comment for this version
To version 93.1
edited by Xiaoling
on 2022/07/09 10:14
Change comment: Uploaded new attachment "image-20220709101450-2.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -N95S31B NB-IoT Temperature & Humidity Sensor User Manual
1 +NDDS75 NB-IoT Distance Detect Sensor User Manual
Content
... ... @@ -1,12 +1,10 @@
1 1  (% style="text-align:center" %)
2 -[[image:1657348034241-728.png||height="470" width="470"]]
2 +[[image:image-20220709085040-1.png||height="542" width="524"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -
9 -
10 10  **Table of Contents:**
11 11  
12 12  
... ... @@ -14,47 +14,50 @@
14 14  
15 15  
16 16  
15 +
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
18 +== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 21  (((
22 22  
23 23  
24 -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*.
23 +(((
24 +The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
25 +\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
26 +\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
28 +\\NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
29 +\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
30 +)))
25 25  
26 -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.
27 -
28 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
29 -
30 -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).
31 -
32 -
33 -~* make sure you have NB-IoT coverage locally.
34 -
35 35  
36 36  )))
37 37  
38 -[[image:1657348284168-431.png]]
35 +[[image:1654503236291-817.png]]
39 39  
40 40  
38 +[[image:1657327959271-447.png]]
41 41  
40 +
41 +
42 42  == 1.2 ​ Features ==
43 43  
44 44  
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* Monitor Temperature & Humidity via SHT31
46 +* Ultra low power consumption
47 +* Distance Detection by Ultrasonic technology
48 +* Flat object range 280mm - 7500mm
49 +* Accuracy: ±(1cm+S*0.3%) (S: Distance)
50 +* Cable Length: 25cm
47 47  * AT Commands to change parameters
48 48  * Uplink on periodically
49 49  * Downlink to change configure
50 50  * IP66 Waterproof Enclosure
51 -* Ultra-Low Power consumption
52 -* AT Commands to change parameters
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 56  
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -74,7 +74,6 @@
74 74  
75 75  (% style="color:#037691" %)**Battery:**
76 76  
77 -
78 78  * Li/SOCI2 un-chargeable battery
79 79  * Capacity: 8500mAh
80 80  * Self Discharge: <1% / Year @ 25°C
... ... @@ -81,8 +81,13 @@
81 81  * Max continuously current: 130mA
82 82  * Max boost current: 2A, 1 second
83 83  
84 +(% style="color:#037691" %)**Power Consumption**
84 84  
86 +* STOP Mode: 10uA @ 3.3v
87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
85 85  
89 +
90 +
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -96,55 +96,25 @@
96 96  ​
97 97  
98 98  
104 +
99 99  == 1.5  Pin Definitions ==
100 100  
101 -N95S31B use the mother board from NBSN95 which as below.
102 102  
103 -[[image:image-20220709144723-1.png]]
108 +[[image:1657328609906-564.png]]
104 104  
105 105  
106 -=== 1.5.1 Jumper JP2 ===
107 107  
108 -Power on Device when put this jumper.
112 += 2.  Use NDDS75 to communicate with IoT Server =
109 109  
110 -
111 -
112 -=== 1.5.2 BOOT MODE / SW1 ===
113 -
114 -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.
115 -
116 -2) Flash: work mode, device starts to work and send out console output for further debug
117 -
118 -
119 -
120 -=== 1.5.3 Reset Button ===
121 -
122 -Press to reboot the device.
123 -
124 -
125 -
126 -=== 1.5.4 LED ===
127 -
128 -It will flash:
129 -
130 -1. When boot the device in flash mode
131 -1. Send an uplink packet
132 -
133 -
134 -
135 -
136 -= 2.  Use N95S31B to communicate with IoT Server =
137 -
138 138  == 2.1  How it works ==
139 139  
140 -
141 141  (((
142 -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.
117 +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.
143 143  )))
144 144  
145 145  
146 146  (((
147 -The diagram below shows the working flow in default firmware of N95S31B:
122 +The diagram below shows the working flow in default firmware of NDDS75:
148 148  )))
149 149  
150 150  (((
... ... @@ -151,7 +151,7 @@
151 151  
152 152  )))
153 153  
154 -[[image:1657350248151-650.png]]
129 +[[image:1657328659945-416.png]]
155 155  
156 156  (((
157 157  
... ... @@ -158,46 +158,30 @@
158 158  )))
159 159  
160 160  
161 -== 2.2 ​ Configure the N95S31B ==
136 +== 2.2 ​ Configure the NDDS75 ==
162 162  
163 163  
164 -=== 2.2.1  Power On N95S31B ===
165 -
166 -
167 -[[image:image-20220709150546-2.png]]
168 -
169 -
170 170  === 2.2.1 Test Requirement ===
171 171  
141 +(((
142 +To use NDDS75 in your city, make sure meet below requirements:
143 +)))
172 172  
173 -To use N95S31B in your city, make sure meet below requirements:
174 -
175 175  * Your local operator has already distributed a NB-IoT Network there.
176 -* The local NB-IoT network used the band that N95S31B supports.
146 +* The local NB-IoT network used the band that NSE01 supports.
177 177  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
178 178  
179 -
180 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181 -
182 -N95S31B supports different communication protocol such as :
183 -
184 184  (((
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(%%))
189 -
190 -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.
191 -
192 -
150 +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
193 193  )))
194 194  
195 -[[image:1657350625843-586.png]]
196 196  
154 +[[image:1657328756309-230.png]]
197 197  
198 198  
199 -=== 2.2.3  Insert SIM card ===
200 200  
158 +=== 2.2.2 Insert SIM card ===
159 +
201 201  (((
202 202  Insert the NB-IoT Card get from your provider.
203 203  )))
... ... @@ -207,19 +207,19 @@
207 207  )))
208 208  
209 209  
210 -[[image:1657351240556-536.png]]
169 +[[image:1657328884227-504.png]]
211 211  
212 212  
213 213  
214 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
215 215  
216 216  (((
217 217  (((
218 -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.
177 +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.
219 219  )))
220 220  )))
221 221  
222 -[[image:1657351312545-300.png]]
181 +[[image:image-20220709092052-2.png]]
223 223  
224 224  **Connection:**
225 225  
... ... @@ -239,110 +239,90 @@
239 239  * Flow Control: (% style="color:green" %)**None**
240 240  
241 241  (((
242 -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.
201 +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.
243 243  )))
244 244  
245 245  [[image:1657329814315-101.png]]
246 246  
247 247  (((
248 -(% 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/]]
207 +(% 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/]]
249 249  )))
250 250  
251 251  
252 252  
253 -=== 2.2.5  Use CoAP protocol to uplink data ===
212 +=== 2.2.4 Use CoAP protocol to uplink data ===
254 254  
255 255  (% 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/]]
256 256  
257 257  
258 -(((
259 259  **Use below commands:**
260 -)))
261 261  
262 -* (((
263 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
264 -)))
265 -* (((
266 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
267 -)))
268 -* (((
269 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
270 -)))
219 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
221 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
271 271  
272 -(((
273 -
274 -
275 275  For parameter description, please refer to AT command set
276 -)))
277 277  
278 -[[image:1657352146020-183.png]]
225 +[[image:1657330452568-615.png]]
279 279  
280 280  
281 -(((
282 282  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.
283 -)))
284 284  
285 -[[image:1657352185396-303.png]]
230 +[[image:1657330472797-498.png]]
286 286  
287 287  
288 288  
289 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
290 290  
291 291  
292 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
237 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
293 293  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
294 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
239 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
295 295  
296 -[[image:1657352391268-297.png]]
241 +[[image:1657330501006-241.png]]
297 297  
298 298  
299 -[[image:1657352403317-397.png]]
244 +[[image:1657330533775-472.png]]
300 300  
301 301  
302 302  
303 -=== 2.2.7  Use MQTT protocol to uplink data ===
248 +=== 2.2.6 Use MQTT protocol to uplink data ===
304 304  
305 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
306 306  
307 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
308 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
309 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
310 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
311 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
312 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
313 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
251 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
256 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
257 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
314 314  
315 -[[image:1657352634421-276.png]]
259 +[[image:1657249978444-674.png]]
316 316  
317 317  
318 -[[image:1657352645687-385.png]]
262 +[[image:1657330723006-866.png]]
319 319  
320 -(((
321 -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.
322 -)))
323 323  
324 -
325 325  (((
326 -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.
266 +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.
327 327  )))
328 328  
329 329  
330 330  
331 -=== 2.2.8  Use TCP protocol to uplink data ===
271 +=== 2.2.7 Use TCP protocol to uplink data ===
332 332  
333 -This feature is supported since firmware version v110
334 334  
335 335  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
336 336  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
337 337  
338 -[[image:1657352898400-901.png]]
277 +[[image:image-20220709093918-1.png]]
339 339  
340 340  
341 -[[image:1657352914475-252.png]]
280 +[[image:image-20220709093918-2.png]]
342 342  
343 343  
344 344  
345 -=== 2.2.9  Change Update Interval ===
284 +=== 2.2.8 Change Update Interval ===
346 346  
347 347  User can use below command to change the (% style="color:green" %)**uplink interval**.
348 348  
... ... @@ -349,21 +349,25 @@
349 349  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
350 350  
351 351  (((
352 -
291 +(% style="color:red" %)**NOTE:**
353 353  )))
354 354  
294 +(((
295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
296 +)))
355 355  
356 356  
299 +
357 357  == 2.3  Uplink Payload ==
358 358  
359 359  In this mode, uplink payload includes in total 14 bytes
360 360  
361 361  
362 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
305 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
363 363  |=(% style="width: 60px;" %)(((
364 364  **Size(bytes)**
365 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
366 -|(% 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"]]
308 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
309 +|(% 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:108px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
367 367  
368 368  (((
369 369  If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
... ... @@ -398,12 +398,9 @@
398 398  )))
399 399  * (((
400 400  Interrupt: 0x00 = 0
401 -
402 -
403 -
404 -
405 405  )))
406 406  
346 +
407 407  == 2.4  Payload Explanation and Sensor Interface ==
408 408  
409 409  
... ... @@ -446,6 +446,10 @@
446 446  === 2.4.3  Battery Info ===
447 447  
448 448  (((
389 +Check the battery voltage for LSE01.
390 +)))
391 +
392 +(((
449 449  Ex1: 0x0B45 = 2885mV
450 450  )))
451 451  
... ... @@ -487,13 +487,11 @@
487 487  
488 488  
489 489  
490 -=== 2.4.5  Distance ===
434 +=== 2.4.5  Soil Moisture ===
491 491  
492 492  Get the distance. Flat object range 280mm - 7500mm.
493 493  
494 -(((
495 495  For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
496 -)))
497 497  
498 498  (((
499 499  (((
... ... @@ -636,9 +636,7 @@
636 636  == 2.7  ​Firmware Change Log ==
637 637  
638 638  
639 -(((
640 640  Download URL & Firmware Change log
641 -)))
642 642  
643 643  (((
644 644  [[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/]]
... ... @@ -645,25 +645,25 @@
645 645  )))
646 646  
647 647  
648 -(((
649 649  Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
650 -)))
651 651  
652 652  
653 653  
654 -== 2.8  ​Battery Analysis ==
592 +== 2.9  ​Battery Analysis ==
655 655  
656 -=== 2.8.1  ​Battery Type ===
594 +=== 2.9.1  ​Battery Type ===
657 657  
658 658  
659 659  (((
660 -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.
598 +The NSE01 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.
661 661  )))
662 662  
601 +
663 663  (((
664 664  The battery is designed to last for several years depends on the actually use environment and update interval. 
665 665  )))
666 666  
606 +
667 667  (((
668 668  The battery related documents as below:
669 669  )))
... ... @@ -673,12 +673,12 @@
673 673  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
674 674  
675 675  (((
676 -[[image:image-20220709101450-2.png]]
616 +[[image:image-20220708140453-6.png]]
677 677  )))
678 678  
679 679  
680 680  
681 -=== 2.8.2  Power consumption Analyze ===
621 +=== 2.9.2  Power consumption Analyze ===
682 682  
683 683  (((
684 684  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.
... ... @@ -712,11 +712,11 @@
712 712  And the Life expectation in difference case will be shown on the right.
713 713  )))
714 714  
715 -[[image:image-20220709110451-3.png]]
655 +[[image:image-20220708141352-7.jpeg]]
716 716  
717 717  
718 718  
719 -=== 2.8.3  ​Battery Note ===
659 +=== 2.9.3  ​Battery Note ===
720 720  
721 721  (((
722 722  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.
... ... @@ -724,10 +724,10 @@
724 724  
725 725  
726 726  
727 -=== 2.8.4  Replace the battery ===
667 +=== 2.9.4  Replace the battery ===
728 728  
729 729  (((
730 -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).
670 +The default battery pack of NSE01 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).
731 731  )))
732 732  
733 733  
... ... @@ -742,7 +742,7 @@
742 742  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/]] 
743 743  )))
744 744  
745 -[[image:1657333200519-600.png]]
685 +[[image:1657261278785-153.png]]
746 746  
747 747  
748 748  
... ... @@ -750,7 +750,7 @@
750 750  
751 751  == 4.1  Access AT Commands ==
752 752  
753 -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/]]
693 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
754 754  
755 755  
756 756  AT+<CMD>?  : Help on <CMD>
... ... @@ -838,11 +838,18 @@
838 838  )))
839 839  
840 840  (((
841 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
781 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
842 842  )))
843 843  
844 844  
845 845  
786 +== 5.2  Can I calibrate NSE01 to different soil types? ==
787 +
788 +(((
789 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
790 +)))
791 +
792 +
846 846  = 6.  Trouble Shooting =
847 847  
848 848  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -870,7 +870,7 @@
870 870  = 7. ​ Order Info =
871 871  
872 872  
873 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
820 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
874 874  
875 875  
876 876  (% class="wikigeneratedid" %)
... ... @@ -885,7 +885,7 @@
885 885  
886 886  (% style="color:#037691" %)**Package Includes**:
887 887  
888 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
835 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
889 889  * External antenna x 1
890 890  )))
891 891  
... ... @@ -894,11 +894,8 @@
894 894  
895 895  (% style="color:#037691" %)**Dimension and weight**:
896 896  
897 -
898 -* Device Size: 13.0 x 5 x 4.5 cm
899 -* Device Weight: 150g
900 -* Package Size / pcs : 15 x 12x 5.5 cm
901 -* Weight / pcs : 220g
844 +* Size: 195 x 125 x 55 mm
845 +* Weight:   420g
902 902  )))
903 903  
904 904  (((
1657332990863-496.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657348034241-728.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.3 KB
Content
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
image-20220709110451-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -611.5 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -333.5 KB
Content