Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 97.1 >
edited by Xiaoling
on 2022/07/09 11:06
To version < 118.8 >
edited by Xiaoling
on 2022/07/12 17:36
>
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,49 +13,59 @@
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:1654503236291-817.png]]
45 +(((
46 +~* make sure you have NB-IoT coverage locally.
47 +)))
37 37  
49 +
50 +)))
38 38  
39 -[[image:1657327959271-447.png]]
52 +[[image:1657348284168-431.png]]
40 40  
41 41  
42 42  
43 43  == 1.2 ​ Features ==
44 44  
45 -
46 46  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
47 -* Ultra low power consumption
48 -* Distance Detection by Ultrasonic technology
49 -* Flat object range 280mm - 7500mm
50 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
51 -* Cable Length: 25cm
59 +* Monitor Temperature & Humidity via SHT31
52 52  * AT Commands to change parameters
53 53  * Uplink on periodically
54 54  * Downlink to change configure
55 55  * IP66 Waterproof Enclosure
64 +* Ultra-Low Power consumption
65 +* AT Commands to change parameters
56 56  * Micro SIM card slot for NB-IoT SIM
57 57  * 8500mAh Battery for long term use
58 58  
69 +
70 +
59 59  == 1.3  Specification ==
60 60  
61 61  
... ... @@ -81,12 +81,8 @@
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 88  
89 -
90 90  == ​1.4  Applications ==
91 91  
92 92  * Smart Buildings & Home Automation
... ... @@ -100,25 +100,57 @@
100 100  ​
101 101  
102 102  
111 +== 1.5  Pin Definitions & Switch ==
103 103  
104 -== 1.5  Pin Definitions ==
113 +N95S31B use the mother board from NBSN95 which as below.
105 105  
115 +[[image:image-20220709144723-1.png]]
106 106  
107 -[[image:1657328609906-564.png]]
108 108  
118 +=== 1.5.1 Jumper JP2 ===
109 109  
120 +Power on Device when put this jumper.
110 110  
111 -= 2.  Use NDDS75 to communicate with IoT Server =
112 112  
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 +
113 113  == 2.1  How it works ==
114 114  
154 +
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.
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.
117 117  )))
118 118  
119 119  
120 120  (((
121 -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:
122 122  )))
123 123  
124 124  (((
... ... @@ -125,7 +125,7 @@
125 125  
126 126  )))
127 127  
128 -[[image:1657328659945-416.png]]
168 +[[image:1657520100595-569.png]]
129 129  
130 130  (((
131 131  
... ... @@ -132,30 +132,67 @@
132 132  )))
133 133  
134 134  
135 -== 2.2 ​ Configure the NDDS75 ==
175 +== 2.2 ​ Configure the N95S31B ==
136 136  
137 137  
178 +=== 2.2.1  Power On N95S31B ===
179 +
180 +
181 +[[image:image-20220709150546-2.png]]
182 +
183 +
138 138  === 2.2.1 Test Requirement ===
139 139  
186 +
140 140  (((
141 -To use NDDS75 in your city, make sure meet below requirements:
188 +To use N95S31B in your city, make sure meet below requirements:
142 142  )))
143 143  
144 -* Your local operator has already distributed a NB-IoT Network there.
145 -* The local NB-IoT network used the band that NSE01 supports.
146 -* 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 +)))
147 147  
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
202 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
150 150  )))
151 151  
205 +(((
206 +N95S31B supports different communication protocol such as :
207 +)))
152 152  
153 -[[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 +)))
154 154  
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 +)))
155 155  
227 +
228 +)))
156 156  
157 -=== 2.2.2 Insert SIM card ===
230 +[[image:1657350625843-586.png]]
158 158  
232 +
233 +
234 +=== 2.2.3  Insert SIM card ===
235 +
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]]
245 +[[image:1657351240556-536.png]]
169 169  
170 170  
171 171  
172 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
249 +=== 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.
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.
177 177  )))
178 178  )))
179 179  
180 -[[image:image-20220709092052-2.png]]
257 +[[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.
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.
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/]]
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/]]
207 207  )))
208 208  
209 209  
210 210  
211 -=== 2.2.4 Use CoAP protocol to uplink data ===
288 +=== 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  
293 +(((
216 216  **Use below commands:**
295 +)))
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
297 +* (((
298 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
299 +)))
300 +* (((
301 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
302 +)))
303 +* (((
304 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
305 +)))
221 221  
307 +(((
308 +
309 +
222 222  For parameter description, please refer to AT command set
311 +)))
223 223  
224 -[[image:1657330452568-615.png]]
313 +[[image:1657352146020-183.png]]
225 225  
226 226  
316 +(((
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.
318 +)))
228 228  
229 -[[image:1657330472797-498.png]]
320 +[[image:1657352185396-303.png]]
230 230  
231 231  
232 232  
233 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
324 +=== 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
327 +* (% 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
329 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
239 239  
240 -[[image:1657330501006-241.png]]
331 +[[image:1657352391268-297.png]]
241 241  
242 242  
243 -[[image:1657330533775-472.png]]
334 +[[image:1657352403317-397.png]]
244 244  
245 245  
246 246  
247 -=== 2.2.6 Use MQTT protocol to uplink data ===
338 +=== 2.2.7  Use MQTT protocol to uplink data ===
248 248  
340 +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
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
257 257  
258 -[[image:1657249978444-674.png]]
350 +[[image:1657352634421-276.png]]
259 259  
260 260  
261 -[[image:1657330723006-866.png]]
353 +[[image:1657352645687-385.png]]
262 262  
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 +)))
263 263  
359 +
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.
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.
266 266  )))
267 267  
268 268  
269 269  
270 -=== 2.2.7 Use TCP protocol to uplink data ===
366 +=== 2.2.8  Use TCP protocol to uplink data ===
271 271  
368 +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]]
373 +[[image:1657352898400-901.png]]
277 277  
278 278  
279 -[[image:image-20220709093918-2.png]]
376 +[[image:1657352914475-252.png]]
280 280  
281 281  
282 282  
283 -=== 2.2.8 Change Update Interval ===
380 +=== 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,59 +287,51 @@
287 287  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
288 288  
289 289  (((
290 -(% style="color:red" %)**NOTE:**
387 +
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  
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 +)))
303 303  
304 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
305 -|=(% style="width: 80px;" %)(((
306 -**Size(bytes)**
307 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]]
309 309  
310 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.
401 +For example:
312 312  )))
313 313  
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 +)))
314 314  
315 -[[image:1657331036973-987.png]]
316 316  
317 317  (((
318 -The payload is ASCII string, representative same HEX:
410 +The uplink payloads are composed in  ASCII String. For example:
319 319  )))
320 320  
321 321  (((
322 -0x72403155615900640c6c19029200 where:
414 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
323 323  )))
324 324  
325 -* (((
326 -Device ID: 0x724031556159 = 724031556159
417 +(((
418 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
327 327  )))
328 -* (((
329 -Version: 0x0064=100=1.0.0
420 +
421 +
422 +(((
423 +(% style="color:red" %)**NOTE:**
330 330  )))
331 331  
332 -* (((
333 -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"]].
334 334  )))
335 -* (((
336 -Signal: 0x19 = 25
337 -)))
338 -* (((
339 -Distance: 0x0292= 658 mm
340 -)))
341 -* (((
342 -Interrupt: 0x00 = 0
430 +1. (((
431 +By default, the device will send an uplink message every 1 hour.
343 343  
344 344  
345 345  
... ... @@ -346,172 +346,189 @@
346 346  
347 347  )))
348 348  
349 -== 2.4  Payload Explanation and Sensor Interface ==
438 +=== 2.3.1  Payload Analyze ===
350 350  
440 +N95S31B uplink payload includes in total 21 bytes
351 351  
352 -=== 2.4.1  Device ID ===
353 353  
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" %)(((
354 354  (((
355 -By default, the Device ID equal to the last 6 bytes of IMEI.
449 +Reserve/ Same as NBSN95 CFGMOD=1
356 356  )))
357 357  
358 358  (((
359 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
453 +No function here.
360 360  )))
455 +)))|(% style="width:77px" %)(((
456 +(((
457 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
458 +)))
361 361  
362 362  (((
363 -**Example:**
461 +By SHT31
364 364  )))
463 +)))|(% style="width:80px" %)(((
464 +(((
465 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
466 +)))
365 365  
366 366  (((
367 -AT+DEUI=A84041F15612
469 +By SHT31
368 368  )))
471 +)))
369 369  
370 370  (((
371 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
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.
372 372  )))
477 +)))
373 373  
374 374  
480 +[[image:1657354294009-643.png]]
375 375  
376 -=== 2.4.2  Version Info ===
377 377  
483 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
484 +
485 +* Device ID: 0x724031607457 = 724031607457
486 +* Version: 0x006e=110=1.1.0
487 +
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
494 +
378 378  (((
379 -Specify the software version: 0x64=100, means firmware version 1.00.
496 +
380 380  )))
381 381  
382 382  (((
383 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
500 +
384 384  )))
385 385  
386 386  
504 +=== 2.3.2  Device ID ===
387 387  
388 -=== 2.4.3  Battery Info ===
506 +(((
507 +By default, the Device ID equal to the last 6 bytes of IMEI.
508 +)))
389 389  
390 390  (((
391 -Check the battery voltage for LSE01.
511 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
392 392  )))
393 393  
394 394  (((
395 -Ex1: 0x0B45 = 2885mV
515 +**Example:**
396 396  )))
397 397  
398 398  (((
399 -Ex2: 0x0B49 = 2889mV
519 +AT+DEUI=A84041F15612
400 400  )))
401 401  
522 +(((
523 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
524 +)))
402 402  
403 403  
404 -=== 2.4.4  Signal Strength ===
405 405  
406 -(((
407 -NB-IoT Network signal Strength.
408 -)))
528 +=== 2.3.3  Version Info ===
409 409  
410 410  (((
411 -**Ex1: 0x1d = 29**
531 +These bytes include the hardware and software version.
412 412  )))
413 413  
414 414  (((
415 -(% style="color:blue" %)**0**(%%)  -113dBm or less
535 +Higher byte: Specify hardware version: always 0x00 for N95S31B
416 416  )))
417 417  
418 418  (((
419 -(% style="color:blue" %)**1**(%%)  -111dBm
539 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
420 420  )))
421 421  
422 422  (((
423 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
543 +
424 424  )))
425 425  
426 426  (((
427 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
547 +For example: 0x00 6E: this device is N95S31B with firmware version 110.
428 428  )))
429 429  
430 430  (((
431 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
551 +
432 432  )))
433 433  
434 434  
555 +=== 2.3.4  Battery Info ===
435 435  
436 -=== 2.4.5  Distance ===
437 -
438 -Get the distance. Flat object range 280mm - 7500mm.
439 -
440 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
441 -
442 442  (((
443 -(((
444 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
558 +Ex1: 0x0B45 = 2885mV
445 445  )))
446 -)))
447 447  
448 448  (((
449 -
562 +Ex2: 0x0B49 = 2889mV
450 450  )))
451 451  
452 -(((
453 -
454 -)))
455 455  
456 -=== 2.4.6  Digital Interrupt ===
457 457  
567 +=== 2.3.5  Signal Strength ===
568 +
458 458  (((
459 -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.
570 +NB-IoT Network signal Strength.
460 460  )))
461 461  
462 462  (((
463 -The command is:
574 +**Ex1: 0x1d = 29**
464 464  )))
465 465  
466 466  (((
467 -(% 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]])**.**
578 +(% style="color:blue" %)**0**(%%)  -113dBm or less
468 468  )))
469 469  
470 -
471 471  (((
472 -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.
582 +(% style="color:blue" %)**1**(%%)  -111dBm
473 473  )))
474 474  
475 -
476 476  (((
477 -Example:
586 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
478 478  )))
479 479  
480 480  (((
481 -0x(00): Normal uplink packet.
590 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
482 482  )))
483 483  
484 484  (((
485 -0x(01): Interrupt Uplink Packet.
594 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
486 486  )))
487 487  
488 488  
489 489  
490 -=== 2.4.7  ​+5V Output ===
599 +=== 2.3.6  Temperature & Humidity ===
491 491  
492 -(((
493 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
494 -)))
601 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
495 495  
603 +[[image:image-20220709161741-3.png]]
496 496  
497 -(((
498 -The 5V output time can be controlled by AT Command.
499 -)))
500 500  
501 -(((
502 -(% style="color:blue" %)**AT+5VT=1000**
503 -)))
606 +Convert the read byte to decimal and divide it by ten.
504 504  
505 -(((
506 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
507 -)))
508 508  
609 +**Example:**
509 509  
611 +Temperature:  Read:00ec (H) = 236(D)  Value:  236 /10=23.6℃
510 510  
511 -== 2.5  Downlink Payload ==
613 +Humidity:    Read:0295(H)=661(D)    Value:  661 / 10=66.1, So 66.1%
512 512  
513 -By default, NDDS75 prints the downlink payload to console port.
514 514  
616 +
617 +== 2.4  Downlink Payload ==
618 +
619 +By default, N95S31B prints the downlink payload to console port.
620 +
515 515  [[image:image-20220709100028-1.png]]
516 516  
517 517  
... ... @@ -548,7 +548,7 @@
548 548  )))
549 549  
550 550  (((
551 -If payload = 0x04FF, it will reset the NDDS75
657 +If payload = 0x04FF, it will reset the N95S31B
552 552  )))
553 553  
554 554  
... ... @@ -560,47 +560,16 @@
560 560  
561 561  
562 562  
563 -== 2.6  ​LED Indicator ==
669 +== 2.5  ​Battery Analysis ==
564 564  
671 +=== 2.5.1  ​Battery Type ===
565 565  
566 -The NDDS75 has an internal LED which is to show the status of different state.
567 567  
568 -
569 -* 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)
570 -* Then the LED will be on for 1 second means device is boot normally.
571 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
572 -* For each uplink probe, LED will be on for 500ms.
573 -
574 574  (((
575 -
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.
576 576  )))
577 577  
578 -
579 -
580 -== 2.7  ​Firmware Change Log ==
581 -
582 -
583 -Download URL & Firmware Change log
584 -
585 585  (((
586 -[[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/]]
587 -)))
588 -
589 -
590 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
591 -
592 -
593 -
594 -== 2.8  ​Battery Analysis ==
595 -
596 -=== 2.8.1  ​Battery Type ===
597 -
598 -
599 -(((
600 -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.
601 -)))
602 -
603 -(((
604 604  The battery is designed to last for several years depends on the actually use environment and update interval. 
605 605  )))
606 606  
... ... @@ -618,56 +618,35 @@
618 618  
619 619  
620 620  
621 -=== 2.8.2  Power consumption Analyze ===
696 +=== 2.5.2  Power consumption Analyze ===
622 622  
623 623  (((
624 -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.
625 625  )))
626 626  
627 -
628 628  (((
629 -Instruction to use as below:
703 +
630 630  )))
631 631  
632 -(((
633 -(% 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/]]
634 -)))
635 635  
707 +=== 2.5.3  ​Battery Note ===
636 636  
637 637  (((
638 -(% 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.
639 639  )))
640 640  
641 -* (((
642 -Product Model
643 -)))
644 -* (((
645 -Uplink Interval
646 -)))
647 -* (((
648 -Working Mode
649 -)))
650 650  
651 -(((
652 -And the Life expectation in difference case will be shown on the right.
653 -)))
654 654  
655 -[[image:image-20220709110451-3.png]]
715 +=== 2.5.4  Replace the battery ===
656 656  
657 657  
658 -
659 -=== 2.8.3  ​Battery Note ===
660 -
661 661  (((
662 -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.
663 663  )))
664 664  
665 665  
666 -
667 -=== 2.8.4  Replace the battery ===
668 -
669 669  (((
670 -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).
671 671  )))
672 672  
673 673  
... ... @@ -690,7 +690,7 @@
690 690  
691 691  == 4.1  Access AT Commands ==
692 692  
693 -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/]]
694 694  
695 695  
696 696  AT+<CMD>?  : Help on <CMD>
... ... @@ -778,8 +778,12 @@
778 778  )))
779 779  
780 780  (((
781 -(% 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.
782 782  )))
840 +)))
783 783  
784 784  
785 785  
... ... @@ -810,7 +810,7 @@
810 810  = 7. ​ Order Info =
811 811  
812 812  
813 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
871 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
814 814  
815 815  
816 816  (% class="wikigeneratedid" %)
... ... @@ -825,7 +825,7 @@
825 825  
826 826  (% style="color:#037691" %)**Package Includes**:
827 827  
828 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
886 +* N95S31B NB-IoT Temperature and Humidity Sensor
829 829  * External antenna x 1
830 830  )))
831 831  
... ... @@ -834,11 +834,10 @@
834 834  
835 835  (% style="color:#037691" %)**Dimension and weight**:
836 836  
837 -
838 838  * Device Size: 13.0 x 5 x 4.5 cm
839 839  * Device Weight: 150g
840 -* Package Size / pcs : 15 x 12x 5.5 cm
841 -* Weight / pcs : 220g
897 +* Package Size / pcs : 14.0 x 8x 5 cm
898 +* Weight / pcs : 180g
842 842  )))
843 843  
844 844  (((
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