Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 77.1
edited by Xiaoling
on 2022/07/09 09:04
Change comment: Uploaded new attachment "1657328659945-416.png", version {1}
To version 125.4
edited by Xiaoling
on 2022/09/09 15:57
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual
Content
... ... @@ -1,41 +1,56 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:1657348034241-728.png||height="470" width="470"]]
3 3  
4 4  
5 5  
6 6  
7 7  
8 -**Table of Contents:**
9 9  
10 10  
10 +**Table of Contents:**
11 11  
12 +{{toc/}}
12 12  
13 13  
14 14  
15 15  
17 +
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 19  
21 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
22 +
20 20  (((
21 21  
22 22  
23 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.
27 +The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
30 30  )))
31 31  
30 +(((
31 +The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
32 +)))
33 +
34 +(((
35 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 +)))
37 +
38 +(((
39 +N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
40 +)))
41 +
42 +(((
32 32  
33 33  )))
34 34  
35 -[[image:1654503236291-817.png]]
46 +(((
47 +~* make sure you have NB-IoT coverage locally.
48 +)))
36 36  
50 +
51 +)))
37 37  
38 -[[image:1657327959271-447.png]]
53 +[[image:1657348284168-431.png]]
39 39  
40 40  
41 41  
... ... @@ -43,20 +43,17 @@
43 43  
44 44  
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
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
61 +* Monitor Temperature & Humidity via SHT31
51 51  * AT Commands to change parameters
52 52  * Uplink on periodically
53 53  * Downlink to change configure
54 54  * IP66 Waterproof Enclosure
66 +* Ultra-Low Power consumption
67 +* AT Commands to change parameters
55 55  * Micro SIM card slot for NB-IoT SIM
56 56  * 8500mAh Battery for long term use
57 57  
58 58  
59 -
60 60  == 1.3  Specification ==
61 61  
62 62  
... ... @@ -74,7 +74,6 @@
74 74  * - B20 @H-FDD: 800MHz
75 75  * - B28 @H-FDD: 700MHz
76 76  
77 -
78 78  (% style="color:#037691" %)**Battery:**
79 79  
80 80  * Li/SOCI2 un-chargeable battery
... ... @@ -84,16 +84,9 @@
84 84  * Max boost current: 2A, 1 second
85 85  
86 86  
87 -(% style="color:#037691" %)**Power Consumption**
88 -
89 -* STOP Mode: 10uA @ 3.3v
90 -* Max transmit power: 350mA@3.3v
91 -
92 -
93 -
94 -
95 95  == ​1.4  Applications ==
96 96  
100 +
97 97  * Smart Buildings & Home Automation
98 98  * Logistics and Supply Chain Management
99 99  * Smart Metering
... ... @@ -106,61 +106,142 @@
106 106  
107 107  
108 108  
109 -== 1.5  Pin Definitions ==
110 110  
114 +== 1.5  Pin Definitions & Switch ==
111 111  
112 -[[image:1657328609906-564.png]]
113 113  
117 +N95S31B use the mother board from NBSN95 which as below.
114 114  
115 115  
120 +[[image:image-20220709144723-1.png]]
116 116  
117 -= 2.  Use NSE01 to communicate with IoT Server =
118 118  
123 +
124 +=== 1.5.1 Jumper JP2 ===
125 +
126 +
127 +Power on Device when put this jumper.
128 +
129 +
130 +
131 +=== 1.5.2 BOOT MODE / SW1 ===
132 +
133 +
134 +(((
135 +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.
136 +)))
137 +
138 +(((
139 +2) Flash: work mode, device starts to work and send out console output for further debug
140 +)))
141 +
142 +
143 +
144 +=== 1.5.3 Reset Button ===
145 +
146 +
147 +Press to reboot the device.
148 +
149 +
150 +
151 +=== 1.5.4 LED ===
152 +
153 +
154 +It will flash:
155 +
156 +1. When boot the device in flash mode
157 +1. Send an uplink packet
158 +
159 +
160 += 2.  Use N95S31B to communicate with IoT Server =
161 +
162 +
119 119  == 2.1  How it works ==
120 120  
121 121  
122 122  (((
123 -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.
167 +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.
124 124  )))
125 125  
126 126  
127 127  (((
128 -The diagram below shows the working flow in default firmware of NSE01:
172 +The diagram below shows the working flow in default firmware of N95S31B:
129 129  )))
130 130  
131 -[[image:image-20220708101605-2.png]]
175 +(((
176 +
177 +)))
132 132  
179 +[[image:1657520100595-569.png]]
180 +
133 133  (((
134 134  
135 135  )))
136 136  
137 137  
186 +== 2.2 ​ Configure the N95S31B ==
138 138  
139 -== 2.2 ​ Configure the NSE01 ==
140 140  
189 +=== 2.2.1  Power On N95S31B ===
141 141  
191 +
192 +[[image:image-20220709150546-2.png]]
193 +
194 +
195 +
142 142  === 2.2.1 Test Requirement ===
143 143  
144 144  
145 145  (((
146 -To use NSE01 in your city, make sure meet below requirements:
200 +To use N95S31B in your city, make sure meet below requirements:
147 147  )))
148 148  
149 -* Your local operator has already distributed a NB-IoT Network there.
150 -* The local NB-IoT network used the band that NSE01 supports.
151 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
203 +* (((
204 +Your local operator has already distributed a NB-IoT Network there.
205 +)))
206 +* (((
207 +The local NB-IoT network used the band that N95S31B supports.
208 +)))
209 +* (((
210 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
211 +)))
152 152  
153 153  (((
154 -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
214 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
155 155  )))
156 156  
217 +(((
218 +N95S31B supports different communication protocol such as :
219 +)))
157 157  
158 -[[image:1657249419225-449.png]]
221 +(((
222 +* (((
223 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
224 +)))
225 +* (((
226 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
227 +)))
228 +* (((
229 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
230 +)))
231 +* (((
232 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
233 +)))
159 159  
235 +(((
236 +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.
237 +)))
160 160  
239 +
240 +)))
161 161  
162 -=== 2.2.2 Insert SIM card ===
242 +[[image:1657350625843-586.png]]
163 163  
244 +
245 +
246 +=== 2.2.3  Insert SIM card ===
247 +
248 +
164 164  (((
165 165  Insert the NB-IoT Card get from your provider.
166 166  )))
... ... @@ -170,19 +170,24 @@
170 170  )))
171 171  
172 172  
173 -[[image:1657249468462-536.png]]
258 +[[image:1657351240556-536.png]]
174 174  
175 175  
176 176  
177 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
262 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
178 178  
264 +
179 179  (((
180 180  (((
181 -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.
267 +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.
268 +
269 +
182 182  )))
183 183  )))
184 184  
273 +[[image:1657351312545-300.png]]
185 185  
275 +
186 186  **Connection:**
187 187  
188 188   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -201,286 +201,362 @@
201 201  * Flow Control: (% style="color:green" %)**None**
202 202  
203 203  (((
204 -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.
294 +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.
205 205  )))
206 206  
207 -[[image:image-20220708110657-3.png]]
297 +[[image:1657329814315-101.png]]
208 208  
299 +
209 209  (((
210 -(% 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/]]
301 +(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
211 211  )))
212 212  
213 213  
214 214  
215 -=== 2.2.4 Use CoAP protocol to uplink data ===
306 +=== 2.2.5  Use CoAP protocol to uplink data ===
216 216  
217 -(% 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/]]
218 218  
309 +(% 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/]]**
219 219  
311 +
312 +(((
220 220  **Use below commands:**
314 +)))
221 221  
222 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
223 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
224 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
316 +* (((
317 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
318 +)))
319 +* (((
320 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
321 +)))
322 +* (((
323 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
324 +)))
225 225  
326 +(((
327 +
328 +
226 226  For parameter description, please refer to AT command set
330 +)))
227 227  
228 -[[image:1657249793983-486.png]]
332 +[[image:1657352146020-183.png]]
229 229  
230 230  
231 -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.
335 +(((
336 +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.
337 +)))
232 232  
233 -[[image:1657249831934-534.png]]
339 +[[image:1657352185396-303.png]]
234 234  
235 235  
236 236  
237 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
343 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
238 238  
239 -This feature is supported since firmware version v1.0.1
240 240  
241 -
242 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
346 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
243 243  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
244 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
348 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
245 245  
246 -[[image:1657249864775-321.png]]
350 +[[image:1657352391268-297.png]]
247 247  
248 248  
249 -[[image:1657249930215-289.png]]
353 +[[image:1657352403317-397.png]]
250 250  
251 251  
252 252  
253 -=== 2.2.6 Use MQTT protocol to uplink data ===
357 +=== 2.2.7  Use MQTT protocol to uplink data ===
254 254  
255 -This feature is supported since firmware version v110
256 256  
360 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
257 257  
258 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
259 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
260 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
261 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
262 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
263 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
264 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
362 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
363 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
364 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
365 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
366 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
367 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
368 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
265 265  
266 -[[image:1657249978444-674.png]]
370 +[[image:1657352634421-276.png]]
267 267  
268 268  
269 -[[image:1657249990869-686.png]]
373 +[[image:1657352645687-385.png]]
270 270  
271 271  
272 272  (((
273 -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.
377 +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.
274 274  )))
275 275  
276 276  
381 +(((
382 +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.
383 +)))
277 277  
278 -=== 2.2.7 Use TCP protocol to uplink data ===
279 279  
280 -This feature is supported since firmware version v110
281 281  
387 +=== 2.2.8  Use TCP protocol to uplink data ===
282 282  
389 +
390 +This feature is supported since firmware version v110
391 +
283 283  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
284 284  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
285 285  
286 -[[image:1657250217799-140.png]]
395 +[[image:1657352898400-901.png]]
287 287  
288 288  
289 -[[image:1657250255956-604.png]]
398 +[[image:1657352914475-252.png]]
290 290  
291 291  
292 292  
293 -=== 2.2.8 Change Update Interval ===
402 +=== 2.2.9  Change Update Interval ===
294 294  
404 +
295 295  User can use below command to change the (% style="color:green" %)**uplink interval**.
296 296  
297 297  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
298 298  
299 299  (((
300 -(% style="color:red" %)**NOTE:**
410 +
301 301  )))
302 302  
303 303  (((
304 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
414 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:**
305 305  )))
306 306  
417 +(((
418 +(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
419 +)))
307 307  
308 308  
422 +
309 309  == 2.3  Uplink Payload ==
310 310  
311 -In this mode, uplink payload includes in total 18 bytes
312 312  
313 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
314 -|=(% style="width: 60px;" %)(((
315 -**Size(bytes)**
316 -)))|=(% 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**
317 -|(% 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"]]
318 -
319 319  (((
320 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
427 +N95S31B has different working modes for the connections of different types of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
321 321  )))
322 322  
323 323  
324 -[[image:image-20220708111918-4.png]]
325 -
326 -
327 -The payload is ASCII string, representative same HEX:
328 -
329 -0x72403155615900640c7817075e0a8c02f900 where:
330 -
331 -* Device ID: 0x 724031556159 = 724031556159
332 -* Version: 0x0064=100=1.0.0
333 -
334 -* BAT: 0x0c78 = 3192 mV = 3.192V
335 -* Singal: 0x17 = 23
336 -* Soil Moisture: 0x075e= 1886 = 18.86  %
337 -* Soil Temperature:0x0a8c =2700=27 °C
338 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
339 -* Interrupt: 0x00 = 0
340 -
341 -== 2.4  Payload Explanation and Sensor Interface ==
342 -
343 -
344 -=== 2.4.1  Device ID ===
345 -
346 346  (((
347 -By default, the Device ID equal to the last 6 bytes of IMEI.
432 +For example:
348 348  )))
349 349  
350 350  (((
351 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
436 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
352 352  )))
353 353  
439 +
354 354  (((
355 -**Example:**
441 +The uplink payloads are composed in  ASCII String. For example:
356 356  )))
357 357  
358 358  (((
359 -AT+DEUI=A84041F15612
445 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
360 360  )))
361 361  
362 362  (((
363 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
449 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
364 364  )))
365 365  
366 366  
367 -
368 -=== 2.4.2  Version Info ===
369 -
370 370  (((
371 -Specify the software version: 0x64=100, means firmware version 1.00.
454 +(% style="color:red" %)**NOTE:**
372 372  )))
373 373  
374 -(((
375 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
457 +(% style="color:red" %)
458 +1. (((
459 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].**
376 376  )))
461 +1. (((
462 +**By default, the device will send an uplink message every 1 hour.**
377 377  
378 378  
379 379  
380 -=== 2.4.3  Battery Info ===
381 -
382 -(((
383 -Check the battery voltage for LSE01.
466 +
384 384  )))
385 385  
386 -(((
387 -Ex1: 0x0B45 = 2885mV
388 -)))
469 +=== 2.3.1  Payload Analyze ===
389 389  
390 -(((
391 -Ex2: 0x0B49 = 2889mV
392 -)))
393 393  
472 +==== 2.3.1.1  Before Firmware v1.2 ====
394 394  
395 395  
396 -=== 2.4.4  Signal Strength ===
475 +N95S31B uplink payload includes in total 21 bytes
397 397  
477 +
478 +(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
479 +|=(% style="width: 60px;" %)(((
480 +**Size(bytes)**
481 +)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2**
482 +|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:174px" %)(((
398 398  (((
399 -NB-IoT Network signal Strength.
484 +Reserve/ Same as NBSN95 CFGMOD=1
400 400  )))
401 401  
402 402  (((
403 -**Ex1: 0x1d = 29**
488 +No function here.
404 404  )))
405 -
490 +)))|(% style="width:106px" %)(((
406 406  (((
407 -(% style="color:blue" %)**0**(%%)  -113dBm or less
492 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
408 408  )))
409 409  
410 410  (((
411 -(% style="color:blue" %)**1**(%%)  -111dBm
496 +By SHT31
412 412  )))
413 -
498 +)))|(% style="width:85px" %)(((
414 414  (((
415 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
500 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
416 416  )))
417 417  
418 418  (((
419 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
504 +By SHT31
420 420  )))
506 +)))
421 421  
422 422  (((
423 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
509 +
510 +
511 +(((
512 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
424 424  )))
514 +)))
425 425  
426 426  
517 +[[image:1657354294009-643.png]]
427 427  
428 -=== 2.4.5  Soil Moisture ===
429 429  
430 -(((
431 -(((
432 -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.
433 -)))
434 -)))
520 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
435 435  
436 -(((
437 -(((
438 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
439 -)))
440 -)))
522 +* Device ID:  0x724031607457 = 724031607457
441 441  
524 +* Version:  0x006e=110=1.1.0
525 +
526 +* BAT:  0x0ccd = 3277 mV = 3.277V
527 +
528 +* Signal:  0x1b = 27
529 +
530 +* Model:  0x01 = 1
531 +
532 +* 0x00dc000ccc= reserve, ignore in N95S31B
533 +
534 +* Temperature by SHT31:  0x00e1 = 225 = 22.5 °C
535 +
536 +* Humidity by SHT31:  0x0186 = 390 = 39.0 %rh
537 +
442 442  (((
443 443  
444 -)))
445 445  
446 -(((
447 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
541 +
542 +
448 448  )))
449 449  
545 +==== 2.3.1.2 Since Firmware v1.2 ====
450 450  
451 451  
452 -=== 2.4.6  Soil Temperature ===
548 +In this mode, uplink payload includes 91 bytes in total by default.
453 453  
550 +Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
551 +
552 +
553 +(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
554 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:82px" %)**8**|(% style="width:43px" %)**2**|(% style="width:47px" %)**2**|(% style="width:124px" %)**1**|(% style="width:56px" %)**1**|(% style="width:109px" %)**2**|(% style="width:80px" %)**1**|(% style="width:51px" %)**2**|(% style="width:79px" %)**2**|(% style="width:84px" %)**2**|(% style="width:100px" %)**4**|(% style="width:76px" %)**2**|(% style="width:81px" %)**2**|(% style="width:121px" %)**4**
555 +|(% style="width:95px" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp .....
556 +
557 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
558 +
559 +
560 +[[image:image-20220908154949-1.png]]
561 +
562 +
563 +The payload is ASCII string, representative same HEX:
564 +
565 +0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where:
566 +
567 +* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
568 +
569 +* (% style="color:blue" %)Version: 0x000c=120=1.2
570 +
571 +* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
572 +
573 +* (% style="color:red" %)Singal: 0x0c = 12
574 +
575 +* (% style="color:blue" %)Mod: 0x01 = 1
576 +
577 +* TemDS18B20: 0x0000= 0 = 0
578 +
579 +* (% style="color:green" %)Interrupt: 0x00= 0
580 +
581 +* (% style="color:green" %)adc: 0x0030= 48
582 +
583 +* SHTTEM: 0x0114= 276 = 27.6
584 +
585 +* SHTHUM:0x0231 =561=56.1%
586 +
587 +* (% style="color:red" %)Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
588 +
589 +* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
590 +
591 +* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,.......
592 +
593 +
594 +
595 +
596 +=== 2.3.2  Device ID ===
597 +
598 +
454 454  (((
455 -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
600 +By default, the Device ID equal to the last 6 bytes of IMEI.
456 456  )))
457 457  
458 458  (((
459 -**Example**:
604 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
605 +
606 +
460 460  )))
461 461  
462 462  (((
463 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
610 +** (% style="color:blue" %)Example:**
464 464  )))
465 465  
466 466  (((
467 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
614 +AT+DEUI=A84041F15612
468 468  )))
469 469  
617 +(((
618 +The Device ID is stored in a none-erase area, Upgrade the firmware or run ** (% style="color:blue" %)AT+FDR**(%%) won't erase Device ID.
470 470  
620 +
621 +)))
471 471  
472 -=== 2.4.7  Soil Conductivity (EC) ===
623 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:**
473 473  
625 +
626 +By default, the Device ID equal to the last 15 bits of IMEI.
627 +
628 +User can use ** (% style="color:blue" %)AT+DEUI**(%%) to set Device ID
629 +
630 +
631 +** (% style="color:blue" %)Example:**
632 +
633 +AT+DEUI=868411056754138
634 +
635 +
636 +
637 +=== 2.3.3  Version Info ===
638 +
639 +
474 474  (((
475 -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).
641 +These bytes include the hardware and software version.
476 476  )))
477 477  
478 478  (((
479 -For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
645 +Higher byte: Specify hardware version: always 0x00 for N95S31B
480 480  )))
481 481  
482 482  (((
483 -Generally, the EC value of irrigation water is less than 800uS / cm.
649 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
484 484  )))
485 485  
486 486  (((
... ... @@ -488,71 +488,87 @@
488 488  )))
489 489  
490 490  (((
491 -
657 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
492 492  )))
493 493  
494 -=== 2.4.8  Digital Interrupt ===
495 -
496 496  (((
497 -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.
661 +
498 498  )))
499 499  
664 +
665 +=== 2.3.4  Battery Info ===
666 +
667 +
500 500  (((
501 -The command is:
669 +Ex1: 0x0B45 = 2885mV
502 502  )))
503 503  
504 504  (((
505 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
673 +Ex2: 0x0B49 = 2889mV
506 506  )))
507 507  
508 508  
509 -(((
510 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
511 -)))
512 512  
678 +=== 2.3.5  Signal Strength ===
513 513  
680 +
514 514  (((
515 -Example:
682 +NB-IoT Network signal Strength.
516 516  )))
517 517  
518 518  (((
519 -0x(00): Normal uplink packet.
686 +**Ex1: 0x1d = 29**
520 520  )))
521 521  
522 522  (((
523 -0x(01): Interrupt Uplink Packet.
690 +(% style="color:blue" %)**0**(%%)  -113dBm or less
524 524  )))
525 525  
526 -
527 -
528 -=== 2.4.9  ​+5V Output ===
529 -
530 530  (((
531 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
694 +(% style="color:blue" %)**1**(%%)  -111dBm
532 532  )))
533 533  
534 -
535 535  (((
536 -The 5V output time can be controlled by AT Command.
698 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
537 537  )))
538 538  
539 539  (((
540 -(% style="color:blue" %)**AT+5VT=1000**
702 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
541 541  )))
542 542  
543 543  (((
544 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
706 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
545 545  )))
546 546  
547 547  
548 548  
549 -== 2.5  Downlink Payload ==
711 +=== 2.3.6  Temperature & Humidity ===
550 550  
551 -By default, NSE01 prints the downlink payload to console port.
552 552  
553 -[[image:image-20220708133731-5.png]]
714 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
554 554  
716 +[[image:image-20220709161741-3.png]]
555 555  
718 +
719 +Convert the read byte to decimal and divide it by ten.
720 +
721 +
722 +**Example:**
723 +
724 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
725 +
726 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
727 +
728 +
729 +
730 +== 2.4  Downlink Payload ==
731 +
732 +
733 +By default, N95S31B prints the downlink payload to console port.
734 +
735 +[[image:image-20220709100028-1.png]]
736 +
737 +
556 556  (((
557 557  (% style="color:blue" %)**Examples:**
558 558  )))
... ... @@ -586,7 +586,7 @@
586 586  )))
587 587  
588 588  (((
589 -If payload = 0x04FF, it will reset the NSE01
771 +If payload = 0x04FF, it will reset the N95S31B
590 590  )))
591 591  
592 592  
... ... @@ -597,79 +597,67 @@
597 597  )))
598 598  
599 599  
782 +== 2.5 Humidity and Temperature alarm function ==
600 600  
601 -== 2.6  ​LED Indicator ==
784 +➢ AT Command:
602 602  
603 -(((
604 -The NSE01 has an internal LED which is to show the status of different state.
786 +AT+ SHHUM=min,max
605 605  
788 +² When min=0, and max≠0, Alarm higher than max
606 606  
607 -* 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)
608 -* Then the LED will be on for 1 second means device is boot normally.
609 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
610 -* For each uplink probe, LED will be on for 500ms.
611 -)))
790 +² When min≠0, and max=0, Alarm lower than min
612 612  
792 +² When min≠0 and max≠0, Alarm higher than max or lower than min
613 613  
794 +Example:
614 614  
796 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
615 615  
616 -== 2.7  Installation in Soil ==
617 617  
618 -__**Measurement the soil surface**__
799 +AT+ SHTEMP=min,max
619 619  
620 -(((
621 -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]]
622 -)))
801 +² When min=0, and max≠0, Alarm higher than max
623 623  
624 -[[image:1657259653666-883.png]] ​
803 +² When min≠0, and max=0, Alarm lower than min
625 625  
805 +² When min≠0 and max≠0, Alarm higher than max or lower than min
626 626  
627 -(((
628 -
807 +Example:
629 629  
630 -(((
631 -Dig a hole with diameter > 20CM.
632 -)))
809 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
633 633  
634 -(((
635 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
636 -)))
637 -)))
811 +== 2.6 Set the number of data to be uploaded and the recording time ==
638 638  
639 -[[image:1654506665940-119.png]]
813 +➢ AT Command:
640 640  
641 -(((
642 -
643 -)))
815 +AT+TR=900  ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
644 644  
817 +AT+NOUD=8  ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
645 645  
646 -== 2.8  ​Firmware Change Log ==
819 +== 2.7 Read or Clear cached data ==
647 647  
821 +➢ AT Command:
648 648  
649 -Download URL & Firmware Change log
823 +AT+CDP ~/~/ Read cached data
650 650  
651 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
825 +[[image:image-20220908163102-2.png]]
652 652  
827 +AT+CDP=0 ~/~/ Clear cached data
653 653  
654 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
829 +== 2.8  ​Battery Analysis ==
655 655  
656 656  
832 +=== 2.8.1  ​Battery Type ===
657 657  
658 -== 2.9  ​Battery Analysis ==
659 659  
660 -=== 2.9.1  ​Battery Type ===
661 -
662 -
663 663  (((
664 -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.
836 +The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
665 665  )))
666 666  
667 -
668 668  (((
669 669  The battery is designed to last for several years depends on the actually use environment and update interval. 
670 670  )))
671 671  
672 -
673 673  (((
674 674  The battery related documents as below:
675 675  )))
... ... @@ -679,61 +679,42 @@
679 679  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
680 680  
681 681  (((
682 -[[image:image-20220708140453-6.png]]
852 +[[image:image-20220709101450-2.png]]
683 683  )))
684 684  
685 685  
686 686  
687 -=== 2.9.2  Power consumption Analyze ===
857 +=== 2.8.2  Power consumption Analyze ===
688 688  
689 -(((
690 -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.
691 -)))
692 692  
693 -
694 694  (((
695 -Instruction to use as below:
861 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
696 696  )))
697 697  
698 698  (((
699 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
865 +
700 700  )))
701 701  
702 702  
703 -(((
704 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
705 -)))
869 +=== 2.8.3  ​Battery Note ===
706 706  
707 -* (((
708 -Product Model
709 -)))
710 -* (((
711 -Uplink Interval
712 -)))
713 -* (((
714 -Working Mode
715 -)))
716 716  
717 717  (((
718 -And the Life expectation in difference case will be shown on the right.
873 +The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
719 719  )))
720 720  
721 -[[image:image-20220708141352-7.jpeg]]
722 722  
723 723  
878 +=== 2.8.4  Replace the battery ===
724 724  
725 -=== 2.9.3  ​Battery Note ===
726 726  
727 727  (((
728 -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.
882 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
729 729  )))
730 730  
731 731  
732 -
733 -=== 2.9.4  Replace the battery ===
734 -
735 735  (((
736 -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).
887 +The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
737 737  )))
738 738  
739 739  
... ... @@ -740,6 +740,7 @@
740 740  
741 741  = 3. ​ Access NB-IoT Module =
742 742  
894 +
743 743  (((
744 744  Users can directly access the AT command set of the NB-IoT module.
745 745  )))
... ... @@ -746,19 +746,23 @@
746 746  
747 747  (((
748 748  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/]] 
901 +
902 +
749 749  )))
750 750  
751 -[[image:1657261278785-153.png]]
905 +[[image:1657333200519-600.png]]
752 752  
753 753  
754 754  
755 755  = 4.  Using the AT Commands =
756 756  
911 +
757 757  == 4.1  Access AT Commands ==
758 758  
759 -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/]]
760 760  
915 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
761 761  
917 +
762 762  AT+<CMD>?  : Help on <CMD>
763 763  
764 764  AT+<CMD>         : Run <CMD>
... ... @@ -798,7 +798,24 @@
798 798  
799 799  AT+SERVADDR  : Server Address
800 800  
957 +AT+TR      : Get or Set record time
801 801  
959 +AT+APN     : Get or set the APN
960 +
961 +AT+FBAND   : Get or Set whether to automatically modify the frequency band
962 +
963 +AT+DNSCFG  : Get or Set DNS Server
964 +
965 +AT+GETSENSORVALUE   : Returns the current sensor measurement
966 +
967 +AT+NOUD      : Get or Set the number of data to be uploaded
968 +
969 +AT+CDP     : Read or Clear cached data
970 +
971 +AT+SHTEMP: Get or Set alarm of temp
972 +
973 +AT+SHHUM: Get or Set alarm of moisture
974 +
802 802  (% style="color:#037691" %)**COAP Management**      
803 803  
804 804  AT+URI            : Resource parameters
... ... @@ -832,6 +832,7 @@
832 832  
833 833  = ​5.  FAQ =
834 834  
1008 +
835 835  == 5.1 ​ How to Upgrade Firmware ==
836 836  
837 837  
... ... @@ -844,20 +844,18 @@
844 844  )))
845 845  
846 846  (((
847 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
848 -)))
1021 +
849 849  
850 -
851 -
852 -== 5.2  Can I calibrate NSE01 to different soil types? ==
853 -
854 854  (((
855 -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]].
1024 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.**
856 856  )))
1026 +)))
857 857  
858 858  
1029 +
859 859  = 6.  Trouble Shooting =
860 860  
1032 +
861 861  == 6.1  ​Connection problem when uploading firmware ==
862 862  
863 863  
... ... @@ -873,6 +873,7 @@
873 873  
874 874  == 6.2  AT Command input doesn't work ==
875 875  
1048 +
876 876  (((
877 877  In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
878 878  
... ... @@ -883,7 +883,7 @@
883 883  = 7. ​ Order Info =
884 884  
885 885  
886 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
1059 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
887 887  
888 888  
889 889  (% class="wikigeneratedid" %)
... ... @@ -898,7 +898,7 @@
898 898  
899 899  (% style="color:#037691" %)**Package Includes**:
900 900  
901 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
1074 +* N95S31B NB-IoT Temperature and Humidity Sensor
902 902  * External antenna x 1
903 903  )))
904 904  
... ... @@ -907,8 +907,10 @@
907 907  
908 908  (% style="color:#037691" %)**Dimension and weight**:
909 909  
910 -* Size: 195 x 125 x 55 mm
911 -* Weight:   420g
1083 +* Device Size: 13.0 x 5 x 4.5 cm
1084 +* Device Weight: 150g
1085 +* Package Size / pcs : 14.0 x 8x 5 cm
1086 +* Weight / pcs : 180g
912 912  )))
913 913  
914 914  (((
... ... @@ -920,5 +920,6 @@
920 920  
921 921  = 9.  Support =
922 922  
1098 +
923 923  * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
924 924  * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]
1657328756309-230.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.5 KB
Content
1657328884227-504.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657329814315-101.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.3 KB
Content
1657330452568-615.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +71.3 KB
Content
1657330472797-498.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +68.9 KB
Content
1657330501006-241.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +119.2 KB
Content
1657330533775-472.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.9 KB
Content
1657330723006-866.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content
1657331036973-987.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +83.8 KB
Content
1657332990863-496.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.2 KB
Content
1657333200519-600.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657348034241-728.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
image-20220709092052-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +247.3 KB
Content
image-20220709093918-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +42.2 KB
Content
image-20220709093918-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +61.9 KB
Content
image-20220709100028-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +8.8 KB
Content
image-20220709101450-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +138.5 KB
Content
image-20220709110451-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +611.5 KB
Content
image-20220709144723-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content
image-20220908154949-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +58.5 KB
Content
image-20220908163102-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.David
Size
... ... @@ -1,0 +1,1 @@
1 +29.7 KB
Content