Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 113.1 >
edited by Xiaoling
on 2022/07/09 15:48
To version < 75.1 >
edited by Xiaoling
on 2022/07/09 08:52
>
Change comment: Uploaded new attachment "1657327959271-447.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,36 +14,39 @@
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:1657245163077-232.png]]
41 41  
42 -== 1.2 ​ Features ==
43 43  
44 44  
42 +== 1.2 ​ Features ==
43 +
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* Monitor Temperature & Humidity via SHT31
45 +* Monitor Soil Moisture
46 +* Monitor Soil Temperature
47 +* Monitor Soil Conductivity
47 47  * AT Commands to change parameters
48 48  * Uplink on periodically
49 49  * Downlink to change configure
... ... @@ -53,8 +53,6 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -72,132 +72,75 @@
72 72  * - B20 @H-FDD: 800MHz
73 73  * - B28 @H-FDD: 700MHz
74 74  
75 -(% style="color:#037691" %)**Battery:**
74 +Probe(% style="color:#037691" %)** Specification:**
76 76  
76 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
77 77  
78 -* Li/SOCI2 un-chargeable battery
79 -* Capacity: 8500mAh
80 -* Self Discharge: <1% / Year @ 25°C
81 -* Max continuously current: 130mA
82 -* Max boost current: 2A, 1 second
78 +[[image:image-20220708101224-1.png]]
83 83  
84 84  
85 85  
86 86  == ​1.4  Applications ==
87 87  
88 -* Smart Buildings & Home Automation
89 -* Logistics and Supply Chain Management
90 -* Smart Metering
91 91  * Smart Agriculture
92 -* Smart Cities
93 -* Smart Factory
94 94  
95 95  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
96 96  ​
97 97  
98 -
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]]
92 +[[image:1657246476176-652.png]]
104 104  
105 105  
106 -=== 1.5.1 Jumper JP2 ===
107 107  
108 -Power on Device when put this jumper.
96 += 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.
102 +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:
107 +The diagram below shows the working flow in default firmware of NSE01:
148 148  )))
149 149  
150 -(((
151 -
152 -)))
110 +[[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  
118 +== 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:
124 +(((
125 +To use NSE01 in your city, make sure meet below requirements:
126 +)))
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.
129 +* 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 -
133 +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  
137 +[[image:1657249419225-449.png]]
197 197  
198 198  
199 -=== 2.2.3  Insert SIM card ===
200 200  
141 +=== 2.2.2 Insert SIM card ===
142 +
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]]
152 +[[image:1657249468462-536.png]]
211 211  
212 212  
213 213  
214 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
156 +=== 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.
160 +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,91 +239,76 @@
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.
183 +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]]
186 +[[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/]]
189 +(% 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  
252 252  
253 -=== 2.2.5  Use CoAP protocol to uplink data ===
194 +=== 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 -)))
201 +* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
202 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
203 +* (% 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]]
207 +[[image:1657249793983-486.png]]
279 279  
280 280  
281 -(((
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 -)))
210 +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.
284 284  
285 -[[image:1657352185396-303.png]]
212 +[[image:1657249831934-534.png]]
286 286  
287 287  
288 288  
289 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
216 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
290 290  
218 +This feature is supported since firmware version v1.0.1
291 291  
292 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
220 +
221 +* (% 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
223 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
295 295  
296 -[[image:1657352391268-297.png]]
225 +[[image:1657249864775-321.png]]
297 297  
298 298  
299 -[[image:1657352403317-397.png]]
228 +[[image:1657249930215-289.png]]
300 300  
301 301  
302 302  
303 -=== 2.2.7  Use MQTT protocol to uplink data ===
232 +=== 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.
234 +This feature is supported since firmware version v110
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
314 314  
315 -[[image:1657352634421-276.png]]
237 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
238 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
239 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
240 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
241 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
242 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
243 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
316 316  
245 +[[image:1657249978444-674.png]]
317 317  
318 -[[image:1657352645687-385.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 -)))
248 +[[image:1657249990869-686.png]]
323 323  
324 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.
252 +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,14 +330,16 @@
330 330  
331 331  === 2.2.7 Use TCP protocol to uplink data ===
332 332  
259 +This feature is supported since firmware version v110
333 333  
261 +
334 334  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
335 335  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
336 336  
337 -[[image:image-20220709093918-1.png]]
265 +[[image:1657250217799-140.png]]
338 338  
339 339  
340 -[[image:image-20220709093918-2.png]]
268 +[[image:1657250255956-604.png]]
341 341  
342 342  
343 343  
... ... @@ -359,54 +359,36 @@
359 359  
360 360  == 2.3  Uplink Payload ==
361 361  
362 -In this mode, uplink payload includes in total 14 bytes
290 +In this mode, uplink payload includes in total 18 bytes
363 363  
364 -
365 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
292 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
366 366  |=(% style="width: 60px;" %)(((
367 367  **Size(bytes)**
368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 -|(% 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"]]
295 +)))|=(% 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**
296 +|(% 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"]]
370 370  
371 371  (((
372 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
299 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
373 373  )))
374 374  
375 375  
376 -[[image:1657331036973-987.png]]
303 +[[image:image-20220708111918-4.png]]
377 377  
378 -(((
305 +
379 379  The payload is ASCII string, representative same HEX:
380 -)))
381 381  
382 -(((
383 -0x72403155615900640c6c19029200 where:
384 -)))
308 +0x72403155615900640c7817075e0a8c02f900 where:
385 385  
386 -* (((
387 -Device ID: 0x724031556159 = 724031556159
388 -)))
389 -* (((
390 -Version: 0x0064=100=1.0.0
391 -)))
310 +* Device ID: 0x 724031556159 = 724031556159
311 +* Version: 0x0064=100=1.0.0
392 392  
393 -* (((
394 -BAT: 0x0c6c = 3180 mV = 3.180V
395 -)))
396 -* (((
397 -Signal: 0x19 = 25
398 -)))
399 -* (((
400 -Distance: 0x0292= 658 mm
401 -)))
402 -* (((
403 -Interrupt: 0x00 = 0
313 +* BAT: 0x0c78 = 3192 mV = 3.192V
314 +* Singal: 0x17 = 23
315 +* Soil Moisture: 0x075e= 1886 = 18.86  %
316 +* Soil Temperature:0x0a8c =2700=27 °C
317 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
318 +* Interrupt: 0x00 = 0
404 404  
405 -
406 -
407 -
408 -)))
409 -
410 410  == 2.4  Payload Explanation and Sensor Interface ==
411 411  
412 412  
... ... @@ -429,7 +429,7 @@
429 429  )))
430 430  
431 431  (((
432 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
342 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
433 433  )))
434 434  
435 435  
... ... @@ -441,7 +441,7 @@
441 441  )))
442 442  
443 443  (((
444 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
354 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
445 445  )))
446 446  
447 447  
... ... @@ -449,6 +449,10 @@
449 449  === 2.4.3  Battery Info ===
450 450  
451 451  (((
362 +Check the battery voltage for LSE01.
363 +)))
364 +
365 +(((
452 452  Ex1: 0x0B45 = 2885mV
453 453  )))
454 454  
... ... @@ -490,21 +490,65 @@
490 490  
491 491  
492 492  
493 -=== 2.4.5  Distance ===
407 +=== 2.4.5  Soil Moisture ===
494 494  
495 -Get the distance. Flat object range 280mm - 7500mm.
409 +(((
410 +(((
411 +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.
412 +)))
413 +)))
496 496  
497 497  (((
498 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
416 +(((
417 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
499 499  )))
419 +)))
500 500  
501 501  (((
422 +
423 +)))
424 +
502 502  (((
503 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
426 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
504 504  )))
428 +
429 +
430 +
431 +=== 2.4.6  Soil Temperature ===
432 +
433 +(((
434 +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
505 505  )))
506 506  
507 507  (((
438 +**Example**:
439 +)))
440 +
441 +(((
442 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
443 +)))
444 +
445 +(((
446 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
447 +)))
448 +
449 +
450 +
451 +=== 2.4.7  Soil Conductivity (EC) ===
452 +
453 +(((
454 +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).
455 +)))
456 +
457 +(((
458 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
459 +)))
460 +
461 +(((
462 +Generally, the EC value of irrigation water is less than 800uS / cm.
463 +)))
464 +
465 +(((
508 508  
509 509  )))
510 510  
... ... @@ -512,10 +512,10 @@
512 512  
513 513  )))
514 514  
515 -=== 2.4.6  Digital Interrupt ===
473 +=== 2.4.8  Digital Interrupt ===
516 516  
517 517  (((
518 -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.
476 +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.
519 519  )))
520 520  
521 521  (((
... ... @@ -546,10 +546,10 @@
546 546  
547 547  
548 548  
549 -=== 2.4.7  ​+5V Output ===
507 +=== 2.4.9  ​+5V Output ===
550 550  
551 551  (((
552 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
510 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
553 553  )))
554 554  
555 555  
... ... @@ -569,9 +569,9 @@
569 569  
570 570  == 2.5  Downlink Payload ==
571 571  
572 -By default, NDDS75 prints the downlink payload to console port.
530 +By default, NSE01 prints the downlink payload to console port.
573 573  
574 -[[image:image-20220709100028-1.png]]
532 +[[image:image-20220708133731-5.png]]
575 575  
576 576  
577 577  (((
... ... @@ -607,7 +607,7 @@
607 607  )))
608 608  
609 609  (((
610 -If payload = 0x04FF, it will reset the NDDS75
568 +If payload = 0x04FF, it will reset the NSE01
611 611  )))
612 612  
613 613  
... ... @@ -621,52 +621,76 @@
621 621  
622 622  == 2.6  ​LED Indicator ==
623 623  
582 +(((
583 +The NSE01 has an internal LED which is to show the status of different state.
624 624  
625 -The NDDS75 has an internal LED which is to show the status of different state.
626 626  
627 -
628 -* 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)
586 +* 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)
629 629  * Then the LED will be on for 1 second means device is boot normally.
630 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
588 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
631 631  * For each uplink probe, LED will be on for 500ms.
590 +)))
632 632  
592 +
593 +
594 +
595 +== 2.7  Installation in Soil ==
596 +
597 +__**Measurement the soil surface**__
598 +
633 633  (((
634 -
600 +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]]
635 635  )))
636 636  
603 +[[image:1657259653666-883.png]] ​
637 637  
638 638  
639 -== 2.7  ​Firmware Change Log ==
606 +(((
607 +
640 640  
641 -
642 642  (((
643 -Download URL & Firmware Change log
610 +Dig a hole with diameter > 20CM.
644 644  )))
645 645  
646 646  (((
647 -[[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/]]
614 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
648 648  )))
616 +)))
649 649  
618 +[[image:1654506665940-119.png]]
650 650  
651 651  (((
652 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
621 +
653 653  )))
654 654  
655 655  
625 +== 2.8  ​Firmware Change Log ==
656 656  
657 -== 2.8  ​Battery Analysis ==
658 658  
659 -=== 2.8.1  ​Battery Type ===
628 +Download URL & Firmware Change log
660 660  
630 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
661 661  
632 +
633 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
634 +
635 +
636 +
637 +== 2.9  ​Battery Analysis ==
638 +
639 +=== 2.9.1  ​Battery Type ===
640 +
641 +
662 662  (((
663 -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.
643 +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.
664 664  )))
665 665  
646 +
666 666  (((
667 667  The battery is designed to last for several years depends on the actually use environment and update interval. 
668 668  )))
669 669  
651 +
670 670  (((
671 671  The battery related documents as below:
672 672  )))
... ... @@ -676,12 +676,12 @@
676 676  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
677 677  
678 678  (((
679 -[[image:image-20220709101450-2.png]]
661 +[[image:image-20220708140453-6.png]]
680 680  )))
681 681  
682 682  
683 683  
684 -=== 2.8.2  Power consumption Analyze ===
666 +=== 2.9.2  Power consumption Analyze ===
685 685  
686 686  (((
687 687  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.
... ... @@ -715,11 +715,11 @@
715 715  And the Life expectation in difference case will be shown on the right.
716 716  )))
717 717  
718 -[[image:image-20220709110451-3.png]]
700 +[[image:image-20220708141352-7.jpeg]]
719 719  
720 720  
721 721  
722 -=== 2.8.3  ​Battery Note ===
704 +=== 2.9.3  ​Battery Note ===
723 723  
724 724  (((
725 725  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.
... ... @@ -727,10 +727,10 @@
727 727  
728 728  
729 729  
730 -=== 2.8.4  Replace the battery ===
712 +=== 2.9.4  Replace the battery ===
731 731  
732 732  (((
733 -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).
715 +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).
734 734  )))
735 735  
736 736  
... ... @@ -745,7 +745,7 @@
745 745  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/]] 
746 746  )))
747 747  
748 -[[image:1657333200519-600.png]]
730 +[[image:1657261278785-153.png]]
749 749  
750 750  
751 751  
... ... @@ -753,7 +753,7 @@
753 753  
754 754  == 4.1  Access AT Commands ==
755 755  
756 -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/]]
738 +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/]]
757 757  
758 758  
759 759  AT+<CMD>?  : Help on <CMD>
... ... @@ -841,11 +841,18 @@
841 841  )))
842 842  
843 843  (((
844 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
826 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
845 845  )))
846 846  
847 847  
848 848  
831 +== 5.2  Can I calibrate NSE01 to different soil types? ==
832 +
833 +(((
834 +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]].
835 +)))
836 +
837 +
849 849  = 6.  Trouble Shooting =
850 850  
851 851  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -873,7 +873,7 @@
873 873  = 7. ​ Order Info =
874 874  
875 875  
876 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
865 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
877 877  
878 878  
879 879  (% class="wikigeneratedid" %)
... ... @@ -888,7 +888,7 @@
888 888  
889 889  (% style="color:#037691" %)**Package Includes**:
890 890  
891 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
880 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
892 892  * External antenna x 1
893 893  )))
894 894  
... ... @@ -897,11 +897,8 @@
897 897  
898 898  (% style="color:#037691" %)**Dimension and weight**:
899 899  
900 -
901 -* Device Size: 13.0 x 5 x 4.5 cm
902 -* Device Weight: 150g
903 -* Package Size / pcs : 15 x 12x 5.5 cm
904 -* Weight / pcs : 220g
889 +* Size: 195 x 125 x 55 mm
890 +* Weight:   420g
905 905  )))
906 906  
907 907  (((
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
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-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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0