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

Version 129.34 by Xiaoling on 2022/12/30 11:21

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

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

Applications