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 "1657333200519-600.png", version {1}
Summary
-
Page properties (3 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 22 removed)
- 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-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,16 +58,19 @@ 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 58 + 71 71 == 1.3 Specification == 72 72 73 73 ... ... @@ -93,9 +93,15 @@ 93 93 * Max continuously current: 130mA 94 94 * Max boost current: 2A, 1 second 95 95 96 - ==1.4Applications ==84 +(% style="color:#037691" %)**Power Consumption** 97 97 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 98 98 89 + 90 + 91 +== 1.4 Applications == 92 + 99 99 * Smart Buildings & Home Automation 100 100 * Logistics and Supply Chain Management 101 101 * Smart Metering ... ... @@ -108,64 +108,24 @@ 108 108 109 109 110 110 111 -== 1.5 Pin Definitions & Switch==105 +== 1.5 Pin Definitions == 112 112 113 113 114 - N95S31B use themother board from NBSN95which as below.108 +[[image:1657328609906-564.png]] 115 115 116 116 117 -[[image:image-20220709144723-1.png]] 118 118 112 += 2. Use NDDS75 to communicate with IoT Server = 119 119 120 - 121 -=== 1.5.1 Jumper JP2 === 122 - 123 - 124 -Power on Device when put this jumper. 125 - 126 - 127 - 128 -=== 1.5.2 BOOT MODE / SW1 === 129 - 130 - 131 -((( 132 -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. 133 -))) 134 - 135 -((( 136 -2) Flash: work mode, device starts to work and send out console output for further debug 137 -))) 138 - 139 - 140 - 141 -=== 1.5.3 Reset Button === 142 - 143 - 144 -Press to reboot the device. 145 - 146 - 147 - 148 -=== 1.5.4 LED === 149 - 150 - 151 -It will flash: 152 - 153 -1. When boot the device in flash mode 154 -1. Send an uplink packet 155 - 156 -= 2. Use N95S31B to communicate with IoT Server = 157 - 158 - 159 159 == 2.1 How it works == 160 160 161 - 162 162 ((( 163 -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.117 +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. 164 164 ))) 165 165 166 166 167 167 ((( 168 -The diagram below shows the working flow in default firmware of N 95S31B:122 +The diagram below shows the working flow in default firmware of NDDS75: 169 169 ))) 170 170 171 171 ((( ... ... @@ -172,7 +172,7 @@ 172 172 173 173 ))) 174 174 175 -[[image:1657 520100595-569.png]]129 +[[image:1657328659945-416.png]] 176 176 177 177 ((( 178 178 ... ... @@ -179,69 +179,30 @@ 179 179 ))) 180 180 181 181 182 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 183 183 184 184 185 -=== 2.2.1 Power On N95S31B === 186 - 187 - 188 -[[image:image-20220709150546-2.png]] 189 - 190 - 191 - 192 192 === 2.2.1 Test Requirement === 193 193 194 - 195 195 ((( 196 -To use N 95S31Bin your city, make sure meet below requirements:142 +To use NDDS75 in your city, make sure meet below requirements: 197 197 ))) 198 198 199 -* ((( 200 -Your local operator has already distributed a NB-IoT Network there. 201 -))) 202 -* ((( 203 -The local NB-IoT network used the band that N95S31B supports. 204 -))) 205 -* ((( 206 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 207 -))) 145 +* Your local operator has already distributed a NB-IoT Network there. 146 +* The local NB-IoT network used the band that NSE01 supports. 147 +* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 208 208 209 209 ((( 210 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 150 +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 211 211 ))) 212 212 213 -((( 214 -N95S31B supports different communication protocol such as : 215 -))) 216 216 217 -((( 218 -* ((( 219 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 220 -))) 221 -* ((( 222 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 223 -))) 224 -* ((( 225 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 226 -))) 227 -* ((( 228 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 229 -))) 154 +[[image:1657328756309-230.png]] 230 230 231 -((( 232 -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. 233 -))) 234 234 235 - 236 -))) 237 237 238 - [[image:1657350625843-586.png]]158 +=== 2.2.2 Insert SIM card === 239 239 240 - 241 - 242 -=== 2.2.3 Insert SIM card === 243 - 244 - 245 245 ((( 246 246 Insert the NB-IoT Card get from your provider. 247 247 ))) ... ... @@ -251,24 +251,20 @@ 251 251 ))) 252 252 253 253 254 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 255 255 256 256 257 257 258 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 259 259 260 - 261 261 ((( 262 262 ((( 263 -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. 264 - 265 - 177 +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. 266 266 ))) 267 267 ))) 268 268 269 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 270 270 271 - 272 272 **Connection:** 273 273 274 274 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -287,323 +287,253 @@ 287 287 * Flow Control: (% style="color:green" %)**None** 288 288 289 289 ((( 290 -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.201 +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. 291 291 ))) 292 292 293 293 [[image:1657329814315-101.png]] 294 294 295 - 296 296 ((( 297 -(% 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]]**207 +(% 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/]] 298 298 ))) 299 299 300 300 301 301 302 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 303 303 214 +(% 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/]] 304 304 305 -(% 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/]]** 306 306 307 - 308 -((( 309 309 **Use below commands:** 310 -))) 311 311 312 -* ((( 313 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 314 -))) 315 -* ((( 316 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 317 -))) 318 -* ((( 319 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 320 -))) 219 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 221 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 321 321 322 -((( 323 - 324 - 325 325 For parameter description, please refer to AT command set 326 -))) 327 327 328 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 329 329 330 330 331 -((( 332 332 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. 333 -))) 334 334 335 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 336 336 337 337 338 338 339 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 340 340 341 341 342 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 343 343 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 344 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 345 345 346 -[[image:16573 52391268-297.png]]241 +[[image:1657330501006-241.png]] 347 347 348 348 349 -[[image:16573 52403317-397.png]]244 +[[image:1657330533775-472.png]] 350 350 351 351 352 352 353 -=== 2.2. 7Use MQTT protocol to uplink data ===248 +=== 2.2.6 Use MQTT protocol to uplink data === 354 354 355 355 356 -N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 251 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 252 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 253 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 254 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 255 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 256 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 257 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 357 357 358 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 359 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 360 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 361 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 362 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 363 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 364 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 259 +[[image:1657249978444-674.png]] 365 365 366 -[[image:1657352634421-276.png]] 367 367 262 +[[image:1657330723006-866.png]] 368 368 369 -[[image:1657352645687-385.png]] 370 370 371 - 372 372 ((( 373 -To savebatterylife,N95S31Bwillestablishasubscriptionbeforeeachuplinkandclose thesubscription3 secondsafteruplinksuccessful. Any downlink commandsfromserver will onlyarriveduringthesubscriptionperiod.266 +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. 374 374 ))) 375 375 376 376 377 -((( 378 -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. 379 -))) 380 380 271 +=== 2.2.7 Use TCP protocol to uplink data === 381 381 382 382 383 -=== 2.2.8 Use TCP protocol to uplink data === 384 - 385 - 386 -This feature is supported since firmware version v110 387 - 388 388 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 389 389 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 390 390 391 -[[image: 1657352898400-901.png]]277 +[[image:image-20220709093918-1.png]] 392 392 393 393 394 -[[image: 1657352914475-252.png]]280 +[[image:image-20220709093918-2.png]] 395 395 396 396 397 397 398 -=== 2.2. 9Change Update Interval ===284 +=== 2.2.8 Change Update Interval === 399 399 400 - 401 401 User can use below command to change the (% style="color:green" %)**uplink interval**. 402 402 403 403 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 404 404 405 405 ((( 406 - 291 +(% style="color:red" %)**NOTE:** 407 407 ))) 408 408 409 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 294 +((( 295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 296 +))) 410 410 411 -**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).** 412 412 413 413 414 414 == 2.3 Uplink Payload == 415 415 302 +In this mode, uplink payload includes in total 14 bytes 416 416 417 -((( 418 -N95S31B 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. 419 -))) 420 420 305 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 306 +|=(% style="width: 60px;" %)((( 307 +**Size(bytes)** 308 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 50px;" %)**1** 309 +|(% 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" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 421 421 422 422 ((( 423 - For example:312 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 424 424 ))) 425 425 426 -((( 427 - (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 428 -))) 429 429 316 +[[image:1657331036973-987.png]] 430 430 431 431 ((( 432 -The uplink payloadsare composedinASCIIString.Forxample:319 +The payload is ASCII string, representative same HEX: 433 433 ))) 434 434 435 435 ((( 436 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:323 +0x72403155615900640c6c19029200 where: 437 437 ))) 438 438 439 -((( 440 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes326 +* ((( 327 +Device ID: 0x724031556159 = 724031556159 441 441 ))) 442 - 443 - 444 -((( 445 -(% style="color:red" %)**NOTE:** 329 +* ((( 330 +Version: 0x0064=100=1.0.0 446 446 ))) 447 447 448 -(% style="color:red" %) 449 -1. ((( 450 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 333 +* ((( 334 +BAT: 0x0c6c = 3180 mV = 3.180V 451 451 ))) 452 -1. ((( 453 -**By default, the device will send an uplink message every 1 hour.** 454 - 455 - 456 - 457 - 336 +* ((( 337 +Signal: 0x19 = 25 458 458 ))) 339 +* ((( 340 +Distance: 0x0292= 658 mm 341 +))) 342 +* ((( 343 +Interrupt: 0x00 = 0 344 +))) 459 459 460 -=== 2.3.1 Payload Analyze === 461 461 347 +== 2.4 Payload Explanation and Sensor Interface == 462 462 463 -N95S31B uplink payload includes in total 21 bytes 464 464 350 +=== 2.4.1 Device ID === 465 465 466 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %) 467 -|=(% style="width: 60px;" %)((( 468 -**Size(bytes)** 469 -)))|=(% 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** 470 -|(% 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" %)((( 471 471 ((( 472 - Reserve/Same asNBSN95CFGMOD=1353 +By default, the Device ID equal to the last 6 bytes of IMEI. 473 473 ))) 474 474 475 475 ((( 476 - Nofunctionhere.357 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 477 477 ))) 478 -)))|(% style="width:77px" %)((( 479 -((( 480 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 481 -))) 482 482 483 483 ((( 484 - By SHT31361 +**Example:** 485 485 ))) 486 -)))|(% style="width:80px" %)((( 487 -((( 488 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 489 -))) 490 490 491 491 ((( 492 - By SHT31365 +AT+DEUI=A84041F15612 493 493 ))) 494 -))) 495 495 496 496 ((( 497 - 498 - 499 -((( 500 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 369 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 501 501 ))) 502 -))) 503 503 504 504 505 -[[image:1657354294009-643.png]] 506 506 374 +=== 2.4.2 Version Info === 507 507 508 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 509 - 510 -* Device ID: 0x724031607457 = 724031607457 511 -* Version: 0x006e=110=1.1.0 512 - 513 -* BAT: 0x0ccd = 3277 mV = 3.277V 514 -* Signal: 0x1b = 27 515 -* Model: 0x01 = 1 516 -* 0x00dc000ccc= reserve, ignore in N95S31B 517 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 518 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 519 - 520 520 ((( 521 - 377 +Specify the software version: 0x64=100, means firmware version 1.00. 522 522 ))) 523 523 524 524 ((( 525 - (%style="color:red"%)**NOTE:Whenthefirmware versionis v1.2 and later firmware:**381 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 526 526 ))) 527 527 528 -In this mode, uplink payload includes 91 bytes in total by default. 529 529 530 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded. 531 531 532 -|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 533 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 386 +=== 2.4.3 Battery Info === 534 534 535 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 388 +((( 389 +Check the battery voltage for LSE01. 390 +))) 536 536 537 -[[image:image-20220908154949-1.png]] 392 +((( 393 +Ex1: 0x0B45 = 2885mV 394 +))) 538 538 539 -The payload is ASCII string, representative same HEX: 396 +((( 397 +Ex2: 0x0B49 = 2889mV 398 +))) 540 540 541 -0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00**//0030//**(% style="color:blue" %)**//0114//**(% style="color:red" %)**//0231//**(% style="color:green" %)**//63199d3c//**0113023163199d12//**0113023163199c5e**//0112023763199baa//**0112023263199af6**//0111023b631999a7//**0112023b631998f3**//011202426319983f//**01110242631996eb**//(%%) where: 542 542 543 -* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 544 -* (% style="color:blue" %) Version: 0x000c=120=1.2 545 -* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 546 -* (% style="color:red" %) Singal: 0x0c = 12 547 -* (% style="color:blue" %) Mod: 0x01 = 1 548 -* TemDS18B20: 0x0000= 0 = 0 549 -* (% style="color:green" %)Interrupt: 0x00= 0 550 -* (% style="color:green" %)adc: 0x0030= 48 551 -* SHTTEM: 0x0114= 276 = 27.6 552 -* SHTHUM:0x0231 =561=56.1% 553 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 554 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 555 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 556 556 557 -=== 2. 3.2DeviceID===402 +=== 2.4.4 Signal Strength === 558 558 404 +((( 405 +NB-IoT Network signal Strength. 406 +))) 559 559 560 560 ((( 561 - Bydefault,theDevice ID equal to the last 6 bytes of IMEI.409 +**Ex1: 0x1d = 29** 562 562 ))) 563 563 564 564 ((( 565 - User can use(% style="color:blue" %)**AT+DEUI**(%%)tosetDeviceID413 +(% style="color:blue" %)**0**(%%) -113dBm or less 566 566 ))) 567 567 568 568 ((( 569 - **Example:**417 +(% style="color:blue" %)**1**(%%) -111dBm 570 570 ))) 571 571 572 572 ((( 573 - AT+DEUI=A84041F15612421 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 574 574 ))) 575 575 576 576 ((( 577 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 425 +(% style="color:blue" %)**31** (%%) -51dBm or greater 426 +))) 578 578 579 - 428 +((( 429 +(% style="color:blue" %)**99** (%%) Not known or not detectable 580 580 ))) 581 581 582 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 583 583 584 584 585 - Bydefault,the Device ID equaltohelast 15 bits of IMEI.434 +=== 2.4.5 Soil Moisture === 586 586 587 - Usercanuse**AT+DEUI**tosetDeviceID436 +Get the distance. Flat object range 280mm - 7500mm. 588 588 589 - **Example:**438 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 590 590 591 -AT+DEUI=868411056754138 592 - 593 - 594 -=== 2.3.3 Version Info === 595 - 596 - 597 597 ((( 598 -These bytes include the hardware and software version. 599 -))) 600 - 601 601 ((( 602 - Higherbyte: Specify hardwareversion:always0x00forN95S31B442 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 603 603 ))) 444 +))) 604 604 605 605 ((( 606 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110447 + 607 607 ))) 608 608 609 609 ((( ... ... @@ -610,85 +610,65 @@ 610 610 611 611 ))) 612 612 454 +=== 2.4.6 Digital Interrupt === 455 + 613 613 ((( 614 - For example:0x00 6E:thisdevice isN95S31Bwithfirmwareversion110.457 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 615 615 ))) 616 616 617 617 ((( 618 - 461 +The command is: 619 619 ))) 620 620 621 - 622 -=== 2.3.4 Battery Info === 623 - 624 - 625 625 ((( 626 - Ex1:0x0B45=2885mV465 +(% 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]])**.** 627 627 ))) 628 628 468 + 629 629 ((( 630 - Ex2:0x0B49=2889mV470 +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. 631 631 ))) 632 632 633 633 634 - 635 -=== 2.3.5 Signal Strength === 636 - 637 - 638 638 ((( 639 - NB-IoT Network signalStrength.475 +Example: 640 640 ))) 641 641 642 642 ((( 643 - **Ex1:0x1d=29**479 +0x(00): Normal uplink packet. 644 644 ))) 645 645 646 646 ((( 647 -( %style="color:blue"%)**0**(%%) -113dBm orless483 +0x(01): Interrupt Uplink Packet. 648 648 ))) 649 649 486 + 487 + 488 +=== 2.4.7 +5V Output === 489 + 650 650 ((( 651 - (%style="color:blue"%)**1**(%%)-111dBm491 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 652 652 ))) 653 653 494 + 654 654 ((( 655 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm496 +The 5V output time can be controlled by AT Command. 656 656 ))) 657 657 658 658 ((( 659 -(% style="color:blue" %)** 31**(%%) -51dBm or greater500 +(% style="color:blue" %)**AT+5VT=1000** 660 660 ))) 661 661 662 662 ((( 663 - (%style="color:blue"%)**99**(%%)Notknownornotdetectable504 +Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 664 664 ))) 665 665 666 666 667 667 668 -== =2.3.6Temperature & Humidity ===509 +== 2.5 Downlink Payload == 669 669 511 +By default, NDDS75 prints the downlink payload to console port. 670 670 671 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 672 - 673 -[[image:image-20220709161741-3.png]] 674 - 675 - 676 -Convert the read byte to decimal and divide it by ten. 677 - 678 - 679 -**Example:** 680 - 681 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 682 - 683 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 684 - 685 - 686 - 687 -== 2.4 Downlink Payload == 688 - 689 - 690 -By default, N95S31B prints the downlink payload to console port. 691 - 692 692 [[image:image-20220709100028-1.png]] 693 693 694 694 ... ... @@ -725,7 +725,7 @@ 725 725 ))) 726 726 727 727 ((( 728 -If payload = 0x04FF, it will reset the 95S31B549 +If payload = 0x04FF, it will reset the NDDS75 729 729 ))) 730 730 731 731 ... ... @@ -736,67 +736,53 @@ 736 736 ))) 737 737 738 738 739 -== 2.5 Humidity and Temperature alarm function == 740 740 741 - ➢ATCommand:561 +== 2.6 LED Indicator == 742 742 743 -AT+ SHHUM=min,max 744 744 745 - ² Whenmin=0,andmax≠0,Alarmhigherthanmax564 +The NDDS75 has an internal LED which is to show the status of different state. 746 746 747 -² When min≠0, and max=0, Alarm lower than min 748 748 749 -² When min≠0 and max≠0, Alarm higher than max or lower than min 567 +* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 568 +* Then the LED will be on for 1 second means device is boot normally. 569 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 570 +* For each uplink probe, LED will be on for 500ms. 750 750 751 -Example: 572 +((( 573 + 574 +))) 752 752 753 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 754 754 755 755 756 - AT+ SHTEMP=min,max578 +== 2.7 Firmware Change Log == 757 757 758 -² When min=0, and max≠0, Alarm higher than max 759 759 760 - ² Whenmin≠0,andmax=0,Alarmlowerthanmin581 +Download URL & Firmware Change log 761 761 762 -² When min≠0 and max≠0, Alarm higher than max or lower than min 583 +((( 584 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]] 585 +))) 763 763 764 -Example: 765 765 766 - AT+SHTEMP=20,30~/~/ Alarmhenemperaturelowerthan 20.588 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 767 767 768 -== 2.6 Set the number of data to be uploaded and the recording time == 769 769 770 -➢ AT Command: 771 771 772 - AT+TR=900~/~/The unit is seconds,andthe defaultis to recorddata once every900seconds.( The minimum can besetto 180 seconds)592 +== 2.9 Battery Analysis == 773 773 774 - AT+NOUD=8~/~/The device uploads 8 sets of recorded data bydefault. Upto 32 setsof record data can be uploaded.594 +=== 2.9.1 Battery Type === 775 775 776 -== 2.7 Read or Clear cached data == 777 777 778 -➢ AT Command: 779 - 780 -AT+CDP ~/~/ Read cached data 781 - 782 -[[image:image-20220908163102-2.png]] 783 - 784 -AT+CDP=0 ~/~/ Clear cached data 785 - 786 -== 2.8 Battery Analysis == 787 - 788 - 789 -=== 2.8.1 Battery Type === 790 - 791 - 792 792 ((( 793 -The N 95S31Bbattery 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.598 +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. 794 794 ))) 795 795 601 + 796 796 ((( 797 797 The battery is designed to last for several years depends on the actually use environment and update interval. 798 798 ))) 799 799 606 + 800 800 ((( 801 801 The battery related documents as below: 802 802 ))) ... ... @@ -806,42 +806,61 @@ 806 806 * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 807 807 808 808 ((( 809 -[[image:image-2022070 9101450-2.png]]616 +[[image:image-20220708140453-6.png]] 810 810 ))) 811 811 812 812 813 813 814 -=== 2. 8.2 Power consumption Analyze ===621 +=== 2.9.2 Power consumption Analyze === 815 815 623 +((( 624 +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. 625 +))) 816 816 627 + 817 817 ((( 818 - 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.629 +Instruction to use as below: 819 819 ))) 820 820 821 821 ((( 822 - 633 +(% 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/]] 823 823 ))) 824 824 825 825 826 -=== 2.8.3 Battery Note === 637 +((( 638 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 639 +))) 827 827 641 +* ((( 642 +Product Model 643 +))) 644 +* ((( 645 +Uplink Interval 646 +))) 647 +* ((( 648 +Working Mode 649 +))) 828 828 829 829 ((( 830 - 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.652 +And the Life expectation in difference case will be shown on the right. 831 831 ))) 832 832 655 +[[image:image-20220708141352-7.jpeg]] 833 833 834 834 835 -=== 2.8.4 Replace the battery === 836 836 659 +=== 2.9.3 Battery Note === 837 837 838 838 ((( 839 - 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.662 +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. 840 840 ))) 841 841 842 842 666 + 667 +=== 2.9.4 Replace the battery === 668 + 843 843 ((( 844 -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).670 +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). 845 845 ))) 846 846 847 847 ... ... @@ -848,7 +848,6 @@ 848 848 849 849 = 3. Access NB-IoT Module = 850 850 851 - 852 852 ((( 853 853 Users can directly access the AT command set of the NB-IoT module. 854 854 ))) ... ... @@ -855,23 +855,19 @@ 855 855 856 856 ((( 857 857 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/]] 858 - 859 - 860 860 ))) 861 861 862 -[[image:1657 333200519-600.png]]685 +[[image:1657261278785-153.png]] 863 863 864 864 865 865 866 866 = 4. Using the AT Commands = 867 867 868 - 869 869 == 4.1 Access AT Commands == 870 870 693 +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/]] 871 871 872 -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]] 873 873 874 - 875 875 AT+<CMD>? : Help on <CMD> 876 876 877 877 AT+<CMD> : Run <CMD> ... ... @@ -911,24 +911,7 @@ 911 911 912 912 AT+SERVADDR : Server Address 913 913 914 -AT+TR : Get or Set record time 915 915 916 -AT+APN : Get or set the APN 917 - 918 -AT+FBAND : Get or Set whether to automatically modify the frequency band 919 - 920 -AT+DNSCFG : Get or Set DNS Server 921 - 922 -AT+GETSENSORVALUE : Returns the current sensor measurement 923 - 924 -AT+NOUD : Get or Set the number of data to be uploaded 925 - 926 -AT+CDP : Read or Clear cached data 927 - 928 -AT+SHTEMP: Get or Set alarm of temp 929 - 930 -AT+SHHUM: Get or Set alarm of moisture 931 - 932 932 (% style="color:#037691" %)**COAP Management** 933 933 934 934 AT+URI : Resource parameters ... ... @@ -962,7 +962,6 @@ 962 962 963 963 = 5. FAQ = 964 964 965 - 966 966 == 5.1 How to Upgrade Firmware == 967 967 968 968 ... ... @@ -975,18 +975,20 @@ 975 975 ))) 976 976 977 977 ((( 978 - 781 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 782 +))) 979 979 784 + 785 + 786 +== 5.2 Can I calibrate NSE01 to different soil types? == 787 + 980 980 ((( 981 - (%style="color:red"%)**Notice,N95S31BandLSN50v2share thesamemotherboard.Theyuse thesameconnectionand method toupdate.**789 +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]]. 982 982 ))) 983 -))) 984 984 985 985 986 - 987 987 = 6. Trouble Shooting = 988 988 989 - 990 990 == 6.1 Connection problem when uploading firmware == 991 991 992 992 ... ... @@ -1002,7 +1002,6 @@ 1002 1002 1003 1003 == 6.2 AT Command input doesn't work == 1004 1004 1005 - 1006 1006 ((( 1007 1007 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. 1008 1008 ... ... @@ -1013,7 +1013,7 @@ 1013 1013 = 7. Order Info = 1014 1014 1015 1015 1016 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**820 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 1017 1017 1018 1018 1019 1019 (% class="wikigeneratedid" %) ... ... @@ -1028,7 +1028,7 @@ 1028 1028 1029 1029 (% style="color:#037691" %)**Package Includes**: 1030 1030 1031 -* N 95S31BNB-IoTTemperatureandHumiditySensor835 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 1032 1032 * External antenna x 1 1033 1033 ))) 1034 1034 ... ... @@ -1037,10 +1037,8 @@ 1037 1037 1038 1038 (% style="color:#037691" %)**Dimension and weight**: 1039 1039 1040 -* Device Size: 13.0 x 5 x 4.5 cm 1041 -* Device Weight: 150g 1042 -* Package Size / pcs : 14.0 x 8x 5 cm 1043 -* Weight / pcs : 180g 844 +* Size: 195 x 125 x 55 mm 845 +* Weight: 420g 1044 1044 ))) 1045 1045 1046 1046 ((( ... ... @@ -1052,8 +1052,5 @@ 1052 1052 1053 1053 = 9. Support = 1054 1054 1055 - 1056 1056 * 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. 1057 1057 * 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]] 1058 - 1059 -
- 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-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