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

Version 119.2 by Xiaoling on 2022/08/22 14:47

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