Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 100.2 >
edited by Xiaoling
on 2022/07/09 14:53
To version < 111.2 >
edited by Xiaoling
on 2022/07/09 15:45
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -137,13 +137,14 @@
137 137  
138 138  == 2.1  How it works ==
139 139  
140 +
140 140  (((
141 -The NDDS75 is equipped with a NB-IoT module, the pre-loaded firmware in NDDS75 will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module.  The NB-IoT network will forward this value to IoT server via the protocol defined by NDDS75.
142 +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.
142 142  )))
143 143  
144 144  
145 145  (((
146 -The diagram below shows the working flow in default firmware of NDDS75:
147 +The diagram below shows the working flow in default firmware of N95S31B:
147 147  )))
148 148  
149 149  (((
... ... @@ -150,7 +150,7 @@
150 150  
151 151  )))
152 152  
153 -[[image:1657328659945-416.png]]
154 +[[image:1657350248151-650.png]]
154 154  
155 155  (((
156 156  
... ... @@ -157,30 +157,46 @@
157 157  )))
158 158  
159 159  
160 -== 2.2 ​ Configure the NDDS75 ==
161 +== 2.2 ​ Configure the N95S31B ==
161 161  
162 162  
164 +=== 2.2.1  Power On N95S31B ===
165 +
166 +
167 +[[image:image-20220709150546-2.png]]
168 +
169 +
163 163  === 2.2.1 Test Requirement ===
164 164  
165 -(((
166 -To use NDDS75 in your city, make sure meet below requirements:
167 -)))
168 168  
173 +To use N95S31B in your city, make sure meet below requirements:
174 +
169 169  * Your local operator has already distributed a NB-IoT Network there.
170 -* The local NB-IoT network used the band that NSE01 supports.
176 +* The local NB-IoT network used the band that N95S31B supports.
171 171  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
172 172  
179 +
180 +Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181 +
182 +N95S31B supports different communication protocol such as :
183 +
173 173  (((
174 -Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.  The NDDS75 will use CoAP((% style="color:red" %)120.24.4.116:5683)(%%) or raw UDP((% style="color:red" %)120.24.4.116:5601)(%%) or MQTT((% style="color:red" %)120.24.4.116:1883)(%%)or TCP((% style="color:red" %)120.24.4.116:5600)(%%)protocol to send data to the test server
175 -)))
185 +* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
186 +* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
187 +* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
188 +* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
176 176  
190 +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.
177 177  
178 -[[image:1657328756309-230.png]]
192 +
193 +)))
179 179  
195 +[[image:1657350625843-586.png]]
180 180  
181 181  
182 -=== 2.2.2 Insert SIM card ===
183 183  
199 +=== 2.2.3  Insert SIM card ===
200 +
184 184  (((
185 185  Insert the NB-IoT Card get from your provider.
186 186  )))
... ... @@ -190,19 +190,19 @@
190 190  )))
191 191  
192 192  
193 -[[image:1657328884227-504.png]]
210 +[[image:1657351240556-536.png]]
194 194  
195 195  
196 196  
197 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
214 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
198 198  
199 199  (((
200 200  (((
201 -User need to configure NDDS75 via serial port to set the (% style="color:blue" %)**Server Address** / **Uplink Topic** (%%)to define where and how-to uplink packets. NDDS75 support AT Commands, user can use a USB to TTL adapter to connect to NDDS75 and use AT Commands to configure it, as below.
218 +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.
202 202  )))
203 203  )))
204 204  
205 -[[image:image-20220709092052-2.png]]
222 +[[image:1657351312545-300.png]]
206 206  
207 207  **Connection:**
208 208  
... ... @@ -222,18 +222,18 @@
222 222  * Flow Control: (% style="color:green" %)**None**
223 223  
224 224  (((
225 -Make sure the switch is in FLASH position, then power on device by connecting the jumper on NDDS75. NDDS75 will output system info once power on as below, we can enter the (% style="color:green" %)**password: 12345678**(%%) to access AT Command input.
242 +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.
226 226  )))
227 227  
228 228  [[image:1657329814315-101.png]]
229 229  
230 230  (((
231 -(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NDDS75/]]
248 +(% 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/]]
232 232  )))
233 233  
234 234  
235 235  
236 -=== 2.2.4 Use CoAP protocol to uplink data ===
253 +=== 2.2.5  Use CoAP protocol to uplink data ===
237 237  
238 238  (% 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/]]
239 239  
... ... @@ -253,10 +253,12 @@
253 253  )))
254 254  
255 255  (((
273 +
274 +
256 256  For parameter description, please refer to AT command set
257 257  )))
258 258  
259 -[[image:1657330452568-615.png]]
278 +[[image:1657352146020-183.png]]
260 260  
261 261  
262 262  (((
... ... @@ -263,11 +263,11 @@
263 263  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.
264 264  )))
265 265  
266 -[[image:1657330472797-498.png]]
285 +[[image:1657352185396-303.png]]
267 267  
268 268  
269 269  
270 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
289 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
271 271  
272 272  
273 273  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -274,15 +274,16 @@
274 274  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
275 275  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
276 276  
277 -[[image:1657330501006-241.png]]
296 +[[image:1657352391268-297.png]]
278 278  
279 279  
280 -[[image:1657330533775-472.png]]
299 +[[image:1657352403317-397.png]]
281 281  
282 282  
283 283  
284 -=== 2.2.6 Use MQTT protocol to uplink data ===
303 +=== 2.2.7  Use MQTT protocol to uplink data ===
285 285  
305 +N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption.
286 286  
287 287  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
288 288  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -289,17 +289,21 @@
289 289  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
290 290  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
291 291  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
292 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
293 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic of MQTT
312 +* (% style="color:blue" %)**AT+PUBTOPIC=f9527  **(%%)~/~/Set the sending topic of MQTT
313 +* (% style="color:blue" %)**AT+SUBTOPIC=Ns9527  **(%%) ~/~/Set the subscription topic of MQTT
294 294  
295 -[[image:1657249978444-674.png]]
315 +[[image:1657352634421-276.png]]
296 296  
297 297  
298 -[[image:1657330723006-866.png]]
318 +[[image:1657352645687-385.png]]
299 299  
320 +(((
321 +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.
322 +)))
300 300  
324 +
301 301  (((
302 -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.
326 +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.
303 303  )))
304 304  
305 305  
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
image-20220709150546-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +333.5 KB
Content

Applications

Navigation

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