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

Version 107.2 by Xiaoling on 2022/07/09 15:37

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