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

Version 115.2 by Xiaoling on 2022/07/09 16:18

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