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, 47 removed)
- 1657249419225-449.png
- 1657249468462-536.png
- 1657249793983-486.png
- 1657249831934-534.png
- 1657249864775-321.png
- 1657249930215-289.png
- 1657249978444-674.png
- 1657249990869-686.png
- 1657250217799-140.png
- 1657250255956-604.png
- 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-20220708110657-3.png
- image-20220708111918-4.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,73 +1,61 @@ 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 ... ... @@ -81,6 +81,7 @@ 81 81 * Supply Voltage: 2.1v ~~ 3.6v 82 82 * Operating Temperature: -40 ~~ 85°C 83 83 72 + 84 84 (% style="color:#037691" %)**NB-IoT Spec:** 85 85 86 86 * - B1 @H-FDD: 2100MHz ... ... @@ -90,741 +90,719 @@ 90 90 * - B20 @H-FDD: 800MHz 91 91 * - B28 @H-FDD: 700MHz 92 92 93 -(% style="color:#037691" %)**Battery:** 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 83 +(% style="color:#037691" %)**Probe Specification:** 100 100 101 - (%style="color:#037691"%)**PowerConsumption**85 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 102 102 103 -* STOP Mode: 10uA @ 3.3v 104 -* Max transmit power: 350mA@3.3v 87 +[[image:image-20220708101224-1.png]] 105 105 106 106 107 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]]101 +[[image:1657246476176-652.png]] 128 128 129 129 130 130 131 -= 2. UseNDDS75to communicatewithIoTServer=105 += 2. Configure LSE01 to connect to LoRaWAN network = 132 132 107 +== 2.1 How it works == 133 133 134 -== 2.1 How it works == 135 - 136 - 137 137 ((( 138 -The NDDS75isequippedwithaNB-IoT module,thepre-loadedfirmwareinNDDS75willgetenvironmentdatafrom sensorsandsend thevaluetolocalNB-IoTnetworkviatheNB-IoTmodule.The NB-IoTnetworkwillforwardthisvaluetoIoTserver viatheprotocoldefinedbyNDDS75.110 +The LSE01 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LSE0150. It will automatically join the network via OTAA and start to send the sensor value 139 139 ))) 140 140 141 - 142 142 ((( 143 - Thediagrambelowshows theworkingflowindefaultfirmwaref NDDS75:114 +In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>||anchor="H3.200BUsingtheATCommands"]]. 144 144 ))) 145 145 146 -((( 147 - 148 -))) 149 149 150 -[[image:1657328659945-416.png]] 151 151 152 -((( 153 - 154 -))) 119 +== 2.2 Quick guide to connect to LoRaWAN server (OTAA) == 155 155 121 +Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example. 156 156 157 -== 2.2 Configure the NDDS75 == 158 158 124 +[[image:1654503992078-669.png]] 159 159 160 -=== 2.2.1 Test Requirement === 161 161 127 +The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server. 162 162 163 -((( 164 -To use NDDS75 in your city, make sure meet below requirements: 165 -))) 166 166 167 -* Your local operator has already distributed a NB-IoT Network there. 168 -* The local NB-IoT network used the band that NDDS75 supports. 169 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 130 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSE01. 170 170 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 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. 173 -))) 132 +Each LSE01 is shipped with a sticker with the default device EUI as below: 174 174 134 +[[image:image-20220606163732-6.jpeg]] 175 175 176 - [[image:1657328756309-230.png]]136 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: 177 177 138 +**Add APP EUI in the application** 178 178 179 179 180 - === 2.2.2 Insert SIM card ===141 +[[image:1654504596150-405.png]] 181 181 182 182 183 -((( 184 -Insert the NB-IoT Card get from your provider. 185 -))) 186 186 187 -((( 188 -User need to take out the NB-IoT module and insert the SIM card like below: 189 -))) 145 +**Add APP KEY and DEV EUI** 190 190 147 +[[image:1654504683289-357.png]] 191 191 192 -[[image:1657328884227-504.png]] 193 193 194 194 151 +(% style="color:blue" %)**Step 2**(%%): Power on LSE01 195 195 196 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 197 197 154 +Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position). 198 198 199 -((( 200 -((( 201 -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. 202 -))) 203 -))) 156 +[[image:image-20220606163915-7.png]] 204 204 205 -[[image:image-20220709092052-2.png]] 206 206 159 +(% style="color:blue" %)**Step 3**(%%)**:** The LSE01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel. 207 207 208 - (% style="color:blue" %)**Connection:**161 +[[image:1654504778294-788.png]] 209 209 210 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND** 211 211 212 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)** 213 213 214 - **~(%style="background-color:yellow"%)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**165 +== 2.3 Uplink Payload == 215 215 216 216 217 - InthePC, usebelow serialoolsettings:168 +=== 2.3.1 MOD~=0(Default Mode) === 218 218 219 -* Baud: (% style="color:green" %)**9600** 220 -* Data bits:** (% style="color:green" %)8(%%)** 221 -* Stop bits: (% style="color:green" %)**1** 222 -* Parity: (% style="color:green" %)**None** 223 -* Flow Control: (% style="color:green" %)**None** 170 +LSE01 will uplink payload via LoRaWAN with below payload format: 224 224 225 225 ((( 226 - Make sure the switch is in FLASHposition,thenpower ondeviceby connecting the jumper on NDDS75. NDDS75 will output systeminfoonce power onas below,we can enter the (% style="color:green" %)**password:12345678**(%%)to access AT Command input.173 +Uplink payload includes in total 11 bytes. 227 227 ))) 228 228 229 -[[image:1657329814315-101.png]] 176 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 177 +|((( 178 +**Size** 230 230 180 +**(bytes)** 181 +)))|**2**|**2**|**2**|**2**|**2**|**1** 182 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|((( 183 +Temperature 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]]** 185 +(Reserve, Ignore now) 186 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|((( 187 +MOD & Digital Interrupt 188 + 189 +(Optional) 234 234 ))) 235 235 192 +=== 2.3.2 MOD~=1(Original value) === 236 236 194 +This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation). 237 237 238 -=== 2.2.4 Use CoAP protocol to uplink data === 196 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 197 +|((( 198 +**Size** 239 239 200 +**(bytes)** 201 +)))|**2**|**2**|**2**|**2**|**2**|**1** 202 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|((( 203 +Temperature 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/]]** 205 +(Reserve, Ignore now) 206 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|((( 207 +MOD & Digital Interrupt 242 242 209 +(Optional) 210 +))) 243 243 212 +=== 2.3.3 Battery Info === 213 + 244 244 ((( 245 - **Use belowcommands:**215 +Check the battery voltage for LSE01. 246 246 ))) 247 247 248 - *(((249 - (% style="color:blue"%)**AT+PRO=1**(%%) ~/~/ Set to use CoAP protocol to uplink218 +((( 219 +Ex1: 0x0B45 = 2885mV 250 250 ))) 251 -* ((( 252 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 221 + 222 +((( 223 +Ex2: 0x0B49 = 2889mV 253 253 ))) 254 -* ((( 255 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/ Set COAP resource path 256 256 257 257 258 - 227 + 228 +=== 2.3.4 Soil Moisture === 229 + 230 +((( 231 +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. 259 259 ))) 260 260 261 261 ((( 262 -For parameter description, please refer to AT command set 235 +For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is 236 +))) 263 263 238 +((( 264 264 265 265 ))) 266 266 267 -[[image:1657330452568-615.png]] 242 +((( 243 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 244 +))) 268 268 269 269 270 270 248 +=== 2.3.5 Soil Temperature === 249 + 271 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. 251 + 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 252 +))) 273 273 274 - 254 +((( 255 +**Example**: 275 275 ))) 276 276 277 -[[image:1657330472797-498.png]] 258 +((( 259 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 260 +))) 278 278 262 +((( 263 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 264 +))) 279 279 280 280 281 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 282 282 268 +=== 2.3.6 Soil Conductivity (EC) === 283 283 284 - *(% style="color:blue" %)**AT+PRO=2 **(%%) ~/~/ Set to use UDP protocol to uplink285 - *(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601** (%%)~/~/tosetUDPserveraddress andport286 - * (% style="color:blue" %)**AT+CFM=1 ** (%%)~/~/ If the server does not respond, this command is unnecessary270 +((( 271 +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). 272 +))) 287 287 274 +((( 275 +For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 276 +))) 288 288 278 +((( 279 +Generally, the EC value of irrigation water is less than 800uS / cm. 280 +))) 289 289 290 -[[image:1657330501006-241.png]] 282 +((( 283 + 284 +))) 291 291 286 +((( 287 + 288 +))) 292 292 293 - [[image:1657330533775-472.png]]290 +=== 2.3.7 MOD === 294 294 292 +Firmware version at least v2.1 supports changing mode. 295 295 294 +For example, bytes[10]=90 296 296 297 - === 2.2.6 Use MQTT protocol to uplinkdata===296 +mod=(bytes[10]>>7)&0x01=1. 298 298 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 299 +**Downlink Command:** 307 307 308 - [[image:1657249978444-674.png]]301 +If payload = 0x0A00, workmode=0 309 309 303 +If** **payload =** **0x0A01, workmode=1 310 310 311 -[[image:1657330723006-866.png]] 312 312 313 313 314 -((( 315 -MQTT protocol has a much higher power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval. 316 -))) 307 +=== 2.3.8 Decode payload in The Things Network === 317 317 309 +While using TTN network, you can add the payload format to decode the payload. 318 318 319 319 320 - ===2.2.7 Use TCPprotocol to uplink data ===312 +[[image:1654505570700-128.png]] 321 321 314 +((( 315 +The payload decoder function for TTN is here: 316 +))) 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 318 +((( 319 +LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]] 320 +))) 325 325 326 -[[image:image-20220709093918-1.png]] 327 327 323 +== 2.4 Uplink Interval == 328 328 329 - [[image:image-20220709093918-2.png]]325 +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"]] 330 330 331 331 332 332 333 -== =2.2.8ChangeUpdate Interval ===329 +== 2.5 Downlink Payload == 334 334 331 +By default, LSE50 prints the downlink payload to console port. 335 335 336 - User can use below command to changethe (% style="color:green" %)**uplink interval**.333 +[[image:image-20220606165544-8.png]] 337 337 338 -* (% style="color:blue" %)**AT+TDC=600 ** (%%)~/~/ Set Update Interval to 600s 339 339 340 340 ((( 337 +(% style="color:blue" %)**Examples:** 338 +))) 339 + 340 +((( 341 341 342 +))) 342 342 344 +* ((( 345 +(% style="color:blue" %)**Set TDC** 346 +))) 343 343 344 -(% style="color:red" %)**NOTE:** 348 +((( 349 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01. 350 +))) 345 345 346 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.** 352 +((( 353 +Payload: 01 00 00 1E TDC=30S 354 +))) 347 347 348 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:** 356 +((( 357 +Payload: 01 00 00 3C TDC=60S 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).** 360 +((( 361 + 362 +))) 352 352 364 +* ((( 365 +(% style="color:blue" %)**Reset** 366 +))) 353 353 368 +((( 369 +If payload = 0x04FF, it will reset the LSE01 370 +))) 354 354 355 -== 2.3 Uplink Payload == 356 356 373 +* (% style="color:blue" %)**CFM** 357 357 358 - ===2.3.1BeforeFirmwarev1.3.2===375 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0 359 359 360 360 361 -In this mode, uplink payload includes in total 14 bytes 362 362 363 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 364 -|=(% style="width: 60px;" %)((( 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="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"]] 379 +== 2.6 Show Data in DataCake IoT Server == 368 368 369 369 ((( 370 - If weusetheMQTTclient to subscribe tothisMQTTtopic, we can seethefollowing informationwhentheNDDS751uplinkdata.382 +[[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: 371 371 ))) 372 372 373 - 374 -[[image:1657331036973-987.png]] 375 - 376 - 377 377 ((( 378 - Thepayload is **ASCII** string, representative same HEX:386 + 379 379 ))) 380 380 381 381 ((( 382 - 0x72403155615900640c6c19029200where:390 +(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time. 383 383 ))) 384 384 385 - *(((386 - DeviceID:0x724031556159=724031556159393 +((( 394 +(% 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: 387 387 ))) 388 -* ((( 389 -Version: 0x0064=100=1.0.0 390 -))) 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 403 403 398 +[[image:1654505857935-743.png]] 404 404 405 405 401 +[[image:1654505874829-548.png]] 406 406 407 - 408 -))) 409 409 410 -= ==**2.3.2Sincefirmwarev1.3.2** ===404 +(% style="color:blue" %)**Step 3**(%%)**:** Create an account or log in Datacake. 411 411 406 +(% style="color:blue" %)**Step 4**(%%)**:** Search the LSE01 and add DevEUI. 412 412 413 -In this mode, uplink payload includes 69 bytes in total by default. 414 414 415 - Each time the device uploads a data package, 8 sets of recorded data will be attached.Upto 32 sets of recorded data canbe uploaded.409 +[[image:1654505905236-553.png]] 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....... 420 420 421 - Ifweuse theMQTT clienttosubscribeto this MQTTtopic,wecansee the followinginformation whentheNDDS75 uplinkdata.412 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices. 422 422 423 -[[image: image-20220908175246-1.png]]414 +[[image:1654505925508-181.png]] 424 424 425 425 426 -The payload is ASCII string, representative same HEX: 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:418 +== 2.7 Frequency Plans == 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**//,....... 420 +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. 440 440 441 441 423 +=== 2.7.1 EU863-870 (EU868) === 442 442 443 - ==2.4 Payload Explanation and SensorInterface==425 +(% style="color:#037691" %)** Uplink:** 444 444 427 +868.1 - SF7BW125 to SF12BW125 445 445 446 - ===2.4.1DeviceID===429 +868.3 - SF7BW125 to SF12BW125 and SF7BW250 447 447 431 +868.5 - SF7BW125 to SF12BW125 448 448 449 -((( 450 -By default, the Device ID equal to the last 6 bytes of IMEI. 451 -))) 433 +867.1 - SF7BW125 to SF12BW125 452 452 453 -((( 454 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 435 +867.3 - SF7BW125 to SF12BW125 455 455 456 - 457 -))) 437 +867.5 - SF7BW125 to SF12BW125 458 458 459 -((( 460 -(% style="color:blue" %)**Example :** 461 -))) 439 +867.7 - SF7BW125 to SF12BW125 462 462 463 -((( 464 -AT+DEUI=A84041F15612 465 -))) 441 +867.9 - SF7BW125 to SF12BW125 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 -))) 443 +868.8 - FSK 470 470 471 471 472 -(% style="color: red" %)**NOTE:When the firmware versionis v1.3.2 andlater firmware:**446 +(% style="color:#037691" %)** Downlink:** 473 473 474 - (% style="color:red" %)**By default, the DeviceID equal to theast15bits of IMEI.**448 +Uplink channels 1-9 (RX1) 475 475 476 - Usercanuse(%style="color:blue" %)**AT+DEUI**(%%) to set Device ID450 +869.525 - SF9BW125 (RX2 downlink only) 477 477 478 478 479 -(% style="color:blue" %)**Example :** 480 480 481 - AT+DEUI=868411056754138454 +=== 2.7.2 US902-928(US915) === 482 482 456 +Used in USA, Canada and South America. Default use CHE=2 483 483 458 +(% style="color:#037691" %)**Uplink:** 484 484 485 - ===2.4.2VersionInfo ===460 +903.9 - SF7BW125 to SF10BW125 486 486 462 +904.1 - SF7BW125 to SF10BW125 487 487 488 -((( 489 -Specify the software version: 0x64=100, means firmware version 1.00. 490 -))) 464 +904.3 - SF7BW125 to SF10BW125 491 491 492 -((( 493 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 494 -))) 466 +904.5 - SF7BW125 to SF10BW125 495 495 468 +904.7 - SF7BW125 to SF10BW125 496 496 470 +904.9 - SF7BW125 to SF10BW125 497 497 498 - === 2.4.3BatteryInfo===472 +905.1 - SF7BW125 to SF10BW125 499 499 474 +905.3 - SF7BW125 to SF10BW125 500 500 501 -((( 502 -Ex1: 0x0B45 = 2885mV 503 -))) 504 504 505 -((( 506 -Ex2: 0x0B49 = 2889mV 507 -))) 477 +(% style="color:#037691" %)**Downlink:** 508 508 479 +923.3 - SF7BW500 to SF12BW500 509 509 481 +923.9 - SF7BW500 to SF12BW500 510 510 511 - ===2.4.4SignalStrength===483 +924.5 - SF7BW500 to SF12BW500 512 512 485 +925.1 - SF7BW500 to SF12BW500 513 513 514 -((( 515 -NB-IoT Network signal Strength. 516 -))) 487 +925.7 - SF7BW500 to SF12BW500 517 517 518 -((( 519 -**Ex1: 0x1d = 29** 520 -))) 489 +926.3 - SF7BW500 to SF12BW500 521 521 522 -((( 523 -(% style="color:blue" %)**0**(%%) -113dBm or less 524 -))) 491 +926.9 - SF7BW500 to SF12BW500 525 525 526 -((( 527 -(% style="color:blue" %)**1**(%%) -111dBm 528 -))) 493 +927.5 - SF7BW500 to SF12BW500 529 529 530 -((( 531 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 532 -))) 495 +923.3 - SF12BW500(RX2 downlink only) 533 533 534 -((( 535 -(% style="color:blue" %)**31** (%%) -51dBm or greater 536 -))) 537 537 538 -((( 539 -(% style="color:blue" %)**99** (%%) Not known or not detectable 540 -))) 541 541 499 +=== 2.7.3 CN470-510 (CN470) === 542 542 501 +Used in China, Default use CHE=1 543 543 544 - ===2.4.5 Distance==503 +(% style="color:#037691" %)**Uplink:** 545 545 505 +486.3 - SF7BW125 to SF12BW125 546 546 547 - Get the distance. Flatobjectrange280mm - 7500mm.507 +486.5 - SF7BW125 to SF12BW125 548 548 549 -((( 550 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 551 -))) 509 +486.7 - SF7BW125 to SF12BW125 552 552 553 -((( 554 -((( 555 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 556 -))) 557 -))) 511 +486.9 - SF7BW125 to SF12BW125 558 558 559 -((( 560 - 561 -))) 513 +487.1 - SF7BW125 to SF12BW125 562 562 563 -((( 564 - 565 -))) 515 +487.3 - SF7BW125 to SF12BW125 566 566 567 - === 2.4.6DigitalInterrupt===517 +487.5 - SF7BW125 to SF12BW125 568 568 519 +487.7 - SF7BW125 to SF12BW125 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 573 574 -((( 575 -The command is: 576 -))) 522 +(% style="color:#037691" %)**Downlink:** 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 -))) 524 +506.7 - SF7BW125 to SF12BW125 581 581 526 +506.9 - SF7BW125 to SF12BW125 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 -))) 528 +507.1 - SF7BW125 to SF12BW125 586 586 530 +507.3 - SF7BW125 to SF12BW125 587 587 588 -((( 589 -Example: 590 -))) 532 +507.5 - SF7BW125 to SF12BW125 591 591 592 -((( 593 -0x(00): Normal uplink packet. 594 -))) 534 +507.7 - SF7BW125 to SF12BW125 595 595 596 -((( 597 -0x(01): Interrupt Uplink Packet. 598 -))) 536 +507.9 - SF7BW125 to SF12BW125 599 599 538 +508.1 - SF7BW125 to SF12BW125 600 600 540 +505.3 - SF12BW125 (RX2 downlink only) 601 601 602 -=== 2.4.7 +5V Output === 603 603 604 604 605 -((( 606 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 607 -))) 544 +=== 2.7.4 AU915-928(AU915) === 608 608 546 +Default use CHE=2 609 609 610 -((( 611 -The 5V output time can be controlled by AT Command. 548 +(% style="color:#037691" %)**Uplink:** 612 612 613 - 614 -))) 550 +916.8 - SF7BW125 to SF12BW125 615 615 616 -((( 617 -(% style="color:blue" %)**AT+5VT=1000** 552 +917.0 - SF7BW125 to SF12BW125 618 618 619 - 620 -))) 554 +917.2 - SF7BW125 to SF12BW125 621 621 622 -((( 623 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 624 -))) 556 +917.4 - SF7BW125 to SF12BW125 625 625 558 +917.6 - SF7BW125 to SF12BW125 626 626 560 +917.8 - SF7BW125 to SF12BW125 627 627 628 - ==2.5DownlinkPayload ==562 +918.0 - SF7BW125 to SF12BW125 629 629 564 +918.2 - SF7BW125 to SF12BW125 630 630 631 -By default, NDDS75 prints the downlink payload to console port. 632 632 633 - [[image:image-20220709100028-1.png]]567 +(% style="color:#037691" %)**Downlink:** 634 634 569 +923.3 - SF7BW500 to SF12BW500 635 635 636 -((( 637 -(% style="color:blue" %)**Examples:** 638 -))) 571 +923.9 - SF7BW500 to SF12BW500 639 639 640 -((( 641 - 642 -))) 573 +924.5 - SF7BW500 to SF12BW500 643 643 644 -* ((( 645 -(% style="color:blue" %)**Set TDC** 646 -))) 575 +925.1 - SF7BW500 to SF12BW500 647 647 648 -((( 649 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 650 -))) 577 +925.7 - SF7BW500 to SF12BW500 651 651 652 -((( 653 -Payload: 01 00 00 1E TDC=30S 654 -))) 579 +926.3 - SF7BW500 to SF12BW500 655 655 656 -((( 657 -Payload: 01 00 00 3C TDC=60S 658 -))) 581 +926.9 - SF7BW500 to SF12BW500 659 659 660 -((( 661 - 662 -))) 583 +927.5 - SF7BW500 to SF12BW500 663 663 664 -* ((( 665 -(% style="color:blue" %)**Reset** 666 -))) 585 +923.3 - SF12BW500(RX2 downlink only) 667 667 668 -((( 669 -If payload = 0x04FF, it will reset the NDDS75 670 -))) 671 671 672 672 673 - *(%style="color:blue"%)**INTMOD**589 +=== 2.7.5 AS920-923 & AS923-925 (AS923) === 674 674 675 -((( 676 -Downlink Payload: 06000003, Set AT+INTMOD=3 677 -))) 591 +(% style="color:#037691" %)**Default Uplink channel:** 678 678 593 +923.2 - SF7BW125 to SF10BW125 679 679 595 +923.4 - SF7BW125 to SF10BW125 680 680 681 -== 2.6 Distance alarm function(Since firmware v1.3.2) == 682 682 598 +(% style="color:#037691" %)**Additional Uplink Channel**: 683 683 684 -( %style="color:blue"%)**➢ATCommand:**600 +(OTAA mode, channel added by JoinAccept message) 685 685 686 -(% style="color:#037691" %)** T+ LDDSALARM=min,max**602 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**: 687 687 688 - ²Whenmin=0, and max≠0, Alarm higherthanmax604 +922.2 - SF7BW125 to SF10BW125 689 689 690 - ²Whenmin≠0, and max=0, Alarm lowerthan min606 +922.4 - SF7BW125 to SF10BW125 691 691 692 - ²Whenmin≠0 and max≠0, Alarm higherthan maxorlower than min608 +922.6 - SF7BW125 to SF10BW125 693 693 610 +922.8 - SF7BW125 to SF10BW125 694 694 695 - (%style="color:blue"%)** Example:**612 +923.0 - SF7BW125 to SF10BW125 696 696 697 - **AT+ LDDSALARM=260,2000**~/~/ Alarm when distance lowerthan 260.614 +922.0 - SF7BW125 to SF10BW125 698 698 699 699 617 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**: 700 700 701 - ==2.7Setthe numberofdata to be uploaded and the recording time ==619 +923.6 - SF7BW125 to SF10BW125 702 702 621 +923.8 - SF7BW125 to SF10BW125 703 703 704 - (%style="color:blue"%)**➢ AT Command:**623 +924.0 - SF7BW125 to SF10BW125 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. 625 +924.2 - SF7BW125 to SF10BW125 708 708 627 +924.4 - SF7BW125 to SF10BW125 709 709 629 +924.6 - SF7BW125 to SF10BW125 710 710 711 711 712 - ==2.8 Reador Clearcacheddata ==632 +(% style="color:#037691" %)** Downlink:** 713 713 634 +Uplink channels 1-8 (RX1) 714 714 715 - (%style="color:blue"%)**➢ AT Command:**636 +923.2 - SF10BW125 (RX2) 716 716 717 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 718 -* (% style="color:#037691" %)** AT+CDP=0** (%%) ~/~/ Clear cached data 719 719 720 -[[image:image-20220908175333-2.png]] 721 721 640 +=== 2.7.6 KR920-923 (KR920) === 722 722 642 +Default channel: 723 723 724 - ==2.9LEDIndicator==644 +922.1 - SF7BW125 to SF12BW125 725 725 646 +922.3 - SF7BW125 to SF12BW125 726 726 727 - TheNDDS75has an internal LED which is toshow the status of different state.648 +922.5 - SF7BW125 to SF12BW125 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. 651 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)** 734 734 735 -((( 736 - 737 -))) 653 +922.1 - SF7BW125 to SF12BW125 738 738 655 +922.3 - SF7BW125 to SF12BW125 739 739 657 +922.5 - SF7BW125 to SF12BW125 740 740 741 - ==2.10FirmwareChange Log==659 +922.7 - SF7BW125 to SF12BW125 742 742 661 +922.9 - SF7BW125 to SF12BW125 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 -))) 663 +923.1 - SF7BW125 to SF12BW125 747 747 748 -((( 749 - 750 -))) 665 +923.3 - SF7BW125 to SF12BW125 751 751 752 -((( 753 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]] 754 -))) 755 755 668 +(% style="color:#037691" %)**Downlink:** 756 756 670 +Uplink channels 1-7(RX1) 757 757 758 - ==2.11BatteryAnalysis==672 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 759 759 760 760 761 -=== 2.11.1 Battery Type === 762 762 676 +=== 2.7.7 IN865-867 (IN865) === 763 763 678 +(% style="color:#037691" %)** Uplink:** 679 + 680 +865.0625 - SF7BW125 to SF12BW125 681 + 682 +865.4025 - SF7BW125 to SF12BW125 683 + 684 +865.9850 - SF7BW125 to SF12BW125 685 + 686 + 687 +(% style="color:#037691" %) **Downlink:** 688 + 689 +Uplink channels 1-3 (RX1) 690 + 691 +866.550 - SF10BW125 (RX2) 692 + 693 + 694 + 695 + 696 +== 2.8 LED Indicator == 697 + 698 +The LSE01 has an internal LED which is to show the status of different state. 699 + 700 +* Blink once when device power on. 701 +* Solid ON for 5 seconds once device successful Join the network. 702 +* Blink once when device transmit a packet. 703 + 704 +== 2.9 Installation in Soil == 705 + 706 +**Measurement the soil surface** 707 + 708 + 709 +[[image:1654506634463-199.png]] 710 + 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. 712 +((( 713 +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 ))) 715 +))) 767 767 717 + 718 + 719 +[[image:1654506665940-119.png]] 720 + 768 768 ((( 769 - The batteryis designedto lastfor severalyearsdepends ontheactually use environmentand updateinterval.722 +Dig a hole with diameter > 20CM. 770 770 ))) 771 771 772 772 ((( 773 - The batteryrelateddocumentsasbelow:726 +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 730 +== 2.10 Firmware Change Log == 731 + 780 780 ((( 781 - [[image:image-20220709101450-2.png]]733 +**Firmware download link:** 782 782 ))) 783 783 736 +((( 737 +[[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/]] 738 +))) 784 784 740 +((( 741 + 742 +))) 785 785 786 -=== 2.11.2 Power consumption Analyze === 744 +((( 745 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 746 +))) 787 787 748 +((( 749 + 750 +))) 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.753 +**V1.0.** 791 791 ))) 792 792 756 +((( 757 +Release 758 +))) 793 793 760 + 761 +== 2.11 Battery Analysis == 762 + 763 +=== 2.11.1 Battery Type === 764 + 794 794 ((( 795 - Instruction touse as below:766 +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/]]770 +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 774 +((( 775 +The battery-related documents are as below: 805 805 ))) 777 +))) 806 806 807 807 * ((( 808 - Product Model780 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], 809 809 ))) 810 810 * ((( 811 - UplinkInterval783 +[[Lithium-Thionyl Chloride Battery datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], 812 812 ))) 813 813 * ((( 814 - WorkingMode786 +[[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 -))) 789 + [[image:image-20220610172436-1.png]] 820 820 821 -[[image:image-20220709110451-3.png]] 822 822 823 823 793 +=== 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 ===801 +=== 2.11.3 Replace the battery === 835 835 803 +((( 804 +If Battery is lower than 2.7v, user should replace the battery of LSE01. 805 +))) 836 836 837 837 ((( 838 - Thedefault battery packofNDDS75includes aER26500plussupercapacitor.Ifuser can'tfind thispacklocally,theycanfindER26500 orequivalencewithouttheSPC1520capacitor,whichwillalsowork inmost case.TheSPCcanenlargethebatterylifeforhighfrequencyuse(updateperiodbelow5minutes).808 +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 811 +((( 812 +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) 813 +))) 841 841 842 842 843 -= 3. Access NB-IoT Module = 844 844 817 += 3. Using the AT Commands = 845 845 846 -((( 847 -Users can directly access the AT command set of the NB-IoT module. 848 -))) 819 +== 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 -))) 822 +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]]824 +[[image:1654501986557-872.png||height="391" width="800"]] 857 857 858 858 827 +Or if you have below board, use below connection: 859 859 860 -= 4. Using the AT Commands = 861 861 830 +[[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]]834 +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>837 + [[image:1654502050864-459.png||height="564" width="806"]] 870 870 871 -AT+<CMD> : Run <CMD> 872 872 873 - AT+<CMD>=<value>:Set thevalue840 +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 843 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD> 877 877 845 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD> 846 + 847 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value 848 + 849 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%) : Get the value 850 + 851 + 878 878 (% style="color:#037691" %)**General Commands**(%%) 879 879 880 -AT 854 +(% style="background-color:#dcdcdc" %)**AT**(%%) : Attention 881 881 882 -AT? 856 +(% style="background-color:#dcdcdc" %)**AT?**(%%) : Short Help 883 883 884 -ATZ 858 +(% style="background-color:#dcdcdc" %)**ATZ**(%%) : MCU Reset 885 885 886 -AT+TDC 860 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%) : Application Data Transmission Interval 887 887 888 -AT+CFG : Print all configurations 889 889 890 - AT+CFGMOD:Workingmodeselection863 +(% style="color:#037691" %)**Keys, IDs and EUIs management** 891 891 892 -AT+I NTMOD:Setthe trigger interruptmode865 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%) : Application EUI 893 893 894 -AT+ 5VTSetextend the timeof5V power867 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%) : Application Key 895 895 896 -AT+P ROChooseagreement869 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%) : Application Session Key 897 897 898 -AT+ WEIGREGet weightorsetweight to 0871 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%) : Device Address 899 899 900 -AT+ WEIGAPGet or SettheGapValue of weight873 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%) : Device EUI 901 901 902 -AT+ RXDL: Extendthe sendingandreceivingtime875 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%) : Network ID (You can enter this command change only after successful network connection) 903 903 904 -AT+ CNTFACGettcountingparameters877 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%) : Network Session Key Joining and sending date on LoRa network 905 905 906 -AT+ SERVADDR:ServerAddress879 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%) : Confirm Mode 907 907 908 -AT+ TRGetor Setrecordtime"881 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%) : Confirm Status 909 909 910 -AT+ APNGetorsetthe APN883 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%) : Join LoRa? Network 911 911 912 -AT+ FBAND:GetorSethethertoautomaticallymodify thefrequency band885 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%) : LoRa? Network Join Mode 913 913 914 -AT+ DNSCFGGetetDNS Server887 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%) : LoRa? Network Join Status 915 915 916 -AT+ GETSENSORVALUE :Returnsthecurrentsensormeasurement889 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%) : Print Last Received Data in Raw Format 917 917 918 -AT+ NOUD:Get orSet thenumber ofdatatobeuploaded891 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%) : Print Last Received Data in Binary Format 919 919 920 -AT+ CDP:Reador Clearcached data893 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%) : Send Text Data 921 921 922 -AT+ LDDSALARM:Get orSetalarm ofdistance895 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%) : Send Hexadecimal Data 923 923 924 924 925 -(% style="color:#037691" %)** COAPManagement**898 +(% style="color:#037691" %)**LoRa Network Management** 926 926 927 -AT+ URIResourceparameters900 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%) : Adaptive Rate 928 928 902 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%) : LoRa Class(Currently only support class A 929 929 930 -(% style="color:# 037691" %)**UDPManagement**904 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%) : Duty Cycle Setting 931 931 932 -AT+ CFM:Uploadconfirmationmode (onlyvalid forUDP)906 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%) : Data Rate (Can Only be Modified after ADR=0) 933 933 908 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%) : Frame Counter Downlink 934 934 935 -(% style="color:# 037691" %)**MQTTManagement**910 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%) : Frame Counter Uplink 936 936 937 -AT+ CLIENTGetorSetMQTT client912 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%) : Join Accept Delay1 938 938 939 -AT+ UNAMEGetorSetMQTT Username914 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%) : Join Accept Delay2 940 940 941 -AT+P WDGetSetMQTT password916 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%) : Public Network Mode 942 942 943 -AT+ PUBTOPIC:Get or SetMQTT publishtopic918 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%) : Receive Delay1 944 944 945 -AT+ SUBTOPIC:Get or Set MQTT subscriptiontopic920 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%) : Receive Delay2 946 946 922 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%) : Rx2 Window Data Rate 947 947 948 -(% style="color:# 037691" %)**Information**924 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%) : Rx2 Window Frequency 949 949 950 -AT+ FDRFactory DataReset926 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%) : Transmit Power 951 951 952 -AT+ PWORD :rialAccess Password928 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%) : Set work mode 953 953 954 954 931 +(% style="color:#037691" %)**Information** 955 955 956 -= 5.FAQ=933 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%) : RSSI of the Last Received Packet 957 957 935 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%) : SNR of the Last Received Packet 958 958 959 -= =5.1HowtoUpgradeFirmware==937 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%) : Image Version and Frequency Band 960 960 939 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Factory Data Reset 961 961 941 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%) : Application Port 942 + 943 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%) : Get or Set Frequency (Unit: Hz) for Single Channel Mode 944 + 945 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%) : Get or Set eight channels mode, Only for US915, AU915, CN470 946 + 947 + 948 += 4. FAQ = 949 + 950 +== 4.1 How to change the LoRa Frequency Bands/Region? == 951 + 962 962 ((( 963 -User can upgrade the firmware for 1) bug fix, 2) new feature release. 953 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]]. 954 +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]]958 + 968 968 ))) 969 969 970 970 ((( 971 - (%style="color:red"%)**Notice,NDDS75andLDDS75share thememotherboard.Theyuse thesameconnection andmethodto update.**962 +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 965 +((( 966 + 967 +))) 974 974 969 +((( 970 +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. 971 +))) 975 975 976 -= 6. Trouble Shooting = 973 +((( 974 + 975 +))) 977 977 977 +((( 978 +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. 979 +))) 978 978 979 - == 6.1 Connection problemwhen uploadingfirmware==981 +[[image:image-20220606154726-3.png]] 980 980 981 981 984 +When you use the TTN network, the US915 frequency bands use are: 985 + 986 +* 903.9 - SF7BW125 to SF10BW125 987 +* 904.1 - SF7BW125 to SF10BW125 988 +* 904.3 - SF7BW125 to SF10BW125 989 +* 904.5 - SF7BW125 to SF10BW125 990 +* 904.7 - SF7BW125 to SF10BW125 991 +* 904.9 - SF7BW125 to SF10BW125 992 +* 905.1 - SF7BW125 to SF10BW125 993 +* 905.3 - SF7BW125 to SF10BW125 994 +* 904.6 - SF8BW500 995 + 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]] 997 +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: 998 + 999 +* (% style="color:#037691" %)**AT+CHE=2** 1000 +* (% style="color:#037691" %)**ATZ** 984 984 ))) 985 985 986 -(% class="wikigeneratedid" %) 987 987 ((( 988 988 1005 + 1006 +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 1009 +((( 1010 + 1011 +))) 991 991 992 -== 6.2 AT Command input doesn't work == 1013 +((( 1014 +The **AU915** band is similar. Below are the AU915 Uplink Channels. 1015 +))) 993 993 1017 +[[image:image-20220606154825-4.png]] 994 994 1019 + 1020 +== 4.2 Can I calibrate LSE01 to different soil types? == 1021 + 1022 +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]]. 1023 + 1024 + 1025 += 5. Trouble Shooting = 1026 + 1027 +== 5.1 Why I can't join TTN in US915 / AU915 bands? == 1028 + 1029 +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. 1030 + 1031 + 1032 +== 5.2 AT Command input doesn't work == 1033 + 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. 1036 +))) 997 997 998 - 1038 + 1039 +== 5.3 Device rejoin in at the second uplink packet == 1040 + 1041 +(% style="color:#4f81bd" %)**Issue describe as below:** 1042 + 1043 +[[image:1654500909990-784.png]] 1044 + 1045 + 1046 +(% style="color:#4f81bd" %)**Cause for this issue:** 1047 + 1048 +((( 1049 +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=1053 +(% style="color:#4f81bd" %)**Solution: ** 1003 1003 1055 +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**1057 +[[image:1654500929571-736.png||height="458" width="832"]] 1006 1006 1007 1007 1060 += 6. Order Info = 1061 + 1062 + 1063 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY** 1064 + 1065 + 1066 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band 1067 + 1068 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band 1069 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band 1070 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band 1071 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band 1072 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band 1073 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band 1074 +* (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1075 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1076 + 1077 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option 1078 + 1079 +* (% style="color:red" %)**4**(%%): 4000mAh battery 1080 +* (% style="color:red" %)**8**(%%): 8500mAh battery 1081 + 1008 1008 (% class="wikigeneratedid" %) 1009 1009 ((( 1010 1010 1011 1011 ))) 1012 1012 1013 -= 8.1087 += 7. Packing Info = 1014 1014 1015 1015 ((( 1016 1016 1017 1017 1018 1018 (% style="color:#037691" %)**Package Includes**: 1093 +))) 1019 1019 1020 -* NDDS75 NB-IoT Distance Detect Sensor Node x 11021 - *Externalantennax 11095 +* ((( 1096 +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**: 1103 +))) 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 1105 +* ((( 1106 +Device Size: cm 1034 1034 ))) 1108 +* ((( 1109 +Device Weight: g 1110 +))) 1111 +* ((( 1112 +Package Size / pcs : cm 1113 +))) 1114 +* ((( 1115 +Weight / pcs : g 1035 1035 1036 -((( 1037 1037 1038 - 1039 - 1040 - 1041 1041 ))) 1042 1042 1043 -= 9.1120 += 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]]
- 1657249419225-449.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -81.0 KB - Content
- 1657249468462-536.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -483.6 KB - Content
- 1657249793983-486.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -85.8 KB - Content
- 1657249831934-534.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -72.5 KB - Content
- 1657249864775-321.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -87.0 KB - Content
- 1657249930215-289.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -77.3 KB - Content
- 1657249978444-674.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -139.5 KB - Content
- 1657249990869-686.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -96.9 KB - Content
- 1657250217799-140.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -98.7 KB - Content
- 1657250255956-604.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -99.0 KB - Content
- 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-20220708110657-3.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -251.7 KB - Content
- image-20220708111918-4.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -38.8 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