Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 19 added, 0 removed)
- 1657348034241-728.png
- 1657348284168-431.png
- 1657350248151-650.png
- 1657350625843-586.png
- 1657351240556-536.png
- 1657351312545-300.png
- 1657352146020-183.png
- 1657352185396-303.png
- 1657352391268-297.png
- 1657352403317-397.png
- 1657352634421-276.png
- 1657352645687-385.png
- 1657352898400-901.png
- 1657352914475-252.png
- 1657354294009-643.png
- 1657520100595-569.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N DDS75 NB-IoTDistanceDetect Sensor User Manual1 +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,51 +13,58 @@ 13 13 14 14 15 15 16 - 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==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:165732 7959271-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 59 59 60 - 61 61 == 1.3 Specification == 62 62 63 63 ... ... @@ -83,13 +83,7 @@ 83 83 * Max continuously current: 130mA 84 84 * Max boost current: 2A, 1 second 85 85 86 -(% style="color:#037691" %)**Power Consumption** 87 87 88 -* STOP Mode: 10uA @ 3.3v 89 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 90 - 91 - 92 - 93 93 == 1.4 Applications == 94 94 95 95 * Smart Buildings & Home Automation ... ... @@ -103,25 +103,57 @@ 103 103 104 104 105 105 109 +== 1.5 Pin Definitions & Switch == 106 106 107 - == 1.5PinDefinitions==111 +N95S31B use the mother board from NBSN95 which as below. 108 108 113 +[[image:image-20220709144723-1.png]] 109 109 110 -[[image:1657328609906-564.png]] 111 111 116 +=== 1.5.1 Jumper JP2 === 112 112 118 +Power on Device when put this jumper. 113 113 114 -= 2. Use NDDS75 to communicate with IoT Server = 115 115 121 + 122 +=== 1.5.2 BOOT MODE / SW1 === 123 + 124 +((( 125 +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. 126 +))) 127 + 128 +((( 129 +2) Flash: work mode, device starts to work and send out console output for further debug 130 +))) 131 + 132 + 133 + 134 +=== 1.5.3 Reset Button === 135 + 136 +Press to reboot the device. 137 + 138 + 139 + 140 +=== 1.5.4 LED === 141 + 142 +It will flash: 143 + 144 +1. When boot the device in flash mode 145 +1. Send an uplink packet 146 + 147 + 148 += 2. Use N95S31B to communicate with IoT Server = 149 + 116 116 == 2.1 How it works == 117 117 152 + 118 118 ((( 119 -The N DDS75 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.154 +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. 120 120 ))) 121 121 122 122 123 123 ((( 124 -The diagram below shows the working flow in default firmware of N DDS75:159 +The diagram below shows the working flow in default firmware of N95S31B: 125 125 ))) 126 126 127 127 ((( ... ... @@ -128,7 +128,7 @@ 128 128 129 129 ))) 130 130 131 -[[image:1657328 659945-416.png]]166 +[[image:1657350248151-650.png]] 132 132 133 133 ((( 134 134 ... ... @@ -135,30 +135,67 @@ 135 135 ))) 136 136 137 137 138 -== 2.2 Configure the N DDS75 ==173 +== 2.2 Configure the N95S31B == 139 139 140 140 176 +=== 2.2.1 Power On N95S31B === 177 + 178 + 179 +[[image:image-20220709150546-2.png]] 180 + 181 + 141 141 === 2.2.1 Test Requirement === 142 142 184 + 143 143 ((( 144 -To use N DDS75 in your city, make sure meet below requirements:186 +To use N95S31B in your city, make sure meet below requirements: 145 145 ))) 146 146 147 -* Your local operator has already distributed a NB-IoT Network there. 148 -* The local NB-IoT network used the band that NSE01 supports. 149 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 189 +* ((( 190 +Your local operator has already distributed a NB-IoT Network there. 191 +))) 192 +* ((( 193 +The local NB-IoT network used the band that N95S31B supports. 194 +))) 195 +* ((( 196 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 197 +))) 150 150 151 151 ((( 152 -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 server200 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 153 153 ))) 154 154 203 +((( 204 +N95S31B supports different communication protocol such as : 205 +))) 155 155 156 -[[image:1657328756309-230.png]] 207 +((( 208 +* ((( 209 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 210 +))) 211 +* ((( 212 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 213 +))) 214 +* ((( 215 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 216 +))) 217 +* ((( 218 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 219 +))) 157 157 221 +((( 222 +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. 223 +))) 158 158 225 + 226 +))) 159 159 160 - ===2.2.2 Insert SIM card ===228 +[[image:1657350625843-586.png]] 161 161 230 + 231 + 232 +=== 2.2.3 Insert SIM card === 233 + 162 162 ((( 163 163 Insert the NB-IoT Card get from your provider. 164 164 ))) ... ... @@ -168,19 +168,19 @@ 168 168 ))) 169 169 170 170 171 -[[image:165732 8884227-504.png]]243 +[[image:1657351240556-536.png]] 172 172 173 173 174 174 175 -=== 2.2. 3DDS75 to configure it ===247 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 176 176 177 177 ((( 178 178 ((( 179 -User need to configure DDS75 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 toDDS75 and use AT Commands to configure it, as below.251 +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. 180 180 ))) 181 181 ))) 182 182 183 -[[image: image-20220709092052-2.png]]255 +[[image:1657351312545-300.png]] 184 184 185 185 **Connection:** 186 186 ... ... @@ -200,90 +200,110 @@ 200 200 * Flow Control: (% style="color:green" %)**None** 201 201 202 202 ((( 203 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.275 +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. 204 204 ))) 205 205 206 206 [[image:1657329814315-101.png]] 207 207 208 208 ((( 209 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]281 +(% 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/]] 210 210 ))) 211 211 212 212 213 213 214 -=== 2.2. 4286 +=== 2.2.5 Use CoAP protocol to uplink data === 215 215 216 216 (% 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/]] 217 217 218 218 291 +((( 219 219 **Use below commands:** 293 +))) 220 220 221 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 222 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 223 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 295 +* ((( 296 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 297 +))) 298 +* ((( 299 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 300 +))) 301 +* ((( 302 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 303 +))) 224 224 305 +((( 306 + 307 + 225 225 For parameter description, please refer to AT command set 309 +))) 226 226 227 -[[image:16573 30452568-615.png]]311 +[[image:1657352146020-183.png]] 228 228 229 229 314 +((( 230 230 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. 316 +))) 231 231 232 -[[image:16573 30472797-498.png]]318 +[[image:1657352185396-303.png]] 233 233 234 234 235 235 236 -=== 2.2. 5322 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 237 237 238 238 239 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 325 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 240 240 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 241 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 327 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 242 242 243 -[[image:16573 30501006-241.png]]329 +[[image:1657352391268-297.png]] 244 244 245 245 246 -[[image:16573 30533775-472.png]]332 +[[image:1657352403317-397.png]] 247 247 248 248 249 249 250 -=== 2.2. 6336 +=== 2.2.7 Use MQTT protocol to uplink data === 251 251 338 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 252 252 253 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 254 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 255 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 256 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 257 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 258 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT259 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT340 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 341 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 342 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 343 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 344 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 345 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 346 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 260 260 261 -[[image:165724 9978444-674.png]]348 +[[image:1657352634421-276.png]] 262 262 263 263 264 -[[image:16573 30723006-866.png]]351 +[[image:1657352645687-385.png]] 265 265 353 +((( 354 +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. 355 +))) 266 266 357 + 267 267 ((( 268 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.359 +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. 269 269 ))) 270 270 271 271 272 272 273 -=== 2.2. 7364 +=== 2.2.8 Use TCP protocol to uplink data === 274 274 366 +This feature is supported since firmware version v110 275 275 276 276 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 277 277 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 278 278 279 -[[image: image-20220709093918-1.png]]371 +[[image:1657352898400-901.png]] 280 280 281 281 282 -[[image: image-20220709093918-2.png]]374 +[[image:1657352914475-252.png]] 283 283 284 284 285 285 286 -=== 2.2. 8378 +=== 2.2.9 Change Update Interval === 287 287 288 288 User can use below command to change the (% style="color:green" %)**uplink interval**. 289 289 ... ... @@ -290,229 +290,235 @@ 290 290 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 291 291 292 292 ((( 293 - (%style="color:red" %)**NOTE:**385 + 294 294 ))) 295 295 296 -((( 297 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 298 -))) 299 299 300 300 301 - 302 302 == 2.3 Uplink Payload == 303 303 304 -In this mode, uplink payload includes in total 14 bytes 305 305 393 +((( 394 +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. 395 +))) 306 306 307 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 308 -|=(% style="width: 80px;" %)((( 309 -**Size(bytes)** 310 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 311 -|(% 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"]] 312 312 313 313 ((( 314 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.399 +For example: 315 315 ))) 316 316 402 +((( 403 + (% 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. 404 +))) 317 317 318 -[[image:1657331036973-987.png]] 319 319 320 320 ((( 321 -The payload is ASCIIstring,representative sameHEX:408 +The uplink payloads are composed in ASCII String. For example: 322 322 ))) 323 323 324 324 ((( 325 -0 x72403155615900640c6c19029200where:412 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 326 326 ))) 327 327 328 - *(((329 - DeviceID:0x724031556159=724031556159415 +((( 416 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 330 330 ))) 331 -* ((( 332 -Version: 0x0064=100=1.0.0 418 + 419 + 420 +((( 421 +(% style="color:red" %)**NOTE:** 333 333 ))) 334 334 335 -* ((( 336 -BAT: 0x0c6c = 3180 mV = 3.180V 424 +(% style="color:red" %) 425 +1. ((( 426 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]]. 337 337 ))) 338 - *(((339 - Signal:0x19=25428 +1. ((( 429 +By default, the device will send an uplink message every 1 hour. 340 340 ))) 341 -* ((( 342 -Distance: 0x0292= 658 mm 343 -))) 344 -* ((( 345 -Interrupt: 0x00 = 0 346 346 347 347 433 +=== 2.3.1 Payload Analyze === 348 348 349 - 350 -))) 435 +N95S31B uplink payload includes in total 21 bytes 351 351 352 -== 2.4 Payload Explanation and Sensor Interface == 353 353 354 - 355 -=== 2.4.1 Device ID === 356 - 438 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 439 +|=(% style="width: 60px;" %)((( 440 +**Size(bytes)** 441 +)))|=(% 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** 442 +|(% 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" %)((( 357 357 ((( 358 - By default, theDeviceID equal to thelast6bytes of IMEI.444 +Reserve/ Same as NBSN95 CFGMOD=1 359 359 ))) 360 360 361 361 ((( 362 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID448 +No function here. 363 363 ))) 450 +)))|(% style="width:77px" %)((( 451 +((( 452 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 453 +))) 364 364 365 365 ((( 366 - **Example:**456 +By SHT31 367 367 ))) 458 +)))|(% style="width:80px" %)((( 459 +((( 460 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 461 +))) 368 368 369 369 ((( 370 - AT+DEUI=A84041F15612464 +By SHT31 371 371 ))) 466 +))) 372 372 373 373 ((( 374 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 469 +((( 470 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 375 375 ))) 472 +))) 376 376 377 377 475 +[[image:1657354294009-643.png]] 378 378 379 -=== 2.4.2 Version Info === 380 380 478 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 479 + 480 +* Device ID: 0x724031607457 = 724031607457 481 +* Version: 0x006e=110=1.1.0 482 + 483 +* BAT: 0x0ccd = 3277 mV = 3.277V 484 +* Signal: 0x1b = 27 485 +* Model: 0x01 = 1 486 +* 0x00dc000ccc= reserve, ignore in N95S31B 487 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 488 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 489 + 381 381 ((( 382 - Specifythe software version: 0x64=100, means firmware version 1.00.491 + 383 383 ))) 384 384 385 385 ((( 386 - Forexample: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.495 + 387 387 ))) 388 388 389 389 499 +=== 2.3.2 Device ID === 390 390 391 -=== 2.4.3 Battery Info === 501 +((( 502 +By default, the Device ID equal to the last 6 bytes of IMEI. 503 +))) 392 392 393 393 ((( 394 - CheckthebatteryvoltageforLSE01.506 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 395 395 ))) 396 396 397 397 ((( 398 -Ex 1: 0x0B45 = 2885mV510 +**Example:** 399 399 ))) 400 400 401 401 ((( 402 -E x2:0x0B49 =2889mV514 +AT+DEUI=A84041F15612 403 403 ))) 404 404 517 +((( 518 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 519 +))) 405 405 406 406 407 -=== 2.4.4 Signal Strength === 408 408 409 -((( 410 -NB-IoT Network signal Strength. 411 -))) 523 +=== 2.3.3 Version Info === 412 412 413 413 ((( 414 - **Ex1:0x1d=29**526 +These bytes include the hardware and software version. 415 415 ))) 416 416 417 417 ((( 418 - (%style="color:blue"%)**0**(%%)-113dBmorless530 +Higher byte: Specify hardware version: always 0x00 for N95S31B 419 419 ))) 420 420 421 421 ((( 422 - (%style="color:blue"%)**1**(%%)-111dBm534 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 423 423 ))) 424 424 425 425 ((( 426 - (%style="color:blue" %)**2...30**(%%) -109dBm... -53dBm538 + 427 427 ))) 428 428 429 429 ((( 430 - (%style="color:blue"%)**31**(%%)-51dBmorgreater542 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 431 431 ))) 432 432 433 433 ((( 434 - (%style="color:blue" %)**99** (%%) Not known or not detectable546 + 435 435 ))) 436 436 437 437 550 +=== 2.3.4 Battery Info === 438 438 439 -=== 2.4.5 Distance === 440 - 441 -Get the distance. Flat object range 280mm - 7500mm. 442 - 443 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 444 - 445 445 ((( 446 -((( 447 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 553 +Ex1: 0x0B45 = 2885mV 448 448 ))) 449 -))) 450 450 451 451 ((( 452 - 557 +Ex2: 0x0B49 = 2889mV 453 453 ))) 454 454 455 -((( 456 - 457 -))) 458 458 459 -=== 2.4.6 Digital Interrupt === 460 460 562 +=== 2.3.5 Signal Strength === 563 + 461 461 ((( 462 - DigitalInterrupt refers topin (% style="color:blue" %)**GPIO_EXTI**(%%),and there are differenttrigger methods. When thereisa trigger, the NDDS75 will sendapacketto the server.565 +NB-IoT Network signal Strength. 463 463 ))) 464 464 465 465 ((( 466 - Thecommandis:569 +**Ex1: 0x1d = 29** 467 467 ))) 468 468 469 469 ((( 470 -(% style="color:blue" %)** AT+INTMOD=3**(%%)~/~/(moreinfoaboutINMODpleaserefer[[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**573 +(% style="color:blue" %)**0**(%%) -113dBm or less 471 471 ))) 472 472 473 - 474 474 ((( 475 - Thelower four bitsofthis data field shows if this packet is generatedby interruptornot.Clickhereforthehardwareandsoftware set up.577 +(% style="color:blue" %)**1**(%%) -111dBm 476 476 ))) 477 477 478 - 479 479 ((( 480 - Example:581 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 481 481 ))) 482 482 483 483 ((( 484 - 0x(00):Normalplinkpacket.585 +(% style="color:blue" %)**31** (%%) -51dBm or greater 485 485 ))) 486 486 487 487 ((( 488 - 0x(01):InterruptUplinkPacket.589 +(% style="color:blue" %)**99** (%%) Not known or not detectable 489 489 ))) 490 490 491 491 492 492 493 -=== 2. 4.7+5VOutput===594 +=== 2.3.6 Temperature & Humidity === 494 494 495 -((( 496 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 497 -))) 596 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 498 498 598 +[[image:image-20220709161741-3.png]] 499 499 500 -((( 501 -The 5V output time can be controlled by AT Command. 502 -))) 503 503 504 -((( 505 -(% style="color:blue" %)**AT+5VT=1000** 506 -))) 601 +Convert the read byte to decimal and divide it by ten. 507 507 508 -((( 509 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 510 -))) 511 511 604 +**Example:** 512 512 606 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 513 513 514 - ==2.5Downlink Payload==608 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 515 515 610 + 611 + 612 +== 2.4 Downlink Payload == 613 + 516 516 By default, NDDS75 prints the downlink payload to console port. 517 517 518 518 [[image:image-20220709100028-1.png]] ... ... @@ -563,47 +563,16 @@ 563 563 564 564 565 565 566 -== 2. 6LED Indicator ==664 +== 2.5 Battery Analysis == 567 567 666 +=== 2.5.1 Battery Type === 568 568 569 -The NDDS75 has an internal LED which is to show the status of different state. 570 570 571 - 572 -* 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) 573 -* Then the LED will be on for 1 second means device is boot normally. 574 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 575 -* For each uplink probe, LED will be on for 500ms. 576 - 577 577 ((( 578 - 670 +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. 579 579 ))) 580 580 581 - 582 - 583 -== 2.7 Firmware Change Log == 584 - 585 - 586 -Download URL & Firmware Change log 587 - 588 588 ((( 589 -[[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/]] 590 -))) 591 - 592 - 593 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 594 - 595 - 596 - 597 -== 2.8 Battery Analysis == 598 - 599 -=== 2.8.1 Battery Type === 600 - 601 - 602 -((( 603 -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. 604 -))) 605 - 606 -((( 607 607 The battery is designed to last for several years depends on the actually use environment and update interval. 608 608 ))) 609 609 ... ... @@ -621,56 +621,35 @@ 621 621 622 622 623 623 624 -=== 2. 8.2 Power consumption Analyze ===691 +=== 2.5.2 Power consumption Analyze === 625 625 626 626 ((( 627 - Draginobatterypoweredproductareall runsinLow Powermode.Wehave an update battery calculatorwhichbaseonthe measurement oftherealdevice. User can usethis calculatortocheck the batterylifeandcalculatethe batterylifeifwant tousedifferenttransmit interval.694 +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. 628 628 ))) 629 629 630 - 631 631 ((( 632 - Instructionto use as below:698 + 633 633 ))) 634 634 635 -((( 636 -(% 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/]] 637 -))) 638 638 702 +=== 2.5.3 Battery Note === 639 639 640 640 ((( 641 - (%style="color:blue"%)**Step2:**(%%)Open it andchoose705 +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. 642 642 ))) 643 643 644 -* ((( 645 -Product Model 646 -))) 647 -* ((( 648 -Uplink Interval 649 -))) 650 -* ((( 651 -Working Mode 652 -))) 653 653 654 -((( 655 -And the Life expectation in difference case will be shown on the right. 656 -))) 657 657 658 - [[image:image-20220709110451-3.png]]710 +=== 2.5.4 Replace the battery === 659 659 660 660 661 - 662 -=== 2.8.3 Battery Note === 663 - 664 664 ((( 665 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.714 +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. 666 666 ))) 667 667 668 668 669 - 670 -=== 2.8.4 Replace the battery === 671 - 672 672 ((( 673 -The default battery pack of N DDS75 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).719 +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). 674 674 ))) 675 675 676 676 ... ... @@ -693,7 +693,7 @@ 693 693 694 694 == 4.1 Access AT Commands == 695 695 696 -See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]742 +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/]] 697 697 698 698 699 699 AT+<CMD>? : Help on <CMD> ... ... @@ -781,8 +781,12 @@ 781 781 ))) 782 782 783 783 ((( 784 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 830 + 831 + 832 +((( 833 +(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update. 785 785 ))) 835 +))) 786 786 787 787 788 788 ... ... @@ -813,7 +813,7 @@ 813 813 = 7. Order Info = 814 814 815 815 816 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**866 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 817 817 818 818 819 819 (% class="wikigeneratedid" %) ... ... @@ -828,7 +828,7 @@ 828 828 829 829 (% style="color:#037691" %)**Package Includes**: 830 830 831 -* NS E01DistanceDetectSensorNode x 1881 +* N95S31B NB-IoT Temperature and Humidity Sensor 832 832 * External antenna x 1 833 833 ))) 834 834 ... ... @@ -837,11 +837,10 @@ 837 837 838 838 (% style="color:#037691" %)**Dimension and weight**: 839 839 840 - 841 841 * Device Size: 13.0 x 5 x 4.5 cm 842 842 * Device Weight: 150g 843 -* Package Size / pcs : 1 5x12x 5.5cm844 -* Weight / pcs : 220g892 +* Package Size / pcs : 14.0 x 8x 5 cm 893 +* Weight / pcs : 180g 845 845 ))) 846 846 847 847 (((
- 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