Last modified by Bei Jinggeng on 2024/05/31 09:53
<
From version < 45.5 >
edited by Xiaoling
on 2022/07/08 10:39
To version < 57.4 >
edited by Xiaoling
on 2022/07/08 11:40
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -59,8 +59,6 @@
59 59  * Micro SIM card slot for NB-IoT SIM
60 60  * 8500mAh Battery for long term use
61 61  
62 -
63 -
64 64  == 1.3  Specification ==
65 65  
66 66  
... ... @@ -69,7 +69,6 @@
69 69  * Supply Voltage: 2.1v ~~ 3.6v
70 70  * Operating Temperature: -40 ~~ 85°C
71 71  
72 -
73 73  (% style="color:#037691" %)**NB-IoT Spec:**
74 74  
75 75  * - B1 @H-FDD: 2100MHz
... ... @@ -79,7 +79,6 @@
79 79  * - B20 @H-FDD: 800MHz
80 80  * - B28 @H-FDD: 700MHz
81 81  
82 -
83 83  (% style="color:#037691" %)**Probe Specification:**
84 84  
85 85  Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
... ... @@ -126,6 +126,7 @@
126 126  
127 127  == 2.2 ​ Configure the NSE01 ==
128 128  
125 +
129 129  === 2.2.1 Test Requirement ===
130 130  
131 131  
... ... @@ -135,11 +135,12 @@
135 135  * The local NB-IoT network used the band that NSE01 supports.
136 136  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
137 137  
138 -
135 +(((
139 139  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 +)))
140 140  
141 141  
142 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image002.gif]]
140 +[[image:1657249419225-449.png]]
143 143  
144 144  
145 145  
... ... @@ -147,205 +147,199 @@
147 147  
148 148  Insert the NB-IoT Card get from your provider.
149 149  
150 -
151 151  User need to take out the NB-IoT module and insert the SIM card like below:
152 152  
153 153  
154 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image004.gif]]
151 +[[image:1657249468462-536.png]]
155 155  
156 156  
154 +
157 157  === 2.2.3 Connect USB – TTL to NSE01 to configure it ===
158 158  
157 +(((
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.
160 +)))
161 +)))
159 159  
160 -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.
161 161  
164 +**Connection:**
162 162  
166 + (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
163 163  
168 + (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
164 164  
165 -Connection:
170 + (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
166 166  
167 -USB TTL GND <~-~-~-~-> GND
168 168  
169 -USB TTL TXD <~-~-~-~-> UART_RXD
170 -
171 -USB TTL RXD <~-~-~-~-> UART_TXD
172 -
173 -
174 -
175 175  In the PC, use below serial tool settings:
176 176  
177 -* Baud: **9600**
178 -* Data bits:** 8**
179 -* Stop bits: **1**
180 -* Parity: **None**
181 -* Flow Control: **None**
175 +* Baud:  (% style="color:green" %)**9600**
176 +* Data bits:** (% style="color:green" %)8(%%)**
177 +* Stop bits: (% style="color:green" %)**1**
178 +* Parity:  (% style="color:green" %)**None**
179 +* Flow Control: (% style="color:green" %)**None**
182 182  
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.
183 +)))
183 183  
184 -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 **password: 12345678** to access AT Command input.
185 +[[image:image-20220708110657-3.png]]
185 185  
186 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image009.jpg]]
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/]]
187 187  
188 -Note: the valid AT Commands can be found at:
189 189  
190 -[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
191 191  
191 +=== 2.2.4 Use CoAP protocol to uplink data ===
192 192  
193 -1.
194 -11.
195 -111. Use CoAP protocol to uplink data 
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/]]
196 196  
197 197  
198 -Note: if you don’t have CoAP server, you can refer this link to set up one:
196 +**Use below commands:**
199 199  
200 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
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
201 201  
202 +For parameter description, please refer to AT command set
202 202  
203 -Use below commands:
204 +[[image:1657249793983-486.png]]
204 204  
205 -* **AT+PRO=1**    ~/~/ Set to use CoAP protocol to uplink
206 -* **AT+SERVADDR=120.24.4.116,5683   **~/~/ to set CoAP server address and port
207 -* **AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0"       **~/~/Set COAP resource path
208 208  
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.
209 209  
210 -For parameter description, please refer to AT command set
209 +[[image:1657249831934-534.png]]
211 211  
212 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
213 213  
214 214  
215 -After configure the server address and **reset the device** (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
213 +=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
216 216  
217 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
215 +This feature is supported since firmware version v1.0.1
218 218  
219 -1.
220 -11.
221 -111. Use UDP protocol to uplink data(Default protocol)
222 222  
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
223 223  
224 -This feature is supported since firmware version v1.0.1
222 +[[image:1657249864775-321.png]]
225 225  
226 226  
227 -* **AT+PRO=2   ** ~/~/ Set to use UDP protocol to uplink
228 -* **AT+SERVADDR=120.24.4.116,5601   **~/~/ to set UDP server address and port
229 -* **AT+CFM=1       **~/~/If the server does not respond, this command is unnecessary
230 230  
231 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image015.jpg]]
226 +[[image:1657249930215-289.png]]
232 232  
233 233  
234 234  
230 +=== 2.2.6 Use MQTT protocol to uplink data ===
235 235  
232 +This feature is supported since firmware version v110
236 236  
237 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
238 238  
235 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
236 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
237 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
238 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
239 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
240 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
241 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
239 239  
240 -1.
241 -11.
242 -111. Use MQTT protocol to uplink data
243 +[[image:1657249978444-674.png]]
243 243  
244 244  
245 -This feature is supported since firmware version v110
246 +[[image:1657249990869-686.png]]
246 246  
247 247  
248 -* **AT+PRO=3   ** ~/~/Set to use MQTT protocol to uplink
249 -* **AT+SERVADDR=120.24.4.116,1883   **~/~/Set MQTT server address and port
250 -* **AT+CLIENT=CLIENT **~/~/Set up the CLIENT of MQTT
251 -* **AT+UNAME=UNAME                           **~/~/Set the username of MQTT
252 -* **AT+PWD=PWD                                      **~/~/Set the password of MQTT
253 -* **AT+PUBTOPIC=NSE01_PUB   **~/~/Set the sending topic of MQTT
254 -* **AT+SUBTOPIC=NSE01_SUB    **~/~/Set the subscription topic of MQTT
255 255  
250 +(((
251 +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.
252 +)))
256 256  
257 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
258 258  
259 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
260 260  
256 +=== 2.2.7 Use TCP protocol to uplink data ===
261 261  
262 -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.
258 +This feature is supported since firmware version v110
263 263  
264 264  
265 -1.
266 -11.
267 -111. Use TCP protocol to uplink data
261 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
262 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
268 268  
264 +[[image:1657250217799-140.png]]
269 269  
270 -This feature is supported since firmware version v110
271 271  
267 +[[image:1657250255956-604.png]]
272 272  
273 -* **AT+PRO=4   ** ~/~/ Set to use TCP protocol to uplink
274 -* **AT+SERVADDR=120.24.4.116,5600   **~/~/ to set TCP server address and port
275 275  
276 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
270 +=== 2.2.8 Change Update Interval ===
277 277  
272 +User can use below command to change the (% style="color:green" %)**uplink interval**.
278 278  
274 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
279 279  
280 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
276 +(((
277 +(% style="color:red" %)**NOTE:**
278 +)))
281 281  
280 +(((
281 +(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
282 +)))
282 282  
283 -1.
284 -11.
285 -111. Change Update Interval
286 286  
287 -User can use below command to change the **uplink interval**.
288 288  
289 -**~ AT+TDC=600      **~/~/ Set Update Interval to 600s
286 +== 2.3  Uplink Payload ==
290 290  
288 +In this mode, uplink payload includes in total 18 bytes
291 291  
292 -**NOTE:**
290 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
291 +|=(% style="width: 50px;" %)(((
292 +**Size(bytes)**
293 +)))|=(% 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**
294 +|(% 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"]]
293 293  
294 -1. By default, the device will send an uplink message every 1 hour.
296 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
295 295  
296 296  
299 +[[image:image-20220708111918-4.png]]
297 297  
298 298  
302 +The payload is ASCII string, representative same HEX:
299 299  
304 +0x72403155615900640c7817075e0a8c02f900 where:
300 300  
306 +* Device ID: 0x 724031556159 = 724031556159
307 +* Version: 0x0064=100=1.0.0
301 301  
302 -== 2.3 Uplink Payload ==
309 +* BAT: 0x0c78 = 3192 mV = 3.192V
310 +* Singal: 0x17 = 23
311 +* Soil Moisture: 0x075e= 1886 = 18.86  %
312 +* Soil Temperature:0x0a8c =2700=27 °C
313 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
314 +* Interrupt: 0x00 = 0
303 303  
304 304  
305 -=== 2.3.1 MOD~=0(Default Mode) ===
306 306  
307 -LSE01 will uplink payload via LoRaWAN with below payload format: 
318 +== 2.4  Payload Explanation and Sensor Interface ==
308 308  
309 -(((
310 -Uplink payload includes in total 11 bytes.
311 -)))
320 +2.4.1  Device ID
312 312  
313 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
314 -|(((
315 -**Size**
322 +By default, the Device ID equal to the last 6 bytes of IMEI.
316 316  
317 -**(bytes)**
318 -)))|**2**|**2**|**2**|**2**|**2**|**1**
319 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
320 -Temperature
324 +User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
321 321  
322 -(Reserve, Ignore now)
323 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]]|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]]|(((
324 -MOD & Digital Interrupt
326 +**Example:**
325 325  
326 -(Optional)
327 -)))
328 +AT+DEUI=A84041F15612
328 328  
329 -=== 2.3.2 MOD~=1(Original value) ===
330 +The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
330 330  
331 -This mode can get the original AD value of moisture and original conductivity (with temperature drift compensation).
332 332  
333 -(% border="1" cellspacing="10" style="background-color:#ffffcc; width:500px" %)
334 -|(((
335 -**Size**
333 +2.4.2  Version Info
336 336  
337 -**(bytes)**
338 -)))|**2**|**2**|**2**|**2**|**2**|**1**
339 -|**Value**|[[BAT>>||anchor="H2.3.3BatteryInfo"]]|(((
340 -Temperature
335 +Specify the software version: 0x64=100, means firmware version 1.00.
341 341  
342 -(Reserve, Ignore now)
343 -)))|[[Soil Moisture>>||anchor="H2.3.4SoilMoisture"]](raw)|[[Soil Temperature>>||anchor="H2.3.5SoilTemperature"]]|[[Soil Conductivity (EC)>>||anchor="H2.3.6SoilConductivity28EC29"]](raw)|(((
344 -MOD & Digital Interrupt
337 +For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
345 345  
346 -(Optional)
347 -)))
348 348  
340 +
349 349  === 2.3.3 Battery Info ===
350 350  
351 351  (((
1657249419225-449.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +81.0 KB
Content
1657249468462-536.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +483.6 KB
Content
1657249793983-486.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +85.8 KB
Content
1657249831934-534.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +72.5 KB
Content
1657249864775-321.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +87.0 KB
Content
1657249930215-289.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +77.3 KB
Content
1657249978444-674.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +139.5 KB
Content
1657249990869-686.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +96.9 KB
Content
1657250217799-140.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.7 KB
Content
1657250255956-604.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +99.0 KB
Content
image-20220708110657-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +251.7 KB
Content
image-20220708111918-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +38.8 KB
Content

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0