Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 52.2
edited by Xiaoling
on 2022/07/08 11:12
Change comment: There is no comment for this version
To version 104.1
edited by Edwin Chen
on 2022/09/08 23:13
Change comment: There is no comment for this version

Summary

Details

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