Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 46.1 >
edited by Xiaoling
on 2022/07/08 11:03
To version < 57.2 >
edited by Xiaoling
on 2022/07/08 11:31
>
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,23 +147,24 @@
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  
163 -
164 -
165 -Connection:
166 -
167 167   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
168 168  
169 169   (% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
... ... @@ -171,129 +171,154 @@
171 171   (% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
172 172  
173 173  
174 -
175 175  In the PC, use below serial tool settings:
176 176  
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**
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 **(% style="background-color:green" %)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 +(% 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/]]
193 193  
194 -=== 2.2.4 Use CoAP protocol to uplink data === 
195 195  
196 +**Use below commands:**
196 196  
197 -(% style="background-color:red" %)Note: if you don’t have CoAP server, you can refer this link to set up one:
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
198 198  
199 -[[http:~~/~~/wiki.dragino.com/index.php?title=Set_up_CoAP_Server>>url:http://wiki.dragino.com/index.php?title=Set_up_CoAP_Server]]
200 200  
201 -
202 -Use below commands:
203 -
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
207 -
208 -
209 209  For parameter description, please refer to AT command set
210 210  
211 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image011.jpg]]
205 +[[image:1657249793983-486.png]]
212 212  
213 213  
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.
208 +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.
215 215  
216 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image013.jpg]]
210 +[[image:1657249831934-534.png]]
217 217  
218 218  
213 +
219 219  === 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
220 220  
221 -
222 222  This feature is supported since firmware version v1.0.1
223 223  
224 224  
225 -* **(% style="color:blue" %)AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
226 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
227 -* **(% style="color:blue" %)AT+CFM=1       ** (%%) ~/~/If the server does not respond, this command is unnecessary
219 +* (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
220 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
221 +* (% style="color:blue" %)**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]]
230 230  
224 +[[image:1657249864775-321.png]]
231 231  
232 232  
233 233  
228 +[[image:1657249930215-289.png]]
234 234  
235 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image017.jpg]]
236 236  
237 237  
238 238  === 2.2.6 Use MQTT protocol to uplink data ===
239 239  
240 -
241 241  This feature is supported since firmware version v110
242 242  
243 243  
244 -* **(% style="color:blue" %)AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
245 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
246 -* **(% style="color:blue" %)AT+CLIENT=CLIENT ** (%%)~/~/Set up the CLIENT of MQTT
247 -* **(% style="color:blue" %)AT+UNAME=UNAME            **(%%)~/~/Set the username of MQTT
248 -* **(% style="color:blue" %)AT+PWD=PWD                  **(%%)~/~/Set the password of MQTT
249 -* **(% style="color:blue" %)AT+PUBTOPIC=NSE01_PUB   **(%%)~/~/Set the sending topic of MQTT
250 -* **(% style="color:blue" %)AT+SUBTOPIC=NSE01_SUB    **(%%) ~/~/Set the subscription topic of MQTT
237 +* (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
238 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
239 +* (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
240 +* (% style="color:blue" %)**AT+UNAME=UNAME                               **(%%)~/~/Set the username of MQTT
241 +* (% style="color:blue" %)**AT+PWD=PWD                                        **(%%)~/~/Set the password of MQTT
242 +* (% style="color:blue" %)**AT+PUBTOPIC=NSE01_PUB                    **(%%)~/~/Set the sending topic of MQTT
243 +* (% style="color:blue" %)**AT+SUBTOPIC=NSE01_SUB          **(%%) ~/~/Set the subscription topic of MQTT
251 251  
252 252  
253 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image019.gif]]
246 +[[image:1657249978444-674.png]]
254 254  
255 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image021.jpg]]
256 256  
249 +[[image:1657249990869-686.png]]
257 257  
251 +
252 +
253 +(((
258 258  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.
255 +)))
259 259  
260 260  
258 +
261 261  === 2.2.7 Use TCP protocol to uplink data ===
262 262  
263 -
264 264  This feature is supported since firmware version v110
265 265  
266 266  
267 -* **(% style="color:blue" %)AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
268 -* **(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
264 +* (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
265 +* (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
269 269  
270 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image023.jpg]]
267 +[[image:1657250217799-140.png]]
271 271  
272 272  
270 +[[image:1657250255956-604.png]]
273 273  
274 -[[image:file:///C:/Users/93456/AppData/Local/Temp/msohtmlclip1/01/clip_image025.jpg]]
275 275  
276 -
277 277  === 2.2.8 Change Update Interval ===
278 278  
279 -User can use below command to change the **(% style="color:green" %)uplink interval**.
275 +User can use below command to change the (% style="color:green" %)**uplink interval**.
280 280  
281 -**~ (% style="color:blue" %)AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
277 +* (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
282 282  
279 +(((
280 +(% style="color:red" %)**NOTE:**
281 +)))
283 283  
284 -**(% style="color:red" %)NOTE:**
285 -
283 +(((
286 286  (% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
285 +)))
287 287  
288 288  
289 289  
289 +== 2.3  Uplink Payload ==
290 290  
291 +In this mode, uplink payload includes in total 18 bytes
291 291  
293 +(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
294 +|=(% style="width: 50px;" %)(((
295 +**Size(bytes)**
296 +)))|=(% 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**
297 +|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>path:#Device_ID]]|(% style="width:41px" %)[[Ver>>path:#Version]]|(% style="width:46px" %)[[BAT>>path:#battery]]|(% style="width:123px" %)[[Signal Strength>>path:#Signal]]|(% style="width:108px" %)[[Soil Moisture>>path:#Payload_Explain]]|(% style="width:133px" %)[[Soil Temperature>>path:#Payload_Explain]]|(% style="width:159px" %)[[Soil Conductivity(EC)>>path:#Payload_Explain]]|(% style="width:80px" %)[[Interrupt>>path:#Interrupt]]
292 292  
299 +If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
293 293  
294 -== 2.3 Uplink Payload ==
295 295  
302 +[[image:image-20220708111918-4.png]]
296 296  
304 +
305 +The payload is ASCII string, representative same HEX:
306 +
307 +0x72403155615900640c7817075e0a8c02f900 where:
308 +
309 +* Device ID: 0x 724031556159 = 724031556159
310 +* Version: 0x0064=100=1.0.0
311 +
312 +* BAT: 0x0c78 = 3192 mV = 3.192V
313 +* Singal: 0x17 = 23
314 +* Soil Moisture: 0x075e= 1886 = 18.86  %
315 +* Soil Temperature:0x0a8c =2700=27 °C
316 +* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
317 +* Interrupt: 0x00 = 0
318 +
319 +
320 +
297 297  === 2.3.1 MOD~=0(Default Mode) ===
298 298  
299 299  LSE01 will uplink payload via LoRaWAN with below payload format: 
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-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0