Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 1 removed)
  • 1657520100595-569.png

Details

Page properties

Content

...	...	@@ -68,6 +68,7 @@
68	68
69	69
70	70
	71	+
71	71	== 1.3  Specification ==
72	72
73	73
...	...	@@ -87,6 +87,7 @@
87	87
88	88	(% style="color:#037691" %)**Battery:**
89	89
	91	+
90	90	* Li/SOCI2 un-chargeable battery
91	91	* Capacity: 8500mAh
92	92	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -93,8 +93,6 @@
93	93	* Max continuously current: 130mA
94	94	* Max boost current: 2A, 1 second
95	95
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 & Switch ==
	111	+== 1.5  Pin Definitions ==
112	112
113	113	N95S31B use the mother board from NBSN95 which as below.
114	114
...	...	@@ -123,13 +123,9 @@
123	123
124	124	=== 1.5.2 BOOT MODE / SW1 ===
125	125
126		-(((
127	127	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		-)))
129	129
130		-(((
131	131	2) Flash: work mode, device starts to work and send out console output for further debug
132		-)))
133	133
134	134
135	135
...	...	@@ -146,8 +146,6 @@
146	146	1. When boot the device in flash mode
147	147	1. Send an uplink packet
148	148
149		-
150		-
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]]
	163	+[[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		-)))
	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.
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		-)))
	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(%%))
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,45 +393,28 @@
393	393	== 2.3  Uplink Payload ==
394	394
395	395
396		-(((
397	397	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.
398		-)))
399	399
400	400
401		-(((
402	402	For example:
403		-)))
404	404
405		-(((
406	406	(% 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.
407		-)))
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.
433		-)))
	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.
434	434
	389	+
435	435	=== 2.3.1  Payload Analyze ===
436	436
437	437	N95S31B uplink payload includes in total 21 bytes
...	...	@@ -524,25 +524,15 @@
524	524
525	525	=== 2.3.3  Version Info ===
526	526
527		-(((
	482	+
528	528	These bytes include the hardware and software version.
529		-)))
530	530
531		-(((
532	532	Higher byte: Specify hardware version: always 0x00 for N95S31B
533		-)))
534	534
535		-(((
536	536	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
537		-)))
538	538
539		-(((
540		-
541		-)))
542	542
543		-(((
544	544	For example: 0x00 6E: this device is N95S31B with firmware version 110.
545		-)))
546	546
547	547	(((
548	548
...	...	@@ -831,10 +831,8 @@
831	831	(((
832	832
833	833
834		-(((
835	835	(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
836	836	)))
837		-)))
838	838
839	839
840	840

1657520100595-569.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.Xiaoling

Size

...	...	@@ -1,1 +1,0 @@
1		-126.1 KB

Content