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

Version 102.2 by Xiaoling on 2022/07/09 15:06

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