Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 104.2
edited by Xiaoling
on 2022/09/09 10:26
Change comment: There is no comment for this version
To version 35.14
edited by Xiaoling
on 2022/06/14 14:12
Change comment: There is no comment for this version

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +LSE01-LoRaWAN Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,10 +1,8 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220709085040-1.png||height="542" width="524"]]
2 +[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
3 3  
4 4  
5 5  
6 -
7 -
8 8  **Table of Contents:**
9 9  
10 10  {{toc/}}
... ... @@ -14,812 +14,771 @@
14 14  
15 15  
16 16  
17 -= 1.  Introduction =
15 += 1. Introduction =
18 18  
17 +== 1.1 ​What is LoRaWAN Soil Moisture & EC Sensor ==
19 19  
20 -== 1.1 ​ What is NDDS75 Distance Detection Sensor ==
21 -
22 22  (((
23 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.
22 +The Dragino LSE01 is a (% style="color:#4f81bd" %)**LoRaWAN Soil Moisture & EC Sensor**(%%) for IoT of Agriculture. It is designed to measure the soil moisture of saline-alkali soil and loamy soil. The soil sensor uses FDR method to calculate the soil moisture with the compensation from soil temperature and conductivity. It also has been calibrated in factory for Mineral soil type.
28 28  )))
29 29  
30 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.
26 +It detects (% style="color:#4f81bd" %)**Soil Moisture**(%%), (% style="color:#4f81bd" %)**Soil Temperature**(%%) and (% style="color:#4f81bd" %)**Soil Conductivity**(%%), and uploads the value via wireless to LoRaWAN IoT Server.
32 32  )))
33 33  
34 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.
30 +The LoRa wireless technology used in LES01 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
36 36  )))
37 37  
38 38  (((
39 -NDDS75 supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP** (%%)for different application requirement.
34 +LES01 is powered by (% style="color:#4f81bd" %)**4000mA or 8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to 10 years.
40 40  )))
41 41  
42 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)
38 +Each LES01 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
44 44  )))
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 -)))
50 50  
51 -
52 -)))
42 +[[image:1654503236291-817.png]]
53 53  
54 -[[image:1657327959271-447.png]]
55 55  
45 +[[image:1654503265560-120.png]]
56 56  
57 57  
58 -== 1.2 ​ Features ==
59 59  
49 +== 1.2 ​Features ==
60 60  
61 -* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
51 +* LoRaWAN 1.0.3 Class A
62 62  * Ultra low power consumption
63 -* Distance Detection by Ultrasonic technology
64 -* Flat object range 280mm - 7500mm
65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 -* Cable Length: 25cm
53 +* Monitor Soil Moisture
54 +* Monitor Soil Temperature
55 +* Monitor Soil Conductivity
56 +* 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
61 +* 4000mAh or 8500mAh Battery for long term use
73 73  
74 74  
75 -== 1.3  Specification ==
64 +== 1.3 Specification ==
76 76  
66 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
77 77  
78 -(% style="color:#037691" %)**Common DC Characteristics:**
68 +[[image:image-20220606162220-5.png]]
79 79  
80 -* Supply Voltage: 2.1v ~~ 3.6v
81 -* Operating Temperature: -40 ~~ 85°C
82 82  
83 -(% style="color:#037691" %)**NB-IoT Spec:**
84 84  
85 -* - B1 @H-FDD: 2100MHz
86 -* - B3 @H-FDD: 1800MHz
87 -* - B8 @H-FDD: 900MHz
88 -* - B5 @H-FDD: 850MHz
89 -* - B20 @H-FDD: 800MHz
90 -* - B28 @H-FDD: 700MHz
72 +== ​1.4 Applications ==
91 91  
92 -(% style="color:#037691" %)**Battery:**
74 +* Smart Agriculture
93 93  
94 -* Li/SOCI2 un-chargeable battery
95 -* Capacity: 8500mAh
96 -* Self Discharge: <1% / Year @ 25°C
97 -* Max continuously current: 130mA
98 -* Max boost current: 2A, 1 second
76 +(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
77 +​
99 99  
100 -(% style="color:#037691" %)**Power Consumption**
79 +== 1.5 Firmware Change log ==
101 101  
102 -* STOP Mode: 10uA @ 3.3v
103 -* Max transmit power: 350mA@3.3v
104 104  
82 +**LSE01 v1.0 :**  Release
105 105  
106 -== ​1.4  Applications ==
107 107  
108 108  
109 -* Smart Buildings & Home Automation
110 -* Logistics and Supply Chain Management
111 -* Smart Metering
112 -* Smart Agriculture
113 -* Smart Cities
114 -* Smart Factory
86 += 2. Configure LSE01 to connect to LoRaWAN network =
115 115  
116 -(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
117 -​
88 +== 2.1 How it works ==
118 118  
90 +(((
91 +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
92 +)))
119 119  
94 +(((
95 +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"]].
96 +)))
120 120  
121 121  
122 -== 1.5  Pin Definitions ==
123 123  
100 +== 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
124 124  
125 -[[image:1657328609906-564.png]]
102 +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.
126 126  
127 127  
105 +[[image:1654503992078-669.png]]
128 128  
129 -= 2.  Use NDDS75 to communicate with IoT Server =
130 130  
108 +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 -== 2.1  How it works ==
133 133  
111 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN with the OTAA keys from LSE01.
134 134  
135 -(((
136 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
137 -)))
113 +Each LSE01 is shipped with a sticker with the default device EUI as below:
138 138  
115 +[[image:image-20220606163732-6.jpeg]]
139 139  
140 -(((
141 -The diagram below shows the working flow in default firmware of NDDS75:
142 -)))
117 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
143 143  
144 -(((
145 -
146 -)))
119 +**Add APP EUI in the application**
147 147  
148 -[[image:1657328659945-416.png]]
149 149  
150 -(((
151 -
152 -)))
122 +[[image:1654504596150-405.png]]
153 153  
154 154  
155 -== 2.2 ​ Configure the NDDS75 ==
156 156  
126 +**Add APP KEY and DEV EUI**
157 157  
158 -=== 2.2.1 Test Requirement ===
128 +[[image:1654504683289-357.png]]
159 159  
160 160  
161 -(((
162 -To use NDDS75 in your city, make sure meet below requirements:
163 -)))
164 164  
165 -* Your local operator has already distributed a NB-IoT Network there.
166 -* The local NB-IoT network used the band that NDDS75 supports.
167 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
132 +(% style="color:blue" %)**Step 2**(%%): Power on LSE01
168 168  
169 -(((
170 -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.
171 -)))
172 172  
135 +Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position).
173 173  
174 -[[image:1657328756309-230.png]]
137 +[[image:image-20220606163915-7.png]]
175 175  
176 176  
140 +(% 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  
178 -=== 2.2.2 Insert SIM card ===
142 +[[image:1654504778294-788.png]]
179 179  
180 180  
145 +
146 +== 2.3 Uplink Payload ==
147 +
148 +
149 +=== 2.3.1 MOD~=0(Default Mode) ===
150 +
151 +LSE01 will uplink payload via LoRaWAN with below payload format: 
152 +
181 181  (((
182 -Insert the NB-IoT Card get from your provider.
154 +Uplink payload includes in total 11 bytes.
183 183  )))
184 184  
185 -(((
186 -User need to take out the NB-IoT module and insert the SIM card like below:
157 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
158 +|(((
159 +**Size**
160 +
161 +**(bytes)**
162 +)))|**2**|**2**|**2**|**2**|**2**|**1**
163 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
164 +Temperature
165 +
166 +(Reserve, Ignore now)
167 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
168 +MOD & Digital Interrupt
169 +
170 +(Optional)
187 187  )))
188 188  
189 189  
190 -[[image:1657328884227-504.png]]
191 191  
192 192  
176 +=== 2.3.2 MOD~=1(Original value) ===
193 193  
194 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
178 +This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
195 195  
180 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
181 +|(((
182 +**Size**
196 196  
197 -(((
198 -(((
199 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
184 +**(bytes)**
185 +)))|**2**|**2**|**2**|**2**|**2**|**1**
186 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
187 +Temperature
188 +
189 +(Reserve, Ignore now)
190 +)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
191 +MOD & Digital Interrupt
192 +
193 +(Optional)
200 200  )))
201 -)))
202 202  
203 -[[image:image-20220709092052-2.png]]
204 204  
205 205  
206 -**Connection:**
207 207  
208 - (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
199 +=== 2.3.3 Battery Info ===
209 209  
210 - (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
201 +(((
202 +Check the battery voltage for LSE01.
203 +)))
211 211  
212 - (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
205 +(((
206 +Ex1: 0x0B45 = 2885mV
207 +)))
213 213  
209 +(((
210 +Ex2: 0x0B49 = 2889mV
211 +)))
214 214  
215 -In the PC, use below serial tool settings:
216 216  
217 -* Baud:  (% style="color:green" %)**9600**
218 -* Data bits:** (% style="color:green" %)8(%%)**
219 -* Stop bits: (% style="color:green" %)**1**
220 -* Parity:  (% style="color:green" %)**None**
221 -* Flow Control: (% style="color:green" %)**None**
222 222  
215 +=== 2.3.4 Soil Moisture ===
216 +
223 223  (((
224 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
218 +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.
225 225  )))
226 226  
227 -[[image:1657329814315-101.png]]
221 +(((
222 +For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
223 +)))
228 228  
225 +(((
226 +
227 +)))
229 229  
230 230  (((
231 -(% style="color:red" %)**Note: the valid AT Commands can be found at: **(%%)**[[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]**
230 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
232 232  )))
233 233  
234 234  
235 235  
236 -=== 2.2.4 Use CoAP protocol to uplink data ===
235 +=== 2.3.5 Soil Temperature ===
237 237  
237 +(((
238 + 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
239 +)))
238 238  
239 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
241 +(((
242 +**Example**:
243 +)))
240 240  
245 +(((
246 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
247 +)))
241 241  
242 242  (((
243 -**Use below commands:**
250 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
244 244  )))
245 245  
246 -* (((
247 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
253 +
254 +
255 +=== 2.3.6 Soil Conductivity (EC) ===
256 +
257 +(((
258 +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).
248 248  )))
249 -* (((
250 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
260 +
261 +(((
262 +For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
251 251  )))
252 -* (((
253 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
254 254  
265 +(((
266 +Generally, the EC value of irrigation water is less than 800uS / cm.
267 +)))
255 255  
269 +(((
256 256  
257 257  )))
258 258  
259 259  (((
260 -For parameter description, please refer to AT command set
261 -
262 262  
263 263  )))
264 264  
265 -[[image:1657330452568-615.png]]
277 +=== 2.3.7 MOD ===
266 266  
279 +Firmware version at least v2.1 supports changing mode.
267 267  
281 +For example, bytes[10]=90
268 268  
269 -(((
270 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
283 +mod=(bytes[10]>>7)&0x01=1.
271 271  
272 -
273 -)))
274 274  
275 -[[image:1657330472797-498.png]]
286 +**Downlink Command:**
276 276  
288 +If payload = 0x0A00, workmode=0
277 277  
290 +If** **payload =** **0x0A01, workmode=1
278 278  
279 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
280 280  
281 281  
282 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
283 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
284 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
294 +=== 2.3.8 ​Decode payload in The Things Network ===
285 285  
286 -[[image:1657330501006-241.png]]
296 +While using TTN network, you can add the payload format to decode the payload.
287 287  
288 288  
289 -[[image:1657330533775-472.png]]
299 +[[image:1654505570700-128.png]]
290 290  
301 +(((
302 +The payload decoder function for TTN is here:
303 +)))
291 291  
305 +(((
306 +LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
307 +)))
292 292  
293 -=== 2.2.6 Use MQTT protocol to uplink data ===
294 294  
310 +== 2.4 Uplink Interval ==
295 295  
296 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
297 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
298 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
299 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
300 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
301 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
302 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
312 +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"]]
303 303  
304 -[[image:1657249978444-674.png]]
305 305  
306 306  
307 -[[image:1657330723006-866.png]]
316 +== 2.5 Downlink Payload ==
308 308  
318 +By default, LSE50 prints the downlink payload to console port.
309 309  
320 +[[image:image-20220606165544-8.png]]
321 +
322 +
310 310  (((
311 -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.
324 +**Examples:**
312 312  )))
313 313  
327 +(((
328 +
329 +)))
314 314  
331 +* (((
332 +**Set TDC**
333 +)))
315 315  
316 -=== 2.2.7 Use TCP protocol to uplink data ===
335 +(((
336 +If the payload=0100003C, it means set the END Node’s TDC to 0x00003C=60(S), while type code is 01.
337 +)))
317 317  
339 +(((
340 +Payload:    01 00 00 1E    TDC=30S
341 +)))
318 318  
319 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
320 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
343 +(((
344 +Payload:    01 00 00 3C    TDC=60S
345 +)))
321 321  
322 -[[image:image-20220709093918-1.png]]
347 +(((
348 +
349 +)))
323 323  
351 +* (((
352 +**Reset**
353 +)))
324 324  
325 -[[image:image-20220709093918-2.png]]
355 +(((
356 +If payload = 0x04FF, it will reset the LSE01
357 +)))
326 326  
327 327  
360 +* **CFM**
328 328  
329 -=== 2.2.8 Change Update Interval ===
362 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
330 330  
331 331  
332 -User can use below command to change the (% style="color:green" %)**uplink interval**.
333 333  
334 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
366 +== 2.6 ​Show Data in DataCake IoT Server ==
335 335  
336 336  (((
337 -(% style="color:red" %)**NOTE 1: By default, the device will send an uplink message every 1 hour.**
369 +[[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:
370 +)))
338 338  
372 +(((
339 339  
340 340  )))
341 341  
342 -(% style="color:red" %)**NOTE 2: When the firmware version is v1.3.2 and later firmware:**
376 +(((
377 +**(% style="color:blue" %)Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
378 +)))
343 343  
344 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
380 +(((
381 +**(% 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:
382 +)))
345 345  
346 346  
385 +[[image:1654505857935-743.png]]
347 347  
348 -== 2.3  Uplink Payload ==
349 349  
388 +[[image:1654505874829-548.png]]
350 350  
351 -=== 2.3.1  Before Firmware 1.3.2 ===
390 +**(% style="color:blue" %)Step 3(%%):**  Create an account or log in Datacake.
352 352  
392 +**(% style="color:blue" %)Step 4(%%):**  Search the LSE01 and add DevEUI.
353 353  
354 -In this mode, uplink payload includes in total 14 bytes
355 355  
356 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
357 -|=(% style="width: 60px;" %)(((
358 -**Size(bytes)**
359 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
360 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
395 +[[image:1654505905236-553.png]]
361 361  
362 -(((
363 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
364 -)))
365 365  
398 +After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
366 366  
367 -[[image:1657331036973-987.png]]
400 +[[image:1654505925508-181.png]]
368 368  
369 369  
370 -(((
371 -The payload is **ASCII** string, representative same HEX:
372 -)))
373 373  
374 -(((
375 -0x72403155615900640c6c19029200 where:
376 -)))
404 +== 2.7 Frequency Plans ==
377 377  
378 -* (((
379 -Device ID: 0x724031556159 = 724031556159
380 -)))
381 -* (((
382 -Version:  0x0064=100=1.0.0
383 -)))
406 +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.
384 384  
385 -* (((
386 -BAT:  0x0c6c = 3180 mV = 3.180V
387 -)))
388 -* (((
389 -Signal: 0x19 = 25
390 -)))
391 -* (((
392 -Distance: 0x0292= 658 mm
393 -)))
394 -* (((
395 -Interrupt: 0x00 = 0
396 396  
409 +=== 2.7.1 EU863-870 (EU868) ===
397 397  
411 +(% style="color:#037691" %)** Uplink:**
398 398  
413 +868.1 - SF7BW125 to SF12BW125
399 399  
400 -
401 -)))
415 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
402 402  
403 -=== **2.3.2  Since firmware v1.3.2** ===
417 +868.5 - SF7BW125 to SF12BW125
404 404  
419 +867.1 - SF7BW125 to SF12BW125
405 405  
406 -In this mode, uplink payload includes 69 bytes in total by default.
421 +867.3 - SF7BW125 to SF12BW125
407 407  
408 -Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
423 +867.5 - SF7BW125 to SF12BW125
409 409  
410 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
411 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
412 -|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
425 +867.7 - SF7BW125 to SF12BW125
413 413  
414 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
427 +867.9 - SF7BW125 to SF12BW125
415 415  
416 -[[image:image-20220908175246-1.png]]
429 +868.8 - FSK
417 417  
418 418  
419 -The payload is ASCII string, representative same HEX:
432 +(% style="color:#037691" %)** Downlink:**
420 420  
421 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
434 +Uplink channels 1-9 (RX1)
422 422  
423 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
424 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
425 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
426 -* (% style="color:blue" %)Singal: 0x1e = 30
427 -* (% style="color:red" %)Mod: 0x01 = 1
428 -* Interrupt: 0x00= 0
429 -* Distance: 0x0039= 57 = 57
430 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
431 -* Distance,Time stamp : 00396319baf0
432 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
436 +869.525 - SF9BW125 (RX2 downlink only)
433 433  
434 434  
435 -== 2.4  Payload Explanation and Sensor Interface ==
436 436  
440 +=== 2.7.2 US902-928(US915) ===
437 437  
438 -=== 2.4.1  Device ID ===
442 +Used in USA, Canada and South America. Default use CHE=2
439 439  
444 +(% style="color:#037691" %)**Uplink:**
440 440  
441 -(((
442 -By default, the Device ID equal to the last 6 bytes of IMEI.
443 -)))
446 +903.9 - SF7BW125 to SF10BW125
444 444  
445 -(((
446 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
448 +904.1 - SF7BW125 to SF10BW125
447 447  
448 -
449 -)))
450 +904.3 - SF7BW125 to SF10BW125
450 450  
451 -(((
452 -(% style="color:blue" %)**Example :**
453 -)))
452 +904.5 - SF7BW125 to SF10BW125
454 454  
455 -(((
456 -AT+DEUI=A84041F15612
457 -)))
454 +904.7 - SF7BW125 to SF10BW125
458 458  
459 -(((
460 -The Device ID is stored in a none-erase area, Upgrade the firmware or run (% style="color:blue" %)**AT+FDR**(%%) won't erase Device ID.
461 -)))
456 +904.9 - SF7BW125 to SF10BW125
462 462  
458 +905.1 - SF7BW125 to SF10BW125
463 463  
464 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
460 +905.3 - SF7BW125 to SF10BW125
465 465  
466 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
467 467  
468 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
463 +(% style="color:#037691" %)**Downlink:**
469 469  
465 +923.3 - SF7BW500 to SF12BW500
470 470  
471 -(% style="color:blue" %)**Example :**
467 +923.9 - SF7BW500 to SF12BW500
472 472  
473 -AT+DEUI=868411056754138
469 +924.5 - SF7BW500 to SF12BW500
474 474  
471 +925.1 - SF7BW500 to SF12BW500
475 475  
473 +925.7 - SF7BW500 to SF12BW500
476 476  
477 -=== 2.4.2  Version Info ===
475 +926.3 - SF7BW500 to SF12BW500
478 478  
477 +926.9 - SF7BW500 to SF12BW500
479 479  
480 -(((
481 -Specify the software version: 0x64=100, means firmware version 1.00.
482 -)))
479 +927.5 - SF7BW500 to SF12BW500
483 483  
484 -(((
485 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
486 -)))
481 +923.3 - SF12BW500(RX2 downlink only)
487 487  
488 488  
489 489  
490 -=== 2.4.3  Battery Info ===
485 +=== 2.7.3 CN470-510 (CN470) ===
491 491  
487 +Used in China, Default use CHE=1
492 492  
493 -(((
494 -Ex1: 0x0B45 = 2885mV
495 -)))
489 +(% style="color:#037691" %)**Uplink:**
496 496  
497 -(((
498 -Ex2: 0x0B49 = 2889mV
499 -)))
491 +486.3 - SF7BW125 to SF12BW125
500 500  
493 +486.5 - SF7BW125 to SF12BW125
501 501  
495 +486.7 - SF7BW125 to SF12BW125
502 502  
503 -=== 2.4.4  Signal Strength ===
497 +486.9 - SF7BW125 to SF12BW125
504 504  
499 +487.1 - SF7BW125 to SF12BW125
505 505  
506 -(((
507 -NB-IoT Network signal Strength.
508 -)))
501 +487.3 - SF7BW125 to SF12BW125
509 509  
510 -(((
511 -**Ex1: 0x1d = 29**
512 -)))
503 +487.5 - SF7BW125 to SF12BW125
513 513  
514 -(((
515 -(% style="color:blue" %)**0**(%%)  -113dBm or less
516 -)))
505 +487.7 - SF7BW125 to SF12BW125
517 517  
518 -(((
519 -(% style="color:blue" %)**1**(%%)  -111dBm
520 -)))
521 521  
522 -(((
523 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
524 -)))
508 +(% style="color:#037691" %)**Downlink:**
525 525  
526 -(((
527 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
528 -)))
510 +506.7 - SF7BW125 to SF12BW125
529 529  
530 -(((
531 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
532 -)))
512 +506.9 - SF7BW125 to SF12BW125
533 533  
514 +507.1 - SF7BW125 to SF12BW125
534 534  
516 +507.3 - SF7BW125 to SF12BW125
535 535  
536 -=== 2.4.5  Distance ===
518 +507.5 - SF7BW125 to SF12BW125
537 537  
520 +507.7 - SF7BW125 to SF12BW125
538 538  
539 -Get the distance. Flat object range 280mm - 7500mm.
522 +507.9 - SF7BW125 to SF12BW125
540 540  
541 -(((
542 -For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
543 -)))
524 +508.1 - SF7BW125 to SF12BW125
544 544  
545 -(((
546 -(((
547 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
548 -)))
549 -)))
526 +505.3 - SF12BW125 (RX2 downlink only)
550 550  
551 -(((
552 -
553 -)))
554 554  
555 -(((
556 -
557 -)))
558 558  
559 -=== 2.4.6  Digital Interrupt ===
530 +=== 2.7.4 AU915-928(AU915) ===
560 560  
532 +Default use CHE=2
561 561  
562 -(((
563 -Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NDDS75 will send a packet to the server.
564 -)))
534 +(% style="color:#037691" %)**Uplink:**
565 565  
566 -(((
567 -The command is:
568 -)))
536 +916.8 - SF7BW125 to SF12BW125
569 569  
570 -(((
571 -(% style="color:blue" %)**AT+INTMOD=3 **(%%) ~/~/(more info about INMOD please refer [[**AT Command Manual**>>url:https://www.dragino.com/downloads/downloads/NB-IoT/NBSN95/DRAGINO_NBSN95-NB_AT%20Commands_v1.1.0.pdf]])**.**
572 -)))
538 +917.0 - SF7BW125 to SF12BW125
573 573  
540 +917.2 - SF7BW125 to SF12BW125
574 574  
575 -(((
576 -The lower four bits of this data field shows if this packet is generated by interrupt or not. Click here for the hardware and software set up.
577 -)))
542 +917.4 - SF7BW125 to SF12BW125
578 578  
544 +917.6 - SF7BW125 to SF12BW125
579 579  
580 -(((
581 -Example:
582 -)))
546 +917.8 - SF7BW125 to SF12BW125
583 583  
584 -(((
585 -0x(00): Normal uplink packet.
586 -)))
548 +918.0 - SF7BW125 to SF12BW125
587 587  
588 -(((
589 -0x(01): Interrupt Uplink Packet.
590 -)))
550 +918.2 - SF7BW125 to SF12BW125
591 591  
592 592  
553 +(% style="color:#037691" %)**Downlink:**
593 593  
594 -=== 2.4.7  ​+5V Output ===
555 +923.3 - SF7BW500 to SF12BW500
595 595  
557 +923.9 - SF7BW500 to SF12BW500
596 596  
597 -(((
598 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
599 -)))
559 +924.5 - SF7BW500 to SF12BW500
600 600  
561 +925.1 - SF7BW500 to SF12BW500
601 601  
602 -(((
603 -The 5V output time can be controlled by AT Command.
563 +925.7 - SF7BW500 to SF12BW500
604 604  
605 -
606 -)))
565 +926.3 - SF7BW500 to SF12BW500
607 607  
608 -(((
609 -(% style="color:blue" %)**AT+5VT=1000**
567 +926.9 - SF7BW500 to SF12BW500
610 610  
611 -
612 -)))
569 +927.5 - SF7BW500 to SF12BW500
613 613  
614 -(((
615 -Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
616 -)))
571 +923.3 - SF12BW500(RX2 downlink only)
617 617  
618 618  
619 619  
620 -== 2.5  Downlink Payload ==
575 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
621 621  
577 +(% style="color:#037691" %)**Default Uplink channel:**
622 622  
623 -By default, NDDS75 prints the downlink payload to console port.
579 +923.2 - SF7BW125 to SF10BW125
624 624  
625 -[[image:image-20220709100028-1.png]]
581 +923.4 - SF7BW125 to SF10BW125
626 626  
627 627  
628 -(((
629 -(% style="color:blue" %)**Examples:**
630 -)))
584 +(% style="color:#037691" %)**Additional Uplink Channel**:
631 631  
632 -(((
633 -
634 -)))
586 +(OTAA mode, channel added by JoinAccept message)
635 635  
636 -* (((
637 -(% style="color:blue" %)**Set TDC**
638 -)))
588 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
639 639  
640 -(((
641 -If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
642 -)))
590 +922.2 - SF7BW125 to SF10BW125
643 643  
644 -(((
645 -Payload:    01 00 00 1E    TDC=30S
646 -)))
592 +922.4 - SF7BW125 to SF10BW125
647 647  
648 -(((
649 -Payload:    01 00 00 3C    TDC=60S
650 -)))
594 +922.6 - SF7BW125 to SF10BW125
651 651  
652 -(((
653 -
654 -)))
596 +922.8 - SF7BW125 to SF10BW125
655 655  
656 -* (((
657 -(% style="color:blue" %)**Reset**
658 -)))
598 +923.0 - SF7BW125 to SF10BW125
659 659  
660 -(((
661 -If payload = 0x04FF, it will reset the NDDS75
662 -)))
600 +922.0 - SF7BW125 to SF10BW125
663 663  
664 664  
665 -* (% style="color:blue" %)**INTMOD**
603 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
666 666  
667 -(((
668 -Downlink Payload: 06000003, Set AT+INTMOD=3
669 -)))
605 +923.6 - SF7BW125 to SF10BW125
670 670  
607 +923.8 - SF7BW125 to SF10BW125
671 671  
609 +924.0 - SF7BW125 to SF10BW125
672 672  
673 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
611 +924.2 - SF7BW125 to SF10BW125
674 674  
613 +924.4 - SF7BW125 to SF10BW125
675 675  
676 -(% style="color:blue" %)** ➢ AT Command:**
615 +924.6 - SF7BW125 to SF10BW125
677 677  
678 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
679 679  
680 -² When min=0, and max≠0, Alarm higher than max
618 +(% style="color:#037691" %)** Downlink:**
681 681  
682 -² When min≠0, and max=0, Alarm lower than min
620 +Uplink channels 1-8 (RX1)
683 683  
684 -² When min≠0 and max≠0, Alarm higher than max or lower than min
622 +923.2 - SF10BW125 (RX2)
685 685  
686 686  
687 -(% style="color:blue" %)** Example:**
688 688  
689 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
626 +=== 2.7.6 KR920-923 (KR920) ===
690 690  
628 +Default channel:
691 691  
630 +922.1 - SF7BW125 to SF12BW125
692 692  
693 -== 2.7  Set the number of data to be uploaded and the recording time ==
632 +922.3 - SF7BW125 to SF12BW125
694 694  
634 +922.5 - SF7BW125 to SF12BW125
695 695  
696 -(% style="color:blue" %)** ➢ AT Command:**
697 697  
698 -(% style="color:#037691" %)** AT+TR=900** (%%) ~/~/ The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
637 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
699 699  
700 -(% style="color:#037691" %)** AT+NOUD=8** (%%) ~/~/  The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
639 +922.1 - SF7BW125 to SF12BW125
701 701  
641 +922.3 - SF7BW125 to SF12BW125
702 702  
643 +922.5 - SF7BW125 to SF12BW125
703 703  
704 -== 2.8  Read or Clear cached data ==
645 +922.7 - SF7BW125 to SF12BW125
705 705  
647 +922.9 - SF7BW125 to SF12BW125
706 706  
707 -(% style="color:blue" %)** ➢ AT Command:**
649 +923.1 - SF7BW125 to SF12BW125
708 708  
709 -(% style="color:#037691" %)** AT+CDP ** (%%) ~/~/ Read cached data
651 +923.3 - SF7BW125 to SF12BW125
710 710  
711 711  
712 -[[image:image-20220908175333-2.png]]
654 +(% style="color:#037691" %)**Downlink:**
713 713  
656 +Uplink channels 1-7(RX1)
714 714  
715 -(% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/ Clear cached data
658 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
716 716  
717 717  
718 718  
719 -== 2.9  ​LED Indicator ==
662 +=== 2.7.7 IN865-867 (IN865) ===
720 720  
664 +(% style="color:#037691" %)** Uplink:**
721 721  
722 -The NDDS75 has an internal LED which is to show the status of different state.
666 +865.0625 - SF7BW125 to SF12BW125
723 723  
668 +865.4025 - SF7BW125 to SF12BW125
724 724  
725 -* When power on, NDDS75 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
726 -* Then the LED will be on for 1 second means device is boot normally.
727 -* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
728 -* For each uplink probe, LED will be on for 500ms.
670 +865.9850 - SF7BW125 to SF12BW125
729 729  
730 -(((
731 -
732 -)))
733 733  
673 +(% style="color:#037691" %) **Downlink:**
734 734  
675 +Uplink channels 1-3 (RX1)
735 735  
736 -== 2.10  ​Firmware Change Log ==
677 +866.550 - SF10BW125 (RX2)
737 737  
738 738  
739 -(((
740 -Download URL & Firmware Change log:  [[https:~~/~~/www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0>>https://www.dropbox.com/sh/3hb94r49iszmstx/AADvSJcXxahEUfxqKWVnZx-La?dl=0]]
741 -)))
742 742  
743 -(((
744 -
745 -)))
746 746  
747 -(((
748 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
749 -)))
682 +== 2.8 LED Indicator ==
750 750  
684 +The LSE01 has an internal LED which is to show the status of different state.
751 751  
686 +* Blink once when device power on.
687 +* Solid ON for 5 seconds once device successful Join the network.
688 +* Blink once when device transmit a packet.
752 752  
753 -== 2.11  ​Battery Analysis ==
690 +== 2.9 Installation in Soil ==
754 754  
692 +**Measurement the soil surface**
755 755  
756 -=== 2.11.1  ​Battery Type ===
757 757  
695 +[[image:1654506634463-199.png]] ​
758 758  
759 759  (((
760 -The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
698 +(((
699 +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.
761 761  )))
701 +)))
762 762  
703 +
704 +[[image:1654506665940-119.png]]
705 +
763 763  (((
764 -The battery is designed to last for several years depends on the actually use environment and update interval. 
707 +Dig a hole with diameter > 20CM.
765 765  )))
766 766  
767 767  (((
768 -The battery related documents as below:
711 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
769 769  )))
770 770  
771 -* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
772 -* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
773 -* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
774 774  
715 +== 2.10 ​Firmware Change Log ==
716 +
775 775  (((
776 -[[image:image-20220709101450-2.png]]
718 +**Firmware download link:**
777 777  )))
778 778  
721 +(((
722 +[[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/]]
723 +)))
779 779  
725 +(((
726 +
727 +)))
780 780  
781 -=== 2.11.2  Power consumption Analyze ===
729 +(((
730 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
731 +)))
782 782  
733 +(((
734 +
735 +)))
783 783  
784 784  (((
785 -Dragino battery powered product are all runs in Low Power mode. We have an update battery calculator which base on the measurement of the real device. User can use this calculator to check the battery life and calculate the battery life if want to use different transmit interval.
738 +**V1.0.**
786 786  )))
787 787  
741 +(((
742 +Release
743 +)))
788 788  
745 +
746 +== 2.11 ​Battery Analysis ==
747 +
748 +=== 2.11.1 ​Battery Type ===
749 +
789 789  (((
790 -Instruction to use as below:
751 +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.
791 791  )))
792 792  
793 793  (((
794 -(% style="color:blue" %)**Step 1:  **(%%)Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/Battery_Analyze/]]
755 +The battery is designed to last for more than 5 years for the LSN50.
795 795  )))
796 796  
797 -
798 798  (((
799 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
759 +(((
760 +The battery-related documents are as below:
800 800  )))
762 +)))
801 801  
802 802  * (((
803 -Product Model
765 +[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
804 804  )))
805 805  * (((
806 -Uplink Interval
768 +[[Lithium-Thionyl Chloride Battery  datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
807 807  )))
808 808  * (((
809 -Working Mode
771 +[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
810 810  )))
811 811  
812 -(((
813 -And the Life expectation in difference case will be shown on the right.
814 -)))
774 + [[image:image-20220610172436-1.png]]
815 815  
816 -[[image:image-20220709110451-3.png]]
817 817  
818 818  
778 +=== 2.11.2 ​Battery Note ===
819 819  
820 -=== 2.11.3  ​Battery Note ===
821 -
822 -
823 823  (((
824 824  The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to transmit LoRa, then the battery life may be decreased.
825 825  )))
... ... @@ -826,217 +826,327 @@
826 826  
827 827  
828 828  
829 -=== 2.11.4  Replace the battery ===
786 +=== 2.11.3 Replace the battery ===
830 830  
788 +(((
789 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
790 +)))
831 831  
832 832  (((
833 -The default battery pack of NDDS75 includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
793 +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.
834 834  )))
835 835  
796 +(((
797 +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)
798 +)))
836 836  
837 837  
838 -= 3. ​ Access NB-IoT Module =
839 839  
802 += 3. ​Using the AT Commands =
840 840  
841 -(((
842 -Users can directly access the AT command set of the NB-IoT module.
843 -)))
804 +== 3.1 Access AT Commands ==
844 844  
845 -(((
846 -The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]] 
847 847  
848 -
849 -)))
807 +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.
850 850  
851 -[[image:1657333200519-600.png]]
809 +[[image:1654501986557-872.png||height="391" width="800"]]
852 852  
853 853  
812 +Or if you have below board, use below connection:
854 854  
855 -= 4.  Using the AT Commands =
856 856  
815 +[[image:1654502005655-729.png||height="503" width="801"]]
857 857  
858 -== 4.1  Access AT Commands ==
859 859  
860 860  
861 -See this link for detail:  [[https:~~/~~/www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0>>https://www.dropbox.com/sh/aaq2xcl0bzfu0yd/AAAEAHRa7Io_465ds4Y7-F3aa?dl=0]]
819 +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:
862 862  
863 863  
864 -AT+<CMD>?  : Help on <CMD>
822 + [[image:1654502050864-459.png||height="564" width="806"]]
865 865  
866 -AT+<CMD>         : Run <CMD>
867 867  
868 -AT+<CMD>=<value> : Set the value
825 +Below are the available commands, a more detailed AT Command manual can be found at [[AT Command Manual>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/]]: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/]]
869 869  
870 -AT+<CMD>=?  : Get the value
871 871  
828 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
872 872  
830 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
831 +
832 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
833 +
834 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
835 +
836 +
873 873  (% style="color:#037691" %)**General Commands**(%%)      
874 874  
875 -AT  : Attention       
839 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
876 876  
877 -AT?  : Short Help     
841 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
878 878  
879 -ATZ  : MCU Reset    
843 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
880 880  
881 -AT+TDC  : Application Data Transmission Interval
845 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
882 882  
883 -AT+CFG  : Print all configurations
884 884  
885 -AT+CFGMOD           : Working mode selection
848 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
886 886  
887 -AT+INTMOD            : Set the trigger interrupt mode
850 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
888 888  
889 -AT+5VT  : Set extend the time of 5V power  
852 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
890 890  
891 -AT+PRO  : Choose agreement
854 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
892 892  
893 -AT+WEIGRE  : Get weight or set weight to 0
856 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
894 894  
895 -AT+WEIGAP  : Get or Set the GapValue of weight
858 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
896 896  
897 -AT+RXDL  : Extend the sending and receiving time
860 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
898 898  
899 -AT+CNTFAC  : Get or set counting parameters
862 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
900 900  
901 -AT+SERVADDR  : Server Address
864 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
902 902  
903 -AT+TR      : Get or Set record time"
866 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
904 904  
905 -AT+APN     : Get or set the APN
868 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
906 906  
907 -AT+FBAND   : Get or Set whether to automatically modify the frequency band
870 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
908 908  
909 -AT+DNSCFG  : Get or Set DNS Server
872 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
910 910  
911 -AT+GETSENSORVALUE   : Returns the current sensor measurement
874 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
912 912  
913 -AT+NOUD      : Get or Set the number of data to be uploaded
876 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
914 914  
915 -AT+CDP     : Read or Clear cached data
878 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
916 916  
917 -AT+LDDSALARM : Get or Set alarm of distance
880 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
918 918  
919 919  
920 -(% style="color:#037691" %)**COAP Management**      
883 +(% style="color:#037691" %)**LoRa Network Management**
921 921  
922 -AT+URI            : Resource parameters
885 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
923 923  
887 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
924 924  
925 -(% style="color:#037691" %)**UDP Management**
889 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
926 926  
927 -AT+CFM          : Upload confirmation mode (only valid for UDP)
891 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
928 928  
893 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
929 929  
930 -(% style="color:#037691" %)**MQTT Management**
895 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
931 931  
932 -AT+CLIENT               : Get or Set MQTT client
897 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
933 933  
934 -AT+UNAME  : Get or Set MQTT Username
899 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
935 935  
936 -AT+PWD                  : Get or Set MQTT password
901 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
937 937  
938 -AT+PUBTOPIC  : Get or Set MQTT publish topic
903 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
939 939  
940 -AT+SUBTOPIC  : Get or Set MQTT subscription topic
905 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
941 941  
907 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
942 942  
943 -(% style="color:#037691" %)**Information**          
909 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
944 944  
945 -AT+FDR  : Factory Data Reset
911 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
946 946  
947 -AT+PWORD  : Serial Access Password
913 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
948 948  
949 949  
916 +(% style="color:#037691" %)**Information** 
950 950  
951 -= ​5.  FAQ =
918 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
952 952  
920 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
953 953  
954 -== 5.1 ​ How to Upgrade Firmware ==
922 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
955 955  
924 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
956 956  
926 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
927 +
928 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
929 +
930 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
931 +
932 +
933 += ​4. FAQ =
934 +
935 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
936 +
957 957  (((
958 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
938 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
939 +When downloading the images, choose the required image file for download. ​
959 959  )))
960 960  
961 961  (((
962 -Please see this link for how to upgrade:  [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
943 +
963 963  )))
964 964  
965 965  (((
966 -(% style="color:red" %)**Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.**
947 +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.
967 967  )))
968 968  
950 +(((
951 +
952 +)))
969 969  
954 +(((
955 +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.
956 +)))
970 970  
971 -= 6.  Trouble Shooting =
958 +(((
959 +
960 +)))
972 972  
962 +(((
963 +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.
964 +)))
973 973  
974 -== 6.1  ​Connection problem when uploading firmware ==
966 +[[image:image-20220606154726-3.png]]
975 975  
976 976  
969 +When you use the TTN network, the US915 frequency bands use are:
970 +
971 +* 903.9 - SF7BW125 to SF10BW125
972 +* 904.1 - SF7BW125 to SF10BW125
973 +* 904.3 - SF7BW125 to SF10BW125
974 +* 904.5 - SF7BW125 to SF10BW125
975 +* 904.7 - SF7BW125 to SF10BW125
976 +* 904.9 - SF7BW125 to SF10BW125
977 +* 905.1 - SF7BW125 to SF10BW125
978 +* 905.3 - SF7BW125 to SF10BW125
979 +* 904.6 - SF8BW500
980 +
977 977  (((
978 -**Please see: **[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
982 +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:
979 979  )))
980 980  
981 -(% class="wikigeneratedid" %)
985 +(% class="box infomessage" %)
982 982  (((
987 +**AT+CHE=2**
988 +)))
989 +
990 +(% class="box infomessage" %)
991 +(((
992 +**ATZ**
993 +)))
994 +
995 +(((
996 +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.
997 +)))
998 +
999 +(((
983 983  
984 984  )))
985 985  
1003 +(((
1004 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
1005 +)))
986 986  
987 -== 6.2  AT Command input doesn't work ==
1007 +[[image:image-20220606154825-4.png]]
988 988  
989 989  
1010 +
1011 += 5. Trouble Shooting =
1012 +
1013 +== 5.1 ​Why I can’t join TTN in US915 / AU915 bands? ==
1014 +
1015 +It is due to channel mapping. Please see the [[Eight Channel Mode>>doc:Main.LoRaWAN Communication Debug.WebHome||anchor="H2.NoticeofUS9152FCN4702FAU915Frequencyband"]] section above for details.
1016 +
1017 +
1018 +== 5.2 AT Command input doesn’t work ==
1019 +
990 990  (((
991 -In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)**ENTER**(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)**ENTER**(%%) while press the send key, user need to add ENTER in their string.
1021 +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.
1022 +)))
992 992  
993 -
1024 +
1025 +== 5.3 Device rejoin in at the second uplink packet ==
1026 +
1027 +(% style="color:#4f81bd" %)**Issue describe as below:**
1028 +
1029 +[[image:1654500909990-784.png]]
1030 +
1031 +
1032 +(% style="color:#4f81bd" %)**Cause for this issue:**
1033 +
1034 +(((
1035 +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.
994 994  )))
995 995  
996 996  
997 -= 7. ​ Order Info =
1039 +(% style="color:#4f81bd" %)**Solution: **
998 998  
1041 +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:
999 999  
1000 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1043 +[[image:1654500929571-736.png||height="458" width="832"]]
1001 1001  
1002 1002  
1046 += 6. ​Order Info =
1047 +
1048 +
1049 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
1050 +
1051 +
1052 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
1053 +
1054 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
1055 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
1056 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
1057 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
1058 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
1059 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
1060 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
1061 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
1062 +
1063 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
1064 +
1065 +* (% style="color:red" %)**4**(%%): 4000mAh battery
1066 +* (% style="color:red" %)**8**(%%): 8500mAh battery
1067 +
1003 1003  (% class="wikigeneratedid" %)
1004 1004  (((
1005 1005  
1006 1006  )))
1007 1007  
1008 -= 8.  Packing Info =
1073 += 7. Packing Info =
1009 1009  
1010 1010  (((
1011 1011  
1012 1012  
1013 1013  (% style="color:#037691" %)**Package Includes**:
1079 +)))
1014 1014  
1015 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
1016 -* External antenna x 1
1081 +* (((
1082 +LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
1017 1017  )))
1018 1018  
1019 1019  (((
1020 1020  
1021 1021  
1022 -
1023 1023  (% style="color:#037691" %)**Dimension and weight**:
1089 +)))
1024 1024  
1025 -* Device Size: 13.0 x 5 x 4.5 cm
1026 -* Device Weight: 150g
1027 -* Package Size / pcs : 15 x 12x 5.5 cm
1028 -* Weight / pcs : 220g
1091 +* (((
1092 +Device Size: cm
1029 1029  )))
1094 +* (((
1095 +Device Weight: g
1096 +)))
1097 +* (((
1098 +Package Size / pcs : cm
1099 +)))
1100 +* (((
1101 +Weight / pcs : g
1030 1030  
1031 -(((
1032 1032  
1033 -
1034 -
1035 -
1036 1036  )))
1037 1037  
1038 -= 9.  Support =
1106 += 8. Support =
1039 1039  
1040 -
1041 1041  * 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.
1042 1042  * 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]]
1657245163077-232.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -81.0 KB
Content
1657246476176-652.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -492.6 KB
Content
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-20220708101224-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 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