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

Version 102.1 by Xiaoling on 2022/07/09 15:05

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