Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 97.18 >
edited by Xiaoling
on 2022/07/09 11:54
To version < 118.4 >
edited by Xiaoling
on 2022/07/12 17:29
>
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,63 +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 -(((
26 -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 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*.
27 27  )))
28 28  
29 29  (((
30 -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.
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 31  )))
32 32  
33 33  (((
34 -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.
34 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
35 35  )))
36 36  
37 37  (((
38 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
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 39  )))
40 40  
41 41  (((
42 -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)
42 +
43 43  )))
44 44  
45 45  (((
46 -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.
46 +~* make sure you have NB-IoT coverage locally.
47 47  )))
48 -)))
49 49  
50 50  
51 51  )))
52 52  
53 -[[image:1657327959271-447.png]]
52 +[[image:1657348284168-431.png]]
54 54  
55 55  
56 56  
57 57  == 1.2 ​ Features ==
58 58  
59 -
60 60  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
61 -* Ultra low power consumption
62 -* Distance Detection by Ultrasonic technology
63 -* Flat object range 280mm - 7500mm
64 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
65 -* Cable Length: 25cm
59 +* Monitor Temperature & Humidity via SHT31
66 66  * AT Commands to change parameters
67 67  * Uplink on periodically
68 68  * Downlink to change configure
69 69  * IP66 Waterproof Enclosure
64 +* Ultra-Low Power consumption
65 +* AT Commands to change parameters
70 70  * Micro SIM card slot for NB-IoT SIM
71 71  * 8500mAh Battery for long term use
72 72  
69 +
70 +
73 73  == 1.3  Specification ==
74 74  
75 75  
... ... @@ -95,10 +95,7 @@
95 95  * Max continuously current: 130mA
96 96  * Max boost current: 2A, 1 second
97 97  
98 -(% style="color:#037691" %)**Power Consumption**
99 99  
100 -* STOP Mode: 10uA @ 3.3v
101 -* Max transmit power: 350mA@3.3v
102 102  
103 103  == ​1.4  Applications ==
104 104  
... ... @@ -113,24 +113,57 @@
113 113  ​
114 114  
115 115  
116 -== 1.5  Pin Definitions ==
111 +== 1.5  Pin Definitions & Switch ==
117 117  
113 +N95S31B use the mother board from NBSN95 which as below.
118 118  
119 -[[image:1657328609906-564.png]]
115 +[[image:image-20220709144723-1.png]]
120 120  
121 121  
118 +=== 1.5.1 Jumper JP2 ===
122 122  
123 -= 2.  Use NDDS75 to communicate with IoT Server =
120 +Power on Device when put this jumper.
124 124  
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 +
125 125  == 2.1  How it works ==
126 126  
154 +
127 127  (((
128 -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.
129 129  )))
130 130  
131 131  
132 132  (((
133 -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:
134 134  )))
135 135  
136 136  (((
... ... @@ -137,7 +137,7 @@
137 137  
138 138  )))
139 139  
140 -[[image:1657328659945-416.png]]
168 +[[image:1657520100595-569.png]]
141 141  
142 142  (((
143 143  
... ... @@ -144,30 +144,67 @@
144 144  )))
145 145  
146 146  
147 -== 2.2 ​ Configure the NDDS75 ==
175 +== 2.2 ​ Configure the N95S31B ==
148 148  
149 149  
178 +=== 2.2.1  Power On N95S31B ===
179 +
180 +
181 +[[image:image-20220709150546-2.png]]
182 +
183 +
150 150  === 2.2.1 Test Requirement ===
151 151  
186 +
152 152  (((
153 -To use NDDS75 in your city, make sure meet below requirements:
188 +To use N95S31B in your city, make sure meet below requirements:
154 154  )))
155 155  
156 -* Your local operator has already distributed a NB-IoT Network there.
157 -* The local NB-IoT network used the band that NSE01 supports.
158 -* 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 +)))
159 159  
160 160  (((
161 -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.
162 162  )))
163 163  
205 +(((
206 +N95S31B supports different communication protocol such as :
207 +)))
164 164  
165 -[[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 +)))
166 166  
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 +)))
167 167  
227 +
228 +)))
168 168  
169 -=== 2.2.2 Insert SIM card ===
230 +[[image:1657350625843-586.png]]
170 170  
232 +
233 +
234 +=== 2.2.3  Insert SIM card ===
235 +
171 171  (((
172 172  Insert the NB-IoT Card get from your provider.
173 173  )))
... ... @@ -177,19 +177,19 @@
177 177  )))
178 178  
179 179  
180 -[[image:1657328884227-504.png]]
245 +[[image:1657351240556-536.png]]
181 181  
182 182  
183 183  
184 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
249 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
185 185  
186 186  (((
187 187  (((
188 -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.
189 189  )))
190 190  )))
191 191  
192 -[[image:image-20220709092052-2.png]]
257 +[[image:1657351312545-300.png]]
193 193  
194 194  **Connection:**
195 195  
... ... @@ -209,18 +209,18 @@
209 209  * Flow Control: (% style="color:green" %)**None**
210 210  
211 211  (((
212 -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.
213 213  )))
214 214  
215 215  [[image:1657329814315-101.png]]
216 216  
217 217  (((
218 -(% 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/]]
219 219  )))
220 220  
221 221  
222 222  
223 -=== 2.2.4 Use CoAP protocol to uplink data ===
288 +=== 2.2.5  Use CoAP protocol to uplink data ===
224 224  
225 225  (% 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/]]
226 226  
... ... @@ -240,10 +240,12 @@
240 240  )))
241 241  
242 242  (((
308 +
309 +
243 243  For parameter description, please refer to AT command set
244 244  )))
245 245  
246 -[[image:1657330452568-615.png]]
313 +[[image:1657352146020-183.png]]
247 247  
248 248  
249 249  (((
... ... @@ -250,11 +250,11 @@
250 250  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.
251 251  )))
252 252  
253 -[[image:1657330472797-498.png]]
320 +[[image:1657352185396-303.png]]
254 254  
255 255  
256 256  
257 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
324 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
258 258  
259 259  
260 260  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -261,15 +261,16 @@
261 261  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
262 262  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
263 263  
264 -[[image:1657330501006-241.png]]
331 +[[image:1657352391268-297.png]]
265 265  
266 266  
267 -[[image:1657330533775-472.png]]
334 +[[image:1657352403317-397.png]]
268 268  
269 269  
270 270  
271 -=== 2.2.6 Use MQTT protocol to uplink data ===
338 +=== 2.2.7  Use MQTT protocol to uplink data ===
272 272  
340 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
273 273  
274 274  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
275 275  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -276,35 +276,40 @@
276 276  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
277 277  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
278 278  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
279 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
280 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic 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
281 281  
282 -[[image:1657249978444-674.png]]
350 +[[image:1657352634421-276.png]]
283 283  
284 284  
285 -[[image:1657330723006-866.png]]
353 +[[image:1657352645687-385.png]]
286 286  
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 +)))
287 287  
359 +
288 288  (((
289 -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.
290 290  )))
291 291  
292 292  
293 293  
294 -=== 2.2.7 Use TCP protocol to uplink data ===
366 +=== 2.2.8  Use TCP protocol to uplink data ===
295 295  
368 +This feature is supported since firmware version v110
296 296  
297 297  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
298 298  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
299 299  
300 -[[image:image-20220709093918-1.png]]
373 +[[image:1657352898400-901.png]]
301 301  
302 302  
303 -[[image:image-20220709093918-2.png]]
376 +[[image:1657352914475-252.png]]
304 304  
305 305  
306 306  
307 -=== 2.2.8 Change Update Interval ===
380 +=== 2.2.9  Change Update Interval ===
308 308  
309 309  User can use below command to change the (% style="color:green" %)**uplink interval**.
310 310  
... ... @@ -311,59 +311,51 @@
311 311  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
312 312  
313 313  (((
314 -(% style="color:red" %)**NOTE:**
387 +
315 315  )))
316 316  
317 -(((
318 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
319 -)))
320 320  
321 321  
322 -
323 323  == 2.3  Uplink Payload ==
324 324  
325 -In this mode, uplink payload includes in total 14 bytes
326 326  
395 +(((
396 +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.
397 +)))
327 327  
328 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
329 -|=(% style="width: 60px;" %)(((
330 -**Size(bytes)**
331 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
332 -|(% 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"]]
333 333  
334 334  (((
335 -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:
336 336  )))
337 337  
404 +(((
405 + (% 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.
406 +)))
338 338  
339 -[[image:1657331036973-987.png]]
340 340  
341 341  (((
342 -The payload is ASCII string, representative same HEX:
410 +The uplink payloads are composed in  ASCII String. For example:
343 343  )))
344 344  
345 345  (((
346 -0x72403155615900640c6c19029200 where:
414 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
347 347  )))
348 348  
349 -* (((
350 -Device ID: 0x724031556159 = 724031556159
417 +(((
418 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
351 351  )))
352 -* (((
353 -Version: 0x0064=100=1.0.0
420 +
421 +
422 +(((
423 +(% style="color:red" %)**NOTE:**
354 354  )))
355 355  
356 -* (((
357 -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"]].
358 358  )))
359 -* (((
360 -Signal: 0x19 = 25
361 -)))
362 -* (((
363 -Distance: 0x0292= 658 mm
364 -)))
365 -* (((
366 -Interrupt: 0x00 = 0
430 +1. (((
431 +By default, the device will send an uplink message every 1 hour.
367 367  
368 368  
369 369  
... ... @@ -370,105 +370,108 @@
370 370  
371 371  )))
372 372  
373 -== 2.4  Payload Explanation and Sensor Interface ==
438 +=== 2.3.1  Payload Analyze ===
374 374  
440 +N95S31B uplink payload includes in total 21 bytes
375 375  
376 -=== 2.4.1  Device ID ===
377 377  
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" %)(((
378 378  (((
379 -By default, the Device ID equal to the last 6 bytes of IMEI.
449 +Reserve/ Same as NBSN95 CFGMOD=1
380 380  )))
381 381  
382 382  (((
383 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
453 +No function here.
384 384  )))
385 -
455 +)))|(% style="width:77px" %)(((
386 386  (((
387 -**Example:**
457 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
388 388  )))
389 389  
390 390  (((
391 -AT+DEUI=A84041F15612
461 +By SHT31
392 392  )))
393 -
463 +)))|(% style="width:80px" %)(((
394 394  (((
395 -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"]]
396 396  )))
397 397  
398 -
399 -
400 -=== 2.4.2  Version Info ===
401 -
402 402  (((
403 -Specify the software version: 0x64=100, means firmware version 1.00.
469 +By SHT31
404 404  )))
471 +)))
405 405  
406 406  (((
407 -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.
408 408  )))
477 +)))
409 409  
410 410  
480 +[[image:1657354294009-643.png]]
411 411  
412 -=== 2.4.3  Battery Info ===
413 413  
414 -(((
415 -Ex1: 0x0B45 = 2885mV
416 -)))
483 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
417 417  
418 -(((
419 -Ex2: 0x0B49 = 2889mV
420 -)))
485 +* Device ID: 0x724031607457 = 724031607457
486 +* Version: 0x006e=110=1.1.0
421 421  
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
422 422  
423 -
424 -=== 2.4.4  Signal Strength ===
425 -
426 426  (((
427 -NB-IoT Network signal Strength.
496 +
428 428  )))
429 429  
430 430  (((
431 -**Ex1: 0x1d = 29**
500 +
432 432  )))
433 433  
503 +
504 +=== 2.3.2  Device ID ===
505 +
434 434  (((
435 -(% style="color:blue" %)**0**(%%)  -113dBm or less
507 +By default, the Device ID equal to the last 6 bytes of IMEI.
436 436  )))
437 437  
438 438  (((
439 -(% style="color:blue" %)**1**(%%)  -111dBm
511 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
440 440  )))
441 441  
442 442  (((
443 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 +**Example:**
444 444  )))
445 445  
446 446  (((
447 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 +AT+DEUI=A84041F15612
448 448  )))
449 449  
450 450  (((
451 -(% 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.
452 452  )))
453 453  
454 454  
455 455  
456 -=== 2.4.5  Distance ===
528 +=== 2.3.3  Version Info ===
457 457  
458 -Get the distance. Flat object range 280mm - 7500mm.
459 -
460 460  (((
461 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
531 +These bytes include the hardware and software version.
462 462  )))
463 463  
464 464  (((
465 -(((
466 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
535 +Higher byte: Specify hardware version: always 0x00 for N95S31B
467 467  )))
468 -)))
469 469  
470 470  (((
471 -
539 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110
472 472  )))
473 473  
474 474  (((
... ... @@ -475,63 +475,79 @@
475 475  
476 476  )))
477 477  
478 -=== 2.4.6  Digital Interrupt ===
479 -
480 480  (((
481 -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.
482 482  )))
483 483  
484 484  (((
485 -The command is:
551 +
486 486  )))
487 487  
554 +
555 +=== 2.3.4  Battery Info ===
556 +
488 488  (((
489 -(% 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
490 490  )))
491 491  
492 -
493 493  (((
494 -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
495 495  )))
496 496  
497 497  
566 +
567 +=== 2.3.5  Signal Strength ===
568 +
498 498  (((
499 -Example:
570 +NB-IoT Network signal Strength.
500 500  )))
501 501  
502 502  (((
503 -0x(00): Normal uplink packet.
574 +**Ex1: 0x1d = 29**
504 504  )))
505 505  
506 506  (((
507 -0x(01): Interrupt Uplink Packet.
578 +(% style="color:blue" %)**0**(%%)  -113dBm or less
508 508  )))
509 509  
510 -
511 -
512 -=== 2.4.7  ​+5V Output ===
513 -
514 514  (((
515 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
582 +(% style="color:blue" %)**1**(%%)  -111dBm
516 516  )))
517 517  
518 -
519 519  (((
520 -The 5V output time can be controlled by AT Command.
586 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
521 521  )))
522 522  
523 523  (((
524 -(% style="color:blue" %)**AT+5VT=1000**
590 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
525 525  )))
526 526  
527 527  (((
528 -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
529 529  )))
530 530  
531 531  
532 532  
533 -== 2.5  Downlink Payload ==
599 +=== 2.3.6  Temperature & Humidity ===
534 534  
601 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
602 +
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 +
535 535  By default, NDDS75 prints the downlink payload to console port.
536 536  
537 537  [[image:image-20220709100028-1.png]]
... ... @@ -582,51 +582,16 @@
582 582  
583 583  
584 584  
585 -== 2.6  ​LED Indicator ==
669 +== 2.5  ​Battery Analysis ==
586 586  
671 +=== 2.5.1  ​Battery Type ===
587 587  
588 -The NDDS75 has an internal LED which is to show the status of different state.
589 589  
590 -
591 -* 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)
592 -* Then the LED will be on for 1 second means device is boot normally.
593 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
594 -* For each uplink probe, LED will be on for 500ms.
595 -
596 596  (((
597 -
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.
598 598  )))
599 599  
600 -
601 -
602 -== 2.7  ​Firmware Change Log ==
603 -
604 -
605 605  (((
606 -Download URL & Firmware Change log
607 -)))
608 -
609 -(((
610 -[[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/]]
611 -)))
612 -
613 -
614 -(((
615 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
616 -)))
617 -
618 -
619 -
620 -== 2.8  ​Battery Analysis ==
621 -
622 -=== 2.8.1  ​Battery Type ===
623 -
624 -
625 -(((
626 -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.
627 -)))
628 -
629 -(((
630 630  The battery is designed to last for several years depends on the actually use environment and update interval. 
631 631  )))
632 632  
... ... @@ -644,56 +644,35 @@
644 644  
645 645  
646 646  
647 -=== 2.8.2  Power consumption Analyze ===
696 +=== 2.5.2  Power consumption Analyze ===
648 648  
649 649  (((
650 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
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.
651 651  )))
652 652  
653 -
654 654  (((
655 -Instruction to use as below:
703 +
656 656  )))
657 657  
658 -(((
659 -(% 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/]]
660 -)))
661 661  
707 +=== 2.5.3  ​Battery Note ===
662 662  
663 663  (((
664 -(% 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.
665 665  )))
666 666  
667 -* (((
668 -Product Model
669 -)))
670 -* (((
671 -Uplink Interval
672 -)))
673 -* (((
674 -Working Mode
675 -)))
676 676  
677 -(((
678 -And the Life expectation in difference case will be shown on the right.
679 -)))
680 680  
681 -[[image:image-20220709110451-3.png]]
715 +=== 2.5.4  Replace the battery ===
682 682  
683 683  
684 -
685 -=== 2.8.3  ​Battery Note ===
686 -
687 687  (((
688 -The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
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.
689 689  )))
690 690  
691 691  
692 -
693 -=== 2.8.4  Replace the battery ===
694 -
695 695  (((
696 -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).
697 697  )))
698 698  
699 699  
... ... @@ -716,7 +716,7 @@
716 716  
717 717  == 4.1  Access AT Commands ==
718 718  
719 -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/]]
720 720  
721 721  
722 722  AT+<CMD>?  : Help on <CMD>
... ... @@ -804,8 +804,12 @@
804 804  )))
805 805  
806 806  (((
807 -(% 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.
808 808  )))
840 +)))
809 809  
810 810  
811 811  
... ... @@ -836,7 +836,7 @@
836 836  = 7. ​ Order Info =
837 837  
838 838  
839 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
871 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY**
840 840  
841 841  
842 842  (% class="wikigeneratedid" %)
... ... @@ -851,7 +851,7 @@
851 851  
852 852  (% style="color:#037691" %)**Package Includes**:
853 853  
854 -* NSE01 NB-IoT Distance Detect Sensor Node x 1
886 +* N95S31B NB-IoT Temperature and Humidity Sensor
855 855  * External antenna x 1
856 856  )))
857 857  
... ... @@ -860,11 +860,10 @@
860 860  
861 861  (% style="color:#037691" %)**Dimension and weight**:
862 862  
863 -
864 864  * Device Size: 13.0 x 5 x 4.5 cm
865 865  * Device Weight: 150g
866 -* Package Size / pcs : 15 x 12x 5.5 cm
867 -* Weight / pcs : 220g
897 +* Package Size / pcs : 14.0 x 8x 5 cm
898 +* Weight / pcs : 180g
868 868  )))
869 869  
870 870  (((
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