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 (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 30 added, 0 removed)
- 1657261119050-993.png
- 1657261278785-153.png
- 1657271519014-786.png
- 1657327959271-447.png
- 1657328609906-564.png
- 1657328659945-416.png
- 1657328756309-230.png
- 1657328884227-504.png
- 1657329814315-101.png
- 1657330452568-615.png
- 1657330472797-498.png
- 1657330501006-241.png
- 1657330533775-472.png
- 1657330723006-866.png
- 1657331036973-987.png
- 1657332990863-496.png
- 1657333200519-600.png
- image-20220709084038-1.jpeg
- image-20220709084137-2.jpeg
- image-20220709084207-3.jpeg
- image-20220709084458-4.png
- image-20220709085040-1.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
Details
- Page properties
-
- Title
-
... ... @@ -1,1 +1,1 @@ 1 -NS E01-NB-IoTSoil Moisture&ECSensor User Manual1 +NDDS75 NB-IoT Distance Detect Sensor User Manual - Content
-
... ... @@ -1,64 +1,77 @@ 1 1 (% style="text-align:center" %) 2 -[[image:image-20220 606151504-2.jpeg||height="554" width="554"]]2 +[[image:image-20220709085040-1.png||height="542" width="524"]] 3 3 4 4 5 5 6 6 7 7 8 +**Table of Contents:** 8 8 10 +{{toc/}} 9 9 10 10 11 11 12 12 13 13 14 -**Table of Contents:** 15 15 17 += 1. Introduction = 16 16 17 17 20 +== 1.1 What is NDDS75 Distance Detection Sensor == 18 18 22 +((( 23 + 19 19 25 +((( 26 +((( 27 +The Dragino NDDS75 is a (% style="color:blue" %)**NB-IoT Distance Detection Sensor**(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data. 28 +))) 20 20 21 -= 1. Introduction = 30 +((( 31 +The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 32 +))) 22 22 23 -== 1.1 What is LoRaWAN Soil Moisture & EC Sensor == 34 +((( 35 +NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 36 +))) 24 24 25 25 ((( 26 - 39 +NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 40 +))) 27 27 28 -Dragino NSE01 is an (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory. 42 +((( 43 +NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 44 +))) 29 29 30 -It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly. 46 +((( 47 +To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 48 +))) 49 +))) 31 31 32 -The wireless technology used in NSE01 allows the device to send data at a low data rate and reach ultra-long distances, providing ultra-long-distance spread spectrum Communication. 33 - 34 -NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years. 35 - 36 36 37 37 ))) 38 38 39 -[[image:165 4503236291-817.png]]54 +[[image:1657327959271-447.png]] 40 40 41 41 42 -[[image:1657245163077-232.png]] 43 43 58 +== 1.2 Features == 44 44 45 45 46 -== 1.2 Features == 47 - 48 - 49 49 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 50 -* Monitor Soil Moisture 51 -* Monitor Soil Temperature 52 -* Monitor Soil Conductivity 62 +* Ultra low power consumption 63 +* Distance Detection by Ultrasonic technology 64 +* Flat object range 280mm - 7500mm 65 +* Accuracy: ±(1cm+S*0.3%) (S: Distance) 66 +* Cable Length: 25cm 53 53 * AT Commands to change parameters 54 54 * Uplink on periodically 55 55 * Downlink to change configure 56 56 * IP66 Waterproof Enclosure 57 -* Ultra-Low Power consumption 58 -* AT Commands to change parameters 59 59 * Micro SIM card slot for NB-IoT SIM 60 60 * 8500mAh Battery for long term use 61 61 74 + 62 62 == 1.3 Specification == 63 63 64 64 ... ... @@ -76,91 +76,120 @@ 76 76 * - B20 @H-FDD: 800MHz 77 77 * - B28 @H-FDD: 700MHz 78 78 79 -(% style="color:#037691" %)** Probe Specification:**92 +(% style="color:#037691" %)**Battery:** 80 80 81 -Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 94 +* Li/SOCI2 un-chargeable battery 95 +* Capacity: 8500mAh 96 +* Self Discharge: <1% / Year @ 25°C 97 +* Max continuously current: 130mA 98 +* Max boost current: 2A, 1 second 82 82 83 - [[image:image-20220708101224-1.png]]100 +(% style="color:#037691" %)**Power Consumption** 84 84 102 +* STOP Mode: 10uA @ 3.3v 103 +* Max transmit power: 350mA@3.3v 85 85 86 86 87 87 == 1.4 Applications == 88 88 108 + 109 +* Smart Buildings & Home Automation 110 +* Logistics and Supply Chain Management 111 +* Smart Metering 89 89 * Smart Agriculture 113 +* Smart Cities 114 +* Smart Factory 90 90 91 91 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 92 92 93 93 119 + 120 + 121 + 94 94 == 1.5 Pin Definitions == 95 95 96 96 97 -[[image:16572 46476176-652.png]]125 +[[image:1657328609906-564.png]] 98 98 99 99 100 100 101 -= 2. Use NS E01to communicate with IoT Server =129 += 2. Use NDDS75 to communicate with IoT Server = 102 102 131 + 103 103 == 2.1 How it works == 104 104 105 105 106 106 ((( 107 -The NS E01is equipped with a NB-IoT module, the pre-loaded firmware in NSE01will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NSE01.136 +The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75. 108 108 ))) 109 109 110 110 111 111 ((( 112 -The diagram below shows the working flow in default firmware of NS E01:141 +The diagram below shows the working flow in default firmware of NDDS75: 113 113 ))) 114 114 115 -[[image:image-20220708101605-2.png]] 116 - 117 117 ((( 118 118 119 119 ))) 120 120 148 +[[image:1657328659945-416.png]] 121 121 150 +((( 151 + 152 +))) 122 122 123 -== 2.2 Configure the NSE01 == 124 124 155 +== 2.2 Configure the NDDS75 == 125 125 157 + 126 126 === 2.2.1 Test Requirement === 127 127 128 128 129 -To use NSE01 in your city, make sure meet below requirements: 161 +((( 162 +To use NDDS75 in your city, make sure meet below requirements: 163 +))) 130 130 131 131 * Your local operator has already distributed a NB-IoT Network there. 132 -* The local NB-IoT network used the band that NS E01supports.166 +* The local NB-IoT network used the band that NDDS75 supports. 133 133 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 134 134 135 135 ((( 136 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The E01will 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 server170 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server. 137 137 ))) 138 138 139 139 140 -[[image:16572 49419225-449.png]]174 +[[image:1657328756309-230.png]] 141 141 142 142 143 143 144 144 === 2.2.2 Insert SIM card === 145 145 180 + 181 +((( 146 146 Insert the NB-IoT Card get from your provider. 183 +))) 147 147 185 +((( 148 148 User need to take out the NB-IoT module and insert the SIM card like below: 187 +))) 149 149 150 150 151 -[[image:16572 49468462-536.png]]190 +[[image:1657328884227-504.png]] 152 152 153 153 154 154 155 -=== 2.2.3 Connect USB – TTL to NS E01to configure it ===194 +=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 156 156 196 + 157 157 ((( 158 158 ((( 159 -User need to configure NS E01via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NSE01support AT Commands, user can use a USB to TTL adapter to connect to NSE01and use AT Commands to configure it, as below.199 +User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below. 160 160 ))) 161 161 ))) 162 162 203 +[[image:image-20220709092052-2.png]] 163 163 205 + 164 164 **Connection:** 165 165 166 166 (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND ... ... @@ -179,70 +179,90 @@ 179 179 * Flow Control: (% style="color:green" %)**None** 180 180 181 181 ((( 182 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NS E01. NSE01will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.224 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input. 183 183 ))) 184 184 185 -[[image: image-20220708110657-3.png]]227 +[[image:1657329814315-101.png]] 186 186 187 -(% 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/]] 188 188 230 +((( 231 +(% 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]]** 232 +))) 189 189 190 190 235 + 191 191 === 2.2.4 Use CoAP protocol to uplink data === 192 192 193 -(% 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/]] 194 194 239 +(% 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/]]** 195 195 241 + 242 +((( 196 196 **Use below commands:** 244 +))) 197 197 198 -* (% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 199 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 200 -* (% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 246 +* ((( 247 +(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 248 +))) 249 +* ((( 250 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 251 +))) 252 +* ((( 253 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 201 201 255 + 256 + 257 +))) 258 + 259 +((( 202 202 For parameter description, please refer to AT command set 203 203 204 -[[image:1657249793983-486.png]] 262 + 263 +))) 205 205 265 +[[image:1657330452568-615.png]] 206 206 207 -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. 208 208 209 -[[image:1657249831934-534.png]] 210 210 269 +((( 270 +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. 211 211 272 + 273 +))) 212 212 213 - === 2.2.5 Use UDP protocol to uplink data(Defaultprotocol) ===275 +[[image:1657330472797-498.png]] 214 214 215 -This feature is supported since firmware version v1.0.1 216 216 217 217 218 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 279 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 280 + 281 + 282 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 219 219 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 220 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/If the server does not respond, this command is unnecessary 284 +* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 221 221 222 -[[image:1657 249864775-321.png]]286 +[[image:1657330501006-241.png]] 223 223 224 224 225 -[[image:1657 249930215-289.png]]289 +[[image:1657330533775-472.png]] 226 226 227 227 228 228 229 229 === 2.2.6 Use MQTT protocol to uplink data === 230 230 231 -This feature is supported since firmware version v110 232 232 296 +* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 297 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 298 +* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 299 +* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 300 +* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 301 +* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 302 +* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 233 233 234 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 235 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 236 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 237 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 238 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 239 -* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB **(%%)~/~/Set the sending topic of MQTT 240 -* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB **(%%) ~/~/Set the subscription topic of MQTT 241 - 242 242 [[image:1657249978444-674.png]] 243 243 244 244 245 -[[image:16572 49990869-686.png]]307 +[[image:1657330723006-866.png]] 246 246 247 247 248 248 ((( ... ... @@ -253,177 +253,238 @@ 253 253 254 254 === 2.2.7 Use TCP protocol to uplink data === 255 255 256 -This feature is supported since firmware version v110 257 257 258 - 259 259 * (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 260 260 * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 261 261 262 -[[image: 1657250217799-140.png]]322 +[[image:image-20220709093918-1.png]] 263 263 264 264 265 -[[image: 1657250255956-604.png]]325 +[[image:image-20220709093918-2.png]] 266 266 267 267 268 268 269 269 === 2.2.8 Change Update Interval === 270 270 331 + 271 271 User can use below command to change the (% style="color:green" %)**uplink interval**. 272 272 273 273 * (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 274 274 275 275 ((( 276 -(% style="color:red" %)**NOTE:** 277 -))) 337 +(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.** 278 278 279 -((( 280 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 339 + 281 281 ))) 282 282 342 +(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:** 283 283 344 +(% 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).** 284 284 346 + 347 + 285 285 == 2.3 Uplink Payload == 286 286 287 -In this mode, uplink payload includes in total 18 bytes 288 288 289 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 290 -|=(% style="width: 50px;" %)((( 351 +=== 2.3.1 Before Firmware 1.3.2 === 352 + 353 + 354 +In this mode, uplink payload includes in total 14 bytes 355 + 356 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 357 +|=(% style="width: 60px;" %)((( 291 291 **Size(bytes)** 292 -)))|=(% style="width: 50px;" %)**6**|=(% style="width:25px;" %)2|=(% style="width:25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width:80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width:80px;" %)**2**|=(% style="width: 40px;" %)**1**293 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H "]]|(% style="width:108px" %)[[SoilMoisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px"%)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]359 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 360 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]] 294 294 295 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 362 +((( 363 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 364 +))) 296 296 297 297 298 -[[image: image-20220708111918-4.png]]367 +[[image:1657331036973-987.png]] 299 299 300 300 301 -The payload is ASCII string, representative same HEX: 370 +((( 371 +The payload is **ASCII** string, representative same HEX: 372 +))) 302 302 303 -0x72403155615900640c7817075e0a8c02f900 where: 374 +((( 375 +0x72403155615900640c6c19029200 where: 376 +))) 304 304 305 -* Device ID: 0x 724031556159 = 724031556159 306 -* Version: 0x0064=100=1.0.0 378 +* ((( 379 +Device ID: 0x724031556159 = 724031556159 380 +))) 381 +* ((( 382 +Version: 0x0064=100=1.0.0 383 +))) 307 307 308 -* BAT: 0x0c78 = 3192 mV = 3.192V 309 -* Singal: 0x17 = 23 310 -* Soil Moisture: 0x075e= 1886 = 18.86 % 311 -* Soil Temperature:0x0a8c =2700=27 °C 312 -* Soil Conductivity(EC) = 0x02f9 =761 uS /cm 313 -* Interrupt: 0x00 = 0 385 +* ((( 386 +BAT: 0x0c6c = 3180 mV = 3.180V 387 +))) 388 +* ((( 389 +Signal: 0x19 = 25 390 +))) 391 +* ((( 392 +Distance: 0x0292= 658 mm 393 +))) 394 +* ((( 395 +Interrupt: 0x00 = 0 314 314 315 -== 2.4 Payload Explanation and Sensor Interface == 316 316 317 317 318 -=== 2.4.1 Device ID === 319 319 320 -By default, the Device ID equal to the last 6 bytes of IMEI. 400 + 401 +))) 321 321 322 - User can use (% style="color:blue"%)**AT+DEUI**(%%)to setDeviceID403 +=== **2.3.2 Since firmware v1.3.2** === 323 323 324 -**Example:** 325 325 326 - AT+DEUI=A84041F15612406 +In this mode, uplink payload includes 69 bytes in total by default. 327 327 328 - TheDeviceID is storedinanone-erasearea, Upgrade thefirmware orrunAT+FDRwon'teraseDeviceID.408 +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. 329 329 410 +(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 411 +|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4 412 +|(% 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....... 330 330 414 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 331 331 332 - ===2.4.2 VersionInfo ===416 +[[image:image-20220908175246-1.png]] 333 333 334 -Specify the software version: 0x64=100, means firmware version 1.00. 335 335 336 - Forexample: 0x00 64 : thisdeviceisNSE01with firmwarersion1.0.0.419 +The payload is ASCII string, representative same HEX: 337 337 421 +0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where: 338 338 423 +* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 424 +* (% style="color:red" %)Version: 0x0084=132=1.3.2 425 +* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 426 +* (% style="color:blue" %)Singal: 0x1e = 30 427 +* (% style="color:red" %)Mod: 0x01 = 1 428 +* Interrupt: 0x00= 0 429 +* Distance: 0x0039= 57 = 57 430 +* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 431 +* Distance,Time stamp : 00396319baf0 432 +* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 339 339 340 -=== 2.4.3 Battery Info === 341 341 435 +== 2.4 Payload Explanation and Sensor Interface == 436 + 437 + 438 +=== 2.4.1 Device ID === 439 + 440 + 342 342 ((( 343 - CheckthebatteryvoltageforLSE01.442 +By default, the Device ID equal to the last 6 bytes of IMEI. 344 344 ))) 345 345 346 346 ((( 347 -Ex1: 0x0B45 = 2885mV 446 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 447 + 448 + 348 348 ))) 349 349 350 350 ((( 351 - Ex2:0x0B49=2889mV452 +(% style="color:blue" %)**Example :** 352 352 ))) 353 353 455 +((( 456 +AT+DEUI=A84041F15612 457 +))) 354 354 459 +((( 460 +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. 461 +))) 355 355 356 -=== 2.4.4 Signal Strength === 357 357 358 - NB-IoTNetworksignalStrength.464 +(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:** 359 359 360 -** Ex1:0x1d=29**466 +(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.** 361 361 362 -(% style="color:blue" %)** 0**(%%)-113dBmorless468 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 363 363 364 -(% style="color:blue" %)**1**(%%) -111dBm 365 365 366 -(% style="color:blue" %)** 2...30**(%%) -109dBm...-53dBm471 +(% style="color:blue" %)**Example :** 367 367 368 - (% style="color:blue" %)**31** (%%) -51dBm or greater473 +AT+DEUI=868411056754138 369 369 370 -(% style="color:blue" %)**99** (%%) Not known or not detectable 371 371 372 372 477 +=== 2.4.2 Version Info === 373 373 374 -=== 2.4.5 Soil Moisture === 375 375 376 376 ((( 377 - Get the moisturecontent of the soil. The valuerangeof theegisteris0-10000(Decimal),dividethis value by 100 to get the percentageofmoisturein theoil.481 +Specify the software version: 0x64=100, means firmware version 1.00. 378 378 ))) 379 379 380 380 ((( 381 -For example ,ifthedatayou getfrom theregisteris**__0x050xDC__**,themoisturecontentinthe soil is485 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 382 382 ))) 383 383 488 + 489 + 490 +=== 2.4.3 Battery Info === 491 + 492 + 384 384 ((( 385 - 494 +Ex1: 0x0B45 = 2885mV 386 386 ))) 387 387 388 388 ((( 389 - (% style="color:#4f81bd"%)**05DC(H) = 1500(D)/100=15%.**498 +Ex2: 0x0B49 = 2889mV 390 390 ))) 391 391 392 392 393 393 394 -=== 2.4. 6SoilTemperature ===503 +=== 2.4.4 Signal Strength === 395 395 505 + 396 396 ((( 397 - Get the temperature in the soil.Thevaluerange oftheregisteris-4000 - +800(Decimal), divide this value by 100 toget the temperature inthe soil. For example,ifthe data you get from theregister is __**0x09 0xEC**__, the temperature content in the soil is507 +NB-IoT Network signal Strength. 398 398 ))) 399 399 400 400 ((( 401 -**Ex ample**:511 +**Ex1: 0x1d = 29** 402 402 ))) 403 403 404 404 ((( 405 - Ifpayload is 0105H:((0x0105&0x8000)>>15===0),temp=0105(H)/100=2.61 °C515 +(% style="color:blue" %)**0**(%%) -113dBm or less 406 406 ))) 407 407 408 408 ((( 409 - Ifpayload is FF7EH: ((FF7E&0x8000)>>15===1),temp=(FF7E(H)-FFFF(H))/100=-1.29 °C519 +(% style="color:blue" %)**1**(%%) -111dBm 410 410 ))) 411 411 522 +((( 523 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 524 +))) 412 412 526 +((( 527 +(% style="color:blue" %)**31** (%%) -51dBm or greater 528 +))) 413 413 414 -=== 2.4.7 Soil Conductivity (EC) === 415 - 416 416 ((( 417 - Obtain(% style="color:#4f81bd" %)**__soluble salt concentration__**(%%)insoilor (% style="color:#4f81bd"%)**__soluble ionconcentrationinliquid fertilizer__**(%%)or (% style="color:#4f81bd"%)**__planting medium__**(%%). Thevalue range oftheregister is 0 - 20000(Decimal)( Canbegreater than 20000).531 +(% style="color:blue" %)**99** (%%) Not known or not detectable 418 418 ))) 419 419 534 + 535 + 536 +=== 2.4.5 Distance === 537 + 538 + 539 +Get the distance. Flat object range 280mm - 7500mm. 540 + 420 420 ((( 421 -For example, if the data you get from the register is __**0x000xC8**__, thesoil conductivityis00C8(H)=200(D) = 200uS/cm.542 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 422 422 ))) 423 423 424 424 ((( 425 -Generally, the EC value of irrigation water is less than 800uS / cm. 546 +((( 547 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 426 426 ))) 549 +))) 427 427 428 428 ((( 429 429 ... ... @@ -433,45 +433,73 @@ 433 433 434 434 ))) 435 435 436 -=== 2.4. 8Digital Interrupt ===559 +=== 2.4.6 Digital Interrupt === 437 437 438 -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. 439 439 562 +((( 563 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server. 564 +))) 565 + 566 +((( 440 440 The command is: 568 +))) 441 441 570 +((( 442 442 (% 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]])**.** 572 +))) 443 443 444 444 445 -The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up. 575 +((( 576 +The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up. 577 +))) 446 446 447 447 580 +((( 448 448 Example: 582 +))) 449 449 584 +((( 450 450 0x(00): Normal uplink packet. 586 +))) 451 451 588 +((( 452 452 0x(01): Interrupt Uplink Packet. 590 +))) 453 453 454 454 455 455 456 -=== 2.4. 9+5V Output ===594 +=== 2.4.7 +5V Output === 457 457 458 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 459 459 597 +((( 598 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 599 +))) 460 460 601 + 602 +((( 461 461 The 5V output time can be controlled by AT Command. 462 462 605 + 606 +))) 607 + 608 +((( 463 463 (% style="color:blue" %)**AT+5VT=1000** 464 464 611 + 612 +))) 613 + 614 +((( 465 465 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 616 +))) 466 466 467 467 468 468 469 469 == 2.5 Downlink Payload == 470 470 471 -By default, NSE01 prints the downlink payload to console port. 472 472 473 - [[image:image-20220708133731-5.png]]623 +By default, NDDS75 prints the downlink payload to console port. 474 474 625 +[[image:image-20220709100028-1.png]] 475 475 476 476 477 477 ((( ... ... @@ -507,435 +507,385 @@ 507 507 ))) 508 508 509 509 ((( 510 -If payload = 0x04FF, it will reset the NS E01661 +If payload = 0x04FF, it will reset the NDDS75 511 511 ))) 512 512 513 513 514 514 * (% style="color:blue" %)**INTMOD** 515 515 667 +((( 516 516 Downlink Payload: 06000003, Set AT+INTMOD=3 669 +))) 517 517 518 518 519 519 520 -== 2.6 LEDIndicator ==673 +== 2.6 Distance alarm function(Since firmware v1.3.2) == 521 521 522 -((( 523 -The NSE01 has an internal LED which is to show the status of different state. 524 524 676 +(% style="color:blue" %)** ➢ AT Command:** 525 525 526 -* 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) 527 -* Then the LED will be on for 1 second means device is boot normally. 528 -* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds. 529 -* For each uplink probe, LED will be on for 500ms. 530 -))) 678 +(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 531 531 680 +² When min=0, and max≠0, Alarm higher than max 532 532 682 +² When min≠0, and max=0, Alarm lower than min 533 533 684 +² When min≠0 and max≠0, Alarm higher than max or lower than min 534 534 535 -== 2.7 Installation in Soil == 536 536 537 - __**Measurementthesoilsurface**__687 +(% style="color:blue" %)** Example:** 538 538 539 - Choosethe proper measuring position.Avoidtheprobetotouch rocks or hard things. Split the surface soil according to themeasureddeep. Keep themeasured as originaldensity. Vertical insertthe probe into the soiltobemeasured.Make sure notshake wheninserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]689 +**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 540 540 541 -[[image:1657259653666-883.png]] 542 542 543 543 544 -((( 545 - 693 +== 2.7 Set the number of data to be uploaded and the recording time == 546 546 547 -((( 548 -Dig a hole with diameter > 20CM. 549 -))) 550 550 551 -((( 552 -Horizontal insert the probe to the soil and fill the hole for long term measurement. 553 -))) 554 -))) 696 +(% style="color:blue" %)** ➢ AT Command:** 555 555 556 - [[image:1654506665940-119.png]]698 +(% 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) 557 557 558 -((( 559 - 560 -))) 700 +(% 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. 561 561 562 562 563 -== 2.8 Firmware Change Log == 564 564 704 +== 2.8 Read or Clear cached data == 565 565 566 -Download URL & Firmware Change log 567 567 568 - [[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]707 +(% style="color:blue" %)** ➢ AT Command:** 569 569 709 +(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 570 570 571 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H"]] 572 572 712 +[[image:image-20220908175333-2.png]] 573 573 574 574 575 - ==2.9BatteryAnalysis==715 +(% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 576 576 577 -=== 2.9.1 Battery Type === 578 578 579 579 580 - TheNSE01 battery is a combination of an 8500mAh Li/SOCI2Battery and a Super Capacitor.Thebattery isnone-rechargeable battery type with a lowdischarge rate (<2% per year). This typeof batteryis commonly used in IoT devices such as water meter.719 +== 2.9 LED Indicator == 581 581 582 582 583 -The batteryisdesignedto last for severalyearsdepends onthe actually useenvironment and updateinterval.722 +The NDDS75 has an internal LED which is to show the status of different state. 584 584 585 585 586 -The battery related documents as below: 725 +* 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) 726 +* Then the LED will be on for 1 second means device is boot normally. 727 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 728 +* For each uplink probe, LED will be on for 500ms. 587 587 588 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 589 -* [[Lithium-Thionyl Chloride Battery>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]][[ datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 590 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 591 - 592 592 ((( 593 - [[image:image-20220708140453-6.png]]731 + 594 594 ))) 595 595 596 596 597 597 598 -2. 9.2736 +== 2.10 Firmware Change Log == 599 599 600 -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. 601 601 739 +((( 740 +Download URL & Firmware Change log: [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]] 741 +))) 602 602 603 -Instruction to use as below: 743 +((( 744 + 745 +))) 604 604 747 +((( 748 +Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 749 +))) 605 605 606 -Step 1: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: 607 607 608 -[[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/]] 609 609 753 +== 2.11 Battery Analysis == 610 610 611 -Step 2: Open it and choose 612 612 613 -* Product Model 614 -* Uplink Interval 615 -* Working Mode 756 +=== 2.11.1 Battery Type === 616 616 617 -And the Life expectation in difference case will be shown on the right. 618 618 759 +((( 760 +The NDDS75 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. 761 +))) 619 619 763 +((( 764 +The battery is designed to last for several years depends on the actually use environment and update interval. 765 +))) 620 620 621 -=== 2.9.3 Battery Note === 622 - 623 623 ((( 624 -The Li-SICObatteryis designed forsmall current /long periodapplication. It is not good to usea high current, short periodtransmit method. The recommended minimumperiod for use of this battery is 5 minutes.If you useahorterperiod time to transmit LoRa, then thebatterylife may be decreased.768 +The battery related documents as below: 625 625 ))) 626 626 771 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 772 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 773 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 627 627 775 +((( 776 +[[image:image-20220709101450-2.png]] 777 +))) 628 628 629 -=== 2.9.4 Replace the battery === 630 630 631 -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). 632 632 781 +=== 2.11.2 Power consumption Analyze === 633 633 634 634 635 -= 3. Using the AT Commands = 784 +((( 785 +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. 786 +))) 636 636 637 -== 3.1 Access AT Commands == 638 638 789 +((( 790 +Instruction to use as below: 791 +))) 639 639 640 -LSE01 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LSE01 for using AT command, as below. 793 +((( 794 +(% 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/]] 795 +))) 641 641 642 -[[image:1654501986557-872.png||height="391" width="800"]] 643 643 798 +((( 799 +(% style="color:blue" %)**Step 2: **(%%) Open it and choose 800 +))) 644 644 645 -Or if you have below board, use below connection: 802 +* ((( 803 +Product Model 804 +))) 805 +* ((( 806 +Uplink Interval 807 +))) 808 +* ((( 809 +Working Mode 810 +))) 646 646 812 +((( 813 +And the Life expectation in difference case will be shown on the right. 814 +))) 647 647 648 -[[image: 1654502005655-729.png||height="503" width="801"]]816 +[[image:image-20220709110451-3.png]] 649 649 650 650 651 651 652 - In the PC, you need to set the serial baud rate to (% style="color:green"%)**9600**(%%) to access the serial console for LSE01.LSE01 will outputsystem info once power on as below:820 +=== 2.11.3 Battery Note === 653 653 654 654 655 - [[image:1654502050864-459.png||height="564" width="806"]] 823 +((( 824 +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. 825 +))) 656 656 657 657 658 -Below are the available commands, a more detailed AT Command manual can be found at [[AT Command Manual>>https://www.dropbox.com/sh/qr6vproz4z4kzjz/AAAD48h3OyWrU1hq_Cqm8jIwa?dl=0]]: [[https:~~/~~/www.dropbox.com/sh/qr6vproz4z4kzjz/AAAD48h3OyWrU1hq_Cqm8jIwa?dl=0>>https://www.dropbox.com/sh/qr6vproz4z4kzjz/AAAD48h3OyWrU1hq_Cqm8jIwa?dl=0]] 659 659 829 +=== 2.11.4 Replace the battery === 660 660 661 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD> 662 662 663 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD> 832 +((( 833 +The default battery pack of NDDS75 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). 834 +))) 664 664 665 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value 666 666 667 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%) : Get the value 668 668 838 += 3. Access NB-IoT Module = 669 669 670 -(% style="color:#037691" %)**General Commands**(%%) 671 671 672 -(% style="background-color:#dcdcdc" %)**AT**(%%) : Attention 841 +((( 842 +Users can directly access the AT command set of the NB-IoT module. 843 +))) 673 673 674 -(% style="background-color:#dcdcdc" %)**AT?**(%%) : Short Help 845 +((( 846 +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/]] 675 675 676 -(% style="background-color:#dcdcdc" %)**ATZ**(%%) : MCU Reset 848 + 849 +))) 677 677 678 - (% style="background-color:#dcdcdc" %)**AT+TDC**(%%) : ApplicationData Transmission Interval851 +[[image:1657333200519-600.png]] 679 679 680 680 681 -(% style="color:#037691" %)**Keys, IDs and EUIs management** 682 682 683 - (%style="background-color:#dcdcdc"%)**AT+APPEUI**(%%): ApplicationEUI855 += 4. Using the AT Commands = 684 684 685 -(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%) : Application Key 686 686 687 - (% style="background-color:#dcdcdc"%)**AT+APPSKEY**(%%):Application SessionKey858 +== 4.1 Access AT Commands == 688 688 689 -(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%) : Device Address 690 690 691 - (%style="background-color:#dcdcdc" %)**AT+DEUI**(%%) : Device EUI861 +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]] 692 692 693 -(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%) : Network ID (You can enter this command change only after successful network connection) 694 694 695 - (% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%):NetworkSessionKeyJoiningandsendingdateonLoRanetwork864 +AT+<CMD>? : Help on <CMD> 696 696 697 - (% style="background-color:#dcdcdc" %)**AT+CFM**(%%)ConfirmMode866 +AT+<CMD> : Run <CMD> 698 698 699 - (% style="background-color:#dcdcdc" %)**AT+CFS**(%%):ConfirmStatus868 +AT+<CMD>=<value> : Set the value 700 700 701 - (% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)Join LoRa? Network870 +AT+<CMD>=? : Get the value 702 702 703 -(% style="background-color:#dcdcdc" %)**AT+NJM**(%%) : LoRa? Network Join Mode 704 704 705 -(% style=" background-color:#dcdcdc" %)**AT+NJS**(%%): LoRa? Network Join Status873 +(% style="color:#037691" %)**General Commands**(%%) 706 706 707 - (%style="background-color:#dcdcdc" %)**AT+RECV**(%%): Print Last Received Data in Raw Format875 +AT : Attention 708 708 709 - (% style="background-color:#dcdcdc" %)**AT+RECVB**(%%):PrintLastReceivedDatainBinaryFormat877 +AT? : Short Help 710 710 711 - (% style="background-color:#dcdcdc" %)**AT+SEND**(%%)SendTextData879 +ATZ : MCU Reset 712 712 713 - (% style="background-color:#dcdcdc" %)**AT+SENB**(%%):SendHexadecimalData881 +AT+TDC : Application Data Transmission Interval 714 714 883 +AT+CFG : Print all configurations 715 715 716 - (%style="color:#037691"%)**LoRa NetworkManagement**885 +AT+CFGMOD : Working mode selection 717 717 718 - (% style="background-color:#dcdcdc" %)**AT+ADR**(%%):AdaptiveRate887 +AT+INTMOD : Set the trigger interrupt mode 719 719 720 - (% style="background-color:#dcdcdc" %)**AT+CLASS**(%%):LoRaClass(Currentlyonlysupportclass A889 +AT+5VT : Set extend the time of 5V power 721 721 722 - (% style="background-color:#dcdcdc" %)**AT+DCS**(%%):DutyCycleSetting891 +AT+PRO : Choose agreement 723 723 724 - (% style="background-color:#dcdcdc" %)**AT+DR**(%%):DataRate(CanOnly beModifiedafterADR=0)893 +AT+WEIGRE : Get weight or set weight to 0 725 725 726 - (% style="background-color:#dcdcdc" %)**AT+FCD**(%%):FrameCounterDownlink895 +AT+WEIGAP : Get or Set the GapValue of weight 727 727 728 - (% style="background-color:#dcdcdc" %)**AT+FCU**(%%):FrameCounterUplink897 +AT+RXDL : Extend the sending and receiving time 729 729 730 - (% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%):JoinAcceptDelay1899 +AT+CNTFAC : Get or set counting parameters 731 731 732 - (% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%):JoinAccept Delay2901 +AT+SERVADDR : Server Address 733 733 734 - (% style="background-color:#dcdcdc" %)**AT+PNM**(%%)Public NetworkMode903 +AT+TR : Get or Set record time" 735 735 736 - (% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%):ReceiveDelay1905 +AT+APN : Get or set the APN 737 737 738 - (% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%):ReceiveDelay2907 +AT+FBAND : Get or Set whether to automatically modify the frequency band 739 739 740 - (% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%):Rx2WindowDataRate909 +AT+DNSCFG : Get or Set DNS Server 741 741 742 - (% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)x2WindowFrequency911 +AT+GETSENSORVALUE : Returns the current sensor measurement 743 743 744 - (% style="background-color:#dcdcdc" %)**AT+TXP**(%%): TransmitPower913 +AT+NOUD : Get or Set the number of data to be uploaded 745 745 746 - (% style="background-color:#dcdcdc" %)**AT+MOD**(%%)Setworkmode915 +AT+CDP : Read or Clear cached data 747 747 917 +AT+LDDSALARM : Get or Set alarm of distance 748 748 749 -(% style="color:#037691" %)**Information** 750 750 751 -(% style=" background-color:#dcdcdc" %)**AT+RSSI**(%%): RSSI of the Last Received Packet920 +(% style="color:#037691" %)**COAP Management** 752 752 753 - (% style="background-color:#dcdcdc" %)**AT+SNR**(%%):SNRof theLast ReceivedPacket922 +AT+URI : Resource parameters 754 754 755 -(% style="background-color:#dcdcdc" %)**AT+VER**(%%) : Image Version and Frequency Band 756 756 757 -(% style=" background-color:#dcdcdc" %)**AT+FDR**(%%): Factory Data Reset925 +(% style="color:#037691" %)**UDP Management** 758 758 759 - (% style="background-color:#dcdcdc" %)**AT+PORT**(%%)ApplicationPort927 +AT+CFM : Upload confirmation mode (only valid for UDP) 760 760 761 -(% style="background-color:#dcdcdc" %)**AT+CHS**(%%) : Get or Set Frequency (Unit: Hz) for Single Channel Mode 762 762 763 - background-color:#dcdcdc" %)**AT+CHE**(%%): Get or Set eight channelsmode, Only for US915, AU915, CN470930 +(% style="color:#037691" %)**MQTT Management** 764 764 932 +AT+CLIENT : Get or Set MQTT client 765 765 766 - =4.FAQ=934 +AT+UNAME : Get or Set MQTT Username 767 767 768 - ==4.1How to changeheLoRa FrequencyBands/Region? ==936 +AT+PWD : Get or Set MQTT password 769 769 770 -((( 771 -You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]]. 772 -When downloading the images, choose the required image file for download. 773 -))) 938 +AT+PUBTOPIC : Get or Set MQTT publish topic 774 774 775 -((( 776 - 777 -))) 940 +AT+SUBTOPIC : Get or Set MQTT subscription topic 778 778 779 -((( 780 -How to set up LSE01 to work in 8 channel mode By default, the frequency bands US915, AU915, CN470 work in 72 frequencies. Many gateways are 8 channel gateways, and in this case, the OTAA join time and uplink schedule is long and unpredictable while the end node is hopping in 72 frequencies. 781 -))) 782 782 783 -((( 784 - 785 -))) 943 +(% style="color:#037691" %)**Information** 786 786 787 -((( 788 -You can configure the end node to work in 8 channel mode by using the AT+CHE command. The 500kHz channels are always included for OTAA. 789 -))) 945 +AT+FDR : Factory Data Reset 790 790 791 -((( 792 - 793 -))) 947 +AT+PWORD : Serial Access Password 794 794 795 -((( 796 -For example, in **US915** band, the frequency table is as below. By default, the end node will use all channels (0~~71) for OTAA Join process. After the OTAA Join, the end node will use these all channels (0~~71) to send uplink packets. 797 -))) 798 798 799 -[[image:image-20220606154726-3.png]] 800 800 951 += 5. FAQ = 801 801 802 -When you use the TTN network, the US915 frequency bands use are: 803 803 804 -* 903.9 - SF7BW125 to SF10BW125 805 -* 904.1 - SF7BW125 to SF10BW125 806 -* 904.3 - SF7BW125 to SF10BW125 807 -* 904.5 - SF7BW125 to SF10BW125 808 -* 904.7 - SF7BW125 to SF10BW125 809 -* 904.9 - SF7BW125 to SF10BW125 810 -* 905.1 - SF7BW125 to SF10BW125 811 -* 905.3 - SF7BW125 to SF10BW125 812 -* 904.6 - SF8BW500 954 +== 5.1 How to Upgrade Firmware == 813 813 814 -((( 815 -Because the end node is now hopping in 72 frequency, it makes it difficult for the devices to Join the TTN network and uplink data. To solve this issue, you can access the device via the AT commands and run: 816 816 817 -* (% style="color:#037691" %)**AT+CHE=2** 818 -* (% style="color:#037691" %)**ATZ** 819 -))) 820 - 821 821 ((( 822 - 823 - 824 -to set the end node to work in 8 channel mode. The device will work in Channel 8-15 & 64-71 for OTAA, and channel 8-15 for Uplink. 958 +User can upgrade the firmware for 1) bug fix, 2) new feature release. 825 825 ))) 826 826 827 827 ((( 828 - 962 +Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]] 829 829 ))) 830 830 831 831 ((( 832 - The **AU915**bandissimilar.Beloware theAU915UplinkChannels.966 +(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.** 833 833 ))) 834 834 835 -[[image:image-20220606154825-4.png]] 836 836 837 837 838 -= =4.2Can I calibrateLSE01 todifferentsoil types?==971 += 6. Trouble Shooting = 839 839 840 -LSE01 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/index.php?dir=LoRa_End_Node/LSE01/&file=Calibrate_to_other_Soil_20220605.pdf]]. 841 841 974 +== 6.1 Connection problem when uploading firmware == 842 842 843 -= 5. Trouble Shooting = 844 844 845 -== 5.1 Why I can't join TTN in US915 / AU915 bands? == 846 - 847 -It is due to channel mapping. Please see the [[Eight Channel Mode>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H7.19EightChannelMode"]] section above for details. 848 - 849 - 850 -== 5.2 AT Command input doesn't work == 851 - 852 852 ((( 853 - In thecaseif user can seethe console outputbut can't typeinput tothe device. Please checkif youalready includethe (%yle="color:green"%)**ENTER**(%%) whileendingouthecommand. Someserial tooldoesn'tsend (% style="color:green"%)**ENTER**(%%) whileess the sendkey,userneed toadd ENTER in theirstring.978 +**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]] 854 854 ))) 855 855 856 - 857 -== 5.3 Device rejoin in at the second uplink packet == 858 - 859 -(% style="color:#4f81bd" %)**Issue describe as below:** 860 - 861 -[[image:1654500909990-784.png]] 862 - 863 - 864 -(% style="color:#4f81bd" %)**Cause for this issue:** 865 - 981 +(% class="wikigeneratedid" %) 866 866 ((( 867 - Thefuse on LSE01 is not large enough, some of the soil probe require large current up to 5v 800mA, in a short pulse. When this happen, it cause the device reboot so user see rejoin.983 + 868 868 ))) 869 869 870 870 871 - (% style="color:#4f81bd"%)**Solution:**987 +== 6.2 AT Command input doesn't work == 872 872 873 -All new shipped LSE01 after 2020-May-30 will have this to fix. For the customer who see this issue, please bypass the fuse as below: 874 874 875 -[[image:1654500929571-736.png||height="458" width="832"]] 990 +((( 991 +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. 876 876 993 + 994 +))) 877 877 878 -= 6. Order Info = 879 879 997 += 7. Order Info = 880 880 881 -Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY** 882 882 1000 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75** 883 883 884 -(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band 885 885 886 -* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band 887 -* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band 888 -* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band 889 -* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band 890 -* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band 891 -* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band 892 -* (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 893 -* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 894 - 895 -(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option 896 - 897 -* (% style="color:red" %)**4**(%%): 4000mAh battery 898 -* (% style="color:red" %)**8**(%%): 8500mAh battery 899 - 900 900 (% class="wikigeneratedid" %) 901 901 ((( 902 902 903 903 ))) 904 904 905 -= 7. Packing Info =1008 += 8. Packing Info = 906 906 907 907 ((( 908 908 909 909 910 910 (% style="color:#037691" %)**Package Includes**: 911 -))) 912 912 913 -* (((914 - LSE01LoRaWAN SoilMoisture& EC Sensorx 11015 +* NDDS75 NB-IoT Distance Detect Sensor Node x 1 1016 +* External antenna x 1 915 915 ))) 916 916 917 917 ((( 918 918 919 919 1022 + 920 920 (% style="color:#037691" %)**Dimension and weight**: 921 -))) 922 922 923 -* ((( 924 -Device Size: cm 1025 +* Device Size: 13.0 x 5 x 4.5 cm 1026 +* Device Weight: 150g 1027 +* Package Size / pcs : 15 x 12x 5.5 cm 1028 +* Weight / pcs : 220g 925 925 ))) 926 -* ((( 927 -Device Weight: g 928 -))) 929 -* ((( 930 -Package Size / pcs : cm 931 -))) 932 -* ((( 933 -Weight / pcs : g 934 934 1031 +((( 935 935 1033 + 1034 + 1035 + 936 936 ))) 937 937 938 -= 8. Support =1038 += 9. Support = 939 939 1040 + 940 940 * 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. 941 941 * 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]]
- 1657261119050-993.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- 1657261278785-153.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- 1657271519014-786.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +71.5 KB - Content
- 1657327959271-447.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.3 KB - Content
- 1657328609906-564.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +492.6 KB - Content
- 1657328659945-416.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.8 KB - Content
- 1657328756309-230.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.5 KB - Content
- 1657328884227-504.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +483.6 KB - Content
- 1657329814315-101.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +85.3 KB - Content
- 1657330452568-615.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +71.3 KB - Content
- 1657330472797-498.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +68.9 KB - Content
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +83.8 KB - Content
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +126.1 KB - Content
- image-20220709084038-1.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084137-2.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084207-3.jpeg
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +72.0 KB - Content
- image-20220709084458-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +199.5 KB - Content
- image-20220709085040-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +200.4 KB - Content
- image-20220709092052-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +247.3 KB - Content
- image-20220709093918-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +42.2 KB - Content
- image-20220709093918-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +61.9 KB - Content
- image-20220709100028-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +8.8 KB - Content
- image-20220709101450-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +138.5 KB - Content
- image-20220709110451-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +611.5 KB - Content
- image-20220908175246-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +55.7 KB - Content
- image-20220908175333-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.David - Size
-
... ... @@ -1,0 +1,1 @@ 1 +31.1 KB - Content