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

Version 115.24 by Xiaoling on 2022/07/09 18:19

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