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, 12 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -59,8 +59,6 @@ 59 59 * Micro SIM card slot for NB-IoT SIM 60 60 * 8500mAh Battery for long term use 61 61 62 - 63 - 64 64 == 1.3 Specification == 65 65 66 66 ... ... @@ -69,7 +69,6 @@ 69 69 * Supply Voltage: 2.1v ~~ 3.6v 70 70 * Operating Temperature: -40 ~~ 85°C 71 71 72 - 73 73 (% style="color:#037691" %)**NB-IoT Spec:** 74 74 75 75 * - B1 @H-FDD: 2100MHz ... ... @@ -79,7 +79,6 @@ 79 79 * - B20 @H-FDD: 800MHz 80 80 * - B28 @H-FDD: 700MHz 81 81 82 - 83 83 (% style="color:#037691" %)**Probe Specification:** 84 84 85 85 Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. ... ... @@ -126,6 +126,7 @@ 126 126 127 127 == 2.2 Configure the NSE01 == 128 128 125 + 129 129 === 2.2.1 Test Requirement === 130 130 131 131 ... ... @@ -135,11 +135,12 @@ 135 135 * The local NB-IoT network used the band that NSE01 supports. 136 136 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 137 137 138 - 135 +((( 139 139 Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSE01 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 137 +))) 140 140 141 141 142 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.gif]]140 +[[image:1657249419225-449.png]] 143 143 144 144 145 145 ... ... @@ -147,23 +147,24 @@ 147 147 148 148 Insert the NB-IoT Card get from your provider. 149 149 150 - 151 151 User need to take out the NB-IoT module and insert the SIM card like below: 152 152 153 153 154 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]151 +[[image:1657249468462-536.png]] 155 155 156 156 154 + 157 157 === 2.2.3 Connect USB – TTL to NSE01 to configure it === 158 158 157 +((( 158 +((( 159 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below. 160 +))) 161 +))) 159 159 160 -User need to configure NSE01 via serial port to set the **(% style="color:blue" %)Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below. 161 161 164 +**Connection:** 162 162 163 - 164 - 165 -Connection: 166 - 167 167 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 168 168 169 169 (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD ... ... @@ -171,172 +171,174 @@ 171 171 (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 172 172 173 173 174 - 175 175 In the PC, use below serial tool settings: 176 176 177 -* Baud: **(% style="background-color:green" %)9600**(%%)178 -* Data bits:** (% style=" background-color:green" %)8**(%%)179 -* Stop bits: **(% style="background-color:green" %)1**(%%)180 -* Parity: **(% style="background-color:green" %)None**(%%)181 -* Flow Control: **(% style="background-color:green" %)None**175 +* Baud: (% style="color:green" %)**9600** 176 +* Data bits:** (% style="color:green" %)8(%%)** 177 +* Stop bits: (% style="color:green" %)**1** 178 +* Parity: (% style="color:green" %)**None** 179 +* Flow Control: (% style="color:green" %)**None** 182 182 181 +((( 182 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 183 +))) 183 183 184 - Make sure the switch is in FLASH position, then power on device by connectingthejumper on NSE01. NSE01 will output systeminfo once power onas below, we can enter the **(% style="background-color:green" %)password: 12345678**(%%) to access AT Command input.185 +[[image:image-20220708110657-3.png]] 185 185 186 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]]187 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 187 187 188 -Note: the valid AT Commands can be found at: 189 189 190 -[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 191 191 191 +=== 2.2.4 Use CoAP protocol to uplink data === 192 192 193 +(% 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/]] 193 193 194 -=== 2.2.4 Use CoAP protocol to uplink data === 195 195 196 +**Use below commands:** 196 196 197 -(% style="background-color:red" %)Note: if you don’t have CoAP server, you can refer this link to set up one: 198 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 199 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 200 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 198 198 199 - [[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]202 +For parameter description, please refer to AT command set 200 200 204 +[[image:1657249793983-486.png]] 201 201 202 -Use below commands: 203 203 204 -* **(% style="color:blue" %)AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 205 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 206 -* **(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 207 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server. 207 207 209 +[[image:1657249831934-534.png]] 208 208 209 -For parameter description, please refer to AT command set 210 210 211 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]] 212 212 213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 213 213 214 - Afterconfigurehe serveraddressand **(%style="color:green" %)resettheevice**(%%)(via AT+ATZ ), NSE01will start to uplink sensorvaluestoCoAP server.215 +This feature is supported since firmware version v1.0.1 215 215 216 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]] 217 217 218 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 220 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 218 218 219 - ===2.2.5 Use UDPprotocol to uplink data(Default protocol) ===222 +[[image:1657249864775-321.png]] 220 220 221 221 222 -This feature is supported since firmware version v1.0.1 223 223 226 +[[image:1657249930215-289.png]] 224 224 225 -* **(% style="color:blue" %)AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 226 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 227 -* **(% style="color:blue" %)AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 228 228 229 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]] 230 230 230 +=== 2.2.6 Use MQTT protocol to uplink data === 231 231 232 +This feature is supported since firmware version v110 232 232 233 233 235 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 236 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 237 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 238 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 239 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 240 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 241 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 234 234 235 -[[image: file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]243 +[[image:1657249978444-674.png]] 236 236 237 237 238 - ===2.2.6Use MQTTprotocol to uplink data ===246 +[[image:1657249990869-686.png]] 239 239 240 240 241 -This feature is supported since firmware version v110 242 242 250 +((( 251 +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. 252 +))) 243 243 244 -* **(% style="color:blue" %)AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 245 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 246 -* **(% style="color:blue" %)AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 247 -* **(% style="color:blue" %)AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 248 -* **(% style="color:blue" %)AT+PWD=PWD **(%%)~/~/Set the password of MQTT 249 -* **(% style="color:blue" %)AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 250 -* **(% style="color:blue" %)AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 251 251 252 252 253 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]256 +=== 2.2.7 Use TCP protocol to uplink data === 254 254 255 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]258 +This feature is supported since firmware version v110 256 256 257 257 258 -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. 261 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 262 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 259 259 264 +[[image:1657250217799-140.png]] 260 260 261 -=== 2.2.7 Use TCP protocol to uplink data === 262 262 267 +[[image:1657250255956-604.png]] 263 263 264 -This feature is supported since firmware version v110 265 265 270 +=== 2.2.8 Change Update Interval === 266 266 267 -* **(% style="color:blue" %)AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 268 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 272 +User can use below command to change the (% style="color:green" %)**uplink interval**. 269 269 270 - [[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]274 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 271 271 276 +((( 277 +(% style="color:red" %)**NOTE:** 278 +))) 272 272 280 +((( 281 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 282 +))) 273 273 274 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]] 275 275 276 276 277 -== =2.2.8ChangeUpdate Interval ===286 +== 2.3 Uplink Payload == 278 278 279 - User canusebelowcommandto change the **(% style="color:green"%)uplinkinterval**.288 +In this mode, uplink payload includes in total 18 bytes 280 280 281 -**~ (% style="color:blue" %)AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 290 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 291 +|=(% style="width: 50px;" %)((( 292 +**Size(bytes)** 293 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1** 294 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]] 282 282 296 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 283 283 284 -**(% style="color:red" %)NOTE:** 285 285 286 - (% style="color:red" %)1. By default, thedevice will send an uplinkmessageevery1hour.299 +[[image:image-20220708111918-4.png]] 287 287 288 288 302 +The payload is ASCII string, representative same HEX: 289 289 304 +0x72403155615900640c7817075e0a8c02f900 where: 290 290 306 +* Device ID: 0x 724031556159 = 724031556159 307 +* Version: 0x0064=100=1.0.0 291 291 309 +* BAT: 0x0c78 = 3192 mV = 3.192V 310 +* Singal: 0x17 = 23 311 +* Soil Moisture: 0x075e= 1886 = 18.86 % 312 +* Soil Temperature:0x0a8c =2700=27 °C 313 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 314 +* Interrupt: 0x00 = 0 292 292 293 293 294 -== 2.3 Uplink Payload == 295 295 296 296 297 -== =2.3.1MOD~=0(DefaultMode)===319 +== 2.4 Payload Explanation and Sensor Interface == 298 298 299 - LSE01will uplink payloadvia LoRaWAN with belowpayload format:321 +2.4.1 Device ID 300 300 301 -((( 302 -Uplink payload includes in total 11 bytes. 303 -))) 323 +By default, the Device ID equal to the last 6 bytes of IMEI. 304 304 305 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 306 -|((( 307 -**Size** 325 +User can use **(% style="color:blue" %)AT+DEUI**(%%) to set Device ID 308 308 309 -**(bytes)** 310 -)))|**2**|**2**|**2**|**2**|**2**|**1** 311 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|((( 312 -Temperature 327 +**Example:** 313 313 314 -(Reserve, Ignore now) 315 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|((( 316 -MOD & Digital Interrupt 329 +AT+DEUI=A84041F15612 317 317 318 -(Optional) 319 -))) 331 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 320 320 321 -=== 2.3.2 MOD~=1(Original value) === 322 322 323 - Thismodecan get the original AD value of moisture and original conductivity(with temperature drift compensation).334 +2.4.2 Version Info 324 324 325 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 326 -|((( 327 -**Size** 336 +Specify the software version: 0x64=100, means firmware version 1.00. 328 328 329 -**(bytes)** 330 -)))|**2**|**2**|**2**|**2**|**2**|**1** 331 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|((( 332 -Temperature 338 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 333 333 334 -(Reserve, Ignore now) 335 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|((( 336 -MOD & Digital Interrupt 337 337 338 -(Optional) 339 -))) 340 340 341 341 === 2.3.3 Battery Info === 342 342
- 1657249419225-449.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +81.0 KB - Content
- 1657249468462-536.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657249793983-486.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +85.8 KB - Content
- 1657249831934-534.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.5 KB - Content
- 1657249864775-321.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +87.0 KB - Content
- 1657249930215-289.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +77.3 KB - Content
- 1657249978444-674.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +139.5 KB - Content
- 1657249990869-686.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +96.9 KB - Content
- 1657250217799-140.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.7 KB - Content
- 1657250255956-604.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +99.0 KB - Content
- image-20220708110657-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +251.7 KB - Content
- image-20220708111918-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +38.8 KB - Content