Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -67,8 +67,6 @@
67	67	* 8500mAh Battery for long term use
68	68
69	69
70		-
71		-
72	72	== 1.3  Specification ==
73	73
74	74
...	...	@@ -77,7 +77,6 @@
77	77	* Supply Voltage: 2.1v ~~ 3.6v
78	78	* Operating Temperature: -40 ~~ 85°C
79	79
80		-
81	81	(% style="color:#037691" %)**NB-IoT Spec:**
82	82
83	83	* - B1 @H-FDD: 2100MHz
...	...	@@ -87,7 +87,6 @@
87	87	* - B20 @H-FDD: 800MHz
88	88	* - B28 @H-FDD: 700MHz
89	89
90		-
91	91	(% style="color:#037691" %)**Battery:**
92	92
93	93	* Li/SOCI2 un-chargeable battery
...	...	@@ -97,8 +97,6 @@
97	97	* Max boost current: 2A, 1 second
98	98
99	99
100		-
101		-
102	102	== ​1.4  Applications ==
103	103
104	104	* Smart Buildings & Home Automation
...	...	@@ -112,7 +112,7 @@
112	112	​
113	113
114	114
115		-== 1.5  Pin Definitions ==
	109	+== 1.5  Pin Definitions & Switch ==
116	116
117	117	N95S31B use the mother board from NBSN95 which as below.
118	118
...	...	@@ -127,9 +127,13 @@
127	127
128	128	=== 1.5.2 BOOT MODE / SW1 ===
129	129
	124	+(((
130	130	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.
	126	+)))
131	131
	128	+(((
132	132	2) Flash: work mode, device starts to work and send out console output for further debug
	130	+)))
133	133
134	134
135	135
...	...	@@ -146,6 +146,7 @@
146	146	1. When boot the device in flash mode
147	147	1. Send an uplink packet
148	148
	147	+
149	149	= 2.  Use N95S31B to communicate with IoT Server =
150	150
151	151	== 2.1  How it works ==
...	...	@@ -183,23 +183,45 @@
183	183	=== 2.2.1 Test Requirement ===
184	184
185	185
	185	+(((
186	186	To use N95S31B in your city, make sure meet below requirements:
	187	+)))
187	187
188		-* Your local operator has already distributed a NB-IoT Network there.
189		-* The local NB-IoT network used the band that N95S31B supports.
190		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	189	+* (((
	190	+Your local operator has already distributed a NB-IoT Network there.
	191	+)))
	192	+* (((
	193	+The local NB-IoT network used the band that N95S31B supports.
	194	+)))
	195	+* (((
	196	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	197	+)))
191	191
	199	+(((
192	192	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	201	+)))
193	193
	203	+(((
194	194	N95S31B supports different communication protocol such as :
	205	+)))
195	195
196	196	(((
197		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
198		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
199		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
200		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	208	+* (((
	209	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	210	+)))
	211	+* (((
	212	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	213	+)))
	214	+* (((
	215	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	216	+)))
	217	+* (((
	218	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	219	+)))
201	201
	221	+(((
202	202	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.
	223	+)))
203	203
204	204
205	205	)))
...	...	@@ -369,26 +369,44 @@
369	369	== 2.3  Uplink Payload ==
370	370
371	371
	393	+(((
372	372	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	+)))
373	373
374	374
	398	+(((
375	375	For example:
	400	+)))
376	376
	402	+(((
377	377	(% 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	+)))
378	378
379	379
	407	+(((
380	380	The uplink payloads are composed in  ASCII String. For example:
	409	+)))
381	381
	411	+(((
382	382	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	413	+)))
383	383
	415	+(((
384	384	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	417	+)))
385	385
386	386
	420	+(((
387	387	(% style="color:red" %)**NOTE:**
	422	+)))
388	388
389	389	(% style="color:red" %)
390		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
391		-1. By default, the device will send an uplink message every 1 hour.
	425	+1. (((
	426	+All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	427	+)))
	428	+1. (((
	429	+By default, the device will send an uplink message every 1 hour.
	430	+)))
392	392
393	393
394	394	=== 2.3.1  Payload Analyze ===
...	...	@@ -483,15 +483,25 @@
483	483
484	484	=== 2.3.3  Version Info ===
485	485
486		-
	525	+(((
487	487	These bytes include the hardware and software version.
	527	+)))
488	488
	529	+(((
489	489	Higher byte: Specify hardware version: always 0x00 for N95S31B
	531	+)))
490	490
	533	+(((
491	491	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
	535	+)))
492	492
	537	+(((
	538	+
	539	+)))
493	493
	541	+(((
494	494	For example: 0x00 6E: this device is N95S31B with firmware version 110.
	543	+)))
495	495
496	496	(((
497	497
...	...	@@ -780,8 +780,10 @@
780	780	(((
781	781
782	782
	832	+(((
783	783	(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
784	784	)))
	835	+)))
785	785
786	786
787	787