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

Version 115.27 by Xiaoling on 2022/07/11 08:36

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