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

Version 116.3 by Xiaoling on 2022/07/11 09:42

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