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

Version 129.4 by Xiaoling on 2022/10/25 17:00

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