Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 102.1 >
edited by Xiaoling
on 2022/07/09 15:05
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
Content
... ... @@ -54,7 +54,6 @@
54 54  * 8500mAh Battery for long term use
55 55  
56 56  
57 -
58 58  == 1.3  Specification ==
59 59  
60 60  
... ... @@ -82,7 +82,6 @@
82 82  * Max boost current: 2A, 1 second
83 83  
84 84  
85 -
86 86  == ​1.4  Applications ==
87 87  
88 88  * Smart Buildings & Home Automation
... ... @@ -132,7 +132,6 @@
132 132  
133 133  
134 134  
135 -
136 136  = 2.  Use N95S31B to communicate with IoT Server =
137 137  
138 138  == 2.1  How it works ==
... ... @@ -151,7 +151,7 @@
151 151  
152 152  )))
153 153  
154 -[[image:1657328659945-416.png]]
151 +[[image:1657350248151-650.png]]
155 155  
156 156  (((
157 157  
... ... @@ -158,30 +158,45 @@
158 158  )))
159 159  
160 160  
161 -== 2.2 ​ Configure the NDDS75 ==
158 +== 2.2 ​ Configure the N95S31B ==
162 162  
163 163  
161 +=== 2.2.1  Power On N95S31B ===
162 +
163 +
164 +[[image:image-20220709150546-2.png]]
165 +
166 +
164 164  === 2.2.1 Test Requirement ===
165 165  
166 -(((
167 -To use NDDS75 in your city, make sure meet below requirements:
168 -)))
169 169  
170 +To use N95S31B in your city, make sure meet below requirements:
171 +
170 170  * Your local operator has already distributed a NB-IoT Network there.
171 -* The local NB-IoT network used the band that NSE01 supports.
173 +* The local NB-IoT network used the band that N95S31B supports.
172 172  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
173 173  
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 +
174 174  (((
175 -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
176 -)))
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(%%))
177 177  
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.
178 178  
179 -[[image:1657328756309-230.png]]
188 +
189 +)))
180 180  
191 +[[image:1657350625843-586.png]]
181 181  
182 182  
183 -=== 2.2.2 Insert SIM card ===
184 184  
195 +=== 2.2.3  Insert SIM card ===
196 +
185 185  (((
186 186  Insert the NB-IoT Card get from your provider.
187 187  )))
... ... @@ -191,19 +191,19 @@
191 191  )))
192 192  
193 193  
194 -[[image:1657328884227-504.png]]
206 +[[image:1657351240556-536.png]]
195 195  
196 196  
197 197  
198 -=== 2.2.3 Connect USB – TTL to NDDS75 to configure it ===
210 +=== 2.2.4  Connect USB – TTL to N95S31B to configure it ===
199 199  
200 200  (((
201 201  (((
202 -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.
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.
203 203  )))
204 204  )))
205 205  
206 -[[image:image-20220709092052-2.png]]
218 +[[image:1657351312545-300.png]]
207 207  
208 208  **Connection:**
209 209  
... ... @@ -223,18 +223,18 @@
223 223  * Flow Control: (% style="color:green" %)**None**
224 224  
225 225  (((
226 -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.
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.
227 227  )))
228 228  
229 229  [[image:1657329814315-101.png]]
230 230  
231 231  (((
232 -(% 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/]]
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/]]
233 233  )))
234 234  
235 235  
236 236  
237 -=== 2.2.4 Use CoAP protocol to uplink data ===
249 +=== 2.2.5  Use CoAP protocol to uplink data ===
238 238  
239 239  (% 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/]]
240 240  
... ... @@ -254,10 +254,12 @@
254 254  )))
255 255  
256 256  (((
269 +
270 +
257 257  For parameter description, please refer to AT command set
258 258  )))
259 259  
260 -[[image:1657330452568-615.png]]
274 +[[image:1657352146020-183.png]]
261 261  
262 262  
263 263  (((
... ... @@ -264,11 +264,11 @@
264 264  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.
265 265  )))
266 266  
267 -[[image:1657330472797-498.png]]
281 +[[image:1657352185396-303.png]]
268 268  
269 269  
270 270  
271 -=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
285 +=== 2.2.6  Use UDP protocol to uplink data(Default protocol) ===
272 272  
273 273  
274 274  * (% style="color:blue" %)**AT+PRO=2   ** (%%) ~/~/ Set to use UDP protocol to uplink
... ... @@ -275,15 +275,16 @@
275 275  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5601   ** (%%) ~/~/ to set UDP server address and port
276 276  * (% style="color:blue" %)**AT+CFM=1       ** (%%) ~/~/ If the server does not respond, this command is unnecessary
277 277  
278 -[[image:1657330501006-241.png]]
292 +[[image:1657352391268-297.png]]
279 279  
280 280  
281 -[[image:1657330533775-472.png]]
295 +[[image:1657352403317-397.png]]
282 282  
283 283  
284 284  
285 -=== 2.2.6 Use MQTT protocol to uplink data ===
299 +=== 2.2.7  Use MQTT protocol to uplink data ===
286 286  
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
287 287  
288 288  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
289 289  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -290,35 +290,40 @@
290 290  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
291 291  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
292 292  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password of MQTT
293 -* (% style="color:blue" %)**AT+PUBTOPIC=NDDS75_PUB                 **(%%)~/~/Set the sending topic of MQTT
294 -* (% style="color:blue" %)**AT+SUBTOPIC=NDDS75_SUB          **(%%) ~/~/Set the subscription topic 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
295 295  
296 -[[image:1657249978444-674.png]]
311 +[[image:1657352634421-276.png]]
297 297  
298 298  
299 -[[image:1657330723006-866.png]]
314 +[[image:1657352645687-385.png]]
300 300  
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 +)))
301 301  
320 +
302 302  (((
303 -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.
304 304  )))
305 305  
306 306  
307 307  
308 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
309 309  
329 +This feature is supported since firmware version v110
310 310  
311 311  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
312 312  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
313 313  
314 -[[image:image-20220709093918-1.png]]
334 +[[image:1657352898400-901.png]]
315 315  
316 316  
317 -[[image:image-20220709093918-2.png]]
337 +[[image:1657352914475-252.png]]
318 318  
319 319  
320 320  
321 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
322 322  
323 323  User can use below command to change the (% style="color:green" %)**uplink interval**.
324 324  
... ... @@ -325,32 +325,69 @@
325 325  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
326 326  
327 327  (((
328 -(% style="color:red" %)**NOTE:**
348 +
329 329  )))
330 330  
331 -(((
332 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
333 -)))
334 334  
335 335  
336 -
337 337  == 2.3  Uplink Payload ==
338 338  
339 -In this mode, uplink payload includes in total 14 bytes
340 340  
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.
341 341  
358 +
359 +For example:
360 +
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.
362 +
363 +
364 +The uplink payloads are composed in  ASCII String. For example:
365 +
366 +0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
367 +
368 +0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
369 +
370 +
371 +(% style="color:red" %)**NOTE:**
372 +
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.
376 +
377 +
378 +
379 +
380 +=== 2.3.1  Payload Analyze ===
381 +
382 +N95S31B uplink payload includes in total 21 bytes
383 +
384 +
342 342  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
343 343  |=(% style="width: 60px;" %)(((
344 344  **Size(bytes)**
345 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
346 -|(% 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:120px" %)[[Distance (unit: mm)>>||anchor="H2.4.5A0Distance"]]|(% style="width:80px" %)[[Interrupt>>||anchor="H2.4.6A0DigitalInterrupt"]]
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
347 347  
392 +No function here.
393 +)))|(% style="width:77px" %)(((
394 +[[Temperature >>||anchor="H2.4.5A0Distance"]]
395 +
396 +By SHT31
397 +)))|(% style="width:80px" %)(((
398 +[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
399 +
400 +By SHT31
401 +)))
402 +
348 348  (((
349 -If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NDDS751 uplink data.
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.
350 350  )))
407 +)))
351 351  
352 352  
353 -[[image:1657331036973-987.png]]
410 +[[image:1657354294009-643.png]]
354 354  
355 355  (((
356 356  The payload is ASCII string, representative same HEX:
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

Applications

Navigation

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