Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 113.1 >
edited by Xiaoling
on 2022/07/09 15:48
To version < 115.1 >
edited by Xiaoling
on 2022/07/09 16:17
>
Change comment: Uploaded new attachment "image-20220709161741-3.png", version {1}

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 ==
... ... @@ -176,7 +176,6 @@
176 176  * The local NB-IoT network used the band that N95S31B supports.
177 177  * Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
178 178  
179 -
180 180  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
181 181  
182 182  N95S31B supports different communication protocol such as :
... ... @@ -302,7 +302,7 @@
302 302  
303 303  === 2.2.7  Use MQTT protocol to uplink data ===
304 304  
305 -N95S31B supports only plain MQTT now it doesn’t support TLS and other related encryption.
301 +N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
306 306  
307 307  * (% style="color:blue" %)**AT+PRO=3   ** (%%) ~/~/Set to use MQTT protocol to uplink
308 308  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,1883   ** (%%) ~/~/Set MQTT server address and port
... ... @@ -309,8 +309,8 @@
309 309  * (% style="color:blue" %)**AT+CLIENT=CLIENT       ** (%%)~/~/Set up the CLIENT of MQTT
310 310  * (% style="color:blue" %)**AT+UNAME=UNAME                                **(%%)~/~/Set the username of MQTT
311 311  * (% style="color:blue" %)**AT+PWD=PWD                                         **(%%)~/~/Set the password 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
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
314 314  
315 315  [[image:1657352634421-276.png]]
316 316  
... ... @@ -328,20 +328,21 @@
328 328  
329 329  
330 330  
331 -=== 2.2.7 Use TCP protocol to uplink data ===
327 +=== 2.2.8  Use TCP protocol to uplink data ===
332 332  
329 +This feature is supported since firmware version v110
333 333  
334 334  * (% style="color:blue" %)**AT+PRO=4   ** (%%) ~/~/ Set to use TCP protocol to uplink
335 335  * (% style="color:blue" %)**AT+SERVADDR=120.24.4.116,5600   **(%%) ~/~/ to set TCP server address and port
336 336  
337 -[[image:image-20220709093918-1.png]]
334 +[[image:1657352898400-901.png]]
338 338  
339 339  
340 -[[image:image-20220709093918-2.png]]
337 +[[image:1657352914475-252.png]]
341 341  
342 342  
343 343  
344 -=== 2.2.8 Change Update Interval ===
341 +=== 2.2.9  Change Update Interval ===
345 345  
346 346  User can use below command to change the (% style="color:green" %)**uplink interval**.
347 347  
... ... @@ -348,32 +348,69 @@
348 348  * (% style="color:blue" %)**AT+TDC=600      ** (%%)~/~/ Set Update Interval to 600s
349 349  
350 350  (((
351 -(% style="color:red" %)**NOTE:**
348 +
352 352  )))
353 353  
354 -(((
355 -(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
356 -)))
357 357  
358 358  
359 -
360 360  == 2.3  Uplink Payload ==
361 361  
362 -In this mode, uplink payload includes in total 14 bytes
363 363  
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.
364 364  
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 +
365 365  (% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
366 366  |=(% style="width: 60px;" %)(((
367 367  **Size(bytes)**
368 -)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 100px;" %)**2**|=(% style="width: 60px;" %)**1**
369 -|(% 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
370 370  
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 +
371 371  (((
372 -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.
373 373  )))
407 +)))
374 374  
375 375  
376 -[[image:1657331036973-987.png]]
410 +[[image:1657354294009-643.png]]
377 377  
378 378  (((
379 379  The payload is ASCII string, representative same HEX:
1657354294009-643.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +214.7 KB
Content
image-20220709161741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +111.2 KB
Content

Applications

Navigation

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