Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.28 >
edited by Xiaoling
on 2022/07/11 08:37
To version < 100.1 >
edited by Xiaoling
on 2022/07/09 14:47
>
Change comment: Uploaded new attachment "image-20220709144723-1.png", version {1}

Summary

Details

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

Applications

Navigation

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