Skip to Content
Last modified by Bei Jinggeng on 2024/05/31 09:53
From version 106.1
edited by Edwin Chen
on 2022/10/09 00:06
Change comment: There is no comment for this version
To version 62.1
edited by Xiaoling
on 2022/07/08 14:13
Change comment: Uploaded new attachment "image-20220708141352-7.jpeg", 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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,73 +1,61 @@
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 (% style="color:blue" %)**NB-IOT soil moisture & EC sensor**(%%) for agricultural IoT. Used to measure the soil moisture of saline-alkali soil and loam. The soil sensor uses the FDR method to calculate soil moisture and compensates it with soil temperature and electrical conductivity. It has also been calibrated for mineral soil types at the factory.
45 45  
46 -(((
47 -To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
48 -)))
49 -)))
30 +It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
50 50  
32 +The wireless technology used in NSE01 allows the device to send data at a low data rate and reach ultra-long distances, providing ultra-long-distance spread spectrum Communication.
33 +
34 +NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
35 +
51 51  
52 52  )))
53 53  
54 -[[image: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  
46 +== 1.2 ​Features ==
47 +
48 +
61 61  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
62 -* Ultra low power consumption
63 -* Distance Detection by Ultrasonic technology
64 -* Flat object range 280mm - 7500mm
65 -* Accuracy: ±(1cm+S*0.3%) (S: Distance)
66 -* Cable Length: 25cm
50 +* Monitor Soil Moisture
51 +* Monitor Soil Temperature
52 +* Monitor Soil Conductivity
67 67  * AT Commands to change parameters
68 68  * Uplink on periodically
69 69  * Downlink to change configure
70 70  * IP66 Waterproof Enclosure
57 +* Ultra-Low Power consumption
58 +* AT Commands to change parameters
71 71  * Micro SIM card slot for NB-IoT SIM
72 72  * 8500mAh Battery for long term use
73 73  
... ... @@ -88,128 +88,100 @@
88 88  * - B20 @H-FDD: 800MHz
89 89  * - B28 @H-FDD: 700MHz
90 90  
91 -(% style="color:#037691" %)**Battery:**
79 +(% style="color:#037691" %)**Probe Specification:**
92 92  
93 -* Li/SOCI2 un-chargeable battery
94 -* Capacity: 8500mAh
95 -* Self Discharge: <1% / Year @ 25°C
96 -* Max continuously current: 130mA
97 -* Max boost current: 2A, 1 second
81 +Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
98 98  
99 -(% style="color:#037691" %)**Power Consumption**
83 +[[image:image-20220708101224-1.png]]
100 100  
101 -* STOP Mode: 10uA @ 3.3v
102 -* Max transmit power: 350mA@3.3v
103 103  
86 +
104 104  == ​1.4  Applications ==
105 105  
106 -
107 -* Smart Buildings & Home Automation
108 -* Logistics and Supply Chain Management
109 -* Smart Metering
110 110  * Smart Agriculture
111 -* Smart Cities
112 -* Smart Factory
113 113  
114 114  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
115 115  ​
116 116  
117 -
118 -
119 -
120 120  == 1.5  Pin Definitions ==
121 121  
122 122  
123 -[[image:1657328609906-564.png]]
97 +[[image:1657246476176-652.png]]
124 124  
125 125  
126 126  
127 -= 2.  Use NDDS75 to communicate with IoT Server =
101 += 2.  Use NSE01 to communicate with IoT Server =
128 128  
129 -
130 130  == 2.1  How it works ==
131 131  
132 132  
133 133  (((
134 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
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.
135 135  )))
136 136  
137 137  
138 138  (((
139 -The diagram below shows the working flow in default firmware of NDDS75:
112 +The diagram below shows the working flow in default firmware of NSE01:
140 140  )))
141 141  
142 -(((
143 -
144 -)))
115 +[[image:image-20220708101605-2.png]]
145 145  
146 -[[image:1657328659945-416.png]]
147 -
148 148  (((
149 149  
150 150  )))
151 151  
152 152  
153 -== 2.2 ​ Configure the NDDS75 ==
154 154  
123 +== 2.2 ​ Configure the NSE01 ==
155 155  
125 +
156 156  === 2.2.1 Test Requirement ===
157 157  
158 158  
159 -(((
160 -To use NDDS75 in your city, make sure meet below requirements:
161 -)))
129 +To use NSE01 in your city, make sure meet below requirements:
162 162  
163 163  * Your local operator has already distributed a NB-IoT Network there.
164 -* The local NB-IoT network used the band that NDDS75 supports.
132 +* The local NB-IoT network used the band that NSE01 supports.
165 165  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
166 166  
167 167  (((
168 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server.
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
169 169  )))
170 170  
171 171  
172 -[[image:1657328756309-230.png]]
140 +[[image:1657249419225-449.png]]
173 173  
174 174  
175 175  
176 176  === 2.2.2 Insert SIM card ===
177 177  
178 -
179 -(((
180 180  Insert the NB-IoT Card get from your provider.
181 -)))
182 182  
183 -(((
184 184  User need to take out the NB-IoT module and insert the SIM card like below:
185 -)))
186 186  
187 187  
188 -[[image:1657328884227-504.png]]
151 +[[image:1657249468462-536.png]]
189 189  
190 190  
191 191  
192 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
155 +=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
193 193  
194 -
195 195  (((
196 196  (((
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.
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.
198 198  )))
199 199  )))
200 200  
201 -[[image:image-20220709092052-2.png]]
202 202  
164 +**Connection:**
203 203  
204 -(% style="color:blue" %)**Connection:**
166 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
205 205  
206 - (% style="background-color:yellow" %)**USB TTL GND <~-~-~-~-> GND**
168 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
207 207  
208 -**~ (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD(%%)**
170 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
209 209  
210 -**~ (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD(%%)**
211 211  
212 -
213 213  In the PC, use below serial tool settings:
214 214  
215 215  * Baud:  (% style="color:green" %)**9600**
... ... @@ -219,90 +219,70 @@
219 219  * Flow Control: (% style="color:green" %)**None**
220 220  
221 221  (((
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.
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.
223 223  )))
224 224  
225 -[[image:1657329814315-101.png]]
185 +[[image:image-20220708110657-3.png]]
226 226  
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/]]
227 227  
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 -)))
231 231  
232 232  
233 -
234 234  === 2.2.4 Use CoAP protocol to uplink data ===
235 235  
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/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
236 236  
237 -(% style="color:red" %)**Note: if you don't have CoAP server, you can refer this link to set up one: **(%%)**[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]**
238 238  
239 -
240 -(((
241 241  **Use below commands:**
242 -)))
243 243  
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
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
252 252  
253 -
254 -
255 -)))
256 -
257 -(((
258 258  For parameter description, please refer to AT command set
259 259  
260 -
261 -)))
204 +[[image:1657249793983-486.png]]
262 262  
263 -[[image:1657330452568-615.png]]
264 264  
207 +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.
265 265  
209 +[[image:1657249831934-534.png]]
266 266  
267 -(((
268 -After configure the server address and (% style="color:green" %)**reset the device**(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
269 269  
270 -
271 -)))
272 272  
273 -[[image:1657330472797-498.png]]
274 -
275 -
276 -
277 277  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
278 278  
215 +This feature is supported since firmware version v1.0.1
279 279  
280 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/  Set to use UDP protocol to uplink
281 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/  to set UDP server address and port
282 -* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/  If the server does not respond, this command is unnecessary
283 283  
284 -[[image:1657330501006-241.png]]
218 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
219 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
220 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
285 285  
222 +[[image:1657249864775-321.png]]
286 286  
287 -[[image:1657330533775-472.png]]
288 288  
225 +[[image:1657249930215-289.png]]
289 289  
290 290  
228 +
291 291  === 2.2.6 Use MQTT protocol to uplink data ===
292 292  
231 +This feature is supported since firmware version v110
293 293  
294 -* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/  Set to use MQTT protocol to uplink
295 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/  Set MQTT server address and port
296 -* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/  Set up the CLIENT of MQTT
297 -* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/  Set the username of MQTT
298 -* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/  Set the password of MQTT
299 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/  Set the sending topic of MQTT
300 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/  Set the subscription topic of MQTT
301 301  
234 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
235 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
236 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
237 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
238 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
239 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
240 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
241 +
302 302  [[image:1657249978444-674.png]]
303 303  
304 304  
305 -[[image:1657330723006-866.png]]
245 +[[image:1657249990869-686.png]]
306 306  
307 307  
308 308  (((
... ... @@ -313,240 +313,177 @@
313 313  
314 314  === 2.2.7 Use TCP protocol to uplink data ===
315 315  
256 +This feature is supported since firmware version v110
316 316  
317 -* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/  Set to use TCP protocol to uplink
318 -* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/  to set TCP server address and port
319 319  
320 -[[image:image-20220709093918-1.png]]
259 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
260 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
321 321  
262 +[[image:1657250217799-140.png]]
322 322  
323 -[[image:image-20220709093918-2.png]]
324 324  
265 +[[image:1657250255956-604.png]]
325 325  
326 326  
268 +
327 327  === 2.2.8 Change Update Interval ===
328 328  
329 -
330 330  User can use below command to change the (% style="color:green" %)**uplink interval**.
331 331  
332 -* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/  Set Update Interval to 600s
273 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
333 333  
334 334  (((
335 -
336 -
337 -
338 338  (% style="color:red" %)**NOTE:**
277 +)))
339 339  
340 -(% style="color:red" %)**1. By default, the device will send an uplink message every 1 hour.**
341 -
342 -(% style="color:red" %)**2. When the firmware version is v1.3.2 and later firmware:**
279 +(((
280 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
343 343  )))
344 344  
345 -(% style="color:red" %)**By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).**
346 346  
347 347  
348 -
349 349  == 2.3  Uplink Payload ==
350 350  
287 +In this mode, uplink payload includes in total 18 bytes
351 351  
352 -=== 2.3.1  Before Firmware v1.3.2 ===
353 -
354 -
355 -In this mode, uplink payload includes in total 14 bytes
356 -
357 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
358 -|=(% style="width: 60px;" %)(((
289 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 +|=(% style="width: 50px;" %)(((
359 359  **Size(bytes)**
360 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
361 -|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
292 +)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 80px;" %)**2**|=(% style="width: 40px;" %)**1**
293 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H"]]|(% style="width:41px" %)[[Ver>>||anchor="H"]]|(% style="width:46px" %)[[BAT>>||anchor="H"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H"]]|(% style="width:108px" %)[[Soil Moisture>>||anchor="H"]]|(% style="width:133px" %)[[Soil Temperature>>||anchor="H"]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>||anchor="H"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H"]]
362 362  
363 -(((
364 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
365 -)))
295 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
366 366  
367 367  
368 -[[image:1657331036973-987.png]]
298 +[[image:image-20220708111918-4.png]]
369 369  
370 370  
371 -(((
372 -The payload is **ASCII** string, representative same HEX:
373 -)))
301 +The payload is ASCII string, representative same HEX:
374 374  
375 -(((
376 -0x72403155615900640c6c19029200 where:
377 -)))
303 +0x72403155615900640c7817075e0a8c02f900 where:
378 378  
379 -* (((
380 -Device ID: 0x724031556159 = 724031556159
381 -)))
382 -* (((
383 -Version:  0x0064=100=1.0.0
384 -)))
305 +* Device ID: 0x 724031556159 = 724031556159
306 +* Version: 0x0064=100=1.0.0
385 385  
386 -* (((
387 -BAT:  0x0c6c = 3180 mV = 3.180V
388 -)))
389 -* (((
390 -Signal: 0x19 = 25
391 -)))
392 -* (((
393 -Distance: 0x0292= 658 mm
394 -)))
395 -* (((
396 -Interrupt: 0x00 = 0
308 +* BAT: 0x0c78 = 3192 mV = 3.192V
309 +* Singal: 0x17 = 23
310 +* Soil Moisture: 0x075e= 1886 = 18.86  %
311 +* Soil Temperature:0x0a8c =2700=27 °C
312 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
313 +* Interrupt: 0x00 = 0
397 397  
315 +== 2.4  Payload Explanation and Sensor Interface ==
398 398  
399 399  
318 +=== 2.4.1  Device ID ===
400 400  
401 -
402 -)))
320 +By default, the Device ID equal to the last 6 bytes of IMEI.
403 403  
404 -=== **2.3.2  Since firmware v1.3.2** ===
322 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
405 405  
324 +**Example:**
406 406  
407 -In this mode, uplink payload includes 69 bytes in total by default.
326 +AT+DEUI=A84041F15612
408 408  
409 -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.
328 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
410 410  
411 -(% border="2" style="background-color:#ffffcc; color:green; width:896px" %)
412 -|(% style="width:95px" %)**Size(bytes)**|(% style="width:84px" %)**8**|(% style="width:44px" %)2|(% style="width:48px" %)2|(% style="width:123px" %)1|(% style="width:55px" %)1|(% style="width:80px" %)1|(% style="width:77px" %)2|(% style="width:94px" %)4|(% style="width:77px" %)2|(% style="width:116px" %)4
413 -|(% style="width:95px" %)**Value**|(% style="width:84px" %)Device ID|(% style="width:44px" %)Ver|(% style="width:48px" %)BAT|(% style="width:123px" %)Signal Strength|(% style="width:55px" %)MOD|(% style="width:80px" %)Interrupt|(% style="width:77px" %)Distance|(% style="width:94px" %)Timestamp|(% style="width:77px" %)Distance|(% style="width:116px" %)Timestamp.......
414 414  
415 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS75 uplink data.
416 416  
417 -[[image:image-20220908175246-1.png]]
332 +=== 2.4.2  Version Info ===
418 418  
334 +Specify the software version: 0x64=100, means firmware version 1.00.
419 419  
420 -The payload is ASCII string, representative same HEX:
336 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
421 421  
422 -0x(% style="color:red" %)f867787050213317(% style="color:blue" %)0084(% style="color:green" %)0cf4(% style="color:red" %)1e(% style="color:blue" %)01(% style="color:green" %)00(% style="color:red" %)**//00396319bb32//**00396319baf0//**00396319ba3c**//00396319b988//**00396319b8d4**//00396319b820//**00396319b76c**//00396319b6b8//**00396319b604**//(%%) where:
423 423  
424 -* (% style="color:green" %)Device ID: f867787050213317 = f867787050213317
425 -* (% style="color:red" %)Version: 0x0084=132=1.3.2
426 -* (% style="color:green" %)BAT: 0x0cf4 = 3316 mV = 3.316V
427 -* (% style="color:blue" %)Singal: 0x1e = 30
428 -* (% style="color:red" %)Mod: 0x01 = 1
429 -* Interrupt: 0x00= 0
430 -* Distance: 0x0039= 57 = 57
431 -* Time stamp : 0x6315537b =1662342011  ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
432 -* Distance,Time stamp : 00396319baf0
433 -* (% style="color:red" %) 8 sets of recorded data: Distance,Time stamp : //**00396319ba3c**//,.......
434 434  
435 -== 2.4  Payload Explanation and Sensor Interface ==
340 +=== 2.4.3  Battery Info ===
436 436  
437 -
438 -=== 2.4.1  Device ID ===
439 -
440 -
441 441  (((
442 -By default, the Device ID equal to the last 6 bytes of IMEI.
343 +Check the battery voltage for LSE01.
443 443  )))
444 444  
445 445  (((
446 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
447 -
448 -
347 +Ex1: 0x0B45 = 2885mV
449 449  )))
450 450  
451 451  (((
452 -(% style="color:blue" %)**Example :**
351 +Ex2: 0x0B49 = 2889mV
453 453  )))
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  
356 +=== 2.4.4  Signal Strength ===
463 463  
464 -(% style="color:red" %)**NOTE: When the firmware version is v1.3.2 and later firmware:**
358 +NB-IoT Network signal Strength.
465 465  
466 -(% style="color:red" %)**By default, the Device ID equal to the last 15 bits of IMEI.**
360 +**Ex1: 0x1d = 29**
467 467  
468 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
362 +(% style="color:blue" %)**0**(%%)  -113dBm or less
469 469  
364 +(% style="color:blue" %)**1**(%%)  -111dBm
470 470  
471 -(% style="color:blue" %)**Example :**
366 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
472 472  
473 -AT+DEUI=868411056754138
368 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
474 474  
370 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
475 475  
476 476  
477 -=== 2.4.2  Version Info ===
478 478  
374 +=== 2.4.5  Soil Moisture ===
479 479  
480 480  (((
481 -Specify the software version: 0x64=100, means firmware version 1.00.
377 +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.
482 482  )))
483 483  
484 484  (((
485 -For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
381 +For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
486 486  )))
487 487  
488 -
489 -
490 -=== 2.4.3  Battery Info ===
491 -
492 -
493 493  (((
494 -Ex1: 0x0B45 = 2885mV
385 +
495 495  )))
496 496  
497 497  (((
498 -Ex2: 0x0B49 = 2889mV
389 +(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
499 499  )))
500 500  
501 501  
502 502  
503 -=== 2.4.4  Signal Strength ===
394 +=== 2.4.6  Soil Temperature ===
504 504  
505 -
506 506  (((
507 -NB-IoT Network signal Strength.
397 + 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
508 508  )))
509 509  
510 510  (((
511 -**Ex1: 0x1d = 29**
401 +**Example**:
512 512  )))
513 513  
514 514  (((
515 -(% style="color:blue" %)**0**(%%)  -113dBm or less
405 +If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
516 516  )))
517 517  
518 518  (((
519 -(% style="color:blue" %)**1**(%%)  -111dBm
409 +If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
520 520  )))
521 521  
522 -(((
523 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
524 -)))
525 525  
526 -(((
527 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
528 -)))
529 529  
414 +=== 2.4.7  Soil Conductivity (EC) ===
415 +
530 530  (((
531 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
417 +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).
532 532  )))
533 533  
534 -
535 -
536 -=== 2.4.5  Distance ===
537 -
538 -
539 -Get the distance. Flat object range 280mm - 7500mm.
540 -
541 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
421 +For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
543 543  )))
544 544  
545 545  (((
546 -(((
547 -(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
425 +Generally, the EC value of irrigation water is less than 800uS / cm.
548 548  )))
549 -)))
550 550  
551 551  (((
552 552  
... ... @@ -556,73 +556,45 @@
556 556  
557 557  )))
558 558  
559 -=== 2.4.6  Digital Interrupt ===
436 +=== 2.4.8  Digital Interrupt ===
560 560  
438 +Digital Interrupt refers to pin (% style="color:blue" %)**GPIO_EXTI**(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
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 -)))
565 -
566 -(((
567 567  The command is:
568 -)))
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 -)))
442 +(% 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]])**.**
573 573  
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 -)))
445 +The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up.
578 578  
579 579  
580 -(((
581 581  Example:
582 -)))
583 583  
584 -(((
585 585  0x(00): Normal uplink packet.
586 -)))
587 587  
588 -(((
589 589  0x(01): Interrupt Uplink Packet.
590 -)))
591 591  
592 592  
593 593  
594 -=== 2.4.7  ​+5V Output ===
456 +=== 2.4.9  ​+5V Output ===
595 595  
458 +NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
596 596  
597 -(((
598 -NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
599 -)))
600 600  
601 -
602 -(((
603 603  The 5V output time can be controlled by AT Command.
604 604  
605 -
606 -)))
607 -
608 -(((
609 609  (% style="color:blue" %)**AT+5VT=1000**
610 610  
611 -
612 -)))
613 -
614 -(((
615 615  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
616 -)))
617 617  
618 618  
619 619  
620 620  == 2.5  Downlink Payload ==
621 621  
471 +By default, NSE01 prints the downlink payload to console port.
622 622  
623 -By default, NDDS75 prints the downlink payload to console port.
473 +[[image:image-20220708133731-5.png]]
624 624  
625 -[[image:image-20220709100028-1.png]]
626 626  
627 627  
628 628  (((
... ... @@ -658,385 +658,435 @@
658 658  )))
659 659  
660 660  (((
661 -If payload = 0x04FF, it will reset the NDDS75
510 +If payload = 0x04FF, it will reset the NSE01
662 662  )))
663 663  
664 664  
665 665  * (% style="color:blue" %)**INTMOD**
666 666  
667 -(((
668 668  Downlink Payload: 06000003, Set AT+INTMOD=3
669 -)))
670 670  
671 671  
672 672  
673 -== 2.6  Distance alarm function(Since firmware v1.3.2) ==
520 +== 2.6  ​LED Indicator ==
674 674  
522 +(((
523 +The NSE01 has an internal LED which is to show the status of different state.
675 675  
676 -(% style="color:blue" %)** ➢ AT Command:**
677 677  
678 -(% style="color:#037691" %)** AT+ LDDSALARM=min,max**
526 +* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
527 +* Then the LED will be on for 1 second means device is boot normally.
528 +* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
529 +* For each uplink probe, LED will be on for 500ms.
530 +)))
679 679  
680 -² When min=0, and max≠0, Alarm higher than max
681 681  
682 -² When min≠0, and max=0, Alarm lower than min
683 683  
684 -² When min≠0 and max≠0, Alarm higher than max or lower than min
685 685  
535 +== 2.7  Installation in Soil ==
686 686  
687 -(% style="color:blue" %)** Example:**
537 +__**Measurement the soil surface**__
688 688  
689 -**AT+ LDDSALARM=260,2000**  ~/~/ Alarm when distance lower than 260.
539 +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. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
690 690  
541 +[[image:1657259653666-883.png]] ​
691 691  
692 692  
693 -== 2.7  Set the number of data to be uploaded and the recording time ==
544 +(((
545 +
694 694  
547 +(((
548 +Dig a hole with diameter > 20CM.
549 +)))
695 695  
696 -(% style="color:blue" %)** ➢ AT Command:**
551 +(((
552 +Horizontal insert the probe to the soil and fill the hole for long term measurement.
553 +)))
554 +)))
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.
556 +[[image:1654506665940-119.png]]
700 700  
701 - The diagram below explains the relationship between TR, NOUD, and TDC more clearly**:**
558 +(((
559 +
560 +)))
702 702  
703 -[[image:image-20221009000513-1.png||height="732" width="1018"]]
704 704  
563 +== 2.8  ​Firmware Change Log ==
705 705  
706 706  
707 -== 2.8  Read or Clear cached data ==
566 +Download URL & Firmware Change log
708 708  
568 +[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
709 709  
710 -(% style="color:blue" %)** ➢ AT Command:**
711 711  
712 -* (% style="color:#037691" %)** AT+CDP ** (%%) ~/~/  Read cached data
713 -* (% style="color:#037691" %)** AT+CDP=0**  (%%) ~/~/  Clear cached data
571 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H"]]
714 714  
715 -[[image:image-20220908175333-2.png]]
716 716  
717 717  
575 +== 2.9  ​Battery Analysis ==
718 718  
719 -== 2.9  ​LED Indicator ==
577 +=== 2.9.1  ​Battery Type ===
720 720  
721 721  
722 -The NDDS75 has an internal LED which is to show the status of different state.
580 +The NSE01 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.
723 723  
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.
583 +The battery is designed to last for several years depends on the actually use environment and update interval.
729 729  
730 -(((
731 -
732 -)))
733 733  
586 +The battery related documents as below:
734 734  
588 +* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
589 +* [[Lithium-Thionyl Chloride Battery>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]][[ datasheet>>https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
590 +* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
735 735  
736 -== 2.10  ​Firmware Change Log ==
737 -
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]]
593 +[[image:image-20220708140453-6.png]]
741 741  )))
742 742  
743 -(((
744 -
745 -)))
746 746  
747 -(((
748 -Upgrade Instruction: [[Upgrade Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
749 -)))
750 750  
598 +2.9.2 
751 751  
600 +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.
752 752  
753 -== 2.11  ​Battery Analysis ==
754 754  
603 +Instruction to use as below:
755 755  
756 -=== 2.11.1  ​Battery Type ===
757 757  
606 +Step 1: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
758 758  
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.
761 -)))
608 +[[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/]]
762 762  
763 -(((
764 -The battery is designed to last for several years depends on the actually use environment and update interval. 
765 -)))
766 766  
767 -(((
768 -The battery related documents as below:
769 -)))
611 +Step 2: Open it and choose
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/]]
613 +* Product Model
614 +* Uplink Interval
615 +* Working Mode
774 774  
775 -(((
776 -[[image:image-20220709101450-2.png]]
777 -)))
617 +And the Life expectation in difference case will be shown on the right.
778 778  
779 779  
780 780  
781 -=== 2.11.2  Power consumption Analyze ===
621 +=== 2.9.3  ​Battery Note ===
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.
624 +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.
786 786  )))
787 787  
788 788  
789 -(((
790 -Instruction to use as below:
791 -)))
792 792  
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 -)))
629 +=== 2.9.4  Replace the battery ===
796 796  
631 +The default battery pack of NSE01 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).
797 797  
798 -(((
799 -(% style="color:blue" %)**Step 2: **(%%) Open it and choose
800 -)))
801 801  
802 -* (((
803 -Product Model
804 -)))
805 -* (((
806 -Uplink Interval
807 -)))
808 -* (((
809 -Working Mode
810 -)))
811 811  
812 -(((
813 -And the Life expectation in difference case will be shown on the right.
814 -)))
635 += 3. ​Using the AT Commands =
815 815  
816 -[[image:image-20220709110451-3.png]]
637 +== 3.1 Access AT Commands ==
817 817  
818 818  
640 +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.
819 819  
820 -=== 2.11.3  ​Battery Note ===
642 +[[image:1654501986557-872.png||height="391" width="800"]]
821 821  
822 822  
823 -(((
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 -)))
645 +Or if you have below board, use below connection:
826 826  
827 827  
648 +[[image:1654502005655-729.png||height="503" width="801"]]
828 828  
829 -=== 2.11.4  Replace the battery ===
830 830  
831 831  
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).
834 -)))
652 +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:
835 835  
836 836  
655 + [[image:1654502050864-459.png||height="564" width="806"]]
837 837  
838 -= 3. ​ Access NB-IoT Module =
839 839  
658 +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]]
840 840  
841 -(((
842 -Users can directly access the AT command set of the NB-IoT module.
843 -)))
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/]] 
661 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
847 847  
848 -
849 -)))
663 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
850 850  
851 -[[image:1657333200519-600.png]]
665 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
852 852  
667 +(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
853 853  
854 854  
855 -= 4.  Using the AT Commands =
670 +(% style="color:#037691" %)**General Commands**(%%)      
856 856  
672 +(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
857 857  
858 -== 4.1  Access AT Commands ==
674 +(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
859 859  
676 +(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
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]]
678 +(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
862 862  
863 863  
864 -AT+<CMD>?  :  Help on <CMD>
681 +(% style="color:#037691" %)**Keys, IDs and EUIs management**
865 865  
866 -AT+<CMD>         :  Run <CMD>
683 +(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
867 867  
868 -AT+<CMD>=<value> :  Set the value
685 +(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
869 869  
870 -AT+<CMD>=?  :  Get the value
687 +(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
871 871  
689 +(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
872 872  
873 -(% style="color:#037691" %)**General Commands**(%%)      
691 +(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
874 874  
875 -AT  :  Attention       
693 +(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
876 876  
877 -AT?  :  Short Help     
695 +(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
878 878  
879 -ATZ  :  MCU Reset    
697 +(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
880 880  
881 -AT+TDC  :  Application Data Transmission Interval
699 +(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
882 882  
883 -AT+CFG  :  Print all configurations
701 +(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
884 884  
885 -AT+CFGMOD           :  Working mode selection
703 +(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
886 886  
887 -AT+INTMOD            :  Set the trigger interrupt mode
705 +(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
888 888  
889 -AT+5VT  :  Set extend the time of 5V power  
707 +(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
890 890  
891 -AT+PRO  :  Choose agreement
709 +(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
892 892  
893 -AT+WEIGRE  :  Get weight or set weight to 0
711 +(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
894 894  
895 -AT+WEIGAP  :  Get or Set the GapValue of weight
713 +(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
896 896  
897 -AT+RXDL  :  Extend the sending and receiving time
898 898  
899 -AT+CNTFAC  :  Get or set counting parameters
716 +(% style="color:#037691" %)**LoRa Network Management**
900 900  
901 -AT+SERVADDR  :  Server Address
718 +(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
902 902  
903 -AT+TR  :  Get or Set record time"
720 +(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
904 904  
905 -AT+APN     :  Get or set the APN
722 +(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
906 906  
907 -AT+FBAND  :  Get or Set whether to automatically modify the frequency band
724 +(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
908 908  
909 -AT+DNSCFG  : Get or Set DNS Server
726 +(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
910 910  
911 -AT+GETSENSORVALUE   :  Returns the current sensor measurement
728 +(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
912 912  
913 -AT+NOUD  :  Get or Set the number of data to be uploaded
730 +(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
914 914  
915 -AT+CDP     :  Read or Clear cached data
732 +(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
916 916  
917 -AT+LDDSALARM :  Get or Set alarm of distance
734 +(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
918 918  
736 +(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
919 919  
920 -(% style="color:#037691" %)**COAP Management**      
738 +(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
921 921  
922 -AT+URI            :  Resource parameters
740 +(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
923 923  
742 +(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
924 924  
925 -(% style="color:#037691" %)**UDP Management**
744 +(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
926 926  
927 -AT+CFM          :  Upload confirmation mode (only valid for UDP)
746 +(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
928 928  
929 929  
930 -(% style="color:#037691" %)**MQTT Management**
749 +(% style="color:#037691" %)**Information** 
931 931  
932 -AT+CLIENT  :  Get or Set MQTT client
751 +(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
933 933  
934 -AT+UNAME  :  Get or Set MQTT Username
753 +(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
935 935  
936 -AT+PWD  :  Get or Set MQTT password
755 +(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
937 937  
938 -AT+PUBTOPIC  :  Get or Set MQTT publish topic
757 +(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
939 939  
940 -AT+SUBTOPIC  :  Get or Set MQTT subscription topic
759 +(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
941 941  
761 +(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
942 942  
943 -(% style="color:#037691" %)**Information**          
763 + (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
944 944  
945 -AT+FDR  :  Factory Data Reset
946 946  
947 -AT+PWORD  :  Serial Access Password
766 += ​4. FAQ =
948 948  
768 +== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
949 949  
770 +(((
771 +You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
772 +When downloading the images, choose the required image file for download. ​
773 +)))
950 950  
951 -= ​5.  FAQ =
775 +(((
776 +
777 +)))
952 952  
779 +(((
780 +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.
781 +)))
953 953  
954 -== 5.1 ​ How to Upgrade Firmware ==
783 +(((
784 +
785 +)))
955 955  
956 -
957 957  (((
958 -User can upgrade the firmware for 1) bug fix, 2) new feature release.
788 +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.
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]]
792 +
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.**
796 +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.
967 967  )))
968 968  
799 +[[image:image-20220606154726-3.png]]
969 969  
970 970  
971 -= 6.  Trouble Shooting =
802 +When you use the TTN network, the US915 frequency bands use are:
972 972  
804 +* 903.9 - SF7BW125 to SF10BW125
805 +* 904.1 - SF7BW125 to SF10BW125
806 +* 904.3 - SF7BW125 to SF10BW125
807 +* 904.5 - SF7BW125 to SF10BW125
808 +* 904.7 - SF7BW125 to SF10BW125
809 +* 904.9 - SF7BW125 to SF10BW125
810 +* 905.1 - SF7BW125 to SF10BW125
811 +* 905.3 - SF7BW125 to SF10BW125
812 +* 904.6 - SF8BW500
973 973  
974 -== 6.1  ​Connection problem when uploading firmware ==
814 +(((
815 +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 975  
817 +* (% style="color:#037691" %)**AT+CHE=2**
818 +* (% style="color:#037691" %)**ATZ**
819 +)))
976 976  
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]]
822 +
823 +
824 +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.
979 979  )))
980 980  
981 -(% class="wikigeneratedid" %)
982 982  (((
983 983  
984 984  )))
985 985  
831 +(((
832 +The **AU915** band is similar. Below are the AU915 Uplink Channels.
833 +)))
986 986  
987 -== 6.2  AT Command input doesn't work ==
835 +[[image:image-20220606154825-4.png]]
988 988  
989 989  
838 +== 4.2 ​Can I calibrate LSE01 to different soil types? ==
839 +
840 +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]].
841 +
842 +
843 += 5. Trouble Shooting =
844 +
845 +== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
846 +
847 +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.
848 +
849 +
850 +== 5.2 AT Command input doesn't work ==
851 +
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.
854 +)))
992 992  
993 -
856 +
857 +== 5.3 Device rejoin in at the second uplink packet ==
858 +
859 +(% style="color:#4f81bd" %)**Issue describe as below:**
860 +
861 +[[image:1654500909990-784.png]]
862 +
863 +
864 +(% style="color:#4f81bd" %)**Cause for this issue:**
865 +
866 +(((
867 +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 =
871 +(% style="color:#4f81bd" %)**Solution: **
998 998  
873 +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**
875 +[[image:1654500929571-736.png||height="458" width="832"]]
1001 1001  
1002 1002  
878 += 6. ​Order Info =
879 +
880 +
881 +Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
882 +
883 +
884 +(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
885 +
886 +* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
887 +* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
888 +* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
889 +* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
890 +* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
891 +* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
892 +* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
893 +* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
894 +
895 +(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
896 +
897 +* (% style="color:red" %)**4**(%%): 4000mAh battery
898 +* (% style="color:red" %)**8**(%%): 8500mAh battery
899 +
1003 1003  (% class="wikigeneratedid" %)
1004 1004  (((
1005 1005  
1006 1006  )))
1007 1007  
1008 -= 8.  Packing Info =
905 += 7. Packing Info =
1009 1009  
1010 1010  (((
1011 1011  
1012 1012  
1013 1013  (% style="color:#037691" %)**Package Includes**:
911 +)))
1014 1014  
1015 -* NDDS75 NB-IoT Distance Detect Sensor Node x 1
1016 -* External antenna x 1
913 +* (((
914 +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**:
921 +)))
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
923 +* (((
924 +Device Size: cm
1029 1029  )))
926 +* (((
927 +Device Weight: g
928 +)))
929 +* (((
930 +Package Size / pcs : cm
931 +)))
932 +* (((
933 +Weight / pcs : g
1030 1030  
1031 -(((
1032 1032  
1033 -
1034 -
1035 -
1036 1036  )))
1037 1037  
1038 -= 9.  Support =
938 += 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]]
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-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