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

Version 100.1 by Xiaoling on 2022/07/09 14:47

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