Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (2 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 - 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,18 +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 71 71 72 - 73 73 == 1.3 Specification == 74 74 75 75 ... ... @@ -95,11 +95,15 @@ 95 95 * Max continuously current: 130mA 96 96 * Max boost current: 2A, 1 second 97 97 84 +(% style="color:#037691" %)**Power Consumption** 98 98 86 +* STOP Mode: 10uA @ 3.3v 87 +* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 99 99 100 -== 1.4 Applications == 101 101 102 102 91 +== 1.4 Applications == 92 + 103 103 * Smart Buildings & Home Automation 104 104 * Logistics and Supply Chain Management 105 105 * Smart Metering ... ... @@ -112,67 +112,24 @@ 112 112 113 113 114 114 105 +== 1.5 Pin Definitions == 115 115 116 -== 1.5 Pin Definitions & Switch == 117 117 108 +[[image:1657328609906-564.png]] 118 118 119 -N95S31B use the mother board from NBSN95 which as below. 120 120 121 121 122 - [[image:image-20220709144723-1.png]]112 += 2. Use NDDS75 to communicate with IoT Server = 123 123 124 - 125 - 126 -=== 1.5.1 Jumper JP2 === 127 - 128 - 129 -Power on Device when put this jumper. 130 - 131 - 132 - 133 -=== 1.5.2 BOOT MODE / SW1 === 134 - 135 - 136 -((( 137 -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. 138 -))) 139 - 140 -((( 141 -2) Flash: work mode, device starts to work and send out console output for further debug 142 -))) 143 - 144 - 145 - 146 -=== 1.5.3 Reset Button === 147 - 148 - 149 -Press to reboot the device. 150 - 151 - 152 - 153 -=== 1.5.4 LED === 154 - 155 - 156 -It will flash: 157 - 158 -1. When boot the device in flash mode 159 -1. Send an uplink packet 160 - 161 - 162 - 163 -= 2. Use N95S31B to communicate with IoT Server = 164 - 165 - 166 166 == 2.1 How it works == 167 167 168 - 169 169 ((( 170 -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. 171 171 ))) 172 172 173 173 174 174 ((( 175 -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: 176 176 ))) 177 177 178 178 ((( ... ... @@ -179,7 +179,7 @@ 179 179 180 180 ))) 181 181 182 -[[image:1657 520100595-569.png]]129 +[[image:1657328659945-416.png]] 183 183 184 184 ((( 185 185 ... ... @@ -186,69 +186,30 @@ 186 186 ))) 187 187 188 188 189 -== 2.2 Configure the N 95S31B==136 +== 2.2 Configure the NDDS75 == 190 190 191 191 192 -=== 2.2.1 Power On N95S31B === 193 - 194 - 195 -[[image:image-20220709150546-2.png]] 196 - 197 - 198 - 199 199 === 2.2.1 Test Requirement === 200 200 201 - 202 202 ((( 203 -To use N 95S31Bin your city, make sure meet below requirements:142 +To use NDDS75 in your city, make sure meet below requirements: 204 204 ))) 205 205 206 -* ((( 207 -Your local operator has already distributed a NB-IoT Network there. 208 -))) 209 -* ((( 210 -The local NB-IoT network used the band that N95S31B supports. 211 -))) 212 -* ((( 213 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 214 -))) 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. 215 215 216 216 ((( 217 -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 218 218 ))) 219 219 220 -((( 221 -N95S31B supports different communication protocol such as : 222 -))) 223 223 224 -((( 225 -* ((( 226 -CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 227 -))) 228 -* ((( 229 -raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 230 -))) 231 -* ((( 232 -MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 233 -))) 234 -* ((( 235 -TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 236 -))) 154 +[[image:1657328756309-230.png]] 237 237 238 -((( 239 -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. 240 -))) 241 241 242 - 243 -))) 244 244 245 - [[image:1657350625843-586.png]]158 +=== 2.2.2 Insert SIM card === 246 246 247 - 248 - 249 -=== 2.2.3 Insert SIM card === 250 - 251 - 252 252 ((( 253 253 Insert the NB-IoT Card get from your provider. 254 254 ))) ... ... @@ -258,24 +258,20 @@ 258 258 ))) 259 259 260 260 261 -[[image:16573 51240556-536.png]]169 +[[image:1657328884227-504.png]] 262 262 263 263 264 264 265 -=== 2.2. 4Connect USB – TTL to N95S31Bto configure it ===173 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 266 266 267 - 268 268 ((( 269 269 ((( 270 -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. 271 - 272 - 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. 273 273 ))) 274 274 ))) 275 275 276 -[[image: 1657351312545-300.png]]181 +[[image:image-20220709092052-2.png]] 277 277 278 - 279 279 **Connection:** 280 280 281 281 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -294,338 +294,253 @@ 294 294 * Flow Control: (% style="color:green" %)**None** 295 295 296 296 ((( 297 -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. 298 298 ))) 299 299 300 300 [[image:1657329814315-101.png]] 301 301 302 - 303 303 ((( 304 -(% 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/]] 305 305 ))) 306 306 307 307 308 308 309 -=== 2.2. 5Use CoAP protocol to uplink data ===212 +=== 2.2.4 Use CoAP protocol to uplink data === 310 310 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/]] 311 311 312 -(% 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/]]** 313 313 314 - 315 -((( 316 316 **Use below commands:** 317 -))) 318 318 319 -* ((( 320 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 321 -))) 322 -* ((( 323 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 324 -))) 325 -* ((( 326 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 327 -))) 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 328 328 329 -((( 330 - 331 - 332 332 For parameter description, please refer to AT command set 333 -))) 334 334 335 -[[image:1657352 146020-183.png]]225 +[[image:1657330452568-615.png]] 336 336 337 337 338 -((( 339 339 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. 340 -))) 341 341 342 -[[image:16573 52185396-303.png]]230 +[[image:1657330472797-498.png]] 343 343 344 344 345 345 346 -=== 2.2. 6Use UDP protocol to uplink data(Default protocol) ===234 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 347 347 348 348 349 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) 237 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 350 350 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 351 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ 239 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 352 352 353 -[[image:16573 52391268-297.png]]241 +[[image:1657330501006-241.png]] 354 354 355 355 356 -[[image:16573 52403317-397.png]]244 +[[image:1657330533775-472.png]] 357 357 358 358 359 359 360 -=== 2.2. 7Use MQTT protocol to uplink data ===248 +=== 2.2.6 Use MQTT protocol to uplink data === 361 361 362 362 363 -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 364 364 365 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 366 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 367 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 368 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 369 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 370 -* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 371 -* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 259 +[[image:1657249978444-674.png]] 372 372 373 -[[image:1657352634421-276.png]] 374 374 262 +[[image:1657330723006-866.png]] 375 375 376 -[[image:1657352645687-385.png]] 377 377 378 - 379 379 ((( 380 -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. 381 381 ))) 382 382 383 383 384 -((( 385 -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. 386 -))) 387 387 271 +=== 2.2.7 Use TCP protocol to uplink data === 388 388 389 389 390 -=== 2.2.8 Use TCP protocol to uplink data === 391 - 392 - 393 -This feature is supported since firmware version v110 394 - 395 395 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 396 396 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 397 397 398 -[[image: 1657352898400-901.png]]277 +[[image:image-20220709093918-1.png]] 399 399 400 400 401 -[[image: 1657352914475-252.png]]280 +[[image:image-20220709093918-2.png]] 402 402 403 403 404 404 405 -=== 2.2. 9Change Update Interval ===284 +=== 2.2.8 Change Update Interval === 406 406 407 - 408 408 User can use below command to change the (% style="color:green" %)**uplink interval**. 409 409 410 410 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 411 411 412 412 ((( 413 - 291 +(% style="color:red" %)**NOTE:** 414 414 ))) 415 415 416 416 ((( 417 -(% style="color:red" %) **NOTE:Sincefirmware version is v1.2:**295 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 418 418 ))) 419 419 420 -((( 421 -(% style="color:red" %)**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).** 422 -))) 423 423 424 424 425 - 426 426 == 2.3 Uplink Payload == 427 427 302 +In this mode, uplink payload includes in total 14 bytes 428 428 429 -((( 430 -N95S31B has different working modes for the connections of different types 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. 431 -))) 432 432 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"]] 433 433 434 434 ((( 435 - 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. 436 436 ))) 437 437 438 -((( 439 - (% 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. 440 -))) 441 441 316 +[[image:1657331036973-987.png]] 442 442 443 443 ((( 444 -The uplink payloadsare composedinASCIIString.Forxample:319 +The payload is ASCII string, representative same HEX: 445 445 ))) 446 446 447 447 ((( 448 -0 a cd00ed0acc0ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:323 +0x72403155615900640c6c19029200 where: 449 449 ))) 450 450 451 -((( 452 - 0x 0acd 00ed0acc0000ef 02d21d Total12 bytes326 +* ((( 327 +Device ID: 0x724031556159 = 724031556159 453 453 ))) 454 - 455 - 456 -((( 457 -(% style="color:red" %)**NOTE:** 329 +* ((( 330 +Version: 0x0064=100=1.0.0 458 458 ))) 459 459 460 -(% style="color:red" %) 461 -1. ((( 462 -**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 333 +* ((( 334 +BAT: 0x0c6c = 3180 mV = 3.180V 463 463 ))) 464 -1. ((( 465 -**By default, the device will send an uplink message every 1 hour.** 466 - 467 - 468 - 469 - 336 +* ((( 337 +Signal: 0x19 = 25 470 470 ))) 339 +* ((( 340 +Distance: 0x0292= 658 mm 341 +))) 342 +* ((( 343 +Interrupt: 0x00 = 0 344 +))) 471 471 472 -=== 2.3.1 Payload Analyze === 473 473 347 +== 2.4 Payload Explanation and Sensor Interface == 474 474 475 -==== 2.3.1.1 Before Firmware v1.2 ==== 476 476 350 +=== 2.4.1 Device ID === 477 477 478 -N95S31B uplink payload includes in total 21 bytes 479 - 480 - 481 -(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %) 482 -|=(% style="width: 60px;" %)((( 483 -**Size(bytes)** 484 -)))|=(% style="width: 65px;" %)**6**|=(% style="width: 50px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 75px;" %)**1**|=(% style="width: 59px;" %)1|=(% style="width: 174px;" %)5|=(% style="width: 106px;" %)**2**|=(% style="width: 85px;" %)**2** 485 -|(% style="width:97px" %)**Value**|(% style="width:65px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:50px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:75px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:59px" %)MOD 0X01|(% style="width:174px" %)((( 486 486 ((( 487 - Reserve/Same asNBSN95CFGMOD=1353 +By default, the Device ID equal to the last 6 bytes of IMEI. 488 488 ))) 489 489 490 490 ((( 491 - Nofunctionhere.357 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 492 492 ))) 493 -)))|(% style="width:106px" %)((( 494 -((( 495 -[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 496 -))) 497 497 498 498 ((( 499 - By SHT31361 +**Example:** 500 500 ))) 501 -)))|(% style="width:85px" %)((( 502 -((( 503 -[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 504 -))) 505 505 506 506 ((( 507 - By SHT31365 +AT+DEUI=A84041F15612 508 508 ))) 509 -))) 510 510 511 511 ((( 512 - 513 - 514 -((( 515 -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. 516 516 ))) 517 -))) 518 518 519 519 520 -[[image:1657354294009-643.png]] 521 521 374 +=== 2.4.2 Version Info === 522 522 523 -The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where: 376 +((( 377 +Specify the software version: 0x64=100, means firmware version 1.00. 378 +))) 524 524 525 -* Device ID: 0x724031607457 = 724031607457 380 +((( 381 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 382 +))) 526 526 527 -* Version: 0x006e=110=1.1.0 528 528 529 -* BAT: 0x0ccd = 3277 mV = 3.277V 530 530 531 - *Signal:0x1b=27386 +=== 2.4.3 Battery Info === 532 532 533 -* Model: 0x01 = 1 388 +((( 389 +Check the battery voltage for LSE01. 390 +))) 534 534 535 -* 0x00dc000ccc= reserve, ignore in N95S31B 536 - 537 -* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C 538 - 539 -* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh 540 - 541 541 ((( 542 - 393 +Ex1: 0x0B45 = 2885mV 394 +))) 543 543 544 - 545 - 396 +((( 397 +Ex2: 0x0B49 = 2889mV 546 546 ))) 547 547 548 -==== 2.3.1.2 Since Firmware v1.2 ==== 549 549 550 -In this mode, uplink payload includes 91 bytes in total by default. 551 551 552 - Eachtimethe device uploads a data package, 8 sets of recorded data willbe attached. Up to 32 sets ofrecorded datacan be uploaded.402 +=== 2.4.4 Signal Strength === 553 553 554 -|**Size(bytes)**|**8**|2|2|1|1|2|1|2|2|2|4|2|2|4 555 -|**Value**|Device ID|Ver|BAT|Signal Strength|MOD|TemDS18B20|Interrupt|ADC|SHTTEM|SHTHUM|Time stamp |SHTTEM|SHTHUM|Time stamp ..... 404 +((( 405 +NB-IoT Network signal Strength. 406 +))) 556 556 557 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 558 - 559 -[[image:image-20220908154949-1.png]] 560 - 561 -The payload is ASCII string, representative same HEX: 562 - 563 -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: 564 - 565 -* (% style="color:red" %) Device ID: f868411056758782 = f868411056758782 566 -* (% style="color:blue" %) Version: 0x000c=120=1.2 567 -* (% style="color:green" %) BAT: 0x0d0f = 3343 mV = 3.343V 568 -* (% style="color:red" %) Singal: 0x0c = 12 569 -* (% style="color:blue" %) Mod: 0x01 = 1 570 -* TemDS18B20: 0x0000= 0 = 0 571 -* (% style="color:green" %)Interrupt: 0x00= 0 572 -* (% style="color:green" %)adc: 0x0030= 48 573 -* SHTTEM: 0x0114= 276 = 27.6 574 -* SHTHUM:0x0231 =561=56.1% 575 -* (% style="color:red" %) Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 576 -* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12 577 -* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //**0113023163199c5e**//,....... 578 - 579 -=== 2.3.2 Device ID === 580 - 581 - 582 582 ((( 583 - Bydefault,theDevice ID equal to the last 6 bytes of IMEI.409 +**Ex1: 0x1d = 29** 584 584 ))) 585 585 586 586 ((( 587 - User can use(% style="color:blue" %)**AT+DEUI**(%%)tosetDeviceID413 +(% style="color:blue" %)**0**(%%) -113dBm or less 588 588 ))) 589 589 590 590 ((( 591 - **Example:**417 +(% style="color:blue" %)**1**(%%) -111dBm 592 592 ))) 593 593 594 594 ((( 595 - AT+DEUI=A84041F15612421 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 596 596 ))) 597 597 598 598 ((( 599 -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 +))) 600 600 601 - 428 +((( 429 +(% style="color:blue" %)**99** (%%) Not known or not detectable 602 602 ))) 603 603 604 -(% style="color:red" %)**NOTE:When the firmware version is v1.2 and later firmware:** 605 605 606 606 607 - Bydefault,the Device ID equaltohelast 15 bits of IMEI.434 +=== 2.4.5 Soil Moisture === 608 608 609 - Usercanuse**AT+DEUI**tosetDeviceID436 +Get the distance. Flat object range 280mm - 7500mm. 610 610 611 - **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 612 612 613 -AT+DEUI=868411056754138 614 - 615 - 616 -=== 2.3.3 Version Info === 617 - 618 - 619 619 ((( 620 -These bytes include the hardware and software version. 621 -))) 622 - 623 623 ((( 624 - Higherbyte: Specify hardwareversion:always0x00forN95S31B442 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 625 625 ))) 444 +))) 626 626 627 627 ((( 628 - Lowerbyte: Specify the software version: 0x6E=110, means firmware version 110447 + 629 629 ))) 630 630 631 631 ((( ... ... @@ -632,85 +632,65 @@ 632 632 633 633 ))) 634 634 454 +=== 2.4.6 Digital Interrupt === 455 + 635 635 ((( 636 - 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. 637 637 ))) 638 638 639 639 ((( 640 - 461 +The command is: 641 641 ))) 642 642 643 - 644 -=== 2.3.4 Battery Info === 645 - 646 - 647 647 ((( 648 - 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]])**.** 649 649 ))) 650 650 468 + 651 651 ((( 652 - 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. 653 653 ))) 654 654 655 655 656 - 657 -=== 2.3.5 Signal Strength === 658 - 659 - 660 660 ((( 661 - NB-IoT Network signalStrength.475 +Example: 662 662 ))) 663 663 664 664 ((( 665 - **Ex1:0x1d=29**479 +0x(00): Normal uplink packet. 666 666 ))) 667 667 668 668 ((( 669 -( %style="color:blue"%)**0**(%%) -113dBm orless483 +0x(01): Interrupt Uplink Packet. 670 670 ))) 671 671 486 + 487 + 488 +=== 2.4.7 +5V Output === 489 + 672 672 ((( 673 - (%style="color:blue"%)**1**(%%)-111dBm491 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 674 674 ))) 675 675 494 + 676 676 ((( 677 - (%style="color:blue"%)**2...30**(%%)-109dBm...-53dBm496 +The 5V output time can be controlled by AT Command. 678 678 ))) 679 679 680 680 ((( 681 -(% style="color:blue" %)** 31**(%%) -51dBm or greater500 +(% style="color:blue" %)**AT+5VT=1000** 682 682 ))) 683 683 684 684 ((( 685 - (%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. 686 686 ))) 687 687 688 688 689 689 690 -== =2.3.6Temperature & Humidity ===509 +== 2.5 Downlink Payload == 691 691 511 +By default, NDDS75 prints the downlink payload to console port. 692 692 693 -The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 694 - 695 -[[image:image-20220709161741-3.png]] 696 - 697 - 698 -Convert the read byte to decimal and divide it by ten. 699 - 700 - 701 -**Example:** 702 - 703 -Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 704 - 705 -Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 706 - 707 - 708 - 709 -== 2.4 Downlink Payload == 710 - 711 - 712 -By default, N95S31B prints the downlink payload to console port. 713 - 714 714 [[image:image-20220709100028-1.png]] 715 715 716 716 ... ... @@ -747,7 +747,7 @@ 747 747 ))) 748 748 749 749 ((( 750 -If payload = 0x04FF, it will reset the 95S31B549 +If payload = 0x04FF, it will reset the NDDS75 751 751 ))) 752 752 753 753 ... ... @@ -758,61 +758,45 @@ 758 758 ))) 759 759 760 760 761 -== 2.5 Humidity and Temperature alarm function == 762 762 763 - ➢ATCommand:561 +== 2.6 LED Indicator == 764 764 765 -AT+ SHHUM=min,max 766 766 767 - ² Whenmin=0,andmax≠0,Alarmhigherthanmax564 +The NDDS75 has an internal LED which is to show the status of different state. 768 768 769 -² When min≠0, and max=0, Alarm lower than min 770 770 771 -² 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. 772 772 773 -Example: 572 +((( 573 + 574 +))) 774 774 775 -AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 776 776 777 777 778 - AT+ SHTEMP=min,max578 +== 2.7 Firmware Change Log == 779 779 780 -² When min=0, and max≠0, Alarm higher than max 781 781 782 - ² Whenmin≠0,andmax=0,Alarmlowerthanmin581 +Download URL & Firmware Change log 783 783 784 -² 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 +))) 785 785 786 -Example: 787 787 788 - AT+SHTEMP=20,30~/~/ Alarmhenemperaturelowerthan 20.588 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 789 789 790 -== 2.6 Set the number of data to be uploaded and the recording time == 791 791 792 -➢ AT Command: 793 793 794 -AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds) 795 - 796 -AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 797 - 798 -== 2.7 Read or Clear cached data == 799 - 800 -➢ AT Command: 801 - 802 -AT+CDP ~/~/ Read cached data 803 - 804 -[[image:image-20220908163102-2.png]] 805 - 806 -AT+CDP=0 ~/~/ Clear cached data 807 - 808 808 == 2.8 Battery Analysis == 809 809 810 - 811 811 === 2.8.1 Battery Type === 812 812 813 813 814 814 ((( 815 -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 NDDS75 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. 816 816 ))) 817 817 818 818 ((( ... ... @@ -835,35 +835,54 @@ 835 835 836 836 === 2.8.2 Power consumption Analyze === 837 837 621 +((( 622 +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. 623 +))) 838 838 625 + 839 839 ((( 840 - 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.627 +Instruction to use as below: 841 841 ))) 842 842 843 843 ((( 844 - 631 +(% 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/]] 845 845 ))) 846 846 847 847 848 -=== 2.8.3 Battery Note === 635 +((( 636 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 637 +))) 849 849 639 +* ((( 640 +Product Model 641 +))) 642 +* ((( 643 +Uplink Interval 644 +))) 645 +* ((( 646 +Working Mode 647 +))) 850 850 851 851 ((( 852 - 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.650 +And the Life expectation in difference case will be shown on the right. 853 853 ))) 854 854 653 +[[image:image-20220708141352-7.jpeg]] 855 855 856 856 857 -=== 2.8.4 Replace the battery === 858 858 657 +=== 2.8.3 Battery Note === 859 859 860 860 ((( 861 - 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.660 +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. 862 862 ))) 863 863 864 864 664 + 665 +=== 2.8.4 Replace the battery === 666 + 865 865 ((( 866 -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).668 +The default battery pack of NDDS75 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). 867 867 ))) 868 868 869 869 ... ... @@ -870,7 +870,6 @@ 870 870 871 871 = 3. Access NB-IoT Module = 872 872 873 - 874 874 ((( 875 875 Users can directly access the AT command set of the NB-IoT module. 876 876 ))) ... ... @@ -877,8 +877,6 @@ 877 877 878 878 ((( 879 879 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/]] 880 - 881 - 882 882 ))) 883 883 884 884 [[image:1657333200519-600.png]] ... ... @@ -887,13 +887,11 @@ 887 887 888 888 = 4. Using the AT Commands = 889 889 890 - 891 891 == 4.1 Access AT Commands == 892 892 691 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 893 893 894 -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]] 895 895 896 - 897 897 AT+<CMD>? : Help on <CMD> 898 898 899 899 AT+<CMD> : Run <CMD> ... ... @@ -933,24 +933,7 @@ 933 933 934 934 AT+SERVADDR : Server Address 935 935 936 -AT+TR : Get or Set record time 937 937 938 -AT+APN : Get or set the APN 939 - 940 -AT+FBAND : Get or Set whether to automatically modify the frequency band 941 - 942 -AT+DNSCFG : Get or Set DNS Server 943 - 944 -AT+GETSENSORVALUE : Returns the current sensor measurement 945 - 946 -AT+NOUD : Get or Set the number of data to be uploaded 947 - 948 -AT+CDP : Read or Clear cached data 949 - 950 -AT+SHTEMP: Get or Set alarm of temp 951 - 952 -AT+SHHUM: Get or Set alarm of moisture 953 - 954 954 (% style="color:#037691" %)**COAP Management** 955 955 956 956 AT+URI : Resource parameters ... ... @@ -984,7 +984,6 @@ 984 984 985 985 = 5. FAQ = 986 986 987 - 988 988 == 5.1 How to Upgrade Firmware == 989 989 990 990 ... ... @@ -997,18 +997,13 @@ 997 997 ))) 998 998 999 999 ((( 1000 - 1001 - 1002 -((( 1003 -(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 779 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1004 1004 ))) 1005 -))) 1006 1006 1007 1007 1008 1008 1009 1009 = 6. Trouble Shooting = 1010 1010 1011 - 1012 1012 == 6.1 Connection problem when uploading firmware == 1013 1013 1014 1014 ... ... @@ -1024,7 +1024,6 @@ 1024 1024 1025 1025 == 6.2 AT Command input doesn't work == 1026 1026 1027 - 1028 1028 ((( 1029 1029 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. 1030 1030 ... ... @@ -1035,7 +1035,7 @@ 1035 1035 = 7. Order Info = 1036 1036 1037 1037 1038 -Part Number**:** (% style="color:#4f81bd" %)**N 95S31B-YY**811 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 1039 1039 1040 1040 1041 1041 (% class="wikigeneratedid" %) ... ... @@ -1050,7 +1050,7 @@ 1050 1050 1051 1051 (% style="color:#037691" %)**Package Includes**: 1052 1052 1053 -* N 95S31BNB-IoTTemperatureandHumiditySensor826 +* NSE01 NB-IoT Distance Detect Sensor Node x 1 1054 1054 * External antenna x 1 1055 1055 ))) 1056 1056 ... ... @@ -1059,10 +1059,11 @@ 1059 1059 1060 1060 (% style="color:#037691" %)**Dimension and weight**: 1061 1061 835 + 1062 1062 * Device Size: 13.0 x 5 x 4.5 cm 1063 1063 * Device Weight: 150g 1064 -* Package Size / pcs : 1 4.0x8x 5 cm1065 -* Weight / pcs : 180g838 +* Package Size / pcs : 15 x 12x 5.5 cm 839 +* Weight / pcs : 220g 1066 1066 ))) 1067 1067 1068 1068 ((( ... ... @@ -1074,6 +1074,5 @@ 1074 1074 1075 1075 = 9. Support = 1076 1076 1077 - 1078 1078 * 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. 1079 1079 * 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]]
- 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