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

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