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, 0 added, 35 removed)
- 1657259653666-883.png
- 1657260785982-288.png
- 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-20220708133731-5.png
- image-20220708140453-6.png
- image-20220708141352-7.jpeg
- 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 -N DDS75NB-IoTDistanceDetectSensor User Manual1 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual - Content
-
... ... @@ -1,78 +1,64 @@ 1 1 (% style="text-align:center" %) 2 -[[image:image-20220 709085040-1.png||height="542" width="524"]]2 +[[image:image-20220606151504-2.jpeg||height="554" width="554"]] 3 3 4 4 5 5 6 6 7 7 8 -**Table of Contents:** 9 9 10 -{{toc/}} 11 11 12 12 13 13 14 14 15 15 14 +**Table of Contents:** 16 16 17 -= 1. Introduction = 18 18 19 19 20 -== 1.1 What is NDDS75 Distance Detection Sensor == 21 21 22 -((( 23 - 24 24 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 -))) 29 29 30 -((( 31 -The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network. 32 -))) 21 += 1. Introduction = 33 33 34 -((( 35 -NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage. 36 -))) 23 +== 1.1 What is LoRaWAN Soil Moisture & EC Sensor == 37 37 38 38 ((( 39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement. 40 -))) 26 + 41 41 42 -((( 43 -NDDS75 is powered by (% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method) 44 -))) 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. 45 45 46 -((( 47 -To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection. 48 -))) 49 -))) 30 +It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly. 50 50 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 + 51 51 52 52 ))) 53 53 54 -[[image:165 7327959271-447.png]]39 +[[image:1654503236291-817.png]] 55 55 56 56 42 +[[image:1657245163077-232.png]] 57 57 58 -== 1.2 Features == 59 59 60 60 46 +== 1.2 Features == 47 + 48 + 61 61 * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 62 -* Ultra low power consumption 63 -* Distance Detection by Ultrasonic technology 64 -* Flat object range 280mm - 7500mm 65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance) 66 -* Cable Length: 25cm 50 +* Monitor Soil Moisture 51 +* Monitor Soil Temperature 52 +* Monitor Soil Conductivity 67 67 * AT Commands to change parameters 68 68 * Uplink on periodically 69 69 * Downlink to change configure 70 70 * IP66 Waterproof Enclosure 57 +* Ultra-Low Power consumption 58 +* AT Commands to change parameters 71 71 * Micro SIM card slot for NB-IoT SIM 72 72 * 8500mAh Battery for long term use 73 73 74 - 75 - 76 76 == 1.3 Specification == 77 77 78 78 ... ... @@ -90,130 +90,100 @@ 90 90 * - B20 @H-FDD: 800MHz 91 91 * - B28 @H-FDD: 700MHz 92 92 93 -(% style="color:#037691" %)** Battery:**79 +(% style="color:#037691" %)**Probe Specification:** 94 94 95 -* Li/SOCI2 un-chargeable battery 96 -* Capacity: 8500mAh 97 -* Self Discharge: <1% / Year @ 25°C 98 -* Max continuously current: 130mA 99 -* Max boost current: 2A, 1 second 81 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 100 100 101 - (% style="color:#037691" %)**Power Consumption**83 +[[image:image-20220708101224-1.png]] 102 102 103 -* STOP Mode: 10uA @ 3.3v 104 -* Max transmit power: 350mA@3.3v 105 105 106 106 107 - 108 108 == 1.4 Applications == 109 109 110 - 111 -* Smart Buildings & Home Automation 112 -* Logistics and Supply Chain Management 113 -* Smart Metering 114 114 * Smart Agriculture 115 -* Smart Cities 116 -* Smart Factory 117 117 118 118 (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 119 119 120 120 121 - 122 - 123 - 124 124 == 1.5 Pin Definitions == 125 125 126 126 127 -[[image:1657 328609906-564.png]]97 +[[image:1657246476176-652.png]] 128 128 129 129 130 130 131 -= 2. Use N DDS75to communicate with IoT Server =101 += 2. Use NSE01 to communicate with IoT Server = 132 132 133 - 134 134 == 2.1 How it works == 135 135 136 136 137 137 ((( 138 -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.107 +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. 139 139 ))) 140 140 141 141 142 142 ((( 143 -The diagram below shows the working flow in default firmware of N DDS75:112 +The diagram below shows the working flow in default firmware of NSE01: 144 144 ))) 145 145 146 -((( 147 - 148 -))) 115 +[[image:image-20220708101605-2.png]] 149 149 150 -[[image:1657328659945-416.png]] 151 - 152 152 ((( 153 153 154 154 ))) 155 155 156 156 157 -== 2.2 Configure the NDDS75 == 158 158 123 +== 2.2 Configure the NSE01 == 159 159 125 + 160 160 === 2.2.1 Test Requirement === 161 161 162 162 163 -((( 164 -To use NDDS75 in your city, make sure meet below requirements: 165 -))) 129 +To use NSE01 in your city, make sure meet below requirements: 166 166 167 167 * Your local operator has already distributed a NB-IoT Network there. 168 -* The local NB-IoT network used the band that N DDS75supports.132 +* The local NB-IoT network used the band that NSE01 supports. 169 169 * Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 170 170 171 171 ((( 172 -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.136 +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 173 173 ))) 174 174 175 175 176 -[[image:1657 328756309-230.png]]140 +[[image:1657249419225-449.png]] 177 177 178 178 179 179 180 180 === 2.2.2 Insert SIM card === 181 181 182 - 183 -((( 184 184 Insert the NB-IoT Card get from your provider. 185 -))) 186 186 187 -((( 188 188 User need to take out the NB-IoT module and insert the SIM card like below: 189 -))) 190 190 191 191 192 -[[image:1657 328884227-504.png]]151 +[[image:1657249468462-536.png]] 193 193 194 194 195 195 196 -=== 2.2.3 Connect USB – TTL to N DDS75to configure it ===155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it === 197 197 198 - 199 199 ((( 200 200 ((( 201 -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.159 +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. 202 202 ))) 203 203 ))) 204 204 205 -[[image:image-20220709092052-2.png]] 206 206 164 +**Connection:** 207 207 208 -(% style="color: blue" %)**Connection:**166 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 209 209 210 - (% style="background-color:yellow" %) **USB TTLGND <~-~-~-~->GND**168 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 211 211 212 - **~(% style="background-color:yellow" %)USB TTLTXD <~-~-~-~-> UART_RXD(%%)**170 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 213 213 214 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)** 215 215 216 - 217 217 In the PC, use below serial tool settings: 218 218 219 219 * Baud: (% style="color:green" %)**9600** ... ... @@ -223,92 +223,70 @@ 223 223 * Flow Control: (% style="color:green" %)**None** 224 224 225 225 ((( 226 -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.182 +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. 227 227 ))) 228 228 229 -[[image: 1657329814315-101.png]]185 +[[image:image-20220708110657-3.png]] 230 230 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/]] 231 231 232 -((( 233 -(% 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]]** 234 -))) 235 235 236 236 237 - 238 238 === 2.2.4 Use CoAP protocol to uplink data === 239 239 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/]] 240 240 241 -(% 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/]]** 242 242 243 - 244 -((( 245 245 **Use below commands:** 246 -))) 247 247 248 -* ((( 249 -(% style="color:blue" %)**AT+PRO=1** (%%) ~/~/ Set to use CoAP protocol to uplink 250 -))) 251 -* ((( 252 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 253 -))) 254 -* ((( 255 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 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 256 256 257 - 258 - 259 -))) 260 - 261 -((( 262 262 For parameter description, please refer to AT command set 263 263 264 - 265 -))) 204 +[[image:1657249793983-486.png]] 266 266 267 -[[image:1657330452568-615.png]] 268 268 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. 269 269 209 +[[image:1657249831934-534.png]] 270 270 271 -((( 272 -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. 273 273 274 - 275 -))) 276 276 277 -[[image:1657330472797-498.png]] 278 - 279 - 280 - 281 281 === 2.2.5 Use UDP protocol to uplink data(Default protocol) === 282 282 215 +This feature is supported since firmware version v1.0.1 283 283 284 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 285 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 286 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 287 287 218 +* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 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 288 288 222 +[[image:1657249864775-321.png]] 289 289 290 -[[image:1657330501006-241.png]] 291 291 225 +[[image:1657249930215-289.png]] 292 292 293 -[[image:1657330533775-472.png]] 294 294 295 295 296 - 297 297 === 2.2.6 Use MQTT protocol to uplink data === 298 298 231 +This feature is supported since firmware version v110 299 299 300 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/ Set to use MQTT protocol to uplink 301 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/ Set MQTT server address and port 302 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/ Set up the CLIENT of MQTT 303 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/ Set the username of MQTT 304 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/ Set the password of MQTT 305 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/ Set the sending topic of MQTT 306 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/ Set the subscription topic of MQTT 307 307 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 + 308 308 [[image:1657249978444-674.png]] 309 309 310 310 311 -[[image:1657 330723006-866.png]]245 +[[image:1657249990869-686.png]] 312 312 313 313 314 314 ((( ... ... @@ -319,242 +319,178 @@ 319 319 320 320 === 2.2.7 Use TCP protocol to uplink data === 321 321 256 +This feature is supported since firmware version v110 322 322 323 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 324 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 325 325 326 -[[image:image-20220709093918-1.png]] 259 +* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 260 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 327 327 262 +[[image:1657250217799-140.png]] 328 328 329 -[[image:image-20220709093918-2.png]] 330 330 265 +[[image:1657250255956-604.png]] 331 331 332 332 268 + 333 333 === 2.2.8 Change Update Interval === 334 334 335 - 336 336 User can use below command to change the (% style="color:green" %)**uplink interval**. 337 337 338 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ 273 +* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 339 339 340 340 ((( 341 - 342 - 343 - 344 344 (% style="color:red" %)**NOTE:** 277 +))) 345 345 346 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 347 - 348 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 279 +((( 280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour. 349 349 ))) 350 350 351 -(% 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).** 352 352 353 353 354 - 355 355 == 2.3 Uplink Payload == 356 356 287 +In this mode, uplink payload includes in total 18 bytes 357 357 358 -=== 2.3.1 Before Firmware v1.3.2 === 359 - 360 - 361 -In this mode, uplink payload includes in total 14 bytes 362 - 363 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 364 -|=(% style="width: 60px;" %)((( 289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %) 290 +|=(% style="width: 50px;" %)((( 365 365 **Size(bytes)** 366 -)))|=(% style="width: 60px;" %)**6**|=(% style="width:35px;" %)2|=(% style="width:35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width:100px;" %)**2**|=(% style="width:60px;" %)**1**367 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H 2.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"]]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" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]] 368 368 369 -((( 370 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 371 -))) 295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data. 372 372 373 373 374 -[[image: 1657331036973-987.png]]298 +[[image:image-20220708111918-4.png]] 375 375 376 376 377 -((( 378 -The payload is **ASCII** string, representative same HEX: 379 -))) 301 +The payload is ASCII string, representative same HEX: 380 380 381 -((( 382 -0x72403155615900640c6c19029200 where: 383 -))) 303 +0x72403155615900640c7817075e0a8c02f900 where: 384 384 385 -* ((( 386 -Device ID: 0x724031556159 = 724031556159 387 -))) 388 -* ((( 389 -Version: 0x0064=100=1.0.0 390 -))) 305 +* Device ID: 0x 724031556159 = 724031556159 306 +* Version: 0x0064=100=1.0.0 391 391 392 -* ((( 393 -BAT: 0x0c6c = 3180 mV = 3.180V 394 -))) 395 -* ((( 396 -Signal: 0x19 = 25 397 -))) 398 -* ((( 399 -Distance: 0x0292= 658 mm 400 -))) 401 -* ((( 402 -Interrupt: 0x00 = 0 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 403 403 404 404 316 +== 2.4 Payload Explanation and Sensor Interface == 405 405 406 406 407 - 408 -))) 319 +=== 2.4.1 Device ID === 409 409 410 - ===**2.3.2Sincefirmwarev1.3.2**===321 +By default, the Device ID equal to the last 6 bytes of IMEI. 411 411 323 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 412 412 413 - In thismode, uplink payload includes 69 bytes in total by default.325 +**Example:** 414 414 415 -E ach time the device uploads a data package, 8 sets of recorded data will be attached.Up to 32sets of recorded data can be uploaded.327 +AT+DEUI=A84041F15612 416 416 417 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 418 -|(% 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 419 -|(% 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....... 329 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID. 420 420 421 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 422 422 423 -[[image:image-20220908175246-1.png]] 424 424 333 +=== 2.4.2 Version Info === 425 425 426 - ThepayloadisASCIIstring,representativesameHEX:335 +Specify the software version: 0x64=100, means firmware version 1.00. 427 427 428 - 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:337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0. 429 429 430 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 431 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 432 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 433 -* (% style="color:blue" %)Singal: 0x1e = 30 434 -* (% style="color:red" %)Mod: 0x01 = 1 435 -* Interrupt: 0x00= 0 436 -* Distance: 0x0039= 57 = 57 437 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 438 -* Distance,Time stamp : 00396319baf0 439 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 440 440 441 441 341 +=== 2.4.3 Battery Info === 442 442 443 -== 2.4 Payload Explanation and Sensor Interface == 444 - 445 - 446 -=== 2.4.1 Device ID === 447 - 448 - 449 449 ((( 450 - By default,theDevice ID equaltothe last6 bytesofIMEI.344 +Check the battery voltage for LSE01. 451 451 ))) 452 452 453 453 ((( 454 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 455 - 456 - 348 +Ex1: 0x0B45 = 2885mV 457 457 ))) 458 458 459 459 ((( 460 - (% style="color:blue"%)**Example:**352 +Ex2: 0x0B49 = 2889mV 461 461 ))) 462 462 463 -((( 464 -AT+DEUI=A84041F15612 465 -))) 466 466 467 -((( 468 -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. 469 -))) 470 470 357 +=== 2.4.4 Signal Strength === 471 471 472 - (% style="color:red" %)**NOTE:Whenthe firmwareversionis v1.3.2andlaterfirmware:**359 +NB-IoT Network signal Strength. 473 473 474 - (% style="color:red" %)**Bydefault,theDevice ID equal to the last 15 bits of IMEI.**361 +**Ex1: 0x1d = 29** 475 475 476 - User can use(% style="color:blue" %)**AT+DEUI**(%%)tosetDeviceID363 +(% style="color:blue" %)**0**(%%) -113dBm or less 477 477 365 +(% style="color:blue" %)**1**(%%) -111dBm 478 478 479 -(% style="color:blue" %)** Example :**367 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 480 480 481 - AT+DEUI=868411056754138369 +(% style="color:blue" %)**31** (%%) -51dBm or greater 482 482 371 +(% style="color:blue" %)**99** (%%) Not known or not detectable 483 483 484 484 485 -=== 2.4.2 Version Info === 486 486 375 +=== 2.4.5 Soil Moisture === 487 487 488 488 ((( 489 - Specifythe softwareversion:0x64=100,meansfirmwareversion1.00.378 +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. 490 490 ))) 491 491 492 492 ((( 493 -For example :0x0064:thisdevice isNDDS75withfirmwareversion1.0.0.382 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is 494 494 ))) 495 495 496 - 497 - 498 -=== 2.4.3 Battery Info === 499 - 500 - 501 501 ((( 502 - Ex1:0x0B45 = 2885mV386 + 503 503 ))) 504 504 505 505 ((( 506 - Ex2: 0x0B49=2889mV390 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 507 507 ))) 508 508 509 509 510 510 511 -=== 2.4. 4SignalStrength===395 +=== 2.4.6 Soil Temperature === 512 512 513 - 514 514 ((( 515 - NB-IoTNetworksignalStrength.398 + 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 516 516 ))) 517 517 518 518 ((( 519 -**Ex 1: 0x1d = 29**402 +**Example**: 520 520 ))) 521 521 522 522 ((( 523 - (%style="color:blue"%)**0**(%%)-113dBmorless406 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 524 524 ))) 525 525 526 526 ((( 527 - (%style="color:blue"%)**1**(%%)-111dBm410 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 528 528 ))) 529 529 530 -((( 531 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 532 -))) 533 533 534 -((( 535 -(% style="color:blue" %)**31** (%%) -51dBm or greater 536 -))) 537 537 415 +=== 2.4.7 Soil Conductivity (EC) === 416 + 538 538 ((( 539 -(% style="color:b lue" %)**99**Notknown or not detectable418 +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). 540 540 ))) 541 541 542 - 543 - 544 -=== 2.4.5 Distance === 545 - 546 - 547 -Get the distance. Flat object range 280mm - 7500mm. 548 - 549 549 ((( 550 -For example, if the data you get from the register is **__0x0B0x05__**, thedistance betweenthesensorandthemeasuredobjectis422 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 551 551 ))) 552 552 553 553 ((( 554 -((( 555 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 426 +Generally, the EC value of irrigation water is less than 800uS / cm. 556 556 ))) 557 -))) 558 558 559 559 ((( 560 560 ... ... @@ -564,75 +564,54 @@ 564 564 565 565 ))) 566 566 567 -=== 2.4. 6Digital Interrupt ===437 +=== 2.4.8 Digital Interrupt === 568 568 439 +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. 569 569 570 -((( 571 -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. 572 -))) 573 - 574 -((( 575 575 The command is: 576 -))) 577 577 578 -((( 579 -(% 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]])**.** 580 -))) 443 +(% 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]])**.** 581 581 582 582 583 -((( 584 -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. 585 -))) 446 +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. 586 586 587 587 588 -((( 589 589 Example: 590 -))) 591 591 592 -((( 593 593 0x(00): Normal uplink packet. 594 -))) 595 595 596 -((( 597 597 0x(01): Interrupt Uplink Packet. 598 -))) 599 599 600 600 601 601 602 -=== 2.4.7 +5V Output === 603 603 458 +=== 2.4.9 +5V Output === 604 604 605 -((( 606 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 607 -))) 608 608 461 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 609 609 610 - (((463 + 611 611 The 5V output time can be controlled by AT Command. 612 612 613 - 614 -))) 615 - 616 -((( 617 617 (% style="color:blue" %)**AT+5VT=1000** 618 618 619 - 620 -))) 621 - 622 -((( 623 623 Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 624 -))) 625 625 626 626 627 627 628 -== 2. 5DownlinkPayload==472 +== 2.4 Uplink Interval == 629 629 474 +The LSE01 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]] 630 630 631 -By default, NDDS75 prints the downlink payload to console port. 632 632 633 -[[image:image-20220709100028-1.png]] 634 634 478 +== 2.5 Downlink Payload == 635 635 480 +By default, LSE50 prints the downlink payload to console port. 481 + 482 +[[image:image-20220606165544-8.png]] 483 + 484 + 636 636 ((( 637 637 (% style="color:blue" %)**Examples:** 638 638 ))) ... ... @@ -646,7 +646,7 @@ 646 646 ))) 647 647 648 648 ((( 649 -If the payload=0100003C, it means set the END Node 's TDC to 0x00003C=60(S), while type code is 01.498 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01. 650 650 ))) 651 651 652 652 ((( ... ... @@ -666,165 +666,432 @@ 666 666 ))) 667 667 668 668 ((( 669 -If payload = 0x04FF, it will reset the NDDS75518 +If payload = 0x04FF, it will reset the LSE01 670 670 ))) 671 671 672 672 673 -* (% style="color:blue" %)** INTMOD**522 +* (% style="color:blue" %)**CFM** 674 674 524 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0 525 + 526 + 527 + 528 +== 2.6 Show Data in DataCake IoT Server == 529 + 675 675 ((( 676 -Do wnlinkPayload:06000003,SetAT+INTMOD=3531 +[[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps: 677 677 ))) 678 678 534 +((( 535 + 536 +))) 679 679 538 +((( 539 +(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time. 540 +))) 680 680 681 -== 2.6 Distance alarm function(Since firmware v1.3.2) == 542 +((( 543 +(% style="color:blue" %)**Step 2**(%%): To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps: 544 +))) 682 682 683 683 684 - (% style="color:blue" %)** ➢ AT Command:**547 +[[image:1654505857935-743.png]] 685 685 686 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 687 687 688 - ² When min=0, andmax≠0, Alarm higher thanmax550 +[[image:1654505874829-548.png]] 689 689 690 -² When min≠0, and max=0, Alarm lower than min 691 691 692 - ²Whenmin≠0andmax≠0,Alarm higherthanmaxor lowerthan min553 +(% style="color:blue" %)**Step 3**(%%)**:** Create an account or log in Datacake. 693 693 555 +(% style="color:blue" %)**Step 4**(%%)**:** Search the LSE01 and add DevEUI. 694 694 695 -(% style="color:blue" %)** Example:** 696 696 697 - **AT+ LDDSALARM=260,2000** ~/~/ Alarm when distancelower than 260.558 +[[image:1654505905236-553.png]] 698 698 699 699 561 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices. 700 700 701 - == 2.7 Set the number of data to beuploaded and the recordingtime ==563 +[[image:1654505925508-181.png]] 702 702 703 703 704 -(% style="color:blue" %)** ➢ AT Command:** 705 705 706 -* (% 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) 707 -* (% 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. 567 +== 2.7 Frequency Plans == 708 708 569 +The LSE01 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets. 709 709 710 710 572 +=== 2.7.1 EU863-870 (EU868) === 711 711 712 - ==2.8 Reador Clearcacheddata ==574 +(% style="color:#037691" %)** Uplink:** 713 713 576 +868.1 - SF7BW125 to SF12BW125 714 714 715 - (%style="color:blue"%)**➢ AT Command:**578 +868.3 - SF7BW125 to SF12BW125 and SF7BW250 716 716 717 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 718 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 580 +868.5 - SF7BW125 to SF12BW125 719 719 720 - [[image:image-20220908175333-2.png]]582 +867.1 - SF7BW125 to SF12BW125 721 721 584 +867.3 - SF7BW125 to SF12BW125 722 722 586 +867.5 - SF7BW125 to SF12BW125 723 723 724 - == 2.9LEDIndicator==588 +867.7 - SF7BW125 to SF12BW125 725 725 590 +867.9 - SF7BW125 to SF12BW125 726 726 727 - The NDDS75 has an internal LED which is to show the status of different state.592 +868.8 - FSK 728 728 729 729 730 -* 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) 731 -* Then the LED will be on for 1 second means device is boot normally. 732 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 733 -* For each uplink probe, LED will be on for 500ms. 595 +(% style="color:#037691" %)** Downlink:** 734 734 735 -((( 736 - 737 -))) 597 +Uplink channels 1-9 (RX1) 738 738 599 +869.525 - SF9BW125 (RX2 downlink only) 739 739 740 740 741 -== 2.10 Firmware Change Log == 742 742 603 +=== 2.7.2 US902-928(US915) === 743 743 744 -((( 745 -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]] 746 -))) 605 +Used in USA, Canada and South America. Default use CHE=2 747 747 748 -((( 749 - 750 -))) 607 +(% style="color:#037691" %)**Uplink:** 751 751 752 -((( 753 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 754 -))) 609 +903.9 - SF7BW125 to SF10BW125 755 755 611 +904.1 - SF7BW125 to SF10BW125 756 756 613 +904.3 - SF7BW125 to SF10BW125 757 757 758 - == 2.11BatteryAnalysis ==615 +904.5 - SF7BW125 to SF10BW125 759 759 617 +904.7 - SF7BW125 to SF10BW125 760 760 761 - === 2.11.1BatteryType ===619 +904.9 - SF7BW125 to SF10BW125 762 762 621 +905.1 - SF7BW125 to SF10BW125 763 763 623 +905.3 - SF7BW125 to SF10BW125 624 + 625 + 626 +(% style="color:#037691" %)**Downlink:** 627 + 628 +923.3 - SF7BW500 to SF12BW500 629 + 630 +923.9 - SF7BW500 to SF12BW500 631 + 632 +924.5 - SF7BW500 to SF12BW500 633 + 634 +925.1 - SF7BW500 to SF12BW500 635 + 636 +925.7 - SF7BW500 to SF12BW500 637 + 638 +926.3 - SF7BW500 to SF12BW500 639 + 640 +926.9 - SF7BW500 to SF12BW500 641 + 642 +927.5 - SF7BW500 to SF12BW500 643 + 644 +923.3 - SF12BW500(RX2 downlink only) 645 + 646 + 647 + 648 +=== 2.7.3 CN470-510 (CN470) === 649 + 650 +Used in China, Default use CHE=1 651 + 652 +(% style="color:#037691" %)**Uplink:** 653 + 654 +486.3 - SF7BW125 to SF12BW125 655 + 656 +486.5 - SF7BW125 to SF12BW125 657 + 658 +486.7 - SF7BW125 to SF12BW125 659 + 660 +486.9 - SF7BW125 to SF12BW125 661 + 662 +487.1 - SF7BW125 to SF12BW125 663 + 664 +487.3 - SF7BW125 to SF12BW125 665 + 666 +487.5 - SF7BW125 to SF12BW125 667 + 668 +487.7 - SF7BW125 to SF12BW125 669 + 670 + 671 +(% style="color:#037691" %)**Downlink:** 672 + 673 +506.7 - SF7BW125 to SF12BW125 674 + 675 +506.9 - SF7BW125 to SF12BW125 676 + 677 +507.1 - SF7BW125 to SF12BW125 678 + 679 +507.3 - SF7BW125 to SF12BW125 680 + 681 +507.5 - SF7BW125 to SF12BW125 682 + 683 +507.7 - SF7BW125 to SF12BW125 684 + 685 +507.9 - SF7BW125 to SF12BW125 686 + 687 +508.1 - SF7BW125 to SF12BW125 688 + 689 +505.3 - SF12BW125 (RX2 downlink only) 690 + 691 + 692 + 693 +=== 2.7.4 AU915-928(AU915) === 694 + 695 +Default use CHE=2 696 + 697 +(% style="color:#037691" %)**Uplink:** 698 + 699 +916.8 - SF7BW125 to SF12BW125 700 + 701 +917.0 - SF7BW125 to SF12BW125 702 + 703 +917.2 - SF7BW125 to SF12BW125 704 + 705 +917.4 - SF7BW125 to SF12BW125 706 + 707 +917.6 - SF7BW125 to SF12BW125 708 + 709 +917.8 - SF7BW125 to SF12BW125 710 + 711 +918.0 - SF7BW125 to SF12BW125 712 + 713 +918.2 - SF7BW125 to SF12BW125 714 + 715 + 716 +(% style="color:#037691" %)**Downlink:** 717 + 718 +923.3 - SF7BW500 to SF12BW500 719 + 720 +923.9 - SF7BW500 to SF12BW500 721 + 722 +924.5 - SF7BW500 to SF12BW500 723 + 724 +925.1 - SF7BW500 to SF12BW500 725 + 726 +925.7 - SF7BW500 to SF12BW500 727 + 728 +926.3 - SF7BW500 to SF12BW500 729 + 730 +926.9 - SF7BW500 to SF12BW500 731 + 732 +927.5 - SF7BW500 to SF12BW500 733 + 734 +923.3 - SF12BW500(RX2 downlink only) 735 + 736 + 737 + 738 +=== 2.7.5 AS920-923 & AS923-925 (AS923) === 739 + 740 +(% style="color:#037691" %)**Default Uplink channel:** 741 + 742 +923.2 - SF7BW125 to SF10BW125 743 + 744 +923.4 - SF7BW125 to SF10BW125 745 + 746 + 747 +(% style="color:#037691" %)**Additional Uplink Channel**: 748 + 749 +(OTAA mode, channel added by JoinAccept message) 750 + 751 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**: 752 + 753 +922.2 - SF7BW125 to SF10BW125 754 + 755 +922.4 - SF7BW125 to SF10BW125 756 + 757 +922.6 - SF7BW125 to SF10BW125 758 + 759 +922.8 - SF7BW125 to SF10BW125 760 + 761 +923.0 - SF7BW125 to SF10BW125 762 + 763 +922.0 - SF7BW125 to SF10BW125 764 + 765 + 766 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**: 767 + 768 +923.6 - SF7BW125 to SF10BW125 769 + 770 +923.8 - SF7BW125 to SF10BW125 771 + 772 +924.0 - SF7BW125 to SF10BW125 773 + 774 +924.2 - SF7BW125 to SF10BW125 775 + 776 +924.4 - SF7BW125 to SF10BW125 777 + 778 +924.6 - SF7BW125 to SF10BW125 779 + 780 + 781 +(% style="color:#037691" %)** Downlink:** 782 + 783 +Uplink channels 1-8 (RX1) 784 + 785 +923.2 - SF10BW125 (RX2) 786 + 787 + 788 + 789 +=== 2.7.6 KR920-923 (KR920) === 790 + 791 +Default channel: 792 + 793 +922.1 - SF7BW125 to SF12BW125 794 + 795 +922.3 - SF7BW125 to SF12BW125 796 + 797 +922.5 - SF7BW125 to SF12BW125 798 + 799 + 800 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)** 801 + 802 +922.1 - SF7BW125 to SF12BW125 803 + 804 +922.3 - SF7BW125 to SF12BW125 805 + 806 +922.5 - SF7BW125 to SF12BW125 807 + 808 +922.7 - SF7BW125 to SF12BW125 809 + 810 +922.9 - SF7BW125 to SF12BW125 811 + 812 +923.1 - SF7BW125 to SF12BW125 813 + 814 +923.3 - SF7BW125 to SF12BW125 815 + 816 + 817 +(% style="color:#037691" %)**Downlink:** 818 + 819 +Uplink channels 1-7(RX1) 820 + 821 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 822 + 823 + 824 + 825 +=== 2.7.7 IN865-867 (IN865) === 826 + 827 +(% style="color:#037691" %)** Uplink:** 828 + 829 +865.0625 - SF7BW125 to SF12BW125 830 + 831 +865.4025 - SF7BW125 to SF12BW125 832 + 833 +865.9850 - SF7BW125 to SF12BW125 834 + 835 + 836 +(% style="color:#037691" %) **Downlink:** 837 + 838 +Uplink channels 1-3 (RX1) 839 + 840 +866.550 - SF10BW125 (RX2) 841 + 842 + 843 + 844 + 845 +== 2.8 LED Indicator == 846 + 847 +The LSE01 has an internal LED which is to show the status of different state. 848 + 849 +* Blink once when device power on. 850 +* Solid ON for 5 seconds once device successful Join the network. 851 +* Blink once when device transmit a packet. 852 + 853 +== 2.9 Installation in Soil == 854 + 855 +**Measurement the soil surface** 856 + 857 + 858 +[[image:1654506634463-199.png]] 859 + 764 764 ((( 765 -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. 861 +((( 862 +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. 766 766 ))) 864 +))) 767 767 866 + 867 + 868 +[[image:1654506665940-119.png]] 869 + 768 768 ((( 769 - The batteryis designedto lastfor severalyearsdepends ontheactually use environmentand updateinterval.871 +Dig a hole with diameter > 20CM. 770 770 ))) 771 771 772 772 ((( 773 - The batteryrelateddocumentsasbelow:875 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 774 774 ))) 775 775 776 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 777 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 778 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 779 779 879 +== 2.10 Firmware Change Log == 880 + 780 780 ((( 781 - [[image:image-20220709101450-2.png]]882 +**Firmware download link:** 782 782 ))) 783 783 885 +((( 886 +[[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]] 887 +))) 784 784 889 +((( 890 + 891 +))) 785 785 786 -=== 2.11.2 Power consumption Analyze === 893 +((( 894 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 895 +))) 787 787 897 +((( 898 + 899 +))) 788 788 789 789 ((( 790 - 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.902 +**V1.0.** 791 791 ))) 792 792 905 +((( 906 +Release 907 +))) 793 793 909 + 910 +== 2.11 Battery Analysis == 911 + 912 +=== 2.11.1 Battery Type === 913 + 794 794 ((( 795 - Instruction touse as below:915 +The LSE01 battery is a combination of a 4000mAh Li/SOCI2 Battery and a Super Capacitor. The battery is non-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. 796 796 ))) 797 797 798 798 ((( 799 - (% style="color:blue" %)**Step 1: **(%%)Downlink theup-to-date DRAGINO_Battery_Life_Prediction_Table.xlsxfrom: [[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/]]919 +The battery is designed to last for more than 5 years for the LSN50. 800 800 ))) 801 801 802 - 803 803 ((( 804 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose 923 +((( 924 +The battery-related documents are as below: 805 805 ))) 926 +))) 806 806 807 807 * ((( 808 - Product Model929 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], 809 809 ))) 810 810 * ((( 811 - UplinkInterval932 +[[Lithium-Thionyl Chloride Battery datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], 812 812 ))) 813 813 * ((( 814 - WorkingMode935 +[[Lithium-ion Battery-Capacitor datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], [[Tech Spec>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]] 815 815 ))) 816 816 817 -((( 818 -And the Life expectation in difference case will be shown on the right. 819 -))) 938 + [[image:image-20220610172436-1.png]] 820 820 821 -[[image:image-20220709110451-3.png]] 822 822 823 823 942 +=== 2.11.2 Battery Note === 824 824 825 -=== 2.11.3 Battery Note === 826 - 827 - 828 828 ((( 829 829 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. 830 830 ))) ... ... @@ -831,217 +831,326 @@ 831 831 832 832 833 833 834 -=== 2.11. 4Replace the battery ===950 +=== 2.11.3 Replace the battery === 835 835 952 +((( 953 +If Battery is lower than 2.7v, user should replace the battery of LSE01. 954 +))) 836 836 837 837 ((( 838 - Thedefault battery packofNDDS75includes aER26500plussupercapacitor.Ifuser can'tfind thispacklocally,theycanfindER26500 orequivalencewithouttheSPC1520capacitor,whichwillalsowork inmost case.TheSPCcanenlargethebatterylifeforhighfrequencyuse(updateperiodbelow5minutes).957 +You can change the battery in the LSE01.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board. 839 839 ))) 840 840 960 +((( 961 +The default battery pack of LSE01 includes a ER18505 plus super capacitor. If user can’t find this pack locally, they can find ER18505 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes) 962 +))) 841 841 842 842 843 -= 3. Access NB-IoT Module = 844 844 966 += 3. Using the AT Commands = 845 845 846 -((( 847 -Users can directly access the AT command set of the NB-IoT module. 848 -))) 968 +== 3.1 Access AT Commands == 849 849 850 -((( 851 -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/]] 852 852 853 - 854 -))) 971 +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. 855 855 856 -[[image:165 7333200519-600.png]]973 +[[image:1654501986557-872.png||height="391" width="800"]] 857 857 858 858 976 +Or if you have below board, use below connection: 859 859 860 -= 4. Using the AT Commands = 861 861 979 +[[image:1654502005655-729.png||height="503" width="801"]] 862 862 863 -== 4.1 Access AT Commands == 864 864 865 865 866 - Seethislinkfordetail: [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]983 +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 output system info once power on as below: 867 867 868 868 869 - AT+<CMD>?: Helpon<CMD>986 + [[image:1654502050864-459.png||height="564" width="806"]] 870 870 871 -AT+<CMD> : Run <CMD> 872 872 873 - AT+<CMD>=<value>:Set thevalue989 +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]] 874 874 875 -AT+<CMD>=? : Get the value 876 876 992 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD> 877 877 994 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD> 995 + 996 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value 997 + 998 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%) : Get the value 999 + 1000 + 878 878 (% style="color:#037691" %)**General Commands**(%%) 879 879 880 -AT 1003 +(% style="background-color:#dcdcdc" %)**AT**(%%) : Attention 881 881 882 -AT? 1005 +(% style="background-color:#dcdcdc" %)**AT?**(%%) : Short Help 883 883 884 -ATZ 1007 +(% style="background-color:#dcdcdc" %)**ATZ**(%%) : MCU Reset 885 885 886 -AT+TDC 1009 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%) : Application Data Transmission Interval 887 887 888 -AT+CFG : Print all configurations 889 889 890 - AT+CFGMOD:Workingmodeselection1012 +(% style="color:#037691" %)**Keys, IDs and EUIs management** 891 891 892 -AT+I NTMOD:Setthe trigger interruptmode1014 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%) : Application EUI 893 893 894 -AT+ 5VTSetextend the timeof5V power1016 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%) : Application Key 895 895 896 -AT+P ROChooseagreement1018 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%) : Application Session Key 897 897 898 -AT+ WEIGREGet weightorsetweight to 01020 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%) : Device Address 899 899 900 -AT+ WEIGAPGet or SettheGapValue of weight1022 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%) : Device EUI 901 901 902 -AT+ RXDL: Extendthe sendingandreceivingtime1024 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%) : Network ID (You can enter this command change only after successful network connection) 903 903 904 -AT+ CNTFACGettcountingparameters1026 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%) : Network Session Key Joining and sending date on LoRa network 905 905 906 -AT+ SERVADDR:ServerAddress1028 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%) : Confirm Mode 907 907 908 -AT+ TRGetor Setrecordtime"1030 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%) : Confirm Status 909 909 910 -AT+ APNGetorsetthe APN1032 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%) : Join LoRa? Network 911 911 912 -AT+ FBAND:GetorSethethertoautomaticallymodify thefrequency band1034 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%) : LoRa? Network Join Mode 913 913 914 -AT+ DNSCFGGetetDNS Server1036 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%) : LoRa? Network Join Status 915 915 916 -AT+ GETSENSORVALUE :Returnsthecurrentsensormeasurement1038 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%) : Print Last Received Data in Raw Format 917 917 918 -AT+ NOUD:Get orSet thenumber ofdatatobeuploaded1040 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%) : Print Last Received Data in Binary Format 919 919 920 -AT+ CDP:Reador Clearcached data1042 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%) : Send Text Data 921 921 922 -AT+ LDDSALARM:Get orSetalarm ofdistance1044 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%) : Send Hexadecimal Data 923 923 924 924 925 -(% style="color:#037691" %)** COAPManagement**1047 +(% style="color:#037691" %)**LoRa Network Management** 926 926 927 -AT+ URIResourceparameters1049 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%) : Adaptive Rate 928 928 1051 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%) : LoRa Class(Currently only support class A 929 929 930 -(% style="color:# 037691" %)**UDPManagement**1053 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%) : Duty Cycle Setting 931 931 932 -AT+ CFM:Uploadconfirmationmode (onlyvalid forUDP)1055 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%) : Data Rate (Can Only be Modified after ADR=0) 933 933 1057 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%) : Frame Counter Downlink 934 934 935 -(% style="color:# 037691" %)**MQTTManagement**1059 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%) : Frame Counter Uplink 936 936 937 -AT+ CLIENTGetorSetMQTT client1061 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%) : Join Accept Delay1 938 938 939 -AT+ UNAMEGetorSetMQTT Username1063 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%) : Join Accept Delay2 940 940 941 -AT+P WDGetSetMQTT password1065 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%) : Public Network Mode 942 942 943 -AT+ PUBTOPIC:Get or SetMQTT publishtopic1067 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%) : Receive Delay1 944 944 945 -AT+ SUBTOPIC:Get or Set MQTT subscriptiontopic1069 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%) : Receive Delay2 946 946 1071 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%) : Rx2 Window Data Rate 947 947 948 -(% style="color:# 037691" %)**Information**1073 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%) : Rx2 Window Frequency 949 949 950 -AT+ FDRFactory DataReset1075 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%) : Transmit Power 951 951 952 -AT+ PWORD :rialAccess Password1077 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%) : Set work mode 953 953 954 954 1080 +(% style="color:#037691" %)**Information** 955 955 956 -= 5.FAQ=1082 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%) : RSSI of the Last Received Packet 957 957 1084 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%) : SNR of the Last Received Packet 958 958 959 -= =5.1HowtoUpgradeFirmware==1086 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%) : Image Version and Frequency Band 960 960 1088 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Factory Data Reset 961 961 1090 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%) : Application Port 1091 + 1092 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%) : Get or Set Frequency (Unit: Hz) for Single Channel Mode 1093 + 1094 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%) : Get or Set eight channels mode, Only for US915, AU915, CN470 1095 + 1096 + 1097 += 4. FAQ = 1098 + 1099 +== 4.1 How to change the LoRa Frequency Bands/Region? == 1100 + 962 962 ((( 963 -User can upgrade the firmware for 1) bug fix, 2) new feature release. 1102 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]]. 1103 +When downloading the images, choose the required image file for download. 964 964 ))) 965 965 966 966 ((( 967 - Pleasesee 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]]1107 + 968 968 ))) 969 969 970 970 ((( 971 - (%style="color:red"%)**Notice,NDDS75andLDDS75share thememotherboard.Theyuse thesameconnection andmethodto update.**1111 +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. 972 972 ))) 973 973 1114 +((( 1115 + 1116 +))) 974 974 1118 +((( 1119 +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. 1120 +))) 975 975 976 -= 6. Trouble Shooting = 1122 +((( 1123 + 1124 +))) 977 977 1126 +((( 1127 +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. 1128 +))) 978 978 979 - == 6.1 Connection problemwhen uploadingfirmware==1130 +[[image:image-20220606154726-3.png]] 980 980 981 981 1133 +When you use the TTN network, the US915 frequency bands use are: 1134 + 1135 +* 903.9 - SF7BW125 to SF10BW125 1136 +* 904.1 - SF7BW125 to SF10BW125 1137 +* 904.3 - SF7BW125 to SF10BW125 1138 +* 904.5 - SF7BW125 to SF10BW125 1139 +* 904.7 - SF7BW125 to SF10BW125 1140 +* 904.9 - SF7BW125 to SF10BW125 1141 +* 905.1 - SF7BW125 to SF10BW125 1142 +* 905.3 - SF7BW125 to SF10BW125 1143 +* 904.6 - SF8BW500 1144 + 982 982 ((( 983 -**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]] 1146 +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: 1147 + 1148 +* (% style="color:#037691" %)**AT+CHE=2** 1149 +* (% style="color:#037691" %)**ATZ** 984 984 ))) 985 985 986 -(% class="wikigeneratedid" %) 987 987 ((( 988 988 1154 + 1155 +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. 989 989 ))) 990 990 1158 +((( 1159 + 1160 +))) 991 991 992 -== 6.2 AT Command input doesn't work == 1162 +((( 1163 +The **AU915** band is similar. Below are the AU915 Uplink Channels. 1164 +))) 993 993 1166 +[[image:image-20220606154825-4.png]] 994 994 1168 + 1169 +== 4.2 Can I calibrate LSE01 to different soil types? == 1170 + 1171 +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]]. 1172 + 1173 + 1174 += 5. Trouble Shooting = 1175 + 1176 +== 5.1 Why I can't join TTN in US915 / AU915 bands? == 1177 + 1178 +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. 1179 + 1180 + 1181 +== 5.2 AT Command input doesn't work == 1182 + 995 995 ((( 996 996 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. 1185 +))) 997 997 998 - 1187 + 1188 +== 5.3 Device rejoin in at the second uplink packet == 1189 + 1190 +(% style="color:#4f81bd" %)**Issue describe as below:** 1191 + 1192 +[[image:1654500909990-784.png]] 1193 + 1194 + 1195 +(% style="color:#4f81bd" %)**Cause for this issue:** 1196 + 1197 +((( 1198 +The fuse 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. 999 999 ))) 1000 1000 1001 1001 1002 - =7. OrderInfo=1202 +(% style="color:#4f81bd" %)**Solution: ** 1003 1003 1204 +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: 1004 1004 1005 - Part Number**:** (% style="color:#4f81bd"%)**NSDDS75**1206 +[[image:1654500929571-736.png||height="458" width="832"]] 1006 1006 1007 1007 1209 += 6. Order Info = 1210 + 1211 + 1212 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY** 1213 + 1214 + 1215 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band 1216 + 1217 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band 1218 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band 1219 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band 1220 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band 1221 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band 1222 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band 1223 +* (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1224 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1225 + 1226 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option 1227 + 1228 +* (% style="color:red" %)**4**(%%): 4000mAh battery 1229 +* (% style="color:red" %)**8**(%%): 8500mAh battery 1230 + 1008 1008 (% class="wikigeneratedid" %) 1009 1009 ((( 1010 1010 1011 1011 ))) 1012 1012 1013 -= 8.1236 += 7. Packing Info = 1014 1014 1015 1015 ((( 1016 1016 1017 1017 1018 1018 (% style="color:#037691" %)**Package Includes**: 1242 +))) 1019 1019 1020 -* NDDS75 NB-IoT Distance Detect Sensor Node x 11021 - *Externalantennax 11244 +* ((( 1245 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1 1022 1022 ))) 1023 1023 1024 1024 ((( 1025 1025 1026 1026 1027 - 1028 1028 (% style="color:#037691" %)**Dimension and weight**: 1252 +))) 1029 1029 1030 -* Device Size: 13.0 x 5 x 4.5 cm 1031 -* Device Weight: 150g 1032 -* Package Size / pcs : 15 x 12x 5.5 cm 1033 -* Weight / pcs : 220g 1254 +* ((( 1255 +Device Size: cm 1034 1034 ))) 1257 +* ((( 1258 +Device Weight: g 1259 +))) 1260 +* ((( 1261 +Package Size / pcs : cm 1262 +))) 1263 +* ((( 1264 +Weight / pcs : g 1035 1035 1036 -((( 1037 1037 1038 - 1039 - 1040 - 1041 1041 ))) 1042 1042 1043 -= 9.1269 += 8. Support = 1044 1044 1045 - 1046 1046 * 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. 1047 1047 * 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]]
- 1657259653666-883.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -344.4 KB - Content
- 1657260785982-288.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657261119050-993.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657261278785-153.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- 1657271519014-786.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.5 KB - Content
- 1657327959271-447.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.3 KB - Content
- 1657328609906-564.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -492.6 KB - Content
- 1657328659945-416.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.8 KB - Content
- 1657328756309-230.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -78.5 KB - Content
- 1657328884227-504.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657329814315-101.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.3 KB - Content
- 1657330452568-615.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -71.3 KB - Content
- 1657330472797-498.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -68.9 KB - Content
- 1657330501006-241.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -119.2 KB - Content
- 1657330533775-472.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.9 KB - Content
- 1657330723006-866.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -74.1 KB - Content
- 1657331036973-987.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -83.8 KB - Content
- 1657332990863-496.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -138.2 KB - Content
- 1657333200519-600.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -126.1 KB - Content
- image-20220708133731-5.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -8.7 KB - Content
- image-20220708140453-6.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -132.7 KB - Content
- image-20220708141352-7.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -102.7 KB - Content
- image-20220709084038-1.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.0 KB - Content
- image-20220709084137-2.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.0 KB - Content
- image-20220709084207-3.jpeg
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.0 KB - Content
- image-20220709084458-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -199.5 KB - Content
- image-20220709085040-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -200.4 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