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

Version 115.19 by Xiaoling on 2022/07/09 18:14

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