Wiki source code of N95S31B NB-IoT Temperature & Humidity Sensor User Manual

Version 125.3 by Xiaoling on 2022/09/09 15:56

version	line-number	content
74.2	1	(% style="text-align:center" %)
99.2	2	[[image:1657348034241-728.png\|\|height="470" width="470"]]
1.1	3
	4
	5
35.25	6
	7
99.2	8
	9
35.4	10	Table of Contents:
1.1	11
115.14	12	{{toc/}}
1.1	13
	14
	15
	16
31.17	17
44.2	18	= 1. Introduction =
1.1	19
119.2	20
99.2	21	== 1.1 What is N95S31B NB-IoT Sensor Node ==
1.1	22
12.2	23	(((
35.4	24
	25
115.25	26	(((
99.2	27	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*.
115.25	28	)))
97.13	29
115.25	30	(((
99.2	31	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.
115.25	32	)))
97.13	33
115.25	34	(((
99.2	35	N95S31B supports different uplink methods include (% style="color:blue" %)TCP, MQTT, UDP and CoAP(%%) for different application requirement.
115.25	36	)))
97.13	37
115.25	38	(((
99.2	39	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).
115.25	40	)))
97.13	41
115.25	42	(((
	43
	44	)))
97.13	45
115.25	46	(((
99.2	47	~* make sure you have NB-IoT coverage locally.
115.25	48	)))
4.2	49
42.2	50
12.2	51	)))
4.2	52
99.2	53	[[image:1657348284168-431.png]]
4.2	54
	55
	56
65.3	57	== 1.2 Features ==
13.3	58
119.2	59
44.2	60	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
100.2	61	* Monitor Temperature & Humidity via SHT31
4.2	62	* AT Commands to change parameters
	63	* Uplink on periodically
	64	* Downlink to change configure
	65	* IP66 Waterproof Enclosure
100.2	66	* Ultra-Low Power consumption
	67	* AT Commands to change parameters
44.2	68	* Micro SIM card slot for NB-IoT SIM
	69	* 8500mAh Battery for long term use
4.2	70
125.2	71
44.2	72	== 1.3 Specification ==
	73
	74
	75	(% style="color:#037691" %)Common DC Characteristics:
	76
	77	* Supply Voltage: 2.1v ~~ 3.6v
	78	* Operating Temperature: -40 ~~ 85°C
	79
	80	(% style="color:#037691" %)NB-IoT Spec:
	81
	82	* - B1 @H-FDD: 2100MHz
	83	* - B3 @H-FDD: 1800MHz
	84	* - B8 @H-FDD: 900MHz
	85	* - B5 @H-FDD: 850MHz
	86	* - B20 @H-FDD: 800MHz
	87	* - B28 @H-FDD: 700MHz
	88
75.3	89	(% style="color:#037691" %)Battery:
4.2	90
75.3	91	* Li/SOCI2 un-chargeable battery
	92	* Capacity: 8500mAh
	93	* Self Discharge: <1% / Year @ 25°C
	94	* Max continuously current: 130mA
	95	* Max boost current: 2A, 1 second
14.2	96
125.2	97
44.2	98	== 1.4 Applications ==
4.2	99
119.2	100
75.4	101	* Smart Buildings & Home Automation
	102	* Logistics and Supply Chain Management
	103	* Smart Metering
4.2	104	* Smart Agriculture
75.4	105	* Smart Cities
	106	* Smart Factory
4.2	107
15.6	108	(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
	109
4.2	110
75.4	111
119.2	112
125.2	113
117.2	114	== 1.5 Pin Definitions & Switch ==
15.6	115
119.2	116
100.2	117	N95S31B use the mother board from NBSN95 which as below.
15.6	118
119.2	119
100.2	120	[[image:image-20220709144723-1.png]]
4.2	121
14.3	122
119.2	123
100.2	124	=== 1.5.1 Jumper JP2 ===
14.3	125
119.2	126
100.2	127	Power on Device when put this jumper.
14.3	128
100.2	129
	130
	131	=== 1.5.2 BOOT MODE / SW1 ===
	132
119.2	133
115.29	134	(((
100.2	135	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.
115.29	136	)))
100.2	137
115.29	138	(((
100.2	139	2) Flash: work mode, device starts to work and send out console output for further debug
115.29	140	)))
100.2	141
	142
	143
	144	=== 1.5.3 Reset Button ===
	145
119.2	146
100.2	147	Press to reboot the device.
	148
	149
	150
	151	=== 1.5.4 LED ===
	152
119.2	153
100.2	154	It will flash:
	155
	156	1. When boot the device in flash mode
	157	1. Send an uplink packet
	158
125.2	159
100.2	160	= 2. Use N95S31B to communicate with IoT Server =
	161
119.2	162
45.2	163	== 2.1 How it works ==
14.3	164
100.3	165
15.3	166	(((
100.3	167	The N95S31B is equipped with a NB-IoT module, the pre-loaded firmware in N95S31B will get environment data from sensors and send the value to local NB-IoT network via the NB-IoT module. The NB-IoT network will forward this value to IoT server via the protocol defined by N95S31B.
15.3	168	)))
4.2	169
45.2	170
15.3	171	(((
100.3	172	The diagram below shows the working flow in default firmware of N95S31B:
15.3	173	)))
4.2	174
77.2	175	(((
	176
	177	)))
4.2	178
118.2	179	[[image:1657520100595-569.png]]
77.2	180
45.2	181	(((
	182
	183	)))
4.2	184
45.2	185
102.2	186	== 2.2 Configure the N95S31B ==
4.2	187
48.2	188
102.2	189	=== 2.2.1 Power On N95S31B ===
	190
	191
	192	[[image:image-20220709150546-2.png]]
	193
102.3	194
119.2	195
45.4	196	=== 2.2.1 Test Requirement ===
4.2	197
	198
115.31	199	(((
102.3	200	To use N95S31B in your city, make sure meet below requirements:
115.31	201	)))
102.3	202
115.31	203	* (((
	204	Your local operator has already distributed a NB-IoT Network there.
	205	)))
	206	* (((
	207	The local NB-IoT network used the band that N95S31B supports.
	208	)))
	209	* (((
	210	Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	211	)))
4.2	212
115.31	213	(((
102.3	214	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
115.31	215	)))
102.3	216
115.31	217	(((
102.3	218	N95S31B supports different communication protocol such as :
115.31	219	)))
102.3	220
48.2	221	(((
115.31	222	* (((
	223	CoAP ((% style="color:red" %)120.24.4.116:5683(%%))
	224	)))
	225	* (((
	226	raw UDP ((% style="color:red" %)120.24.4.116:5601(%%))
	227	)))
	228	* (((
	229	MQTT ((% style="color:red" %)120.24.4.116:1883(%%))
	230	)))
	231	* (((
	232	TCP ((% style="color:red" %)120.24.4.116:5600(%%))
	233	)))
102.3	234
115.31	235	(((
102.3	236	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.
115.31	237	)))
102.3	238
	239
	240	)))
	241
103.2	242	[[image:1657350625843-586.png]]
4.2	243
	244
	245
104.2	246	=== 2.2.3 Insert SIM card ===
4.2	247
119.2	248
65.11	249	(((
45.4	250	Insert the NB-IoT Card get from your provider.
65.11	251	)))
4.2	252
65.11	253	(((
45.4	254	User need to take out the NB-IoT module and insert the SIM card like below:
65.11	255	)))
4.2	256
	257
104.2	258	[[image:1657351240556-536.png]]
4.2	259
	260
48.2	261
107.2	262	=== 2.2.4 Connect USB – TTL to N95S31B to configure it ===
4.2	263
119.2	264
48.2	265	(((
	266	(((
105.2	267	User need to configure N95S31B via serial port to set the (% style="color:blue" %)Server Address / Uplink Topic (%%)to define where and how-to uplink packets. N95S31B support AT Commands, user can use a USB to TTL adapter to connect to N95S31B and use AT Commands to configure it, as below.
119.2	268
	269
48.2	270	)))
	271	)))
19.2	272
105.2	273	[[image:1657351312545-300.png]]
4.2	274
119.2	275
48.2	276	Connection:
4.2	277
45.6	278	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	279
45.6	280	(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
4.2	281
45.6	282	(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
4.2	283
	284
45.4	285	In the PC, use below serial tool settings:
	286
57.4	287	* Baud: (% style="color:green" %)9600
48.2	288	* Data bits: (% style="color:green" %)8(%%)
	289	* Stop bits: (% style="color:green" %)1
57.4	290	* Parity: (% style="color:green" %)None
48.2	291	* Flow Control: (% style="color:green" %)None
45.4	292
48.2	293	(((
105.2	294	Make sure the switch is in FLASH position, then power on device by connecting the jumper on N95S31B. N95S31B will output system info once power on as below, we can enter the (% style="color:green" %)password: 12345678(%%) to access AT Command input.
48.2	295	)))
45.4	296
81.2	297	[[image:1657329814315-101.png]]
45.4	298
119.2	299
65.12	300	(((
119.2	301	(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]]
65.12	302	)))
45.4	303
	304
	305
107.2	306	=== 2.2.5 Use CoAP protocol to uplink data ===
45.4	307
	308
119.2	309	(% style="color:red" %)Note: if you don't have CoAP server, you can refer this link to set up one: (%%)[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/>>http://wiki.dragino.com/xwiki/bin/view/Main/Set%20up%20CoAP%20Server/]]
45.4	310
119.2	311
97.9	312	(((
50.2	313	Use below commands:
97.9	314	)))
45.4	315
97.9	316	* (((
	317	(% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	318	)))
	319	* (((
	320	(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
	321	)))
	322	* (((
	323	(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/Set COAP resource path
	324	)))
45.4	325
97.9	326	(((
107.2	327
	328
45.4	329	For parameter description, please refer to AT command set
97.9	330	)))
45.4	331
107.2	332	[[image:1657352146020-183.png]]
45.4	333
	334
97.10	335	(((
86.2	336	After configure the server address and (% style="color:green" %)reset the device(%%) (via AT+ATZ ), NDDS75 will start to uplink sensor values to CoAP server.
97.10	337	)))
45.4	338
107.2	339	[[image:1657352185396-303.png]]
45.4	340
	341
50.2	342
107.2	343	=== 2.2.6 Use UDP protocol to uplink data(Default protocol) ===
45.4	344
	345
97.5	346	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
48.2	347	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
97.5	348	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
45.4	349
111.2	350	[[image:1657352391268-297.png]]
45.4	351
	352
111.2	353	[[image:1657352403317-397.png]]
45.4	354
52.3	355
86.2	356
111.2	357	=== 2.2.7 Use MQTT protocol to uplink data ===
45.4	358
119.3	359
113.2	360	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
45.4	361
97.11	362	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/Set to use MQTT protocol to uplink
	363	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/Set MQTT server address and port
	364	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/Set up the CLIENT of MQTT
97.13	365	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/Set the username of MQTT
	366	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/Set the password of MQTT
114.2	367	* (% style="color:blue" %)AT+PUBTOPIC=f9527 (%%)~/~/Set the sending topic of MQTT
	368	* (% style="color:blue" %)AT+SUBTOPIC=Ns9527 (%%) ~/~/Set the subscription topic of MQTT
45.4	369
111.2	370	[[image:1657352634421-276.png]]
45.4	371
54.2	372
111.2	373	[[image:1657352645687-385.png]]
54.2	374
119.3	375
111.2	376	(((
	377	To save battery life, N95S31B will establish a subscription before each uplink and close the subscription 3 seconds after uplink successful. Any downlink commands from server will only arrive during the subscription period.
	378	)))
45.4	379
111.2	380
54.3	381	(((
111.2	382	MQTT protocol has a much high-power consumption compare vs UDP / CoAP protocol. Please check the power analyze document and adjust the uplink period to a suitable interval.
54.3	383	)))
45.4	384
	385
54.3	386
113.2	387	=== 2.2.8 Use TCP protocol to uplink data ===
45.4	388
119.3	389
113.2	390	This feature is supported since firmware version v110
45.4	391
56.2	392	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	393	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	394
113.2	395	[[image:1657352898400-901.png]]
45.4	396
	397
113.2	398	[[image:1657352914475-252.png]]
45.4	399
57.6	400
89.2	401
113.2	402	=== 2.2.9 Change Update Interval ===
45.4	403
119.3	404
48.2	405	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	406
56.3	407	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	408
56.3	409	(((
113.2	410
56.3	411	)))
45.4	412
125.2	413	(((
125.1	414	(% style="color:red" %)NOTE: Since firmware version is v1.2:
125.2	415	)))
45.4	416
125.2	417	(((
	418	(% style="color:red" %)By default, the device will send an uplink message every 2 hours. Each Uplink Include 8 set of records in this 2 hour (15 minute interval / record).
	419	)))
45.4	420
122.1	421
125.2	422
57.2	423	== 2.3 Uplink Payload ==
4.2	424
32.9	425
115.32	426	(((
125.1	427	N95S31B has different working modes for the connections of different types 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.
115.32	428	)))
90.2	429
114.2	430
115.32	431	(((
114.2	432	For example:
115.32	433	)))
114.2	434
115.32	435	(((
118.7	436	(% style="color:blue" %)AT+CFGMOD=2 (%%)~/~/will set the N95S31B to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
115.32	437	)))
114.2	438
	439
115.32	440	(((
114.2	441	The uplink payloads are composed in ASCII String. For example:
115.32	442	)))
114.2	443
115.32	444	(((
114.2	445	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
115.32	446	)))
114.2	447
115.32	448	(((
114.2	449	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
115.32	450	)))
114.2	451
	452
115.32	453	(((
114.2	454	(% style="color:red" %)NOTE:
115.32	455	)))
114.2	456
	457	(% style="color:red" %)
115.32	458	1. (((
119.3	459	All modes share the same Payload Explanation from [[HERE>>\|\|anchor="H2.3A0UplinkPayload"]].
115.32	460	)))
	461	1. (((
119.3	462	By default, the device will send an uplink message every 1 hour.
118.4	463
	464
	465
	466
115.32	467	)))
114.2	468
	469	=== 2.3.1 Payload Analyze ===
	470
119.3	471
125.2	472	==== 2.3.1.1 Before Firmware v1.2 ====
125.1	473
125.2	474
114.2	475	N95S31B uplink payload includes in total 21 bytes
	476
	477
125.2	478	(% border="2" cellspacing="10" style="background-color:#ffffcc; color:green; width:760px" %)
115.19	479	\|=(% style="width: 60px;" %)(((
57.2	480	Size(bytes)
125.2	481	)))\|=(% style="width: 65px;" %)6\|=(% style="width: 50px;" %)2\|=(% style="width: 25px;" %)2\|=(% style="width: 75px;" %)1\|=(% style="width: 59px;" %)1\|=(% style="width: 174px;" %)5\|=(% style="width: 106px;" %)2\|=(% style="width: 85px;" %)2
	482	\|(% style="width:97px" %)Value\|(% style="width:65px" %)[[Device ID>>\|\|anchor="H2.3.2A0DeviceID"]]\|(% style="width:50px" %)[[Ver>>\|\|anchor="H2.3.3A0VersionInfo"]]\|(% style="width:46px" %)[[BAT>>\|\|anchor="H2.3.4A0BatteryInfo"]]\|(% style="width:75px" %)[[Signal Strength>>\|\|anchor="H2.3.5A0SignalStrength"]]\|(% style="width:59px" %)MOD 0X01\|(% style="width:174px" %)(((
115.21	483	(((
114.2	484	Reserve/ Same as NBSN95 CFGMOD=1
115.21	485	)))
57.2	486
115.21	487	(((
114.2	488	No function here.
115.21	489	)))
125.2	490	)))\|(% style="width:106px" %)(((
115.21	491	(((
115.15	492	[[Temperature >>\|\|anchor="H2.3.6A0Temperature26Humidity"]]
115.21	493	)))
114.2	494
115.21	495	(((
114.2	496	By SHT31
115.21	497	)))
125.2	498	)))\|(% style="width:85px" %)(((
115.21	499	(((
115.15	500	[[Humidity>>\|\|anchor="H2.3.6A0Temperature26Humidity"]]
115.21	501	)))
114.2	502
115.21	503	(((
114.2	504	By SHT31
	505	)))
115.21	506	)))
114.2	507
65.13	508	(((
119.3	509
	510
114.2	511	(((
	512	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NB sensor uplink data.
65.13	513	)))
114.2	514	)))
57.2	515
	516
114.2	517	[[image:1657354294009-643.png]]
57.2	518
	519
115.2	520	The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
57.2	521
125.2	522	* Device ID: 0x724031607457 = 724031607457
57.2	523
125.2	524	* Version: 0x006e=110=1.1.0
	525
	526	* BAT: 0x0ccd = 3277 mV = 3.277V
	527
	528	* Signal: 0x1b = 27
	529
	530	* Model: 0x01 = 1
	531
115.2	532	* 0x00dc000ccc= reserve, ignore in N95S31B
	533
125.2	534	* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
	535
	536	* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	537
115.2	538	(((
	539
125.2	540
	541
	542
90.2	543	)))
95.5	544
125.1	545	==== 2.3.1.2 Since Firmware v1.2 ====
57.2	546
125.3	547
122.1	548	In this mode, uplink payload includes 91 bytes in total by default.
4.2	549
122.1	550	Each time the device uploads a data package, 8 sets of recorded data will be attached. Up to 32 sets of recorded data can be uploaded.
	551
	552
125.3	553	(% border="2" style="background-color:#ffffcc; color:green; width:1234px" %)
	554	\|(% style="width:95px" %)Size(bytes)\|(% style="width:82px" %)8\|(% style="width:43px" %)2\|(% style="width:47px" %)2\|(% style="width:124px" %)1\|(% style="width:56px" %)1\|(% style="width:109px" %)2\|(% style="width:80px" %)1\|(% style="width:51px" %)2\|(% style="width:79px" %)2\|(% style="width:84px" %)2\|(% style="width:100px" %)4\|(% style="width:76px" %)2\|(% style="width:81px" %)2\|(% style="width:121px" %)4
	555	\|(% style="width:95px" %)Value\|(% style="width:82px" %)Device ID\|(% style="width:43px" %)Ver\|(% style="width:47px" %)BAT\|(% style="width:124px" %)Signal Strength\|(% style="width:56px" %)MOD\|(% style="width:109px" %)TemDS18B20\|(% style="width:80px" %)Interrupt\|(% style="width:51px" %)ADC\|(% style="width:79px" %)SHTTEM\|(% style="width:84px" %)SHTHUM\|(% style="width:100px" %)Time stamp \|(% style="width:76px" %)SHTTEM\|(% style="width:81px" %)SHTHUM\|(% style="width:121px" %)Time stamp .....
	556
123.1	557	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the N95S31B uplink data.
122.1	558
125.3	559
122.1	560	[[image:image-20220908154949-1.png]]
	561
125.3	562
122.1	563	The payload is ASCII string, representative same HEX:
	564
	565	0x(% style="color:red" %)f868411056758782(% style="color:blue" %)000c(% style="color:green" %)0d0f(% style="color:red" %)0c(% style="color:blue" %)01(% style="color:green" %)0000(% style="color:red" %)00//0030//(% style="color:blue" %)//0114//(% style="color:red" %)//0231//(% style="color:green" %)//63199d3c//0113023163199d12//0113023163199c5e//0112023763199baa//0112023263199af6//0111023b631999a7//0112023b631998f3//011202426319983f//01110242631996eb//(%%) where:
	566
125.3	567	* (% style="color:red" %)Device ID: f868411056758782 = f868411056758782
	568
	569	* (% style="color:blue" %)Version: 0x000c=120=1.2
	570
	571	* (% style="color:green" %)BAT: 0x0d0f = 3343 mV = 3.343V
	572
	573	* (% style="color:red" %)Singal: 0x0c = 12
	574
	575	* (% style="color:blue" %)Mod: 0x01 = 1
	576
122.1	577	* TemDS18B20: 0x0000= 0 = 0
125.3	578
122.1	579	* (% style="color:green" %)Interrupt: 0x00= 0
125.3	580
122.1	581	* (% style="color:green" %)adc: 0x0030= 48
125.3	582
122.1	583	* SHTTEM: 0x0114= 276 = 27.6
125.3	584
122.1	585	* SHTHUM:0x0231 =561=56.1%
125.3	586
	587	* (% style="color:red" %)Time stamp : 0x6315537b =1662342011 ([[Unix Epoch Time>>url:http://www.epochconverter.com/]])
	588
122.1	589	* (% style="color:red" %)SHTTEM,SHTHUM,Time stamp : 0113023163199d12
125.3	590
123.1	591	* 8 sets of recorded data: SHTTEM,SHTHUM,Time stamp : //0113023163199c5e//,.......
122.1	592
125.3	593
	594
	595
115.2	596	=== 2.3.2 Device ID ===
57.7	597
119.3	598
65.13	599	(((
57.3	600	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	601	)))
4.2	602
65.13	603	(((
57.4	604	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
65.13	605	)))
4.2	606
65.13	607	(((
57.3	608	Example:
65.13	609	)))
4.2	610
65.13	611	(((
57.3	612	AT+DEUI=A84041F15612
65.13	613	)))
4.2	614
65.13	615	(((
91.1	616	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
122.1	617
	618
65.13	619	)))
22.2	620
122.1	621	(% style="color:red" %)NOTE:When the firmware version is v1.2 and later firmware:
4.2	622
	623
122.1	624	By default, the Device ID equal to the last 15 bits of IMEI.
	625
	626	User can use AT+DEUI to set Device ID
	627
	628	Example:
	629
	630	AT+DEUI=868411056754138
	631
	632
115.2	633	=== 2.3.3 Version Info ===
57.5	634
119.3	635
116.2	636	(((
115.2	637	These bytes include the hardware and software version.
116.2	638	)))
115.2	639
116.2	640	(((
115.2	641	Higher byte: Specify hardware version: always 0x00 for N95S31B
116.2	642	)))
115.2	643
116.2	644	(((
115.2	645	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
116.2	646	)))
115.2	647
116.2	648	(((
	649
	650	)))
115.2	651
116.2	652	(((
115.2	653	For example: 0x00 6E: this device is N95S31B with firmware version 110.
116.2	654	)))
115.2	655
65.13	656	(((
115.2	657
65.13	658	)))
4.2	659
	660
115.2	661	=== 2.3.4 Battery Info ===
57.3	662
119.3	663
32.10	664	(((
4.2	665	Ex1: 0x0B45 = 2885mV
32.10	666	)))
4.2	667
32.10	668	(((
4.2	669	Ex2: 0x0B49 = 2889mV
32.10	670	)))
4.2	671
	672
	673
115.2	674	=== 2.3.5 Signal Strength ===
4.2	675
119.3	676
65.13	677	(((
57.6	678	NB-IoT Network signal Strength.
65.13	679	)))
57.6	680
65.13	681	(((
57.6	682	Ex1: 0x1d = 29
65.13	683	)))
57.6	684
65.13	685	(((
57.6	686	(% style="color:blue" %)0(%%) -113dBm or less
65.13	687	)))
57.6	688
65.13	689	(((
57.6	690	(% style="color:blue" %)1(%%) -111dBm
65.13	691	)))
57.6	692
65.13	693	(((
57.6	694	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	695	)))
57.6	696
65.13	697	(((
57.6	698	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	699	)))
57.6	700
65.13	701	(((
57.6	702	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	703	)))
57.6	704
	705
	706
115.2	707	=== 2.3.6 Temperature & Humidity ===
57.6	708
119.3	709
115.2	710	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
4.2	711
115.2	712	[[image:image-20220709161741-3.png]]
4.2	713
	714
115.2	715	Convert the read byte to decimal and divide it by ten.
4.2	716
23.2	717
115.2	718	Example:
23.2	719
115.2	720	Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃
4.2	721
115.2	722	Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1%
4.2	723
	724
	725
115.14	726	== 2.4 Downlink Payload ==
4.2	727
119.3	728
118.5	729	By default, N95S31B prints the downlink payload to console port.
4.2	730
92.2	731	[[image:image-20220709100028-1.png]]
4.2	732
	733
32.14	734	(((
40.4	735	(% style="color:blue" %)Examples:
32.14	736	)))
4.2	737
32.14	738	(((
	739
	740	)))
4.2	741
32.14	742	* (((
40.4	743	(% style="color:blue" %)Set TDC
32.14	744	)))
4.2	745
32.14	746	(((
60.2	747	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	748	)))
4.2	749
32.14	750	(((
4.2	751	Payload: 01 00 00 1E TDC=30S
32.14	752	)))
4.2	753
32.14	754	(((
4.2	755	Payload: 01 00 00 3C TDC=60S
32.14	756	)))
4.2	757
32.14	758	(((
	759
	760	)))
4.2	761
32.14	762	* (((
40.4	763	(% style="color:blue" %)Reset
32.14	764	)))
4.2	765
32.14	766	(((
118.5	767	If payload = 0x04FF, it will reset the N95S31B
32.14	768	)))
4.2	769
	770
60.2	771	* (% style="color:blue" %)INTMOD
4.2	772
65.17	773	(((
60.2	774	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	775	)))
4.2	776
	777
122.1	778	== 2.5 Humidity and Temperature alarm function ==
26.2	779
122.1	780	➢ AT Command:
4.2	781
122.1	782	AT+ SHHUM=min,max
119.3	783
122.1	784	² When min=0, and max≠0, Alarm higher than max
4.2	785
122.1	786	² When min≠0, and max=0, Alarm lower than min
4.2	787
122.1	788	² When min≠0 and max≠0, Alarm higher than max or lower than min
	789
	790	Example:
	791
	792	AT+ SHHUM=50,80 ~/~/ Alarm when humidity lower than 50.
	793
	794
	795	AT+ SHTEMP=min,max
	796
	797	² When min=0, and max≠0, Alarm higher than max
	798
	799	² When min≠0, and max=0, Alarm lower than min
	800
	801	² When min≠0 and max≠0, Alarm higher than max or lower than min
	802
	803	Example:
	804
	805	AT+ SHTEMP=20,30 ~/~/ Alarm when temperature lower than 20.
	806
	807	== 2.6 Set the number of data to be uploaded and the recording time ==
	808
	809	➢ AT Command:
	810
	811	AT+TR=900 ~/~/The unit is seconds, and the default is to record data once every 900 seconds.( The minimum can be set to 180 seconds)
	812
	813	AT+NOUD=8 ~/~/The device uploads 8 sets of recorded data by default. Up to 32 sets of record data can be uploaded.
	814
	815	== 2.7 Read or Clear cached data ==
	816
	817	➢ AT Command:
	818
	819	AT+CDP ~/~/ Read cached data
	820
	821	[[image:image-20220908163102-2.png]]
	822
	823	AT+CDP=0 ~/~/ Clear cached data
	824
	825	== 2.8 Battery Analysis ==
	826
	827
	828	=== 2.8.1 Battery Type ===
	829
	830
65.18	831	(((
115.7	832	The N95S31B battery is a combination of an 8500mAh Li/SOCI2 Battery and a Super Capacitor. The battery is none-rechargeable battery type with a low discharge rate (<2% per year). This type of battery is commonly used in IoT devices such as water meter.
65.18	833	)))
4.2	834
65.18	835	(((
62.3	836	The battery is designed to last for several years depends on the actually use environment and update interval.
65.18	837	)))
4.2	838
65.18	839	(((
60.2	840	The battery related documents as below:
65.18	841	)))
4.2	842
60.2	843	* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
65.7	844	* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
60.2	845	* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
4.2	846
29.2	847	(((
95.2	848	[[image:image-20220709101450-2.png]]
29.2	849	)))
4.2	850
	851
35.18	852
122.1	853	=== 2.8.2 Power consumption Analyze ===
4.2	854
119.3	855
62.3	856	(((
119.3	857	The file DRAGINO_N95S31B-Power-Analyzer.pdf from [[https:~~/~~/www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i~~-~~-AyZcQkoua?dl=0>>https://www.dropbox.com/sh/mlpd6l05bogvaf6/AABwAJLMttqG7i--AyZcQkoua?dl=0]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
62.3	858	)))
4.2	859
62.3	860	(((
115.7	861
62.3	862	)))
4.2	863
	864
122.1	865	=== 2.8.3 Battery Note ===
4.2	866
119.3	867
31.6	868	(((
115.7	869	The Li-SICO battery is designed for small current / long period application. It is not good to use a high current, short period transmit method. The recommended minimum period for use of this battery is 5 minutes. If you use a shorter period time to uplink data, then the battery life may be decreased.
31.3	870	)))
4.2	871
	872
	873
122.1	874	=== 2.8.4 Replace the battery ===
31.2	875
115.8	876
62.2	877	(((
115.8	878	You can change the battery in the N95S31B.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won't be voltage drop between battery and main board.
62.2	879	)))
4.2	880
	881
115.8	882	(((
	883	The default battery pack of N95S31B includes a ER26500 plus super capacitor. If user can't find this pack locally, they can find ER26500 or equivalence without the SPC1520 capacitor, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes).
	884	)))
4.2	885
115.8	886
	887
63.2	888	= 3. Access NB-IoT Module =
4.2	889
119.3	890
63.2	891	(((
	892	Users can directly access the AT command set of the NB-IoT module.
	893	)))
	894
	895	(((
64.2	896	The AT Command set can refer the BC35-G NB-IoT Module AT Command: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/other_vendors/BC35-G/]]
119.3	897
	898
63.2	899	)))
	900
95.2	901	[[image:1657333200519-600.png]]
63.2	902
	903
	904
64.2	905	= 4. Using the AT Commands =
63.2	906
119.3	907
64.2	908	== 4.1 Access AT Commands ==
9.2	909
11.4	910
119.3	911	See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0>>https://www.dropbox.com/sh/jao1xt9kw5r3yq4/AAAMpJkZzExF2JLbRWxGoQ9Na?dl=0]]
4.2	912
119.3	913
64.2	914	AT+<CMD>? : Help on <CMD>
4.2	915
64.2	916	AT+<CMD> : Run <CMD>
4.2	917
64.2	918	AT+<CMD>=<value> : Set the value
4.2	919
64.2	920	AT+<CMD>=? : Get the value
4.2	921
	922
11.6	923	(% style="color:#037691" %)General Commands(%%)
4.2	924
64.2	925	AT : Attention
4.2	926
64.2	927	AT? : Short Help
4.2	928
64.2	929	ATZ : MCU Reset
4.2	930
64.2	931	AT+TDC : Application Data Transmission Interval
4.2	932
64.2	933	AT+CFG : Print all configurations
4.2	934
64.2	935	AT+CFGMOD : Working mode selection
4.2	936
64.2	937	AT+INTMOD : Set the trigger interrupt mode
4.2	938
64.2	939	AT+5VT : Set extend the time of 5V power
4.2	940
64.2	941	AT+PRO : Choose agreement
4.2	942
64.2	943	AT+WEIGRE : Get weight or set weight to 0
4.2	944
64.2	945	AT+WEIGAP : Get or Set the GapValue of weight
4.2	946
64.2	947	AT+RXDL : Extend the sending and receiving time
4.2	948
64.2	949	AT+CNTFAC : Get or set counting parameters
4.2	950
64.2	951	AT+SERVADDR : Server Address
4.2	952
122.1	953	AT+TR : Get or Set record time
4.2	954
122.1	955	AT+APN : Get or set the APN
	956
	957	AT+FBAND : Get or Set whether to automatically modify the frequency band
	958
	959	AT+DNSCFG : Get or Set DNS Server
	960
	961	AT+GETSENSORVALUE : Returns the current sensor measurement
	962
	963	AT+NOUD : Get or Set the number of data to be uploaded
	964
	965	AT+CDP : Read or Clear cached data
	966
	967	AT+SHTEMP: Get or Set alarm of temp
	968
	969	AT+SHHUM: Get or Set alarm of moisture
	970
64.2	971	(% style="color:#037691" %)COAP Management
4.2	972
64.2	973	AT+URI : Resource parameters
4.2	974
	975
64.2	976	(% style="color:#037691" %)UDP Management
4.2	977
64.2	978	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	979
	980
64.2	981	(% style="color:#037691" %)MQTT Management
4.2	982
64.2	983	AT+CLIENT : Get or Set MQTT client
4.2	984
64.2	985	AT+UNAME : Get or Set MQTT Username
4.2	986
64.2	987	AT+PWD : Get or Set MQTT password
4.2	988
64.2	989	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	990
64.2	991	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	992
	993
64.2	994	(% style="color:#037691" %)Information
4.2	995
64.2	996	AT+FDR : Factory Data Reset
4.2	997
64.2	998	AT+PWORD : Serial Access Password
4.2	999
	1000
	1001
64.4	1002	= 5. FAQ =
4.2	1003
119.3	1004
64.4	1005	== 5.1 How to Upgrade Firmware ==
6.3	1006
4.2	1007
31.35	1008	(((
64.4	1009	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	1010	)))
4.2	1011
31.35	1012	(((
64.4	1013	Please see this link for how to upgrade: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList>>http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H2.HardwareUpgradeMethodSupportList]]
31.35	1014	)))
4.2	1015
31.35	1016	(((
115.10	1017
	1018
115.34	1019	(((
119.3	1020	(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
31.35	1021	)))
115.34	1022	)))
4.2	1023
	1024
	1025
64.5	1026	= 6. Trouble Shooting =
4.2	1027
119.3	1028
64.5	1029	== 6.1 Connection problem when uploading firmware ==
4.9	1030
4.2	1031
65.20	1032	(((
	1033	Please see: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20Upgrade%20Instruction%20for%20STM32%20base%20products/#H3.3Troubleshooting]]
	1034	)))
	1035
64.5	1036	(% class="wikigeneratedid" %)
31.29	1037	(((
65.20	1038
31.29	1039	)))
4.2	1040
	1041
64.5	1042	== 6.2 AT Command input doesn't work ==
4.2	1043
119.3	1044
31.30	1045	(((
64.5	1046	In the case if user can see the console output but can't type input to the device. Please check if you already include the (% style="color:green" %)ENTER(%%) while sending out the command. Some serial tool doesn't send (% style="color:green" %)ENTER(%%) while press the send key, user need to add ENTER in their string.
65.22	1047
65.23	1048
31.30	1049	)))
4.2	1050
	1051
64.5	1052	= 7. Order Info =
4.2	1053
	1054
115.12	1055	Part Number: (% style="color:#4f81bd" %)N95S31B-YY
4.7	1056
4.2	1057
31.10	1058	(% class="wikigeneratedid" %)
	1059	(((
	1060
	1061	)))
	1062
65.2	1063	= 8. Packing Info =
4.2	1064
4.3	1065	(((
31.39	1066
	1067
31.40	1068	(% style="color:#037691" %)Package Includes:
64.5	1069
115.12	1070	* N95S31B NB-IoT Temperature and Humidity Sensor
64.5	1071	* External antenna x 1
4.3	1072	)))
4.2	1073
4.3	1074	(((
31.40	1075
	1076
	1077	(% style="color:#037691" %)Dimension and weight:
4.2	1078
95.3	1079	* Device Size: 13.0 x 5 x 4.5 cm
	1080	* Device Weight: 150g
115.13	1081	* Package Size / pcs : 14.0 x 8x 5 cm
	1082	* Weight / pcs : 180g
4.3	1083	)))
31.11	1084
64.5	1085	(((
31.11	1086
64.5	1087
	1088
	1089
4.3	1090	)))
4.2	1091
64.5	1092	= 9. Support =
4.2	1093
119.3	1094
4.2	1095	* Support is provided Monday to Friday, from 09:00 to 18:00 GMT+8. Due to different timezones we cannot offer live support. However, your questions will be answered as soon as possible in the before-mentioned schedule.
	1096	* Provide as much information as possible regarding your enquiry (product models, accurately describe your problem and steps to replicate it etc) and send a mail to [[support@dragino.com>>url:http://../../../../../../D:%5C%E5%B8%82%E5%9C%BA%E8%B5%84%E6%96%99%5C%E8%AF%B4%E6%98%8E%E4%B9%A6%5CLoRa%5CLT%E7%B3%BB%E5%88%97%5Csupport@dragino.com]]

Wiki source code of N95S31B NB-IoT Temperature & Humidity Sensor User Manual

Applications