Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 91.2
edited by Xiaoling
on 2022/07/09 09:58
Change comment: There is no comment for this version
To version 115.2
edited by Xiaoling
on 2022/07/09 16:18
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,62 +1,59 @@
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 12  
13 13  
14 14  
15 15  
16 +
16 16  = 1.  Introduction =
17 17  
18 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
19 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
19 19  
20 20  (((
21 21  
22 22  
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 -)))
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*.
31 31  
32 -
33 -)))
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.
34 34  
35 -[[image:1654503236291-817.png]]
28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
36 36  
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).
37 37  
38 -[[image:1657327959271-447.png]]
39 39  
33 +~* make sure you have NB-IoT coverage locally.
40 40  
35 +
36 +)))
41 41  
38 +[[image:1657348284168-431.png]]
39 +
40 +
41 +
42 42  == 1.2 ​ Features ==
43 43  
44 44  
45 45  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
46 -* 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
46 +* 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
51 +* Ultra-Low Power consumption
52 +* 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  
... ... @@ -76,6 +76,7 @@
76 76  
77 77  (% style="color:#037691" %)**Battery:**
78 78  
76 +
79 79  * Li/SOCI2 un-chargeable battery
80 80  * Capacity: 8500mAh
81 81  * Self Discharge: <1% / Year @ 25°C
... ... @@ -82,11 +82,7 @@
82 82  * Max continuously current: 130mA
83 83  * Max boost current: 2A, 1 second
84 84  
85 -(% style="color:#037691" %)**Power Consumption**
86 86  
87 -* STOP Mode: 10uA @ 3.3v
88 -* Max transmit power: 350mA@3.3v
89 -
90 90  == ​1.4  Applications ==
91 91  
92 92  * Smart Buildings & Home Automation
... ... @@ -100,25 +100,54 @@
100 100  ​
101 101  
102 102  
103 -
104 104  == 1.5  Pin Definitions ==
105 105  
99 +N95S31B use the mother board from NBSN95 which as below.
106 106  
107 -[[image:1657328609906-564.png]]
101 +[[image:image-20220709144723-1.png]]
108 108  
109 109  
104 +=== 1.5.1 Jumper JP2 ===
110 110  
111 -= 2.  Use NDDS75 to communicate with IoT Server =
106 +Power on Device when put this jumper.
112 112  
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 +
113 113  == 2.1  How it works ==
114 114  
137 +
115 115  (((
116 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
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.
117 117  )))
118 118  
119 119  
120 120  (((
121 -The diagram below shows the working flow in default firmware of NDDS75:
144 +The diagram below shows the working flow in default firmware of N95S31B:
122 122  )))
123 123  
124 124  (((
... ... @@ -125,7 +125,7 @@
125 125  
126 126  )))
127 127  
128 -[[image:1657328659945-416.png]]
151 +[[image:1657350248151-650.png]]
129 129  
130 130  (((
131 131  
... ... @@ -132,30 +132,45 @@
132 132  )))
133 133  
134 134  
135 -== 2.2 ​ Configure the NDDS75 ==
158 +== 2.2 ​ Configure the N95S31B ==
136 136  
137 137  
161 +=== 2.2.1  Power On N95S31B ===
162 +
163 +
164 +[[image:image-20220709150546-2.png]]
165 +
166 +
138 138  === 2.2.1 Test Requirement ===
139 139  
140 -(((
141 -To use NDDS75 in your city, make sure meet below requirements:
142 -)))
143 143  
170 +To use N95S31B in your city, make sure meet below requirements:
171 +
144 144  * Your local operator has already distributed a NB-IoT Network there.
145 -* The local NB-IoT network used the band that NSE01 supports.
173 +* The local NB-IoT network used the band that N95S31B supports.
146 146  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
147 147  
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 +
148 148  (((
149 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
150 -)))
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(%%))
151 151  
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.
152 152  
153 -[[image:1657328756309-230.png]]
188 +
189 +)))
154 154  
191 +[[image:1657350625843-586.png]]
155 155  
156 156  
157 -=== 2.2.2 Insert SIM card ===
158 158  
195 +=== 2.2.3  Insert SIM card ===
196 +
159 159  (((
160 160  Insert the NB-IoT Card get from your provider.
161 161  )))
... ... @@ -165,19 +165,19 @@
165 165  )))
166 166  
167 167  
168 -[[image:1657328884227-504.png]]
206 +[[image:1657351240556-536.png]]
169 169  
170 170  
171 171  
172 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
210 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
173 173  
174 174  (((
175 175  (((
176 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
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.
177 177  )))
178 178  )))
179 179  
180 -[[image:image-20220709092052-2.png]]
218 +[[image:1657351312545-300.png]]
181 181  
182 182  **Connection:**
183 183  
... ... @@ -197,90 +197,110 @@
197 197  * Flow Control: (% style="color:green" %)**None**
198 198  
199 199  (((
200 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
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.
201 201  )))
202 202  
203 203  [[image:1657329814315-101.png]]
204 204  
205 205  (((
206 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
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/]]
207 207  )))
208 208  
209 209  
210 210  
211 -=== 2.2.4 Use CoAP protocol to uplink data ===
249 +=== 2.2.5  Use CoAP protocol to uplink data ===
212 212  
213 213  (% 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/]]
214 214  
215 215  
254 +(((
216 216  **Use below commands:**
256 +)))
217 217  
218 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
219 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
220 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
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 +)))
221 221  
268 +(((
269 +
270 +
222 222  For parameter description, please refer to AT command set
272 +)))
223 223  
224 -[[image:1657330452568-615.png]]
274 +[[image:1657352146020-183.png]]
225 225  
226 226  
277 +(((
227 227  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 +)))
228 228  
229 -[[image:1657330472797-498.png]]
281 +[[image:1657352185396-303.png]]
230 230  
231 231  
232 232  
233 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
285 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
234 234  
235 235  
236 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
288 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
237 237  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
238 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
290 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
239 239  
240 -[[image:1657330501006-241.png]]
292 +[[image:1657352391268-297.png]]
241 241  
242 242  
243 -[[image:1657330533775-472.png]]
295 +[[image:1657352403317-397.png]]
244 244  
245 245  
246 246  
247 -=== 2.2.6 Use MQTT protocol to uplink data ===
299 +=== 2.2.7  Use MQTT protocol to uplink data ===
248 248  
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
249 249  
250 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
251 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
252 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
253 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
254 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
255 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
256 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
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
257 257  
258 -[[image:1657249978444-674.png]]
311 +[[image:1657352634421-276.png]]
259 259  
260 260  
261 -[[image:1657330723006-866.png]]
314 +[[image:1657352645687-385.png]]
262 262  
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 +)))
263 263  
320 +
264 264  (((
265 -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.
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.
266 266  )))
267 267  
268 268  
269 269  
270 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
271 271  
329 +This feature is supported since firmware version v110
272 272  
273 273  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
274 274  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
275 275  
276 -[[image:image-20220709093918-1.png]]
334 +[[image:1657352898400-901.png]]
277 277  
278 278  
279 -[[image:image-20220709093918-2.png]]
337 +[[image:1657352914475-252.png]]
280 280  
281 281  
282 282  
283 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
284 284  
285 285  User can use below command to change the (% style="color:green" %)**uplink interval**.
286 286  
... ... @@ -287,69 +287,95 @@
287 287  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
288 288  
289 289  (((
290 -(% style="color:red" %)**NOTE:**
348 +
291 291  )))
292 292  
293 -(((
294 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
295 -)))
296 296  
297 297  
298 -
299 299  == 2.3  Uplink Payload ==
300 300  
301 -In this mode, uplink payload includes in total 14 bytes
302 302  
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.
303 303  
304 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
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" %)
305 305  |=(% style="width: 60px;" %)(((
306 306  **Size(bytes)**
307 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
308 -|(% 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" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
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
309 309  
310 -(((
311 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
312 -)))
392 +No function here.
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
313 313  
396 +By SHT31
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
314 314  
315 -[[image:1657331036973-987.png]]
316 -
317 -(((
318 -The payload is ASCII string, representative same HEX:
400 +By SHT31
319 319  )))
320 320  
321 321  (((
322 -0x72403155615900640c6c19029200 where:
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.
323 323  )))
324 -
325 -* (((
326 -Device ID: 0x724031556159 = 724031556159
327 327  )))
328 -* (((
329 -Version: 0x0064=100=1.0.0
330 -)))
331 331  
332 -* (((
333 -BAT: 0x0c6c = 3180 mV = 3.180V
334 -)))
335 -* (((
336 -Signal: 0x19 = 25
337 -)))
338 -* (((
339 -Distance: 0x0292= 658 mm
340 -)))
341 -* (((
342 -Interrupt: 0x00 = 0
343 -)))
344 344  
410 +[[image:1657354294009-643.png]]
345 345  
346 346  
347 -== 2.4  Payload Explanation and Sensor Interface ==
413 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
348 348  
415 +* Device ID: 0x724031607457 = 724031607457
416 +* Version: 0x006e=110=1.1.0
349 349  
350 -=== 2.4.1  Device ID ===
418 +* BAT: 0x0ccd = 3277 mV = 3.277V
419 +* Signal: 0x1b = 27
420 +* Model: 0x01 = 1
421 +* 0x00dc000ccc= reserve, ignore in N95S31B
422 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
423 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
351 351  
352 352  (((
426 +
427 +)))
428 +
429 +(((
430 +
431 +)))
432 +
433 +
434 +=== 2.3.2  Device ID ===
435 +
436 +(((
353 353  By default, the Device ID equal to the last 6 bytes of IMEI.
354 354  )))
355 355  
... ... @@ -371,24 +371,25 @@
371 371  
372 372  
373 373  
374 -=== 2.4.2  Version Info ===
458 +=== 2.3.3  Version Info ===
375 375  
376 -(((
377 -Specify the software version: 0x64=100, means firmware version 1.00.
378 -)))
379 379  
380 -(((
381 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
382 -)))
461 +These bytes include the hardware and software version.
383 383  
463 +Higher byte: Specify hardware version: always 0x00 for N95S31B
384 384  
465 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
385 385  
386 -=== 2.4.3  Battery Info ===
387 387  
468 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
469 +
388 388  (((
389 -Check the battery voltage for LSE01.
471 +
390 390  )))
391 391  
474 +
475 +=== 2.3.4  Battery Info ===
476 +
392 392  (((
393 393  Ex1: 0x0B45 = 2885mV
394 394  )))
... ... @@ -399,7 +399,7 @@
399 399  
400 400  
401 401  
402 -=== 2.4.4  Signal Strength ===
487 +=== 2.3.5  Signal Strength ===
403 403  
404 404  (((
405 405  NB-IoT Network signal Strength.
... ... @@ -431,86 +431,29 @@
431 431  
432 432  
433 433  
434 -=== 2.4.5  Soil Moisture ===
519 +=== 2.3.6  Temperature & Humidity ===
435 435  
436 -Get the distance. Flat object range 280mm - 7500mm.
521 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
437 437  
438 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
523 +[[image:image-20220709161741-3.png]]
439 439  
440 -(((
441 -(((
442 -(% style="color:#4f81bd" %)** 0B05(H) = 2821(D) = 2821mm.**
443 -)))
444 -)))
445 445  
446 -(((
447 -
448 -)))
526 +Convert the read byte to decimal and divide it by ten.
449 449  
450 -(((
451 -
452 -)))
453 453  
454 -=== 2.4.6  Digital Interrupt ===
529 +**Example:**
455 455  
456 -(((
457 -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.
458 -)))
531 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
459 459  
460 -(((
461 -The command is:
462 -)))
533 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
463 463  
464 -(((
465 -(% 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]])**.**
466 -)))
467 467  
468 468  
469 -(((
470 -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.
471 -)))
472 -
473 -
474 -(((
475 -Example:
476 -)))
477 -
478 -(((
479 -0x(00): Normal uplink packet.
480 -)))
481 -
482 -(((
483 -0x(01): Interrupt Uplink Packet.
484 -)))
485 -
486 -
487 -
488 -=== 2.4.7  ​+5V Output ===
489 -
490 -(((
491 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
492 -)))
493 -
494 -
495 -(((
496 -The 5V output time can be controlled by AT Command.
497 -)))
498 -
499 -(((
500 -(% style="color:blue" %)**AT+5VT=1000**
501 -)))
502 -
503 -(((
504 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
505 -)))
506 -
507 -
508 -
509 509  == 2.5  Downlink Payload ==
510 510  
511 -By default, NSE01 prints the downlink payload to console port.
539 +By default, NDDS75 prints the downlink payload to console port.
512 512  
513 -[[image:image-20220708133731-5.png]]
541 +[[image:image-20220709100028-1.png]]
514 514  
515 515  
516 516  (((
... ... @@ -546,7 +546,7 @@
546 546  )))
547 547  
548 548  (((
549 -If payload = 0x04FF, it will reset the NSE01
577 +If payload = 0x04FF, it will reset the NDDS75
550 550  )))
551 551  
552 552  
... ... @@ -560,76 +560,52 @@
560 560  
561 561  == 2.6  ​LED Indicator ==
562 562  
563 -(((
564 -The NSE01 has an internal LED which is to show the status of different state.
565 565  
592 +The NDDS75 has an internal LED which is to show the status of different state.
566 566  
567 -* 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)
594 +
595 +* 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)
568 568  * Then the LED will be on for 1 second means device is boot normally.
569 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
597 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
570 570  * For each uplink probe, LED will be on for 500ms.
571 -)))
572 572  
573 -
574 -
575 -
576 -== 2.7  Installation in Soil ==
577 -
578 -__**Measurement the soil surface**__
579 -
580 580  (((
581 -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]]
601 +
582 582  )))
583 583  
584 -[[image:1657259653666-883.png]] ​
585 585  
586 586  
587 -(((
588 -
606 +== 2.7  ​Firmware Change Log ==
589 589  
608 +
590 590  (((
591 -Dig a hole with diameter > 20CM.
610 +Download URL & Firmware Change log
592 592  )))
593 593  
594 594  (((
595 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
614 +[[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/]]
596 596  )))
597 -)))
598 598  
599 -[[image:1654506665940-119.png]]
600 600  
601 601  (((
602 -
619 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
603 603  )))
604 604  
605 605  
606 -== 2.8  ​Firmware Change Log ==
607 607  
624 +== 2.8  ​Battery Analysis ==
608 608  
609 -Download URL & Firmware Change log
626 +=== 2.8.1  ​Battery Type ===
610 610  
611 -[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
612 612  
613 -
614 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
615 -
616 -
617 -
618 -== 2.9  ​Battery Analysis ==
619 -
620 -=== 2.9.1  ​Battery Type ===
621 -
622 -
623 623  (((
624 -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.
630 +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.
625 625  )))
626 626  
627 -
628 628  (((
629 629  The battery is designed to last for several years depends on the actually use environment and update interval. 
630 630  )))
631 631  
632 -
633 633  (((
634 634  The battery related documents as below:
635 635  )))
... ... @@ -639,12 +639,12 @@
639 639  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
640 640  
641 641  (((
642 -[[image:image-20220708140453-6.png]]
646 +[[image:image-20220709101450-2.png]]
643 643  )))
644 644  
645 645  
646 646  
647 -=== 2.9.2  Power consumption Analyze ===
651 +=== 2.8.2  Power consumption Analyze ===
648 648  
649 649  (((
650 650  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.
... ... @@ -678,11 +678,11 @@
678 678  And the Life expectation in difference case will be shown on the right.
679 679  )))
680 680  
681 -[[image:image-20220708141352-7.jpeg]]
685 +[[image:image-20220709110451-3.png]]
682 682  
683 683  
684 684  
685 -=== 2.9.3  ​Battery Note ===
689 +=== 2.8.3  ​Battery Note ===
686 686  
687 687  (((
688 688  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.
... ... @@ -690,10 +690,10 @@
690 690  
691 691  
692 692  
693 -=== 2.9.4  Replace the battery ===
697 +=== 2.8.4  Replace the battery ===
694 694  
695 695  (((
696 -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).
700 +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).
697 697  )))
698 698  
699 699  
... ... @@ -708,7 +708,7 @@
708 708  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/]] 
709 709  )))
710 710  
711 -[[image:1657261278785-153.png]]
715 +[[image:1657333200519-600.png]]
712 712  
713 713  
714 714  
... ... @@ -716,7 +716,7 @@
716 716  
717 717  == 4.1  Access AT Commands ==
718 718  
719 -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/]]
723 +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/]]
720 720  
721 721  
722 722  AT+<CMD>?  : Help on <CMD>
... ... @@ -804,18 +804,11 @@
804 804  )))
805 805  
806 806  (((
807 -(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
811 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
808 808  )))
809 809  
810 810  
811 811  
812 -== 5.2  Can I calibrate NSE01 to different soil types? ==
813 -
814 -(((
815 -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]].
816 -)))
817 -
818 -
819 819  = 6.  Trouble Shooting =
820 820  
821 821  == 6.1  ​Connection problem when uploading firmware ==
... ... @@ -843,7 +843,7 @@
843 843  = 7. ​ Order Info =
844 844  
845 845  
846 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
843 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
847 847  
848 848  
849 849  (% class="wikigeneratedid" %)
... ... @@ -858,7 +858,7 @@
858 858  
859 859  (% style="color:#037691" %)**Package Includes**:
860 860  
861 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
858 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
862 862  * External antenna x 1
863 863  )))
864 864  
... ... @@ -867,8 +867,11 @@
867 867  
868 868  (% style="color:#037691" %)**Dimension and weight**:
869 869  
870 -* Size: 195 x 125 x 55 mm
871 -* Weight:   420g
867 +
868 +* Device Size: 13.0 x 5 x 4.5 cm
869 +* Device Weight: 150g
870 +* Package Size / pcs : 15 x 12x 5.5 cm
871 +* Weight / pcs : 220g
872 872  )))
873 873  
874 874  (((
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
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