Changes for page NDDS75 -- NB-IoT Distance Detect Sensor User Manual
Last modified by Bei Jinggeng on 2024/05/31 09:53
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 23 removed)
- 1657327959271-447.png
- 1657328609906-564.png
- 1657328659945-416.png
- 1657328756309-230.png
- 1657328884227-504.png
- 1657329814315-101.png
- 1657330452568-615.png
- 1657330472797-498.png
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- 1657332990863-496.png
- 1657333200519-600.png
- image-20220709092052-2.png
- image-20220709093918-1.png
- image-20220709093918-2.png
- image-20220709100028-1.png
- image-20220709101450-2.png
- image-20220709110451-3.png
- image-20220908175246-1.png
- image-20220908175333-2.png
- image-20221009001114-1.png
Details
- Page properties
-
- Content
-
... ... @@ -7,7 +7,6 @@ 7 7 8 8 **Table of Contents:** 9 9 10 -{{toc/}} 11 11 12 12 13 13 ... ... @@ -16,7 +16,6 @@ 16 16 17 17 = 1. Introduction = 18 18 19 - 20 20 == 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 22 ((( ... ... @@ -23,55 +23,39 @@ 23 23 24 24 25 25 ((( 26 -((( 27 27 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 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. 32 + 32 32 ))) 33 33 34 -((( 35 -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. 36 -))) 35 +[[image:1654503236291-817.png]] 37 37 38 -((( 39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 40 -))) 41 41 42 -((( 43 -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) 44 -))) 38 +[[image:1657245163077-232.png]] 45 45 46 -((( 47 -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. 48 -))) 49 -))) 50 50 51 - 52 -))) 53 53 54 -[[image:1657327959271-447.png]] 55 - 56 - 57 - 58 58 == 1.2 Features == 59 59 60 - 61 61 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 62 -* Ultra low power consumption 63 -* Distance Detection by Ultrasonic technology 64 -* Flat object range 280mm - 7500mm 65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 66 -* Cable Length: 25cm 45 +* Monitor Soil Moisture 46 +* Monitor Soil Temperature 47 +* Monitor Soil Conductivity 67 67 * AT Commands to change parameters 68 68 * Uplink on periodically 69 69 * Downlink to change configure 70 70 * IP66 Waterproof Enclosure 52 +* Ultra-Low Power consumption 53 +* AT Commands to change parameters 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 74 - 75 75 == 1.3 Specification == 76 76 77 77 ... ... @@ -82,101 +82,82 @@ 82 82 83 83 (% style="color:#037691" %)**NB-IoT Spec:** 84 84 85 -* B1 @H-FDD: 2100MHz 86 -* B3 @H-FDD: 1800MHz 87 -* B8 @H-FDD: 900MHz 88 -* B5 @H-FDD: 850MHz 89 -* B20 @H-FDD: 800MHz 90 -* B28 @H-FDD: 700MHz 67 +* - B1 @H-FDD: 2100MHz 68 +* - B3 @H-FDD: 1800MHz 69 +* - B8 @H-FDD: 900MHz 70 +* - B5 @H-FDD: 850MHz 71 +* - B20 @H-FDD: 800MHz 72 +* - B28 @H-FDD: 700MHz 91 91 92 -(% style="color:#037691" %)** Battery:**74 +Probe(% style="color:#037691" %)** Specification:** 93 93 94 -* Li/SOCI2 un-chargeable battery 95 -* Capacity: 8500mAh 96 -* Self Discharge: <1% / Year @ 25°C 97 -* Max continuously current: 130mA 98 -* Max boost current: 2A, 1 second 76 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 99 99 100 - (% style="color:#037691" %)**Power Consumption**78 +[[image:image-20220708101224-1.png]] 101 101 102 -* STOP Mode: 10uA @ 3.3v 103 -* Max transmit power: 350mA@3.3v 104 104 105 105 106 106 == 1.4 Applications == 107 107 108 - 109 -* Smart Buildings & Home Automation 110 -* Logistics and Supply Chain Management 111 -* Smart Metering 112 112 * Smart Agriculture 113 -* Smart Cities 114 -* Smart Factory 115 115 116 116 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 117 117 118 118 119 - 120 - 121 121 == 1.5 Pin Definitions == 122 122 123 123 124 -[[image:1657 328609906-564.png]]92 +[[image:1657246476176-652.png]] 125 125 126 126 127 127 128 -= 2. Use N DDS75to communicate with IoT Server =96 += 2. Use NSE01 to communicate with IoT Server = 129 129 130 - 131 131 == 2.1 How it works == 132 132 133 133 134 134 ((( 135 -The N DDS75is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75will 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.102 +The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 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 NSE01. 136 136 ))) 137 137 138 138 139 139 ((( 140 -The diagram below shows the working flow in default firmware of N DDS75:107 +The diagram below shows the working flow in default firmware of NSE01: 141 141 ))) 142 142 143 -((( 144 - 145 -))) 110 +[[image:image-20220708101605-2.png]] 146 146 147 -[[image:1657328659945-416.png]] 148 - 149 149 ((( 150 150 151 151 ))) 152 152 153 153 154 -== 2.2 Configure the NDDS75 == 155 155 118 +== 2.2 Configure the NSE01 == 156 156 120 + 157 157 === 2.2.1 Test Requirement === 158 158 159 159 160 160 ((( 161 -To use N DDS75in your city, make sure meet below requirements:125 +To use NSE01 in your city, make sure meet below requirements: 162 162 ))) 163 163 164 164 * Your local operator has already distributed a NB-IoT Network there. 165 -* The local NB-IoT network used the band that N DDS75supports.129 +* The local NB-IoT network used the band that NSE01 supports. 166 166 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 167 167 168 168 ((( 169 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The DDS75will 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.133 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSE01 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 170 170 ))) 171 171 172 172 173 -[[image:1657 328756309-230.png]]137 +[[image:1657249419225-449.png]] 174 174 175 175 176 176 177 177 === 2.2.2 Insert SIM card === 178 178 179 - 180 180 ((( 181 181 Insert the NB-IoT Card get from your provider. 182 182 ))) ... ... @@ -186,31 +186,28 @@ 186 186 ))) 187 187 188 188 189 -[[image:1657 328884227-504.png]]152 +[[image:1657249468462-536.png]] 190 190 191 191 192 192 193 -=== 2.2.3 Connect USB – TTL to N DDS75to configure it ===156 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 194 194 195 - 196 196 ((( 197 197 ((( 198 -User need to configure N DDS75via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75support AT Commands, user can use a USB to TTL adapter to connect to NDDS75and use AT Commands to configure it, as below.160 +User need to configure NSE01 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below. 199 199 ))) 200 200 ))) 201 201 202 -[[image:image-20220709092052-2.png]] 203 203 165 +**Connection:** 204 204 205 -(% style="color: blue" %)**Connection:**167 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 206 206 207 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**169 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 208 208 209 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**171 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 210 210 211 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 212 212 213 - 214 214 In the PC, use below serial tool settings: 215 215 216 216 * Baud: (% style="color:green" %)**9600** ... ... @@ -220,14 +220,13 @@ 220 220 * Flow Control: (% style="color:green" %)**None** 221 221 222 222 ((( 223 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on N DDS75. NDDS75will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.183 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 224 224 ))) 225 225 226 -[[image: 1657329814315-101.png]]186 +[[image:image-20220708110657-3.png]] 227 227 228 - 229 229 ((( 230 -(% style="color:red" %) **Note: the valid AT Commands can be found at:**(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**189 +(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 231 231 ))) 232 232 233 233 ... ... @@ -234,76 +234,59 @@ 234 234 235 235 === 2.2.4 Use CoAP protocol to uplink data === 236 236 196 +(% 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/]] 237 237 238 -(% 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/]]** 239 239 240 - 241 -((( 242 242 **Use below commands:** 243 -))) 244 244 245 -* ((( 246 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 247 -))) 248 -* ((( 249 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 250 -))) 251 -* ((( 252 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 201 +* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 202 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 203 +* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 253 253 254 - 255 - 256 -))) 257 - 258 -((( 259 259 For parameter description, please refer to AT command set 260 260 261 - 262 -))) 207 +[[image:1657249793983-486.png]] 263 263 264 -[[image:1657330452568-615.png]] 265 265 210 +After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server. 266 266 212 +[[image:1657249831934-534.png]] 267 267 268 -((( 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 - 272 -))) 273 273 274 -[[image:1657330472797-498.png]] 275 - 276 - 277 - 278 278 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 279 279 218 +This feature is supported since firmware version v1.0.1 280 280 281 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 282 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 283 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 284 284 285 -[[image:1657330501006-241.png]] 221 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 222 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 223 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 286 286 225 +[[image:1657249864775-321.png]] 287 287 288 -[[image:1657330533775-472.png]] 289 289 228 +[[image:1657249930215-289.png]] 290 290 291 291 231 + 292 292 === 2.2.6 Use MQTT protocol to uplink data === 293 293 234 +This feature is supported since firmware version v110 294 294 295 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 296 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 297 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 298 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 299 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 300 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 301 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 302 302 237 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 238 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 239 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 240 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 241 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 242 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 243 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 244 + 303 303 [[image:1657249978444-674.png]] 304 304 305 305 306 -[[image:1657 330723006-866.png]]248 +[[image:1657249990869-686.png]] 307 307 308 308 309 309 ((( ... ... @@ -314,129 +314,72 @@ 314 314 315 315 === 2.2.7 Use TCP protocol to uplink data === 316 316 259 +This feature is supported since firmware version v110 317 317 318 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 319 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 320 320 321 -[[image:image-20220709093918-1.png]] 262 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 263 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 322 322 265 +[[image:1657250217799-140.png]] 323 323 324 -[[image:image-20220709093918-2.png]] 325 325 268 +[[image:1657250255956-604.png]] 326 326 327 327 271 + 328 328 === 2.2.8 Change Update Interval === 329 329 330 - 331 331 User can use below command to change the (% style="color:green" %)**uplink interval**. 332 332 333 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 276 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 334 334 335 335 ((( 336 - 337 - 338 - 339 339 (% style="color:red" %)**NOTE:** 280 +))) 340 340 341 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 342 - 343 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 282 +((( 283 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 344 344 ))) 345 345 346 -(% 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).** 347 347 348 348 349 - 350 350 == 2.3 Uplink Payload == 351 351 290 +In this mode, uplink payload includes in total 18 bytes 352 352 353 -=== 2.3.1 Before Firmware v1.3.2 === 354 - 355 - 356 -In this mode, uplink payload includes in total 14 bytes 357 - 358 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 292 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 359 359 |=(% style="width: 60px;" %)((( 360 360 **Size(bytes)** 361 -)))|=(% style="width: 60px;" %)**6**|=(% style="width:35px;" %)2|=(% style="width:35px;" %)**2**|=(% style="width:80px;" %)**1**|=(% style="width:100px;" %)**2**|=(% style="width:60px;" %)**1**362 -|(% 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:1 20px" %)[[Distanceunit:mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]295 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 60px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 90px;" %)**2**|=(% style="width: 50px;" %)**1** 296 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H2.4.5A0SoilMoisture"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H2.4.6A0SoilTemperature"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H2.4.7A0SoilConductivity28EC29"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.8A0DigitalInterrupt"]] 363 363 364 364 ((( 365 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N DDS75uplink data.299 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 366 366 ))) 367 367 368 368 369 -[[image: 1657331036973-987.png]]303 +[[image:image-20220708111918-4.png]] 370 370 371 371 372 - 373 -The payload is **ASCII** string, representative same HEX: 374 - 375 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 376 - 377 -**where :** 378 - 379 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 380 - 381 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 382 - 383 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 384 - 385 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 386 - 387 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 388 - 389 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 390 - 391 - 392 -=== 2.3.2 Since firmware v1.3.2 === 393 - 394 - 395 -In this mode, uplink payload includes 69 bytes in total by default. 396 - 397 -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. 398 - 399 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 400 -|=(% scope="row" style="width: 60px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:70px" %)**4**|(% style="width:40px" %)**2**|(% style="width:60px" %)**4** 401 -|=(% style="width: 95px;" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp....... 402 - 403 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 404 - 405 -[[image:image-20220908175246-1.png]] 406 - 407 - 408 408 The payload is ASCII string, representative same HEX: 409 409 410 - **0x(% style="color:red" %)f867787050213317 (% style="color:blue" %)0084(% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01(% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf00396319ba3c 00396319b988 00396319b8d40396319b820 00396319b76c00396319b6b80396319b604(%%)**308 +0x72403155615900640c7817075e0a8c02f900 where: 411 411 412 -**where:** 310 +* Device ID: 0x 724031556159 = 724031556159 311 +* Version: 0x0064=100=1.0.0 413 413 414 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317 313 +* BAT: 0x0c78 = 3192 mV = 3.192V 314 +* Singal: 0x17 = 23 315 +* Soil Moisture: 0x075e= 1886 = 18.86 % 316 +* Soil Temperature:0x0a8c =2700=27 °C 317 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 318 +* Interrupt: 0x00 = 0 415 415 416 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 417 - 418 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 419 - 420 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 421 - 422 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 423 - 424 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 425 - 426 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 427 - 428 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 429 - 430 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 431 - 432 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 433 - 434 434 == 2.4 Payload Explanation and Sensor Interface == 435 435 436 436 437 437 === 2.4.1 Device ID === 438 438 439 - 440 440 ((( 441 441 By default, the Device ID equal to the last 6 bytes of IMEI. 442 442 ))) ... ... @@ -443,12 +443,10 @@ 443 443 444 444 ((( 445 445 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 446 - 447 - 448 448 ))) 449 449 450 450 ((( 451 - (% style="color:blue" %)**Example334 +**Example:** 452 452 ))) 453 453 454 454 ((( ... ... @@ -456,32 +456,19 @@ 456 456 ))) 457 457 458 458 ((( 459 -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.342 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 460 460 ))) 461 461 462 462 463 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 464 464 465 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 466 - 467 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 468 - 469 - 470 -(% style="color:blue" %)**Example :** 471 - 472 -AT+DEUI=868411056754138 473 - 474 - 475 - 476 476 === 2.4.2 Version Info === 477 477 478 - 479 479 ((( 480 480 Specify the software version: 0x64=100, means firmware version 1.00. 481 481 ))) 482 482 483 483 ((( 484 -For example: 0x00 64 : this device is N DDS75with firmware version 1.0.0.354 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 485 485 ))) 486 486 487 487 ... ... @@ -488,6 +488,9 @@ 488 488 489 489 === 2.4.3 Battery Info === 490 490 361 +((( 362 +Check the battery voltage for LSE01. 363 +))) 491 491 492 492 ((( 493 493 Ex1: 0x0B45 = 2885mV ... ... @@ -501,7 +501,6 @@ 501 501 502 502 === 2.4.4 Signal Strength === 503 503 504 - 505 505 ((( 506 506 NB-IoT Network signal Strength. 507 507 ))) ... ... @@ -532,22 +532,65 @@ 532 532 533 533 534 534 535 -=== 2.4.5 Distance ===407 +=== 2.4.5 Soil Moisture === 536 536 409 +((( 410 +((( 411 +Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil. 412 +))) 413 +))) 537 537 538 -Get the distance. Flat object range 280mm - 7500mm. 415 +((( 416 +((( 417 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 418 +))) 419 +))) 539 539 540 540 ((( 541 - Forexample, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is422 + 542 542 ))) 543 543 544 544 ((( 426 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 427 +))) 428 + 429 + 430 + 431 +=== 2.4.6 Soil Temperature === 432 + 545 545 ((( 546 - (%style="color:blue"%)**0B05(H) = 2821(D) = 2821mm.**434 +Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __**0x09 0xEC**__, the temperature content in the soil is 547 547 ))) 436 + 437 +((( 438 +**Example**: 548 548 ))) 549 549 550 550 ((( 442 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 443 +))) 444 + 445 +((( 446 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 447 +))) 448 + 449 + 450 + 451 +=== 2.4.7 Soil Conductivity (EC) === 452 + 453 +((( 454 +Obtain (% style="color:#4f81bd" %)**__soluble salt concentration__**(%%) in soil or (% style="color:#4f81bd" %)**__soluble ion concentration in liquid fertilizer__**(%%) or (% style="color:#4f81bd" %)**__planting medium__**(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000). 455 +))) 456 + 457 +((( 458 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 459 +))) 460 + 461 +((( 462 +Generally, the EC value of irrigation water is less than 800uS / cm. 463 +))) 464 + 465 +((( 551 551 552 552 ))) 553 553 ... ... @@ -555,11 +555,10 @@ 555 555 556 556 ))) 557 557 558 -=== 2.4. 6Digital Interrupt ===473 +=== 2.4.8 Digital Interrupt === 559 559 560 - 561 561 ((( 562 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the N DDS75will send a packet to the server.476 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server. 563 563 ))) 564 564 565 565 ((( ... ... @@ -567,7 +567,7 @@ 567 567 ))) 568 568 569 569 ((( 570 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/ 484 +(% 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]])**.** 571 571 ))) 572 572 573 573 ... ... @@ -590,24 +590,19 @@ 590 590 591 591 592 592 593 -=== 2.4. 7+5V Output ===507 +=== 2.4.9 +5V Output === 594 594 595 - 596 596 ((( 597 -N DDS75will enable +5V output before all sampling and disable the +5v after all sampling.510 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 598 598 ))) 599 599 600 600 601 601 ((( 602 602 The 5V output time can be controlled by AT Command. 603 - 604 - 605 605 ))) 606 606 607 607 ((( 608 608 (% style="color:blue" %)**AT+5VT=1000** 609 - 610 - 611 611 ))) 612 612 613 613 ((( ... ... @@ -618,12 +618,11 @@ 618 618 619 619 == 2.5 Downlink Payload == 620 620 530 +By default, NSE01 prints the downlink payload to console port. 621 621 622 - By default, NDDS75 prints thedownlink payload to consoleport.532 +[[image:image-20220708133731-5.png]] 623 623 624 -[[image:image-20220709100028-1.png]] 625 625 626 - 627 627 ((( 628 628 (% style="color:blue" %)**Examples:** 629 629 ))) ... ... @@ -657,7 +657,7 @@ 657 657 ))) 658 658 659 659 ((( 660 -If payload = 0x04FF, it will reset the N DDS75568 +If payload = 0x04FF, it will reset the NSE01 661 661 ))) 662 662 663 663 ... ... @@ -669,209 +669,240 @@ 669 669 670 670 671 671 672 -== 2.6 D istancealarm function(Since firmwarev1.3.2)==580 +== 2.6 LED Indicator == 673 673 582 +((( 583 +The NSE01 has an internal LED which is to show the status of different state. 674 674 675 -(% style="color:blue" %)** ➢ AT Command:** 676 676 677 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 586 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe) 587 +* Then the LED will be on for 1 second means device is boot normally. 588 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 589 +* For each uplink probe, LED will be on for 500ms. 590 +))) 678 678 679 -² When min=0, and max≠0, Alarm higher than max 680 680 681 -² When min≠0, and max=0, Alarm lower than min 682 682 683 -² When min≠0 and max≠0, Alarm higher than max or lower than min 684 684 595 +== 2.7 Installation in Soil == 685 685 686 - (%style="color:blue"%)** Example:**597 +__**Measurement the soil surface**__ 687 687 688 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 599 +((( 600 +Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]] 601 +))) 689 689 603 +[[image:1657259653666-883.png]] 690 690 691 691 692 -== 2.7 Set the number of data to be uploaded and the recording time == 606 +((( 607 + 693 693 609 +((( 610 +Dig a hole with diameter > 20CM. 611 +))) 694 694 695 -(% style="color:blue" %)** ➢ AT Command:** 613 +((( 614 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 615 +))) 616 +))) 696 696 697 -* (% 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) 698 -* (% 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. 618 +[[image:1654506665940-119.png]] 699 699 700 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 620 +((( 621 + 622 +))) 701 701 702 -[[image:image-20221009001114-1.png||height="687" width="955"]] 703 703 625 +== 2.8 Firmware Change Log == 704 704 705 705 706 - == 2.8 ReadorClearcacheddata ==628 +Download URL & Firmware Change log 707 707 630 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]] 708 708 709 -(% style="color:blue" %)** ➢ AT Command:** 710 710 711 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 712 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 633 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 713 713 714 -[[image:image-20220908175333-2.png]] 715 715 716 716 637 +== 2.9 Battery Analysis == 717 717 718 -== 2.9 LED Indicator ==639 +=== 2.9.1 Battery Type === 719 719 720 720 721 -The NDDS75 has an internal LED which is to show the status of different state. 642 +((( 643 +The NSE01 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter. 644 +))) 722 722 723 723 724 -* 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) 725 -* Then the LED will be on for 1 second means device is boot normally. 726 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 727 -* For each uplink probe, LED will be on for 500ms. 647 +((( 648 +The battery is designed to last for several years depends on the actually use environment and update interval. 649 +))) 728 728 651 + 729 729 ((( 730 - 653 +The battery related documents as below: 731 731 ))) 732 732 656 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 657 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 658 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 733 733 660 +((( 661 +[[image:image-20220708140453-6.png]] 662 +))) 734 734 735 -== 2.10 Firmware Change Log == 736 736 737 737 666 +=== 2.9.2 Power consumption Analyze === 667 + 738 738 ((( 739 -D ownloadURL & FirmwareChangelog: [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]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. 740 740 ))) 741 741 672 + 742 742 ((( 743 - 674 +Instruction to use as below: 744 744 ))) 745 745 746 746 ((( 747 - Upgrade Instruction:[[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]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/]] 748 748 ))) 749 749 750 750 682 +((( 683 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 684 +))) 751 751 752 -== 2.11 Battery & Power Consumption == 686 +* ((( 687 +Product Model 688 +))) 689 +* ((( 690 +Uplink Interval 691 +))) 692 +* ((( 693 +Working Mode 694 +))) 753 753 696 +((( 697 +And the Life expectation in difference case will be shown on the right. 698 +))) 754 754 755 - PS-LB-NA uses ER26500+ SPC1520 battery pack.See below link for detail information about the battery info and how to replace.700 +[[image:image-20220708141352-7.jpeg]] 756 756 757 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 758 758 759 -= 3. Access NB-IoT Module = 760 760 704 +=== 2.9.3 Battery Note === 761 761 762 762 ((( 763 - Users can directlyaccess theAT command setof theNB-IoTmodule.707 +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. 764 764 ))) 765 765 766 -((( 767 -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/]] 768 768 769 - 770 -))) 771 771 772 - [[image:1657333200519-600.png]]712 +=== 2.9.4 Replace the battery === 773 773 714 +((( 715 +The default battery pack of NSE01 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes). 716 +))) 774 774 775 775 776 -= 4. Using the AT Commands = 777 777 720 += 3. Access NB-IoT Module = 778 778 779 -== 4.1 Access AT Commands == 722 +((( 723 +Users can directly access the AT command set of the NB-IoT module. 724 +))) 780 780 726 +((( 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/]] 728 +))) 781 781 782 - See this link for detail:[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]730 +[[image:1657261278785-153.png]] 783 783 784 784 785 -AT+<CMD>? : Help on <CMD> 786 786 787 - AT+<CMD>: Run<CMD>734 += 4. Using the AT Commands = 788 788 789 - AT+<CMD>=<value>:Setthevalue736 +== 4.1 Access AT Commands == 790 790 791 - AT+<CMD>=?Gethe value738 +See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]] 792 792 793 793 794 - (%style="color:#037691"%)**GeneralCommands**(%%)741 +AT+<CMD>? : Help on <CMD> 795 795 796 -AT Attention743 +AT+<CMD> : Run <CMD> 797 797 798 -AT ?hortHelp745 +AT+<CMD>=<value> : Set the value 799 799 800 -AT ZMCU Reset747 +AT+<CMD>=? : Get the value 801 801 802 -AT+TDC : Application Data Transmission Interval 803 803 804 - AT+CFG: Printallconfigurations750 +(% style="color:#037691" %)**General Commands**(%%) 805 805 806 -AT +CFGMOD:Workingmodeselection752 +AT : Attention 807 807 808 -AT +INTMOD:Setthetriggerinterruptmode754 +AT? : Short Help 809 809 810 -AT +5VT:Setextendthetimeof5Vpower756 +ATZ : MCU Reset 811 811 812 -AT+ PROChooseagreement758 +AT+TDC : Application Data Transmission Interval 813 813 814 -AT+ WEIGRE:Getweightorsetweightto0760 +AT+CFG : Print all configurations 815 815 816 -AT+ WEIGAPGetorSettheGapValueof weight762 +AT+CFGMOD : Working mode selection 817 817 818 -AT+ RXDLExtendthesendingand receivingtime764 +AT+INTMOD : Set the trigger interrupt mode 819 819 820 -AT+ CNTFAC:Getorsetcountingparameters766 +AT+5VT : Set extend the time of 5V power 821 821 822 -AT+ SERVADDR:ServerAddress768 +AT+PRO : Choose agreement 823 823 824 -AT+ TRSetrecordtime"770 +AT+WEIGRE : Get weight or set weight to 0 825 825 826 -AT+AP Nset theAPN772 +AT+WEIGAP : Get or Set the GapValue of weight 827 827 828 -AT+ FBAND:GetorSetwhethertoautomaticallymodifythefrequencyband774 +AT+RXDL : Extend the sending and receiving time 829 829 830 -AT+ DNSCFG:Get orSetDNSServer776 +AT+CNTFAC : Get or set counting parameters 831 831 832 -AT+ GETSENSORVALUE:Returnsthecurrentsensormeasurement778 +AT+SERVADDR : Server Address 833 833 834 -AT+NOUD : Get or Set the number of data to be uploaded 835 835 836 -AT+CDP : Read or Clear cached data 837 - 838 -AT+LDDSALARM : Get or Set alarm of distance 839 - 840 - 841 841 (% style="color:#037691" %)**COAP Management** 842 842 843 -AT+URI : 783 +AT+URI : Resource parameters 844 844 845 845 846 846 (% style="color:#037691" %)**UDP Management** 847 847 848 -AT+CFM : 788 +AT+CFM : Upload confirmation mode (only valid for UDP) 849 849 850 850 851 851 (% style="color:#037691" %)**MQTT Management** 852 852 853 -AT+CLIENT 793 +AT+CLIENT : Get or Set MQTT client 854 854 855 -AT+UNAME :Get or Set MQTT Username795 +AT+UNAME : Get or Set MQTT Username 856 856 857 -AT+PWD 797 +AT+PWD : Get or Set MQTT password 858 858 859 -AT+PUBTOPIC :Get or Set MQTT publish topic799 +AT+PUBTOPIC : Get or Set MQTT publish topic 860 860 861 -AT+SUBTOPIC :Get or Set MQTT subscription topic801 +AT+SUBTOPIC : Get or Set MQTT subscription topic 862 862 863 863 864 864 (% style="color:#037691" %)**Information** 865 865 866 -AT+FDR : 806 +AT+FDR : Factory Data Reset 867 867 868 -AT+PWORD : 808 +AT+PWORD : Serial Access Password 869 869 870 870 871 871 872 872 = 5. FAQ = 873 873 874 - 875 875 == 5.1 How to Upgrade Firmware == 876 876 877 877 ... ... @@ -884,14 +884,20 @@ 884 884 ))) 885 885 886 886 ((( 887 -(% style="color:red" %) **Notice, NDDS75and LDDS75share the same mother board. They use the same connection and method to update.**826 +(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update. 888 888 ))) 889 889 890 890 891 891 892 -= 6.Trouble Shooting=831 +== 5.2 Can I calibrate NSE01 to different soil types? == 893 893 833 +((( 834 +NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]]. 835 +))) 894 894 837 + 838 += 6. Trouble Shooting = 839 + 895 895 == 6.1 Connection problem when uploading firmware == 896 896 897 897 ... ... @@ -907,7 +907,6 @@ 907 907 908 908 == 6.2 AT Command input doesn't work == 909 909 910 - 911 911 ((( 912 912 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. 913 913 ... ... @@ -918,7 +918,7 @@ 918 918 = 7. Order Info = 919 919 920 920 921 -Part Number**:** (% style="color:#4f81bd" %)**NS DDS75**865 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 922 922 923 923 924 924 (% class="wikigeneratedid" %) ... ... @@ -933,7 +933,7 @@ 933 933 934 934 (% style="color:#037691" %)**Package Includes**: 935 935 936 -* N DDS75NB-IoTDistanceDetectSensorNodex 1880 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 937 937 * External antenna x 1 938 938 ))) 939 939 ... ... @@ -940,13 +940,10 @@ 940 940 ((( 941 941 942 942 943 - 944 944 (% style="color:#037691" %)**Dimension and weight**: 945 945 946 -* Device Size: 13.0 x 5 x 4.5 cm 947 -* Device Weight: 150g 948 -* Package Size / pcs : 15 x 12x 5.5 cm 949 -* Weight / pcs : 220g 889 +* Size: 195 x 125 x 55 mm 890 +* Weight: 420g 950 950 ))) 951 951 952 952 ((( ... ... @@ -958,6 +958,5 @@ 958 958 959 959 = 9. Support = 960 960 961 - 962 962 * 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. 963 963 * 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]]
- 1657327959271-447.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.3 KB - Content
- 1657328609906-564.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -492.6 KB - Content
- 1657328659945-416.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.8 KB - Content
- 1657328756309-230.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.5 KB - Content
- 1657328884227-504.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657329814315-101.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.3 KB - Content
- 1657330452568-615.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.3 KB - Content
- 1657330472797-498.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.9 KB - Content
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -83.8 KB - Content
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220709092052-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -247.3 KB - Content
- image-20220709093918-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -61.9 KB - Content
- image-20220709100028-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.8 KB - Content
- image-20220709101450-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.5 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -611.5 KB - Content
- image-20220908175246-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.David - Size
-
... ... @@ -1,1 +1,0 @@ 1 -31.1 KB - Content
- image-20221009001114-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Edwin - Size
-
... ... @@ -1,1 +1,0 @@ 1 -282.9 KB - Content