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

Summary

Details

Page properties
Content
... ... @@ -68,6 +68,7 @@
68 68  
69 69  
70 70  
71 +
71 71  == 1.3  Specification ==
72 72  
73 73  
... ... @@ -76,6 +76,7 @@
76 76  * Supply Voltage: 2.1v ~~ 3.6v
77 77  * Operating Temperature: -40 ~~ 85°C
78 78  
80 +
79 79  (% style="color:#037691" %)**NB-IoT Spec:**
80 80  
81 81  * - B1 @H-FDD: 2100MHz
... ... @@ -85,6 +85,7 @@
85 85  * - B20 @H-FDD: 800MHz
86 86  * - B28 @H-FDD: 700MHz
87 87  
90 +
88 88  (% style="color:#037691" %)**Battery:**
89 89  
90 90  * Li/SOCI2 un-chargeable battery
... ... @@ -95,6 +95,7 @@
95 95  
96 96  
97 97  
101 +
98 98  == ​1.4  Applications ==
99 99  
100 100  * Smart Buildings & Home Automation
... ... @@ -108,7 +108,7 @@
108 108  ​
109 109  
110 110  
111 -== 1.5  Pin Definitions & Switch ==
115 +== 1.5  Pin Definitions ==
112 112  
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
... ... @@ -148,6 +148,7 @@
148 148  
149 149  
150 150  
155 +
151 151  = 2.  Use N95S31B to communicate with IoT Server =
152 152  
153 153  == 2.1  How it works ==
... ... @@ -166,7 +166,7 @@
166 166  
167 167  )))
168 168  
169 -[[image:1657520100595-569.png]]
174 +[[image:1657350248151-650.png]]
170 170  
171 171  (((
172 172  
... ... @@ -185,45 +185,23 @@
185 185  === 2.2.1 Test Requirement ===
186 186  
187 187  
188 -(((
189 189  To use N95S31B in your city, make sure meet below requirements:
190 -)))
191 191  
192 -* (((
193 -Your local operator has already distributed a NB-IoT Network there.
194 -)))
195 -* (((
196 -The local NB-IoT network used the band that N95S31B supports.
197 -)))
198 -* (((
199 -Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
200 -)))
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.
201 201  
202 -(((
203 203  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
204 -)))
205 205  
206 -(((
207 207  N95S31B supports different communication protocol such as :
208 -)))
209 209  
210 210  (((
211 -* (((
212 -CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
213 -)))
214 -* (((
215 -raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
216 -)))
217 -* (((
218 -MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
219 -)))
220 -* (((
221 -TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
222 -)))
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(%%))
223 223  
224 -(((
225 225  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.
226 -)))
227 227  
228 228  
229 229  )))
... ... @@ -393,49 +393,28 @@
393 393  == 2.3  Uplink Payload ==
394 394  
395 395  
396 -(((
397 -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.
398 -)))
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.
399 399  
400 400  
401 -(((
402 402  For example:
403 -)))
404 404  
405 -(((
406 - (% 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.
407 -)))
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.
408 408  
409 409  
410 -(((
411 411  The uplink payloads are composed in  ASCII String. For example:
412 -)))
413 413  
414 -(((
415 415  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
416 -)))
417 417  
418 -(((
419 419  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
420 -)))
421 421  
422 422  
423 -(((
424 424  (% style="color:red" %)**NOTE:**
425 -)))
426 426  
427 427  (% style="color:red" %)
428 -1. (((
429 -All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
430 -)))
431 -1. (((
432 -By default, the device will send an uplink message every 1 hour.
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.
433 433  
434 434  
435 -
436 -
437 -)))
438 -
439 439  === 2.3.1  Payload Analyze ===
440 440  
441 441  N95S31B uplink payload includes in total 21 bytes
... ... @@ -528,25 +528,15 @@
528 528  
529 529  === 2.3.3  Version Info ===
530 530  
531 -(((
493 +
532 532  These bytes include the hardware and software version.
533 -)))
534 534  
535 -(((
536 536  Higher byte: Specify hardware version: always 0x00 for N95S31B
537 -)))
538 538  
539 -(((
540 540  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
541 -)))
542 542  
543 -(((
544 -
545 -)))
546 546  
547 -(((
548 548  For example: 0x00 6E: this device is N95S31B with firmware version 110.
549 -)))
550 550  
551 551  (((
552 552  
... ... @@ -617,7 +617,7 @@
617 617  
618 618  == 2.4  Downlink Payload ==
619 619  
620 -By default, N95S31B prints the downlink payload to console port.
572 +By default, NDDS75 prints the downlink payload to console port.
621 621  
622 622  [[image:image-20220709100028-1.png]]
623 623  
... ... @@ -655,7 +655,7 @@
655 655  )))
656 656  
657 657  (((
658 -If payload = 0x04FF, it will reset the N95S31B
610 +If payload = 0x04FF, it will reset the NDDS75
659 659  )))
660 660  
661 661  
... ... @@ -835,10 +835,8 @@
835 835  (((
836 836  
837 837  
838 -(((
839 839  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
840 840  )))
841 -)))
842 842  
843 843  
844 844  
1657520100595-569.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -126.1 KB
Content

Applications

Navigation

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