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, 15 added, 0 removed)
- 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
Details
- Page properties
-
- Content
-
... ... @@ -41,19 +41,19 @@ 41 41 42 42 == 1.2 Features == 43 43 44 + 44 44 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 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 46 +* Monitor Temperature & Humidity via SHT31 50 50 * AT Commands to change parameters 51 51 * Uplink on periodically 52 52 * Downlink to change configure 53 53 * IP66 Waterproof Enclosure 51 +* Ultra-Low Power consumption 52 +* AT Commands to change parameters 54 54 * Micro SIM card slot for NB-IoT SIM 55 55 * 8500mAh Battery for long term use 56 56 56 + 57 57 == 1.3 Specification == 58 58 59 59 ... ... @@ -73,6 +73,7 @@ 73 73 74 74 (% style="color:#037691" %)**Battery:** 75 75 76 + 76 76 * Li/SOCI2 un-chargeable battery 77 77 * Capacity: 8500mAh 78 78 * Self Discharge: <1% / Year @ 25°C ... ... @@ -79,11 +79,7 @@ 79 79 * Max continuously current: 130mA 80 80 * Max boost current: 2A, 1 second 81 81 82 -(% style="color:#037691" %)**Power Consumption** 83 83 84 -* STOP Mode: 10uA @ 3.3v 85 -* Max transmit power: 350mA@3.3v 86 - 87 87 == 1.4 Applications == 88 88 89 89 * Smart Buildings & Home Automation ... ... @@ -99,22 +99,52 @@ 99 99 100 100 == 1.5 Pin Definitions == 101 101 99 +N95S31B use the mother board from NBSN95 which as below. 102 102 103 -[[image: 1657328609906-564.png]]101 +[[image:image-20220709144723-1.png]] 104 104 105 105 104 +=== 1.5.1 Jumper JP2 === 106 106 107 - = 2. UseNDDS75 tocommunicate withIoTServer =106 +Power on Device when put this jumper. 108 108 108 + 109 + 110 +=== 1.5.2 BOOT MODE / SW1 === 111 + 112 +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. 113 + 114 +2) Flash: work mode, device starts to work and send out console output for further debug 115 + 116 + 117 + 118 +=== 1.5.3 Reset Button === 119 + 120 +Press to reboot the device. 121 + 122 + 123 + 124 +=== 1.5.4 LED === 125 + 126 +It will flash: 127 + 128 +1. When boot the device in flash mode 129 +1. Send an uplink packet 130 + 131 + 132 + 133 += 2. Use N95S31B to communicate with IoT Server = 134 + 109 109 == 2.1 How it works == 110 110 137 + 111 111 ((( 112 -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.139 +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. 113 113 ))) 114 114 115 115 116 116 ((( 117 -The diagram below shows the working flow in default firmware of N DDS75:144 +The diagram below shows the working flow in default firmware of N95S31B: 118 118 ))) 119 119 120 120 ((( ... ... @@ -121,7 +121,7 @@ 121 121 122 122 ))) 123 123 124 -[[image:1657328 659945-416.png]]151 +[[image:1657350248151-650.png]] 125 125 126 126 ((( 127 127 ... ... @@ -128,30 +128,45 @@ 128 128 ))) 129 129 130 130 131 -== 2.2 Configure the N DDS75 ==158 +== 2.2 Configure the N95S31B == 132 132 133 133 161 +=== 2.2.1 Power On N95S31B === 162 + 163 + 164 +[[image:image-20220709150546-2.png]] 165 + 166 + 134 134 === 2.2.1 Test Requirement === 135 135 136 -((( 137 -To use NDDS75 in your city, make sure meet below requirements: 138 -))) 139 139 170 +To use N95S31B in your city, make sure meet below requirements: 171 + 140 140 * Your local operator has already distributed a NB-IoT Network there. 141 -* The local NB-IoT network used the band that NS E01 supports.173 +* The local NB-IoT network used the band that N95S31B supports. 142 142 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 143 143 176 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 177 + 178 +N95S31B supports different communication protocol such as : 179 + 144 144 ((( 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 146 -))) 181 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 147 147 186 +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. 148 148 149 -[[image:1657328756309-230.png]] 188 + 189 +))) 150 150 191 +[[image:1657350625843-586.png]] 151 151 152 152 153 -=== 2.2.2 Insert SIM card === 154 154 195 +=== 2.2.3 Insert SIM card === 196 + 155 155 ((( 156 156 Insert the NB-IoT Card get from your provider. 157 157 ))) ... ... @@ -161,19 +161,19 @@ 161 161 ))) 162 162 163 163 164 -[[image:165732 8884227-504.png]]206 +[[image:1657351240556-536.png]] 165 165 166 166 167 167 168 -=== 2.2. 3DDS75 to configure it ===210 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 169 169 170 170 ((( 171 171 ((( 172 -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.214 +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. 173 173 ))) 174 174 ))) 175 175 176 -[[image: image-20220709092052-2.png]]218 +[[image:1657351312545-300.png]] 177 177 178 178 **Connection:** 179 179 ... ... @@ -193,18 +193,18 @@ 193 193 * Flow Control: (% style="color:green" %)**None** 194 194 195 195 ((( 196 -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.238 +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. 197 197 ))) 198 198 199 199 [[image:1657329814315-101.png]] 200 200 201 201 ((( 202 -(% 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/]]244 +(% 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/]] 203 203 ))) 204 204 205 205 206 206 207 -=== 2.2. 4249 +=== 2.2.5 Use CoAP protocol to uplink data === 208 208 209 209 (% 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/]] 210 210 ... ... @@ -224,10 +224,12 @@ 224 224 ))) 225 225 226 226 ((( 269 + 270 + 227 227 For parameter description, please refer to AT command set 228 228 ))) 229 229 230 -[[image:16573 30452568-615.png]]274 +[[image:1657352146020-183.png]] 231 231 232 232 233 233 ((( ... ... @@ -234,11 +234,11 @@ 234 234 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. 235 235 ))) 236 236 237 -[[image:16573 30472797-498.png]]281 +[[image:1657352185396-303.png]] 238 238 239 239 240 240 241 -=== 2.2. 5285 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 242 242 243 243 244 244 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -245,15 +245,16 @@ 245 245 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 246 246 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 247 247 248 -[[image:16573 30501006-241.png]]292 +[[image:1657352391268-297.png]] 249 249 250 250 251 -[[image:16573 30533775-472.png]]295 +[[image:1657352403317-397.png]] 252 252 253 253 254 254 255 -=== 2.2. 6299 +=== 2.2.7 Use MQTT protocol to uplink data === 256 256 301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 257 257 258 258 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 259 259 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -260,35 +260,40 @@ 260 260 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 261 261 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 262 262 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 263 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT264 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT308 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 309 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 265 265 266 -[[image:165724 9978444-674.png]]311 +[[image:1657352634421-276.png]] 267 267 268 268 269 -[[image:16573 30723006-866.png]]314 +[[image:1657352645687-385.png]] 270 270 316 +((( 317 +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. 318 +))) 271 271 320 + 272 272 ((( 273 -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.322 +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. 274 274 ))) 275 275 276 276 277 277 278 -=== 2.2. 7327 +=== 2.2.8 Use TCP protocol to uplink data === 279 279 329 +This feature is supported since firmware version v110 280 280 281 281 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 282 282 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 283 283 284 -[[image: image-20220709093918-1.png]]334 +[[image:1657352898400-901.png]] 285 285 286 286 287 -[[image: image-20220709093918-2.png]]337 +[[image:1657352914475-252.png]] 288 288 289 289 290 290 291 -=== 2.2. 8341 +=== 2.2.9 Change Update Interval === 292 292 293 293 User can use below command to change the (% style="color:green" %)**uplink interval**. 294 294 ... ... @@ -295,32 +295,69 @@ 295 295 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 296 296 297 297 ((( 298 - (%style="color:red" %)**NOTE:**348 + 299 299 ))) 300 300 301 -((( 302 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 303 -))) 304 304 305 305 306 - 307 307 == 2.3 Uplink Payload == 308 308 309 -In this mode, uplink payload includes in total 14 bytes 310 310 356 +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. 311 311 358 + 359 +For example: 360 + 361 + (% 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. 362 + 363 + 364 +The uplink payloads are composed in ASCII String. For example: 365 + 366 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 367 + 368 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 369 + 370 + 371 +(% style="color:red" %)**NOTE:** 372 + 373 +(% style="color:red" %) 374 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 +1. By default, the device will send an uplink message every 1 hour. 376 + 377 + 378 + 379 + 380 +=== 2.3.1 Payload Analyze === 381 + 382 +N95S31B uplink payload includes in total 21 bytes 383 + 384 + 312 312 (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 313 313 |=(% style="width: 60px;" %)((( 314 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"]] 388 +)))|=(% 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** 389 +|(% 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" %)((( 390 +Reserve/ Same as NBSN95 CFGMOD=1 317 317 392 +No function here. 393 +)))|(% style="width:77px" %)((( 394 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 395 + 396 +By SHT31 397 +)))|(% style="width:80px" %)((( 398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 399 + 400 +By SHT31 401 +))) 402 + 318 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. 404 +((( 405 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 320 320 ))) 407 +))) 321 321 322 322 323 -[[image:16573 31036973-987.png]]410 +[[image:1657354294009-643.png]] 324 324 325 325 ((( 326 326 The payload is ASCII string, representative same HEX:
- 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