Summary

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

Details

Page properties

Content

...	...	@@ -150,6 +150,9 @@
150	150	1. When boot the device in flash mode
151	151	1. Send an uplink packet
152	152
	153	+
	154	+
	155	+
153	153	= 2.  Use N95S31B to communicate with IoT Server =
154	154
155	155	== 2.1  How it works ==
...	...	@@ -187,23 +187,45 @@
187	187	=== 2.2.1 Test Requirement ===
188	188
189	189
	193	+(((
190	190	To use N95S31B in your city, make sure meet below requirements:
	195	+)))
191	191
192		-* Your local operator has already distributed a NB-IoT Network there.
193		-* The local NB-IoT network used the band that N95S31B supports.
194		-* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	197	+* (((
	198	+Your local operator has already distributed a NB-IoT Network there.
	199	+)))
	200	+* (((
	201	+The local NB-IoT network used the band that N95S31B supports.
	202	+)))
	203	+* (((
	204	+Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	205	+)))
195	195
	207	+(((
196	196	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	209	+)))
197	197
	211	+(((
198	198	N95S31B supports different communication protocol such as :
	213	+)))
199	199
200	200	(((
201		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
202		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
203		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
204		-* TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	216	+* (((
	217	+CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
	218	+)))
	219	+* (((
	220	+raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
	221	+)))
	222	+* (((
	223	+MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
	224	+)))
	225	+* (((
	226	+TCP  ((% style="color:red" %)120.24.4.116:5600(%%))
	227	+)))
205	205
	229	+(((
206	206	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.
	231	+)))
207	207
208	208
209	209	)))
...	...	@@ -373,28 +373,48 @@
373	373	== 2.3  Uplink Payload ==
374	374
375	375
	401	+(((
376	376	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.
	403	+)))
377	377
378	378
	406	+(((
379	379	For example:
	408	+)))
380	380
	410	+(((
381	381	(% 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.
	412	+)))
382	382
383	383
	415	+(((
384	384	The uplink payloads are composed in  ASCII String. For example:
	417	+)))
385	385
	419	+(((
386	386	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	421	+)))
387	387
	423	+(((
388	388	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	425	+)))
389	389
390	390
	428	+(((
391	391	(% style="color:red" %)**NOTE:**
	430	+)))
392	392
393	393	(% style="color:red" %)
394		-1. All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
395		-1. By default, the device will send an uplink message every 1 hour.
	433	+1. (((
	434	+All modes share the same Payload Explanation from [[HERE>>||anchor="H2.3A0UplinkPayload"]].
	435	+)))
	436	+1. (((
	437	+By default, the device will send an uplink message every 1 hour.
	438	+)))
396	396
397	397
	441	+
	442	+
398	398	=== 2.3.1  Payload Analyze ===
399	399
400	400	N95S31B uplink payload includes in total 21 bytes
...	...	@@ -784,8 +784,10 @@
784	784	(((
785	785
786	786
	832	+(((
787	787	(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
788	788	)))
	835	+)))
789	789
790	790
791	791