Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 105.2 >
edited by Xiaoling
on 2022/07/09 15:29
To version < 75.4 >
edited by Xiaoling
on 2022/07/09 09:02
>
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,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,42 +14,46 @@
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  
... ... @@ -72,9 +72,9 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
77 +
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
... ... @@ -82,7 +82,14 @@
82 82  * Max boost current: 2A, 1 second
83 83  
84 84  
87 +(% style="color:#037691" %)**Power Consumption**
85 85  
89 +* STOP Mode: 10uA @ 3.3v
90 +* Max transmit power: 350mA@3.3v
91 +
92 +
93 +
94 +
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -96,108 +96,61 @@
96 96  ​
97 97  
98 98  
108 +
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]]
112 +[[image:1657246476176-652.png]]
104 104  
105 105  
106 -=== 1.5.1 Jumper JP2 ===
107 107  
108 -Power on Device when put this jumper.
116 += 2.  Use NSE01 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 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.
122 +The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 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 NSE01.
143 143  )))
144 144  
145 145  
146 146  (((
147 -The diagram below shows the working flow in default firmware of N95S31B:
127 +The diagram below shows the working flow in default firmware of NSE01:
148 148  )))
149 149  
150 -(((
151 -
152 -)))
130 +[[image:image-20220708101605-2.png]]
153 153  
154 -[[image:1657350248151-650.png]]
155 -
156 156  (((
157 157  
158 158  )))
159 159  
160 160  
161 -== 2.2 ​ Configure the N95S31B ==
162 162  
138 +== 2.2 ​ Configure the NSE01 ==
163 163  
164 -=== 2.2.1  Power On N95S31B ===
165 165  
166 -
167 -[[image:image-20220709150546-2.png]]
168 -
169 -
170 170  === 2.2.1 Test Requirement ===
171 171  
172 172  
173 -To use N95S31B in your city, make sure meet below requirements:
144 +(((
145 +To use NSE01 in your city, make sure meet below requirements:
146 +)))
174 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.
149 +* 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 -
153 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NSE01 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  
157 +[[image:1657249419225-449.png]]
197 197  
198 198  
199 -=== 2.2.3  Insert SIM card ===
200 200  
161 +=== 2.2.2 Insert SIM card ===
162 +
201 201  (((
202 202  Insert the NB-IoT Card get from your provider.
203 203  )))
... ... @@ -207,19 +207,18 @@
207 207  )))
208 208  
209 209  
210 -[[image:1657351240556-536.png]]
172 +[[image:1657249468462-536.png]]
211 211  
212 212  
213 213  
214 -=== 2.2.3 Connect USB – TTL to N95S31B to configure it ===
176 +=== 2.2.3 Connect USB – TTL to NSE01 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.
180 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
219 219  )))
220 220  )))
221 221  
222 -[[image:1657351312545-300.png]]
223 223  
224 224  **Connection:**
225 225  
... ... @@ -239,13 +239,13 @@
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.
203 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 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 -[[image:1657329814315-101.png]]
206 +[[image:image-20220708110657-3.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/]]
209 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
249 249  )))
250 250  
251 251  
... ... @@ -255,64 +255,56 @@
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 -)))
221 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
222 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
223 +* (% 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 273  For parameter description, please refer to AT command set
274 -)))
275 275  
276 -[[image:1657330452568-615.png]]
227 +[[image:1657249793983-486.png]]
277 277  
278 278  
279 -(((
280 -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.
281 -)))
230 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
282 282  
283 -[[image:1657330472797-498.png]]
232 +[[image:1657249831934-534.png]]
284 284  
285 285  
286 286  
287 287  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
288 288  
238 +This feature is supported since firmware version v1.0.1
289 289  
290 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
240 +
241 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
291 291  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
292 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
243 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
293 293  
294 -[[image:1657330501006-241.png]]
245 +[[image:1657249864775-321.png]]
295 295  
296 296  
297 -[[image:1657330533775-472.png]]
248 +[[image:1657249930215-289.png]]
298 298  
299 299  
300 300  
301 301  === 2.2.6 Use MQTT protocol to uplink data ===
302 302  
254 +This feature is supported since firmware version v110
303 303  
304 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
305 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
306 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
307 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
308 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
309 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
310 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
311 311  
257 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
258 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
259 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
260 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
261 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
262 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
263 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
264 +
312 312  [[image:1657249978444-674.png]]
313 313  
314 314  
315 -[[image:1657330723006-866.png]]
268 +[[image:1657249990869-686.png]]
316 316  
317 317  
318 318  (((
... ... @@ -323,14 +323,16 @@
323 323  
324 324  === 2.2.7 Use TCP protocol to uplink data ===
325 325  
279 +This feature is supported since firmware version v110
326 326  
281 +
327 327  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
328 328  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
329 329  
330 -[[image:image-20220709093918-1.png]]
285 +[[image:1657250217799-140.png]]
331 331  
332 332  
333 -[[image:image-20220709093918-2.png]]
288 +[[image:1657250255956-604.png]]
334 334  
335 335  
336 336  
... ... @@ -352,54 +352,36 @@
352 352  
353 353  == 2.3  Uplink Payload ==
354 354  
355 -In this mode, uplink payload includes in total 14 bytes
310 +In this mode, uplink payload includes in total 18 bytes
356 356  
357 -
358 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
312 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
359 359  |=(% style="width: 60px;" %)(((
360 360  **Size(bytes)**
361 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
362 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
315 +)))|=(% 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**
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: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"]]
363 363  
364 364  (((
365 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
319 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
366 366  )))
367 367  
368 368  
369 -[[image:1657331036973-987.png]]
323 +[[image:image-20220708111918-4.png]]
370 370  
371 -(((
325 +
372 372  The payload is ASCII string, representative same HEX:
373 -)))
374 374  
375 -(((
376 -0x72403155615900640c6c19029200 where:
377 -)))
328 +0x72403155615900640c7817075e0a8c02f900 where:
378 378  
379 -* (((
380 -Device ID: 0x724031556159 = 724031556159
381 -)))
382 -* (((
383 -Version: 0x0064=100=1.0.0
384 -)))
330 +* Device ID: 0x 724031556159 = 724031556159
331 +* Version: 0x0064=100=1.0.0
385 385  
386 -* (((
387 -BAT: 0x0c6c = 3180 mV = 3.180V
388 -)))
389 -* (((
390 -Signal: 0x19 = 25
391 -)))
392 -* (((
393 -Distance: 0x0292= 658 mm
394 -)))
395 -* (((
396 -Interrupt: 0x00 = 0
333 +* BAT: 0x0c78 = 3192 mV = 3.192V
334 +* Singal: 0x17 = 23
335 +* Soil Moisture: 0x075e= 1886 = 18.86  %
336 +* Soil Temperature:0x0a8c =2700=27 °C
337 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
338 +* Interrupt: 0x00 = 0
397 397  
398 -
399 -
400 -
401 -)))
402 -
403 403  == 2.4  Payload Explanation and Sensor Interface ==
404 404  
405 405  
... ... @@ -422,7 +422,7 @@
422 422  )))
423 423  
424 424  (((
425 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
362 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
426 426  )))
427 427  
428 428  
... ... @@ -434,7 +434,7 @@
434 434  )))
435 435  
436 436  (((
437 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
374 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
438 438  )))
439 439  
440 440  
... ... @@ -442,6 +442,10 @@
442 442  === 2.4.3  Battery Info ===
443 443  
444 444  (((
382 +Check the battery voltage for LSE01.
383 +)))
384 +
385 +(((
445 445  Ex1: 0x0B45 = 2885mV
446 446  )))
447 447  
... ... @@ -483,21 +483,65 @@
483 483  
484 484  
485 485  
486 -=== 2.4.5  Distance ===
427 +=== 2.4.5  Soil Moisture ===
487 487  
488 -Get the distance. Flat object range 280mm - 7500mm.
429 +(((
430 +(((
431 +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.
432 +)))
433 +)))
489 489  
490 490  (((
491 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
436 +(((
437 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
492 492  )))
439 +)))
493 493  
494 494  (((
442 +
443 +)))
444 +
495 495  (((
496 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
446 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
497 497  )))
448 +
449 +
450 +
451 +=== 2.4.6  Soil Temperature ===
452 +
453 +(((
454 +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
498 498  )))
499 499  
500 500  (((
458 +**Example**:
459 +)))
460 +
461 +(((
462 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
463 +)))
464 +
465 +(((
466 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
467 +)))
468 +
469 +
470 +
471 +=== 2.4.7  Soil Conductivity (EC) ===
472 +
473 +(((
474 +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).
475 +)))
476 +
477 +(((
478 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
479 +)))
480 +
481 +(((
482 +Generally, the EC value of irrigation water is less than 800uS / cm.
483 +)))
484 +
485 +(((
501 501  
502 502  )))
503 503  
... ... @@ -505,10 +505,10 @@
505 505  
506 506  )))
507 507  
508 -=== 2.4.6  Digital Interrupt ===
493 +=== 2.4.8  Digital Interrupt ===
509 509  
510 510  (((
511 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
496 +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.
512 512  )))
513 513  
514 514  (((
... ... @@ -539,10 +539,10 @@
539 539  
540 540  
541 541  
542 -=== 2.4.7  ​+5V Output ===
527 +=== 2.4.9  ​+5V Output ===
543 543  
544 544  (((
545 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
530 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
546 546  )))
547 547  
548 548  
... ... @@ -562,9 +562,9 @@
562 562  
563 563  == 2.5  Downlink Payload ==
564 564  
565 -By default, NDDS75 prints the downlink payload to console port.
550 +By default, NSE01 prints the downlink payload to console port.
566 566  
567 -[[image:image-20220709100028-1.png]]
552 +[[image:image-20220708133731-5.png]]
568 568  
569 569  
570 570  (((
... ... @@ -600,7 +600,7 @@
600 600  )))
601 601  
602 602  (((
603 -If payload = 0x04FF, it will reset the NDDS75
588 +If payload = 0x04FF, it will reset the NSE01
604 604  )))
605 605  
606 606  
... ... @@ -614,52 +614,76 @@
614 614  
615 615  == 2.6  ​LED Indicator ==
616 616  
602 +(((
603 +The NSE01 has an internal LED which is to show the status of different state.
617 617  
618 -The NDDS75 has an internal LED which is to show the status of different state.
619 619  
620 -
621 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
606 +* 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)
622 622  * Then the LED will be on for 1 second means device is boot normally.
623 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
608 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
624 624  * For each uplink probe, LED will be on for 500ms.
610 +)))
625 625  
612 +
613 +
614 +
615 +== 2.7  Installation in Soil ==
616 +
617 +__**Measurement the soil surface**__
618 +
626 626  (((
627 -
620 +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]]
628 628  )))
629 629  
623 +[[image:1657259653666-883.png]] ​
630 630  
631 631  
632 -== 2.7  ​Firmware Change Log ==
626 +(((
627 +
633 633  
634 -
635 635  (((
636 -Download URL & Firmware Change log
630 +Dig a hole with diameter > 20CM.
637 637  )))
638 638  
639 639  (((
640 -[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
634 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
641 641  )))
636 +)))
642 642  
638 +[[image:1654506665940-119.png]]
643 643  
644 644  (((
645 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
641 +
646 646  )))
647 647  
648 648  
645 +== 2.8  ​Firmware Change Log ==
649 649  
650 -== 2.8  ​Battery Analysis ==
651 651  
652 -=== 2.8.1  ​Battery Type ===
648 +Download URL & Firmware Change log
653 653  
650 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
654 654  
652 +
653 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
654 +
655 +
656 +
657 +== 2.9  ​Battery Analysis ==
658 +
659 +=== 2.9.1  ​Battery Type ===
660 +
661 +
655 655  (((
656 -The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
663 +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.
657 657  )))
658 658  
666 +
659 659  (((
660 660  The battery is designed to last for several years depends on the actually use environment and update interval. 
661 661  )))
662 662  
671 +
663 663  (((
664 664  The battery related documents as below:
665 665  )))
... ... @@ -669,12 +669,12 @@
669 669  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
670 670  
671 671  (((
672 -[[image:image-20220709101450-2.png]]
681 +[[image:image-20220708140453-6.png]]
673 673  )))
674 674  
675 675  
676 676  
677 -=== 2.8.2  Power consumption Analyze ===
686 +=== 2.9.2  Power consumption Analyze ===
678 678  
679 679  (((
680 680  Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
... ... @@ -708,11 +708,11 @@
708 708  And the Life expectation in difference case will be shown on the right.
709 709  )))
710 710  
711 -[[image:image-20220709110451-3.png]]
720 +[[image:image-20220708141352-7.jpeg]]
712 712  
713 713  
714 714  
715 -=== 2.8.3  ​Battery Note ===
724 +=== 2.9.3  ​Battery Note ===
716 716  
717 717  (((
718 718  The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
... ... @@ -720,10 +720,10 @@
720 720  
721 721  
722 722  
723 -=== 2.8.4  Replace the battery ===
732 +=== 2.9.4  Replace the battery ===
724 724  
725 725  (((
726 -The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
735 +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).
727 727  )))
728 728  
729 729  
... ... @@ -738,7 +738,7 @@
738 738  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/]] 
739 739  )))
740 740  
741 -[[image:1657333200519-600.png]]
750 +[[image:1657261278785-153.png]]
742 742  
743 743  
744 744  
... ... @@ -746,7 +746,7 @@
746 746  
747 747  == 4.1  Access AT Commands ==
748 748  
749 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
758 +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/]]
750 750  
751 751  
752 752  AT+<CMD>?  : Help on <CMD>
... ... @@ -834,11 +834,18 @@
834 834  )))
835 835  
836 836  (((
837 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
846 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
838 838  )))
839 839  
840 840  
841 841  
851 +== 5.2  Can I calibrate NSE01 to different soil types? ==
852 +
853 +(((
854 +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]].
855 +)))
856 +
857 +
842 842  = 6.  Trouble Shooting =
843 843  
844 844  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -866,7 +866,7 @@
866 866  = 7. ​ Order Info =
867 867  
868 868  
869 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
885 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
870 870  
871 871  
872 872  (% class="wikigeneratedid" %)
... ... @@ -881,7 +881,7 @@
881 881  
882 882  (% style="color:#037691" %)**Package Includes**:
883 883  
884 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
900 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
885 885  * External antenna x 1
886 886  )))
887 887  
... ... @@ -890,11 +890,8 @@
890 890  
891 891  (% style="color:#037691" %)**Dimension and weight**:
892 892  
893 -
894 -* Device Size: 13.0 x 5 x 4.5 cm
895 -* Device Weight: 150g
896 -* Package Size / pcs : 15 x 12x 5.5 cm
897 -* Weight / pcs : 220g
909 +* Size: 195 x 125 x 55 mm
910 +* Weight:   420g
898 898  )))
899 899  
900 900  (((
1657328609906-564.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
1657328659945-416.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
1657328756309-230.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -74.9 KB
Content
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
image-20220709092052-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -247.3 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

Applications

Navigation

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