Summary

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

Details

Page properties

Content

...	...	@@ -190,23 +190,45 @@
190	190	=== 2.2.1 Test Requirement ===
191	191
192	192
	193	+(((
193	193	To use N95S31B in your city, make sure meet below requirements:
	195	+)))
194	194
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.
	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	+)))
198	198
	207	+(((
199	199	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	209	+)))
200	200
	211	+(((
201	201	N95S31B supports different communication protocol such as :
	213	+)))
202	202
203	203	(((
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(%%))
	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	+)))
208	208
	229	+(((
209	209	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	+)))
210	210
211	211
212	212	)))
...	...	@@ -376,28 +376,48 @@
376	376	== 2.3  Uplink Payload ==
377	377
378	378
	401	+(((
379	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.
	403	+)))
380	380
381	381
	406	+(((
382	382	For example:
	408	+)))
383	383
	410	+(((
384	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.
	412	+)))
385	385
386	386
	415	+(((
387	387	The uplink payloads are composed in  ASCII String. For example:
	417	+)))
388	388
	419	+(((
389	389	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	421	+)))
390	390
	423	+(((
391	391	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	425	+)))
392	392
393	393
	428	+(((
394	394	(% style="color:red" %)**NOTE:**
	430	+)))
395	395
396	396	(% style="color:red" %)
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	+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	+)))
399	399
400	400
	441	+
	442	+
401	401	=== 2.3.1  Payload Analyze ===
402	402
403	403	N95S31B uplink payload includes in total 21 bytes