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, 22 removed)
- 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 ... ... @@ -22,54 +22,39 @@ 22 22 23 23 24 24 ((( 25 -((( 26 26 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. 27 27 ))) 28 28 29 -((( 30 -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 + 31 31 ))) 32 32 33 -((( 34 -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. 35 -))) 35 +[[image:1654503236291-817.png]] 36 36 37 -((( 38 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 39 -))) 40 40 41 -((( 42 -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) 43 -))) 38 +[[image:1657245163077-232.png]] 44 44 45 -((( 46 -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. 47 -))) 48 -))) 49 49 50 - 51 -))) 52 52 53 -[[image:1657327959271-447.png]] 54 - 55 - 56 56 == 1.2 Features == 57 57 58 - 59 59 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 60 -* Ultra low power consumption 61 -* Distance Detection by Ultrasonic technology 62 -* Flat object range 280mm - 7500mm 63 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 64 -* Cable Length: 25cm 45 +* Monitor Soil Moisture 46 +* Monitor Soil Temperature 47 +* Monitor Soil Conductivity 65 65 * AT Commands to change parameters 66 66 * Uplink on periodically 67 67 * Downlink to change configure 68 68 * IP66 Waterproof Enclosure 52 +* Ultra-Low Power consumption 53 +* AT Commands to change parameters 69 69 * Micro SIM card slot for NB-IoT SIM 70 70 * 8500mAh Battery for long term use 71 71 72 - 73 73 == 1.3 Specification == 74 74 75 75 ... ... @@ -80,95 +80,82 @@ 80 80 81 81 (% style="color:#037691" %)**NB-IoT Spec:** 82 82 83 -* B1 @H-FDD: 2100MHz 84 -* B3 @H-FDD: 1800MHz 85 -* B8 @H-FDD: 900MHz 86 -* B5 @H-FDD: 850MHz 87 -* B20 @H-FDD: 800MHz 88 -* 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 89 89 90 -(% style="color:#037691" %)** Battery:**74 +Probe(% style="color:#037691" %)** Specification:** 91 91 92 -* Li/SOCI2 un-chargeable battery 93 -* Capacity: 8500mAh 94 -* Self Discharge: <1% / Year @ 25°C 95 -* Max continuously current: 130mA 96 -* 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. 97 97 98 - (% style="color:#037691" %)**Power Consumption**78 +[[image:image-20220708101224-1.png]] 99 99 100 -* STOP Mode: 10uA @ 3.3v 101 -* Max transmit power: 350mA@3.3v 102 102 103 103 104 104 == 1.4 Applications == 105 105 106 - 107 -* Smart Buildings & Home Automation 108 -* Logistics and Supply Chain Management 109 -* Smart Metering 110 110 * Smart Agriculture 111 -* Smart Cities 112 -* Smart Factory 113 113 114 114 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 115 115 116 116 117 - 118 118 == 1.5 Pin Definitions == 119 119 120 120 121 -[[image:1657 328609906-564.png]]92 +[[image:1657246476176-652.png]] 122 122 123 123 124 -= 2. Use NDDS75 to communicate with IoT Server = 125 125 96 += 2. Use NSE01 to communicate with IoT Server = 97 + 126 126 == 2.1 How it works == 127 127 128 128 129 129 ((( 130 -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. 131 131 ))) 132 132 133 133 134 134 ((( 135 -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: 136 136 ))) 137 137 110 +[[image:image-20220708101605-2.png]] 111 + 138 138 ((( 139 139 140 140 ))) 141 141 142 -[[image:1657328659945-416.png]] 143 143 144 -((( 145 - 146 -))) 147 147 148 -== 2.2 Configure the N DDS75==118 +== 2.2 Configure the NSE01 == 149 149 120 + 150 150 === 2.2.1 Test Requirement === 151 151 152 152 153 153 ((( 154 -To use N DDS75in your city, make sure meet below requirements:125 +To use NSE01 in your city, make sure meet below requirements: 155 155 ))) 156 156 157 157 * Your local operator has already distributed a NB-IoT Network there. 158 -* The local NB-IoT network used the band that N DDS75supports.129 +* The local NB-IoT network used the band that NSE01 supports. 159 159 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 160 160 161 161 ((( 162 -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 163 163 ))) 164 164 165 165 166 -[[image:1657 328756309-230.png]]137 +[[image:1657249419225-449.png]] 167 167 168 168 140 + 169 169 === 2.2.2 Insert SIM card === 170 170 171 - 172 172 ((( 173 173 Insert the NB-IoT Card get from your provider. 174 174 ))) ... ... @@ -178,30 +178,28 @@ 178 178 ))) 179 179 180 180 181 -[[image:1657 328884227-504.png]]152 +[[image:1657249468462-536.png]] 182 182 183 183 184 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 185 185 156 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 186 186 187 187 ((( 188 188 ((( 189 -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. 190 190 ))) 191 191 ))) 192 192 193 -[[image:image-20220709092052-2.png]] 194 194 165 +**Connection:** 195 195 196 -(% style="color: blue" %)**Connection:**167 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 197 197 198 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**169 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 199 199 200 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**171 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 201 201 202 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 203 203 204 - 205 205 In the PC, use below serial tool settings: 206 206 207 207 * Baud: (% style="color:green" %)**9600** ... ... @@ -211,87 +211,72 @@ 211 211 * Flow Control: (% style="color:green" %)**None** 212 212 213 213 ((( 214 -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. 215 215 ))) 216 216 217 -[[image: 1657329814315-101.png]]186 +[[image:image-20220708110657-3.png]] 218 218 219 - 220 220 ((( 221 -(% 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/]] 222 222 ))) 223 223 224 224 193 + 225 225 === 2.2.4 Use CoAP protocol to uplink data === 226 226 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/]] 227 227 228 -(% 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/]]** 229 229 230 - 231 -((( 232 232 **Use below commands:** 233 -))) 234 234 235 -* ((( 236 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 237 -))) 238 -* ((( 239 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 240 -))) 241 -* ((( 242 -(% 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 243 243 244 - 245 - 246 -))) 247 - 248 -((( 249 249 For parameter description, please refer to AT command set 250 250 251 - 252 -))) 207 +[[image:1657249793983-486.png]] 253 253 254 -[[image:1657330452568-615.png]] 255 255 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. 256 256 212 +[[image:1657249831934-534.png]] 257 257 258 -((( 259 -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. 260 260 261 - 262 -))) 263 263 264 - [[image:1657330472797-498.png]]216 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 265 265 218 +This feature is supported since firmware version v1.0.1 266 266 267 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 268 268 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 269 269 270 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 271 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 272 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 225 +[[image:1657249864775-321.png]] 273 273 274 -[[image:1657330501006-241.png]] 275 275 228 +[[image:1657249930215-289.png]] 276 276 277 -[[image:1657330533775-472.png]] 278 278 279 279 280 280 === 2.2.6 Use MQTT protocol to uplink data === 281 281 234 +This feature is supported since firmware version v110 282 282 283 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 284 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 285 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 286 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 287 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 288 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 289 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 290 290 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 + 291 291 [[image:1657249978444-674.png]] 292 292 293 293 294 -[[image:1657 330723006-866.png]]248 +[[image:1657249990869-686.png]] 295 295 296 296 297 297 ((( ... ... @@ -299,125 +299,75 @@ 299 299 ))) 300 300 301 301 256 + 302 302 === 2.2.7 Use TCP protocol to uplink data === 303 303 259 +This feature is supported since firmware version v110 304 304 305 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 306 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 307 307 308 -[[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 309 309 265 +[[image:1657250217799-140.png]] 310 310 311 -[[image:image-20220709093918-2.png]] 312 312 268 +[[image:1657250255956-604.png]] 313 313 314 -=== 2.2.8 Change Update Interval === 315 315 316 316 272 +=== 2.2.8 Change Update Interval === 273 + 317 317 User can use below command to change the (% style="color:green" %)**uplink interval**. 318 318 319 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 276 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 320 320 321 321 ((( 322 - 323 - 324 - 325 325 (% style="color:red" %)**NOTE:** 280 +))) 326 326 327 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 328 - 329 -(% 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. 330 330 ))) 331 331 332 -(% 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).** 333 333 334 334 335 335 == 2.3 Uplink Payload == 336 336 337 - ===2.3.1BeforeFirmwarev1.3.2===290 +In this mode, uplink payload includes in total 18 bytes 338 338 339 - 340 -In this mode, uplink payload includes in total 14 bytes 341 - 342 -(% border="1" cellspacing="10" style="background-color:#f2f2f2; width:440px" %) 343 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)((( 292 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 293 +|=(% style="width: 60px;" %)((( 344 344 **Size(bytes)** 345 -)))|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**6**|=(% style="width:35px;background-color:#D9E2F3;color:#0070C0" %)2|=(% style="width:35px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width:80px;background-color:#D9E2F3;color:#0070C0" %)**1**|=(% style="width:100px;background-color:#D9E2F3;color:#0070C0" %)**2**|=(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**346 -|(% 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"]] 347 347 348 348 ((( 349 -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. 350 350 ))) 351 351 352 352 353 -[[image: 1657331036973-987.png]]303 +[[image:image-20220708111918-4.png]] 354 354 355 355 356 -The payload is **ASCII** string, representative same HEX: 357 - 358 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 ** 359 - 360 -**where :** 361 - 362 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159 363 - 364 -* (% style="color:#037691" %)**Version:**(%%) 0x0064=100=1.0.0 365 - 366 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V 367 - 368 -* (% style="color:#037691" %)**Signal:**(%%) 0x19 = 25 369 - 370 -* (% style="color:#037691" %)**Distance:** (%%)0x0292= 658 mm 371 - 372 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0 373 - 374 -=== 2.3.2 Since firmware v1.3.2 === 375 - 376 - 377 -In this mode, uplink payload includes 69 bytes in total by default. 378 - 379 -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. 380 - 381 -(% border="1" style="background-color:#ffffcc; color:green; width:490px" %) 382 -|=(% style="width: 60px;background-color:#D9E2F3;color:#0070C0" %)**Size(bytes)**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**8**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:25px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**1**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:70px;background-color:#D9E2F3;color:#0070C0" %)**4**|(% style="width:40px;background-color:#D9E2F3;color:#0070C0" %)**2**|(% style="width:60px;background-color:#D9E2F3;color:#0070C0" %)**4** 383 -|=(% 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....... 384 - 385 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 386 - 387 -[[image:image-20220908175246-1.png]] 388 - 389 - 390 390 The payload is ASCII string, representative same HEX: 391 391 392 - **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: 393 393 394 -**where:** 310 +* Device ID: 0x 724031556159 = 724031556159 311 +* Version: 0x0064=100=1.0.0 395 395 396 -* (% 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 397 397 398 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2 399 - 400 -* (% style="color:#037691" %)**BAT:**(%%) 0x0cf4 = 3316 mV = 3.316V 401 - 402 -* (% style="color:#037691" %)**Singal:**(%%) 0x1e = 30 403 - 404 -* (% style="color:#037691" %)**Mod:**(%%)** **0x01 = 1 405 - 406 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0 407 - 408 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57 409 - 410 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 411 - 412 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0 413 - 414 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,....... 415 - 416 416 == 2.4 Payload Explanation and Sensor Interface == 417 417 322 + 418 418 === 2.4.1 Device ID === 419 419 420 - 421 421 ((( 422 422 By default, the Device ID equal to the last 6 bytes of IMEI. 423 423 ))) ... ... @@ -424,12 +424,10 @@ 424 424 425 425 ((( 426 426 User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 427 - 428 - 429 429 ))) 430 430 431 431 ((( 432 - (% style="color:blue" %)**Example334 +**Example:** 433 433 ))) 434 434 435 435 ((( ... ... @@ -437,36 +437,28 @@ 437 437 ))) 438 438 439 439 ((( 440 -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. 441 441 ))) 442 442 443 443 444 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 445 445 446 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 447 - 448 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 449 - 450 - 451 -(% style="color:blue" %)**Example :** 452 - 453 -AT+DEUI=868411056754138 454 - 455 - 456 456 === 2.4.2 Version Info === 457 457 458 - 459 459 ((( 460 460 Specify the software version: 0x64=100, means firmware version 1.00. 461 461 ))) 462 462 463 463 ((( 464 -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. 465 465 ))) 466 466 467 467 358 + 468 468 === 2.4.3 Battery Info === 469 469 361 +((( 362 +Check the battery voltage for LSE01. 363 +))) 470 470 471 471 ((( 472 472 Ex1: 0x0B45 = 2885mV ... ... @@ -477,9 +477,9 @@ 477 477 ))) 478 478 479 479 374 + 480 480 === 2.4.4 Signal Strength === 481 481 482 - 483 483 ((( 484 484 NB-IoT Network signal Strength. 485 485 ))) ... ... @@ -509,30 +509,77 @@ 509 509 ))) 510 510 511 511 512 -=== 2.4.5 Distance === 513 513 407 +=== 2.4.5 Soil Moisture === 514 514 515 -Get the distance. Flat object range 280mm - 7500mm. 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 +))) 516 516 517 517 ((( 518 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 416 +((( 417 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 519 519 ))) 419 +))) 520 520 521 521 ((( 422 + 423 +))) 424 + 522 522 ((( 523 -(% style="color:b lue" %)**B05(H) =2821(D) =2821mm.**426 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 524 524 ))) 428 + 429 + 430 + 431 +=== 2.4.6 Soil Temperature === 432 + 433 +((( 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 525 525 ))) 526 526 527 527 ((( 438 +**Example**: 439 +))) 440 + 441 +((( 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 +((( 528 528 529 529 ))) 530 530 531 -=== 2.4.6 Digital Interrupt === 469 +((( 470 + 471 +))) 532 532 473 +=== 2.4.8 Digital Interrupt === 533 533 534 534 ((( 535 -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. 536 536 ))) 537 537 538 538 ((( ... ... @@ -540,7 +540,7 @@ 540 540 ))) 541 541 542 542 ((( 543 -(% 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]])**.** 544 544 ))) 545 545 546 546 ... ... @@ -562,24 +562,20 @@ 562 562 ))) 563 563 564 564 565 -=== 2.4.7 +5V Output === 566 566 507 +=== 2.4.9 +5V Output === 567 567 568 568 ((( 569 -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. 570 570 ))) 571 571 572 572 573 573 ((( 574 574 The 5V output time can be controlled by AT Command. 575 - 576 - 577 577 ))) 578 578 579 579 ((( 580 580 (% style="color:blue" %)**AT+5VT=1000** 581 - 582 - 583 583 ))) 584 584 585 585 ((( ... ... @@ -587,14 +587,14 @@ 587 587 ))) 588 588 589 589 527 + 590 590 == 2.5 Downlink Payload == 591 591 530 +By default, NSE01 prints the downlink payload to console port. 592 592 593 - By default, NDDS75 prints thedownlink payload to consoleport.532 +[[image:image-20220708133731-5.png]] 594 594 595 -[[image:image-20220709100028-1.png]] 596 596 597 - 598 598 ((( 599 599 (% style="color:blue" %)**Examples:** 600 600 ))) ... ... @@ -628,7 +628,7 @@ 628 628 ))) 629 629 630 630 ((( 631 -If payload = 0x04FF, it will reset the N DDS75568 +If payload = 0x04FF, it will reset the NSE01 632 632 ))) 633 633 634 634 ... ... @@ -639,195 +639,239 @@ 639 639 ))) 640 640 641 641 642 -== 2.6 Distance alarm function(Since firmware v1.3.2) == 643 643 580 +== 2.6 LED Indicator == 644 644 645 -(% style="color:blue" %)** ➢ AT Command:** 582 +((( 583 +The NSE01 has an internal LED which is to show the status of different state. 646 646 647 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 648 648 649 -² When min=0, and max≠0, Alarm higher than 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 +))) 650 650 651 -² When min≠0, and max=0, Alarm lower than min 652 652 653 -² When min≠0 and max≠0, Alarm higher than max or lower than min 654 654 655 655 656 - (%style="color:blue"%)**Example:**595 +== 2.7 Installation in Soil == 657 657 658 -** AT+ LDDSALARM=260,2000** ~/~/ Alarmwhendistancelowerthan 260.597 +__**Measurement the soil surface**__ 659 659 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 +))) 660 660 661 - == 2.7 Set the number of data to beuploaded and the recordingtime ==603 +[[image:1657259653666-883.png]] 662 662 663 663 664 -(% style="color:blue" %)** ➢ AT Command:** 606 +((( 607 + 665 665 666 -* (% 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) 667 -* (% 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. 609 +((( 610 +Dig a hole with diameter > 20CM. 611 +))) 668 668 669 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:** 613 +((( 614 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 615 +))) 616 +))) 670 670 671 -[[image: image-20221009001114-1.png||height="687" width="955"]]618 +[[image:1654506665940-119.png]] 672 672 620 +((( 621 + 622 +))) 673 673 674 -== 2.8 Read or Clear cached data == 675 675 625 +== 2.8 Firmware Change Log == 676 676 677 -(% style="color:blue" %)** ➢ AT Command:** 678 678 679 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 680 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 628 +Download URL & Firmware Change log 681 681 682 -[[ image:image-20220908175333-2.png]]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/]] 683 683 684 684 685 - ==2.9 LEDIndicator=633 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 686 686 687 687 688 -The NDDS75 has an internal LED which is to show the status of different state. 689 689 637 +== 2.9 Battery Analysis == 690 690 691 -* 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) 692 -* Then the LED will be on for 1 second means device is boot normally. 693 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 694 -* For each uplink probe, LED will be on for 500ms. 639 +=== 2.9.1 Battery Type === 695 695 641 + 696 696 ((( 697 - 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. 698 698 ))) 699 699 700 700 701 -== 2.10 Firmware Change Log == 647 +((( 648 +The battery is designed to last for several years depends on the actually use environment and update interval. 649 +))) 702 702 703 703 704 704 ((( 705 - Download URL & FirmwareChange log: [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]653 +The battery related documents as below: 706 706 ))) 707 707 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/]] 659 + 708 708 ((( 709 - Upgrade Instruction:[[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]661 +[[image:image-20220708140453-6.png]] 710 710 ))) 711 711 712 712 713 -== 2.11 Battery & Power Consumption == 714 714 666 +=== 2.9.2 Power consumption Analyze === 715 715 716 -NDDS75 uses ER26500 + SPC1520 battery pack. See below link for detail information about the battery info and how to replace. 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 +))) 717 717 718 -[[**Battery Info & Power Consumption Analyze**>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] . 719 719 673 +((( 674 +Instruction to use as below: 675 +))) 720 720 721 -= 3. Access NB-IoT Module = 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/]] 679 +))) 722 722 723 723 724 724 ((( 725 - Userscan directly accesstheATcommandsetofthe NB-IoT module.683 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 726 726 ))) 727 727 686 +* ((( 687 +Product Model 688 +))) 689 +* ((( 690 +Uplink Interval 691 +))) 692 +* ((( 693 +Working Mode 694 +))) 695 + 728 728 ((( 729 -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/]] 697 +And the Life expectation in difference case will be shown on the right. 698 +))) 730 730 731 - 700 +[[image:image-20220708141352-7.jpeg]] 701 + 702 + 703 + 704 +=== 2.9.3 Battery Note === 705 + 706 +((( 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. 732 732 ))) 733 733 734 -[[image:1657333200519-600.png]] 735 735 736 736 737 -= 4.UsingtheAT Commands=712 +=== 2.9.4 Replace the battery === 738 738 739 -== 4.1 Access AT Commands == 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 +))) 740 740 741 741 742 -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]] 743 743 720 += 3. Access NB-IoT Module = 744 744 745 -AT+<CMD>? : Help on <CMD> 722 +((( 723 +Users can directly access the AT command set of the NB-IoT module. 724 +))) 746 746 747 -AT+<CMD> : Run <CMD> 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 +))) 748 748 749 - AT+<CMD>=<value>:Set the value730 +[[image:1657261278785-153.png]] 750 750 751 -AT+<CMD>=? : Get the value 752 752 753 753 754 - (%style="color:#037691"%)**GeneralCommands**(%%)734 += 4. Using the AT Commands = 755 755 756 - AT:ttention736 +== 4.1 Access AT Commands == 757 757 758 - AT?ShortHelp738 +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/]] 759 759 760 -ATZ : MCU Reset 761 761 762 -AT+ TDC :ApplicationData TransmissionInterval741 +AT+<CMD>? : Help on <CMD> 763 763 764 -AT+C FGPrint all configurations743 +AT+<CMD> : Run <CMD> 765 765 766 -AT+C FGMOD:Workingmodeselection745 +AT+<CMD>=<value> : Set the value 767 767 768 -AT+ INTMOD:Set thetrigger interrupt mode747 +AT+<CMD>=? : Get the value 769 769 770 -AT+5VT : Set extend the time of 5V power 771 771 772 - AT+PRO: Chooseagreement750 +(% style="color:#037691" %)**General Commands**(%%) 773 773 774 -AT +WEIGRE:Getweightorsetweightto0752 +AT : Attention 775 775 776 -AT +WEIGAP:GetorSettheGapValueofweight754 +AT? : Short Help 777 777 778 -AT +RXDL:Extendthesendingandreceivingtime756 +ATZ : MCU Reset 779 779 780 -AT+ CNTFAC:Getorsetcountingparameters758 +AT+TDC : Application Data Transmission Interval 781 781 782 -AT+ SERVADDR:ServerAddress760 +AT+CFG : Print all configurations 783 783 784 -AT+ TRGetorSetrecordtime"762 +AT+CFGMOD : Working mode selection 785 785 786 -AT+ APNGetor set theAPN764 +AT+INTMOD : Set the trigger interrupt mode 787 787 788 -AT+ FBAND:GetorSetwhethertoautomaticallymodifythefrequencyband766 +AT+5VT : Set extend the time of 5V power 789 789 790 -AT+ DNSCFG:GetorSetDNSServer768 +AT+PRO : Choose agreement 791 791 792 -AT+ GETSENSORVALUE:Returnsthecurrentsensormeasurement770 +AT+WEIGRE : Get weight or set weight to 0 793 793 794 -AT+ NOUD:Get or Set thenumberofdata to beuploaded772 +AT+WEIGAP : Get or Set the GapValue of weight 795 795 796 -AT+ CDP:ReadorClearcacheddata774 +AT+RXDL : Extend the sending and receiving time 797 797 798 -AT+ LDDSALARM :Get orSet alarmof distance776 +AT+CNTFAC : Get or set counting parameters 799 799 778 +AT+SERVADDR : Server Address 800 800 780 + 801 801 (% style="color:#037691" %)**COAP Management** 802 802 803 -AT+URI : 783 +AT+URI : Resource parameters 804 804 805 805 806 806 (% style="color:#037691" %)**UDP Management** 807 807 808 -AT+CFM : 788 +AT+CFM : Upload confirmation mode (only valid for UDP) 809 809 810 810 811 811 (% style="color:#037691" %)**MQTT Management** 812 812 813 -AT+CLIENT 793 +AT+CLIENT : Get or Set MQTT client 814 814 815 -AT+UNAME :Get or Set MQTT Username795 +AT+UNAME : Get or Set MQTT Username 816 816 817 -AT+PWD 797 +AT+PWD : Get or Set MQTT password 818 818 819 -AT+PUBTOPIC :Get or Set MQTT publish topic799 +AT+PUBTOPIC : Get or Set MQTT publish topic 820 820 821 -AT+SUBTOPIC :Get or Set MQTT subscription topic801 +AT+SUBTOPIC : Get or Set MQTT subscription topic 822 822 823 823 824 824 (% style="color:#037691" %)**Information** 825 825 826 -AT+FDR : 806 +AT+FDR : Factory Data Reset 827 827 828 -AT+PWORD : 808 +AT+PWORD : Serial Access Password 829 829 830 830 811 + 831 831 = 5. FAQ = 832 832 833 833 == 5.1 How to Upgrade Firmware == ... ... @@ -842,10 +842,18 @@ 842 842 ))) 843 843 844 844 ((( 845 -(% 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. 846 846 ))) 847 847 848 848 830 + 831 +== 5.2 Can I calibrate NSE01 to different soil types? == 832 + 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 +))) 836 + 837 + 849 849 = 6. Trouble Shooting = 850 850 851 851 == 6.1 Connection problem when uploading firmware == ... ... @@ -860,26 +860,27 @@ 860 860 861 861 ))) 862 862 852 + 863 863 == 6.2 AT Command input doesn't work == 864 864 865 - 866 866 ((( 867 867 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. 857 + 858 + 868 868 ))) 869 869 870 870 871 -== 6.3 Not able to connect to NB-IoT network and keep showing "Signal Strength:99". == 872 - 873 - 874 -This means sensor is trying to join the NB-IoT network but fail. Please see this link for **//[[trouble shooting for signal strenght:99>>doc:Main.CSQ\:99,99.WebHome]]//**. 875 - 876 - 877 877 = 7. Order Info = 878 878 879 879 880 -Part Number**:** (% style="color:#4f81bd" %)**NS DDS75**865 +Part Number**:** (% style="color:#4f81bd" %)**NSE01** 881 881 882 882 868 +(% class="wikigeneratedid" %) 869 +((( 870 + 871 +))) 872 + 883 883 = 8. Packing Info = 884 884 885 885 ((( ... ... @@ -887,7 +887,7 @@ 887 887 888 888 (% style="color:#037691" %)**Package Includes**: 889 889 890 -* N DDS75NB-IoTDistanceDetectSensorNodex 1880 +* NSE01 NB-IoT Soil Moisture & EC Sensor x 1 891 891 * External antenna x 1 892 892 ))) 893 893 ... ... @@ -896,21 +896,18 @@ 896 896 897 897 (% style="color:#037691" %)**Dimension and weight**: 898 898 899 -* Device Size: 13.0 x 5 x 4.5 cm 900 -* Device Weight: 150g 901 -* Package Size / pcs : 15 x 12x 5.5 cm 902 -* Weight / pcs : 220g 889 +* Size: 195 x 125 x 55 mm 890 +* Weight: 420g 903 903 ))) 904 904 905 905 ((( 906 906 907 907 896 + 908 908 909 909 ))) 910 910 911 911 = 9. Support = 912 912 913 - 914 914 * 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. 915 - 916 916 * 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]]
- 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