Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 95.2
edited by Xiaoling
on 2022/07/09 10:34
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,57 +1,55 @@
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  
... ... @@ -75,6 +75,7 @@
75 75  
76 76  (% style="color:#037691" %)**Battery:**
77 77  
76 +
78 78  * Li/SOCI2 un-chargeable battery
79 79  * Capacity: 8500mAh
80 80  * Self Discharge: <1% / Year @ 25°C
... ... @@ -81,13 +81,7 @@
81 81  * Max continuously current: 130mA
82 82  * Max boost current: 2A, 1 second
83 83  
84 -(% style="color:#037691" %)**Power Consumption**
85 85  
86 -* STOP Mode: 10uA @ 3.3v
87 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]]
88 -
89 -
90 -
91 91  == ​1.4  Applications ==
92 92  
93 93  * Smart Buildings & Home Automation
... ... @@ -101,25 +101,54 @@
101 101  ​
102 102  
103 103  
104 -
105 105  == 1.5  Pin Definitions ==
106 106  
99 +N95S31B use the mother board from NBSN95 which as below.
107 107  
108 -[[image:1657328609906-564.png]]
101 +[[image:image-20220709144723-1.png]]
109 109  
110 110  
104 +=== 1.5.1 Jumper JP2 ===
111 111  
112 -= 2.  Use NDDS75 to communicate with IoT Server =
106 +Power on Device when put this jumper.
113 113  
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 +
114 114  == 2.1  How it works ==
115 115  
137 +
116 116  (((
117 -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.
118 118  )))
119 119  
120 120  
121 121  (((
122 -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:
123 123  )))
124 124  
125 125  (((
... ... @@ -126,7 +126,7 @@
126 126  
127 127  )))
128 128  
129 -[[image:1657328659945-416.png]]
151 +[[image:1657350248151-650.png]]
130 130  
131 131  (((
132 132  
... ... @@ -133,30 +133,45 @@
133 133  )))
134 134  
135 135  
136 -== 2.2 ​ Configure the NDDS75 ==
158 +== 2.2 ​ Configure the N95S31B ==
137 137  
138 138  
161 +=== 2.2.1  Power On N95S31B ===
162 +
163 +
164 +[[image:image-20220709150546-2.png]]
165 +
166 +
139 139  === 2.2.1 Test Requirement ===
140 140  
141 -(((
142 -To use NDDS75 in your city, make sure meet below requirements:
143 -)))
144 144  
170 +To use N95S31B in your city, make sure meet below requirements:
171 +
145 145  * Your local operator has already distributed a NB-IoT Network there.
146 -* The local NB-IoT network used the band that NSE01 supports.
173 +* The local NB-IoT network used the band that N95S31B supports.
147 147  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
148 148  
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 +
149 149  (((
150 -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
151 -)))
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(%%))
152 152  
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.
153 153  
154 -[[image:1657328756309-230.png]]
188 +
189 +)))
155 155  
191 +[[image:1657350625843-586.png]]
156 156  
157 157  
158 -=== 2.2.2 Insert SIM card ===
159 159  
195 +=== 2.2.3  Insert SIM card ===
196 +
160 160  (((
161 161  Insert the NB-IoT Card get from your provider.
162 162  )))
... ... @@ -166,19 +166,19 @@
166 166  )))
167 167  
168 168  
169 -[[image:1657328884227-504.png]]
206 +[[image:1657351240556-536.png]]
170 170  
171 171  
172 172  
173 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
210 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
174 174  
175 175  (((
176 176  (((
177 -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.
178 178  )))
179 179  )))
180 180  
181 -[[image:image-20220709092052-2.png]]
218 +[[image:1657351312545-300.png]]
182 182  
183 183  **Connection:**
184 184  
... ... @@ -198,90 +198,110 @@
198 198  * Flow Control: (% style="color:green" %)**None**
199 199  
200 200  (((
201 -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.
202 202  )))
203 203  
204 204  [[image:1657329814315-101.png]]
205 205  
206 206  (((
207 -(% 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/]]
208 208  )))
209 209  
210 210  
211 211  
212 -=== 2.2.4 Use CoAP protocol to uplink data ===
249 +=== 2.2.5  Use CoAP protocol to uplink data ===
213 213  
214 214  (% 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/]]
215 215  
216 216  
254 +(((
217 217  **Use below commands:**
256 +)))
218 218  
219 -* (% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
220 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
221 -* (% 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 +)))
222 222  
268 +(((
269 +
270 +
223 223  For parameter description, please refer to AT command set
272 +)))
224 224  
225 -[[image:1657330452568-615.png]]
274 +[[image:1657352146020-183.png]]
226 226  
227 227  
277 +(((
228 228  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 +)))
229 229  
230 -[[image:1657330472797-498.png]]
281 +[[image:1657352185396-303.png]]
231 231  
232 232  
233 233  
234 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
285 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
235 235  
236 236  
237 -* (% 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
238 238  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
239 -* (% 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
240 240  
241 -[[image:1657330501006-241.png]]
292 +[[image:1657352391268-297.png]]
242 242  
243 243  
244 -[[image:1657330533775-472.png]]
295 +[[image:1657352403317-397.png]]
245 245  
246 246  
247 247  
248 -=== 2.2.6 Use MQTT protocol to uplink data ===
299 +=== 2.2.7  Use MQTT protocol to uplink data ===
249 249  
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
250 250  
251 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
252 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
253 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
254 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
255 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
256 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
257 -* (% 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
258 258  
259 -[[image:1657249978444-674.png]]
311 +[[image:1657352634421-276.png]]
260 260  
261 261  
262 -[[image:1657330723006-866.png]]
314 +[[image:1657352645687-385.png]]
263 263  
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 +)))
264 264  
320 +
265 265  (((
266 -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.
267 267  )))
268 268  
269 269  
270 270  
271 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
272 272  
329 +This feature is supported since firmware version v110
273 273  
274 274  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
275 275  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
276 276  
277 -[[image:image-20220709093918-1.png]]
334 +[[image:1657352898400-901.png]]
278 278  
279 279  
280 -[[image:image-20220709093918-2.png]]
337 +[[image:1657352914475-252.png]]
281 281  
282 282  
283 283  
284 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
285 285  
286 286  User can use below command to change the (% style="color:green" %)**uplink interval**.
287 287  
... ... @@ -288,224 +288,195 @@
288 288  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
289 289  
290 290  (((
291 -(% style="color:red" %)**NOTE:**
348 +
292 292  )))
293 293  
294 -(((
295 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
296 -)))
297 297  
298 298  
299 -
300 300  == 2.3  Uplink Payload ==
301 301  
302 -In this mode, uplink payload includes in total 14 bytes
303 303  
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.
304 304  
305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
306 -|=(% style="width: 60px;" %)(((
307 -**Size(bytes)**
308 -)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1**
309 -|(% 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"]]
310 310  
311 -(((
312 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
313 -)))
359 +For example:
314 314  
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.
315 315  
316 -[[image:1657331036973-987.png]]
317 317  
318 -(((
319 -The payload is ASCII string, representative same HEX:
320 -)))
364 +The uplink payloads are composed in  ASCII String. For example:
321 321  
322 -(((
323 -0x72403155615900640c6c19029200 where:
324 -)))
366 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
325 325  
326 -* (((
327 -Device ID: 0x724031556159 = 724031556159
328 -)))
329 -* (((
330 -Version: 0x0064=100=1.0.0
331 -)))
368 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
332 332  
333 -* (((
334 -BAT: 0x0c6c = 3180 mV = 3.180V
335 -)))
336 -* (((
337 -Signal: 0x19 = 25
338 -)))
339 -* (((
340 -Distance: 0x0292= 658 mm
341 -)))
342 -* (((
343 -Interrupt: 0x00 = 0
344 -)))
345 345  
371 +(% style="color:red" %)**NOTE:**
346 346  
347 -== 2.4  Payload Explanation and Sensor Interface ==
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.
348 348  
349 349  
350 -=== 2.4.1  Device ID ===
351 351  
352 -(((
353 -By default, the Device ID equal to the last 6 bytes of IMEI.
354 -)))
355 355  
356 -(((
357 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
358 -)))
380 +=== 2.3.1  Payload Analyze ===
359 359  
360 -(((
361 -**Example:**
362 -)))
382 +N95S31B uplink payload includes in total 21 bytes
363 363  
364 -(((
365 -AT+DEUI=A84041F15612
366 -)))
367 367  
368 -(((
369 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
370 -)))
385 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
386 +|=(% style="width: 60px;" %)(((
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
371 371  
392 +No function here.
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
372 372  
396 +By SHT31
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
373 373  
374 -=== 2.4.2  Version Info ===
375 -
376 -(((
377 -Specify the software version: 0x64=100, means firmware version 1.00.
400 +By SHT31
378 378  )))
379 379  
380 380  (((
381 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
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.
382 382  )))
407 +)))
383 383  
384 384  
410 +[[image:1657354294009-643.png]]
385 385  
386 -=== 2.4.3  Battery Info ===
387 387  
388 -(((
389 -Check the battery voltage for LSE01.
390 -)))
413 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
391 391  
415 +* Device ID: 0x724031607457 = 724031607457
416 +* Version: 0x006e=110=1.1.0
417 +
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
424 +
392 392  (((
393 -Ex1: 0x0B45 = 2885mV
426 +
394 394  )))
395 395  
396 396  (((
397 -Ex2: 0x0B49 = 2889mV
430 +
398 398  )))
399 399  
400 400  
434 +=== 2.3.2  Device ID ===
401 401  
402 -=== 2.4.4  Signal Strength ===
403 -
404 404  (((
405 -NB-IoT Network signal Strength.
437 +By default, the Device ID equal to the last 6 bytes of IMEI.
406 406  )))
407 407  
408 408  (((
409 -**Ex1: 0x1d = 29**
441 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
410 410  )))
411 411  
412 412  (((
413 -(% style="color:blue" %)**0**(%%)  -113dBm or less
445 +**Example:**
414 414  )))
415 415  
416 416  (((
417 -(% style="color:blue" %)**1**(%%)  -111dBm
449 +AT+DEUI=A84041F15612
418 418  )))
419 419  
420 420  (((
421 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
453 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
422 422  )))
423 423  
424 -(((
425 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
426 -)))
427 427  
428 -(((
429 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
430 -)))
431 431  
458 +=== 2.3.3  Version Info ===
432 432  
433 433  
434 -=== 2.4.5  Soil Moisture ===
461 +These bytes include the hardware and software version.
435 435  
436 -Get the distance. Flat object range 280mm - 7500mm.
463 +Higher byte: Specify hardware version: always 0x00 for N95S31B
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
465 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
439 439  
467 +
468 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
469 +
440 440  (((
441 -(((
442 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
471 +
443 443  )))
444 -)))
445 445  
474 +
475 +=== 2.3.4  Battery Info ===
476 +
446 446  (((
447 -
478 +Ex1: 0x0B45 = 2885mV
448 448  )))
449 449  
450 450  (((
451 -
482 +Ex2: 0x0B49 = 2889mV
452 452  )))
453 453  
454 -=== 2.4.6  Digital Interrupt ===
455 455  
486 +
487 +=== 2.3.5  Signal Strength ===
488 +
456 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.
490 +NB-IoT Network signal Strength.
458 458  )))
459 459  
460 460  (((
461 -The command is:
494 +**Ex1: 0x1d = 29**
462 462  )))
463 463  
464 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]])**.**
498 +(% style="color:blue" %)**0**(%%)  -113dBm or less
466 466  )))
467 467  
468 -
469 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.
502 +(% style="color:blue" %)**1**(%%)  -111dBm
471 471  )))
472 472  
473 -
474 474  (((
475 -Example:
506 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
476 476  )))
477 477  
478 478  (((
479 -0x(00): Normal uplink packet.
510 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
480 480  )))
481 481  
482 482  (((
483 -0x(01): Interrupt Uplink Packet.
514 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
484 484  )))
485 485  
486 486  
487 487  
488 -=== 2.4.7  ​+5V Output ===
519 +=== 2.3.6  Temperature & Humidity ===
489 489  
490 -(((
491 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
492 -)))
521 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
493 493  
523 +[[image:image-20220709161741-3.png]]
494 494  
495 -(((
496 -The 5V output time can be controlled by AT Command.
497 -)))
498 498  
499 -(((
500 -(% style="color:blue" %)**AT+5VT=1000**
501 -)))
526 +Convert the read byte to decimal and divide it by ten.
502 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 506  
529 +**Example:**
507 507  
531 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
508 508  
533 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
534 +
535 +
536 +
509 509  == 2.5  Downlink Payload ==
510 510  
511 511  By default, NDDS75 prints the downlink payload to console port.
... ... @@ -578,7 +578,9 @@
578 578  == 2.7  ​Firmware Change Log ==
579 579  
580 580  
609 +(((
581 581  Download URL & Firmware Change log
611 +)))
582 582  
583 583  (((
584 584  [[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/]]
... ... @@ -585,7 +585,9 @@
585 585  )))
586 586  
587 587  
618 +(((
588 588  Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
620 +)))
589 589  
590 590  
591 591  
... ... @@ -650,7 +650,7 @@
650 650  And the Life expectation in difference case will be shown on the right.
651 651  )))
652 652  
653 -[[image:image-20220708141352-7.jpeg]]
685 +[[image:image-20220709110451-3.png]]
654 654  
655 655  
656 656  
... ... @@ -808,7 +808,7 @@
808 808  = 7. ​ Order Info =
809 809  
810 810  
811 -Part Number**:** (% style="color:#4f81bd" %)**NSE01**
843 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
812 812  
813 813  
814 814  (% class="wikigeneratedid" %)
... ... @@ -823,7 +823,7 @@
823 823  
824 824  (% style="color:#037691" %)**Package Includes**:
825 825  
826 -* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
858 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
827 827  * External antenna x 1
828 828  )))
829 829  
... ... @@ -832,8 +832,11 @@
832 832  
833 833  (% style="color:#037691" %)**Dimension and weight**:
834 834  
835 -* Size: 195 x 125 x 55 mm
836 -* 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
837 837  )))
838 838  
839 839  (((
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-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