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

Version 115.30 by Xiaoling on 2022/07/11 08:39

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