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, 48 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-20220708101605-2.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,829 +1,774 @@ 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 **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 **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 **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 61 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD 46 +== 1.2 Features == 47 + 48 +* LoRaWAN 1.0.3 Class A 62 62 * Ultra low power consumption 63 -* Distance Detectionby Ultrasonictechnology64 -* Flat objectrange280mm - 7500mm65 -* Accuracy:±(1cm+S*0.3%) (S: Distance)66 -* Cable Length: 25cm50 +* Monitor Soil Moisture 51 +* Monitor Soil Temperature 52 +* Monitor Soil Conductivity 53 +* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865 67 67 * AT Commands to change parameters 68 68 * Uplink on periodically 69 69 * Downlink to change configure 70 70 * IP66 Waterproof Enclosure 71 -* Micro SIM card slot for NB-IoT SIM 72 -* 8500mAh Battery for long term use 58 +* 4000mAh or 8500mAh Battery for long term use 73 73 74 -== 1.3 60 +== 1.3 Specification == 75 75 62 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height. 76 76 77 - (% style="color:#037691" %)**CommonDC Characteristics:**64 +[[image:image-20220606162220-5.png]] 78 78 79 -* Supply Voltage: 2.1v ~~ 3.6v 80 -* Operating Temperature: -40 ~~ 85°C 81 81 82 -(% style="color:#037691" %)**NB-IoT Spec:** 83 83 84 -* - B1 @H-FDD: 2100MHz 85 -* - B3 @H-FDD: 1800MHz 86 -* - B8 @H-FDD: 900MHz 87 -* - B5 @H-FDD: 850MHz 88 -* - B20 @H-FDD: 800MHz 89 -* - B28 @H-FDD: 700MHz 68 +== 1.4 Applications == 90 90 91 - (%style="color:#037691" %)**Battery:**70 +* Smart Agriculture 92 92 93 -* Li/SOCI2 un-chargeable battery 94 -* Capacity: 8500mAh 95 -* Self Discharge: <1% / Year @ 25°C 96 -* Max continuously current: 130mA 97 -* Max boost current: 2A, 1 second 72 +(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 73 + 98 98 99 - (% style="color:#037691"%)**Power Consumption**75 +== 1.5 Firmware Change log == 100 100 101 -* STOP Mode: 10uA @ 3.3v 102 -* Max transmit power: 350mA@3.3v 103 103 104 - ==1.4Applications==78 +**LSE01 v1.0 :** Release 105 105 106 106 107 -* Smart Buildings & Home Automation 108 -* Logistics and Supply Chain Management 109 -* Smart Metering 110 -* Smart Agriculture 111 -* Smart Cities 112 -* Smart Factory 113 113 114 -(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %) 115 - 82 += 2. Configure LSE01 to connect to LoRaWAN network = 116 116 84 +== 2.1 How it works == 117 117 86 +((( 87 +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 88 +))) 118 118 90 +((( 91 +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"]]. 92 +))) 119 119 120 -== 1.5 Pin Definitions == 121 121 122 122 123 - [[image:1657328609906-564.png]]96 +== 2.2 Quick guide to connect to LoRaWAN server (OTAA) == 124 124 98 +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. 125 125 126 126 127 - = 2. Use NDDS75 to communicatewith IoT Server =101 +[[image:1654503992078-669.png]] 128 128 129 129 130 - ==2.1How it==104 +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. 131 131 132 132 133 -((( 134 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75. 135 -))) 107 +(% style="color:blue" %)**Step 1**(%%): Create a device in TTN with the OTAA keys from LSE01. 136 136 109 +Each LSE01 is shipped with a sticker with the default device EUI as below: 137 137 138 -((( 139 -The diagram below shows the working flow in default firmware of NDDS75: 140 -))) 111 +[[image:image-20220606163732-6.jpeg]] 141 141 142 -((( 143 - 144 -))) 113 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot: 145 145 146 - [[image:1657328659945-416.png]]115 +**Add APP EUI in the application** 147 147 148 -((( 149 - 150 -))) 151 151 118 +[[image:1654504596150-405.png]] 152 152 153 -== 2.2 Configure the NDDS75 == 154 154 155 155 156 - ===2.2.1Test Requirement===122 +**Add APP KEY and DEV EUI** 157 157 124 +[[image:1654504683289-357.png]] 158 158 159 -((( 160 -To use NDDS75 in your city, make sure meet below requirements: 161 -))) 162 162 163 -* Your local operator has already distributed a NB-IoT Network there. 164 -* The local NB-IoT network used the band that NDDS75 supports. 165 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server. 166 166 167 -((( 168 -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. 169 -))) 128 +(% style="color:blue" %)**Step 2**(%%): Power on LSE01 170 170 171 171 172 - [[image:1657328756309-230.png]]131 +Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position). 173 173 133 +[[image:image-20220606163915-7.png]] 174 174 175 175 176 -= ==2.2.2InsertSIMcard===136 +(% 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. 177 177 138 +[[image:1654504778294-788.png]] 178 178 140 + 141 + 142 +== 2.3 Uplink Payload == 143 + 144 + 145 +=== 2.3.1 MOD~=0(Default Mode) === 146 + 147 +LSE01 will uplink payload via LoRaWAN with below payload format: 148 + 179 179 ((( 180 - Insertthe NB-IoT Cardgetfromyourprovider.150 +Uplink payload includes in total 11 bytes. 181 181 ))) 182 182 183 -((( 184 -User need to take out the NB-IoT module and insert the SIM card like below: 153 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 154 +|((( 155 +**Size** 156 + 157 +**(bytes)** 158 +)))|**2**|**2**|**2**|**2**|**2**|**1** 159 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|((( 160 +Temperature 161 + 162 +(Reserve, Ignore now) 163 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|((( 164 +MOD & Digital Interrupt 165 + 166 +(Optional) 185 185 ))) 186 186 169 +=== 2.3.2 MOD~=1(Original value) === 187 187 188 - [[image:1657328884227-504.png]]171 +This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation). 189 189 173 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %) 174 +|((( 175 +**Size** 190 190 177 +**(bytes)** 178 +)))|**2**|**2**|**2**|**2**|**2**|**1** 179 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|((( 180 +Temperature 191 191 192 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it === 182 +(Reserve, Ignore now) 183 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|((( 184 +MOD & Digital Interrupt 193 193 186 +(Optional) 187 +))) 194 194 189 +=== 2.3.3 Battery Info === 190 + 195 195 ((( 192 +Check the battery voltage for LSE01. 193 +))) 194 + 196 196 ((( 197 - Userneed to configure NDDS75via 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 NDDS75 and use AT Commands to configure it, as below.196 +Ex1: 0x0B45 = 2885mV 198 198 ))) 198 + 199 +((( 200 +Ex2: 0x0B49 = 2889mV 199 199 ))) 200 200 201 -[[image:image-20220709092052-2.png]] 202 202 203 203 204 - **Connection:**205 +=== 2.3.4 Soil Moisture === 205 205 206 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND 207 +((( 208 +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. 209 +))) 207 207 208 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD 211 +((( 212 +For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is 213 +))) 209 209 210 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD 215 +((( 216 + 217 +))) 211 211 219 +((( 220 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.** 221 +))) 212 212 213 -In the PC, use below serial tool settings: 214 214 215 -* Baud: (% style="color:green" %)**9600** 216 -* Data bits:** (% style="color:green" %)8(%%)** 217 -* Stop bits: (% style="color:green" %)**1** 218 -* Parity: (% style="color:green" %)**None** 219 -* Flow Control: (% style="color:green" %)**None** 220 220 225 +=== 2.3.5 Soil Temperature === 226 + 221 221 ((( 222 - Makesure the switchisinFLASH position,thenpowerondevice byconnectingthejumperonNDDS75.NDDS75 willoutputsystem infooncepower onasbelow,wecan enter the(%style="color:green"%)**password:12345678**(%%)toaccessAT Commandinput.228 + 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 223 223 ))) 224 224 225 -[[image:1657329814315-101.png]] 231 +((( 232 +**Example**: 233 +))) 226 226 235 +((( 236 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C 237 +))) 227 227 228 228 ((( 229 - (%style="color:red" %)**Note: the validAT Commandscan 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]]**240 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C 230 230 ))) 231 231 232 232 233 233 234 -=== 2. 2.4Use CoAP protocoltouplinkdata===245 +=== 2.3.6 Soil Conductivity (EC) === 235 235 247 +((( 248 +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). 249 +))) 236 236 237 -(% 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/]]** 238 - 239 - 240 240 ((( 241 - **Usebelowcommands:**252 +For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm. 242 242 ))) 243 243 244 - *(((245 - (% style="color:blue"%)**AT+PRO=1** (%%) ~/~/ SettouseCoAPprotocoltouplink255 +((( 256 +Generally, the EC value of irrigation water is less than 800uS / cm. 246 246 ))) 247 -* ((( 248 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683 ** (%%)~/~/ to set CoAP server address and port 249 -))) 250 -* ((( 251 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path 252 252 253 - 259 +((( 254 254 255 255 ))) 256 256 257 257 ((( 258 -For parameter description, please refer to AT command set 259 - 260 260 261 261 ))) 262 262 263 - [[image:1657330452568-615.png]]267 +=== 2.3.7 MOD === 264 264 269 +Firmware version at least v2.1 supports changing mode. 265 265 271 +For example, bytes[10]=90 266 266 267 -((( 268 -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 +mod=(bytes[10]>>7)&0x01=1. 269 269 270 - 271 -))) 272 272 273 - [[image:1657330472797-498.png]]276 +**Downlink Command:** 274 274 278 +If payload = 0x0A00, workmode=0 275 275 280 +If** **payload =** **0x0A01, workmode=1 276 276 277 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) === 278 278 279 279 280 -* (% style="color:blue" %)**AT+PRO=2 ** (%%) ~/~/ Set to use UDP protocol to uplink 281 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601 ** (%%) ~/~/ to set UDP server address and port 282 -* (% style="color:blue" %)**AT+CFM=1 ** (%%) ~/~/ If the server does not respond, this command is unnecessary 284 +=== 2.3.8 Decode payload in The Things Network === 283 283 284 - [[image:1657330501006-241.png]]286 +While using TTN network, you can add the payload format to decode the payload. 285 285 286 286 287 -[[image:165 7330533775-472.png]]289 +[[image:1654505570700-128.png]] 288 288 291 +((( 292 +The payload decoder function for TTN is here: 293 +))) 289 289 295 +((( 296 +LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]] 297 +))) 290 290 291 -=== 2.2.6 Use MQTT protocol to uplink data === 292 292 300 +== 2.4 Uplink Interval == 293 293 294 -* (% style="color:blue" %)**AT+PRO=3 ** (%%) ~/~/Set to use MQTT protocol to uplink 295 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883 ** (%%) ~/~/Set MQTT server address and port 296 -* (% style="color:blue" %)**AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT 297 -* (% style="color:blue" %)**AT+UNAME=UNAME **(%%)~/~/Set the username of MQTT 298 -* (% style="color:blue" %)**AT+PWD=PWD **(%%)~/~/Set the password of MQTT 299 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB **(%%)~/~/Set the sending topic of MQTT 300 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB **(%%) ~/~/Set the subscription topic of MQTT 302 +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"]] 301 301 302 -[[image:1657249978444-674.png]] 303 303 304 304 305 - [[image:1657330723006-866.png]]306 +== 2.5 Downlink Payload == 306 306 308 +By default, LSE50 prints the downlink payload to console port. 307 307 310 +[[image:image-20220606165544-8.png]] 311 + 312 + 308 308 ((( 309 - MQTTprotocolhas a much higher powerconsumption compare vs UDP / CoAP protocol. Please check the poweranalyze documentand adjust the uplink period to asuitable interval.314 +(% style="color:blue" %)**Examples:** 310 310 ))) 311 311 317 +((( 318 + 319 +))) 312 312 321 +* ((( 322 +(% style="color:blue" %)**Set TDC** 323 +))) 313 313 314 -=== 2.2.7 Use TCP protocol to uplink data === 325 +((( 326 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01. 327 +))) 315 315 329 +((( 330 +Payload: 01 00 00 1E TDC=30S 331 +))) 316 316 317 -* (% style="color:blue" %)**AT+PRO=4 ** (%%) ~/~/ Set to use TCP protocol to uplink 318 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600 **(%%) ~/~/ to set TCP server address and port 333 +((( 334 +Payload: 01 00 00 3C TDC=60S 335 +))) 319 319 320 -[[image:image-20220709093918-1.png]] 337 +((( 338 + 339 +))) 321 321 341 +* ((( 342 +(% style="color:blue" %)**Reset** 343 +))) 322 322 323 -[[image:image-20220709093918-2.png]] 345 +((( 346 +If payload = 0x04FF, it will reset the LSE01 347 +))) 324 324 325 325 350 +* (% style="color:blue" %)**CFM** 326 326 327 - ===2.2.8ChangeUpdateInterval===352 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0 328 328 329 329 330 -User can use below command to change the (% style="color:green" %)**uplink interval**. 331 331 332 - * (% style="color:blue" %)**AT+TDC=600** (%%)~/~/SetUpdate Intervalto 600s356 +== 2.6 Show Data in DataCake IoT Server == 333 333 334 334 ((( 359 +[[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: 360 +))) 361 + 362 +((( 335 335 364 +))) 336 336 366 +((( 367 +(% style="color:blue" %)**Step 1**(%%): Be sure that your device is programmed and properly connected to the network at this time. 368 +))) 337 337 338 -(% style="color:red" %)**NOTE:** 370 +((( 371 +(% 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: 372 +))) 339 339 340 -(% style="color:red" %)**1: By default, the device will send an uplink message every 1 hour.** 341 341 342 -(% style="color:red" %)**2: When the firmware version is v1.3.2 and later firmware:** 343 -))) 375 +[[image:1654505857935-743.png]] 344 344 345 -(% 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).** 346 346 378 +[[image:1654505874829-548.png]] 347 347 348 348 349 -= =2.3UplinkPayload==381 +(% style="color:blue" %)**Step 3**(%%)**:** Create an account or log in Datacake. 350 350 383 +(% style="color:blue" %)**Step 4**(%%)**:** Search the LSE01 and add DevEUI. 351 351 352 -=== 2.3.1 Before Firmware 1.3.2 === 353 353 386 +[[image:1654505905236-553.png]] 354 354 355 -In this mode, uplink payload includes in total 14 bytes 356 356 357 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %) 358 -|=(% style="width: 60px;" %)((( 359 -**Size(bytes)** 360 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1** 361 -|(% 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"]] 389 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices. 362 362 363 -((( 364 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data. 365 -))) 391 +[[image:1654505925508-181.png]] 366 366 367 367 368 -[[image:1657331036973-987.png]] 369 369 395 +== 2.7 Frequency Plans == 370 370 371 -((( 372 -The payload is **ASCII** string, representative same HEX: 373 -))) 397 +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. 374 374 375 -((( 376 -0x72403155615900640c6c19029200 where: 377 -))) 378 378 379 -* ((( 380 -Device ID: 0x724031556159 = 724031556159 381 -))) 382 -* ((( 383 -Version: 0x0064=100=1.0.0 384 -))) 400 +=== 2.7.1 EU863-870 (EU868) === 385 385 386 -* ((( 387 -BAT: 0x0c6c = 3180 mV = 3.180V 388 -))) 389 -* ((( 390 -Signal: 0x19 = 25 391 -))) 392 -* ((( 393 -Distance: 0x0292= 658 mm 394 -))) 395 -* ((( 396 -Interrupt: 0x00 = 0 402 +(% style="color:#037691" %)** Uplink:** 397 397 404 +868.1 - SF7BW125 to SF12BW125 398 398 406 +868.3 - SF7BW125 to SF12BW125 and SF7BW250 399 399 408 +868.5 - SF7BW125 to SF12BW125 400 400 401 - 402 -))) 410 +867.1 - SF7BW125 to SF12BW125 403 403 404 - === **2.3.2Sincefirmwarev1.3.2** ===412 +867.3 - SF7BW125 to SF12BW125 405 405 414 +867.5 - SF7BW125 to SF12BW125 406 406 407 - In this mode, uplink payload includes69bytesintotalby default.416 +867.7 - SF7BW125 to SF12BW125 408 408 409 - Each time the device uploads a data package,8sets of recorded data will be attached.Upto 32setsofrecorded data can be uploaded.418 +867.9 - SF7BW125 to SF12BW125 410 410 411 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %) 412 -|(% 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 413 -|(% 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 +868.8 - FSK 414 414 415 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data. 416 416 417 - [[image:image-20220908175246-1.png]]423 +(% style="color:#037691" %)** Downlink:** 418 418 425 +Uplink channels 1-9 (RX1) 419 419 420 - Thepayloadis ASCIIstring,representativesame HEX:427 +869.525 - SF9BW125 (RX2 downlink only) 421 421 422 -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: 423 423 424 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317 425 -* (% style="color:red" %)Version: 0x0084=132=1.3.2 426 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V 427 -* (% style="color:blue" %)Singal: 0x1e = 30 428 -* (% style="color:red" %)Mod: 0x01 = 1 429 -* Interrupt: 0x00= 0 430 -* Distance: 0x0039= 57 = 57 431 -* Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]]) 432 -* Distance,Time stamp : 00396319baf0 433 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,....... 434 434 431 +=== 2.7.2 US902-928(US915) === 435 435 433 +Used in USA, Canada and South America. Default use CHE=2 436 436 435 +(% style="color:#037691" %)**Uplink:** 437 437 437 +903.9 - SF7BW125 to SF10BW125 438 438 439 - == 2.4PayloadExplanation andSensorInterface==439 +904.1 - SF7BW125 to SF10BW125 440 440 441 +904.3 - SF7BW125 to SF10BW125 441 441 442 - === 2.4.1DeviceID===443 +904.5 - SF7BW125 to SF10BW125 443 443 445 +904.7 - SF7BW125 to SF10BW125 444 444 445 -((( 446 -By default, the Device ID equal to the last 6 bytes of IMEI. 447 -))) 447 +904.9 - SF7BW125 to SF10BW125 448 448 449 -((( 450 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID 449 +905.1 - SF7BW125 to SF10BW125 451 451 452 - 453 -))) 451 +905.3 - SF7BW125 to SF10BW125 454 454 455 -((( 456 -(% style="color:blue" %)**Example :** 457 -))) 458 458 459 -((( 460 -AT+DEUI=A84041F15612 461 -))) 454 +(% style="color:#037691" %)**Downlink:** 462 462 463 -((( 464 -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. 465 -))) 456 +923.3 - SF7BW500 to SF12BW500 466 466 458 +923.9 - SF7BW500 to SF12BW500 467 467 468 - (%style="color:red"%)**NOTE:Whenthe firmware versionis v1.3.2and later firmware:**460 +924.5 - SF7BW500 to SF12BW500 469 469 470 - (%style="color:red"%)**Bydefault, the Device ID equal tothe last15bits of IMEI.**462 +925.1 - SF7BW500 to SF12BW500 471 471 472 - Usercanuse (%style="color:blue"%)**AT+DEUI**(%%) to set Device ID464 +925.7 - SF7BW500 to SF12BW500 473 473 466 +926.3 - SF7BW500 to SF12BW500 474 474 475 - (%style="color:blue"%)**Example :**468 +926.9 - SF7BW500 to SF12BW500 476 476 477 - AT+DEUI=868411056754138470 +927.5 - SF7BW500 to SF12BW500 478 478 472 +923.3 - SF12BW500(RX2 downlink only) 479 479 480 480 481 -=== 2.4.2 Version Info === 482 482 476 +=== 2.7.3 CN470-510 (CN470) === 483 483 484 -((( 485 -Specify the software version: 0x64=100, means firmware version 1.00. 486 -))) 478 +Used in China, Default use CHE=1 487 487 488 -((( 489 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0. 490 -))) 480 +(% style="color:#037691" %)**Uplink:** 491 491 482 +486.3 - SF7BW125 to SF12BW125 492 492 484 +486.5 - SF7BW125 to SF12BW125 493 493 494 - === 2.4.3BatteryInfo===486 +486.7 - SF7BW125 to SF12BW125 495 495 488 +486.9 - SF7BW125 to SF12BW125 496 496 497 -((( 498 -Ex1: 0x0B45 = 2885mV 499 -))) 490 +487.1 - SF7BW125 to SF12BW125 500 500 501 -((( 502 -Ex2: 0x0B49 = 2889mV 503 -))) 492 +487.3 - SF7BW125 to SF12BW125 504 504 494 +487.5 - SF7BW125 to SF12BW125 505 505 496 +487.7 - SF7BW125 to SF12BW125 506 506 507 -=== 2.4.4 Signal Strength === 508 508 499 +(% style="color:#037691" %)**Downlink:** 509 509 510 -((( 511 -NB-IoT Network signal Strength. 512 -))) 501 +506.7 - SF7BW125 to SF12BW125 513 513 514 -((( 515 -**Ex1: 0x1d = 29** 516 -))) 503 +506.9 - SF7BW125 to SF12BW125 517 517 518 -((( 519 -(% style="color:blue" %)**0**(%%) -113dBm or less 520 -))) 505 +507.1 - SF7BW125 to SF12BW125 521 521 522 -((( 523 -(% style="color:blue" %)**1**(%%) -111dBm 524 -))) 507 +507.3 - SF7BW125 to SF12BW125 525 525 526 -((( 527 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm 528 -))) 509 +507.5 - SF7BW125 to SF12BW125 529 529 530 -((( 531 -(% style="color:blue" %)**31** (%%) -51dBm or greater 532 -))) 511 +507.7 - SF7BW125 to SF12BW125 533 533 534 -((( 535 -(% style="color:blue" %)**99** (%%) Not known or not detectable 536 -))) 513 +507.9 - SF7BW125 to SF12BW125 537 537 515 +508.1 - SF7BW125 to SF12BW125 538 538 517 +505.3 - SF12BW125 (RX2 downlink only) 539 539 540 -=== 2.4.5 Distance === 541 541 542 542 543 - Getthe distance.Flat object range280mm - 7500mm.521 +=== 2.7.4 AU915-928(AU915) === 544 544 545 -((( 546 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is 547 -))) 523 +Default use CHE=2 548 548 549 -((( 550 -((( 551 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.** 552 -))) 553 -))) 525 +(% style="color:#037691" %)**Uplink:** 554 554 555 -((( 556 - 557 -))) 527 +916.8 - SF7BW125 to SF12BW125 558 558 559 -((( 560 - 561 -))) 529 +917.0 - SF7BW125 to SF12BW125 562 562 563 - ===2.4.6DigitalInterrupt ===531 +917.2 - SF7BW125 to SF12BW125 564 564 533 +917.4 - SF7BW125 to SF12BW125 565 565 566 -((( 567 -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. 568 -))) 535 +917.6 - SF7BW125 to SF12BW125 569 569 570 -((( 571 -The command is: 572 -))) 537 +917.8 - SF7BW125 to SF12BW125 573 573 574 -((( 575 -(% 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]])**.** 576 -))) 539 +918.0 - SF7BW125 to SF12BW125 577 577 541 +918.2 - SF7BW125 to SF12BW125 578 578 579 -((( 580 -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. 581 -))) 582 582 544 +(% style="color:#037691" %)**Downlink:** 583 583 584 -((( 585 -Example: 586 -))) 546 +923.3 - SF7BW500 to SF12BW500 587 587 588 -((( 589 -0x(00): Normal uplink packet. 590 -))) 548 +923.9 - SF7BW500 to SF12BW500 591 591 592 -((( 593 -0x(01): Interrupt Uplink Packet. 594 -))) 550 +924.5 - SF7BW500 to SF12BW500 595 595 552 +925.1 - SF7BW500 to SF12BW500 596 596 554 +925.7 - SF7BW500 to SF12BW500 597 597 598 - ===2.4.7+5VOutput===556 +926.3 - SF7BW500 to SF12BW500 599 599 558 +926.9 - SF7BW500 to SF12BW500 600 600 601 -((( 602 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 603 -))) 560 +927.5 - SF7BW500 to SF12BW500 604 604 562 +923.3 - SF12BW500(RX2 downlink only) 605 605 606 -((( 607 -The 5V output time can be controlled by AT Command. 608 608 609 - 610 -))) 611 611 612 -((( 613 -(% style="color:blue" %)**AT+5VT=1000** 566 +=== 2.7.5 AS920-923 & AS923-925 (AS923) === 614 614 615 - 616 -))) 568 +(% style="color:#037691" %)**Default Uplink channel:** 617 617 618 -((( 619 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors. 620 -))) 570 +923.2 - SF7BW125 to SF10BW125 621 621 572 +923.4 - SF7BW125 to SF10BW125 622 622 623 623 624 -= =2.5 DownlinkPayload ==575 +(% style="color:#037691" %)**Additional Uplink Channel**: 625 625 577 +(OTAA mode, channel added by JoinAccept message) 626 626 627 - Bydefault,NDDS75printsthe downlinkpayload to consoleport.579 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**: 628 628 629 - [[image:image-20220709100028-1.png]]581 +922.2 - SF7BW125 to SF10BW125 630 630 583 +922.4 - SF7BW125 to SF10BW125 631 631 632 -((( 633 -(% style="color:blue" %)**Examples:** 634 -))) 585 +922.6 - SF7BW125 to SF10BW125 635 635 636 -((( 637 - 638 -))) 587 +922.8 - SF7BW125 to SF10BW125 639 639 640 -* ((( 641 -(% style="color:blue" %)**Set TDC** 642 -))) 589 +923.0 - SF7BW125 to SF10BW125 643 643 644 -((( 645 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01. 646 -))) 591 +922.0 - SF7BW125 to SF10BW125 647 647 648 -((( 649 -Payload: 01 00 00 1E TDC=30S 650 -))) 651 651 652 -((( 653 -Payload: 01 00 00 3C TDC=60S 654 -))) 594 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**: 655 655 656 -((( 657 - 658 -))) 596 +923.6 - SF7BW125 to SF10BW125 659 659 660 -* ((( 661 -(% style="color:blue" %)**Reset** 662 -))) 598 +923.8 - SF7BW125 to SF10BW125 663 663 664 -((( 665 -If payload = 0x04FF, it will reset the NDDS75 666 -))) 600 +924.0 - SF7BW125 to SF10BW125 667 667 602 +924.2 - SF7BW125 to SF10BW125 668 668 669 - *(%style="color:blue"%)**INTMOD**604 +924.4 - SF7BW125 to SF10BW125 670 670 671 -((( 672 -Downlink Payload: 06000003, Set AT+INTMOD=3 673 -))) 606 +924.6 - SF7BW125 to SF10BW125 674 674 675 675 609 +(% style="color:#037691" %)** Downlink:** 676 676 677 - == 2.6 Distancealarm function(Sincefirmwarev1.3.2)==611 +Uplink channels 1-8 (RX1) 678 678 613 +923.2 - SF10BW125 (RX2) 679 679 680 -(% style="color:blue" %)** ➢ AT Command:** 681 681 682 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max** 683 683 684 - ²Whenmin=0,and max≠0,Alarm higher than max617 +=== 2.7.6 KR920-923 (KR920) === 685 685 686 - ² When min≠0,and max=0, Alarm lowerthanmin619 +Default channel: 687 687 688 - ²Whenmin≠0 and max≠0, Alarm higherthan maxorlower than min621 +922.1 - SF7BW125 to SF12BW125 689 689 623 +922.3 - SF7BW125 to SF12BW125 690 690 691 - (%style="color:blue"%)** Example:**625 +922.5 - SF7BW125 to SF12BW125 692 692 693 -**AT+ LDDSALARM=260,2000** ~/~/ Alarm when distance lower than 260. 694 694 628 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)** 695 695 630 +922.1 - SF7BW125 to SF12BW125 696 696 697 - ==2.7Setthe numberofdata to be uploaded and the recording time ==632 +922.3 - SF7BW125 to SF12BW125 698 698 634 +922.5 - SF7BW125 to SF12BW125 699 699 700 - (%style="color:blue"%)**➢ AT Command:**636 +922.7 - SF7BW125 to SF12BW125 701 701 702 - (% style="color:#037691" %)** AT+TR=900**(%%)~/~/ The unitis seconds,and the default is to record data once every 900 seconds.( The minimum can be set to180 seconds)638 +922.9 - SF7BW125 to SF12BW125 703 703 704 - (% style="color:#037691"%)**AT+NOUD=8** (%%) ~/~/ The device uploads 8 sets of recorded data by default. Up to 32setsofrecord data can be uploaded.640 +923.1 - SF7BW125 to SF12BW125 705 705 642 +923.3 - SF7BW125 to SF12BW125 706 706 707 707 708 - ==2.8 Reador Clearcached data ==645 +(% style="color:#037691" %)**Downlink:** 709 709 647 +Uplink channels 1-7(RX1) 710 710 711 -( %style="color:blue"%)**➢ATCommand:**649 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 712 712 713 -(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data 714 714 715 715 716 - [[image:image-20220908175333-2.png]]653 +=== 2.7.7 IN865-867 (IN865) === 717 717 655 +(% style="color:#037691" %)** Uplink:** 718 718 719 - (% style="color:#037691"%)**AT+CDP=0**(%%) ~/~/ Clear cached data657 +865.0625 - SF7BW125 to SF12BW125 720 720 659 +865.4025 - SF7BW125 to SF12BW125 721 721 661 +865.9850 - SF7BW125 to SF12BW125 722 722 723 -== 2.9 LED Indicator == 724 724 664 +(% style="color:#037691" %) **Downlink:** 725 725 726 - TheNDDS75has aninternalLED which istoshow the status of different state.666 +Uplink channels 1-3 (RX1) 727 727 668 +866.550 - SF10BW125 (RX2) 728 728 729 -* 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) 730 -* Then the LED will be on for 1 second means device is boot normally. 731 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds. 732 -* For each uplink probe, LED will be on for 500ms. 733 733 734 -((( 735 - 736 -))) 737 737 738 738 673 +== 2.8 LED Indicator == 739 739 740 - ==2.10FirmwareChangeLog ==675 +The LSE01 has an internal LED which is to show the status of different state. 741 741 677 +* Blink once when device power on. 678 +* Solid ON for 5 seconds once device successful Join the network. 679 +* Blink once when device transmit a packet. 742 742 681 +== 2.9 Installation in Soil == 682 + 683 +**Measurement the soil surface** 684 + 685 + 686 +[[image:1654506634463-199.png]] 687 + 743 743 ((( 744 -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]] 689 +((( 690 +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. 745 745 ))) 692 +))) 746 746 694 + 695 + 696 +[[image:1654506665940-119.png]] 697 + 747 747 ((( 748 - 699 +Dig a hole with diameter > 20CM. 749 749 ))) 750 750 751 751 ((( 752 - UpgradeInstruction:[[UpgradeFirmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]703 +Horizontal insert the probe to the soil and fill the hole for long term measurement. 753 753 ))) 754 754 755 755 707 +== 2.10 Firmware Change Log == 756 756 757 -== 2.11 Battery Analysis == 709 +((( 710 +**Firmware download link:** 711 +))) 758 758 713 +((( 714 +[[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/]] 715 +))) 759 759 760 -=== 2.11.1 Battery Type === 717 +((( 718 + 719 +))) 761 761 762 - 763 763 ((( 764 - The NDDS75 batteryis a combination of an 8500mAh Li/SOCI2 Batteryanda SuperCapacitor.The batteryis none-rechargeablebatterytype with a lowdischarge rate(<2%peryear).Thisype of battery iscommonlyused in IoTdevicessuch as watermeter.722 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]] 765 765 ))) 766 766 767 767 ((( 768 - Thebattery is designed to last for several years depends on the actually use environment and update interval.726 + 769 769 ))) 770 770 771 771 ((( 772 - The battery related documents as below:730 +**V1.0.** 773 773 ))) 774 774 775 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 776 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 777 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]] 778 - 779 779 ((( 780 - [[image:image-20220709101450-2.png]]734 +Release 781 781 ))) 782 782 783 783 738 +== 2.11 Battery Analysis == 784 784 785 -=== 2.11. 2Powerconsumption Analyze ===740 +=== 2.11.1 Battery Type === 786 786 787 - 788 788 ((( 789 - Draginobatterypoweredproductareall runsinLowPowermode.Wehave an updatebatterycalculatorwhichbase onthemeasurementof thedevice.Usercan use thiscalculatortocheckthebatterylifendcalculatethe batterylifeif wanttouse differenttransmitinterval.743 +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. 790 790 ))) 791 791 792 - 793 793 ((( 794 - Instruction touse asbelow:747 +The battery is designed to last for more than 5 years for the LSN50. 795 795 ))) 796 796 797 797 ((( 798 -(% style="color:blue" %)**Step 1: **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]] 799 -))) 800 - 801 - 802 802 ((( 803 - (%style="color:blue" %)**Step2: **(%%) Openit andchoose752 +The battery-related documents are as below: 804 804 ))) 754 +))) 805 805 806 806 * ((( 807 - Product Model757 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], 808 808 ))) 809 809 * ((( 810 - UplinkInterval760 +[[Lithium-Thionyl Chloride Battery datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]], 811 811 ))) 812 812 * ((( 813 - WorkingMode763 +[[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/]] 814 814 ))) 815 815 816 -((( 817 -And the Life expectation in difference case will be shown on the right. 818 -))) 766 + [[image:image-20220610172436-1.png]] 819 819 820 -[[image:image-20220709110451-3.png]] 821 821 822 822 770 +=== 2.11.2 Battery Note === 823 823 824 -=== 2.11.3 Battery Note === 825 - 826 - 827 827 ((( 828 828 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. 829 829 ))) ... ... @@ -830,217 +830,326 @@ 830 830 831 831 832 832 833 -=== 2.11. 4Replace the battery ===778 +=== 2.11.3 Replace the battery === 834 834 780 +((( 781 +If Battery is lower than 2.7v, user should replace the battery of LSE01. 782 +))) 835 835 836 836 ((( 837 - Thedefault battery packofNDDS75includes aER26500plussupercapacitor.Ifuser can'tfind thispacklocally,theycanfindER26500 orequivalencewithouttheSPC1520capacitor,whichwillalsowork inmost case.TheSPCcanenlargethebatterylifeforhighfrequencyuse(updateperiodbelow5minutes).785 +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. 838 838 ))) 839 839 788 +((( 789 +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) 790 +))) 840 840 841 841 842 -= 3. Access NB-IoT Module = 843 843 794 += 3. Using the AT Commands = 844 844 845 -((( 846 -Users can directly access the AT command set of the NB-IoT module. 847 -))) 796 +== 3.1 Access AT Commands == 848 848 849 -((( 850 -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/]] 851 851 852 - 853 -))) 799 +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. 854 854 855 -[[image:165 7333200519-600.png]]801 +[[image:1654501986557-872.png||height="391" width="800"]] 856 856 857 857 804 +Or if you have below board, use below connection: 858 858 859 -= 4. Using the AT Commands = 860 860 807 +[[image:1654502005655-729.png||height="503" width="801"]] 861 861 862 -== 4.1 Access AT Commands == 863 863 864 864 865 - Seethislinkfordetail: [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]811 +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: 866 866 867 867 868 - AT+<CMD>?: Helpon<CMD>814 + [[image:1654502050864-459.png||height="564" width="806"]] 869 869 870 -AT+<CMD> : Run <CMD> 871 871 872 - AT+<CMD>=<value>:Set thevalue817 +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]] 873 873 874 -AT+<CMD>=? : Get the value 875 875 820 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD> 876 876 822 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD> 823 + 824 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value 825 + 826 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%) : Get the value 827 + 828 + 877 877 (% style="color:#037691" %)**General Commands**(%%) 878 878 879 -AT 831 +(% style="background-color:#dcdcdc" %)**AT**(%%) : Attention 880 880 881 -AT? 833 +(% style="background-color:#dcdcdc" %)**AT?**(%%) : Short Help 882 882 883 -ATZ 835 +(% style="background-color:#dcdcdc" %)**ATZ**(%%) : MCU Reset 884 884 885 -AT+TDC 837 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%) : Application Data Transmission Interval 886 886 887 -AT+CFG : Print all configurations 888 888 889 - AT+CFGMOD: Workingmode selection840 +(% style="color:#037691" %)**Keys, IDs and EUIs management** 890 890 891 -AT+I NTMOD:Setthe trigger interruptmode842 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%) : Application EUI 892 892 893 -AT+ 5VTSetextend the timeof5V power844 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%) : Application Key 894 894 895 -AT+P ROChooseagreement846 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%) : Application Session Key 896 896 897 -AT+ WEIGREGet weightorsetweight to 0848 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%) : Device Address 898 898 899 -AT+ WEIGAPGet or SettheGapValue of weight850 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%) : Device EUI 900 900 901 -AT+ RXDL: Extendthe sendingandreceivingtime852 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%) : Network ID (You can enter this command change only after successful network connection) 902 902 903 -AT+ CNTFACGettcountingparameters854 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%) : Network Session Key Joining and sending date on LoRa network 904 904 905 -AT+ SERVADDR:ServerAddress856 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%) : Confirm Mode 906 906 907 -AT+ TR:Getor Setrecordtime"858 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%) : Confirm Status 908 908 909 -AT+ APNGetorsetthe APN860 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%) : Join LoRa? Network 910 910 911 -AT+ FBAND:GetorSethethertoautomaticallymodify thefrequency band862 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%) : LoRa? Network Join Mode 912 912 913 -AT+ DNSCFGGetetDNS Server864 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%) : LoRa? Network Join Status 914 914 915 -AT+ GETSENSORVALUE :Returnsthecurrentsensormeasurement866 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%) : Print Last Received Data in Raw Format 916 916 917 -AT+ NOUD:Get orSet thenumber ofdatatobeuploaded868 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%) : Print Last Received Data in Binary Format 918 918 919 -AT+ CDP:Reador Clearcached data870 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%) : Send Text Data 920 920 921 -AT+ LDDSALARM:Get orSetalarm ofdistance872 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%) : Send Hexadecimal Data 922 922 923 923 924 -(% style="color:#037691" %)** COAPManagement**875 +(% style="color:#037691" %)**LoRa Network Management** 925 925 926 -AT+ URIResourceparameters877 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%) : Adaptive Rate 927 927 879 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%) : LoRa Class(Currently only support class A 928 928 929 -(% style="color:# 037691" %)**UDPManagement**881 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%) : Duty Cycle Setting 930 930 931 -AT+ CFMUploadconfirmation mode (onlyvalid forUDP)883 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%) : Data Rate (Can Only be Modified after ADR=0) 932 932 885 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%) : Frame Counter Downlink 933 933 934 -(% style="color:# 037691" %)**MQTTManagement**887 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%) : Frame Counter Uplink 935 935 936 -AT+ CLIENT:GetorSetMQTTclient889 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%) : Join Accept Delay1 937 937 938 -AT+ UNAMEGetorSetMQTT Username891 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%) : Join Accept Delay2 939 939 940 -AT+P WDGetSetMQTT password893 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%) : Public Network Mode 941 941 942 -AT+ PUBTOPICGet or SetMQTT publishtopic895 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%) : Receive Delay1 943 943 944 -AT+ SUBTOPICGet or Set MQTT subscriptiontopic897 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%) : Receive Delay2 945 945 899 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%) : Rx2 Window Data Rate 946 946 947 -(% style="color:# 037691" %)**Information**901 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%) : Rx2 Window Frequency 948 948 949 -AT+ FDRFactory DataReset903 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%) : Transmit Power 950 950 951 -AT+ PWORD : SerialAccess Password905 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%) : Set work mode 952 952 953 953 908 +(% style="color:#037691" %)**Information** 954 954 955 -= 5.FAQ=910 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%) : RSSI of the Last Received Packet 956 956 912 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%) : SNR of the Last Received Packet 957 957 958 -= =5.1HowtoUpgradeFirmware==914 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%) : Image Version and Frequency Band 959 959 916 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%) : Factory Data Reset 960 960 918 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%) : Application Port 919 + 920 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%) : Get or Set Frequency (Unit: Hz) for Single Channel Mode 921 + 922 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%) : Get or Set eight channels mode, Only for US915, AU915, CN470 923 + 924 + 925 += 4. FAQ = 926 + 927 +== 4.1 How to change the LoRa Frequency Bands/Region? == 928 + 961 961 ((( 962 -User can upgrade the firmware for 1) bug fix, 2) new feature release. 930 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]]. 931 +When downloading the images, choose the required image file for download. 963 963 ))) 964 964 965 965 ((( 966 - 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]]935 + 967 967 ))) 968 968 969 969 ((( 970 - (%style="color:red"%)**Notice,NDDS75andLDDS75share thememotherboard.Theyuse thesameconnection andmethodto update.**939 +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. 971 971 ))) 972 972 942 +((( 943 + 944 +))) 973 973 946 +((( 947 +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. 948 +))) 974 974 975 -= 6. Trouble Shooting = 950 +((( 951 + 952 +))) 976 976 954 +((( 955 +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. 956 +))) 977 977 978 - == 6.1 Connection problemwhen uploadingfirmware==958 +[[image:image-20220606154726-3.png]] 979 979 980 980 961 +When you use the TTN network, the US915 frequency bands use are: 962 + 963 +* 903.9 - SF7BW125 to SF10BW125 964 +* 904.1 - SF7BW125 to SF10BW125 965 +* 904.3 - SF7BW125 to SF10BW125 966 +* 904.5 - SF7BW125 to SF10BW125 967 +* 904.7 - SF7BW125 to SF10BW125 968 +* 904.9 - SF7BW125 to SF10BW125 969 +* 905.1 - SF7BW125 to SF10BW125 970 +* 905.3 - SF7BW125 to SF10BW125 971 +* 904.6 - SF8BW500 972 + 981 981 ((( 982 -**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]] 974 +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: 975 + 976 +* (% style="color:#037691" %)**AT+CHE=2** 977 +* (% style="color:#037691" %)**ATZ** 983 983 ))) 984 984 985 -(% class="wikigeneratedid" %) 986 986 ((( 987 987 982 + 983 +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. 988 988 ))) 989 989 986 +((( 987 + 988 +))) 990 990 991 -== 6.2 AT Command input doesn't work == 990 +((( 991 +The **AU915** band is similar. Below are the AU915 Uplink Channels. 992 +))) 992 992 994 +[[image:image-20220606154825-4.png]] 993 993 996 + 997 +== 4.2 Can I calibrate LSE01 to different soil types? == 998 + 999 +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]]. 1000 + 1001 + 1002 += 5. Trouble Shooting = 1003 + 1004 +== 5.1 Why I can't join TTN in US915 / AU915 bands? == 1005 + 1006 +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. 1007 + 1008 + 1009 +== 5.2 AT Command input doesn't work == 1010 + 994 994 ((( 995 995 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. 1013 +))) 996 996 997 - 1015 + 1016 +== 5.3 Device rejoin in at the second uplink packet == 1017 + 1018 +(% style="color:#4f81bd" %)**Issue describe as below:** 1019 + 1020 +[[image:1654500909990-784.png]] 1021 + 1022 + 1023 +(% style="color:#4f81bd" %)**Cause for this issue:** 1024 + 1025 +((( 1026 +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. 998 998 ))) 999 999 1000 1000 1001 - =7. OrderInfo=1030 +(% style="color:#4f81bd" %)**Solution: ** 1002 1002 1032 +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: 1003 1003 1004 - Part Number**:** (% style="color:#4f81bd"%)**NSDDS75**1034 +[[image:1654500929571-736.png||height="458" width="832"]] 1005 1005 1006 1006 1037 += 6. Order Info = 1038 + 1039 + 1040 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY** 1041 + 1042 + 1043 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band 1044 + 1045 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band 1046 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band 1047 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band 1048 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band 1049 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band 1050 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band 1051 +* (% style="color:red" %)**IN865**(%%): LoRaWAN IN865 band 1052 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band 1053 + 1054 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option 1055 + 1056 +* (% style="color:red" %)**4**(%%): 4000mAh battery 1057 +* (% style="color:red" %)**8**(%%): 8500mAh battery 1058 + 1007 1007 (% class="wikigeneratedid" %) 1008 1008 ((( 1009 1009 1010 1010 ))) 1011 1011 1012 -= 8.1064 += 7. Packing Info = 1013 1013 1014 1014 ((( 1015 1015 1016 1016 1017 1017 (% style="color:#037691" %)**Package Includes**: 1070 +))) 1018 1018 1019 -* NDDS75 NB-IoT Distance Detect Sensor Node x 11020 - *Externalantennax 11072 +* ((( 1073 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1 1021 1021 ))) 1022 1022 1023 1023 ((( 1024 1024 1025 1025 1026 - 1027 1027 (% style="color:#037691" %)**Dimension and weight**: 1080 +))) 1028 1028 1029 -* Device Size: 13.0 x 5 x 4.5 cm 1030 -* Device Weight: 150g 1031 -* Package Size / pcs : 15 x 12x 5.5 cm 1032 -* Weight / pcs : 220g 1082 +* ((( 1083 +Device Size: cm 1033 1033 ))) 1085 +* ((( 1086 +Device Weight: g 1087 +))) 1088 +* ((( 1089 +Package Size / pcs : cm 1090 +))) 1091 +* ((( 1092 +Weight / pcs : g 1034 1034 1035 -((( 1036 1036 1037 - 1038 - 1039 - 1040 1040 ))) 1041 1041 1042 -= 9.1097 += 8. Support = 1043 1043 1044 - 1045 1045 * 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. 1046 1046 * 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-20220708101605-2.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -87.5 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