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, 18 added, 0 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
- image-20220709144723-1.png
- image-20220709150546-2.png
- image-20220709161741-3.png
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -N DDS75 NB-IoTDistanceDetect Sensor User Manual1 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual - Content
-
... ... @@ -1,63 +1,59 @@ 1 1 (% style="text-align:center" %) 2 -[[image: image-20220709085040-1.png||height="542" width="524"]]2 +[[image:1657348034241-728.png||height="470" width="470"]] 3 3 4 4 5 5 6 6 7 7 8 -**Table of Contents:** 9 9 10 -{{toc/}} 11 11 10 +**Table of Contents:** 12 12 13 13 14 14 15 15 16 16 16 + 17 17 = 1. Introduction = 18 18 19 -== 1.1 What is N DDS75Distance DetectionSensor ==19 +== 1.1 What is N95S31B NB-IoT Sensor Node == 20 20 21 21 ((( 22 22 23 23 24 -((( 25 -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. 26 -\\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. 27 -\\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. 28 -\\NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 29 -\\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) 30 -\\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. 31 -))) 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*. 32 32 33 - 34 -))) 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. 35 35 36 - [[image:1654503236291-817.png]]28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement. 37 37 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). 38 38 39 -[[image:1657327959271-447.png]] 40 40 33 +~* make sure you have NB-IoT coverage locally. 41 41 35 + 36 +))) 42 42 38 +[[image:1657348284168-431.png]] 39 + 40 + 41 + 43 43 == 1.2 Features == 44 44 45 45 46 46 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 47 -* Ultra low power consumption 48 -* Distance Detection by Ultrasonic technology 49 -* Flat object range 280mm - 7500mm 50 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 51 -* Cable Length: 25cm 46 +* Monitor Temperature & Humidity via SHT31 52 52 * AT Commands to change parameters 53 53 * Uplink on periodically 54 54 * Downlink to change configure 55 55 * IP66 Waterproof Enclosure 51 +* Ultra-Low Power consumption 52 +* AT Commands to change parameters 56 56 * Micro SIM card slot for NB-IoT SIM 57 57 * 8500mAh Battery for long term use 58 58 59 59 60 - 61 61 == 1.3 Specification == 62 62 63 63 ... ... @@ -77,6 +77,7 @@ 77 77 78 78 (% style="color:#037691" %)**Battery:** 79 79 76 + 80 80 * Li/SOCI2 un-chargeable battery 81 81 * Capacity: 8500mAh 82 82 * Self Discharge: <1% / Year @ 25°C ... ... @@ -83,13 +83,7 @@ 83 83 * Max continuously current: 130mA 84 84 * Max boost current: 2A, 1 second 85 85 86 -(% style="color:#037691" %)**Power Consumption** 87 87 88 -* STOP Mode: 10uA @ 3.3v 89 -* Max transmit power: [[350mA@3.3v>>mailto:350mA@3.3v]] 90 - 91 - 92 - 93 93 == 1.4 Applications == 94 94 95 95 * Smart Buildings & Home Automation ... ... @@ -105,22 +105,52 @@ 105 105 106 106 == 1.5 Pin Definitions == 107 107 99 +N95S31B use the mother board from NBSN95 which as below. 108 108 109 -[[image: 1657328609906-564.png]]101 +[[image:image-20220709144723-1.png]] 110 110 111 111 104 +=== 1.5.1 Jumper JP2 === 112 112 113 - = 2. UseNDDS75 tocommunicate withIoTServer =106 +Power on Device when put this jumper. 114 114 108 + 109 + 110 +=== 1.5.2 BOOT MODE / SW1 === 111 + 112 +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. 113 + 114 +2) Flash: work mode, device starts to work and send out console output for further debug 115 + 116 + 117 + 118 +=== 1.5.3 Reset Button === 119 + 120 +Press to reboot the device. 121 + 122 + 123 + 124 +=== 1.5.4 LED === 125 + 126 +It will flash: 127 + 128 +1. When boot the device in flash mode 129 +1. Send an uplink packet 130 + 131 + 132 + 133 += 2. Use N95S31B to communicate with IoT Server = 134 + 115 115 == 2.1 How it works == 116 116 137 + 117 117 ((( 118 -The N DDS75 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.139 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B. 119 119 ))) 120 120 121 121 122 122 ((( 123 -The diagram below shows the working flow in default firmware of N DDS75:144 +The diagram below shows the working flow in default firmware of N95S31B: 124 124 ))) 125 125 126 126 ((( ... ... @@ -127,7 +127,7 @@ 127 127 128 128 ))) 129 129 130 -[[image:1657328 659945-416.png]]151 +[[image:1657350248151-650.png]] 131 131 132 132 ((( 133 133 ... ... @@ -134,30 +134,45 @@ 134 134 ))) 135 135 136 136 137 -== 2.2 Configure the N DDS75 ==158 +== 2.2 Configure the N95S31B == 138 138 139 139 161 +=== 2.2.1 Power On N95S31B === 162 + 163 + 164 +[[image:image-20220709150546-2.png]] 165 + 166 + 140 140 === 2.2.1 Test Requirement === 141 141 142 -((( 143 -To use NDDS75 in your city, make sure meet below requirements: 144 -))) 145 145 170 +To use N95S31B in your city, make sure meet below requirements: 171 + 146 146 * Your local operator has already distributed a NB-IoT Network there. 147 -* The local NB-IoT network used the band that NS E01 supports.173 +* The local NB-IoT network used the band that N95S31B supports. 148 148 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 149 149 176 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. 177 + 178 +N95S31B supports different communication protocol such as : 179 + 150 150 ((( 151 -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 152 -))) 181 +* CoAP ((% style="color:red" %)120.24.4.116:5683(%%)) 182 +* raw UDP ((% style="color:red" %)120.24.4.116:5601(%%)) 183 +* MQTT ((% style="color:red" %)120.24.4.116:1883(%%)) 184 +* TCP ((% style="color:red" %)120.24.4.116:5600(%%)) 153 153 186 +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. 154 154 155 -[[image:1657328756309-230.png]] 188 + 189 +))) 156 156 191 +[[image:1657350625843-586.png]] 157 157 158 158 159 -=== 2.2.2 Insert SIM card === 160 160 195 +=== 2.2.3 Insert SIM card === 196 + 161 161 ((( 162 162 Insert the NB-IoT Card get from your provider. 163 163 ))) ... ... @@ -167,19 +167,19 @@ 167 167 ))) 168 168 169 169 170 -[[image:165732 8884227-504.png]]206 +[[image:1657351240556-536.png]] 171 171 172 172 173 173 174 -=== 2.2. 3DDS75 to configure it ===210 +=== 2.2.4 Connect USB – TTL to N95S31B to configure it === 175 175 176 176 ((( 177 177 ((( 178 -User need to configure DDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect toDDS75 and use AT Commands to configure it, as below.214 +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. 179 179 ))) 180 180 ))) 181 181 182 -[[image: image-20220709092052-2.png]]218 +[[image:1657351312545-300.png]] 183 183 184 184 **Connection:** 185 185 ... ... @@ -199,90 +199,110 @@ 199 199 * Flow Control: (% style="color:green" %)**None** 200 200 201 201 ((( 202 -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.238 +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. 203 203 ))) 204 204 205 205 [[image:1657329814315-101.png]] 206 206 207 207 ((( 208 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N DDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]244 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] 209 209 ))) 210 210 211 211 212 212 213 -=== 2.2. 4249 +=== 2.2.5 Use CoAP protocol to uplink data === 214 214 215 215 (% 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/]] 216 216 217 217 254 +((( 218 218 **Use below commands:** 256 +))) 219 219 220 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 221 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 222 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 258 +* ((( 259 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 260 +))) 261 +* ((( 262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 263 +))) 264 +* ((( 265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 266 +))) 223 223 268 +((( 269 + 270 + 224 224 For parameter description, please refer to AT command set 272 +))) 225 225 226 -[[image:16573 30452568-615.png]]274 +[[image:1657352146020-183.png]] 227 227 228 228 277 +((( 229 229 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. 279 +))) 230 230 231 -[[image:16573 30472797-498.png]]281 +[[image:1657352185396-303.png]] 232 232 233 233 234 234 235 -=== 2.2. 5285 +=== 2.2.6 Use UDP protocol to uplink data(Default protocol) === 236 236 237 237 238 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 288 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 239 239 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 240 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 290 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 241 241 242 -[[image:16573 30501006-241.png]]292 +[[image:1657352391268-297.png]] 243 243 244 244 245 -[[image:16573 30533775-472.png]]295 +[[image:1657352403317-397.png]] 246 246 247 247 248 248 249 -=== 2.2. 6299 +=== 2.2.7 Use MQTT protocol to uplink data === 250 250 301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption. 251 251 252 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 253 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 254 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 255 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 256 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 257 -* (% style="color:blue" %)**AT+PUBTOPIC= NDDS75_PUB**(%%)~/~/Set the sending topic of MQTT258 -* (% style="color:blue" %)**AT+SUBTOPIC=N DDS75_SUB**(%%) ~/~/Set the subscription topic of MQTT303 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 304 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 305 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 306 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 307 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 308 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527 **(%%)~/~/Set the sending topic of MQTT 309 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527 **(%%) ~/~/Set the subscription topic of MQTT 259 259 260 -[[image:165724 9978444-674.png]]311 +[[image:1657352634421-276.png]] 261 261 262 262 263 -[[image:16573 30723006-866.png]]314 +[[image:1657352645687-385.png]] 264 264 316 +((( 317 +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. 318 +))) 265 265 320 + 266 266 ((( 267 -MQTT protocol has a much high erpower consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.322 +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. 268 268 ))) 269 269 270 270 271 271 272 -=== 2.2. 7327 +=== 2.2.8 Use TCP protocol to uplink data === 273 273 329 +This feature is supported since firmware version v110 274 274 275 275 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 276 276 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 277 277 278 -[[image: image-20220709093918-1.png]]334 +[[image:1657352898400-901.png]] 279 279 280 280 281 -[[image: image-20220709093918-2.png]]337 +[[image:1657352914475-252.png]] 282 282 283 283 284 284 285 -=== 2.2. 8341 +=== 2.2.9 Change Update Interval === 286 286 287 287 User can use below command to change the (% style="color:green" %)**uplink interval**. 288 288 ... ... @@ -289,32 +289,69 @@ 289 289 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 290 290 291 291 ((( 292 - (%style="color:red" %)**NOTE:**348 + 293 293 ))) 294 294 295 -((( 296 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 297 -))) 298 298 299 299 300 - 301 301 == 2.3 Uplink Payload == 302 302 303 -In this mode, uplink payload includes in total 14 bytes 304 304 356 +NBSN95 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. 305 305 306 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 307 -|=(% style="width: 80px;" %)((( 358 + 359 +For example: 360 + 361 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor. 362 + 363 + 364 +The uplink payloads are composed in ASCII String. For example: 365 + 366 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload: 367 + 368 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes 369 + 370 + 371 +(% style="color:red" %)**NOTE:** 372 + 373 +(% style="color:red" %) 374 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]]. 375 +1. By default, the device will send an uplink message every 1 hour. 376 + 377 + 378 + 379 + 380 +=== 2.3.1 Payload Analyze === 381 + 382 +N95S31B uplink payload includes in total 21 bytes 383 + 384 + 385 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 386 +|=(% style="width: 60px;" %)((( 308 308 **Size(bytes)** 309 -)))|=(% style="width: 80px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 110px;" %)**1**|=(% style="width: 110px;" %)**2**|=(% style="width: 70px;" %)**1** 310 -|(% 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"]] 388 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1** 389 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)((( 390 +Reserve/ Same as NBSN95 CFGMOD=1 311 311 392 +No function here. 393 +)))|(% style="width:77px" %)((( 394 +[[Temperature >>||anchor="H2.4.5A0Distance"]] 395 + 396 +By SHT31 397 +)))|(% style="width:80px" %)((( 398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]] 399 + 400 +By SHT31 401 +))) 402 + 312 312 ((( 313 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 404 +((( 405 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data. 314 314 ))) 407 +))) 315 315 316 316 317 -[[image:16573 31036973-987.png]]410 +[[image:1657354294009-643.png]] 318 318 319 319 ((( 320 320 The payload is ASCII string, representative same HEX: ... ... @@ -390,10 +390,6 @@ 390 390 === 2.4.3 Battery Info === 391 391 392 392 ((( 393 -Check the battery voltage for LSE01. 394 -))) 395 - 396 -((( 397 397 Ex1: 0x0B45 = 2885mV 398 398 ))) 399 399 ... ... @@ -439,7 +439,9 @@ 439 439 440 440 Get the distance. Flat object range 280mm - 7500mm. 441 441 531 +((( 442 442 For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 533 +))) 443 443 444 444 ((( 445 445 ((( ... ... @@ -582,7 +582,9 @@ 582 582 == 2.7 Firmware Change Log == 583 583 584 584 676 +((( 585 585 Download URL & Firmware Change log 678 +))) 586 586 587 587 ((( 588 588 [[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/]] ... ... @@ -589,7 +589,9 @@ 589 589 ))) 590 590 591 591 685 +((( 592 592 Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 687 +))) 593 593 594 594 595 595
- 1657348034241-728.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +127.8 KB - Content
- 1657348284168-431.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +93.5 KB - Content
- 1657350248151-650.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- 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
- image-20220709144723-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +413.1 KB - Content
- image-20220709150546-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +333.5 KB - Content
- image-20220709161741-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +111.2 KB - Content