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

Version 115.18 by Xiaoling on 2022/07/09 18:08

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