Summary

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

Details

Page properties

Content

...	...	@@ -190,45 +190,23 @@
190	190	=== 2.2.1 Test Requirement ===
191	191
192	192
193		-(((
194	194	To use N95S31B in your city, make sure meet below requirements:
195		-)))
196	196
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	+* 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.
206	206
207		-(((
208	208	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
209		-)))
210	210
211		-(((
212	212	N95S31B supports different communication protocol such as :
213		-)))
214	214
215	215	(((
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		-)))
	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(%%))
228	228
229		-(((
230	230	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		-)))
232	232
233	233
234	234	)))
...	...	@@ -398,44 +398,26 @@
398	398	== 2.3  Uplink Payload ==
399	399
400	400
401		-(((
402	402	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		-)))
404	404
405	405
406		-(((
407	407	For example:
408		-)))
409	409
410		-(((
411	411	(% 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		-)))
413	413
414	414
415		-(((
416	416	The uplink payloads are composed in  ASCII String. For example:
417		-)))
418	418
419		-(((
420	420	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
421		-)))
422	422
423		-(((
424	424	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
425		-)))
426	426
427	427
428		-(((
429	429	(% style="color:red" %)**NOTE:**
430		-)))
431	431
432	432	(% style="color:red" %)
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		-)))
	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.
439	439
440	440
441	441	=== 2.3.1  Payload Analyze ===