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

Version 129.2 by Xiaoling on 2022/10/14 17:59

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