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

Version 103.1 by Xiaoling on 2022/07/09 15:10

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