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

Version 100.2 by Xiaoling on 2022/07/09 14:53

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