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 (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 17 added, 0 removed)
- 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
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Content
-
... ... @@ -1,56 +1,41 @@ 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 -**Table of Contents:** 9 9 10 -{{toc/}} 11 11 10 +**Table of Contents:** 12 12 13 13 14 14 15 15 16 16 16 + 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==19 +== 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 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. 27 -))) 24 +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*. 28 28 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. 31 -))) 26 +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. 32 32 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. 35 -))) 28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 36 37 -((( 38 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 39 -))) 30 +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). 40 40 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) 43 -))) 44 44 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. 47 -))) 48 -))) 33 +~* make sure you have NB-IoT coverage locally. 49 49 50 50 51 51 ))) 52 52 53 -[[image:165732 7959271-447.png]]38 +[[image:1657348284168-431.png]] 54 54 55 55 56 56 ... ... @@ -57,20 +57,19 @@ 57 57 == 1.2 Features == 58 58 59 59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 60 -* Ultra low power consumption 61 -* Distance Detection by Ultrasonic technology 62 -* Flat object range 280mm - 7500mm 63 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 64 -* Cable Length: 25cm 45 +* Monitor Temperature & Humidity via SHT31 65 65 * AT Commands to change parameters 66 66 * Uplink on periodically 67 67 * Downlink to change configure 68 68 * IP66 Waterproof Enclosure 50 +* Ultra-Low Power consumption 51 +* AT Commands to change parameters 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 72 72 73 73 57 + 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -90,6 +90,7 @@ 90 90 91 91 (% style="color:#037691" %)**Battery:** 92 92 77 + 93 93 * Li/SOCI2 un-chargeable battery 94 94 * Capacity: 8500mAh 95 95 * Self Discharge: <1% / Year @ 25°C ... ... @@ -96,13 +96,9 @@ 96 96 * Max continuously current: 130mA 97 97 * Max boost current: 2A, 1 second 98 98 99 -(% style="color:#037691" %)**Power Consumption** 100 100 101 -* STOP Mode: 10uA @ 3.3v 102 -* Max transmit power: 350mA@3.3v 103 103 104 104 105 - 106 106 == 1.4 Applications == 107 107 108 108 * Smart Buildings & Home Automation ... ... @@ -118,22 +118,51 @@ 118 118 119 119 == 1.5 Pin Definitions == 120 120 102 +N95S31B use the mother board from NBSN95 which as below. 121 121 122 -[[image: 1657328609906-564.png]]104 +[[image:image-20220709144723-1.png]] 123 123 124 124 107 +=== 1.5.1 Jumper JP2 === 125 125 126 - = 2. UseNDDS75 tocommunicate withIoTServer =109 +Power on Device when put this jumper. 127 127 111 + 112 + 113 +=== 1.5.2 BOOT MODE / SW1 === 114 + 115 +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. 116 + 117 +2) Flash: work mode, device starts to work and send out console output for further debug 118 + 119 + 120 + 121 +=== 1.5.3 Reset Button === 122 + 123 +Press to reboot the device. 124 + 125 + 126 + 127 +=== 1.5.4 LED === 128 + 129 +It will flash: 130 + 131 +1. When boot the device in flash mode 132 +1. Send an uplink packet 133 + 134 + 135 += 2. Use N95S31B to communicate with IoT Server = 136 + 128 128 == 2.1 How it works == 129 129 139 + 130 130 ((( 131 -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.141 +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. 132 132 ))) 133 133 134 134 135 135 ((( 136 -The diagram below shows the working flow in default firmware of N DDS75:146 +The diagram below shows the working flow in default firmware of N95S31B: 137 137 ))) 138 138 139 139 ((( ... ... @@ -140,7 +140,7 @@ 140 140 141 141 ))) 142 142 143 -[[image:1657328 659945-416.png]]153 +[[image:1657350248151-650.png]] 144 144 145 145 ((( 146 146 ... ... @@ -147,30 +147,45 @@ 147 147 ))) 148 148 149 149 150 -== 2.2 Configure the N DDS75 ==160 +== 2.2 Configure the N95S31B == 151 151 152 152 163 +=== 2.2.1 Power On N95S31B === 164 + 165 + 166 +[[image:image-20220709150546-2.png]] 167 + 168 + 153 153 === 2.2.1 Test Requirement === 154 154 155 -((( 156 -To use NDDS75 in your city, make sure meet below requirements: 157 -))) 158 158 172 +To use N95S31B in your city, make sure meet below requirements: 173 + 159 159 * Your local operator has already distributed a NB-IoT Network there. 160 -* The local NB-IoT network used the band that NS E01 supports.175 +* The local NB-IoT network used the band that N95S31B supports. 161 161 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 162 162 178 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 179 + 180 +N95S31B supports different communication protocol such as : 181 + 163 163 ((( 164 -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 165 -))) 183 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 184 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 185 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 186 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 166 166 188 +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. 167 167 168 -[[image:1657328756309-230.png]] 190 + 191 +))) 169 169 193 +[[image:1657350625843-586.png]] 170 170 171 171 172 -=== 2.2.2 Insert SIM card === 173 173 197 +=== 2.2.3 Insert SIM card === 198 + 174 174 ((( 175 175 Insert the NB-IoT Card get from your provider. 176 176 ))) ... ... @@ -180,19 +180,19 @@ 180 180 ))) 181 181 182 182 183 -[[image:165732 8884227-504.png]]208 +[[image:1657351240556-536.png]] 184 184 185 185 186 186 187 -=== 2.2. 3DDS75 to configure it ===212 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 188 188 189 189 ((( 190 190 ((( 191 -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.216 +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. 192 192 ))) 193 193 ))) 194 194 195 -[[image: image-20220709092052-2.png]]220 +[[image:1657351312545-300.png]] 196 196 197 197 **Connection:** 198 198 ... ... @@ -212,18 +212,18 @@ 212 212 * Flow Control: (% style="color:green" %)**None** 213 213 214 214 ((( 215 -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.240 +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. 216 216 ))) 217 217 218 218 [[image:1657329814315-101.png]] 219 219 220 220 ((( 221 -(% 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/]]246 +(% 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/]] 222 222 ))) 223 223 224 224 225 225 226 -=== 2.2. 4251 +=== 2.2.5 Use CoAP protocol to uplink data === 227 227 228 228 (% 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/]] 229 229 ... ... @@ -243,10 +243,12 @@ 243 243 ))) 244 244 245 245 ((( 271 + 272 + 246 246 For parameter description, please refer to AT command set 247 247 ))) 248 248 249 -[[image:16573 30452568-615.png]]276 +[[image:1657352146020-183.png]] 250 250 251 251 252 252 ((( ... ... @@ -253,11 +253,11 @@ 253 253 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. 254 254 ))) 255 255 256 -[[image:16573 30472797-498.png]]283 +[[image:1657352185396-303.png]] 257 257 258 258 259 259 260 -=== 2.2. 5287 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 261 261 262 262 263 263 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -264,15 +264,16 @@ 264 264 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 265 265 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 266 266 267 -[[image:16573 30501006-241.png]]294 +[[image:1657352391268-297.png]] 268 268 269 269 270 -[[image:16573 30533775-472.png]]297 +[[image:1657352403317-397.png]] 271 271 272 272 273 273 274 -=== 2.2. 6301 +=== 2.2.7 Use MQTT protocol to uplink data === 275 275 303 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 276 276 277 277 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 278 278 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -279,35 +279,40 @@ 279 279 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 280 280 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 281 281 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 282 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT283 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT310 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 311 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 284 284 285 -[[image:165724 9978444-674.png]]313 +[[image:1657352634421-276.png]] 286 286 287 287 288 -[[image:16573 30723006-866.png]]316 +[[image:1657352645687-385.png]] 289 289 318 +((( 319 +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. 320 +))) 290 290 322 + 291 291 ((( 292 -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.324 +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. 293 293 ))) 294 294 295 295 296 296 297 -=== 2.2. 7329 +=== 2.2.8 Use TCP protocol to uplink data === 298 298 331 +This feature is supported since firmware version v110 299 299 300 300 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 301 301 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 302 302 303 -[[image: image-20220709093918-1.png]]336 +[[image:1657352898400-901.png]] 304 304 305 305 306 -[[image: image-20220709093918-2.png]]339 +[[image:1657352914475-252.png]] 307 307 308 308 309 309 310 -=== 2.2. 8343 +=== 2.2.9 Change Update Interval === 311 311 312 312 User can use below command to change the (% style="color:green" %)**uplink interval**. 313 313 ... ... @@ -314,69 +314,92 @@ 314 314 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 315 315 316 316 ((( 317 - (%style="color:red" %)**NOTE:**350 + 318 318 ))) 319 319 320 -((( 321 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 322 -))) 323 323 324 324 325 - 326 326 == 2.3 Uplink Payload == 327 327 328 -In this mode, uplink payload includes in total 14 bytes 329 329 358 +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. 330 330 360 + 361 +For example: 362 + 363 + (% 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. 364 + 365 + 366 +The uplink payloads are composed in ASCII String. For example: 367 + 368 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 369 + 370 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 371 + 372 + 373 +(% style="color:red" %)**NOTE:** 374 + 375 +(% style="color:red" %) 376 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 377 +1. By default, the device will send an uplink message every 1 hour. 378 + 379 + 380 + 381 +=== 2.3.1 Payload Analyze === 382 + 383 +N95S31B uplink payload includes in total 21 bytes 384 + 385 + 331 331 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 332 332 |=(% style="width: 60px;" %)((( 333 333 **Size(bytes)** 334 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 335 -|(% 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"]] 389 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 390 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 391 +Reserve/ Same as NBSN95 CFGMOD=1 336 336 337 - (((338 - Ifwe usethe MQTT client to subscribe to this MQTT topic,we can see the following information when the NDDS751 uplinkdata.339 - )))393 +No function here. 394 +)))|(% style="width:77px" %)((( 395 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 340 340 397 +By SHT31 398 +)))|(% style="width:80px" %)((( 399 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 341 341 342 -[[image:1657331036973-987.png]] 343 - 344 -((( 345 -The payload is ASCII string, representative same HEX: 401 +By SHT31 346 346 ))) 347 347 348 348 ((( 349 -0x72403155615900640c6c19029200 where: 405 +((( 406 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 350 350 ))) 351 - 352 -* ((( 353 -Device ID: 0x724031556159 = 724031556159 354 354 ))) 355 -* ((( 356 -Version: 0x0064=100=1.0.0 357 -))) 358 358 359 -* ((( 360 -BAT: 0x0c6c = 3180 mV = 3.180V 361 -))) 362 -* ((( 363 -Signal: 0x19 = 25 364 -))) 365 -* ((( 366 -Distance: 0x0292= 658 mm 367 -))) 368 -* ((( 369 -Interrupt: 0x00 = 0 370 370 411 +[[image:1657354294009-643.png]] 371 371 372 372 414 +The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 415 + 416 +* Device ID: 0x724031607457 = 724031607457 417 +* Version: 0x006e=110=1.1.0 418 + 419 +* BAT: 0x0ccd = 3277 mV = 3.277V 420 +* Signal: 0x1b = 27 421 +* Model: 0x01 = 1 422 +* 0x00dc000ccc= reserve, ignore in N95S31B 423 +* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 424 +* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 425 + 426 +((( 373 373 374 374 ))) 375 375 376 -== 2.4 Payload Explanation and Sensor Interface == 430 +((( 431 + 432 +))) 377 377 378 378 379 -=== 2. 4.1435 +=== 2.3.2 Device ID === 380 380 381 381 ((( 382 382 By default, the Device ID equal to the last 6 bytes of IMEI. ... ... @@ -400,20 +400,25 @@ 400 400 401 401 402 402 403 -=== 2. 4.2Version Info ===459 +=== 2.3.3 Version Info === 404 404 405 -((( 406 -Specify the software version: 0x64=100, means firmware version 1.00. 407 -))) 408 408 462 +These bytes include the hardware and software version. 463 + 464 +Higher byte: Specify hardware version: always 0x00 for N95S31B 465 + 466 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 467 + 468 + 469 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 470 + 409 409 ((( 410 - Forexample: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.472 + 411 411 ))) 412 412 413 413 476 +=== 2.3.4 Battery Info === 414 414 415 -=== 2.4.3 Battery Info === 416 - 417 417 ((( 418 418 Ex1: 0x0B45 = 2885mV 419 419 ))) ... ... @@ -424,7 +424,7 @@ 424 424 425 425 426 426 427 -=== 2. 4.4Signal Strength ===488 +=== 2.3.5 Signal Strength === 428 428 429 429 ((( 430 430 NB-IoT Network signal Strength. ... ... @@ -456,83 +456,24 @@ 456 456 457 457 458 458 459 -=== 2. 4.5Distance ===520 +=== 2.3.6 Temperature & Humidity === 460 460 461 - Get the distance.Flatobject range280mm-7500mm.522 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 462 462 463 -((( 464 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 465 -))) 524 +[[image:image-20220709161741-3.png]] 466 466 467 -((( 468 -((( 469 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 470 -))) 471 -))) 472 472 473 -((( 474 - 475 -))) 527 +Convert the read byte to decimal and divide it by ten. 476 476 477 -((( 478 - 479 -))) 480 480 481 - === 2.4.6 DigitalInterrupt ===530 +**Example:** 482 482 483 -((( 484 -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. 485 -))) 532 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 486 486 487 -((( 488 -The command is: 489 -))) 534 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 490 490 491 -((( 492 -(% 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]])**.** 493 -))) 494 494 495 495 496 -((( 497 -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. 498 -))) 499 - 500 - 501 -((( 502 -Example: 503 -))) 504 - 505 -((( 506 -0x(00): Normal uplink packet. 507 -))) 508 - 509 -((( 510 -0x(01): Interrupt Uplink Packet. 511 -))) 512 - 513 - 514 - 515 -=== 2.4.7 +5V Output === 516 - 517 -((( 518 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 519 -))) 520 - 521 - 522 -((( 523 -The 5V output time can be controlled by AT Command. 524 -))) 525 - 526 -((( 527 -(% style="color:blue" %)**AT+5VT=1000** 528 -))) 529 - 530 -((( 531 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 532 -))) 533 - 534 - 535 - 536 536 == 2.5 Downlink Payload == 537 537 538 538 By default, NDDS75 prints the downlink payload to console port. ... ... @@ -585,41 +585,6 @@ 585 585 586 586 587 587 588 -== 2.6 LED Indicator == 589 - 590 - 591 -The NDDS75 has an internal LED which is to show the status of different state. 592 - 593 - 594 -* 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) 595 -* Then the LED will be on for 1 second means device is boot normally. 596 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 597 -* For each uplink probe, LED will be on for 500ms. 598 - 599 -((( 600 - 601 -))) 602 - 603 - 604 - 605 -== 2.7 Firmware Change Log == 606 - 607 - 608 -((( 609 -Download URL & Firmware Change log 610 -))) 611 - 612 -((( 613 -[[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/]] 614 -))) 615 - 616 - 617 -((( 618 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 619 -))) 620 - 621 - 622 - 623 623 == 2.8 Battery Analysis == 624 624 625 625 === 2.8.1 Battery Type ===
- 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
- 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