Last modified by Mengting Qiu on 2024/04/02 16:44
<
From version < 115.30 >
edited by Xiaoling
on 2022/07/11 08:39
To version < 119.2 >
edited by Xiaoling
on 2022/08/22 14:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -17,6 +17,7 @@
17 17  
18 18  = 1.  Introduction =
19 19  
20 +
20 20  == 1.1 ​ What is N95S31B NB-IoT Sensor Node ==
21 21  
22 22  (((
... ... @@ -55,6 +55,7 @@
55 55  
56 56  == 1.2 ​ Features ==
57 57  
59 +
58 58  * NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
59 59  * Monitor Temperature & Humidity via SHT31
60 60  * AT Commands to change parameters
... ... @@ -78,6 +78,7 @@
78 78  * Operating Temperature: -40 ~~ 85°C
79 79  
80 80  
83 +
81 81  (% style="color:#037691" %)**NB-IoT Spec:**
82 82  
83 83  * - B1 @H-FDD: 2100MHz
... ... @@ -88,6 +88,7 @@
88 88  * - B28 @H-FDD: 700MHz
89 89  
90 90  
94 +
91 91  (% style="color:#037691" %)**Battery:**
92 92  
93 93  * Li/SOCI2 un-chargeable battery
... ... @@ -101,6 +101,7 @@
101 101  
102 102  == ​1.4  Applications ==
103 103  
108 +
104 104  * Smart Buildings & Home Automation
105 105  * Logistics and Supply Chain Management
106 106  * Smart Metering
... ... @@ -112,15 +112,20 @@
112 112  ​
113 113  
114 114  
115 -== 1.5  Pin Definitions ==
116 116  
121 +== 1.5  Pin Definitions & Switch ==
122 +
123 +
117 117  N95S31B use the mother board from NBSN95 which as below.
118 118  
126 +
119 119  [[image:image-20220709144723-1.png]]
120 120  
121 121  
130 +
122 122  === 1.5.1 Jumper JP2 ===
123 123  
133 +
124 124  Power on Device when put this jumper.
125 125  
126 126  
... ... @@ -127,6 +127,7 @@
127 127  
128 128  === 1.5.2 BOOT MODE / SW1 ===
129 129  
140 +
130 130  (((
131 131  1) ISP: upgrade mode, device won't have any signal in this mode. but ready for upgrade firmware. LED won't work. Firmware won't run.
132 132  )))
... ... @@ -139,6 +139,7 @@
139 139  
140 140  === 1.5.3 Reset Button ===
141 141  
153 +
142 142  Press to reboot the device.
143 143  
144 144  
... ... @@ -145,6 +145,7 @@
145 145  
146 146  === 1.5.4 LED ===
147 147  
160 +
148 148  It will flash:
149 149  
150 150  1. When boot the device in flash mode
... ... @@ -155,6 +155,7 @@
155 155  
156 156  = 2.  Use N95S31B to communicate with IoT Server =
157 157  
171 +
158 158  == 2.1  How it works ==
159 159  
160 160  
... ... @@ -171,7 +171,7 @@
171 171  
172 172  )))
173 173  
174 -[[image:1657350248151-650.png]]
188 +[[image:1657520100595-569.png]]
175 175  
176 176  (((
177 177  
... ... @@ -187,26 +187,49 @@
187 187  [[image:image-20220709150546-2.png]]
188 188  
189 189  
204 +
190 190  === 2.2.1 Test Requirement ===
191 191  
192 192  
208 +(((
193 193  To use N95S31B in your city, make sure meet below requirements:
210 +)))
194 194  
195 -* Your local operator has already distributed a NB-IoT Network there.
196 -* The local NB-IoT network used the band that N95S31B supports.
197 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
212 +* (((
213 +Your local operator has already distributed a NB-IoT Network there.
214 +)))
215 +* (((
216 +The local NB-IoT network used the band that N95S31B supports.
217 +)))
218 +* (((
219 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
220 +)))
198 198  
222 +(((
199 199  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
224 +)))
200 200  
226 +(((
201 201  N95S31B supports different communication protocol such as :
228 +)))
202 202  
203 203  (((
204 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
205 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
206 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
207 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
231 +* (((
232 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
233 +)))
234 +* (((
235 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
236 +)))
237 +* (((
238 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
239 +)))
240 +* (((
241 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
242 +)))
208 208  
244 +(((
209 209  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.
246 +)))
210 210  
211 211  
212 212  )))
... ... @@ -217,6 +217,7 @@
217 217  
218 218  === 2.2.3  Insert SIM card ===
219 219  
257 +
220 220  (((
221 221  Insert the NB-IoT Card get from your provider.
222 222  )))
... ... @@ -232,14 +232,18 @@
232 232  
233 233  === 2.2.4  Connect USB – TTL to N95S31B to configure it ===
234 234  
273 +
235 235  (((
236 236  (((
237 237  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.
277 +
278 +
238 238  )))
239 239  )))
240 240  
241 241  [[image:1657351312545-300.png]]
242 242  
284 +
243 243  **Connection:**
244 244  
245 245   (% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
... ... @@ -263,8 +263,9 @@
263 263  
264 264  [[image:1657329814315-101.png]]
265 265  
308 +
266 266  (((
267 -(% 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/]]
310 +(% style="color:red" %)**Note: the valid AT Commands can be found at:  **(%%)**[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]**
268 268  )))
269 269  
270 270  
... ... @@ -271,9 +271,10 @@
271 271  
272 272  === 2.2.5  Use CoAP protocol to uplink data ===
273 273  
274 -(% 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/]]
275 275  
318 +(% 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/]]**
276 276  
320 +
277 277  (((
278 278  **Use below commands:**
279 279  )))
... ... @@ -376,28 +376,49 @@
376 376  == 2.3  Uplink Payload ==
377 377  
378 378  
379 -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.
423 +(((
424 +N95S31B 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.
425 +)))
380 380  
381 381  
428 +(((
382 382  For example:
430 +)))
383 383  
384 - (% 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.
432 +(((
433 + (% style="color:blue" %)**AT+CFGMOD=2 ** (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
434 +)))
385 385  
386 386  
437 +(((
387 387  The uplink payloads are composed in  ASCII String. For example:
439 +)))
388 388  
441 +(((
389 389  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
443 +)))
390 390  
445 +(((
391 391  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
447 +)))
392 392  
393 393  
450 +(((
394 394  (% style="color:red" %)**NOTE:**
452 +)))
395 395  
396 396  (% style="color:red" %)
397 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
398 -1. By default, the device will send an uplink message every 1 hour.
455 +1. (((
456 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
457 +)))
458 +1. (((
459 +By default, the device will send an uplink message every 1 hour.
399 399  
400 400  
462 +
463 +
464 +)))
465 +
401 401  === 2.3.1  Payload Analyze ===
402 402  
403 403  N95S31B uplink payload includes in total 21 bytes
... ... @@ -490,15 +490,25 @@
490 490  
491 491  === 2.3.3  Version Info ===
492 492  
493 -
558 +(((
494 494  These bytes include the hardware and software version.
560 +)))
495 495  
562 +(((
496 496  Higher byte: Specify hardware version: always 0x00 for N95S31B
564 +)))
497 497  
566 +(((
498 498  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
568 +)))
499 499  
570 +(((
571 +
572 +)))
500 500  
574 +(((
501 501  For example: 0x00 6E: this device is N95S31B with firmware version 110.
576 +)))
502 502  
503 503  (((
504 504  
... ... @@ -569,7 +569,7 @@
569 569  
570 570  == 2.4  Downlink Payload ==
571 571  
572 -By default, NDDS75 prints the downlink payload to console port.
647 +By default, N95S31B prints the downlink payload to console port.
573 573  
574 574  [[image:image-20220709100028-1.png]]
575 575  
... ... @@ -607,7 +607,7 @@
607 607  )))
608 608  
609 609  (((
610 -If payload = 0x04FF, it will reset the NDDS75
685 +If payload = 0x04FF, it will reset the N95S31B
611 611  )))
612 612  
613 613  
... ... @@ -787,8 +787,10 @@
787 787  (((
788 788  
789 789  
865 +(((
790 790  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
791 791  )))
868 +)))
792 792  
793 793  
794 794  
1657520100595-569.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +126.1 KB
Content

Applications

Navigation

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