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

Version 115.1 by Xiaoling on 2022/07/09 16:17

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