Summary

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

Details

Page properties

Content

...	...	@@ -22,16 +22,29 @@
22	22	(((
23	23
24	24
	25	+(((
25	25	The Dragino N95S31B is a (% style="color:blue" %)**NB-IoT Temperature and Humidity Sensor**(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)**surrounding environment temperature and relative air humidity precisely**(%%), and then upload to IoT server via NB-IoT network*.
	27	+)))
26	26
	29	+(((
27	27	The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)**waterproof anti-condensation casing **(%%)for long term use.
	31	+)))
28	28
	33	+(((
29	29	N95S31B supports different uplink methods include (% style="color:blue" %)**TCP, MQTT, UDP and CoAP**(%%) for different application requirement.
	35	+)))
30	30
	37	+(((
31	31	N95S31B is powered by(% style="color:blue" %)**8500mAh Li-SOCI2 battery**(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
	39	+)))
32	32
	41	+(((
	42	+
	43	+)))
33	33
	45	+(((
34	34	~* make sure you have NB-IoT coverage locally.
	47	+)))
35	35
36	36
37	37	)))
...	...	@@ -64,6 +64,7 @@
64	64	* Supply Voltage: 2.1v ~~ 3.6v
65	65	* Operating Temperature: -40 ~~ 85°C
66	66
	80	+
67	67	(% style="color:#037691" %)**NB-IoT Spec:**
68	68
69	69	* - B1 @H-FDD: 2100MHz
...	...	@@ -73,9 +73,9 @@
73	73	* - B20 @H-FDD: 800MHz
74	74	* - B28 @H-FDD: 700MHz
75	75
	90	+
76	76	(% style="color:#037691" %)**Battery:**
77	77
78		-
79	79	* Li/SOCI2 un-chargeable battery
80	80	* Capacity: 8500mAh
81	81	* Self Discharge: <1% / Year @ 25°C
...	...	@@ -113,9 +113,13 @@
113	113
114	114	=== 1.5.2 BOOT MODE / SW1 ===
115	115
	130	+(((
116	116	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.
	132	+)))
117	117
	134	+(((
118	118	2) Flash: work mode, device starts to work and send out console output for further debug
	136	+)))
119	119
120	120
121	121
...	...	@@ -133,6 +133,8 @@
133	133	1. Send an uplink packet
134	134
135	135
	154	+
	155	+
136	136	= 2.  Use N95S31B to communicate with IoT Server =
137	137
138	138	== 2.1  How it works ==
...	...	@@ -170,23 +170,45 @@
170	170	=== 2.2.1 Test Requirement ===
171	171
172	172
	193	+(((
173	173	To use N95S31B in your city, make sure meet below requirements:
	195	+)))
174	174
175		-* Your local operator has already distributed a NB-IoT Network there.
176		-* The local NB-IoT network used the band that N95S31B supports.
177		-* 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	+)))
178	178
	207	+(((
179	179	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
	209	+)))
180	180
	211	+(((
181	181	N95S31B supports different communication protocol such as :
	213	+)))
182	182
183	183	(((
184		-* CoAP  ((% style="color:red" %)120.24.4.116:5683(%%))
185		-* raw UDP  ((% style="color:red" %)120.24.4.116:5601(%%))
186		-* MQTT  ((% style="color:red" %)120.24.4.116:1883(%%))
187		-* 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	+)))
188	188
	229	+(((
189	189	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	+)))
190	190
191	191
192	192	)))
...	...	@@ -356,51 +356,82 @@
356	356	== 2.3  Uplink Payload ==
357	357
358	358
	401	+(((
359	359	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	+)))
360	360
361	361
	406	+(((
362	362	For example:
	408	+)))
363	363
	410	+(((
364	364	(% 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	+)))
365	365
366	366
	415	+(((
367	367	The uplink payloads are composed in  ASCII String. For example:
	417	+)))
368	368
	419	+(((
369	369	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
	421	+)))
370	370
	423	+(((
371	371	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
	425	+)))
372	372
373	373
	428	+(((
374	374	(% style="color:red" %)**NOTE:**
	430	+)))
375	375
376	376	(% style="color:red" %)
377		-1. All modes share the same Payload Explanation from [[HERE>>path:#Payload_Explain]].
378		-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	+)))
379	379
380	380
381	381
	442	+
382	382	=== 2.3.1  Payload Analyze ===
383	383
384	384	N95S31B uplink payload includes in total 21 bytes
385	385
386	386
387		-(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:440px" %)
	448	+(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
388	388	|=(% style="width: 60px;" %)(((
389	389	**Size(bytes)**
390		-)))|=(% style="width: 60px;" %)**6**|=(% style="width: 35px;" %)2|=(% style="width: 35px;" %)**2**|=(% style="width: 80px;" %)**1**|=(% style="width: 80px;" %) |=(% style="width: 99px;" %) |=(% style="width: 77px;" %)**2**|=(% style="width: 60px;" %)**1**
391		-|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.4.1A0A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.4.2A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.4.3A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.4.4A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
	451	+)))|=(% style="width: 50px;" %)**6**|=(% style="width: 25px;" %)2|=(% style="width: 25px;" %)**2**|=(% style="width: 70px;" %)**1**|=(% style="width: 55px;" %)1|=(% style="width: 115px;" %)5|=(% style="width: 60px;" %)**2**|=(% style="width: 60px;" %)**2**
	452	+|(% style="width:97px" %)**Value**|(% style="width:83px" %)[[Device ID>>||anchor="H2.3.2A0DeviceID"]]|(% style="width:41px" %)[[Ver>>||anchor="H2.3.3A0VersionInfo"]]|(% style="width:46px" %)[[BAT>>||anchor="H2.3.4A0BatteryInfo"]]|(% style="width:123px" %)[[Signal Strength>>||anchor="H2.3.5A0SignalStrength"]]|(% style="width:123px" %)MOD 0X01|(% style="width:99px" %)(((
	453	+(((
392	392	Reserve/ Same as NBSN95 CFGMOD=1
	455	+)))
393	393
	457	+(((
394	394	No function here.
	459	+)))
395	395	)))|(% style="width:77px" %)(((
396		-[[Temperature >>||anchor="H2.4.5A0Distance"]]
	461	+(((
	462	+[[Temperature >>||anchor="H2.3.6A0Temperature26Humidity"]]
	463	+)))
397	397
	465	+(((
398	398	By SHT31
	467	+)))
399	399	)))|(% style="width:80px" %)(((
400		-[[Humidity>>||anchor="H2.4.6A0DigitalInterrupt"]]
	469	+(((
	470	+[[Humidity>>||anchor="H2.3.6A0Temperature26Humidity"]]
	471	+)))
401	401
	473	+(((
402	402	By SHT31
403	403	)))
	476	+)))
404	404
405	405	(((
406	406	(((