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

Summary

Details

Page properties
Content
... ... @@ -68,7 +68,6 @@
68 68  
69 69  
70 70  
71 -
72 72  == 1.3  Specification ==
73 73  
74 74  
... ... @@ -88,7 +88,6 @@
88 88  
89 89  (% style="color:#037691" %)**Battery:**
90 90  
91 -
92 92  * Li/SOCI2 un-chargeable battery
93 93  * Capacity: 8500mAh
94 94  * Self Discharge: <1% / Year @ 25°C
... ... @@ -95,6 +95,8 @@
95 95  * Max continuously current: 130mA
96 96  * Max boost current: 2A, 1 second
97 97  
96 +
97 +
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 ==
111 +== 1.5  Pin Definitions & Switch ==
112 112  
113 113  N95S31B use the mother board from NBSN95 which as below.
114 114  
... ... @@ -123,9 +123,13 @@
123 123  
124 124  === 1.5.2 BOOT MODE / SW1 ===
125 125  
126 +(((
126 126  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.
128 +)))
127 127  
130 +(((
128 128  2) Flash: work mode, device starts to work and send out console output for further debug
132 +)))
129 129  
130 130  
131 131  
... ... @@ -142,6 +142,7 @@
142 142  1. When boot the device in flash mode
143 143  1. Send an uplink packet
144 144  
149 +
145 145  = 2.  Use N95S31B to communicate with IoT Server =
146 146  
147 147  == 2.1  How it works ==
... ... @@ -160,7 +160,7 @@
160 160  
161 161  )))
162 162  
163 -[[image:1657350248151-650.png]]
168 +[[image:1657520100595-569.png]]
164 164  
165 165  (((
166 166  
... ... @@ -179,23 +179,45 @@
179 179  === 2.2.1 Test Requirement ===
180 180  
181 181  
187 +(((
182 182  To use N95S31B in your city, make sure meet below requirements:
189 +)))
183 183  
184 -* Your local operator has already distributed a NB-IoT Network there.
185 -* The local NB-IoT network used the band that N95S31B supports.
186 -* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
191 +* (((
192 +Your local operator has already distributed a NB-IoT Network there.
193 +)))
194 +* (((
195 +The local NB-IoT network used the band that N95S31B supports.
196 +)))
197 +* (((
198 +Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
199 +)))
187 187  
201 +(((
188 188  Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
203 +)))
189 189  
205 +(((
190 190  N95S31B supports different communication protocol such as :
207 +)))
191 191  
192 192  (((
193 -* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
194 -* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
195 -* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
196 -* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
210 +* (((
211 +CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
212 +)))
213 +* (((
214 +raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
215 +)))
216 +* (((
217 +MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
218 +)))
219 +* (((
220 +TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
221 +)))
197 197  
223 +(((
198 198  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.
225 +)))
199 199  
200 200  
201 201  )))
... ... @@ -365,28 +365,49 @@
365 365  == 2.3  Uplink Payload ==
366 366  
367 367  
368 -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.
395 +(((
396 +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.
397 +)))
369 369  
370 370  
400 +(((
371 371  For example:
402 +)))
372 372  
373 - (% 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.
404 +(((
405 + (% 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.
406 +)))
374 374  
375 375  
409 +(((
376 376  The uplink payloads are composed in  ASCII String. For example:
411 +)))
377 377  
413 +(((
378 378  0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
415 +)))
379 379  
417 +(((
380 380  0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
419 +)))
381 381  
382 382  
422 +(((
383 383  (% style="color:red" %)**NOTE:**
424 +)))
384 384  
385 385  (% style="color:red" %)
386 -1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
387 -1. By default, the device will send an uplink message every 1 hour.
427 +1. (((
428 +All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
429 +)))
430 +1. (((
431 +By default, the device will send an uplink message every 1 hour.
388 388  
389 389  
434 +
435 +
436 +)))
437 +
390 390  === 2.3.1  Payload Analyze ===
391 391  
392 392  N95S31B uplink payload includes in total 21 bytes
... ... @@ -479,15 +479,25 @@
479 479  
480 480  === 2.3.3  Version Info ===
481 481  
482 -
530 +(((
483 483  These bytes include the hardware and software version.
532 +)))
484 484  
534 +(((
485 485  Higher byte: Specify hardware version: always 0x00 for N95S31B
536 +)))
486 486  
538 +(((
487 487  Lower byte: Specify the software version: 0x6E=110, means firmware version 110
540 +)))
488 488  
542 +(((
543 +
544 +)))
489 489  
546 +(((
490 490  For example: 0x00 6E: this device is N95S31B with firmware version 110.
548 +)))
491 491  
492 492  (((
493 493  
... ... @@ -558,7 +558,7 @@
558 558  
559 559  == 2.4  Downlink Payload ==
560 560  
561 -By default, NDDS75 prints the downlink payload to console port.
619 +By default, N95S31B prints the downlink payload to console port.
562 562  
563 563  [[image:image-20220709100028-1.png]]
564 564  
... ... @@ -596,7 +596,7 @@
596 596  )))
597 597  
598 598  (((
599 -If payload = 0x04FF, it will reset the NDDS75
657 +If payload = 0x04FF, it will reset the N95S31B
600 600  )))
601 601  
602 602  
... ... @@ -776,8 +776,10 @@
776 776  (((
777 777  
778 778  
837 +(((
779 779  (% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
780 780  )))
840 +)))
781 781  
782 782  
783 783  
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