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

Version 130.5 by Xiaoling on 2023/04/28 13:51

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

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

Applications