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

Version 115.32 by Xiaoling on 2022/07/11 09:06

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