Changes for page N95S31B -- NB-IoT Temperature & Humidity Sensor User Manual
Last modified by Mengting Qiu on 2024/04/02 16:44
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 17 added, 0 removed)
- 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-20220709161741-3.png
- image-20220908154949-1.png
- image-20220908163102-2.png
- image-20221009001045-1.png
Details
- Page properties
-
- Content
-
... ... @@ -9,6 +9,7 @@ 9 9 10 10 **Table of Contents:** 11 11 12 +{{toc/}} 12 12 13 13 14 14 ... ... @@ -16,21 +16,35 @@ 16 16 17 17 = 1. Introduction = 18 18 20 + 19 19 == 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 26 +((( 24 24 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*. 28 +))) 25 25 30 +((( 26 26 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 +))) 27 27 34 +((( 28 28 N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 36 +))) 29 29 38 +((( 30 30 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 +))) 31 31 42 +((( 43 + 44 +))) 32 32 46 +((( 33 33 ~* make sure you have NB-IoT coverage locally. 48 +))) 34 34 35 35 36 36 ))) ... ... @@ -53,8 +53,6 @@ 53 53 * Micro SIM card slot for NB-IoT SIM 54 54 * 8500mAh Battery for long term use 55 55 56 - 57 - 58 58 == 1.3 Specification == 59 59 60 60 ... ... @@ -74,7 +74,6 @@ 74 74 75 75 (% style="color:#037691" %)**Battery:** 76 76 77 - 78 78 * Li/SOCI2 un-chargeable battery 79 79 * Capacity: 8500mAh 80 80 * Self Discharge: <1% / Year @ 25°C ... ... @@ -81,10 +81,9 @@ 81 81 * Max continuously current: 130mA 82 82 * Max boost current: 2A, 1 second 83 83 84 - 85 - 86 86 == 1.4 Applications == 87 87 98 + 88 88 * Smart Buildings & Home Automation 89 89 * Logistics and Supply Chain Management 90 90 * Smart Metering ... ... @@ -96,15 +96,20 @@ 96 96 97 97 98 98 99 -== 1.5 Pin Definitions == 100 100 111 +== 1.5 Pin Definitions & Switch == 112 + 113 + 101 101 N95S31B use the mother board from NBSN95 which as below. 102 102 116 + 103 103 [[image:image-20220709144723-1.png]] 104 104 105 105 120 + 106 106 === 1.5.1 Jumper JP2 === 107 107 123 + 108 108 Power on Device when put this jumper. 109 109 110 110 ... ... @@ -111,14 +111,20 @@ 111 111 112 112 === 1.5.2 BOOT MODE / SW1 === 113 113 114 -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. 115 115 116 -2) Flash: work mode, device starts to work and send out console output for further debug 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 +))) 117 117 135 +((( 136 +**2) Flash:** work mode, device starts to work and send out console output for further debug 137 +))) 118 118 119 119 140 + 120 120 === 1.5.3 Reset Button === 121 121 143 + 122 122 Press to reboot the device. 123 123 124 124 ... ... @@ -125,16 +125,18 @@ 125 125 126 126 === 1.5.4 LED === 127 127 150 + 128 128 It will flash: 129 129 130 -1. When boot the device in flash mode 131 -1. Send an uplink packet 153 +1. When boot the device in flash mode 132 132 155 +2. Send an uplink packet 133 133 134 134 135 135 136 136 = 2. Use N95S31B to communicate with IoT Server = 137 137 161 + 138 138 == 2.1 How it works == 139 139 140 140 ... ... @@ -151,7 +151,7 @@ 151 151 152 152 ))) 153 153 154 -[[image:1657 350248151-650.png]]178 +[[image:1657520100595-569.png]] 155 155 156 156 ((( 157 157 ... ... @@ -166,27 +166,61 @@ 166 166 167 167 [[image:image-20220709150546-2.png]] 168 168 193 + 194 + 169 169 === 2.2.1 Test Requirement === 170 170 197 + 171 171 ((( 172 -To use N DDS75 in your city, make sure meet below requirements:199 +To use N95S31B in your city, make sure meet below requirements: 173 173 ))) 174 174 175 -* Your local operator has already distributed a NB-IoT Network there. 176 -* The local NB-IoT network used the band that NSE01 supports. 177 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 202 +* ((( 203 +Your local operator has already distributed a NB-IoT Network there. 204 +))) 205 +* ((( 206 +The local NB-IoT network used the band that N95S31B supports. 207 +))) 208 +* ((( 209 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 210 +))) 178 178 179 179 ((( 180 -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 server213 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 181 181 ))) 182 182 216 +((( 217 +N95S31B supports different communication protocol such as : 218 +))) 183 183 184 -[[image:1657328756309-230.png]] 220 +((( 221 +* ((( 222 +CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 223 +))) 224 +* ((( 225 +raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 226 +))) 227 +* ((( 228 +MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 229 +))) 230 +* ((( 231 +TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 232 +))) 185 185 234 +((( 235 +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. 236 +))) 186 186 238 + 239 +))) 187 187 188 - ===2.2.2 Insert SIM card ===241 +[[image:1657350625843-586.png]] 189 189 243 + 244 + 245 +=== 2.2.3 Insert SIM card === 246 + 247 + 190 190 ((( 191 191 Insert the NB-IoT Card get from your provider. 192 192 ))) ... ... @@ -196,29 +196,33 @@ 196 196 ))) 197 197 198 198 199 -[[image:165732 8884227-504.png]]257 +[[image:1657351240556-536.png]] 200 200 201 201 202 202 203 -=== 2.2. 3DDS75 to configure it ===261 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 204 204 263 + 205 205 ((( 206 206 ((( 207 -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 +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. 267 + 268 + 208 208 ))) 209 209 ))) 210 210 211 -[[image: image-20220709092052-2.png]]272 +[[image:1657351312545-300.png]] 212 212 213 -**Connection:** 214 214 215 - background-color:yellow" %)USB TTL GND <~-~-~-~-> GND275 +(% style="color:blue" %)**Connection:** 216 216 217 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~->UART_RXD277 + (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 218 218 219 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD279 +**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 220 220 281 +**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 221 221 283 + 222 222 In the PC, use below serial tool settings: 223 223 224 224 * Baud: (% style="color:green" %)**9600** ... ... @@ -228,22 +228,24 @@ 228 228 * Flow Control: (% style="color:green" %)**None** 229 229 230 230 ((( 231 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75.DDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.293 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 232 232 ))) 233 233 234 234 [[image:1657329814315-101.png]] 235 235 298 + 236 236 ((( 237 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dr agino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]300 +(% 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]]** 238 238 ))) 239 239 240 240 241 241 242 -=== 2.2. 4305 +=== 2.2.5 Use CoAP protocol to uplink data === 243 243 244 -(% 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/]] 245 245 308 +(% 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/]]** 246 246 310 + 247 247 ((( 248 248 **Use below commands:** 249 249 ))) ... ... @@ -252,17 +252,19 @@ 252 252 (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 253 253 ))) 254 254 * ((( 255 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 319 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 256 256 ))) 257 257 * ((( 258 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 322 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 259 259 ))) 260 260 261 261 ((( 326 + 327 + 262 262 For parameter description, please refer to AT command set 263 263 ))) 264 264 265 -[[image:16573 30452568-615.png]]331 +[[image:1657352146020-183.png]] 266 266 267 267 268 268 ((( ... ... @@ -269,11 +269,11 @@ 269 269 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. 270 270 ))) 271 271 272 -[[image:16573 30472797-498.png]]338 +[[image:1657352185396-303.png]] 273 273 274 274 275 275 276 -=== 2.2. 5342 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 277 277 278 278 279 279 * (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink ... ... @@ -280,109 +280,119 @@ 280 280 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 281 281 * (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 282 282 283 -[[image:16573 30501006-241.png]]349 +[[image:1657352391268-297.png]] 284 284 285 285 286 -[[image:16573 30533775-472.png]]352 +[[image:1657352403317-397.png]] 287 287 288 288 289 289 290 -=== 2.2. 6356 +=== 2.2.7 Use MQTT protocol to uplink data === 291 291 292 292 293 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 294 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 295 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 296 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 297 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 298 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 299 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 359 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 300 300 301 -[[image:1657249978444-674.png]] 361 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 362 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 363 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 364 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 365 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 366 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/ Set the sending topic of MQTT 367 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/ Set the subscription topic of MQTT 302 302 369 +[[image:1657352634421-276.png]] 303 303 304 -[[image:1657330723006-866.png]] 305 305 372 +[[image:1657352645687-385.png]] 306 306 374 + 307 307 ((( 308 - MQTT protocolhas amuch higherpowerconsumptioncomparevsUDP / CoAPprotocol.Pleasecheckthe power analyzedocument and adjustthe uplinkperiodto asuitable interval.376 +To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period. 309 309 ))) 310 310 311 311 380 +((( 381 +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. 382 +))) 312 312 313 -=== 2.2.7 Use TCP protocol to uplink data === 314 314 315 315 386 +=== 2.2.8 Use TCP protocol to uplink data === 387 + 388 + 389 +This feature is supported since firmware version v110 390 + 316 316 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 317 317 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 318 318 319 -[[image: image-20220709093918-1.png]]394 +[[image:1657352898400-901.png]] 320 320 321 321 322 -[[image: image-20220709093918-2.png]]397 +[[image:1657352914475-252.png]] 323 323 324 324 325 325 326 -=== 2.2. 8401 +=== 2.2.9 Change Update Interval === 327 327 403 + 328 328 User can use below command to change the (% style="color:green" %)**uplink interval**. 329 329 330 330 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 331 331 332 332 ((( 333 - (%style="color:red" %)**NOTE:**409 + 334 334 ))) 335 335 336 336 ((( 337 -(% style="color:red" %) 1.By default, thedevicewillsend an uplinkmessageevery1hour.413 +(% style="color:red" %)**NOTE: Since firmware version is v1.2:** 338 338 ))) 339 339 416 +((( 417 +(% 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).** 418 +))) 340 340 341 341 421 + 342 342 == 2.3 Uplink Payload == 343 343 344 -In this mode, uplink payload includes in total 14 bytes 345 345 425 +((( 426 +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. 427 +))) 346 346 347 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 348 -|=(% style="width: 60px;" %)((( 349 -**Size(bytes)** 350 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 351 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 352 352 353 353 ((( 354 - If we use the MQTT client tosubscribeto this MQTT topic, wecan see the following information when the NDDS751 uplink data.431 +For example: 355 355 ))) 356 356 434 +((( 435 + (% 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. 436 +))) 357 357 358 -[[image:1657331036973-987.png]] 359 359 360 360 ((( 361 -The payload is ASCIIstring,representative sameHEX:440 +The uplink payloads are composed in ASCII String. For example: 362 362 ))) 363 363 364 364 ((( 365 -0 x72403155615900640c6c19029200where:444 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 366 366 ))) 367 367 368 - *(((369 - DeviceID:0x724031556159=724031556159447 +((( 448 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 370 370 ))) 371 -* ((( 372 -Version: 0x0064=100=1.0.0 450 + 451 + 452 +((( 453 +(% style="color:red" %)**NOTE:** 373 373 ))) 374 374 375 -* ((( 376 -BAT: 0x0c6c = 3180 mV = 3.180V 456 +(% style="color:red" %) 457 +1. ((( 458 +**All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].** 377 377 ))) 378 -* ((( 379 -Signal: 0x19 = 25 380 -))) 381 -* ((( 382 -Distance: 0x0292= 658 mm 383 -))) 384 -* ((( 385 -Interrupt: 0x00 = 0 460 +1. ((( 461 +**By default, the device will send an uplink message every 1 hour.** 386 386 387 387 388 388 ... ... @@ -389,105 +389,190 @@ 389 389 390 390 ))) 391 391 392 -== 2. 4PayloadExplanation and SensorInterface==468 +=== 2.3.1 Payload Analyze === 393 393 394 394 395 -=== 2. 4.1DeviceID===471 +==== 2.3.1.1 Before Firmware v1.2 ==== 396 396 473 + 474 +N95S31B uplink payload includes in total 21 bytes 475 + 476 + 477 +(% border="1" cellspacing="0" style="background-color:#ffffcc; color:green; width:520px" %) 478 +|(% style="width:50px" %)((( 479 +**Size(bytes)** 480 +)))|=(% style="width: 40px;" %)**6**|=(% style="width: 20px;" %)2|=(% style="width: 20px;" %)**2**|=(% style="width: 60px;" %)**1**|=(% style="width: 50px;" %)1|=(% style="width: 100px;" %)5|=(% style="width: 100px;" %)**2**|=(% style="width: 100px;" %)**2** 481 +|(% 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:162px" %)((( 397 397 ((( 398 - By default, theDeviceID equal to thelast6bytes of IMEI.483 +Reserve/ Same as NBSN95 CFGMOD=1 399 399 ))) 400 400 401 401 ((( 402 - Usercanuse (% style="color:blue" %)**AT+DEUI**(%%)toset Device ID487 +No function here. 403 403 ))) 489 +)))|(% style="width:102px" %)((( 490 +((( 491 +[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]] 492 +))) 404 404 405 405 ((( 406 - **Example:**495 +By SHT31 407 407 ))) 497 +)))|(% style="width:81px" %)((( 498 +((( 499 +[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]] 500 +))) 408 408 409 409 ((( 410 - AT+DEUI=A84041F15612503 +By SHT31 411 411 ))) 505 +))) 412 412 413 413 ((( 414 -The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID. 508 + 509 + 510 +((( 511 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 415 415 ))) 513 +))) 416 416 417 417 516 +[[image:1657354294009-643.png]] 418 418 419 -=== 2.4.2 Version Info === 420 420 421 -((( 422 -Specify the software version: 0x64=100, means firmware version 1.00. 423 -))) 519 +The payload is ASCII string, representative same HEX: (% style="background-color:yellow" %)**0x724031607457 006e 0ccd 1b 01 00dc000ccc 00e1 0186** 424 424 425 -((( 426 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 427 -))) 521 +**where:** 428 428 523 +* (% style="color:#037691" %)**Device ID:** (%%) 0x724031607457 = 724031607457 429 429 525 +* (% style="color:#037691" %)**Version: **(%%) 0x006e=110=1.1.0 430 430 431 - ===2.4.3BatteryInfo===527 +* (% style="color:#037691" %)**BAT:** (%%) 0x0ccd = 3277 mV = 3.277V 432 432 433 -((( 434 -Ex1: 0x0B45 = 2885mV 435 -))) 529 +* (% style="color:#037691" %)**Signal:** (%%) 0x1b = 27 436 436 437 -((( 438 -Ex2: 0x0B49 = 2889mV 439 -))) 531 +* (% style="color:#037691" %)**Model:** (%%) 0x01 = 1 440 440 533 +* (% style="color:#037691" %)**0x00dc000ccc= reserve, ignore in N95S31B** 441 441 535 +* (% style="color:#037691" %)**Temperature by SHT31:** (%%) 0x00e1 = 225 = 22.5 °C 442 442 443 - ===2.4.4SignalStrength===537 +* (% style="color:#037691" %)**Humidity by SHT31:** (%%) 0x0186 = 390 = 39.0 %rh 444 444 445 445 ((( 446 -NB-IoT Network signal Strength. 447 -))) 540 + 448 448 449 - (((450 - **Ex1:0x1d = 29**542 + 543 + 451 451 ))) 452 452 546 +==== 2.3.1.2 Since Firmware v1.2 ==== 547 + 548 + 549 +In this mode, uplink payload includes 91 bytes in total by default. 550 + 551 +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. 552 + 553 + 554 +(% border="1" style="background-color:#ffffcc; color:green; width:520px" %) 555 +|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:50px" %)**2**|(% style="width:50px" %)**1**|(% style="width:30px" %)**2**|(% style="width:50px" %)**2**|(% style="width:50px" %)**2**|(% style="width:30px" %)**4**|(% style="width:30px" %)**2**|(% style="width:30px" %)**2**|(% style="width:30px" %)**4** 556 +|=(% style="width: 95px;" %)**Value**|(% style="width:82px" %)Device ID|(% style="width:43px" %)Ver|(% style="width:47px" %)BAT|(% style="width:124px" %)Signal Strength|(% style="width:56px" %)MOD|(% style="width:109px" %)TemDS18B20|(% style="width:80px" %)Interrupt|(% style="width:51px" %)ADC|(% style="width:79px" %)SHTTEM|(% style="width:84px" %)SHTHUM|(% style="width:100px" %)Time stamp |(% style="width:76px" %)SHTTEM|(% style="width:81px" %)SHTHUM|(% style="width:121px" %)Time stamp ..... 557 + 558 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data. 559 + 560 + 561 +[[image:image-20220908154949-1.png]] 562 + 563 + 564 +The payload is ASCII string, representative same HEX: 565 + 566 +**0x (% style="color:red" %)__f868411056758782__ (% style="color:blue" %)__000c__ (% style="color:green" %)__0d0f__ (% style="color:#00b0f0" %)__0c__ (% style="color:#7030a0" %)__01__ (% style="color:#d60093" %)__0000__ (% style="color:#a14d07" %)__00__ __0030__ (% style="color:#0020b0" %)__0114__ (% style="color:#420042" %)__0231__ (% style="color:#663300" %)__63199d3c__ (%%)__0113023163199d12__ __0113023163199c5e__// //__0112023763199baa__ __0112023263199af6__// //__0111023b631999a7__ ** 567 + 568 +**__0112023b631998f3__// //__011202426319983f__ __01110242631996eb__** 569 + 570 +**where:** 571 + 572 +* (% style="color:#037691" %)**Device ID:**(%%) f868411056758782 = f868411056758782 573 + 574 +* (% style="color:#037691" %)**Version:** (%%)0x000c=120=1.2 575 + 576 +* (% style="color:#037691" %)**BAT:** (%%)0x0d0f = 3343 mV = 3.343V 577 + 578 +* (% style="color:#037691" %)**Singal:**(%%) 0x0c = 12 579 + 580 +* (% style="color:#037691" %)**Mod:**(%%) 0x01 = 1 581 + 582 +* (% style="color:#037691" %)**TemDS18B20:**(%%) 0x0000= 0 = 0 583 + 584 +* (% style="color:#037691" %)**Interrupt:** (%%)0x00= 0 585 + 586 +* (% style="color:#037691" %)**adc:**(%%) 0x0030= 48 587 + 588 +* (% style="color:#037691" %)**SHTTEM:**(%%) 0x0114= 276 = 27.6 589 + 590 +* (% style="color:#037691" %)**SHTHUM:**(%%) 0x0231 =561=56.1% 591 + 592 +* (% style="color:#037691" %)**Time stamp : **(%%)0x63199d3c =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 593 + 594 +* (% style="color:#037691" %)**SHTTEM,SHTHUM,Time stamp :**(%%) 0113023163199d12 595 + 596 +* (% style="color:#037691" %)**8 sets of recorded data:**(%%)** **SHTTEM,SHTHUM,Time stamp : 0113023163199c5e, ....... 597 + 598 +=== 2.3.2 Device ID === 599 + 600 + 453 453 ((( 454 - (% style="color:blue"%)**0**(%%)-113dBmorless602 +By default, the Device ID equal to the last 6 bytes of IMEI. 455 455 ))) 456 456 457 457 ((( 458 -(% style="color:blue" %)**1**(%%) -111dBm 606 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 607 + 608 + 459 459 ))) 460 460 461 461 ((( 462 -(% style="color:blue" %)** 2...30**(%%) -109dBm... -53dBm612 +(% style="color:blue" %)**Example:** 463 463 ))) 464 464 465 465 ((( 466 - (% style="color:blue" %)**31** (%%) -51dBm or greater616 +AT+DEUI=A84041F15612 467 467 ))) 468 468 469 469 ((( 470 -(% style="color:blue" %)**99** (%%) Not known or not detectable 620 +The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID. 621 + 622 + 471 471 ))) 472 472 625 +(% style="color:red" %)**NOTE: When the firmware version is v1.2 and later firmware:** 473 473 474 474 475 - ===2.4.5Distance===628 +By default, the Device ID equal to the last 15 bits of IMEI. 476 476 477 - Getthedistance.Flatbjectrange280mm - 7500mm.630 +User can use ** (% style="color:blue" %)AT+DEUI(%%)** to set Device ID 478 478 632 + 633 +(% style="color:blue" %)**Example:** 634 + 635 +AT+DEUI=868411056754138 636 + 637 + 638 + 639 +=== 2.3.3 Version Info === 640 + 641 + 479 479 ((( 480 - Forexample,if the datayou getfrom theregisteris **__0x0B 0x05__**, the distancebetweenthesensorand the measuredobject is643 +These bytes include the hardware and software version. 481 481 ))) 482 482 483 483 ((( 484 -((( 485 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 647 +Higher byte: Specify hardware version: always 0x00 for N95S31B 486 486 ))) 487 -))) 488 488 489 489 ((( 490 - 651 +Lower byte: Specify the software version: 0x6E=110, means firmware version 110 491 491 ))) 492 492 493 493 ((( ... ... @@ -494,65 +494,85 @@ 494 494 495 495 ))) 496 496 497 -=== 2.4.6 Digital Interrupt === 498 - 499 499 ((( 500 - Digital Interruptrefers topin (% style="color:blue"%)**GPIO_EXTI**(%%),andtherearedifferent triggermethods. When thereisa trigger, theNDDS75 will send a packetto theserver.659 +For example: 0x00 6E: this device is N95S31B with firmware version 110. 501 501 ))) 502 502 503 503 ((( 504 - Thecommand is:663 + 505 505 ))) 506 506 666 + 667 +=== 2.3.4 Battery Info === 668 + 669 + 507 507 ((( 508 - (% 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]])**.**671 +Ex1: 0x0B45 = 2885mV 509 509 ))) 510 510 511 - 512 512 ((( 513 - Thelowerfourbits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.675 +Ex2: 0x0B49 = 2889mV 514 514 ))) 515 515 516 516 679 + 680 +=== 2.3.5 Signal Strength === 681 + 682 + 517 517 ((( 518 - Example:684 +NB-IoT Network signal Strength. 519 519 ))) 520 520 521 521 ((( 522 - 0x(00):Normaluplinkpacket.688 +**Ex1: 0x1d = 29** 523 523 ))) 524 524 525 525 ((( 526 - 0x(01):InterruptUplinkPacket.692 +(% style="color:blue" %)**0**(%%) -113dBm or less 527 527 ))) 528 528 529 - 530 - 531 -=== 2.4.7 +5V Output === 532 - 533 533 ((( 534 - NDDS75willenable +5Voutputbeforeallsamplinganddisablethe+5vafterall sampling.696 +(% style="color:blue" %)**1**(%%) -111dBm 535 535 ))) 536 536 537 - 538 538 ((( 539 - The5V output timean be controlledbyAT Command.700 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 540 540 ))) 541 541 542 542 ((( 543 -(% style="color:blue" %)** AT+5VT=1000**704 +(% style="color:blue" %)**31** (%%) -51dBm or greater 544 544 ))) 545 545 546 546 ((( 547 - Meansset5V valid timetohave 1000ms. Sothereal5V outputwillactuallyhave1000ms+samplingtime for othersensors.708 +(% style="color:blue" %)**99** (%%) Not known or not detectable 548 548 ))) 549 549 550 550 551 551 552 -== 2. 5Downlink Payload ==713 +=== 2.3.6 Temperature & Humidity === 553 553 554 -By default, NDDS75 prints the downlink payload to console port. 555 555 716 +The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server. 717 + 718 +[[image:image-20220709161741-3.png]] 719 + 720 + 721 +Convert the read byte to decimal and divide it by ten. 722 + 723 + 724 +**Example:** 725 + 726 +Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃ 727 + 728 +Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1% 729 + 730 + 731 + 732 +== 2.4 Downlink Payload == 733 + 734 + 735 +By default, N95S31B prints the downlink payload to console port. 736 + 556 556 [[image:image-20220709100028-1.png]] 557 557 558 558 ... ... @@ -589,7 +589,7 @@ 589 589 ))) 590 590 591 591 ((( 592 -If payload = 0x04FF, it will reset the DDS75773 +If payload = 0x04FF, it will reset the N95S31B 593 593 ))) 594 594 595 595 ... ... @@ -601,48 +601,76 @@ 601 601 602 602 603 603 604 -== 2. 6LEDIndicator ==785 +== 2.5 Humidity and Temperature alarm function == 605 605 606 606 607 - TheNDDS75hasan internalLED which is toshow thestatusofdifferent state.788 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 608 608 609 609 610 -* 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) 611 -* Then the LED will be on for 1 second means device is boot normally. 612 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 613 -* For each uplink probe, LED will be on for 500ms. 791 +(% style="color:#037691" %)**AT+ SHHUM=min,max** 614 614 615 -((( 616 - 617 -))) 618 618 794 +² When min=0, and max≠0, Alarm higher than max 619 619 796 +² When min≠0, and max=0, Alarm lower than min 620 620 621 - ==2.7FirmwareChangeLog==798 +² When min≠0 and max≠0, Alarm higher than max or lower than min 622 622 623 623 624 -((( 625 -Download URL & Firmware Change log 626 -))) 801 + (% style="color:blue" %)**Example:** 627 627 628 -((( 629 -[[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/]] 630 -))) 803 +AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50. 631 631 632 632 633 -((( 634 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 635 -))) 806 +(% style="color:#037691" %)**AT+ SHTEMP=min,max** 636 636 808 +² When min=0, and max≠0, Alarm higher than max 637 637 810 +² When min≠0, and max=0, Alarm lower than min 638 638 812 +² When min≠0 and max≠0, Alarm higher than max or lower than min 813 + 814 + 815 +**~ (% style="color:blue" %)Example:(%%)** 816 + 817 +AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20. 818 + 819 + 820 + 821 +== 2.6 Set the number of data to be uploaded and the recording time == 822 + 823 + 824 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 825 + 826 +* (% style="color:#037691" %)**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) 827 +* (% style="color:#037691" %)**AT+NOUD=8** (%%)~/~/ The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded. 828 + 829 + The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 830 + 831 +[[image:image-20221009001045-1.png||height="726" width="1009"]] 832 + 833 + 834 + 835 +== 2.7 Read or Clear cached data == 836 + 837 + 838 +**~ (% style="color:blue" %)➢ AT Command:(%%)** 839 + 840 +* (% style="color:#037691" %)**AT+CDP** (%%) ~/~/ Read cached data 841 +* (% style="color:#037691" %)**AT+CDP=0** (%%) ~/~/ Clear cached data 842 + 843 +[[image:image-20220908163102-2.png]] 844 + 845 + 846 + 639 639 == 2.8 Battery Analysis == 640 640 849 + 641 641 === 2.8.1 Battery Type === 642 642 643 643 644 644 ((( 645 -The N DDS75 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.854 +The N95S31B 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. 646 646 ))) 647 647 648 648 ((( ... ... @@ -665,54 +665,35 @@ 665 665 666 666 === 2.8.2 Power consumption Analyze === 667 667 668 -((( 669 -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. 670 -))) 671 671 672 - 673 673 ((( 674 -Instruction to use as below:879 +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 to analyze the power consumption in different case. User can use it for design guideline for their project. 675 675 ))) 676 676 677 677 ((( 678 - (%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/]]883 + 679 679 ))) 680 680 681 681 682 -((( 683 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 684 -))) 887 +=== 2.8.3 Battery Note === 685 685 686 -* ((( 687 -Product Model 688 -))) 689 -* ((( 690 -Uplink Interval 691 -))) 692 -* ((( 693 -Working Mode 694 -))) 695 695 696 696 ((( 697 - And the Life expectation in difference casewillbe shownon theright.891 +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 uplink data, then the battery life may be decreased. 698 698 ))) 699 699 700 -[[image:image-20220709110451-3.png]] 701 701 702 702 896 +=== 2.8.4 Replace the battery === 703 703 704 -=== 2.8.3 Battery Note === 705 705 706 706 ((( 707 - TheLi-SICObattery isdesignedfor smallcurrent/long period application.It isnotgoodtouseahigh current,shortperiodtransmitmethod.Thecommendedminimumperiodforuseofthisbatteryis5minutes. If you use ashorter period time totransmitLoRa,then the batterylifemaybe decreased.900 +You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board. 708 708 ))) 709 709 710 710 711 - 712 -=== 2.8.4 Replace the battery === 713 - 714 714 ((( 715 -The default battery pack of N DDS75 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).905 +The default battery pack of N95S31B 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). 716 716 ))) 717 717 718 718 ... ... @@ -719,6 +719,7 @@ 719 719 720 720 = 3. Access NB-IoT Module = 721 721 912 + 722 722 ((( 723 723 Users can directly access the AT command set of the NB-IoT module. 724 724 ))) ... ... @@ -725,6 +725,8 @@ 725 725 726 726 ((( 727 727 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/]] 919 + 920 + 728 728 ))) 729 729 730 730 [[image:1657333200519-600.png]] ... ... @@ -733,11 +733,13 @@ 733 733 734 734 = 4. Using the AT Commands = 735 735 929 + 736 736 == 4.1 Access AT Commands == 737 737 738 -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/]] 739 739 933 +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]] 740 740 935 + 741 741 AT+<CMD>? : Help on <CMD> 742 742 743 743 AT+<CMD> : Run <CMD> ... ... @@ -777,7 +777,24 @@ 777 777 778 778 AT+SERVADDR : Server Address 779 779 975 +AT+TR : Get or Set record time 780 780 977 +AT+APN : Get or set the APN 978 + 979 +AT+FBAND : Get or Set whether to automatically modify the frequency band 980 + 981 +AT+DNSCFG : Get or Set DNS Server 982 + 983 +AT+GETSENSORVALUE : Returns the current sensor measurement 984 + 985 +AT+NOUD : Get or Set the number of data to be uploaded 986 + 987 +AT+CDP : Read or Clear cached data 988 + 989 +AT+SHTEMP: Get or Set alarm of temp 990 + 991 +AT+SHHUM: Get or Set alarm of moisture 992 + 781 781 (% style="color:#037691" %)**COAP Management** 782 782 783 783 AT+URI : Resource parameters ... ... @@ -811,6 +811,7 @@ 811 811 812 812 = 5. FAQ = 813 813 1026 + 814 814 == 5.1 How to Upgrade Firmware == 815 815 816 816 ... ... @@ -823,13 +823,18 @@ 823 823 ))) 824 824 825 825 ((( 826 -(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update. 1039 + 1040 + 1041 +((( 1042 +(% style="color:red" %)**Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.** 827 827 ))) 1044 +))) 828 828 829 829 830 830 831 831 = 6. Trouble Shooting = 832 832 1050 + 833 833 == 6.1 Connection problem when uploading firmware == 834 834 835 835 ... ... @@ -845,6 +845,7 @@ 845 845 846 846 == 6.2 AT Command input doesn't work == 847 847 1066 + 848 848 ((( 849 849 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. 850 850 ... ... @@ -855,7 +855,7 @@ 855 855 = 7. Order Info = 856 856 857 857 858 -Part Number**:** (% style="color:#4f81bd" %)**N SDDS75**1077 +Part Number**:** (% style="color:#4f81bd" %)**N95S31B-YY** 859 859 860 860 861 861 (% class="wikigeneratedid" %) ... ... @@ -870,7 +870,7 @@ 870 870 871 871 (% style="color:#037691" %)**Package Includes**: 872 872 873 -* NS E01DistanceDetectSensorNode x 11092 +* N95S31B NB-IoT Temperature and Humidity Sensor 874 874 * External antenna x 1 875 875 ))) 876 876 ... ... @@ -879,11 +879,10 @@ 879 879 880 880 (% style="color:#037691" %)**Dimension and weight**: 881 881 882 - 883 883 * Device Size: 13.0 x 5 x 4.5 cm 884 884 * Device Weight: 150g 885 -* Package Size / pcs : 1 5x12x 5.5cm886 -* Weight / pcs : 220g1103 +* Package Size / pcs : 14.0 x 8x 5 cm 1104 +* Weight / pcs : 180g 887 887 ))) 888 888 889 889 ((( ... ... @@ -895,5 +895,6 @@ 895 895 896 896 = 9. Support = 897 897 1116 + 898 898 * 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. 899 899 * 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]]
- 1657350625843-586.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.3 KB - Content
- 1657351240556-536.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657351312545-300.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +675.8 KB - Content
- 1657352146020-183.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +264.0 KB - Content
- 1657352185396-303.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +98.3 KB - Content
- 1657352391268-297.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +238.0 KB - Content
- 1657352403317-397.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +547.7 KB - Content
- 1657352634421-276.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +163.6 KB - Content
- 1657352645687-385.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657352898400-901.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +144.8 KB - Content
- 1657352914475-252.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +157.0 KB - Content
- 1657354294009-643.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +214.7 KB - Content
- 1657520100595-569.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content
- image-20220908154949-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +58.5 KB - Content
- image-20220908163102-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +29.7 KB - Content
- image-20221009001045-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Edwin - Size
-
... ... @@ -1,0 +1,1 @@ 1 +282.9 KB - Content