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, 11 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657328 659945-416.png]]154 +[[image:1657350248151-650.png]] 155 155 156 156 ((( 157 157 ... ... @@ -158,30 +158,46 @@ 158 158 ))) 159 159 160 160 161 -== 2.2 Configure the N DDS75 ==161 +== 2.2 Configure the N95S31B == 162 162 163 163 164 +=== 2.2.1 Power On N95S31B === 165 + 166 + 167 +[[image:image-20220709150546-2.png]] 168 + 169 + 164 164 === 2.2.1 Test Requirement === 165 165 166 -((( 167 -To use NDDS75 in your city, make sure meet below requirements: 168 -))) 169 169 173 +To use N95S31B in your city, make sure meet below requirements: 174 + 170 170 * Your local operator has already distributed a NB-IoT Network there. 171 -* The local NB-IoT network used the band that NS E01 supports.176 +* The local NB-IoT network used the band that N95S31B supports. 172 172 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 173 173 179 + 180 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 + 182 +N95S31B supports different communication protocol such as : 183 + 174 174 ((( 175 -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 176 -))) 185 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 186 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 187 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 188 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 177 177 190 +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. 178 178 179 -[[image:1657328756309-230.png]] 192 + 193 +))) 180 180 195 +[[image:1657350625843-586.png]] 181 181 182 182 183 -=== 2.2.2 Insert SIM card === 184 184 199 +=== 2.2.3 Insert SIM card === 200 + 185 185 ((( 186 186 Insert the NB-IoT Card get from your provider. 187 187 ))) ... ... @@ -191,19 +191,19 @@ 191 191 ))) 192 192 193 193 194 -[[image:165732 8884227-504.png]]210 +[[image:1657351240556-536.png]] 195 195 196 196 197 197 198 -=== 2.2. 3DDS75 to configure it ===214 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 199 199 200 200 ((( 201 201 ((( 202 -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.218 +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. 203 203 ))) 204 204 ))) 205 205 206 -[[image: image-20220709092052-2.png]]222 +[[image:1657351312545-300.png]] 207 207 208 208 **Connection:** 209 209 ... ... @@ -223,18 +223,18 @@ 223 223 * Flow Control: (% style="color:green" %)**None** 224 224 225 225 ((( 226 -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.242 +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. 227 227 ))) 228 228 229 229 [[image:1657329814315-101.png]] 230 230 231 231 ((( 232 -(% 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/]]248 +(% 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/]] 233 233 ))) 234 234 235 235 236 236 237 -=== 2.2. 4253 +=== 2.2.5 Use CoAP protocol to uplink data === 238 238 239 239 (% 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/]] 240 240 ... ... @@ -254,10 +254,12 @@ 254 254 ))) 255 255 256 256 ((( 273 + 274 + 257 257 For parameter description, please refer to AT command set 258 258 ))) 259 259 260 -[[image:16573 30452568-615.png]]278 +[[image:1657352146020-183.png]] 261 261 262 262 263 263 ((( ... ... @@ -264,11 +264,11 @@ 264 264 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. 265 265 ))) 266 266 267 -[[image:16573 30472797-498.png]]285 +[[image:1657352185396-303.png]] 268 268 269 269 270 270 271 -=== 2.2. 5289 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 272 272 273 273 274 274 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -275,15 +275,16 @@ 275 275 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 276 276 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 277 277 278 -[[image:16573 30501006-241.png]]296 +[[image:1657352391268-297.png]] 279 279 280 280 281 -[[image:16573 30533775-472.png]]299 +[[image:1657352403317-397.png]] 282 282 283 283 284 284 285 -=== 2.2. 6303 +=== 2.2.7 Use MQTT protocol to uplink data === 286 286 305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption. 287 287 288 288 * (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 289 289 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port ... ... @@ -290,17 +290,21 @@ 290 290 * (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 291 291 * (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 292 292 * (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 293 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB294 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 295 295 296 -[[image:165724 9978444-674.png]]315 +[[image:1657352634421-276.png]] 297 297 298 298 299 -[[image:16573 30723006-866.png]]318 +[[image:1657352645687-385.png]] 300 300 320 +((( 321 +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. 322 +))) 301 301 324 + 302 302 ((( 303 -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.326 +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. 304 304 ))) 305 305 306 306
- 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
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content