Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 57.4 >
edited by Xiaoling
on 2022/07/08 11:40
To version < 45.6 >
edited by Xiaoling
on 2022/07/08 10:57
>
Change comment: There is no comment for this version

Summary

Details

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

Applications

Navigation

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