Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 108.4
edited by Xiaoling
on 2022/10/26 09:33
Change comment: There is no comment for this version
To version 43.1
edited by Xiaoling
on 2022/07/08 10:12
Change comment: Uploaded new attachment "image-20220708101224-1.png", version {1}

Summary

Details

Page properties
Title
... ... @@ -1,1 +1,1 @@
1 -NDDS75 NB-IoT Distance Detect Sensor User Manual
1 +NSE01 - NB-IoT Soil Moisture & EC Sensor User Manual
Content
... ... @@ -1,825 +1,774 @@
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 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:1657327959271-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 Detection by Ultrasonic technology
64 -* Flat object range 280mm - 7500mm
65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 -* Cable Length: 25cm
50 +* Monitor Soil Moisture
51 +* Monitor Soil Temperature
52 +* Monitor Soil Conductivity
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  
60 +== 1.3 Specification ==
74 74  
75 -== 1.3  Specification ==
62 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
76 76  
64 +[[image:image-20220606162220-5.png]]
77 77  
78 -(% style="color:#037691" %)**Common DC Characteristics:**
79 79  
80 -* Supply Voltage: 2.1v ~~ 3.6v
81 -* Operating Temperature: -40 ~~ 85°C
82 82  
83 -(% style="color:#037691" %)**NB-IoT Spec:**
68 +== ​1.4 Applications ==
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
70 +* Smart Agriculture
91 91  
92 -(% style="color:#037691" %)**Battery:**
72 +(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
73 +​
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
75 +== 1.5 Firmware Change log ==
99 99  
100 -(% style="color:#037691" %)**Power Consumption**
101 101  
102 -* STOP Mode: 10uA @ 3.3v
103 -* Max transmit power: 350mA@3.3v
78 +**LSE01 v1.0 :**  Release
104 104  
105 105  
106 -== ​1.4  Applications ==
107 107  
82 += 2. Configure LSE01 to connect to LoRaWAN network =
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
84 +== 2.1 How it works ==
115 115  
116 -(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
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 120  
121 -== 1.5  Pin Definitions ==
122 122  
96 +== 2.2 ​Quick guide to connect to LoRaWAN server (OTAA) ==
123 123  
124 -[[image:1657328609906-564.png]]
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  
101 +[[image:1654503992078-669.png]]
127 127  
128 -= 2.  Use NDDS75 to communicate with IoT Server =
129 129  
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.
130 130  
131 -== 2.1  How it works ==
132 132  
107 +(% style="color:blue" %)**Step 1**(%%):  Create a device in TTN with the OTAA keys from LSE01.
133 133  
134 -(((
135 -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.
136 -)))
109 +Each LSE01 is shipped with a sticker with the default device EUI as below:
137 137  
111 +[[image:image-20220606163732-6.jpeg]]
138 138  
139 -(((
140 -The diagram below shows the working flow in default firmware of NDDS75:
141 -)))
113 +You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
142 142  
143 -(((
144 -
145 -)))
115 +**Add APP EUI in the application**
146 146  
147 -[[image:1657328659945-416.png]]
148 148  
149 -(((
150 -
151 -)))
118 +[[image:1654504596150-405.png]]
152 152  
153 153  
154 -== 2.2 ​ Configure the NDDS75 ==
155 155  
122 +**Add APP KEY and DEV EUI**
156 156  
157 -=== 2.2.1 Test Requirement ===
124 +[[image:1654504683289-357.png]]
158 158  
159 159  
160 -(((
161 -To use NDDS75 in your city, make sure meet below requirements:
162 -)))
163 163  
164 -* Your local operator has already distributed a NB-IoT Network there.
165 -* The local NB-IoT network used the band that NDDS75 supports.
166 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
128 +(% style="color:blue" %)**Step 2**(%%): Power on LSE01
167 167  
168 -(((
169 -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.
170 -)))
171 171  
131 +Put a Jumper on JP2 to power on the device. ( The Jumper must be in FLASH position).
172 172  
173 -[[image:1657328756309-230.png]]
133 +[[image:image-20220606163915-7.png]]
174 174  
175 175  
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.
176 176  
177 -=== 2.2.2 Insert SIM card ===
138 +[[image:1654504778294-788.png]]
178 178  
179 179  
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 +
180 180  (((
181 -Insert the NB-IoT Card get from your provider.
150 +Uplink payload includes in total 11 bytes.
182 182  )))
183 183  
184 -(((
185 -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)
186 186  )))
187 187  
169 +=== 2.3.2 MOD~=1(Original value) ===
188 188  
189 -[[image:1657328884227-504.png]]
171 +This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
190 190  
173 +(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
174 +|(((
175 +**Size**
191 191  
177 +**(bytes)**
178 +)))|**2**|**2**|**2**|**2**|**2**|**1**
179 +|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
180 +Temperature
192 192  
193 -=== 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
194 194  
186 +(Optional)
187 +)))
195 195  
189 +=== 2.3.3 Battery Info ===
190 +
196 196  (((
192 +Check the battery voltage for LSE01.
193 +)))
194 +
197 197  (((
198 -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.
196 +Ex1: 0x0B45 = 2885mV
199 199  )))
198 +
199 +(((
200 +Ex2: 0x0B49 = 2889mV
200 200  )))
201 201  
202 -[[image:image-20220709092052-2.png]]
203 203  
204 204  
205 -(% style="color:blue" %)**Connection:**
205 +=== 2.3.4 Soil Moisture ===
206 206  
207 - (% 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 +)))
208 208  
209 -**~ (% 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 +)))
210 210  
211 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
215 +(((
216 +
217 +)))
212 212  
219 +(((
220 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
221 +)))
213 213  
214 -In the PC, use below serial tool settings:
215 215  
216 -* Baud:  (% style="color:green" %)**9600**
217 -* Data bits:** (% style="color:green" %)8(%%)**
218 -* Stop bits: (% style="color:green" %)**1**
219 -* Parity:  (% style="color:green" %)**None**
220 -* Flow Control: (% style="color:green" %)**None**
221 221  
225 +=== 2.3.5 Soil Temperature ===
226 +
222 222  (((
223 -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.
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
224 224  )))
225 225  
226 -[[image:1657329814315-101.png]]
231 +(((
232 +**Example**:
233 +)))
227 227  
235 +(((
236 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
237 +)))
228 228  
229 229  (((
230 -(% 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]]**
240 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
231 231  )))
232 232  
233 233  
234 234  
235 -=== 2.2.4 Use CoAP protocol to uplink data ===
245 +=== 2.3.6 Soil Conductivity (EC) ===
236 236  
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 +)))
237 237  
238 -(% 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/]]**
239 -
240 -
241 241  (((
242 -**Use below commands:**
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.
243 243  )))
244 244  
245 -* (((
246 -(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
255 +(((
256 +Generally, the EC value of irrigation water is less than 800uS / cm.
247 247  )))
248 -* (((
249 -(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/  to set CoAP server address and port
250 -)))
251 -* (((
252 -(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/  Set COAP resource path
253 253  
254 -
259 +(((
255 255  
256 256  )))
257 257  
258 258  (((
259 -For parameter description, please refer to AT command set
260 -
261 261  
262 262  )))
263 263  
264 -[[image:1657330452568-615.png]]
267 +=== 2.3.7 MOD ===
265 265  
269 +Firmware version at least v2.1 supports changing mode.
266 266  
271 +For example, bytes[10]=90
267 267  
268 -(((
269 -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.
270 270  
271 -
272 -)))
273 273  
274 -[[image:1657330472797-498.png]]
276 +**Downlink Command:**
275 275  
278 +If payload = 0x0A00, workmode=0
276 276  
280 +If** **payload =** **0x0A01, workmode=1
277 277  
278 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
279 279  
280 280  
281 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
282 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
283 -* (% 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 ===
284 284  
285 -[[image:1657330501006-241.png]]
286 +While using TTN network, you can add the payload format to decode the payload.
286 286  
287 287  
288 -[[image:1657330533775-472.png]]
289 +[[image:1654505570700-128.png]]
289 289  
291 +(((
292 +The payload decoder function for TTN is here:
293 +)))
290 290  
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 +)))
291 291  
292 -=== 2.2.6 Use MQTT protocol to uplink data ===
293 293  
300 +== 2.4 Uplink Interval ==
294 294  
295 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
296 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
297 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
298 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
299 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
300 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
301 -* (% 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"]]
302 302  
303 -[[image:1657249978444-674.png]]
304 304  
305 305  
306 -[[image:1657330723006-866.png]]
306 +== 2.5 Downlink Payload ==
307 307  
308 +By default, LSE50 prints the downlink payload to console port.
308 308  
310 +[[image:image-20220606165544-8.png]]
311 +
312 +
309 309  (((
310 -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.
314 +(% style="color:blue" %)**Examples:**
311 311  )))
312 312  
317 +(((
318 +
319 +)))
313 313  
321 +* (((
322 +(% style="color:blue" %)**Set TDC**
323 +)))
314 314  
315 -=== 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 +)))
316 316  
329 +(((
330 +Payload:    01 00 00 1E    TDC=30S
331 +)))
317 317  
318 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
319 -* (% 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 +)))
320 320  
321 -[[image:image-20220709093918-1.png]]
337 +(((
338 +
339 +)))
322 322  
341 +* (((
342 +(% style="color:blue" %)**Reset**
343 +)))
323 323  
324 -[[image:image-20220709093918-2.png]]
345 +(((
346 +If payload = 0x04FF, it will reset the LSE01
347 +)))
325 325  
326 326  
350 +* (% style="color:blue" %)**CFM**
327 327  
328 -=== 2.2.8 Change Update Interval ===
352 +Downlink Payload: 05000001, Set AT+CFM=1 or 05000000 , set AT+CFM=0
329 329  
330 330  
331 -User can use below command to change the (% style="color:green" %)**uplink interval**.
332 332  
333 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
356 +== 2.6 ​Show Data in DataCake IoT Server ==
334 334  
335 335  (((
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 +(((
336 336  
364 +)))
337 337  
366 +(((
367 +(% style="color:blue" %)**Step 1**(%%):  Be sure that your device is programmed and properly connected to the network at this time.
368 +)))
338 338  
339 -(% 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 +)))
340 340  
341 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
342 342  
343 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
344 -)))
375 +[[image:1654505857935-743.png]]
345 345  
346 -(% 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).**
347 347  
378 +[[image:1654505874829-548.png]]
348 348  
349 349  
350 -== 2.3  Uplink Payload ==
381 +(% style="color:blue" %)**Step 3**(%%)**:**  Create an account or log in Datacake.
351 351  
383 +(% style="color:blue" %)**Step 4**(%%)**:**  Search the LSE01 and add DevEUI.
352 352  
353 -=== 2.3.1  Before Firmware v1.3.2 ===
354 354  
386 +[[image:1654505905236-553.png]]
355 355  
356 -In this mode, uplink payload includes in total 14 bytes
357 357  
358 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
359 -|=(% style="width: 60px;" %)(((
360 -**Size(bytes)**
361 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
362 -|(% 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.
363 363  
364 -(((
365 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
366 -)))
391 +[[image:1654505925508-181.png]]
367 367  
368 368  
369 -[[image:1657331036973-987.png]]
370 370  
395 +== 2.7 Frequency Plans ==
371 371  
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.
372 372  
373 -The payload is **ASCII** string, representative same HEX:
374 374  
375 -(% style="background-color:yellow" %)**0x 724031556159 0064 0c6c 19 0292 00 **
400 +=== 2.7.1 EU863-870 (EU868) ===
376 376  
377 -**where :**
402 +(% style="color:#037691" %)** Uplink:**
378 378  
379 -* (% style="color:#037691" %)**Device ID:**(%%) 0x724031556159 = 724031556159
404 +868.1 - SF7BW125 to SF12BW125
380 380  
381 -* (% style="color:#037691" %)**Version:**(%%)  0x0064=100=1.0.0
406 +868.3 - SF7BW125 to SF12BW125 and SF7BW250
382 382  
383 -* (% style="color:#037691" %)**BAT:** (%%) 0x0c6c = 3180 mV = 3.180V
408 +868.5 - SF7BW125 to SF12BW125
384 384  
385 -* (% style="color:#037691" %)**Signal:**(%%)  0x19 = 25
410 +867.1 - SF7BW125 to SF12BW125
386 386  
387 -* (% style="color:#037691" %)**Distance:**  (%%)0x0292= 658 mm
412 +867.3 - SF7BW125 to SF12BW125
388 388  
389 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00 = 0
414 +867.5 - SF7BW125 to SF12BW125
390 390  
416 +867.7 - SF7BW125 to SF12BW125
391 391  
392 -=== **2.3.2  Since firmware v1.3.2** ===
418 +867.9 - SF7BW125 to SF12BW125
393 393  
420 +868.8 - FSK
394 394  
395 -In this mode, uplink payload includes 69 bytes in total by default.
396 396  
397 -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 +(% style="color:#037691" %)** Downlink:**
398 398  
399 -(% border="1" style="background-color:#ffffcc; color:green; width:520px" %)
400 -|=(% scope="row" style="width: 50px;" %)**Size(bytes)**|(% style="width:40px" %)**8**|(% style="width:25px" %)**2**|(% style="width:25px" %)**2**|(% style="width:60px" %)**1**|(% style="width:25px" %)**1**|(% style="width:40px" %)**1**|(% style="width:40px" %)**2**|(% style="width:40px" %)**4**|(% style="width:40px" %)**2**|(% style="width:40px" %)**4**
401 -|=(% 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 +Uplink channels 1-9 (RX1)
402 402  
403 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
427 +869.525 - SF9BW125 (RX2 downlink only)
404 404  
405 -[[image:image-20220908175246-1.png]]
406 406  
407 407  
408 -The payload is ASCII string, representative same HEX:
431 +=== 2.7.2 US902-928(US915) ===
409 409  
410 -**0x (% style="color:red" %)f867787050213317 (% style="color:blue" %)0084 (% style="color:green" %)0cf4 (% style="color:#00b0f0" %)1e (% style="color:#7030a0" %)01 (% style="color:#d60093" %)00(% style="color:#a14d07" %) 0039 (% style="color:#0020b0" %)6315537b (% style="color:#663300" %)00396319baf0 00396319ba3c 00396319b988 00396319b8d4 00396319b820 00396319b76c 00396319b6b8 00396319b604 (%%)**
433 +Used in USA, Canada and South America. Default use CHE=2
411 411  
412 -**where:**
435 +(% style="color:#037691" %)**Uplink:**
413 413  
414 -* (% style="color:#037691" %)**Device ID:**(%%) f867787050213317 = f867787050213317
437 +903.9 - SF7BW125 to SF10BW125
415 415  
416 -* (% style="color:#037691" %)**Version:**(%%) 0x0084=132=1.3.2
439 +904.1 - SF7BW125 to SF10BW125
417 417  
418 -* (% style="color:#037691" %)**BAT:**(%%)  0x0cf4 = 3316 mV = 3.316V
441 +904.3 - SF7BW125 to SF10BW125
419 419  
420 -* (% style="color:#037691" %)**Singal:**(%%)  0x1e = 30
443 +904.5 - SF7BW125 to SF10BW125
421 421  
422 -* (% style="color:#037691" %)**Mod:**(%%)**  **0x01 = 1
445 +904.7 - SF7BW125 to SF10BW125
423 423  
424 -* (% style="color:#037691" %)**Interrupt:**(%%) 0x00= 0
447 +904.9 - SF7BW125 to SF10BW125
425 425  
426 -* (% style="color:#037691" %)**Distance:**(%%) 0x0039= 57 = 57
449 +905.1 - SF7BW125 to SF10BW125
427 427  
428 -* (% style="color:#037691" %)**Time stamp:**(%%) 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
451 +905.3 - SF7BW125 to SF10BW125
429 429  
430 -* (% style="color:#037691" %)**Distance,Time stamp:**(%%) 00396319baf0
431 431  
432 -* (% style="color:#037691" %)**8 sets of recorded data: Distance,Time stamp :**(%%) //**00396319ba3c**//,.......
454 +(% style="color:#037691" %)**Downlink:**
433 433  
456 +923.3 - SF7BW500 to SF12BW500
434 434  
435 -== 2.4  Payload Explanation and Sensor Interface ==
458 +923.9 - SF7BW500 to SF12BW500
436 436  
460 +924.5 - SF7BW500 to SF12BW500
437 437  
438 -=== 2.4.1  Device ID ===
462 +925.1 - SF7BW500 to SF12BW500
439 439  
464 +925.7 - SF7BW500 to SF12BW500
440 440  
441 -(((
442 -By default, the Device ID equal to the last 6 bytes of IMEI.
443 -)))
466 +926.3 - SF7BW500 to SF12BW500
444 444  
445 -(((
446 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
468 +926.9 - SF7BW500 to SF12BW500
447 447  
448 -
449 -)))
470 +927.5 - SF7BW500 to SF12BW500
450 450  
451 -(((
452 -(% style="color:blue" %)**Example :**
453 -)))
472 +923.3 - SF12BW500(RX2 downlink only)
454 454  
455 -(((
456 -AT+DEUI=A84041F15612
457 -)))
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 -)))
462 462  
476 +=== 2.7.3 CN470-510 (CN470) ===
463 463  
464 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
478 +Used in China, Default use CHE=1
465 465  
466 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
480 +(% style="color:#037691" %)**Uplink:**
467 467  
468 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
482 +486.3 - SF7BW125 to SF12BW125
469 469  
484 +486.5 - SF7BW125 to SF12BW125
470 470  
471 -(% style="color:blue" %)**Example :**
486 +486.7 - SF7BW125 to SF12BW125
472 472  
473 -AT+DEUI=868411056754138
488 +486.9 - SF7BW125 to SF12BW125
474 474  
490 +487.1 - SF7BW125 to SF12BW125
475 475  
492 +487.3 - SF7BW125 to SF12BW125
476 476  
477 -=== 2.4.2  Version Info ===
494 +487.5 - SF7BW125 to SF12BW125
478 478  
496 +487.7 - SF7BW125 to SF12BW125
479 479  
480 -(((
481 -Specify the software version: 0x64=100, means firmware version 1.00.
482 -)))
483 483  
484 -(((
485 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
486 -)))
499 +(% style="color:#037691" %)**Downlink:**
487 487  
501 +506.7 - SF7BW125 to SF12BW125
488 488  
503 +506.9 - SF7BW125 to SF12BW125
489 489  
490 -=== 2.4.3  Battery Info ===
505 +507.1 - SF7BW125 to SF12BW125
491 491  
507 +507.3 - SF7BW125 to SF12BW125
492 492  
493 -(((
494 -Ex1: 0x0B45 = 2885mV
495 -)))
509 +507.5 - SF7BW125 to SF12BW125
496 496  
497 -(((
498 -Ex2: 0x0B49 = 2889mV
499 -)))
511 +507.7 - SF7BW125 to SF12BW125
500 500  
513 +507.9 - SF7BW125 to SF12BW125
501 501  
515 +508.1 - SF7BW125 to SF12BW125
502 502  
503 -=== 2.4.4  Signal Strength ===
517 +505.3 - SF12BW125 (RX2 downlink only)
504 504  
505 505  
506 -(((
507 -NB-IoT Network signal Strength.
508 -)))
509 509  
510 -(((
511 -**Ex1: 0x1d = 29**
512 -)))
521 +=== 2.7.4 AU915-928(AU915) ===
513 513  
514 -(((
515 -(% style="color:blue" %)**0**(%%)  -113dBm or less
516 -)))
523 +Default use CHE=2
517 517  
518 -(((
519 -(% style="color:blue" %)**1**(%%)  -111dBm
520 -)))
525 +(% style="color:#037691" %)**Uplink:**
521 521  
522 -(((
523 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
524 -)))
527 +916.8 - SF7BW125 to SF12BW125
525 525  
526 -(((
527 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
528 -)))
529 +917.0 - SF7BW125 to SF12BW125
529 529  
530 -(((
531 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
532 -)))
531 +917.2 - SF7BW125 to SF12BW125
533 533  
533 +917.4 - SF7BW125 to SF12BW125
534 534  
535 +917.6 - SF7BW125 to SF12BW125
535 535  
536 -=== 2.4.5  Distance ===
537 +917.8 - SF7BW125 to SF12BW125
537 537  
539 +918.0 - SF7BW125 to SF12BW125
538 538  
539 -Get the distance. Flat object range 280mm - 7500mm.
541 +918.2 - 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 -)))
544 544  
545 -(((
546 -(((
547 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
548 -)))
549 -)))
544 +(% style="color:#037691" %)**Downlink:**
550 550  
551 -(((
552 -
553 -)))
546 +923.3 - SF7BW500 to SF12BW500
554 554  
555 -(((
556 -
557 -)))
548 +923.9 - SF7BW500 to SF12BW500
558 558  
559 -=== 2.4.6  Digital Interrupt ===
550 +924.5 - SF7BW500 to SF12BW500
560 560  
552 +925.1 - SF7BW500 to SF12BW500
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 -)))
554 +925.7 - SF7BW500 to SF12BW500
565 565  
566 -(((
567 -The command is:
568 -)))
556 +926.3 - SF7BW500 to SF12BW500
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 -)))
558 +926.9 - SF7BW500 to SF12BW500
573 573  
560 +927.5 - SF7BW500 to SF12BW500
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 -)))
562 +923.3 - SF12BW500(RX2 downlink only)
578 578  
579 579  
580 -(((
581 -Example:
582 -)))
583 583  
584 -(((
585 -0x(00): Normal uplink packet.
586 -)))
566 +=== 2.7.5 AS920-923 & AS923-925 (AS923) ===
587 587  
588 -(((
589 -0x(01): Interrupt Uplink Packet.
590 -)))
568 +(% style="color:#037691" %)**Default Uplink channel:**
591 591  
570 +923.2 - SF7BW125 to SF10BW125
592 592  
572 +923.4 - SF7BW125 to SF10BW125
593 593  
594 -=== 2.4.7  ​+5V Output ===
595 595  
575 +(% style="color:#037691" %)**Additional Uplink Channel**:
596 596  
597 -(((
598 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
599 -)))
577 +(OTAA mode, channel added by JoinAccept message)
600 600  
579 +(% style="color:#037691" %)**AS920~~AS923 for Japan, Malaysia, Singapore**:
601 601  
602 -(((
603 -The 5V output time can be controlled by AT Command.
581 +922.2 - SF7BW125 to SF10BW125
604 604  
605 -
606 -)))
583 +922.4 - SF7BW125 to SF10BW125
607 607  
608 -(((
609 -(% style="color:blue" %)**AT+5VT=1000**
585 +922.6 - SF7BW125 to SF10BW125
610 610  
611 -
612 -)))
587 +922.8 - SF7BW125 to SF10BW125
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 -)))
589 +923.0 - SF7BW125 to SF10BW125
617 617  
591 +922.0 - SF7BW125 to SF10BW125
618 618  
619 619  
620 -== 2.5  Downlink Payload ==
594 +(% style="color:#037691" %)**AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam**:
621 621  
596 +923.6 - SF7BW125 to SF10BW125
622 622  
623 -By default, NDDS75 prints the downlink payload to console port.
598 +923.8 - SF7BW125 to SF10BW125
624 624  
625 -[[image:image-20220709100028-1.png]]
600 +924.0 - SF7BW125 to SF10BW125
626 626  
602 +924.2 - SF7BW125 to SF10BW125
627 627  
628 -(((
629 -(% style="color:blue" %)**Examples:**
630 -)))
604 +924.4 - SF7BW125 to SF10BW125
631 631  
632 -(((
633 -
634 -)))
606 +924.6 - SF7BW125 to SF10BW125
635 635  
636 -* (((
637 -(% style="color:blue" %)**Set TDC**
638 -)))
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 -)))
609 +(% style="color:#037691" %)** Downlink:**
643 643  
644 -(((
645 -Payload:    01 00 00 1E    TDC=30S
646 -)))
611 +Uplink channels 1-8 (RX1)
647 647  
648 -(((
649 -Payload:    01 00 00 3C    TDC=60S
650 -)))
613 +923.2 - SF10BW125 (RX2)
651 651  
652 -(((
653 -
654 -)))
655 655  
656 -* (((
657 -(% style="color:blue" %)**Reset**
658 -)))
659 659  
660 -(((
661 -If payload = 0x04FF, it will reset the NDDS75
662 -)))
617 +=== 2.7.6 KR920-923 (KR920) ===
663 663  
619 +Default channel:
664 664  
665 -* (% style="color:blue" %)**INTMOD**
621 +922.1 - SF7BW125 to SF12BW125
666 666  
667 -(((
668 -Downlink Payload: 06000003, Set AT+INTMOD=3
669 -)))
623 +922.3 - SF7BW125 to SF12BW125
670 670  
625 +922.5 - SF7BW125 to SF12BW125
671 671  
672 672  
673 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
628 +(% style="color:#037691" %)**Uplink: (OTAA mode, channel added by JoinAccept message)**
674 674  
630 +922.1 - SF7BW125 to SF12BW125
675 675  
676 -(% style="color:blue" %)** ➢ AT Command:**
632 +922.3 - SF7BW125 to SF12BW125
677 677  
678 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
634 +922.5 - SF7BW125 to SF12BW125
679 679  
680 -² When min=0, and max≠0, Alarm higher than max
636 +922.7 - SF7BW125 to SF12BW125
681 681  
682 -² When min≠0, and max=0, Alarm lower than min
638 +922.9 - SF7BW125 to SF12BW125
683 683  
684 -² When min≠0 and max≠0, Alarm higher than max or lower than min
640 +923.1 - SF7BW125 to SF12BW125
685 685  
642 +923.3 - SF7BW125 to SF12BW125
686 686  
687 -(% style="color:blue" %)** Example:**
688 688  
689 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
645 +(% style="color:#037691" %)**Downlink:**
690 690  
647 +Uplink channels 1-7(RX1)
691 691  
649 +921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
692 692  
693 -== 2.7  Set the number of data to be uploaded and the recording time ==
694 694  
695 695  
696 -(% style="color:blue" %)** ➢ AT Command:**
653 +=== 2.7.7 IN865-867 (IN865) ===
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)
699 -* (% 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.
655 +(% style="color:#037691" %)** Uplink:**
700 700  
701 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
657 +865.0625 - SF7BW125 to SF12BW125
702 702  
703 -[[image:image-20221009001114-1.png||height="687" width="955"]]
659 +865.4025 - SF7BW125 to SF12BW125
704 704  
661 +865.9850 - SF7BW125 to SF12BW125
705 705  
706 706  
707 -== 2.8  Read or Clear cached data ==
664 +(% style="color:#037691" %) **Downlink:**
708 708  
666 +Uplink channels 1-3 (RX1)
709 709  
710 -(% style="color:blue" %)** ➢ AT Command:**
668 +866.550 - SF10BW125 (RX2)
711 711  
712 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
713 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
714 714  
715 -[[image:image-20220908175333-2.png]]
716 716  
717 717  
673 +== 2.8 LED Indicator ==
718 718  
719 -== 2.9  ​LED Indicator ==
675 +The LSE01 has an internal LED which is to show the status of different state.
720 720  
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.
721 721  
722 -The NDDS75 has an internal LED which is to show the status of different state.
681 +== 2.9 Installation in Soil ==
723 723  
683 +**Measurement the soil surface**
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.
729 729  
686 +[[image:1654506634463-199.png]] ​
687 +
730 730  (((
731 -
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.
732 732  )))
692 +)))
733 733  
734 734  
735 735  
736 -== 2.10  ​Firmware Change Log ==
696 +[[image:1654506665940-119.png]]
737 737  
698 +(((
699 +Dig a hole with diameter > 20CM.
700 +)))
738 738  
739 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]]
703 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
741 741  )))
742 742  
706 +
707 +== 2.10 ​Firmware Change Log ==
708 +
743 743  (((
744 -
710 +**Firmware download link:**
745 745  )))
746 746  
747 747  (((
748 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
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/]]
749 749  )))
750 750  
717 +(((
718 +
719 +)))
751 751  
752 -
753 -== 2.11  ​Battery Analysis ==
754 -
755 -
756 -=== 2.11.1  ​Battery Type ===
757 -
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.
722 +**Firmware Upgrade Method: **[[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
761 761  )))
762 762  
763 763  (((
764 -The battery is designed to last for several years depends on the actually use environment and update interval. 
726 +
765 765  )))
766 766  
767 767  (((
768 -The battery related documents as below:
730 +**V1.0.**
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 -
775 775  (((
776 -[[image:image-20220709101450-2.png]]
734 +Release
777 777  )))
778 778  
779 779  
738 +== 2.11 ​Battery Analysis ==
780 780  
781 -=== 2.11.2  Power consumption Analyze ===
740 +=== 2.11.1 ​Battery Type ===
782 782  
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.
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.
786 786  )))
787 787  
788 -
789 789  (((
790 -Instruction to use as below:
747 +The battery is designed to last for more than 5 years for the LSN50.
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/]]
795 -)))
796 -
797 -
798 798  (((
799 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
752 +The battery-related documents are as below:
800 800  )))
754 +)))
801 801  
802 802  * (((
803 -Product Model
757 +[[Battery Dimension>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
804 804  )))
805 805  * (((
806 -Uplink Interval
760 +[[Lithium-Thionyl Chloride Battery  datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/]],
807 807  )))
808 808  * (((
809 -Working Mode
763 +[[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/]]
810 810  )))
811 811  
812 -(((
813 -And the Life expectation in difference case will be shown on the right.
814 -)))
766 + [[image:image-20220610172436-1.png]]
815 815  
816 -[[image:image-20220709110451-3.png]]
817 817  
818 818  
770 +=== 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,326 @@
826 826  
827 827  
828 828  
829 -=== 2.11.4  Replace the battery ===
778 +=== 2.11.3 Replace the battery ===
830 830  
780 +(((
781 +If Battery is lower than 2.7v, user should replace the battery of LSE01.
782 +)))
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).
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.
834 834  )))
835 835  
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 +)))
836 836  
837 837  
838 -= 3. ​ Access NB-IoT Module =
839 839  
794 += 3. ​Using the AT Commands =
840 840  
841 -(((
842 -Users can directly access the AT command set of the NB-IoT module.
843 -)))
796 +== 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 -)))
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.
850 850  
851 -[[image:1657333200519-600.png]]
801 +[[image:1654501986557-872.png||height="391" width="800"]]
852 852  
853 853  
804 +Or if you have below board, use below connection:
854 854  
855 -= 4.  Using the AT Commands =
856 856  
807 +[[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]]
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:
862 862  
863 863  
864 -AT+<CMD>?  :  Help on <CMD>
814 + [[image:1654502050864-459.png||height="564" width="806"]]
865 865  
866 -AT+<CMD>         :  Run <CMD>
867 867  
868 -AT+<CMD>=<value> :  Set the value
817 +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]]
869 869  
870 -AT+<CMD>=?  :  Get the value
871 871  
820 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
872 872  
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 +
873 873  (% style="color:#037691" %)**General Commands**(%%)      
874 874  
875 -AT  :  Attention       
831 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
876 876  
877 -AT?  :  Short Help     
833 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
878 878  
879 -ATZ  :  MCU Reset    
835 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
880 880  
881 -AT+TDC  :  Application Data Transmission Interval
837 +(% 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
840 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
886 886  
887 -AT+INTMOD            :  Set the trigger interrupt mode
842 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
888 888  
889 -AT+5VT  :  Set extend the time of 5V power  
844 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
890 890  
891 -AT+PRO  :  Choose agreement
846 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
892 892  
893 -AT+WEIGRE  :  Get weight or set weight to 0
848 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
894 894  
895 -AT+WEIGAP  :  Get or Set the GapValue of weight
850 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
896 896  
897 -AT+RXDL  :  Extend the sending and receiving time
852 +(% 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
854 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
900 900  
901 -AT+SERVADDR  :  Server Address
856 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
902 902  
903 -AT+TR  :  Get or Set record time"
858 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
904 904  
905 -AT+APN     :  Get or set the APN
860 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
906 906  
907 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
862 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
908 908  
909 -AT+DNSCFG  : Get or Set DNS Server
864 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
910 910  
911 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
866 +(% 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
868 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
914 914  
915 -AT+CDP     :  Read or Clear cached data
870 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
916 916  
917 -AT+LDDSALARM :  Get or Set alarm of distance
872 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
918 918  
919 919  
920 -(% style="color:#037691" %)**COAP Management**      
875 +(% style="color:#037691" %)**LoRa Network Management**
921 921  
922 -AT+URI            :  Resource parameters
877 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
923 923  
879 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
924 924  
925 -(% style="color:#037691" %)**UDP Management**
881 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
926 926  
927 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
883 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
928 928  
885 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
929 929  
930 -(% style="color:#037691" %)**MQTT Management**
887 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
931 931  
932 -AT+CLIENT  :  Get or Set MQTT client
889 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
933 933  
934 -AT+UNAME  :  Get or Set MQTT Username
891 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
935 935  
936 -AT+PWD  :  Get or Set MQTT password
893 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
937 937  
938 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
895 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
939 939  
940 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
897 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
941 941  
899 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
942 942  
943 -(% style="color:#037691" %)**Information**          
901 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
944 944  
945 -AT+FDR  :  Factory Data Reset
903 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
946 946  
947 -AT+PWORD  :  Serial Access Password
905 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
948 948  
949 949  
908 +(% style="color:#037691" %)**Information** 
950 950  
951 -= ​5.  FAQ =
910 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
952 952  
912 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
953 953  
954 -== 5.1 ​ How to Upgrade Firmware ==
914 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
955 955  
916 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
956 956  
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 +
957 957  (((
958 -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. ​
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]]
935 +
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.**
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.
967 967  )))
968 968  
942 +(((
943 +
944 +)))
969 969  
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 +)))
970 970  
971 -= 6.  Trouble Shooting =
950 +(((
951 +
952 +)))
972 972  
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 +)))
973 973  
974 -== 6.1  ​Connection problem when uploading firmware ==
958 +[[image:image-20220606154726-3.png]]
975 975  
976 976  
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 +
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]]
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**
979 979  )))
980 980  
981 -(% class="wikigeneratedid" %)
982 982  (((
983 983  
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.
984 984  )))
985 985  
986 +(((
987 +
988 +)))
986 986  
987 -== 6.2  AT Command input doesn't work ==
990 +(((
991 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
992 +)))
988 988  
994 +[[image:image-20220606154825-4.png]]
989 989  
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 +
990 990  (((
991 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.
1013 +)))
992 992  
993 -
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.
994 994  )))
995 995  
996 996  
997 -= 7. ​ Order Info =
1030 +(% style="color:#4f81bd" %)**Solution: **
998 998  
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:
999 999  
1000 -Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
1034 +[[image:1654500929571-736.png||height="458" width="832"]]
1001 1001  
1002 1002  
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 +
1003 1003  (% class="wikigeneratedid" %)
1004 1004  (((
1005 1005  
1006 1006  )))
1007 1007  
1008 -= 8.  Packing Info =
1064 += 7. Packing Info =
1009 1009  
1010 1010  (((
1011 1011  
1012 1012  
1013 1013  (% style="color:#037691" %)**Package Includes**:
1070 +)))
1014 1014  
1015 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
1016 -* External antenna x 1
1072 +* (((
1073 +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**:
1080 +)))
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
1082 +* (((
1083 +Device Size: cm
1029 1029  )))
1085 +* (((
1086 +Device Weight: g
1087 +)))
1088 +* (((
1089 +Package Size / pcs : cm
1090 +)))
1091 +* (((
1092 +Weight / pcs : g
1030 1030  
1031 -(((
1032 1032  
1033 -
1034 -
1035 -
1036 1036  )))
1037 1037  
1038 -= 9.  Support =
1097 += 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]]
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-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
image-20221009001114-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Edwin
Size
... ... @@ -1,1 +1,0 @@
1 -282.9 KB
Content