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

Version 115.13 by Xiaoling on 2022/07/09 17:44

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