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

Version 130.1 by Bei Jinggeng on 2023/04/19 14:36

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

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

Applications