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

Version 124.1 by David Huang on 2022/09/08 16:38

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

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

Applications