Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 114.2 >
edited by Xiaoling
on 2022/07/09 16:12
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,7 +53,6 @@
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
56 -
57 57  == 1.3  Specification ==
58 58  
59 59  
... ... @@ -71,129 +71,75 @@
71 71  * - B20 @H-FDD: 800MHz
72 72  * - B28 @H-FDD: 700MHz
73 73  
74 -(% style="color:#037691" %)**Battery:**
74 +Probe(% style="color:#037691" %)** Specification:**
75 75  
76 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
76 76  
77 -* Li/SOCI2 un-chargeable battery
78 -* Capacity: 8500mAh
79 -* Self Discharge: <1% / Year @ 25°C
80 -* Max continuously current: 130mA
81 -* Max boost current: 2A, 1 second
78 +[[image:image-20220708101224-1.png]]
82 82  
83 83  
81 +
84 84  == ​1.4  Applications ==
85 85  
86 -* Smart Buildings & Home Automation
87 -* Logistics and Supply Chain Management
88 -* Smart Metering
89 89  * Smart Agriculture
90 -* Smart Cities
91 -* Smart Factory
92 92  
93 93  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
94 94  ​
95 95  
96 -
97 97  == 1.5  Pin Definitions ==
98 98  
99 -N95S31B use the mother board from NBSN95 which as below.
100 100  
101 -[[image:image-20220709144723-1.png]]
92 +[[image:1657246476176-652.png]]
102 102  
103 103  
104 -=== 1.5.1 Jumper JP2 ===
105 105  
106 -Power on Device when put this jumper.
96 += 2.  Use NSE01 to communicate with IoT Server =
107 107  
108 -
109 -
110 -=== 1.5.2 BOOT MODE / SW1 ===
111 -
112 -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.
113 -
114 -2) Flash: work mode, device starts to work and send out console output for further debug
115 -
116 -
117 -
118 -=== 1.5.3 Reset Button ===
119 -
120 -Press to reboot the device.
121 -
122 -
123 -
124 -=== 1.5.4 LED ===
125 -
126 -It will flash:
127 -
128 -1. When boot the device in flash mode
129 -1. Send an uplink packet
130 -
131 -
132 -
133 -= 2.  Use N95S31B to communicate with IoT Server =
134 -
135 135  == 2.1  How it works ==
136 136  
137 137  
138 138  (((
139 -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.
140 140  )))
141 141  
142 142  
143 143  (((
144 -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:
145 145  )))
146 146  
147 -(((
148 -
149 -)))
110 +[[image:image-20220708101605-2.png]]
150 150  
151 -[[image:1657350248151-650.png]]
152 -
153 153  (((
154 154  
155 155  )))
156 156  
157 157  
158 -== 2.2 ​ Configure the N95S31B ==
159 159  
118 +== 2.2 ​ Configure the NSE01 ==
160 160  
161 -=== 2.2.1  Power On N95S31B ===
162 162  
163 -
164 -[[image:image-20220709150546-2.png]]
165 -
166 -
167 167  === 2.2.1 Test Requirement ===
168 168  
169 169  
170 -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 +)))
171 171  
172 172  * Your local operator has already distributed a NB-IoT Network there.
173 -* The local NB-IoT network used the band that N95S31B supports.
129 +* The local NB-IoT network used the band that NSE01 supports.
174 174  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
175 175  
176 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
177 -
178 -N95S31B supports different communication protocol such as :
179 -
180 180  (((
181 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
185 -
186 -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.
187 -
188 -
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
189 189  )))
190 190  
191 -[[image:1657350625843-586.png]]
192 192  
137 +[[image:1657249419225-449.png]]
193 193  
194 194  
195 -=== 2.2.3  Insert SIM card ===
196 196  
141 +=== 2.2.2 Insert SIM card ===
142 +
197 197  (((
198 198  Insert the NB-IoT Card get from your provider.
199 199  )))
... ... @@ -203,19 +203,18 @@
203 203  )))
204 204  
205 205  
206 -[[image:1657351240556-536.png]]
152 +[[image:1657249468462-536.png]]
207 207  
208 208  
209 209  
210 -=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
156 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
211 211  
212 212  (((
213 213  (((
214 -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.
215 215  )))
216 216  )))
217 217  
218 -[[image:1657351312545-300.png]]
219 219  
220 220  **Connection:**
221 221  
... ... @@ -235,110 +235,96 @@
235 235  * Flow Control: (% style="color:green" %)**None**
236 236  
237 237  (((
238 -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.
239 239  )))
240 240  
241 -[[image:1657329814315-101.png]]
186 +[[image:image-20220708110657-3.png]]
242 242  
243 243  (((
244 -(% 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/]]
245 245  )))
246 246  
247 247  
248 248  
249 -=== 2.2.5  Use CoAP protocol to uplink data ===
194 +=== 2.2.4 Use CoAP protocol to uplink data ===
250 250  
251 251  (% 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/]]
252 252  
253 253  
254 -(((
255 255  **Use below commands:**
256 -)))
257 257  
258 -* (((
259 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
260 -)))
261 -* (((
262 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
263 -)))
264 -* (((
265 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
266 -)))
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
267 267  
268 -(((
269 -
270 -
271 271  For parameter description, please refer to AT command set
272 -)))
273 273  
274 -[[image:1657352146020-183.png]]
207 +[[image:1657249793983-486.png]]
275 275  
276 276  
277 -(((
278 -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.
279 -)))
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.
280 280  
281 -[[image:1657352185396-303.png]]
212 +[[image:1657249831934-534.png]]
282 282  
283 283  
284 284  
285 -=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
216 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
286 286  
218 +This feature is supported since firmware version v1.0.1
287 287  
288 -* (% 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
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
290 -* (% 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
291 291  
292 -[[image:1657352391268-297.png]]
225 +[[image:1657249864775-321.png]]
293 293  
294 294  
295 -[[image:1657352403317-397.png]]
228 +[[image:1657249930215-289.png]]
296 296  
297 297  
298 298  
299 -=== 2.2.7  Use MQTT protocol to uplink data ===
232 +=== 2.2.6 Use MQTT protocol to uplink data ===
300 300  
301 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
234 +This feature is supported since firmware version v110
302 302  
303 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
305 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
310 310  
311 -[[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
312 312  
245 +[[image:1657249978444-674.png]]
313 313  
314 -[[image:1657352645687-385.png]]
315 315  
316 -(((
317 -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.
318 -)))
248 +[[image:1657249990869-686.png]]
319 319  
320 320  
321 321  (((
322 -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.
323 323  )))
324 324  
325 325  
326 326  
327 -=== 2.2.8  Use TCP protocol to uplink data ===
257 +=== 2.2.7 Use TCP protocol to uplink data ===
328 328  
329 329  This feature is supported since firmware version v110
330 330  
261 +
331 331  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
332 332  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
333 333  
334 -[[image:1657352898400-901.png]]
265 +[[image:1657250217799-140.png]]
335 335  
336 336  
337 -[[image:1657352914475-252.png]]
268 +[[image:1657250255956-604.png]]
338 338  
339 339  
340 340  
341 -=== 2.2.9  Change Update Interval ===
272 +=== 2.2.8 Change Update Interval ===
342 342  
343 343  User can use below command to change the (% style="color:green" %)**uplink interval**.
344 344  
... ... @@ -345,102 +345,47 @@
345 345  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
346 346  
347 347  (((
348 -
279 +(% style="color:red" %)**NOTE:**
349 349  )))
350 350  
282 +(((
283 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
284 +)))
351 351  
352 352  
287 +
353 353  == 2.3  Uplink Payload ==
354 354  
290 +In this mode, uplink payload includes in total 18 bytes
355 355  
356 -NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
357 -
358 -
359 -For example:
360 -
361 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
362 -
363 -
364 -The uplink payloads are composed in  ASCII String. For example:
365 -
366 -0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
367 -
368 -0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
369 -
370 -
371 -(% style="color:red" %)**NOTE:**
372 -
373 -(% style="color:red" %)
374 -1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 -1. By default, the device will send an uplink message every 1 hour.
376 -
377 -
378 -
379 -
380 -=== 2.3.1  Payload Analyze ===
381 -
382 -N95S31B uplink payload includes in total 21 bytes
383 -
384 -
385 -(% 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" %)
386 386  |=(% style="width: 60px;" %)(((
387 387  **Size(bytes)**
388 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
389 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
390 -Reserve/ Same as NBSN95 CFGMOD=1
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"]]
391 391  
392 -No function here.
393 -)))|(% style="width:77px" %)(((
394 -[[Temperature >>||anchor="H2.4.5A0Distance"]]
395 -
396 -By SHT31
397 -)))|(% style="width:80px" %)(((
398 -[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
399 -
400 -By SHT31
401 -)))
402 -
403 403  (((
404 -(((
405 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor 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.
406 406  )))
407 -)))
408 408  
409 409  
410 -[[image:1657354294009-643.png]]
303 +[[image:image-20220708111918-4.png]]
411 411  
412 -(((
305 +
413 413  The payload is ASCII string, representative same HEX:
414 -)))
415 415  
416 -(((
417 -0x72403155615900640c6c19029200 where:
418 -)))
308 +0x72403155615900640c7817075e0a8c02f900 where:
419 419  
420 -* (((
421 -Device ID: 0x724031556159 = 724031556159
422 -)))
423 -* (((
424 -Version: 0x0064=100=1.0.0
425 -)))
310 +* Device ID: 0x 724031556159 = 724031556159
311 +* Version: 0x0064=100=1.0.0
426 426  
427 -* (((
428 -BAT: 0x0c6c = 3180 mV = 3.180V
429 -)))
430 -* (((
431 -Signal: 0x19 = 25
432 -)))
433 -* (((
434 -Distance: 0x0292= 658 mm
435 -)))
436 -* (((
437 -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
438 438  
439 -
440 -
441 -
442 -)))
443 -
444 444  == 2.4  Payload Explanation and Sensor Interface ==
445 445  
446 446  
... ... @@ -463,7 +463,7 @@
463 463  )))
464 464  
465 465  (((
466 -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.
467 467  )))
468 468  
469 469  
... ... @@ -475,7 +475,7 @@
475 475  )))
476 476  
477 477  (((
478 -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.
479 479  )))
480 480  
481 481  
... ... @@ -483,6 +483,10 @@
483 483  === 2.4.3  Battery Info ===
484 484  
485 485  (((
362 +Check the battery voltage for LSE01.
363 +)))
364 +
365 +(((
486 486  Ex1: 0x0B45 = 2885mV
487 487  )))
488 488  
... ... @@ -524,21 +524,65 @@
524 524  
525 525  
526 526  
527 -=== 2.4.5  Distance ===
407 +=== 2.4.5  Soil Moisture ===
528 528  
529 -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 +)))
530 530  
531 531  (((
532 -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
533 533  )))
419 +)))
534 534  
535 535  (((
422 +
423 +)))
424 +
536 536  (((
537 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
426 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
538 538  )))
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
539 539  )))
540 540  
541 541  (((
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 +(((
542 542  
543 543  )))
544 544  
... ... @@ -546,10 +546,10 @@
546 546  
547 547  )))
548 548  
549 -=== 2.4.6  Digital Interrupt ===
473 +=== 2.4.8  Digital Interrupt ===
550 550  
551 551  (((
552 -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.
553 553  )))
554 554  
555 555  (((
... ... @@ -580,10 +580,10 @@
580 580  
581 581  
582 582  
583 -=== 2.4.7  ​+5V Output ===
507 +=== 2.4.9  ​+5V Output ===
584 584  
585 585  (((
586 -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. 
587 587  )))
588 588  
589 589  
... ... @@ -603,9 +603,9 @@
603 603  
604 604  == 2.5  Downlink Payload ==
605 605  
606 -By default, NDDS75 prints the downlink payload to console port.
530 +By default, NSE01 prints the downlink payload to console port.
607 607  
608 -[[image:image-20220709100028-1.png]]
532 +[[image:image-20220708133731-5.png]]
609 609  
610 610  
611 611  (((
... ... @@ -641,7 +641,7 @@
641 641  )))
642 642  
643 643  (((
644 -If payload = 0x04FF, it will reset the NDDS75
568 +If payload = 0x04FF, it will reset the NSE01
645 645  )))
646 646  
647 647  
... ... @@ -655,52 +655,76 @@
655 655  
656 656  == 2.6  ​LED Indicator ==
657 657  
582 +(((
583 +The NSE01 has an internal LED which is to show the status of different state.
658 658  
659 -The NDDS75 has an internal LED which is to show the status of different state.
660 660  
661 -
662 -* 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)
663 663  * Then the LED will be on for 1 second means device is boot normally.
664 -* 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.
665 665  * For each uplink probe, LED will be on for 500ms.
590 +)))
666 666  
592 +
593 +
594 +
595 +== 2.7  Installation in Soil ==
596 +
597 +__**Measurement the soil surface**__
598 +
667 667  (((
668 -
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]]
669 669  )))
670 670  
603 +[[image:1657259653666-883.png]] ​
671 671  
672 672  
673 -== 2.7  ​Firmware Change Log ==
606 +(((
607 +
674 674  
675 -
676 676  (((
677 -Download URL & Firmware Change log
610 +Dig a hole with diameter > 20CM.
678 678  )))
679 679  
680 680  (((
681 -[[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.
682 682  )))
616 +)))
683 683  
618 +[[image:1654506665940-119.png]]
684 684  
685 685  (((
686 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
621 +
687 687  )))
688 688  
689 689  
625 +== 2.8  ​Firmware Change Log ==
690 690  
691 -== 2.8  ​Battery Analysis ==
692 692  
693 -=== 2.8.1  ​Battery Type ===
628 +Download URL & Firmware Change log
694 694  
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/]]
695 695  
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 +
696 696  (((
697 -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.
698 698  )))
699 699  
646 +
700 700  (((
701 701  The battery is designed to last for several years depends on the actually use environment and update interval. 
702 702  )))
703 703  
651 +
704 704  (((
705 705  The battery related documents as below:
706 706  )))
... ... @@ -710,12 +710,12 @@
710 710  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
711 711  
712 712  (((
713 -[[image:image-20220709101450-2.png]]
661 +[[image:image-20220708140453-6.png]]
714 714  )))
715 715  
716 716  
717 717  
718 -=== 2.8.2  Power consumption Analyze ===
666 +=== 2.9.2  Power consumption Analyze ===
719 719  
720 720  (((
721 721  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.
... ... @@ -749,11 +749,11 @@
749 749  And the Life expectation in difference case will be shown on the right.
750 750  )))
751 751  
752 -[[image:image-20220709110451-3.png]]
700 +[[image:image-20220708141352-7.jpeg]]
753 753  
754 754  
755 755  
756 -=== 2.8.3  ​Battery Note ===
704 +=== 2.9.3  ​Battery Note ===
757 757  
758 758  (((
759 759  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.
... ... @@ -761,10 +761,10 @@
761 761  
762 762  
763 763  
764 -=== 2.8.4  Replace the battery ===
712 +=== 2.9.4  Replace the battery ===
765 765  
766 766  (((
767 -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).
768 768  )))
769 769  
770 770  
... ... @@ -779,7 +779,7 @@
779 779  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/]] 
780 780  )))
781 781  
782 -[[image:1657333200519-600.png]]
730 +[[image:1657261278785-153.png]]
783 783  
784 784  
785 785  
... ... @@ -787,7 +787,7 @@
787 787  
788 788  == 4.1  Access AT Commands ==
789 789  
790 -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/]]
791 791  
792 792  
793 793  AT+<CMD>?  : Help on <CMD>
... ... @@ -875,11 +875,18 @@
875 875  )))
876 876  
877 877  (((
878 -(% 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.
879 879  )))
880 880  
881 881  
882 882  
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 +
883 883  = 6.  Trouble Shooting =
884 884  
885 885  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -907,7 +907,7 @@
907 907  = 7. ​ Order Info =
908 908  
909 909  
910 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
865 +Part Number**:** (% style="color:#4f81bd" %)**NSE01**
911 911  
912 912  
913 913  (% class="wikigeneratedid" %)
... ... @@ -922,7 +922,7 @@
922 922  
923 923  (% style="color:#037691" %)**Package Includes**:
924 924  
925 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
880 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
926 926  * External antenna x 1
927 927  )))
928 928  
... ... @@ -931,11 +931,8 @@
931 931  
932 932  (% style="color:#037691" %)**Dimension and weight**:
933 933  
934 -
935 -* Device Size: 13.0 x 5 x 4.5 cm
936 -* Device Weight: 150g
937 -* Package Size / pcs : 15 x 12x 5.5 cm
938 -* Weight / pcs : 220g
889 +* Size: 195 x 125 x 55 mm
890 +* Weight:   420g
939 939  )))
940 940  
941 941  (((
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
1657354294009-643.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -214.7 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