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

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