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