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

Version 129.7 by Xiaoling on 2022/10/25 17:08

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