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

Version 118.5 by Xiaoling on 2022/07/12 17:31

version	line-number	content
74.2	1	(% style="text-align:center" %)
99.2	2	[[image:1657348034241-728.png\|\|height="470" width="470"]]
1.1	3
	4
	5
35.25	6
	7
99.2	8
	9
35.4	10	Table of Contents:
1.1	11
115.14	12	{{toc/}}
1.1	13
	14
	15
	16
31.17	17
44.2	18	= 1. Introduction =
1.1	19
99.2	20	== 1.1 What is N95S31B NB-IoT Sensor Node ==
1.1	21
12.2	22	(((
35.4	23
	24
115.25	25	(((
99.2	26	The Dragino N95S31B is a (% style="color:blue" %)NB-IoT Temperature and Humidity Sensor(%%) for Internet of Things solution. It is used to measure the (% style="color:blue" %)surrounding environment temperature and relative air humidity precisely(%%), and then upload to IoT server via NB-IoT network*.
115.25	27	)))
97.13	28
115.25	29	(((
99.2	30	The temperature & humidity sensor used in N95S31B is SHT31, which is fully calibrated, linearized, and temperature compensated digital output from Sensirion, it provides a strong reliability and long-term stability. The SHT31 is fixed in a (% style="color:blue" %)waterproof anti-condensation casing (%%)for long term use.
115.25	31	)))
97.13	32
115.25	33	(((
99.2	34	N95S31B supports different uplink methods include (% style="color:blue" %)TCP, MQTT, UDP and CoAP(%%) for different application requirement.
115.25	35	)))
97.13	36
115.25	37	(((
99.2	38	N95S31B is powered by(% style="color:blue" %)8500mAh Li-SOCI2 battery(%%), It is designed for long term use up to several years. (Real-world battery life depends on the use environment, update period. Please check related Power Analyze report).
115.25	39	)))
97.13	40
115.25	41	(((
	42
	43	)))
97.13	44
115.25	45	(((
99.2	46	~* make sure you have NB-IoT coverage locally.
115.25	47	)))
4.2	48
42.2	49
12.2	50	)))
4.2	51
99.2	52	[[image:1657348284168-431.png]]
4.2	53
	54
	55
65.3	56	== 1.2 Features ==
13.3	57
44.2	58	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
100.2	59	* Monitor Temperature & Humidity via SHT31
4.2	60	* AT Commands to change parameters
	61	* Uplink on periodically
	62	* Downlink to change configure
	63	* IP66 Waterproof Enclosure
100.2	64	* Ultra-Low Power consumption
	65	* AT Commands to change parameters
44.2	66	* Micro SIM card slot for NB-IoT SIM
	67	* 8500mAh Battery for long term use
4.2	68
115.27	69
118.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
115.28	96
118.2	97
44.2	98	== 1.4 Applications ==
4.2	99
75.4	100	* Smart Buildings & Home Automation
	101	* Logistics and Supply Chain Management
	102	* Smart Metering
4.2	103	* Smart Agriculture
75.4	104	* Smart Cities
	105	* Smart Factory
4.2	106
15.6	107	(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
	108
4.2	109
75.4	110
117.2	111	== 1.5 Pin Definitions & Switch ==
15.6	112
100.2	113	N95S31B use the mother board from NBSN95 which as below.
15.6	114
100.2	115	[[image:image-20220709144723-1.png]]
4.2	116
14.3	117
100.2	118	=== 1.5.1 Jumper JP2 ===
14.3	119
100.2	120	Power on Device when put this jumper.
14.3	121
100.2	122
	123
	124	=== 1.5.2 BOOT MODE / SW1 ===
	125
115.29	126	(((
100.2	127	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	128	)))
100.2	129
115.29	130	(((
100.2	131	2) Flash: work mode, device starts to work and send out console output for further debug
115.29	132	)))
100.2	133
	134
	135
	136	=== 1.5.3 Reset Button ===
	137
	138	Press to reboot the device.
	139
	140
	141
	142	=== 1.5.4 LED ===
	143
	144	It will flash:
	145
	146	1. When boot the device in flash mode
	147	1. Send an uplink packet
	148
115.30	149
100.2	150	= 2. Use N95S31B to communicate with IoT Server =
	151
45.2	152	== 2.1 How it works ==
14.3	153
100.3	154
15.3	155	(((
100.3	156	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	157	)))
4.2	158
45.2	159
15.3	160	(((
100.3	161	The diagram below shows the working flow in default firmware of N95S31B:
15.3	162	)))
4.2	163
77.2	164	(((
	165
	166	)))
4.2	167
118.2	168	[[image:1657520100595-569.png]]
77.2	169
45.2	170	(((
	171
	172	)))
4.2	173
45.2	174
102.2	175	== 2.2 Configure the N95S31B ==
4.2	176
48.2	177
102.2	178	=== 2.2.1 Power On N95S31B ===
	179
	180
	181	[[image:image-20220709150546-2.png]]
	182
102.3	183
45.4	184	=== 2.2.1 Test Requirement ===
4.2	185
	186
115.31	187	(((
102.3	188	To use N95S31B in your city, make sure meet below requirements:
115.31	189	)))
102.3	190
115.31	191	* (((
	192	Your local operator has already distributed a NB-IoT Network there.
	193	)))
	194	* (((
	195	The local NB-IoT network used the band that N95S31B supports.
	196	)))
	197	* (((
	198	Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
	199	)))
4.2	200
115.31	201	(((
102.3	202	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8.
115.31	203	)))
102.3	204
115.31	205	(((
102.3	206	N95S31B supports different communication protocol such as :
115.31	207	)))
102.3	208
48.2	209	(((
115.31	210	* (((
	211	CoAP ((% style="color:red" %)120.24.4.116:5683(%%))
	212	)))
	213	* (((
	214	raw UDP ((% style="color:red" %)120.24.4.116:5601(%%))
	215	)))
	216	* (((
	217	MQTT ((% style="color:red" %)120.24.4.116:1883(%%))
	218	)))
	219	* (((
	220	TCP ((% style="color:red" %)120.24.4.116:5600(%%))
	221	)))
102.3	222
115.31	223	(((
102.3	224	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	225	)))
102.3	226
	227
	228	)))
	229
103.2	230	[[image:1657350625843-586.png]]
4.2	231
	232
	233
104.2	234	=== 2.2.3 Insert SIM card ===
4.2	235
65.11	236	(((
45.4	237	Insert the NB-IoT Card get from your provider.
65.11	238	)))
4.2	239
65.11	240	(((
45.4	241	User need to take out the NB-IoT module and insert the SIM card like below:
65.11	242	)))
4.2	243
	244
104.2	245	[[image:1657351240556-536.png]]
4.2	246
	247
48.2	248
107.2	249	=== 2.2.4 Connect USB – TTL to N95S31B to configure it ===
4.2	250
48.2	251	(((
	252	(((
105.2	253	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.
48.2	254	)))
	255	)))
19.2	256
105.2	257	[[image:1657351312545-300.png]]
4.2	258
48.2	259	Connection:
4.2	260
45.6	261	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	262
45.6	263	(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
4.2	264
45.6	265	(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
4.2	266
	267
45.4	268	In the PC, use below serial tool settings:
	269
57.4	270	* Baud: (% style="color:green" %)9600
48.2	271	* Data bits: (% style="color:green" %)8(%%)
	272	* Stop bits: (% style="color:green" %)1
57.4	273	* Parity: (% style="color:green" %)None
48.2	274	* Flow Control: (% style="color:green" %)None
45.4	275
48.2	276	(((
105.2	277	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	278	)))
45.4	279
81.2	280	[[image:1657329814315-101.png]]
45.4	281
65.12	282	(((
105.2	283	(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]]
65.12	284	)))
45.4	285
	286
	287
107.2	288	=== 2.2.5 Use CoAP protocol to uplink data ===
45.4	289
56.2	290	(% 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	291
	292
97.9	293	(((
50.2	294	Use below commands:
97.9	295	)))
45.4	296
97.9	297	* (((
	298	(% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	299	)))
	300	* (((
	301	(% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
	302	)))
	303	* (((
	304	(% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/Set COAP resource path
	305	)))
45.4	306
97.9	307	(((
107.2	308
	309
45.4	310	For parameter description, please refer to AT command set
97.9	311	)))
45.4	312
107.2	313	[[image:1657352146020-183.png]]
45.4	314
	315
97.10	316	(((
86.2	317	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	318	)))
45.4	319
107.2	320	[[image:1657352185396-303.png]]
45.4	321
	322
50.2	323
107.2	324	=== 2.2.6 Use UDP protocol to uplink data(Default protocol) ===
45.4	325
	326
97.5	327	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
48.2	328	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
97.5	329	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/ If the server does not respond, this command is unnecessary
45.4	330
111.2	331	[[image:1657352391268-297.png]]
45.4	332
	333
111.2	334	[[image:1657352403317-397.png]]
45.4	335
52.3	336
86.2	337
111.2	338	=== 2.2.7 Use MQTT protocol to uplink data ===
45.4	339
113.2	340	N95S31B supports only plain MQTT now it doesn't support TLS and other related encryption.
45.4	341
97.11	342	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/Set to use MQTT protocol to uplink
	343	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/Set MQTT server address and port
	344	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/Set up the CLIENT of MQTT
97.13	345	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/Set the username of MQTT
	346	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/Set the password of MQTT
114.2	347	* (% style="color:blue" %)AT+PUBTOPIC=f9527 (%%)~/~/Set the sending topic of MQTT
	348	* (% style="color:blue" %)AT+SUBTOPIC=Ns9527 (%%) ~/~/Set the subscription topic of MQTT
45.4	349
111.2	350	[[image:1657352634421-276.png]]
45.4	351
54.2	352
111.2	353	[[image:1657352645687-385.png]]
54.2	354
111.2	355	(((
	356	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.
	357	)))
45.4	358
111.2	359
54.3	360	(((
111.2	361	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	362	)))
45.4	363
	364
54.3	365
113.2	366	=== 2.2.8 Use TCP protocol to uplink data ===
45.4	367
113.2	368	This feature is supported since firmware version v110
45.4	369
56.2	370	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	371	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	372
113.2	373	[[image:1657352898400-901.png]]
45.4	374
	375
113.2	376	[[image:1657352914475-252.png]]
45.4	377
57.6	378
89.2	379
113.2	380	=== 2.2.9 Change Update Interval ===
45.4	381
48.2	382	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	383
56.3	384	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	385
56.3	386	(((
113.2	387
56.3	388	)))
45.4	389
	390
	391
57.2	392	== 2.3 Uplink Payload ==
4.2	393
32.9	394
115.32	395	(((
114.2	396	NBSN95 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	397	)))
90.2	398
114.2	399
115.32	400	(((
114.2	401	For example:
115.32	402	)))
114.2	403
115.32	404	(((
114.2	405	(% style="color:blue" %)AT+CFGMOD=2 (%%)~/~/will set the NBSN95 to work in MOD=2 distance mode which target to measure distance via Ultrasonic Sensor.
115.32	406	)))
114.2	407
	408
115.32	409	(((
114.2	410	The uplink payloads are composed in ASCII String. For example:
115.32	411	)))
114.2	412
115.32	413	(((
114.2	414	0a cd 00 ed 0a cc 00 00 ef 02 d2 1d (total 24 ASCII Chars) . Representative the actually payload:
115.32	415	)))
114.2	416
115.32	417	(((
114.2	418	0x 0a cd 00 ed 0a cc 00 00 ef 02 d2 1d Total 12 bytes
115.32	419	)))
114.2	420
	421
115.32	422	(((
114.2	423	(% style="color:red" %)NOTE:
115.32	424	)))
114.2	425
	426	(% style="color:red" %)
115.32	427	1. (((
	428	All modes share the same Payload Explanation from [[HERE>>\|\|anchor="H2.3A0UplinkPayload"]].
	429	)))
	430	1. (((
	431	By default, the device will send an uplink message every 1 hour.
118.4	432
	433
	434
	435
115.32	436	)))
114.2	437
	438	=== 2.3.1 Payload Analyze ===
	439
	440	N95S31B uplink payload includes in total 21 bytes
	441
	442
115.17	443	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:520px" %)
115.19	444	\|=(% style="width: 60px;" %)(((
57.2	445	Size(bytes)
115.23	446	)))\|=(% 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	447	\|(% 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	448	(((
114.2	449	Reserve/ Same as NBSN95 CFGMOD=1
115.21	450	)))
57.2	451
115.21	452	(((
114.2	453	No function here.
115.21	454	)))
114.2	455	)))\|(% style="width:77px" %)(((
115.21	456	(((
115.15	457	[[Temperature >>\|\|anchor="H2.3.6A0Temperature26Humidity"]]
115.21	458	)))
114.2	459
115.21	460	(((
114.2	461	By SHT31
115.21	462	)))
114.2	463	)))\|(% style="width:80px" %)(((
115.21	464	(((
115.15	465	[[Humidity>>\|\|anchor="H2.3.6A0Temperature26Humidity"]]
115.21	466	)))
114.2	467
115.21	468	(((
114.2	469	By SHT31
	470	)))
115.21	471	)))
114.2	472
65.13	473	(((
114.2	474	(((
	475	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	476	)))
114.2	477	)))
57.2	478
	479
114.2	480	[[image:1657354294009-643.png]]
57.2	481
	482
115.2	483	The payload is ASCII string, representative same HEX: 0x724031607457006e0ccd1b0100dc000ccc00e10186 where:
57.2	484
115.2	485	* Device ID: 0x724031607457 = 724031607457
	486	* Version: 0x006e=110=1.1.0
57.2	487
115.2	488	* BAT: 0x0ccd = 3277 mV = 3.277V
	489	* Signal: 0x1b = 27
	490	* Model: 0x01 = 1
	491	* 0x00dc000ccc= reserve, ignore in N95S31B
	492	* Temperature by SHT31: 0x00e1 = 225 = 22.5 °C
	493	* Humidity by SHT31: 0x0186 = 390 = 39.0 %rh
	494
	495	(((
	496
90.2	497	)))
95.5	498
115.2	499	(((
95.5	500
90.2	501	)))
57.2	502
4.2	503
115.2	504	=== 2.3.2 Device ID ===
57.7	505
65.13	506	(((
57.3	507	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	508	)))
4.2	509
65.13	510	(((
57.4	511	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
65.13	512	)))
4.2	513
65.13	514	(((
57.3	515	Example:
65.13	516	)))
4.2	517
65.13	518	(((
57.3	519	AT+DEUI=A84041F15612
65.13	520	)))
4.2	521
65.13	522	(((
91.1	523	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
65.13	524	)))
22.2	525
4.2	526
	527
115.2	528	=== 2.3.3 Version Info ===
57.5	529
116.2	530	(((
115.2	531	These bytes include the hardware and software version.
116.2	532	)))
115.2	533
116.2	534	(((
115.2	535	Higher byte: Specify hardware version: always 0x00 for N95S31B
116.2	536	)))
115.2	537
116.2	538	(((
115.2	539	Lower byte: Specify the software version: 0x6E=110, means firmware version 110
116.2	540	)))
115.2	541
116.2	542	(((
	543
	544	)))
115.2	545
116.2	546	(((
115.2	547	For example: 0x00 6E: this device is N95S31B with firmware version 110.
116.2	548	)))
115.2	549
65.13	550	(((
115.2	551
65.13	552	)))
4.2	553
	554
115.2	555	=== 2.3.4 Battery Info ===
57.3	556
32.10	557	(((
4.2	558	Ex1: 0x0B45 = 2885mV
32.10	559	)))
4.2	560
32.10	561	(((
4.2	562	Ex2: 0x0B49 = 2889mV
32.10	563	)))
4.2	564
	565
	566
115.2	567	=== 2.3.5 Signal Strength ===
4.2	568
65.13	569	(((
57.6	570	NB-IoT Network signal Strength.
65.13	571	)))
57.6	572
65.13	573	(((
57.6	574	Ex1: 0x1d = 29
65.13	575	)))
57.6	576
65.13	577	(((
57.6	578	(% style="color:blue" %)0(%%) -113dBm or less
65.13	579	)))
57.6	580
65.13	581	(((
57.6	582	(% style="color:blue" %)1(%%) -111dBm
65.13	583	)))
57.6	584
65.13	585	(((
57.6	586	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	587	)))
57.6	588
65.13	589	(((
57.6	590	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	591	)))
57.6	592
65.13	593	(((
57.6	594	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	595	)))
57.6	596
	597
	598
115.2	599	=== 2.3.6 Temperature & Humidity ===
57.6	600
115.2	601	The device will be able to get the SHT31 temperature and humidity data now and upload to IoT Server.
4.2	602
115.2	603	[[image:image-20220709161741-3.png]]
4.2	604
	605
115.2	606	Convert the read byte to decimal and divide it by ten.
4.2	607
23.2	608
115.2	609	Example:
23.2	610
115.2	611	Temperature: Read:00ec (H) = 236(D) Value: 236 /10=23.6℃
4.2	612
115.2	613	Humidity: Read:0295(H)=661(D) Value: 661 / 10=66.1, So 66.1%
4.2	614
	615
	616
115.14	617	== 2.4 Downlink Payload ==
4.2	618
118.5	619	By default, N95S31B prints the downlink payload to console port.
4.2	620
92.2	621	[[image:image-20220709100028-1.png]]
4.2	622
	623
32.14	624	(((
40.4	625	(% style="color:blue" %)Examples:
32.14	626	)))
4.2	627
32.14	628	(((
	629
	630	)))
4.2	631
32.14	632	* (((
40.4	633	(% style="color:blue" %)Set TDC
32.14	634	)))
4.2	635
32.14	636	(((
60.2	637	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	638	)))
4.2	639
32.14	640	(((
4.2	641	Payload: 01 00 00 1E TDC=30S
32.14	642	)))
4.2	643
32.14	644	(((
4.2	645	Payload: 01 00 00 3C TDC=60S
32.14	646	)))
4.2	647
32.14	648	(((
	649
	650	)))
4.2	651
32.14	652	* (((
40.4	653	(% style="color:blue" %)Reset
32.14	654	)))
4.2	655
32.14	656	(((
118.5	657	If payload = 0x04FF, it will reset the N95S31B
32.14	658	)))
4.2	659
	660
60.2	661	* (% style="color:blue" %)INTMOD
4.2	662
65.17	663	(((
60.2	664	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	665	)))
4.2	666
	667
26.2	668
115.5	669	== 2.5 Battery Analysis ==
4.2	670
115.5	671	=== 2.5.1 Battery Type ===
4.2	672
	673
65.18	674	(((
115.7	675	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	676	)))
4.2	677
65.18	678	(((
62.3	679	The battery is designed to last for several years depends on the actually use environment and update interval.
65.18	680	)))
4.2	681
65.18	682	(((
60.2	683	The battery related documents as below:
65.18	684	)))
4.2	685
60.2	686	* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
65.7	687	* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
60.2	688	* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
4.2	689
29.2	690	(((
95.2	691	[[image:image-20220709101450-2.png]]
29.2	692	)))
4.2	693
	694
35.18	695
115.6	696	=== 2.5.2 Power consumption Analyze ===
4.2	697
62.3	698	(((
115.7	699	The file DRAGINO_N95S31B-Power-Analyzer.pdf from [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/N95S31B/]] describes a detail measurement to analyze the power consumption in different case. User can use it for design guideline for their project.
62.3	700	)))
4.2	701
62.3	702	(((
115.7	703
62.3	704	)))
4.2	705
	706
115.6	707	=== 2.5.3 Battery Note ===
4.2	708
31.6	709	(((
115.7	710	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	711	)))
4.2	712
	713
	714
115.6	715	=== 2.5.4 Replace the battery ===
31.2	716
115.8	717
62.2	718	(((
115.8	719	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	720	)))
4.2	721
	722
115.8	723	(((
	724	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).
	725	)))
4.2	726
115.8	727
	728
63.2	729	= 3. Access NB-IoT Module =
4.2	730
63.2	731	(((
	732	Users can directly access the AT command set of the NB-IoT module.
	733	)))
	734
	735	(((
64.2	736	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/]]
63.2	737	)))
	738
95.2	739	[[image:1657333200519-600.png]]
63.2	740
	741
	742
64.2	743	= 4. Using the AT Commands =
63.2	744
64.2	745	== 4.1 Access AT Commands ==
9.2	746
115.9	747	See NBSN95 AT Command in this link for detail: [[https:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/>>url:https://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN95/]]
11.4	748
4.2	749
64.2	750	AT+<CMD>? : Help on <CMD>
4.2	751
64.2	752	AT+<CMD> : Run <CMD>
4.2	753
64.2	754	AT+<CMD>=<value> : Set the value
4.2	755
64.2	756	AT+<CMD>=? : Get the value
4.2	757
	758
11.6	759	(% style="color:#037691" %)General Commands(%%)
4.2	760
64.2	761	AT : Attention
4.2	762
64.2	763	AT? : Short Help
4.2	764
64.2	765	ATZ : MCU Reset
4.2	766
64.2	767	AT+TDC : Application Data Transmission Interval
4.2	768
64.2	769	AT+CFG : Print all configurations
4.2	770
64.2	771	AT+CFGMOD : Working mode selection
4.2	772
64.2	773	AT+INTMOD : Set the trigger interrupt mode
4.2	774
64.2	775	AT+5VT : Set extend the time of 5V power
4.2	776
64.2	777	AT+PRO : Choose agreement
4.2	778
64.2	779	AT+WEIGRE : Get weight or set weight to 0
4.2	780
64.2	781	AT+WEIGAP : Get or Set the GapValue of weight
4.2	782
64.2	783	AT+RXDL : Extend the sending and receiving time
4.2	784
64.2	785	AT+CNTFAC : Get or set counting parameters
4.2	786
64.2	787	AT+SERVADDR : Server Address
4.2	788
	789
64.2	790	(% style="color:#037691" %)COAP Management
4.2	791
64.2	792	AT+URI : Resource parameters
4.2	793
	794
64.2	795	(% style="color:#037691" %)UDP Management
4.2	796
64.2	797	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	798
	799
64.2	800	(% style="color:#037691" %)MQTT Management
4.2	801
64.2	802	AT+CLIENT : Get or Set MQTT client
4.2	803
64.2	804	AT+UNAME : Get or Set MQTT Username
4.2	805
64.2	806	AT+PWD : Get or Set MQTT password
4.2	807
64.2	808	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	809
64.2	810	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	811
	812
64.2	813	(% style="color:#037691" %)Information
4.2	814
64.2	815	AT+FDR : Factory Data Reset
4.2	816
64.2	817	AT+PWORD : Serial Access Password
4.2	818
	819
	820
64.4	821	= 5. FAQ =
4.2	822
64.4	823	== 5.1 How to Upgrade Firmware ==
6.3	824
4.2	825
31.35	826	(((
64.4	827	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	828	)))
4.2	829
31.35	830	(((
64.4	831	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	832	)))
4.2	833
31.35	834	(((
115.10	835
	836
115.34	837	(((
115.10	838	(% style="color:red" %)Notice, N95S31B and LSN50v2 share the same mother board. They use the same connection and method to update.
31.35	839	)))
115.34	840	)))
4.2	841
	842
	843
64.5	844	= 6. Trouble Shooting =
4.2	845
64.5	846	== 6.1 Connection problem when uploading firmware ==
4.9	847
4.2	848
65.20	849	(((
	850	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]]
	851	)))
	852
64.5	853	(% class="wikigeneratedid" %)
31.29	854	(((
65.20	855
31.29	856	)))
4.2	857
	858
64.5	859	== 6.2 AT Command input doesn't work ==
4.2	860
31.30	861	(((
64.5	862	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	863
65.23	864
31.30	865	)))
4.2	866
	867
64.5	868	= 7. Order Info =
4.2	869
	870
115.12	871	Part Number: (% style="color:#4f81bd" %)N95S31B-YY
4.7	872
4.2	873
31.10	874	(% class="wikigeneratedid" %)
	875	(((
	876
	877	)))
	878
65.2	879	= 8. Packing Info =
4.2	880
4.3	881	(((
31.39	882
	883
31.40	884	(% style="color:#037691" %)Package Includes:
64.5	885
115.12	886	* N95S31B NB-IoT Temperature and Humidity Sensor
64.5	887	* External antenna x 1
4.3	888	)))
4.2	889
4.3	890	(((
31.40	891
	892
	893	(% style="color:#037691" %)Dimension and weight:
4.2	894
95.3	895	* Device Size: 13.0 x 5 x 4.5 cm
	896	* Device Weight: 150g
115.13	897	* Package Size / pcs : 14.0 x 8x 5 cm
	898	* Weight / pcs : 180g
4.3	899	)))
31.11	900
64.5	901	(((
31.11	902
64.5	903
	904
	905
4.3	906	)))
4.2	907
64.5	908	= 9. Support =
4.2	909
	910	* 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.
	911	* 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