Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 97.9 >
edited by Xiaoling
on 2022/07/09 11:30
To version < 118.7 >
edited by Xiaoling
on 2022/07/12 17:35
>
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,10 +1,12 @@
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 +
9 +
8 8  **Table of Contents:**
9 9  
10 10  {{toc/}}
... ... @@ -13,43 +13,54 @@
13 13  
14 14  
15 15  
16 -
17 17  = 1.  Introduction =
18 18  
19 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
20 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
20 20  
21 21  (((
22 22  
23 23  
24 24  (((
25 -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.
26 -\\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.
27 -\\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.
28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
29 -\\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)
30 -\\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.
26 +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 32  
29 +(((
30 +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.
31 +)))
32 +
33 +(((
34 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 +)))
36 +
37 +(((
38 +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).
39 +)))
40 +
41 +(((
33 33  
34 34  )))
35 35  
36 -[[image:1657327959271-447.png]]
45 +(((
46 +~* make sure you have NB-IoT coverage locally.
47 +)))
37 37  
49 +
50 +)))
38 38  
52 +[[image:1657348284168-431.png]]
39 39  
40 -== 1.2 ​ Features ==
41 41  
42 42  
56 +== 1.2 ​ Features ==
57 +
43 43  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
44 -* Ultra low power consumption
45 -* Distance Detection by Ultrasonic technology
46 -* Flat object range 280mm - 7500mm
47 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
48 -* Cable Length: 25cm
59 +* Monitor Temperature & Humidity via SHT31
49 49  * AT Commands to change parameters
50 50  * Uplink on periodically
51 51  * Downlink to change configure
52 52  * IP66 Waterproof Enclosure
64 +* Ultra-Low Power consumption
65 +* AT Commands to change parameters
53 53  * Micro SIM card slot for NB-IoT SIM
54 54  * 8500mAh Battery for long term use
55 55  
... ... @@ -80,13 +80,8 @@
80 80  * Max continuously current: 130mA
81 81  * Max boost current: 2A, 1 second
82 82  
83 -(% style="color:#037691" %)**Power Consumption**
84 84  
85 -* STOP Mode: 10uA @ 3.3v
86 -* Max transmit power: 350mA@3.3v
87 87  
88 -
89 -
90 90  == ​1.4  Applications ==
91 91  
92 92  * Smart Buildings & Home Automation
... ... @@ -100,24 +100,57 @@
100 100  ​
101 101  
102 102  
103 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
104 104  
113 +N95S31B use the mother board from NBSN95 which as below.
105 105  
106 -[[image:1657328609906-564.png]]
115 +[[image:image-20220709144723-1.png]]
107 107  
108 108  
118 +=== 1.5.1 Jumper JP2 ===
109 109  
110 -= 2.  Use NDDS75 to communicate with IoT Server =
120 +Power on Device when put this jumper.
111 111  
122 +
123 +
124 +=== 1.5.2 BOOT MODE / SW1 ===
125 +
126 +(((
127 +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.
128 +)))
129 +
130 +(((
131 +2) Flash: work mode, device starts to work and send out console output for further debug
132 +)))
133 +
134 +
135 +
136 +=== 1.5.3 Reset Button ===
137 +
138 +Press to reboot the device.
139 +
140 +
141 +
142 +=== 1.5.4 LED ===
143 +
144 +It will flash:
145 +
146 +1. When boot the device in flash mode
147 +1. Send an uplink packet
148 +
149 +
150 += 2.  Use N95S31B to communicate with IoT Server =
151 +
112 112  == 2.1  How it works ==
113 113  
154 +
114 114  (((
115 -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.
156 +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.
116 116  )))
117 117  
118 118  
119 119  (((
120 -The diagram below shows the working flow in default firmware of NDDS75:
161 +The diagram below shows the working flow in default firmware of N95S31B:
121 121  )))
122 122  
123 123  (((
... ... @@ -124,7 +124,7 @@
124 124  
125 125  )))
126 126  
127 -[[image:1657328659945-416.png]]
168 +[[image:1657520100595-569.png]]
128 128  
129 129  (((
130 130  
... ... @@ -131,30 +131,67 @@
131 131  )))
132 132  
133 133  
134 -== 2.2 ​ Configure the NDDS75 ==
175 +== 2.2 ​ Configure the N95S31B ==
135 135  
136 136  
178 +=== 2.2.1  Power On N95S31B ===
179 +
180 +
181 +[[image:image-20220709150546-2.png]]
182 +
183 +
137 137  === 2.2.1 Test Requirement ===
138 138  
186 +
139 139  (((
140 -To use NDDS75 in your city, make sure meet below requirements:
188 +To use N95S31B in your city, make sure meet below requirements:
141 141  )))
142 142  
143 -* Your local operator has already distributed a NB-IoT Network there.
144 -* The local NB-IoT network used the band that NSE01 supports.
145 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
191 +* (((
192 +Your local operator has already distributed a NB-IoT Network there.
193 +)))
194 +* (((
195 +The local NB-IoT network used the band that N95S31B supports.
196 +)))
197 +* (((
198 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +)))
146 146  
147 147  (((
148 -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
202 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
149 149  )))
150 150  
205 +(((
206 +N95S31B supports different communication protocol such as :
207 +)))
151 151  
152 -[[image:1657328756309-230.png]]
209 +(((
210 +* (((
211 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
212 +)))
213 +* (((
214 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
215 +)))
216 +* (((
217 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
218 +)))
219 +* (((
220 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
221 +)))
153 153  
223 +(((
224 +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.
225 +)))
154 154  
227 +
228 +)))
155 155  
156 -=== 2.2.2 Insert SIM card ===
230 +[[image:1657350625843-586.png]]
157 157  
232 +
233 +
234 +=== 2.2.3  Insert SIM card ===
235 +
158 158  (((
159 159  Insert the NB-IoT Card get from your provider.
160 160  )))
... ... @@ -164,19 +164,19 @@
164 164  )))
165 165  
166 166  
167 -[[image:1657328884227-504.png]]
245 +[[image:1657351240556-536.png]]
168 168  
169 169  
170 170  
171 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
249 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
172 172  
173 173  (((
174 174  (((
175 -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.
253 +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.
176 176  )))
177 177  )))
178 178  
179 -[[image:image-20220709092052-2.png]]
257 +[[image:1657351312545-300.png]]
180 180  
181 181  **Connection:**
182 182  
... ... @@ -196,18 +196,18 @@
196 196  * Flow Control: (% style="color:green" %)**None**
197 197  
198 198  (((
199 -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.
277 +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.
200 200  )))
201 201  
202 202  [[image:1657329814315-101.png]]
203 203  
204 204  (((
205 -(% 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/]]
283 +(% 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/]]
206 206  )))
207 207  
208 208  
209 209  
210 -=== 2.2.4 Use CoAP protocol to uplink data ===
288 +=== 2.2.5  Use CoAP protocol to uplink data ===
211 211  
212 212  (% 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/]]
213 213  
... ... @@ -227,19 +227,23 @@
227 227  )))
228 228  
229 229  (((
308 +
309 +
230 230  For parameter description, please refer to AT command set
231 231  )))
232 232  
233 -[[image:1657330452568-615.png]]
313 +[[image:1657352146020-183.png]]
234 234  
235 235  
316 +(((
236 236  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.
318 +)))
237 237  
238 -[[image:1657330472797-498.png]]
320 +[[image:1657352185396-303.png]]
239 239  
240 240  
241 241  
242 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
324 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
243 243  
244 244  
245 245  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -246,50 +246,56 @@
246 246  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
247 247  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
248 248  
249 -[[image:1657330501006-241.png]]
331 +[[image:1657352391268-297.png]]
250 250  
251 251  
252 -[[image:1657330533775-472.png]]
334 +[[image:1657352403317-397.png]]
253 253  
254 254  
255 255  
256 -=== 2.2.6 Use MQTT protocol to uplink data ===
338 +=== 2.2.7  Use MQTT protocol to uplink data ===
257 257  
340 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
258 258  
259 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
260 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
261 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
262 -* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
263 -* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
264 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
265 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
342 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
343 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
344 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
345 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
346 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
347 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
348 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
266 266  
267 -[[image:1657249978444-674.png]]
350 +[[image:1657352634421-276.png]]
268 268  
269 269  
270 -[[image:1657330723006-866.png]]
353 +[[image:1657352645687-385.png]]
271 271  
355 +(((
356 +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.
357 +)))
272 272  
359 +
273 273  (((
274 -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.
361 +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.
275 275  )))
276 276  
277 277  
278 278  
279 -=== 2.2.7 Use TCP protocol to uplink data ===
366 +=== 2.2.8  Use TCP protocol to uplink data ===
280 280  
368 +This feature is supported since firmware version v110
281 281  
282 282  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
283 283  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
284 284  
285 -[[image:image-20220709093918-1.png]]
373 +[[image:1657352898400-901.png]]
286 286  
287 287  
288 -[[image:image-20220709093918-2.png]]
376 +[[image:1657352914475-252.png]]
289 289  
290 290  
291 291  
292 -=== 2.2.8 Change Update Interval ===
380 +=== 2.2.9  Change Update Interval ===
293 293  
294 294  User can use below command to change the (% style="color:green" %)**uplink interval**.
295 295  
... ... @@ -296,59 +296,51 @@
296 296  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
297 297  
298 298  (((
299 -(% style="color:red" %)**NOTE:**
387 +
300 300  )))
301 301  
302 -(((
303 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
304 -)))
305 305  
306 306  
307 -
308 308  == 2.3  Uplink Payload ==
309 309  
310 -In this mode, uplink payload includes in total 14 bytes
311 311  
395 +(((
396 +N95S31B 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.
397 +)))
312 312  
313 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
314 -|=(% style="width: 80px;" %)(((
315 -**Size(bytes)**
316 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
318 318  
319 319  (((
320 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
401 +For example:
321 321  )))
322 322  
404 +(((
405 + (% 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.
406 +)))
323 323  
324 -[[image:1657331036973-987.png]]
325 325  
326 326  (((
327 -The payload is ASCII string, representative same HEX:
410 +The uplink payloads are composed in  ASCII String. For example:
328 328  )))
329 329  
330 330  (((
331 -0x72403155615900640c6c19029200 where:
414 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
332 332  )))
333 333  
334 -* (((
335 -Device ID: 0x724031556159 = 724031556159
417 +(((
418 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
336 336  )))
337 -* (((
338 -Version: 0x0064=100=1.0.0
420 +
421 +
422 +(((
423 +(% style="color:red" %)**NOTE:**
339 339  )))
340 340  
341 -* (((
342 -BAT: 0x0c6c = 3180 mV = 3.180V
426 +(% style="color:red" %)
427 +1. (((
428 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
343 343  )))
344 -* (((
345 -Signal: 0x19 = 25
346 -)))
347 -* (((
348 -Distance: 0x0292= 658 mm
349 -)))
350 -* (((
351 -Interrupt: 0x00 = 0
430 +1. (((
431 +By default, the device will send an uplink message every 1 hour.
352 352  
353 353  
354 354  
... ... @@ -355,103 +355,108 @@
355 355  
356 356  )))
357 357  
358 -== 2.4  Payload Explanation and Sensor Interface ==
438 +=== 2.3.1  Payload Analyze ===
359 359  
440 +N95S31B uplink payload includes in total 21 bytes
360 360  
361 -=== 2.4.1  Device ID ===
362 362  
443 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
444 +|=(% style="width: 60px;" %)(((
445 +**Size(bytes)**
446 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
447 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
363 363  (((
364 -By default, the Device ID equal to the last 6 bytes of IMEI.
449 +Reserve/ Same as NBSN95 CFGMOD=1
365 365  )))
366 366  
367 367  (((
368 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
453 +No function here.
369 369  )))
370 -
455 +)))|(% style="width:77px" %)(((
371 371  (((
372 -**Example:**
457 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
373 373  )))
374 374  
375 375  (((
376 -AT+DEUI=A84041F15612
461 +By SHT31
377 377  )))
378 -
463 +)))|(% style="width:80px" %)(((
379 379  (((
380 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
465 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
381 381  )))
382 382  
383 -
384 -
385 -=== 2.4.2  Version Info ===
386 -
387 387  (((
388 -Specify the software version: 0x64=100, means firmware version 1.00.
469 +By SHT31
389 389  )))
471 +)))
390 390  
391 391  (((
392 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
474 +(((
475 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
393 393  )))
477 +)))
394 394  
395 395  
480 +[[image:1657354294009-643.png]]
396 396  
397 -=== 2.4.3  Battery Info ===
398 398  
399 -(((
400 -Ex1: 0x0B45 = 2885mV
401 -)))
483 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
402 402  
403 -(((
404 -Ex2: 0x0B49 = 2889mV
405 -)))
485 +* Device ID: 0x724031607457 = 724031607457
486 +* Version: 0x006e=110=1.1.0
406 406  
488 +* BAT: 0x0ccd = 3277 mV = 3.277V
489 +* Signal: 0x1b = 27
490 +* Model: 0x01 = 1
491 +* 0x00dc000ccc= reserve, ignore in N95S31B
492 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
493 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
407 407  
408 -
409 -=== 2.4.4  Signal Strength ===
410 -
411 411  (((
412 -NB-IoT Network signal Strength.
496 +
413 413  )))
414 414  
415 415  (((
416 -**Ex1: 0x1d = 29**
500 +
417 417  )))
418 418  
503 +
504 +=== 2.3.2  Device ID ===
505 +
419 419  (((
420 -(% style="color:blue" %)**0**(%%)  -113dBm or less
507 +By default, the Device ID equal to the last 6 bytes of IMEI.
421 421  )))
422 422  
423 423  (((
424 -(% style="color:blue" %)**1**(%%)  -111dBm
511 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
425 425  )))
426 426  
427 427  (((
428 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 +**Example:**
429 429  )))
430 430  
431 431  (((
432 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 +AT+DEUI=A84041F15612
433 433  )))
434 434  
435 435  (((
436 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
523 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
437 437  )))
438 438  
439 439  
440 440  
441 -=== 2.4.5  Distance ===
528 +=== 2.3.3  Version Info ===
442 442  
443 -Get the distance. Flat object range 280mm - 7500mm.
530 +(((
531 +These bytes include the hardware and software version.
532 +)))
444 444  
445 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
446 -
447 447  (((
448 -(((
449 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
535 +Higher byte: Specify hardware version: always 0x00 for N95S31B
450 450  )))
451 -)))
452 452  
453 453  (((
454 -
539 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
455 455  )))
456 456  
457 457  (((
... ... @@ -458,65 +458,81 @@
458 458  
459 459  )))
460 460  
461 -=== 2.4.6  Digital Interrupt ===
462 -
463 463  (((
464 -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.
547 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
465 465  )))
466 466  
467 467  (((
468 -The command is:
551 +
469 469  )))
470 470  
554 +
555 +=== 2.3.4  Battery Info ===
556 +
471 471  (((
472 -(% 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]])**.**
558 +Ex1: 0x0B45 = 2885mV
473 473  )))
474 474  
475 -
476 476  (((
477 -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.
562 +Ex2: 0x0B49 = 2889mV
478 478  )))
479 479  
480 480  
566 +
567 +=== 2.3.5  Signal Strength ===
568 +
481 481  (((
482 -Example:
570 +NB-IoT Network signal Strength.
483 483  )))
484 484  
485 485  (((
486 -0x(00): Normal uplink packet.
574 +**Ex1: 0x1d = 29**
487 487  )))
488 488  
489 489  (((
490 -0x(01): Interrupt Uplink Packet.
578 +(% style="color:blue" %)**0**(%%)  -113dBm or less
491 491  )))
492 492  
493 -
494 -
495 -=== 2.4.7  ​+5V Output ===
496 -
497 497  (((
498 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
582 +(% style="color:blue" %)**1**(%%)  -111dBm
499 499  )))
500 500  
501 -
502 502  (((
503 -The 5V output time can be controlled by AT Command.
586 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
504 504  )))
505 505  
506 506  (((
507 -(% style="color:blue" %)**AT+5VT=1000**
590 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
508 508  )))
509 509  
510 510  (((
511 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
594 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
512 512  )))
513 513  
514 514  
515 515  
516 -== 2.5  Downlink Payload ==
599 +=== 2.3.6  Temperature & Humidity ===
517 517  
518 -By default, NDDS75 prints the downlink payload to console port.
601 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
519 519  
603 +[[image:image-20220709161741-3.png]]
604 +
605 +
606 +Convert the read byte to decimal and divide it by ten.
607 +
608 +
609 +**Example:**
610 +
611 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
612 +
613 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
614 +
615 +
616 +
617 +== 2.4  Downlink Payload ==
618 +
619 +By default, N95S31B prints the downlink payload to console port.
620 +
520 520  [[image:image-20220709100028-1.png]]
521 521  
522 522  
... ... @@ -553,7 +553,7 @@
553 553  )))
554 554  
555 555  (((
556 -If payload = 0x04FF, it will reset the NDDS75
657 +If payload = 0x04FF, it will reset the N95S31B
557 557  )))
558 558  
559 559  
... ... @@ -565,47 +565,16 @@
565 565  
566 566  
567 567  
568 -== 2.6  ​LED Indicator ==
669 +== 2.5  ​Battery Analysis ==
569 569  
671 +=== 2.5.1  ​Battery Type ===
570 570  
571 -The NDDS75 has an internal LED which is to show the status of different state.
572 572  
573 -
574 -* 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)
575 -* Then the LED will be on for 1 second means device is boot normally.
576 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
577 -* For each uplink probe, LED will be on for 500ms.
578 -
579 579  (((
580 -
675 +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.
581 581  )))
582 582  
583 -
584 -
585 -== 2.7  ​Firmware Change Log ==
586 -
587 -
588 -Download URL & Firmware Change log
589 -
590 590  (((
591 -[[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/]]
592 -)))
593 -
594 -
595 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
596 -
597 -
598 -
599 -== 2.8  ​Battery Analysis ==
600 -
601 -=== 2.8.1  ​Battery Type ===
602 -
603 -
604 -(((
605 -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.
606 -)))
607 -
608 -(((
609 609  The battery is designed to last for several years depends on the actually use environment and update interval. 
610 610  )))
611 611  
... ... @@ -623,56 +623,35 @@
623 623  
624 624  
625 625  
626 -=== 2.8.2  Power consumption Analyze ===
696 +=== 2.5.2  Power consumption Analyze ===
627 627  
628 628  (((
629 -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.
699 +The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
630 630  )))
631 631  
632 -
633 633  (((
634 -Instruction to use as below:
703 +
635 635  )))
636 636  
637 -(((
638 -(% 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/]]
639 -)))
640 640  
707 +=== 2.5.3  ​Battery Note ===
641 641  
642 642  (((
643 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
710 +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.
644 644  )))
645 645  
646 -* (((
647 -Product Model
648 -)))
649 -* (((
650 -Uplink Interval
651 -)))
652 -* (((
653 -Working Mode
654 -)))
655 655  
656 -(((
657 -And the Life expectation in difference case will be shown on the right.
658 -)))
659 659  
660 -[[image:image-20220709110451-3.png]]
715 +=== 2.5.4  Replace the battery ===
661 661  
662 662  
663 -
664 -=== 2.8.3  ​Battery Note ===
665 -
666 666  (((
667 -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.
719 +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.
668 668  )))
669 669  
670 670  
671 -
672 -=== 2.8.4  Replace the battery ===
673 -
674 674  (((
675 -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).
724 +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).
676 676  )))
677 677  
678 678  
... ... @@ -695,7 +695,7 @@
695 695  
696 696  == 4.1  Access AT Commands ==
697 697  
698 -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/]]
747 +See NBSN95 AT Command in this link for detail:  [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
699 699  
700 700  
701 701  AT+<CMD>?  : Help on <CMD>
... ... @@ -783,8 +783,12 @@
783 783  )))
784 784  
785 785  (((
786 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
835 +
836 +
837 +(((
838 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
787 787  )))
840 +)))
788 788  
789 789  
790 790  
... ... @@ -815,7 +815,7 @@
815 815  = 7. ​ Order Info =
816 816  
817 817  
818 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
871 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
819 819  
820 820  
821 821  (% class="wikigeneratedid" %)
... ... @@ -830,7 +830,7 @@
830 830  
831 831  (% style="color:#037691" %)**Package Includes**:
832 832  
833 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
886 +* N95S31B NB-IoT Temperature and Humidity Sensor
834 834  * External antenna x 1
835 835  )))
836 836  
... ... @@ -839,11 +839,10 @@
839 839  
840 840  (% style="color:#037691" %)**Dimension and weight**:
841 841  
842 -
843 843  * Device Size: 13.0 x 5 x 4.5 cm
844 844  * Device Weight: 150g
845 -* Package Size / pcs : 15 x 12x 5.5 cm
846 -* Weight / pcs : 220g
897 +* Package Size / pcs : 14.0 x 8x 5 cm
898 +* Weight / pcs : 180g
847 847  )))
848 848  
849 849  (((
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-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

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0