Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Change comment:
Uploaded new attachment "1657330472797-498.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 32 removed)
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- 1657332990863-496.png
- 1657333200519-600.png
- 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-20220709093918-1.png
- image-20220709093918-2.png
- image-20220709100028-1.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N 95S31BNB-IoTTemperature& HumiditySensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. David1 +XWiki.Xiaoling - Content
-
... ... @@ -1,56 +1,41 @@ 1 1 (% style="text-align:center" %) 2 -[[image: 1657348034241-728.png||height="470" width="470"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 - 9 - 10 10 **Table of Contents:** 11 11 12 -{{toc/}} 13 13 14 14 15 15 16 16 17 17 15 + 18 18 = 1. Introduction = 19 19 18 +== 1.1 What is NDDS75 Distance Detection Sensor == 20 20 21 -== 1.1 What is N95S31B NB-IoT Sensor Node == 22 - 23 23 ((( 24 24 25 25 26 26 ((( 27 -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*. 24 +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. 25 +\\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. 26 +\\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. 27 +\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 28 +\\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) 29 +\\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. 28 28 ))) 29 29 30 -((( 31 -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 -))) 33 - 34 -((( 35 -N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 -))) 37 - 38 -((( 39 -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 -))) 41 - 42 -((( 43 43 44 44 ))) 45 45 46 -((( 47 -~* make sure you have NB-IoT coverage locally. 48 -))) 35 +[[image:1654503236291-817.png]] 49 49 50 - 51 -))) 52 52 53 -[[image:16573 48284168-431.png]]38 +[[image:1657327959271-447.png]] 54 54 55 55 56 56 ... ... @@ -58,19 +58,20 @@ 58 58 59 59 60 60 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 61 -* Monitor Temperature & Humidity via SHT31 46 +* Ultra low power consumption 47 +* Distance Detection by Ultrasonic technology 48 +* Flat object range 280mm - 7500mm 49 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 50 +* Cable Length: 25cm 62 62 * AT Commands to change parameters 63 63 * Uplink on periodically 64 64 * Downlink to change configure 65 65 * IP66 Waterproof Enclosure 66 -* Ultra-Low Power consumption 67 -* AT Commands to change parameters 68 68 * Micro SIM card slot for NB-IoT SIM 69 69 * 8500mAh Battery for long term use 70 70 71 71 72 72 73 - 74 74 == 1.3 Specification == 75 75 76 76 ... ... @@ -79,8 +79,6 @@ 79 79 * Supply Voltage: 2.1v ~~ 3.6v 80 80 * Operating Temperature: -40 ~~ 85°C 81 81 82 - 83 - 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 86 * - B1 @H-FDD: 2100MHz ... ... @@ -91,7 +91,6 @@ 91 91 * - B28 @H-FDD: 700MHz 92 92 93 93 94 - 95 95 (% style="color:#037691" %)**Battery:** 96 96 97 97 * Li/SOCI2 un-chargeable battery ... ... @@ -101,11 +101,16 @@ 101 101 * Max boost current: 2A, 1 second 102 102 103 103 87 +(% style="color:#037691" %)**Power Consumption** 104 104 89 +* STOP Mode: 10uA @ 3.3v 90 +* Max transmit power: 350mA@3.3v 105 105 106 -== 1.4 Applications == 107 107 108 108 94 + 95 +== 1.4 Applications == 96 + 109 109 * Smart Buildings & Home Automation 110 110 * Logistics and Supply Chain Management 111 111 * Smart Metering ... ... @@ -118,67 +118,25 @@ 118 118 119 119 120 120 121 -== 1.5 Pin Definitions & Switch==109 +== 1.5 Pin Definitions == 122 122 123 123 124 - N95S31B use themother board from NBSN95which as below.112 +[[image:1657328609906-564.png]] 125 125 126 126 127 -[[image:image-20220709144723-1.png]] 128 128 129 129 117 += 2. Use NDDS75 to communicate with IoT Server = 130 130 131 -=== 1.5.1 Jumper JP2 === 132 - 133 - 134 -Power on Device when put this jumper. 135 - 136 - 137 - 138 -=== 1.5.2 BOOT MODE / SW1 === 139 - 140 - 141 -((( 142 -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. 143 -))) 144 - 145 -((( 146 -2) Flash: work mode, device starts to work and send out console output for further debug 147 -))) 148 - 149 - 150 - 151 -=== 1.5.3 Reset Button === 152 - 153 - 154 -Press to reboot the device. 155 - 156 - 157 - 158 -=== 1.5.4 LED === 159 - 160 - 161 -It will flash: 162 - 163 -1. When boot the device in flash mode 164 -1. Send an uplink packet 165 - 166 - 167 - 168 - 169 -= 2. Use N95S31B to communicate with IoT Server = 170 - 171 - 172 172 == 2.1 How it works == 173 173 174 - 175 175 ((( 176 -The N 95S31Bis equipped with a NB-IoT module, the pre-loaded firmware in N95S31Bwill 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.122 +The NDDS75 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. 177 177 ))) 178 178 179 179 180 180 ((( 181 -The diagram below shows the working flow in default firmware of N 95S31B:127 +The diagram below shows the working flow in default firmware of NDDS75: 182 182 ))) 183 183 184 184 ((( ... ... @@ -185,7 +185,7 @@ 185 185 186 186 ))) 187 187 188 -[[image:1657 520100595-569.png]]134 +[[image:1657328659945-416.png]] 189 189 190 190 ((( 191 191 ... ... @@ -192,69 +192,30 @@ 192 192 ))) 193 193 194 194 195 -== 2.2 Configure the N 95S31B==141 +== 2.2 Configure the NDDS75 == 196 196 197 197 198 -=== 2.2.1 Power On N95S31B === 199 - 200 - 201 -[[image:image-20220709150546-2.png]] 202 - 203 - 204 - 205 205 === 2.2.1 Test Requirement === 206 206 207 - 208 208 ((( 209 -To use N 95S31Bin your city, make sure meet below requirements:147 +To use NDDS75 in your city, make sure meet below requirements: 210 210 ))) 211 211 212 -* ((( 213 -Your local operator has already distributed a NB-IoT Network there. 214 -))) 215 -* ((( 216 -The local NB-IoT network used the band that N95S31B supports. 217 -))) 218 -* ((( 219 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 220 -))) 150 +* Your local operator has already distributed a NB-IoT Network there. 151 +* The local NB-IoT network used the band that NSE01 supports. 152 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 221 221 222 222 ((( 223 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 155 +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 224 224 ))) 225 225 226 -((( 227 -N95S31B supports different communication protocol such as : 228 -))) 229 229 230 -((( 231 -* ((( 232 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 233 -))) 234 -* ((( 235 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 236 -))) 237 -* ((( 238 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 239 -))) 240 -* ((( 241 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 242 -))) 159 +[[image:1657328756309-230.png]] 243 243 244 -((( 245 -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. 246 -))) 247 247 248 - 249 -))) 250 250 251 - [[image:1657350625843-586.png]]163 +=== 2.2.2 Insert SIM card === 252 252 253 - 254 - 255 -=== 2.2.3 Insert SIM card === 256 - 257 - 258 258 ((( 259 259 Insert the NB-IoT Card get from your provider. 260 260 ))) ... ... @@ -264,24 +264,20 @@ 264 264 ))) 265 265 266 266 267 -[[image:16573 51240556-536.png]]174 +[[image:1657328884227-504.png]] 268 268 269 269 270 270 271 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===178 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 272 272 273 - 274 274 ((( 275 275 ((( 276 -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. 277 - 278 - 182 +User need to configure NDDS75 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 to NDDS75 and use AT Commands to configure it, as below. 279 279 ))) 280 280 ))) 281 281 282 -[[image: 1657351312545-300.png]]186 +[[image:image-20220709092052-2.png]] 283 283 284 - 285 285 **Connection:** 286 286 287 287 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -300,286 +300,286 @@ 300 300 * Flow Control: (% style="color:green" %)**None** 301 301 302 302 ((( 303 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N 95S31B.95S31Bwill output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.206 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 304 304 ))) 305 305 306 306 [[image:1657329814315-101.png]] 307 307 308 - 309 309 ((( 310 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**212 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]] 311 311 ))) 312 312 313 313 314 314 315 -=== 2.2. 5Use CoAP protocol to uplink data ===217 +=== 2.2.4 Use CoAP protocol to uplink data === 316 316 219 +(% 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/]] 317 317 318 -(% 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/]]** 319 319 320 - 321 -((( 322 322 **Use below commands:** 323 -))) 324 324 325 -* ((( 326 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 327 -))) 328 -* ((( 329 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 330 -))) 331 -* ((( 332 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 333 -))) 224 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 225 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 226 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 334 334 335 -((( 336 - 337 - 338 338 For parameter description, please refer to AT command set 339 -))) 340 340 341 -[[image:1657 352146020-183.png]]230 +[[image:1657249793983-486.png]] 342 342 343 343 344 -((( 345 -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. 346 -))) 233 +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. 347 347 348 -[[image:1657 352185396-303.png]]235 +[[image:1657249831934-534.png]] 349 349 350 350 351 351 352 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===239 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 353 353 241 +This feature is supported since firmware version v1.0.1 354 354 355 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 243 + 244 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 356 356 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 357 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 246 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 358 358 248 +[[image:1657249864775-321.png]] 359 359 360 360 361 -[[image:1657 352391268-297.png]]251 +[[image:1657249930215-289.png]] 362 362 363 363 364 -[[image:1657352403317-397.png]] 365 365 255 +=== 2.2.6 Use MQTT protocol to uplink data === 366 366 257 +This feature is supported since firmware version v110 367 367 368 -=== 2.2.7 Use MQTT protocol to uplink data === 369 369 260 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 261 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 262 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 263 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 264 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 265 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 266 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 370 370 371 - N95S31B supports only plain MQTT now it doesn't support TLSand other related encryption.268 +[[image:1657249978444-674.png]] 372 372 373 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 374 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 375 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 376 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 377 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 378 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 379 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 380 380 271 +[[image:1657249990869-686.png]] 381 381 382 382 383 -[[image:1657352634421-276.png]] 384 - 385 - 386 -[[image:1657352645687-385.png]] 387 - 388 - 389 389 ((( 390 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.275 +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. 391 391 ))) 392 392 393 393 394 -((( 395 -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. 396 -))) 397 397 280 +=== 2.2.7 Use TCP protocol to uplink data === 398 398 399 - 400 -=== 2.2.8 Use TCP protocol to uplink data === 401 - 402 - 403 403 This feature is supported since firmware version v110 404 404 284 + 405 405 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 406 406 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 407 407 288 +[[image:1657250217799-140.png]] 408 408 409 409 410 -[[image:1657 352898400-901.png]]291 +[[image:1657250255956-604.png]] 411 411 412 412 413 -[[image:1657352914475-252.png]] 414 414 295 +=== 2.2.8 Change Update Interval === 415 415 416 - 417 -=== 2.2.9 Change Update Interval === 418 - 419 - 420 420 User can use below command to change the (% style="color:green" %)**uplink interval**. 421 421 422 422 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 423 423 424 424 ((( 425 - 302 +(% style="color:red" %)**NOTE:** 426 426 ))) 427 427 305 +((( 306 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 307 +))) 428 428 429 429 310 + 430 430 == 2.3 Uplink Payload == 431 431 313 +In this mode, uplink payload includes in total 18 bytes 432 432 315 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 316 +|=(% style="width: 60px;" %)((( 317 +**Size(bytes)** 318 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1** 319 +|(% 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:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 320 + 433 433 ((( 434 - N95S31B has differentworkingmodeforthe connections of different typeofsensors. This section describesthesemodes.Usercanuse theAT Command (% style="color:blue"%)**AT+MOD**(%%)toset NBSN95to different workingmodes.322 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 435 435 ))) 436 436 437 437 326 +[[image:image-20220708111918-4.png]] 327 + 328 + 329 +The payload is ASCII string, representative same HEX: 330 + 331 +0x72403155615900640c7817075e0a8c02f900 where: 332 + 333 +* Device ID: 0x 724031556159 = 724031556159 334 +* Version: 0x0064=100=1.0.0 335 + 336 +* BAT: 0x0c78 = 3192 mV = 3.192V 337 +* Singal: 0x17 = 23 338 +* Soil Moisture: 0x075e= 1886 = 18.86 % 339 +* Soil Temperature:0x0a8c =2700=27 °C 340 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 341 +* Interrupt: 0x00 = 0 342 + 343 +== 2.4 Payload Explanation and Sensor Interface == 344 + 345 + 346 +=== 2.4.1 Device ID === 347 + 438 438 ((( 439 - Forexample:349 +By default, the Device ID equal to the last 6 bytes of IMEI. 440 440 ))) 441 441 442 442 ((( 443 - (% style="color:blue" %)**AT+ CFGMOD=2**~/~/willsetthe N95S31B towork in MOD=2 distancemode whichtargetto measure distancevia UltrasonicSensor.353 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 444 444 ))) 445 445 446 - 447 447 ((( 448 - The uplink payloads are composed in ASCII String. For example:357 +**Example:** 449 449 ))) 450 450 451 451 ((( 452 -0 a cd 00 ed 0a cc 00 00 ef 02 d21d (total24 ASCII Chars) . Representative the actually payload:361 +AT+DEUI=A84041F15612 453 453 ))) 454 454 455 455 ((( 456 - 0x0acd00ed0acc0000ef02d21dTotal12 bytes365 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 457 457 ))) 458 458 459 459 369 + 370 +=== 2.4.2 Version Info === 371 + 460 460 ((( 461 - (%style="color:red"%)**NOTE:**373 +Specify the software version: 0x64=100, means firmware version 1.00. 462 462 ))) 463 463 464 -(% style="color:red" %) 465 -1. ((( 466 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 376 +((( 377 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 467 467 ))) 468 -1. ((( 469 -**By default, the device will send an uplink message every 1 hour.** 470 470 471 471 472 472 473 - 382 +=== 2.4.3 Battery Info === 383 + 384 +((( 385 +Check the battery voltage for LSE01. 474 474 ))) 475 475 476 -=== 2.3.1 Payload Analyze === 388 +((( 389 +Ex1: 0x0B45 = 2885mV 390 +))) 477 477 392 +((( 393 +Ex2: 0x0B49 = 2889mV 394 +))) 478 478 479 -N95S31B uplink payload includes in total 21 bytes 480 480 481 481 482 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 483 -|=(% style="width: 60px;" %)((( 484 -**Size(bytes)** 485 -)))|=(% 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** 486 -|(% 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" %)((( 398 +=== 2.4.4 Signal Strength === 399 + 487 487 ((( 488 - Reserve/Sameas NBSN95 CFGMOD=1401 +NB-IoT Network signal Strength. 489 489 ))) 490 490 491 491 ((( 492 - Nofunctionhere.405 +**Ex1: 0x1d = 29** 493 493 ))) 494 - )))|(% style="width:77px" %)(((407 + 495 495 ((( 496 - [[Temperature>>||anchor="H2.3.6A0Temperature26Humidity"]]409 +(% style="color:blue" %)**0**(%%) -113dBm or less 497 497 ))) 498 498 499 499 ((( 500 - BySHT31413 +(% style="color:blue" %)**1**(%%) -111dBm 501 501 ))) 502 - )))|(% style="width:80px" %)(((415 + 503 503 ((( 504 - [[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]417 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 505 505 ))) 506 506 507 507 ((( 508 - BySHT31421 +(% style="color:blue" %)**31** (%%) -51dBm or greater 509 509 ))) 510 -))) 511 511 512 512 ((( 513 - 514 - 515 -((( 516 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 425 +(% style="color:blue" %)**99** (%%) Not known or not detectable 517 517 ))) 518 -))) 519 519 520 520 521 -[[image:1657354294009-643.png]] 522 522 430 +=== 2.4.5 Soil Moisture === 523 523 524 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 432 +((( 433 +((( 434 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil. 435 +))) 436 +))) 525 525 526 -* Device ID: 0x724031607457 = 724031607457 527 -* Version: 0x006e=110=1.1.0 438 +((( 439 +((( 440 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 441 +))) 442 +))) 528 528 529 -* BAT: 0x0ccd = 3277 mV = 3.277V 530 -* Signal: 0x1b = 27 531 -* Model: 0x01 = 1 532 -* 0x00dc000ccc= reserve, ignore in N95S31B 533 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 534 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 535 - 536 536 ((( 537 537 538 538 ))) 539 539 540 540 ((( 541 - 449 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 542 542 ))) 543 543 544 544 545 -=== 2.3.2 Device ID === 546 546 454 +=== 2.4.6 Soil Temperature === 547 547 548 548 ((( 549 - Bydefault,theDeviceID equal to thelast6bytes ofIMEI.457 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is 550 550 ))) 551 551 552 552 ((( 553 - User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID461 +**Example**: 554 554 ))) 555 555 556 556 ((( 557 - **Example:**465 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 558 558 ))) 559 559 560 560 ((( 561 - AT+DEUI=A84041F15612469 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 562 562 ))) 563 563 564 -((( 565 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 566 -))) 567 567 568 568 474 +=== 2.4.7 Soil Conductivity (EC) === 569 569 570 -=== 2.3.3 Version Info === 571 - 572 - 573 573 ((( 574 - These bytes include thehardware andsoftwareversion.477 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000). 575 575 ))) 576 576 577 577 ((( 578 - Higherbyte: Specifyhardwareversion: always 0x00forN95S31B481 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 579 579 ))) 580 580 581 581 ((( 582 - Lowerbyte:Specifythesoftwareversion:0x6E=110, means firmwareversion110485 +Generally, the EC value of irrigation water is less than 800uS / cm. 583 583 ))) 584 584 585 585 ((( ... ... @@ -587,87 +587,71 @@ 587 587 ))) 588 588 589 589 ((( 590 - Forexample: 0x00 6E: this device is N95S31B with firmware version 110.493 + 591 591 ))) 592 592 496 +=== 2.4.8 Digital Interrupt === 497 + 593 593 ((( 594 - 499 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server. 595 595 ))) 596 596 597 - 598 -=== 2.3.4 Battery Info === 599 - 600 - 601 601 ((( 602 - Ex1:0x0B45 = 2885mV503 +The command is: 603 603 ))) 604 604 605 605 ((( 606 - Ex2:0x0B49=2889mV507 +(% 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]])**.** 607 607 ))) 608 608 609 609 511 +((( 512 +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. 513 +))) 610 610 611 -=== 2.3.5 Signal Strength === 612 612 613 - 614 614 ((( 615 - NB-IoT Network signalStrength.517 +Example: 616 616 ))) 617 617 618 618 ((( 619 - **Ex1:0x1d=29**521 +0x(00): Normal uplink packet. 620 620 ))) 621 621 622 622 ((( 623 -( %style="color:blue"%)**0**(%%) -113dBm orless525 +0x(01): Interrupt Uplink Packet. 624 624 ))) 625 625 528 + 529 + 530 +=== 2.4.9 +5V Output === 531 + 626 626 ((( 627 - (%style="color:blue"%)**1**(%%)-111dBm533 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 628 628 ))) 629 629 536 + 630 630 ((( 631 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm538 +The 5V output time can be controlled by AT Command. 632 632 ))) 633 633 634 634 ((( 635 -(% style="color:blue" %)** 31**(%%) -51dBm or greater542 +(% style="color:blue" %)**AT+5VT=1000** 636 636 ))) 637 637 638 638 ((( 639 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable546 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 640 640 ))) 641 641 642 642 643 643 644 -== =2.3.6Temperature & Humidity ===551 +== 2.5 Downlink Payload == 645 645 553 +By default, NSE01 prints the downlink payload to console port. 646 646 647 - The devicewill beable toget the SHT31temperature and humidity data now and upload to IoT Server.555 +[[image:image-20220708133731-5.png]] 648 648 649 -[[image:image-20220709161741-3.png]] 650 650 651 - 652 -Convert the read byte to decimal and divide it by ten. 653 - 654 - 655 -**Example:** 656 - 657 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 658 - 659 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 660 - 661 - 662 - 663 -== 2.4 Downlink Payload == 664 - 665 - 666 -By default, N95S31B prints the downlink payload to console port. 667 - 668 -[[image:image-20220709100028-1.png]] 669 - 670 - 671 671 ((( 672 672 (% style="color:blue" %)**Examples:** 673 673 ))) ... ... @@ -701,7 +701,7 @@ 701 701 ))) 702 702 703 703 ((( 704 -If payload = 0x04FF, it will reset the 95S31B591 +If payload = 0x04FF, it will reset the NSE01 705 705 ))) 706 706 707 707 ... ... @@ -713,20 +713,78 @@ 713 713 714 714 715 715 716 -== 2. 5BatteryAnalysis==603 +== 2.6 LED Indicator == 717 717 605 +((( 606 +The NSE01 has an internal LED which is to show the status of different state. 718 718 719 -=== 2.5.1 Battery Type === 720 720 609 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 610 +* Then the LED will be on for 1 second means device is boot normally. 611 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 612 +* For each uplink probe, LED will be on for 500ms. 613 +))) 721 721 615 + 616 + 617 + 618 +== 2.7 Installation in Soil == 619 + 620 +__**Measurement the soil surface**__ 621 + 722 722 ((( 723 - TheN95S31B batteryisa combination ofan 8500mAhLi/SOCI2BatteryandaSuperCapacitor.Thebatteryisnone-rechargeablebatterytypewithaowdischargeate(<2%peryear).Thistype ofbatteryiscommonlyusedinIoT devicessuchaswatermeter.623 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]] 724 724 ))) 725 725 626 +[[image:1657259653666-883.png]] 627 + 628 + 726 726 ((( 630 + 631 + 632 +((( 633 +Dig a hole with diameter > 20CM. 634 +))) 635 + 636 +((( 637 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 638 +))) 639 +))) 640 + 641 +[[image:1654506665940-119.png]] 642 + 643 +((( 644 + 645 +))) 646 + 647 + 648 +== 2.8 Firmware Change Log == 649 + 650 + 651 +Download URL & Firmware Change log 652 + 653 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 654 + 655 + 656 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 657 + 658 + 659 + 660 +== 2.9 Battery Analysis == 661 + 662 +=== 2.9.1 Battery Type === 663 + 664 + 665 +((( 666 +The NSE01 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. 667 +))) 668 + 669 + 670 +((( 727 727 The battery is designed to last for several years depends on the actually use environment and update interval. 728 728 ))) 729 729 674 + 730 730 ((( 731 731 The battery related documents as below: 732 732 ))) ... ... @@ -736,42 +736,61 @@ 736 736 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 737 737 738 738 ((( 739 -[[image:image-2022070 9101450-2.png]]684 +[[image:image-20220708140453-6.png]] 740 740 ))) 741 741 742 742 743 743 744 -=== 2. 5.2 Power consumption Analyze ===689 +=== 2.9.2 Power consumption Analyze === 745 745 691 +((( 692 +Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval. 693 +))) 746 746 695 + 747 747 ((( 748 - The file **DRAGINO_N95S31B-Power-Analyzer.pdf** from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement toanalyzethe powerconsumption in different case.User can useit for design guideline for their project.697 +Instruction to use as below: 749 749 ))) 750 750 751 751 ((( 752 - 701 +(% 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/]] 753 753 ))) 754 754 755 755 756 -=== 2.5.3 Battery Note === 705 +((( 706 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 707 +))) 757 757 709 +* ((( 710 +Product Model 711 +))) 712 +* ((( 713 +Uplink Interval 714 +))) 715 +* ((( 716 +Working Mode 717 +))) 758 758 759 759 ((( 760 - The Li-SICO batteryis designed for smallcurrent/ long periodapplication.Itisnotgoodto use a high current, short period transmit method. The recommendedminimum period for useof thisbatteryis5 minutes. If you use a shorterperiod time to uplinkdata, thenthe battery life may be decreased.720 +And the Life expectation in difference case will be shown on the right. 761 761 ))) 762 762 723 +[[image:image-20220708141352-7.jpeg]] 763 763 764 764 765 -=== 2.5.4 Replace the battery === 766 766 727 +=== 2.9.3 Battery Note === 767 767 768 768 ((( 769 - You can changethebattery intheN95S31B.Thetype ofbatteryis notlimitedaslongas theutput isbetween3vto3.6v.Onthemainboard,there isa diode(D1)betweenthebatteryandthemaincircuit. If youneed touse abatterywith less than 3.3v,pleaseremove the D1 andshortcut the twopadsofitso there won'tbe voltagedropbetween batteryandmainboard.730 +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 transmit LoRa, then the battery life may be decreased. 770 770 ))) 771 771 772 772 734 + 735 +=== 2.9.4 Replace the battery === 736 + 773 773 ((( 774 -The default battery pack of N 95S31Bincludes 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).738 +The default battery pack of NSE01 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). 775 775 ))) 776 776 777 777 ... ... @@ -778,7 +778,6 @@ 778 778 779 779 = 3. Access NB-IoT Module = 780 780 781 - 782 782 ((( 783 783 Users can directly access the AT command set of the NB-IoT module. 784 784 ))) ... ... @@ -785,23 +785,19 @@ 785 785 786 786 ((( 787 787 The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 788 - 789 - 790 790 ))) 791 791 792 -[[image:1657 333200519-600.png]]753 +[[image:1657261278785-153.png]] 793 793 794 794 795 795 796 796 = 4. Using the AT Commands = 797 797 798 - 799 799 == 4.1 Access AT Commands == 800 800 761 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 801 801 802 -See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]] 803 803 804 - 805 805 AT+<CMD>? : Help on <CMD> 806 806 807 807 AT+<CMD> : Run <CMD> ... ... @@ -875,7 +875,6 @@ 875 875 876 876 = 5. FAQ = 877 877 878 - 879 879 == 5.1 How to Upgrade Firmware == 880 880 881 881 ... ... @@ -888,18 +888,20 @@ 888 888 ))) 889 889 890 890 ((( 891 - 849 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 850 +))) 892 892 852 + 853 + 854 +== 5.2 Can I calibrate NSE01 to different soil types? == 855 + 893 893 ((( 894 - (%style="color:red"%)**Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.**857 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 895 895 ))) 896 -))) 897 897 898 898 899 - 900 900 = 6. Trouble Shooting = 901 901 902 - 903 903 == 6.1 Connection problem when uploading firmware == 904 904 905 905 ... ... @@ -915,7 +915,6 @@ 915 915 916 916 == 6.2 AT Command input doesn't work == 917 917 918 - 919 919 ((( 920 920 In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string. 921 921 ... ... @@ -926,7 +926,7 @@ 926 926 = 7. Order Info = 927 927 928 928 929 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**888 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 930 930 931 931 932 932 (% class="wikigeneratedid" %) ... ... @@ -941,7 +941,7 @@ 941 941 942 942 (% style="color:#037691" %)**Package Includes**: 943 943 944 -* N 95S31BNB-IoTTemperatureandHumiditySensor903 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 945 945 * External antenna x 1 946 946 ))) 947 947 ... ... @@ -950,10 +950,8 @@ 950 950 951 951 (% style="color:#037691" %)**Dimension and weight**: 952 952 953 -* Device Size: 13.0 x 5 x 4.5 cm 954 -* Device Weight: 150g 955 -* Package Size / pcs : 14.0 x 8x 5 cm 956 -* Weight / pcs : 180g 912 +* Size: 195 x 125 x 55 mm 913 +* Weight: 420g 957 957 ))) 958 958 959 959 ((( ... ... @@ -965,9 +965,5 @@ 965 965 966 966 = 9. Support = 967 967 968 - 969 969 * Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule. 970 970 * Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]] 971 - 972 - 973 -
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -83.8 KB - Content
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709093918-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -61.9 KB - Content
- image-20220709100028-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.8 KB - Content
- image-20220709101450-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.5 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -611.5 KB - Content
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -111.2 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -29.7 KB - Content