Skip to Content
Last modified by Mengting Qiu on 2024/04/02 16:44
From version 64.1
edited by Xiaoling
on 2022/07/08 14:21
Change comment: Uploaded new attachment "1657261278785-153.png", version {1}
To version 114.2
edited by Xiaoling
on 2022/07/09 16:12
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 +N95S31B NB-IoT Temperature & Humidity Sensor User Manual
Content
... ... @@ -1,5 +1,5 @@
1 1  (% style="text-align:center" %)
2 -[[image:image-20220606151504-2.jpeg||height="554" width="554"]]
2 +[[image:1657348034241-728.png||height="470" width="470"]]
3 3  
4 4  
5 5  
... ... @@ -7,10 +7,6 @@
7 7  
8 8  
9 9  
10 -
11 -
12 -
13 -
14 14  **Table of Contents:**
15 15  
16 16  
... ... @@ -20,36 +20,34 @@
20 20  
21 21  = 1.  Introduction =
22 22  
23 -== 1.1 ​ What is LoRaWAN Soil Moisture & EC Sensor ==
19 +== 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
24 24  
25 25  (((
26 26  
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.
24 +The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
29 29  
30 -It can detect (% style="color:blue" %)**Soil Moisture, Soil Temperature and Soil Conductivity**(%%), and upload its value to the server wirelessly.
26 +The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
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.
28 +N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
33 33  
34 -NSE01 are powered by (% style="color:blue" %)**8500mAh Li-SOCI2**(%%) batteries, which can be used for up to 5 years.  
30 +N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
35 35  
32 +
33 +~* make sure you have NB-IoT coverage locally.
34 +
36 36  
37 37  )))
38 38  
39 -[[image:1654503236291-817.png]]
38 +[[image:1657348284168-431.png]]
40 40  
41 41  
42 -[[image:1657245163077-232.png]]
43 43  
42 +== 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
46 +* Monitor Temperature & Humidity via SHT31
53 53  * AT Commands to change parameters
54 54  * Uplink on periodically
55 55  * Downlink to change configure
... ... @@ -59,6 +59,7 @@
59 59  * Micro SIM card slot for NB-IoT SIM
60 60  * 8500mAh Battery for long term use
61 61  
56 +
62 62  == 1.3  Specification ==
63 63  
64 64  
... ... @@ -76,90 +76,151 @@
76 76  * - B20 @H-FDD: 800MHz
77 77  * - B28 @H-FDD: 700MHz
78 78  
79 -(% style="color:#037691" %)**Probe Specification:**
74 +(% 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.
82 82  
83 -[[image:image-20220708101224-1.png]]
77 +* Li/SOCI2 un-chargeable battery
78 +* Capacity: 8500mAh
79 +* Self Discharge: <1% / Year @ 25°C
80 +* Max continuously current: 130mA
81 +* Max boost current: 2A, 1 second
84 84  
85 85  
86 -
87 87  == ​1.4  Applications ==
88 88  
86 +* Smart Buildings & Home Automation
87 +* Logistics and Supply Chain Management
88 +* Smart Metering
89 89  * Smart Agriculture
90 +* Smart Cities
91 +* Smart Factory
90 90  
91 91  (% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
92 92  ​
93 93  
96 +
94 94  == 1.5  Pin Definitions ==
95 95  
99 +N95S31B use the mother board from NBSN95 which as below.
96 96  
97 -[[image:1657246476176-652.png]]
101 +[[image:image-20220709144723-1.png]]
98 98  
99 99  
104 +=== 1.5.1 Jumper JP2 ===
100 100  
101 -= 2.  Use NSE01 to communicate with IoT Server =
106 +Power on Device when put this jumper.
102 102  
108 +
109 +
110 +=== 1.5.2 BOOT MODE / SW1 ===
111 +
112 +1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
113 +
114 +2) Flash: work mode, device starts to work and send out console output for further debug
115 +
116 +
117 +
118 +=== 1.5.3 Reset Button ===
119 +
120 +Press to reboot the device.
121 +
122 +
123 +
124 +=== 1.5.4 LED ===
125 +
126 +It will flash:
127 +
128 +1. When boot the device in flash mode
129 +1. Send an uplink packet
130 +
131 +
132 +
133 += 2.  Use N95S31B to communicate with IoT Server =
134 +
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.
139 +The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B 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 N95S31B.
108 108  )))
109 109  
110 110  
111 111  (((
112 -The diagram below shows the working flow in default firmware of NSE01:
144 +The diagram below shows the working flow in default firmware of N95S31B:
113 113  )))
114 114  
115 -[[image:image-20220708101605-2.png]]
147 +(((
148 +
149 +)))
116 116  
151 +[[image:1657350248151-650.png]]
152 +
117 117  (((
118 118  
119 119  )))
120 120  
121 121  
158 +== 2.2 ​ Configure the N95S31B ==
122 122  
123 -== 2.2 ​ Configure the NSE01 ==
124 124  
161 +=== 2.2.1  Power On N95S31B ===
125 125  
163 +
164 +[[image:image-20220709150546-2.png]]
165 +
166 +
126 126  === 2.2.1 Test Requirement ===
127 127  
128 128  
129 -To use NSE01 in your city, make sure meet below requirements:
170 +To use N95S31B in your city, make sure meet below requirements:
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.
173 +* The local NB-IoT network used the band that N95S31B supports.
133 133  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
134 134  
176 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
177 +
178 +N95S31B supports different communication protocol such as :
179 +
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
137 -)))
181 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
182 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
183 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
184 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
138 138  
186 +We will show how to use with each protocol. The IP addresses above are our test server. User need to change to point their corresponding server.
139 139  
140 -[[image:1657249419225-449.png]]
188 +
189 +)))
141 141  
191 +[[image:1657350625843-586.png]]
142 142  
143 143  
144 -=== 2.2.2 Insert SIM card ===
145 145  
195 +=== 2.2.3  Insert SIM card ===
196 +
197 +(((
146 146  Insert the NB-IoT Card get from your provider.
199 +)))
147 147  
201 +(((
148 148  User need to take out the NB-IoT module and insert the SIM card like below:
203 +)))
149 149  
150 150  
151 -[[image:1657249468462-536.png]]
206 +[[image:1657351240556-536.png]]
152 152  
153 153  
154 154  
155 -=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
210 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
156 156  
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.
214 +User need to configure N95S31B via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
160 160  )))
161 161  )))
162 162  
218 +[[image:1657351312545-300.png]]
163 163  
164 164  **Connection:**
165 165  
... ... @@ -179,94 +179,110 @@
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.
238 +Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B 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]]
241 +[[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/]]
243 +(((
244 +(% style="color:red" %)Note: the valid AT Commands can be found at:  (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
245 +)))
188 188  
189 189  
190 190  
191 -=== 2.2.4 Use CoAP protocol to uplink data ===
249 +=== 2.2.5  Use CoAP protocol to uplink data ===
192 192  
193 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/]]
194 194  
195 195  
254 +(((
196 196  **Use below commands:**
256 +)))
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
258 +* (((
259 +(% style="color:blue" %)**AT+PRO=1**  (%%) ~/~/ Set to use CoAP protocol to uplink
260 +)))
261 +* (((
262 +(% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5683   ** (%%)~/~/ to set CoAP server address and port
263 +)))
264 +* (((
265 +(% style="color:blue" %)**AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" ** (%%) ~/~/Set COAP resource path
266 +)))
201 201  
268 +(((
269 +
270 +
202 202  For parameter description, please refer to AT command set
272 +)))
203 203  
204 -[[image:1657249793983-486.png]]
274 +[[image:1657352146020-183.png]]
205 205  
206 206  
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.
277 +(((
278 +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.
279 +)))
208 208  
209 -[[image:1657249831934-534.png]]
281 +[[image:1657352185396-303.png]]
210 210  
211 211  
212 212  
213 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
285 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
214 214  
215 -This feature is supported since firmware version v1.0.1
216 216  
217 -
218 -* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
288 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
219 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
290 +* (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
221 221  
222 -[[image:1657249864775-321.png]]
292 +[[image:1657352391268-297.png]]
223 223  
224 224  
225 -[[image:1657249930215-289.png]]
295 +[[image:1657352403317-397.png]]
226 226  
227 227  
228 228  
229 -=== 2.2.6 Use MQTT protocol to uplink data ===
299 +=== 2.2.7  Use MQTT protocol to uplink data ===
230 230  
231 -This feature is supported since firmware version v110
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
232 232  
303 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
304 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
305 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
306 +* (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
307 +* (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
308 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527                               **(%%)~/~/Set the sending topic of MQTT
309 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527          **(%%) ~/~/Set the subscription topic of MQTT
233 233  
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
311 +[[image:1657352634421-276.png]]
241 241  
242 -[[image:1657249978444-674.png]]
243 243  
314 +[[image:1657352645687-385.png]]
244 244  
245 -[[image:1657249990869-686.png]]
316 +(((
317 +To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
318 +)))
246 246  
247 247  
248 248  (((
249 -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.
322 +MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
250 250  )))
251 251  
252 252  
253 253  
254 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
255 255  
256 256  This feature is supported since firmware version v110
257 257  
258 -
259 259  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
260 260  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
261 261  
262 -[[image:1657250217799-140.png]]
334 +[[image:1657352898400-901.png]]
263 263  
264 264  
265 -[[image:1657250255956-604.png]]
337 +[[image:1657352914475-252.png]]
266 266  
267 267  
268 268  
269 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
270 270  
271 271  User can use below command to change the (% style="color:green" %)**uplink interval**.
272 272  
... ... @@ -273,157 +273,198 @@
273 273  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
274 274  
275 275  (((
276 -(% style="color:red" %)**NOTE:**
348 +
277 277  )))
278 278  
279 -(((
280 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
281 -)))
282 282  
283 283  
284 -
285 285  == 2.3  Uplink Payload ==
286 286  
287 -In this mode, uplink payload includes in total 18 bytes
288 288  
289 -(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
290 -|=(% style="width: 50px;" %)(((
291 -**Size(bytes)**
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"]]
356 +NBSN95 has different working mode for the connections of different type of sensors. This section describes these modes. User can use the AT Command (% style="color:blue" %)**AT+MOD**(%%) to set NBSN95 to different working modes.
294 294  
295 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
296 296  
359 +For example:
297 297  
298 -[[image:image-20220708111918-4.png]]
361 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
299 299  
300 300  
301 -The payload is ASCII string, representative same HEX:
364 +The uplink payloads are composed in  ASCII String. For example:
302 302  
303 -0x72403155615900640c7817075e0a8c02f900 where:
366 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
304 304  
305 -* Device ID: 0x 724031556159 = 724031556159
306 -* Version: 0x0064=100=1.0.0
368 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
307 307  
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
314 314  
315 -== 2.4  Payload Explanation and Sensor Interface ==
371 +(% style="color:red" %)**NOTE:**
316 316  
373 +(% style="color:red" %)
374 +1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
375 +1. By default, the device will send an uplink message every 1 hour.
317 317  
318 -=== 2.4.1  Device ID ===
319 319  
320 -By default, the Device ID equal to the last 6 bytes of IMEI.
321 321  
322 -User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
323 323  
324 -**Example:**
380 +=== 2.3.1  Payload Analyze ===
325 325  
326 -AT+DEUI=A84041F15612
382 +N95S31B uplink payload includes in total 21 bytes
327 327  
328 -The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
329 329  
385 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
386 +|=(% style="width: 60px;" %)(((
387 +**Size(bytes)**
388 +)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
389 +|(% 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:123px" %)MOD 0X01|(% style="width:99px" %)(((
390 +Reserve/ Same as NBSN95 CFGMOD=1
330 330  
392 +No function here.
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
331 331  
332 -=== 2.4.2  Version Info ===
396 +By SHT31
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
333 333  
334 -Specify the software version: 0x64=100, means firmware version 1.00.
400 +By SHT31
401 +)))
335 335  
336 -For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
403 +(((
404 +(((
405 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
406 +)))
407 +)))
337 337  
338 338  
410 +[[image:1657354294009-643.png]]
339 339  
340 -=== 2.4.3  Battery Info ===
341 -
342 342  (((
343 -Check the battery voltage for LSE01.
413 +The payload is ASCII string, representative same HEX:
344 344  )))
345 345  
346 346  (((
347 -Ex1: 0x0B45 = 2885mV
417 +0x72403155615900640c6c19029200 where:
348 348  )))
349 349  
350 -(((
351 -Ex2: 0x0B49 = 2889mV
420 +* (((
421 +Device ID: 0x724031556159 = 724031556159
352 352  )))
423 +* (((
424 +Version: 0x0064=100=1.0.0
425 +)))
353 353  
427 +* (((
428 +BAT: 0x0c6c = 3180 mV = 3.180V
429 +)))
430 +* (((
431 +Signal: 0x19 = 25
432 +)))
433 +* (((
434 +Distance: 0x0292= 658 mm
435 +)))
436 +* (((
437 +Interrupt: 0x00 = 0
354 354  
355 355  
356 -=== 2.4.4  Signal Strength ===
357 357  
358 -NB-IoT Network signal Strength.
441 +
442 +)))
359 359  
360 -**Ex1: 0x1d = 29**
444 +== 2.4  Payload Explanation and Sensor Interface ==
361 361  
362 -(% style="color:blue" %)**0**(%%)  -113dBm or less
363 363  
364 -(% style="color:blue" %)**1**(%%)  -111dBm
447 +=== 2.4.1  Device ID ===
365 365  
366 -(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
449 +(((
450 +By default, the Device ID equal to the last 6 bytes of IMEI.
451 +)))
367 367  
368 -(% style="color:blue" %)**31**  (%%) -51dBm or greater
453 +(((
454 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
455 +)))
369 369  
370 -(% style="color:blue" %)**99**   (%%) Not known or not detectable
457 +(((
458 +**Example:**
459 +)))
371 371  
461 +(((
462 +AT+DEUI=A84041F15612
463 +)))
372 372  
465 +(((
466 +The Device ID is stored in a none-erase area, Upgrade the firmware or run **AT+FDR** won't erase Device ID.
467 +)))
373 373  
374 -=== 2.4.5  Soil Moisture ===
375 375  
470 +
471 +=== 2.4.2  Version Info ===
472 +
376 376  (((
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.
474 +Specify the software version: 0x64=100, means firmware version 1.00.
378 378  )))
379 379  
380 380  (((
381 -For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
478 +For example: 0x00 64 : this device is NDDS75 with firmware version 1.0.0.
382 382  )))
383 383  
481 +
482 +
483 +=== 2.4.3  Battery Info ===
484 +
384 384  (((
385 -
486 +Ex1: 0x0B45 = 2885mV
386 386  )))
387 387  
388 388  (((
389 -(% style="color:#4f81bd" %)**05DC(H) = 1500(D) /100 = 15%.**
490 +Ex2: 0x0B49 = 2889mV
390 390  )))
391 391  
392 392  
393 393  
394 -=== 2.4.6  Soil Temperature ===
495 +=== 2.4.4  Signal Strength ===
395 395  
396 396  (((
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
498 +NB-IoT Network signal Strength.
398 398  )))
399 399  
400 400  (((
401 -**Example**:
502 +**Ex1: 0x1d = 29**
402 402  )))
403 403  
404 404  (((
405 -If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
506 +(% style="color:blue" %)**0**(%%)  -113dBm or less
406 406  )))
407 407  
408 408  (((
409 -If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
510 +(% style="color:blue" %)**1**(%%)  -111dBm
410 410  )))
411 411  
513 +(((
514 +(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
515 +)))
412 412  
517 +(((
518 +(% style="color:blue" %)**31**  (%%) -51dBm or greater
519 +)))
413 413  
414 -=== 2.4.7  Soil Conductivity (EC) ===
415 -
416 416  (((
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).
522 +(% style="color:blue" %)**99**   (%%) Not known or not detectable
418 418  )))
419 419  
525 +
526 +
527 +=== 2.4.5  Distance ===
528 +
529 +Get the distance. Flat object range 280mm - 7500mm.
530 +
420 420  (((
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.
532 +For example, if the data you get from the register is **__0x0B 0x05__**, the distance between the sensor and the measured object is
422 422  )))
423 423  
424 424  (((
425 -Generally, the EC value of irrigation water is less than 800uS / cm.
536 +(((
537 +(% style="color:blue" %)** 0B05(H) = 2821(D) = 2821mm.**
426 426  )))
539 +)))
427 427  
428 428  (((
429 429  
... ... @@ -433,47 +433,68 @@
433 433  
434 434  )))
435 435  
436 -=== 2.4.8  Digital Interrupt ===
549 +=== 2.4.6  Digital Interrupt ===
437 437  
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.
551 +(((
552 +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.
553 +)))
439 439  
555 +(((
440 440  The command is:
557 +)))
441 441  
559 +(((
442 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]])**.**
561 +)))
443 443  
444 444  
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.
564 +(((
565 +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.
566 +)))
446 446  
447 447  
569 +(((
448 448  Example:
571 +)))
449 449  
573 +(((
450 450  0x(00): Normal uplink packet.
575 +)))
451 451  
577 +(((
452 452  0x(01): Interrupt Uplink Packet.
579 +)))
453 453  
454 454  
455 455  
456 -=== 2.4.9  ​+5V Output ===
583 +=== 2.4.7  ​+5V Output ===
457 457  
458 -NSE01 will enable +5V output before all sampling and disable the +5v after all sampling. 
585 +(((
586 +NDDS75 will enable +5V output before all sampling and disable the +5v after all sampling. 
587 +)))
459 459  
460 460  
590 +(((
461 461  The 5V output time can be controlled by AT Command.
592 +)))
462 462  
594 +(((
463 463  (% style="color:blue" %)**AT+5VT=1000**
596 +)))
464 464  
598 +(((
465 465  Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
600 +)))
466 466  
467 467  
468 468  
469 469  == 2.5  Downlink Payload ==
470 470  
471 -By default, NSE01 prints the downlink payload to console port.
606 +By default, NDDS75 prints the downlink payload to console port.
472 472  
473 -[[image:image-20220708133731-5.png]]
608 +[[image:image-20220709100028-1.png]]
474 474  
475 475  
476 -
477 477  (((
478 478  (% style="color:blue" %)**Examples:**
479 479  )))
... ... @@ -507,95 +507,81 @@
507 507  )))
508 508  
509 509  (((
510 -If payload = 0x04FF, it will reset the NSE01
644 +If payload = 0x04FF, it will reset the NDDS75
511 511  )))
512 512  
513 513  
514 514  * (% style="color:blue" %)**INTMOD**
515 515  
650 +(((
516 516  Downlink Payload: 06000003, Set AT+INTMOD=3
652 +)))
517 517  
518 518  
519 519  
520 520  == 2.6  ​LED Indicator ==
521 521  
522 -(((
523 -The NSE01 has an internal LED which is to show the status of different state.
524 524  
659 +The NDDS75 has an internal LED which is to show the status of different state.
525 525  
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)
661 +
662 +* 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)
527 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.
664 +* After NDDS75 join NB-IoT network. The LED will be ON for 3 seconds.
529 529  * For each uplink probe, LED will be on for 500ms.
666 +
667 +(((
668 +
530 530  )))
531 531  
532 532  
533 533  
673 +== 2.7  ​Firmware Change Log ==
534 534  
535 -== 2.7  Installation in Soil ==
536 536  
537 -__**Measurement the soil surface**__
538 -
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]]
540 -
541 -[[image:1657259653666-883.png]] ​
542 -
543 -
544 544  (((
545 -
546 -
547 -(((
548 -Dig a hole with diameter > 20CM.
677 +Download URL & Firmware Change log
549 549  )))
550 550  
551 551  (((
552 -Horizontal insert the probe to the soil and fill the hole for long term measurement.
681 +[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/Firmware/]]
553 553  )))
554 -)))
555 555  
556 -[[image:1654506665940-119.png]]
557 557  
558 558  (((
559 -
686 +Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H5.1200BHowtoUpgradeFirmware"]]
560 560  )))
561 561  
562 562  
563 -== 2.8  ​Firmware Change Log ==
564 564  
691 +== 2.8  ​Battery Analysis ==
565 565  
566 -Download URL & Firmware Change log
693 +=== 2.8.1  ​Battery Type ===
567 567  
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/]]
569 569  
696 +(((
697 +The NDDS75 battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
698 +)))
570 570  
571 -Upgrade Instruction: [[Upgrade_Firmware>>||anchor="H"]]
572 -
573 -
574 -
575 -== 2.9  ​Battery Analysis ==
576 -
577 -=== 2.9.1  ​Battery Type ===
578 -
579 -
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.
581 -
582 -
700 +(((
583 583  The battery is designed to last for several years depends on the actually use environment and update interval. 
702 +)))
584 584  
585 -
704 +(((
586 586  The battery related documents as below:
706 +)))
587 587  
588 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/]]
709 +* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
590 590  * [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
591 591  
592 592  (((
593 -[[image:image-20220708140453-6.png]]
713 +[[image:image-20220709101450-2.png]]
594 594  )))
595 595  
596 596  
597 597  
598 -=== 2.9.2  Power consumption Analyze ===
718 +=== 2.8.2  Power consumption Analyze ===
599 599  
600 600  (((
601 601  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.
... ... @@ -629,11 +629,11 @@
629 629  And the Life expectation in difference case will be shown on the right.
630 630  )))
631 631  
632 -[[image:image-20220708141352-7.jpeg]]
752 +[[image:image-20220709110451-3.png]]
633 633  
634 634  
635 635  
636 -=== 2.9.3  ​Battery Note ===
756 +=== 2.8.3  ​Battery Note ===
637 637  
638 638  (((
639 639  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.
... ... @@ -641,10 +641,10 @@
641 641  
642 642  
643 643  
644 -=== 2.9.4  Replace the battery ===
764 +=== 2.8.4  Replace the battery ===
645 645  
646 646  (((
647 -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).
767 +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).
648 648  )))
649 649  
650 650  
... ... @@ -656,293 +656,154 @@
656 656  )))
657 657  
658 658  (((
659 -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/]]
779 +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/]] 
660 660  )))
661 661  
662 -[[image:1657261119050-993.png]]
782 +[[image:1657333200519-600.png]]
663 663  
664 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.jpg]]
665 665  
666 666  
786 += 4.  Using the AT Commands =
667 667  
668 -== 3.1 Access AT Commands ==
788 +== 4.1  Access AT Commands ==
669 669  
790 +See this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
670 670  
671 -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.
672 672  
673 -[[image:1654501986557-872.png||height="391" width="800"]]
793 +AT+<CMD>?  : Help on <CMD>
674 674  
795 +AT+<CMD>         : Run <CMD>
675 675  
676 -Or if you have below board, use below connection:
797 +AT+<CMD>=<value> : Set the value
677 677  
799 +AT+<CMD>=?  : Get the value
678 678  
679 -[[image:1654502005655-729.png||height="503" width="801"]]
680 680  
681 -
682 -
683 -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:
684 -
685 -
686 - [[image:1654502050864-459.png||height="564" width="806"]]
687 -
688 -
689 -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]]
690 -
691 -
692 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>? **(%%) : Help on <CMD>
693 -
694 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD> **(%%) : Run <CMD>
695 -
696 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=<value>**(%%) : Set the value
697 -
698 -(% style="background-color:#dcdcdc" %)**AT+<CMD>=?AT+<CMD>=?**(%%)  : Get the value
699 -
700 -
701 701  (% style="color:#037691" %)**General Commands**(%%)      
702 702  
703 -(% style="background-color:#dcdcdc" %)**AT**(%%)  : Attention       
804 +AT  : Attention       
704 704  
705 -(% style="background-color:#dcdcdc" %)**AT?**(%%)  : Short Help     
806 +AT?  : Short Help     
706 706  
707 -(% style="background-color:#dcdcdc" %)**ATZ**(%%)  : MCU Reset    
808 +ATZ  : MCU Reset    
708 708  
709 -(% style="background-color:#dcdcdc" %)**AT+TDC**(%%)  : Application Data Transmission Interval 
810 +AT+TDC  : Application Data Transmission Interval
710 710  
812 +AT+CFG  : Print all configurations
711 711  
712 -(% style="color:#037691" %)**Keys, IDs and EUIs management**
814 +AT+CFGMOD           : Working mode selection
713 713  
714 -(% style="background-color:#dcdcdc" %)**AT+APPEUI**(%%)              : Application EUI      
816 +AT+INTMOD            : Set the trigger interrupt mode
715 715  
716 -(% style="background-color:#dcdcdc" %)**AT+APPKEY**(%%)              : Application Key     
818 +AT+5VT  : Set extend the time of 5V power  
717 717  
718 -(% style="background-color:#dcdcdc" %)**AT+APPSKEY**(%%)            : Application Session Key
820 +AT+PRO  : Choose agreement
719 719  
720 -(% style="background-color:#dcdcdc" %)**AT+DADDR**(%%)              : Device Address     
822 +AT+WEIGRE  : Get weight or set weight to 0
721 721  
722 -(% style="background-color:#dcdcdc" %)**AT+DEUI**(%%)                   : Device EUI     
824 +AT+WEIGAP  : Get or Set the GapValue of weight
723 723  
724 -(% style="background-color:#dcdcdc" %)**AT+NWKID**(%%)               : Network ID (You can enter this command change only after successful network connection) 
826 +AT+RXDL  : Extend the sending and receiving time
725 725  
726 -(% style="background-color:#dcdcdc" %)**AT+NWKSKEY**(%%)          : Network Session Key Joining and sending date on LoRa network  
828 +AT+CNTFAC  : Get or set counting parameters
727 727  
728 -(% style="background-color:#dcdcdc" %)**AT+CFM**(%%)  : Confirm Mode       
830 +AT+SERVADDR  : Server Address
729 729  
730 -(% style="background-color:#dcdcdc" %)**AT+CFS**(%%)                     : Confirm Status       
731 731  
732 -(% style="background-color:#dcdcdc" %)**AT+JOIN**(%%)  : Join LoRa? Network       
833 +(% style="color:#037691" %)**COAP Management**      
733 733  
734 -(% style="background-color:#dcdcdc" %)**AT+NJM**(%%)  : LoRa? Network Join Mode    
835 +AT+URI            : Resource parameters
735 735  
736 -(% style="background-color:#dcdcdc" %)**AT+NJS**(%%)                     : LoRa? Network Join Status    
737 737  
738 -(% style="background-color:#dcdcdc" %)**AT+RECV**(%%)                  : Print Last Received Data in Raw Format
838 +(% style="color:#037691" %)**UDP Management**
739 739  
740 -(% style="background-color:#dcdcdc" %)**AT+RECVB**(%%)                : Print Last Received Data in Binary Format      
840 +AT+CFM          : Upload confirmation mode (only valid for UDP)
741 741  
742 -(% style="background-color:#dcdcdc" %)**AT+SEND**(%%)                  : Send Text Data      
743 743  
744 -(% style="background-color:#dcdcdc" %)**AT+SENB**(%%)                  : Send Hexadecimal Data
843 +(% style="color:#037691" %)**MQTT Management**
745 745  
845 +AT+CLIENT               : Get or Set MQTT client
746 746  
747 -(% style="color:#037691" %)**LoRa Network Management**
847 +AT+UNAME  : Get or Set MQTT Username
748 748  
749 -(% style="background-color:#dcdcdc" %)**AT+ADR**(%%)          : Adaptive Rate
849 +AT+PWD                  : Get or Set MQTT password
750 750  
751 -(% style="background-color:#dcdcdc" %)**AT+CLASS**(%%)  : LoRa Class(Currently only support class A
851 +AT+PUBTOPIC  : Get or Set MQTT publish topic
752 752  
753 -(% style="background-color:#dcdcdc" %)**AT+DCS**(%%)  : Duty Cycle Setting 
853 +AT+SUBTOPIC  : Get or Set MQTT subscription topic
754 754  
755 -(% style="background-color:#dcdcdc" %)**AT+DR**(%%)  : Data Rate (Can Only be Modified after ADR=0)     
756 756  
757 -(% style="background-color:#dcdcdc" %)**AT+FCD**(%%)  : Frame Counter Downlink       
856 +(% style="color:#037691" %)**Information**          
758 758  
759 -(% style="background-color:#dcdcdc" %)**AT+FCU**(%%)  : Frame Counter Uplink   
858 +AT+FDR  : Factory Data Reset
760 760  
761 -(% style="background-color:#dcdcdc" %)**AT+JN1DL**(%%)  : Join Accept Delay1
860 +AT+PWORD  : Serial Access Password
762 762  
763 -(% style="background-color:#dcdcdc" %)**AT+JN2DL**(%%)  : Join Accept Delay2
764 764  
765 -(% style="background-color:#dcdcdc" %)**AT+PNM**(%%)  : Public Network Mode   
766 766  
767 -(% style="background-color:#dcdcdc" %)**AT+RX1DL**(%%)  : Receive Delay1      
864 += ​5.  FAQ =
768 768  
769 -(% style="background-color:#dcdcdc" %)**AT+RX2DL**(%%)  : Receive Delay2      
866 +== 5.1 ​ How to Upgrade Firmware ==
770 770  
771 -(% style="background-color:#dcdcdc" %)**AT+RX2DR**(%%)  : Rx2 Window Data Rate 
772 772  
773 -(% style="background-color:#dcdcdc" %)**AT+RX2FQ**(%%)  : Rx2 Window Frequency
774 -
775 -(% style="background-color:#dcdcdc" %)**AT+TXP**(%%)  : Transmit Power
776 -
777 -(% style="background-color:#dcdcdc" %)**AT+ MOD**(%%)  : Set work mode
778 -
779 -
780 -(% style="color:#037691" %)**Information** 
781 -
782 -(% style="background-color:#dcdcdc" %)**AT+RSSI**(%%)           : RSSI of the Last Received Packet   
783 -
784 -(% style="background-color:#dcdcdc" %)**AT+SNR**(%%)           : SNR of the Last Received Packet   
785 -
786 -(% style="background-color:#dcdcdc" %)**AT+VER**(%%)           : Image Version and Frequency Band       
787 -
788 -(% style="background-color:#dcdcdc" %)**AT+FDR**(%%)           : Factory Data Reset
789 -
790 -(% style="background-color:#dcdcdc" %)**AT+PORT**(%%)  : Application Port    
791 -
792 -(% style="background-color:#dcdcdc" %)**AT+CHS**(%%)  : Get or Set Frequency (Unit: Hz) for Single Channel Mode
793 -
794 - (% style="background-color:#dcdcdc" %)**AT+CHE**(%%)  : Get or Set eight channels mode, Only for US915, AU915, CN470
795 -
796 -
797 -= ​4. FAQ =
798 -
799 -== 4.1 ​How to change the LoRa Frequency Bands/Region? ==
800 -
801 801  (((
802 -You can follow the instructions for [[how to upgrade image>>||anchor="H2.10200BFirmwareChangeLog"]].
803 -When downloading the images, choose the required image file for download. ​
870 +User can upgrade the firmware for 1) bug fix, 2) new feature release.
804 804  )))
805 805  
806 806  (((
807 -
874 +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]]
808 808  )))
809 809  
810 810  (((
811 -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.
878 +(% style="color:red" %)Notice, NDDS75 and LDDS75 share the same mother board. They use the same connection and method to update.
812 812  )))
813 813  
814 -(((
815 -
816 -)))
817 817  
818 -(((
819 -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.
820 -)))
821 821  
822 -(((
823 -
824 -)))
883 += 6.  Trouble Shooting =
825 825  
826 -(((
827 -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.
828 -)))
885 +== 6.1  ​Connection problem when uploading firmware ==
829 829  
830 -[[image:image-20220606154726-3.png]]
831 831  
832 -
833 -When you use the TTN network, the US915 frequency bands use are:
834 -
835 -* 903.9 - SF7BW125 to SF10BW125
836 -* 904.1 - SF7BW125 to SF10BW125
837 -* 904.3 - SF7BW125 to SF10BW125
838 -* 904.5 - SF7BW125 to SF10BW125
839 -* 904.7 - SF7BW125 to SF10BW125
840 -* 904.9 - SF7BW125 to SF10BW125
841 -* 905.1 - SF7BW125 to SF10BW125
842 -* 905.3 - SF7BW125 to SF10BW125
843 -* 904.6 - SF8BW500
844 -
845 845  (((
846 -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:
847 -
848 -* (% style="color:#037691" %)**AT+CHE=2**
849 -* (% style="color:#037691" %)**ATZ**
889 +**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]]
850 850  )))
851 851  
892 +(% class="wikigeneratedid" %)
852 852  (((
853 853  
854 -
855 -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.
856 856  )))
857 857  
858 -(((
859 -
860 -)))
861 861  
862 -(((
863 -The **AU915** band is similar. Below are the AU915 Uplink Channels.
864 -)))
898 +== 6.2  AT Command input doesn't work ==
865 865  
866 -[[image:image-20220606154825-4.png]]
867 -
868 -
869 -== 4.2 ​Can I calibrate LSE01 to different soil types? ==
870 -
871 -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]].
872 -
873 -
874 -= 5. Trouble Shooting =
875 -
876 -== 5.1 ​Why I can't join TTN in US915 / AU915 bands? ==
877 -
878 -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.
879 -
880 -
881 -== 5.2 AT Command input doesn't work ==
882 -
883 883  (((
884 884  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.
885 -)))
886 886  
887 -
888 -== 5.3 Device rejoin in at the second uplink packet ==
889 -
890 -(% style="color:#4f81bd" %)**Issue describe as below:**
891 -
892 -[[image:1654500909990-784.png]]
893 -
894 -
895 -(% style="color:#4f81bd" %)**Cause for this issue:**
896 -
897 -(((
898 -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.
903 +
899 899  )))
900 900  
901 901  
902 -(% style="color:#4f81bd" %)**Solution: **
907 += 7. ​ Order Info =
903 903  
904 -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:
905 905  
906 -[[image:1654500929571-736.png||height="458" width="832"]]
910 +Part Number**:** (% style="color:#4f81bd" %)**NSDDS75**
907 907  
908 908  
909 -= 6. ​Order Info =
910 -
911 -
912 -Part Number**:** (% style="color:#4f81bd" %)**LSE01-XX-YY**
913 -
914 -
915 -(% style="color:#4f81bd" %)**XX**(%%)**:** The default frequency band
916 -
917 -* (% style="color:red" %)**AS923**(%%): LoRaWAN AS923 band
918 -* (% style="color:red" %)**AU915**(%%): LoRaWAN AU915 band
919 -* (% style="color:red" %)**EU433**(%%): LoRaWAN EU433 band
920 -* (% style="color:red" %)**EU868**(%%): LoRaWAN EU868 band
921 -* (% style="color:red" %)**KR920**(%%): LoRaWAN KR920 band
922 -* (% style="color:red" %)**US915**(%%): LoRaWAN US915 band
923 -* (% style="color:red" %)**IN865**(%%):  LoRaWAN IN865 band
924 -* (% style="color:red" %)**CN470**(%%): LoRaWAN CN470 band
925 -
926 -(% style="color:#4f81bd" %)**YY**(%%)**: **Battery Option
927 -
928 -* (% style="color:red" %)**4**(%%): 4000mAh battery
929 -* (% style="color:red" %)**8**(%%): 8500mAh battery
930 -
931 931  (% class="wikigeneratedid" %)
932 932  (((
933 933  
934 934  )))
935 935  
936 -= 7. Packing Info =
918 += 8.  Packing Info =
937 937  
938 938  (((
939 939  
940 940  
941 941  (% style="color:#037691" %)**Package Includes**:
942 -)))
943 943  
944 -* (((
945 -LSE01 LoRaWAN Soil Moisture & EC Sensor x 1
925 +* NSE01 NB-IoT Distance Detect Sensor Node x 1
926 +* External antenna x 1
946 946  )))
947 947  
948 948  (((
... ... @@ -949,24 +949,22 @@
949 949  
950 950  
951 951  (% style="color:#037691" %)**Dimension and weight**:
952 -)))
953 953  
954 -* (((
955 -Device Size: cm
934 +
935 +* Device Size: 13.0 x 5 x 4.5 cm
936 +* Device Weight: 150g
937 +* Package Size / pcs : 15 x 12x 5.5 cm
938 +* Weight / pcs : 220g
956 956  )))
957 -* (((
958 -Device Weight: g
959 -)))
960 -* (((
961 -Package Size / pcs : cm
962 -)))
963 -* (((
964 -Weight / pcs : g
965 965  
941 +(((
966 966  
943 +
944 +
945 +
967 967  )))
968 968  
969 -= 8. Support =
948 += 9.  Support =
970 970  
971 971  * 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.
972 972  * 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]]
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
1657348034241-728.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +127.8 KB
Content
1657348284168-431.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.5 KB
Content
1657350248151-650.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content
1657350625843-586.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +93.3 KB
Content
1657351240556-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657351312545-300.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +675.8 KB
Content
1657352146020-183.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +264.0 KB
Content
1657352185396-303.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.3 KB
Content
1657352391268-297.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +238.0 KB
Content
1657352403317-397.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +547.7 KB
Content
1657352634421-276.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +163.6 KB
Content
1657352645687-385.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
1657352898400-901.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +144.8 KB
Content
1657352914475-252.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +157.0 KB
Content
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.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-20220709144723-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +413.1 KB
Content
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content