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

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,56 +1,41 @@
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 -{{toc/}}
13 13  
14 14  
15 15  
16 16  
17 17  
15 +
18 18  = 1.  Introduction =
19 19  
18 +== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 20  
21 -== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 -
23 23  (((
24 24  
25 25  
26 26  (((
27 -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*.
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.
28 28  )))
29 29  
30 -(((
31 -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.
32 -)))
33 -
34 -(((
35 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 -)))
37 -
38 -(((
39 -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).
40 -)))
41 -
42 -(((
43 43  
44 44  )))
45 45  
46 -(((
47 -~* make sure you have NB-IoT coverage locally.
48 -)))
35 +[[image:1654503236291-817.png]]
49 49  
50 -
51 -)))
52 52  
53 -[[image:1657348284168-431.png]]
38 +[[image:1657327959271-447.png]]
54 54  
55 55  
56 56  
... ... @@ -58,18 +58,19 @@
58 58  
59 59  
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 -* 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
62 62  * AT Commands to change parameters
63 63  * Uplink on periodically
64 64  * Downlink to change configure
65 65  * IP66 Waterproof Enclosure
66 -* Ultra-Low Power consumption
67 -* AT Commands to change parameters
68 68  * Micro SIM card slot for NB-IoT SIM
69 69  * 8500mAh Battery for long term use
70 70  
71 71  
72 -
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -95,11 +95,15 @@
95 95  * Max continuously current: 130mA
96 96  * Max boost current: 2A, 1 second
97 97  
84 +(% style="color:#037691" %)**Power Consumption**
98 98  
86 +* STOP Mode: 10uA @ 3.3v
87 +* Max transmit power: 350mA@3.3v
99 99  
100 -== ​1.4  Applications ==
101 101  
102 102  
91 +== ​1.4  Applications ==
92 +
103 103  * Smart Buildings & Home Automation
104 104  * Logistics and Supply Chain Management
105 105  * Smart Metering
... ... @@ -112,66 +112,24 @@
112 112  
113 113  
114 114  
115 -== 1.5  Pin Definitions & Switch ==
105 +== 1.5  Pin Definitions ==
116 116  
117 117  
118 -N95S31B use the mother board from NBSN95 which as below.
108 +[[image:1657328609906-564.png]]
119 119  
120 120  
121 -[[image:image-20220709144723-1.png]]
122 122  
112 += 2.  Use NDDS75 to communicate with IoT Server =
123 123  
124 -
125 -=== 1.5.1 Jumper JP2 ===
126 -
127 -
128 -Power on Device when put this jumper.
129 -
130 -
131 -
132 -=== 1.5.2 BOOT MODE / SW1 ===
133 -
134 -
135 -(((
136 -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.
137 -)))
138 -
139 -(((
140 -2) Flash: work mode, device starts to work and send out console output for further debug
141 -)))
142 -
143 -
144 -
145 -=== 1.5.3 Reset Button ===
146 -
147 -
148 -Press to reboot the device.
149 -
150 -
151 -
152 -=== 1.5.4 LED ===
153 -
154 -
155 -It will flash:
156 -
157 -1. When boot the device in flash mode
158 -1. Send an uplink packet
159 -
160 -
161 -
162 -= 2.  Use N95S31B to communicate with IoT Server =
163 -
164 -
165 165  == 2.1  How it works ==
166 166  
167 -
168 168  (((
169 -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.
170 170  )))
171 171  
172 172  
173 173  (((
174 -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:
175 175  )))
176 176  
177 177  (((
... ... @@ -178,7 +178,7 @@
178 178  
179 179  )))
180 180  
181 -[[image:1657520100595-569.png]]
129 +[[image:1657328659945-416.png]]
182 182  
183 183  (((
184 184  
... ... @@ -185,69 +185,30 @@
185 185  )))
186 186  
187 187  
188 -== 2.2 ​ Configure the N95S31B ==
136 +== 2.2 ​ Configure the NDDS75 ==
189 189  
190 190  
191 -=== 2.2.1  Power On N95S31B ===
192 -
193 -
194 -[[image:image-20220709150546-2.png]]
195 -
196 -
197 -
198 198  === 2.2.1 Test Requirement ===
199 199  
200 -
201 201  (((
202 -To use N95S31B in your city, make sure meet below requirements:
142 +To use NDDS75 in your city, make sure meet below requirements:
203 203  )))
204 204  
205 -* (((
206 -Your local operator has already distributed a NB-IoT Network there.
207 -)))
208 -* (((
209 -The local NB-IoT network used the band that N95S31B supports.
210 -)))
211 -* (((
212 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
213 -)))
145 +* Your local operator has already distributed a NB-IoT Network there.
146 +* The local NB-IoT network used the band that NSE01 supports.
147 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
214 214  
215 215  (((
216 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
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
217 217  )))
218 218  
219 -(((
220 -N95S31B supports different communication protocol such as :
221 -)))
222 222  
223 -(((
224 -* (((
225 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
226 -)))
227 -* (((
228 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
229 -)))
230 -* (((
231 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
232 -)))
233 -* (((
234 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
235 -)))
154 +[[image:1657328756309-230.png]]
236 236  
237 -(((
238 -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.
239 -)))
240 240  
241 -
242 -)))
243 243  
244 -[[image:1657350625843-586.png]]
158 +=== 2.2.2 Insert SIM card ===
245 245  
246 -
247 -
248 -=== 2.2.3  Insert SIM card ===
249 -
250 -
251 251  (((
252 252  Insert the NB-IoT Card get from your provider.
253 253  )))
... ... @@ -257,24 +257,20 @@
257 257  )))
258 258  
259 259  
260 -[[image:1657351240556-536.png]]
169 +[[image:1657328884227-504.png]]
261 261  
262 262  
263 263  
264 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
265 265  
266 -
267 267  (((
268 268  (((
269 -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.
270 -
271 -
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.
272 272  )))
273 273  )))
274 274  
275 -[[image:1657351312545-300.png]]
181 +[[image:image-20220709092052-2.png]]
276 276  
277 -
278 278  **Connection:**
279 279  
280 280   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -293,366 +293,285 @@
293 293  * Flow Control: (% style="color:green" %)**None**
294 294  
295 295  (((
296 -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.
297 297  )))
298 298  
299 299  [[image:1657329814315-101.png]]
300 300  
301 -
302 302  (((
303 -(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
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/]]
304 304  )))
305 305  
306 306  
307 307  
308 -=== 2.2.5  Use CoAP protocol to uplink data ===
212 +=== 2.2.4 Use CoAP protocol to uplink data ===
309 309  
214 +(% 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/]]
310 310  
311 -(% 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/]]**
312 312  
313 -
314 -(((
315 315  **Use below commands:**
316 -)))
317 317  
318 -* (((
319 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
320 -)))
321 -* (((
322 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
323 -)))
324 -* (((
325 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
326 -)))
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
327 327  
328 -(((
329 -
330 -
331 331  For parameter description, please refer to AT command set
332 -)))
333 333  
334 -[[image:1657352146020-183.png]]
225 +[[image:1657330452568-615.png]]
335 335  
336 336  
337 -(((
338 338  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.
339 -)))
340 340  
341 -[[image:1657352185396-303.png]]
230 +[[image:1657330472797-498.png]]
342 342  
343 343  
344 344  
345 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
346 346  
347 347  
348 -* (% 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
349 349  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
350 -* (% 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
351 351  
352 -[[image:1657352391268-297.png]]
353 353  
242 +[[image:1657330501006-241.png]]
354 354  
355 -[[image:1657352403317-397.png]]
356 356  
245 +[[image:1657330533775-472.png]]
357 357  
358 358  
359 -=== 2.2.7  Use MQTT protocol to uplink data ===
360 360  
249 +=== 2.2.6 Use MQTT protocol to uplink data ===
361 361  
362 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
251 +This feature is supported since firmware version v110
363 363  
364 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
365 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
366 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
367 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
368 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
369 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
370 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
371 371  
372 -[[image:1657352634421-276.png]]
254 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
255 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
256 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
257 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
258 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
259 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
260 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
373 373  
262 +[[image:1657249978444-674.png]]
374 374  
375 -[[image:1657352645687-385.png]]
376 376  
265 +[[image:1657249990869-686.png]]
377 377  
378 -(((
379 -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.
380 -)))
381 381  
382 -
383 383  (((
384 -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.
269 +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.
385 385  )))
386 386  
387 387  
388 388  
389 -=== 2.2.8  Use TCP protocol to uplink data ===
274 +=== 2.2.7 Use TCP protocol to uplink data ===
390 390  
391 -
392 392  This feature is supported since firmware version v110
393 393  
278 +
394 394  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
395 395  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
396 396  
397 -[[image:1657352898400-901.png]]
282 +[[image:1657250217799-140.png]]
398 398  
399 399  
400 -[[image:1657352914475-252.png]]
285 +[[image:1657250255956-604.png]]
401 401  
402 402  
403 403  
404 -=== 2.2.9  Change Update Interval ===
289 +=== 2.2.8 Change Update Interval ===
405 405  
406 -
407 407  User can use below command to change the (% style="color:green" %)**uplink interval**.
408 408  
409 409  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
410 410  
411 411  (((
412 -
296 +(% style="color:red" %)**NOTE:**
413 413  )))
414 414  
415 415  (((
416 -(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
300 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
417 417  )))
418 418  
419 -(((
420 -(% 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).**
421 -)))
422 422  
423 423  
424 -
425 425  == 2.3  Uplink Payload ==
426 426  
307 +In this mode, uplink payload includes in total 18 bytes
427 427  
309 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
310 +|=(% style="width: 60px;" %)(((
311 +**Size(bytes)**
312 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1**
313 +|(% 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" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
314 +
428 428  (((
429 -N95S31B has different working modes for the connections of different types 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.
316 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
430 430  )))
431 431  
432 432  
320 +[[image:image-20220708111918-4.png]]
321 +
322 +
323 +The payload is ASCII string, representative same HEX:
324 +
325 +0x72403155615900640c7817075e0a8c02f900 where:
326 +
327 +* Device ID: 0x 724031556159 = 724031556159
328 +* Version: 0x0064=100=1.0.0
329 +
330 +* BAT: 0x0c78 = 3192 mV = 3.192V
331 +* Singal: 0x17 = 23
332 +* Soil Moisture: 0x075e= 1886 = 18.86  %
333 +* Soil Temperature:0x0a8c =2700=27 °C
334 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
335 +* Interrupt: 0x00 = 0
336 +
337 +== 2.4  Payload Explanation and Sensor Interface ==
338 +
339 +
340 +=== 2.4.1  Device ID ===
341 +
433 433  (((
434 -For example:
343 +By default, the Device ID equal to the last 6 bytes of IMEI.
435 435  )))
436 436  
437 437  (((
438 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
347 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
439 439  )))
440 440  
441 -
442 442  (((
443 -The uplink payloads are composed in  ASCII String. For example:
351 +**Example:**
444 444  )))
445 445  
446 446  (((
447 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
355 +AT+DEUI=A84041F15612
448 448  )))
449 449  
450 450  (((
451 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
359 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
452 452  )))
453 453  
454 454  
363 +
364 +=== 2.4.2  Version Info ===
365 +
455 455  (((
456 -(% style="color:red" %)**NOTE:**
367 +Specify the software version: 0x64=100, means firmware version 1.00.
457 457  )))
458 458  
459 -(% style="color:red" %)
460 -1. (((
461 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
370 +(((
371 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
462 462  )))
463 -1. (((
464 -**By default, the device will send an uplink message every 1 hour.**
465 465  
466 466  
467 467  
468 -
376 +=== 2.4.3  Battery Info ===
377 +
378 +(((
379 +Check the battery voltage for LSE01.
469 469  )))
470 470  
471 -=== 2.3.1  Payload Analyze ===
382 +(((
383 +Ex1: 0x0B45 = 2885mV
384 +)))
472 472  
386 +(((
387 +Ex2: 0x0B49 = 2889mV
388 +)))
473 473  
474 -==== 2.3.1.1  Before Firmware v1.2 ====
475 475  
476 476  
477 -N95S31B uplink payload includes in total 21 bytes
392 +=== 2.4.4  Signal Strength ===
478 478  
479 -
480 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:745px" %)
481 -|=(% style="width: 60px;" %)(((
482 -**Size(bytes)**
483 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 162px;" %)5|=(% style="width: 102px;" %)**2**|=(% style="width: 81px;" %)**2**
484 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:162px" %)(((
485 485  (((
486 -Reserve/ Same as NBSN95 CFGMOD=1
395 +NB-IoT Network signal Strength.
487 487  )))
488 488  
489 489  (((
490 -No function here.
399 +**Ex1: 0x1d = 29**
491 491  )))
492 -)))|(% style="width:102px" %)(((
401 +
493 493  (((
494 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
403 +(% style="color:blue" %)**0**(%%)  -113dBm or less
495 495  )))
496 496  
497 497  (((
498 -By SHT31
407 +(% style="color:blue" %)**1**(%%)  -111dBm
499 499  )))
500 -)))|(% style="width:81px" %)(((
409 +
501 501  (((
502 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
411 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
503 503  )))
504 504  
505 505  (((
506 -By SHT31
415 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
507 507  )))
508 -)))
509 509  
510 510  (((
511 -
512 -
513 -(((
514 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
419 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
515 515  )))
516 -)))
517 517  
518 518  
519 -[[image:1657354294009-643.png]]
520 520  
424 +=== 2.4.5  Soil Moisture ===
521 521  
522 -The payload is ASCII string, representative same HEX: **0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186**
426 +(((
427 +(((
428 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
429 +)))
430 +)))
523 523  
524 -**where:**
432 +(((
433 +(((
434 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
435 +)))
436 +)))
525 525  
526 -* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457
527 -
528 -* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0
529 -
530 -* (% style="color:#037691" %)**BAT:**   (%%) 0x0ccd = 3277 mV = 3.277V
531 -
532 -* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27
533 -
534 -* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1
535 -
536 -* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B**
537 -
538 -* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C
539 -
540 -* (% style="color:#037691" %)**Humidity by SHT31:**  (%%) 0x0186 = 390 = 39.0 %rh
541 -
542 542  (((
543 543  
440 +)))
544 544  
545 -
546 -
442 +(((
443 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
547 547  )))
548 548  
549 -==== 2.3.1.2 Since Firmware v1.2 ====
550 550  
551 551  
552 -In this mode, uplink payload includes 91 bytes in total by default.
448 +=== 2.4.6  Soil Temperature ===
553 553  
554 -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.
555 -
556 -
557 -(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
558 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
559 -|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
560 -
561 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
562 -
563 -
564 -[[image:image-20220908154949-1.png]]
565 -
566 -
567 -The payload is ASCII string, representative same HEX:
568 -
569 -**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ __0112023b631998f3__// //__011202426319983f__ __01110242631996eb__**
570 -
571 -**where:**
572 -
573 -* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782
574 -
575 -* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2
576 -
577 -* (% style="color:#037691" %)**BAT:**  (%%)0x0d0f = 3343 mV = 3.343V
578 -
579 -* (% style="color:#037691" %)**Singal:**(%%)  0x0c = 12
580 -
581 -* (% style="color:#037691" %)**Mod:**(%%)  0x01 = 1
582 -
583 -* (% style="color:#037691" %)**TemDS18B20:**(%%)  0x0000= 0 = 0
584 -
585 -* (% style="color:#037691" %)**Interrupt:**  (%%)0x00= 0
586 -
587 -* (% style="color:#037691" %)**adc:**(%%)  0x0030= 48
588 -
589 -* (% style="color:#037691" %)**SHTTEM:**(%%)  0x0114= 276 = 27.6
590 -
591 -* (% style="color:#037691" %)**SHTHUM:**(%%)  0x0231 =561=56.1%
592 -
593 -* (% style="color:#037691" %)**Time stamp :  **(%%)0x63199d3c =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
594 -
595 -* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%)  0113023163199d12
596 -
597 -* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, .......
598 -
599 -
600 -
601 -
602 -=== 2.3.2  Device ID ===
603 -
604 -
605 605  (((
606 -By default, the Device ID equal to the last 6 bytes of IMEI.
451 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is
607 607  )))
608 608  
609 609  (((
610 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
611 -
612 -
455 +**Example**:
613 613  )))
614 614  
615 615  (((
616 -(% style="color:blue" %)**Example:**
459 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
617 617  )))
618 618  
619 619  (((
620 -AT+DEUI=A84041F15612
463 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
621 621  )))
622 622  
623 -(((
624 -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.
625 625  
626 -
627 -)))
628 628  
629 -(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
468 +=== 2.4.7  Soil Conductivity (EC) ===
630 630  
631 -
632 -By default, the Device ID equal to the last 15 bits of IMEI.
633 -
634 -User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID
635 -
636 -
637 -(% style="color:blue" %)**Example:**
638 -
639 -AT+DEUI=868411056754138
640 -
641 -
642 -
643 -=== 2.3.3  Version Info ===
644 -
645 -
646 646  (((
647 -These bytes include the hardware and software version.
471 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
648 648  )))
649 649  
650 650  (((
651 -Higher byte: Specify hardware version: always 0x00 for N95S31B
475 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
652 652  )))
653 653  
654 654  (((
655 -Lower byte: Specify the software version: 0x6E=110, means firmware version 110
479 +Generally, the EC value of irrigation water is less than 800uS / cm.
656 656  )))
657 657  
658 658  (((
... ... @@ -660,87 +660,71 @@
660 660  )))
661 661  
662 662  (((
663 -For example: 0x00 6E: this device is N95S31B with firmware version 110.
487 +
664 664  )))
665 665  
490 +=== 2.4.8  Digital Interrupt ===
491 +
666 666  (((
667 -
493 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
668 668  )))
669 669  
670 -
671 -=== 2.3.4  Battery Info ===
672 -
673 -
674 674  (((
675 -Ex1: 0x0B45 = 2885mV
497 +The command is:
676 676  )))
677 677  
678 678  (((
679 -Ex2: 0x0B49 = 2889mV
501 +(% 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]])**.**
680 680  )))
681 681  
682 682  
505 +(((
506 +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.
507 +)))
683 683  
684 -=== 2.3.5  Signal Strength ===
685 685  
686 -
687 687  (((
688 -NB-IoT Network signal Strength.
511 +Example:
689 689  )))
690 690  
691 691  (((
692 -**Ex1: 0x1d = 29**
515 +0x(00): Normal uplink packet.
693 693  )))
694 694  
695 695  (((
696 -(% style="color:blue" %)**0**(%%)  -113dBm or less
519 +0x(01): Interrupt Uplink Packet.
697 697  )))
698 698  
522 +
523 +
524 +=== 2.4.9  ​+5V Output ===
525 +
699 699  (((
700 -(% style="color:blue" %)**1**(%%)  -111dBm
527 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
701 701  )))
702 702  
530 +
703 703  (((
704 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
532 +The 5V output time can be controlled by AT Command.
705 705  )))
706 706  
707 707  (((
708 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
536 +(% style="color:blue" %)**AT+5VT=1000**
709 709  )))
710 710  
711 711  (((
712 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
540 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
713 713  )))
714 714  
715 715  
716 716  
717 -=== 2.3.6  Temperature & Humidity ===
545 +== 2.5  Downlink Payload ==
718 718  
547 +By default, NSE01 prints the downlink payload to console port.
719 719  
720 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
549 +[[image:image-20220708133731-5.png]]
721 721  
722 -[[image:image-20220709161741-3.png]]
723 723  
724 -
725 -Convert the read byte to decimal and divide it by ten.
726 -
727 -
728 -**Example:**
729 -
730 -Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
731 -
732 -Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
733 -
734 -
735 -
736 -== 2.4  Downlink Payload ==
737 -
738 -
739 -By default, N95S31B prints the downlink payload to console port.
740 -
741 -[[image:image-20220709100028-1.png]]
742 -
743 -
744 744  (((
745 745  (% style="color:blue" %)**Examples:**
746 746  )))
... ... @@ -774,7 +774,7 @@
774 774  )))
775 775  
776 776  (((
777 -If payload = 0x04FF, it will reset the N95S31B
585 +If payload = 0x04FF, it will reset the NSE01
778 778  )))
779 779  
780 780  
... ... @@ -786,82 +786,78 @@
786 786  
787 787  
788 788  
789 -== 2.5  Humidity and Temperature alarm function ==
597 +== 2.6  ​LED Indicator ==
790 790  
599 +(((
600 +The NSE01 has an internal LED which is to show the status of different state.
791 791  
792 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
793 793  
603 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
604 +* Then the LED will be on for 1 second means device is boot normally.
605 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
606 +* For each uplink probe, LED will be on for 500ms.
607 +)))
794 794  
795 -(% style="color:#037691" %)**AT+ SHHUM=min,max**
796 796  
797 797  
798 -² When min=0, and max≠0, Alarm higher than max
799 799  
800 -² When min≠0, and max=0, Alarm lower than min
612 +== 2.7  Installation in Soil ==
801 801  
802 -² When min≠0 and max≠0, Alarm higher than max or lower than min
614 +__**Measurement the soil surface**__
803 803  
616 +(((
617 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
618 +)))
804 804  
805 - (% style="color:blue" %)**Example:**
620 +[[image:1657259653666-883.png]] ​
806 806  
807 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
808 808  
623 +(((
624 +
809 809  
810 -(% style="color:#037691" %)**AT+ SHTEMP=min,max**
626 +(((
627 +Dig a hole with diameter > 20CM.
628 +)))
811 811  
812 -² When min=0, and max≠0, Alarm higher than max
630 +(((
631 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
632 +)))
633 +)))
813 813  
814 -² When min≠0, and max=0, Alarm lower than min
635 +[[image:1654506665940-119.png]]
815 815  
816 -² When min≠0 and max≠0, Alarm higher than max or lower than min
637 +(((
638 +
639 +)))
817 817  
818 818  
819 -**~ (% style="color:blue" %)Example:(%%)**
642 +== 2.8  ​Firmware Change Log ==
820 820  
821 -AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
822 822  
645 +Download URL & Firmware Change log
823 823  
647 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
824 824  
825 -== 2.6 Set the number of data to be uploaded and the recording time ==
826 826  
650 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
827 827  
828 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
829 829  
830 -* (% 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)
831 -* (% 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.
832 832  
833 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
654 +== 2.9  ​Battery Analysis ==
834 834  
835 -[[image:image-20221009001045-1.png||height="726" width="1009"]]
656 +=== 2.9.1  ​Battery Type ===
836 836  
837 837  
838 -
839 -== 2.7 Read or Clear cached data ==
840 -
841 -
842 -**~ (% style="color:blue" %)➢ AT Command:(%%)**
843 -
844 -* (% style="color:#037691" %)**AT+CDP**  (%%) ~/~/ Read cached data
845 -* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/  Clear cached data
846 -
847 -[[image:image-20220908163102-2.png]]
848 -
849 -
850 -
851 -== 2.8  ​Battery Analysis ==
852 -
853 -
854 -=== 2.8.1  ​Battery Type ===
855 -
856 -
857 857  (((
858 -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.
660 +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.
859 859  )))
860 860  
663 +
861 861  (((
862 862  The battery is designed to last for several years depends on the actually use environment and update interval. 
863 863  )))
864 864  
668 +
865 865  (((
866 866  The battery related documents as below:
867 867  )))
... ... @@ -871,42 +871,61 @@
871 871  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
872 872  
873 873  (((
874 -[[image:image-20220709101450-2.png]]
678 +[[image:image-20220708140453-6.png]]
875 875  )))
876 876  
877 877  
878 878  
879 -=== 2.8.2  Power consumption Analyze ===
683 +=== 2.9.2  Power consumption Analyze ===
880 880  
685 +(((
686 +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.
687 +)))
881 881  
689 +
882 882  (((
883 -The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
691 +Instruction to use as below:
884 884  )))
885 885  
886 886  (((
887 -
695 +(% 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/]]
888 888  )))
889 889  
890 890  
891 -=== 2.8.3  ​Battery Note ===
699 +(((
700 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose
701 +)))
892 892  
703 +* (((
704 +Product Model
705 +)))
706 +* (((
707 +Uplink Interval
708 +)))
709 +* (((
710 +Working Mode
711 +)))
893 893  
894 894  (((
895 -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.
714 +And the Life expectation in difference case will be shown on the right.
896 896  )))
897 897  
717 +[[image:image-20220708141352-7.jpeg]]
898 898  
899 899  
900 -=== 2.8.4  Replace the battery ===
901 901  
721 +=== 2.9.3  ​Battery Note ===
902 902  
903 903  (((
904 -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.
724 +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.
905 905  )))
906 906  
907 907  
728 +
729 +=== 2.9.4  Replace the battery ===
730 +
908 908  (((
909 -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).
732 +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).
910 910  )))
911 911  
912 912  
... ... @@ -913,7 +913,6 @@
913 913  
914 914  = 3. ​ Access NB-IoT Module =
915 915  
916 -
917 917  (((
918 918  Users can directly access the AT command set of the NB-IoT module.
919 919  )))
... ... @@ -920,23 +920,19 @@
920 920  
921 921  (((
922 922  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/]] 
923 -
924 -
925 925  )))
926 926  
927 -[[image:1657333200519-600.png]]
747 +[[image:1657261278785-153.png]]
928 928  
929 929  
930 930  
931 931  = 4.  Using the AT Commands =
932 932  
933 -
934 934  == 4.1  Access AT Commands ==
935 935  
755 +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/]]
936 936  
937 -See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
938 938  
939 -
940 940  AT+<CMD>?  : Help on <CMD>
941 941  
942 942  AT+<CMD>         : Run <CMD>
... ... @@ -976,24 +976,7 @@
976 976  
977 977  AT+SERVADDR  : Server Address
978 978  
979 -AT+TR      : Get or Set record time
980 980  
981 -AT+APN     : Get or set the APN
982 -
983 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
984 -
985 -AT+DNSCFG  : Get or Set DNS Server
986 -
987 -AT+GETSENSORVALUE   : Returns the current sensor measurement
988 -
989 -AT+NOUD      : Get or Set the number of data to be uploaded
990 -
991 -AT+CDP     : Read or Clear cached data
992 -
993 -AT+SHTEMP: Get or Set alarm of temp
994 -
995 -AT+SHHUM: Get or Set alarm of moisture
996 -
997 997  (% style="color:#037691" %)**COAP Management**      
998 998  
999 999  AT+URI            : Resource parameters
... ... @@ -1027,7 +1027,6 @@
1027 1027  
1028 1028  = ​5.  FAQ =
1029 1029  
1030 -
1031 1031  == 5.1 ​ How to Upgrade Firmware ==
1032 1032  
1033 1033  
... ... @@ -1040,18 +1040,20 @@
1040 1040  )))
1041 1041  
1042 1042  (((
1043 -
843 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
844 +)))
1044 1044  
846 +
847 +
848 +== 5.2  Can I calibrate NSE01 to different soil types? ==
849 +
1045 1045  (((
1046 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
851 +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]].
1047 1047  )))
1048 -)))
1049 1049  
1050 1050  
1051 -
1052 1052  = 6.  Trouble Shooting =
1053 1053  
1054 -
1055 1055  == 6.1  ​Connection problem when uploading firmware ==
1056 1056  
1057 1057  
... ... @@ -1067,7 +1067,6 @@
1067 1067  
1068 1068  == 6.2  AT Command input doesn't work ==
1069 1069  
1070 -
1071 1071  (((
1072 1072  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.
1073 1073  
... ... @@ -1078,7 +1078,7 @@
1078 1078  = 7. ​ Order Info =
1079 1079  
1080 1080  
1081 -Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
882 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1082 1082  
1083 1083  
1084 1084  (% class="wikigeneratedid" %)
... ... @@ -1093,7 +1093,7 @@
1093 1093  
1094 1094  (% style="color:#037691" %)**Package Includes**:
1095 1095  
1096 -* N95S31B NB-IoT Temperature and Humidity Sensor
897 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1097 1097  * External antenna x 1
1098 1098  )))
1099 1099  
... ... @@ -1102,10 +1102,8 @@
1102 1102  
1103 1103  (% style="color:#037691" %)**Dimension and weight**:
1104 1104  
1105 -* Device Size: 13.0 x 5 x 4.5 cm
1106 -* Device Weight: 150g
1107 -* Package Size / pcs : 14.0 x 8x 5 cm
1108 -* Weight / pcs : 180g
906 +* Size: 195 x 125 x 55 mm
907 +* Weight:   420g
1109 1109  )))
1110 1110  
1111 1111  (((
... ... @@ -1117,6 +1117,5 @@
1117 1117  
1118 1118  = 9.  Support =
1119 1119  
1120 -
1121 1121  * 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.
1122 1122  * 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]]
1657330723006-866.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -83.8 KB
Content
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
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-20220709093918-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -138.5 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
image-20220709161741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -111.2 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.David
Size
... ... @@ -1,1 +1,0 @@
1 -29.7 KB
Content
image-20221009001045-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content

Applications

Navigation

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