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

Version 127.1 by Edwin Chen on 2022/10/09 00:07

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

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

Applications