Wiki source code of NDDS75 NB-IoT Distance Detect Sensor User Manual

Version 72.1 by Xiaoling on 2022/07/09 08:45

version	line-number	content
71.1	1	[[image:image-20220709084207-3.jpeg\|\|height="548" width="548"]]
1.1	2
	3
	4
35.25	5
	6
	7
	8
35.4	9	Table of Contents:
1.1	10
	11
	12
	13
	14
31.17	15
65.3	16
44.2	17	= 1. Introduction =
1.1	18
67.2	19	== 1.1 What is NDDS75 Distance Detection Sensor ==
1.1	20
12.2	21	(((
35.4	22
	23
65.9	24	(((
68.2	25	The Dragino NDDS75 is a (% style="color:blue" %)NB-IoT Distance Detection Sensor(%%) for Internet of Things solution. It is designed to measure the distance between the sensor and a flat object. The distance detection sensor is a module that uses ultrasonic sensing technology for distance measurement, and temperature compensation is performed internally to improve the reliability of data.
	26	\\The NDDS75 can be applied to scenarios such as horizontal distance measurement, liquid level measurement, parking management system, object proximity and presence detection, intelligent trash can management system, robot obstacle avoidance, automatic control, sewer, bottom water level monitoring, etc. It detects the distance between the measured object and the sensor, and uploads the value via wireless to IoT Server via NB-IoT Network.
	27	\\NarrowBand-Internet of Things (NB-IoT) is a standards-based low power wide area (LPWA) technology developed to enable a wide range of new IoT devices and services. NB-IoT significantly improves the power consumption of user devices, system capacity and spectrum efficiency, especially in deep coverage.
	28	\\NDDS75 supports different uplink methods include (% style="color:blue" %)TCP, MQTT, UDP and CoAP (%%)for different application requirement.
	29	\\NDDS75 is powered by (% style="color:blue" %)8500mAh Li-SOCI2 battery(%%), It is designed for long term use up to 5 years. (Actually Battery life depends on the use environment, update period & uplink method)
	30	\\To use NDDS75, user needs to check if there is NB-IoT coverage in local area and with the bands NDDS75 supports. If the local operate support it, user needs to get a NB-IoT SIM card from local operator and install NDDS75 to get NB-IoT network connection.
65.9	31	)))
4.2	32
42.2	33
12.2	34	)))
4.2	35
12.2	36	[[image:1654503236291-817.png]]
4.2	37
	38
42.2	39	[[image:1657245163077-232.png]]
4.2	40
	41
	42
65.3	43	== 1.2 Features ==
13.3	44
44.2	45	* NB-IoT Bands: B1/B3/B8/B5/B20/B28 @H-FDD
4.2	46	* Monitor Soil Moisture
	47	* Monitor Soil Temperature
	48	* Monitor Soil Conductivity
	49	* AT Commands to change parameters
	50	* Uplink on periodically
	51	* Downlink to change configure
	52	* IP66 Waterproof Enclosure
44.2	53	* Ultra-Low Power consumption
	54	* AT Commands to change parameters
	55	* Micro SIM card slot for NB-IoT SIM
	56	* 8500mAh Battery for long term use
4.2	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
65.3	75	Probe(% style="color:#037691" %) Specification:
65.2	76
4.2	77	Measure Volume: Base on the centra pin of the probe, a cylinder with 7cm diameter and 10cm height.
	78
44.2	79	[[image:image-20220708101224-1.png]]
14.2	80
4.2	81
	82
44.2	83	== 1.4 Applications ==
4.2	84
	85	* Smart Agriculture
	86
15.6	87	(% class="wikigeneratedid" id="H200B1.5FirmwareChangelog" %)
	88
4.2	89
44.2	90	== 1.5 Pin Definitions ==
15.6	91
	92
44.2	93	[[image:1657246476176-652.png]]
4.2	94
14.3	95
	96
45.2	97	= 2. Use NSE01 to communicate with IoT Server =
14.3	98
45.2	99	== 2.1 How it works ==
14.3	100
45.2	101
15.3	102	(((
45.2	103	The NSE01 is equipped with a NB-IoT module, the pre-loaded firmware in NSE01 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 NSE01.
15.3	104	)))
4.2	105
45.2	106
15.3	107	(((
45.2	108	The diagram below shows the working flow in default firmware of NSE01:
15.3	109	)))
4.2	110
45.2	111	[[image:image-20220708101605-2.png]]
4.2	112
45.2	113	(((
	114
	115	)))
4.2	116
45.2	117
	118
45.4	119	== 2.2 Configure the NSE01 ==
4.2	120
48.2	121
45.4	122	=== 2.2.1 Test Requirement ===
4.2	123
	124
65.10	125	(((
45.4	126	To use NSE01 in your city, make sure meet below requirements:
65.10	127	)))
4.2	128
45.4	129	* Your local operator has already distributed a NB-IoT Network there.
	130	* The local NB-IoT network used the band that NSE01 supports.
	131	* Your operator is able to distribute the data received in their NB-IoT network to your IoT server.
4.2	132
48.2	133	(((
45.4	134	Below figure shows our testing structure. Here we have NB-IoT network coverage by China Mobile, the band they use is B8. The NSE01 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	135	)))
4.2	136
	137
48.2	138	[[image:1657249419225-449.png]]
4.2	139
	140
	141
45.5	142	=== 2.2.2 Insert SIM card ===
4.2	143
65.11	144	(((
45.4	145	Insert the NB-IoT Card get from your provider.
65.11	146	)))
4.2	147
65.11	148	(((
45.4	149	User need to take out the NB-IoT module and insert the SIM card like below:
65.11	150	)))
4.2	151
	152
48.2	153	[[image:1657249468462-536.png]]
4.2	154
	155
48.2	156
45.5	157	=== 2.2.3 Connect USB – TTL to NSE01 to configure it ===
4.2	158
48.2	159	(((
	160	(((
	161	User need to configure NSE01 via serial port to set the (% style="color:blue" %)Server Address / Uplink Topic (%%)to define where and how-to uplink packets. NSE01 support AT Commands, user can use a USB to TTL adapter to connect to NSE01 and use AT Commands to configure it, as below.
	162	)))
	163	)))
19.2	164
4.2	165
48.2	166	Connection:
4.2	167
45.6	168	(% style="background-color:yellow" %)USB TTL GND <~-~-~-~-> GND
4.2	169
45.6	170	(% style="background-color:yellow" %)USB TTL TXD <~-~-~-~-> UART_RXD
4.2	171
45.6	172	(% style="background-color:yellow" %)USB TTL RXD <~-~-~-~-> UART_TXD
4.2	173
	174
45.4	175	In the PC, use below serial tool settings:
	176
57.4	177	* Baud: (% style="color:green" %)9600
48.2	178	* Data bits: (% style="color:green" %)8(%%)
	179	* Stop bits: (% style="color:green" %)1
57.4	180	* Parity: (% style="color:green" %)None
48.2	181	* Flow Control: (% style="color:green" %)None
45.4	182
48.2	183	(((
	184	Make sure the switch is in FLASH position, then power on device by connecting the jumper on NSE01. NSE01 will output system info once power on as below, we can enter the (% style="color:green" %)password: 12345678(%%) to access AT Command input.
	185	)))
45.4	186
48.2	187	[[image:image-20220708110657-3.png]]
45.4	188
65.12	189	(((
48.2	190	(% style="color:red" %)Note: the valid AT Commands can be found at: (%%)[[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
65.12	191	)))
45.4	192
	193
	194
48.2	195	=== 2.2.4 Use CoAP protocol to uplink data ===
45.4	196
56.2	197	(% 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	198
	199
50.2	200	Use below commands:
45.4	201
48.2	202	* (% style="color:blue" %)AT+PRO=1 (%%) ~/~/ Set to use CoAP protocol to uplink
	203	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5683 (%%)~/~/ to set CoAP server address and port
	204	* (% style="color:blue" %)AT+URI=5,11,"mqtt",11,"coap",12,"0",15,"c=text1",23,"0" (%%) ~/~/Set COAP resource path
45.4	205
	206	For parameter description, please refer to AT command set
	207
50.2	208	[[image:1657249793983-486.png]]
45.4	209
	210
48.2	211	After configure the server address and (% style="color:green" %)reset the device(%%) (via AT+ATZ ), NSE01 will start to uplink sensor values to CoAP server.
45.4	212
50.2	213	[[image:1657249831934-534.png]]
45.4	214
	215
50.2	216
45.6	217	=== 2.2.5 Use UDP protocol to uplink data(Default protocol) ===
45.4	218
	219	This feature is supported since firmware version v1.0.1
	220
	221
48.2	222	* (% style="color:blue" %)AT+PRO=2 (%%) ~/~/ Set to use UDP protocol to uplink
	223	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5601 (%%) ~/~/ to set UDP server address and port
	224	* (% style="color:blue" %)AT+CFM=1 (%%) ~/~/If the server does not respond, this command is unnecessary
45.4	225
52.2	226	[[image:1657249864775-321.png]]
45.4	227
	228
52.2	229	[[image:1657249930215-289.png]]
45.4	230
	231
52.3	232
45.7	233	=== 2.2.6 Use MQTT protocol to uplink data ===
45.4	234
	235	This feature is supported since firmware version v110
	236
	237
54.3	238	* (% style="color:blue" %)AT+PRO=3 (%%) ~/~/Set to use MQTT protocol to uplink
	239	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,1883 (%%) ~/~/Set MQTT server address and port
	240	* (% style="color:blue" %)AT+CLIENT=CLIENT (%%)~/~/Set up the CLIENT of MQTT
57.2	241	* (% style="color:blue" %)AT+UNAME=UNAME (%%)~/~/Set the username of MQTT
	242	* (% style="color:blue" %)AT+PWD=PWD (%%)~/~/Set the password of MQTT
	243	* (% style="color:blue" %)AT+PUBTOPIC=NSE01_PUB (%%)~/~/Set the sending topic of MQTT
54.3	244	* (% style="color:blue" %)AT+SUBTOPIC=NSE01_SUB (%%) ~/~/Set the subscription topic of MQTT
45.4	245
54.2	246	[[image:1657249978444-674.png]]
45.4	247
54.2	248
	249	[[image:1657249990869-686.png]]
	250
45.4	251
54.3	252	(((
45.4	253	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	254	)))
45.4	255
	256
54.3	257
45.7	258	=== 2.2.7 Use TCP protocol to uplink data ===
45.4	259
	260	This feature is supported since firmware version v110
	261
	262
56.2	263	* (% style="color:blue" %)AT+PRO=4 (%%) ~/~/ Set to use TCP protocol to uplink
48.2	264	* (% style="color:blue" %)AT+SERVADDR=120.24.4.116,5600 (%%) ~/~/ to set TCP server address and port
45.4	265
56.2	266	[[image:1657250217799-140.png]]
45.4	267
	268
56.2	269	[[image:1657250255956-604.png]]
45.4	270
	271
57.6	272
45.7	273	=== 2.2.8 Change Update Interval ===
45.4	274
48.2	275	User can use below command to change the (% style="color:green" %)uplink interval.
45.4	276
56.3	277	* (% style="color:blue" %)AT+TDC=600 (%%)~/~/ Set Update Interval to 600s
45.4	278
56.3	279	(((
48.2	280	(% style="color:red" %)NOTE:
56.3	281	)))
45.4	282
56.3	283	(((
45.7	284	(% style="color:red" %)1. By default, the device will send an uplink message every 1 hour.
56.3	285	)))
45.4	286
	287
	288
57.2	289	== 2.3 Uplink Payload ==
4.2	290
57.2	291	In this mode, uplink payload includes in total 18 bytes
32.9	292
57.2	293	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
65.12	294	\|=(% style="width: 60px;" %)(((
57.2	295	Size(bytes)
65.12	296	)))\|=(% style="width: 50px;" %)6\|=(% style="width: 25px;" %)2\|=(% style="width: 25px;" %)2\|=(% style="width: 70px;" %)1\|=(% style="width: 60px;" %)2\|=(% style="width: 80px;" %)2\|=(% style="width: 90px;" %)2\|=(% style="width: 50px;" %)1
65.4	297	\|(% 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:108px" %)[[Soil Moisture>>\|\|anchor="H2.4.5A0SoilMoisture"]]\|(% style="width:133px" %)[[Soil Temperature>>\|\|anchor="H2.4.6A0SoilTemperature"]]\|(% style="width:159px" %)[[Soil Conductivity(EC)>>\|\|anchor="H2.4.7A0SoilConductivity28EC29"]]\|(% style="width:80px" %)[[Interrupt>>\|\|anchor="H2.4.8A0DigitalInterrupt"]]
57.2	298
65.13	299	(((
57.2	300	If we use the MQTT client to subscribe to this MQTT topic, we can see the following information when the NSE01 uplink data.
65.13	301	)))
57.2	302
	303
	304	[[image:image-20220708111918-4.png]]
	305
	306
	307	The payload is ASCII string, representative same HEX:
	308
	309	0x72403155615900640c7817075e0a8c02f900 where:
	310
	311	* Device ID: 0x 724031556159 = 724031556159
	312	* Version: 0x0064=100=1.0.0
	313
	314	* BAT: 0x0c78 = 3192 mV = 3.192V
	315	* Singal: 0x17 = 23
	316	* Soil Moisture: 0x075e= 1886 = 18.86 %
	317	* Soil Temperature:0x0a8c =2700=27 °C
	318	* Soil Conductivity(EC) = 0x02f9 =761 uS /cm
	319	* Interrupt: 0x00 = 0
	320
57.3	321	== 2.4 Payload Explanation and Sensor Interface ==
4.2	322
57.7	323
57.5	324	=== 2.4.1 Device ID ===
4.2	325
65.13	326	(((
57.3	327	By default, the Device ID equal to the last 6 bytes of IMEI.
65.13	328	)))
4.2	329
65.13	330	(((
57.4	331	User can use (% style="color:blue" %)AT+DEUI(%%) to set Device ID
65.13	332	)))
4.2	333
65.13	334	(((
57.3	335	Example:
65.13	336	)))
4.2	337
65.13	338	(((
57.3	339	AT+DEUI=A84041F15612
65.13	340	)))
4.2	341
65.13	342	(((
57.3	343	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
65.13	344	)))
22.2	345
4.2	346
	347
57.5	348	=== 2.4.2 Version Info ===
	349
65.13	350	(((
57.3	351	Specify the software version: 0x64=100, means firmware version 1.00.
65.13	352	)))
4.2	353
65.13	354	(((
57.3	355	For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
65.13	356	)))
4.2	357
	358
57.3	359
57.5	360	=== 2.4.3 Battery Info ===
22.2	361
32.10	362	(((
4.2	363	Check the battery voltage for LSE01.
32.10	364	)))
4.2	365
32.10	366	(((
4.2	367	Ex1: 0x0B45 = 2885mV
32.10	368	)))
4.2	369
32.10	370	(((
4.2	371	Ex2: 0x0B49 = 2889mV
32.10	372	)))
4.2	373
	374
	375
57.6	376	=== 2.4.4 Signal Strength ===
4.2	377
65.13	378	(((
57.6	379	NB-IoT Network signal Strength.
65.13	380	)))
57.6	381
65.13	382	(((
57.6	383	Ex1: 0x1d = 29
65.13	384	)))
57.6	385
65.13	386	(((
57.6	387	(% style="color:blue" %)0(%%) -113dBm or less
65.13	388	)))
57.6	389
65.13	390	(((
57.6	391	(% style="color:blue" %)1(%%) -111dBm
65.13	392	)))
57.6	393
65.13	394	(((
57.6	395	(% style="color:blue" %)2...30(%%) -109dBm... -53dBm
65.13	396	)))
57.6	397
65.13	398	(((
57.6	399	(% style="color:blue" %)31 (%%) -51dBm or greater
65.13	400	)))
57.6	401
65.13	402	(((
57.6	403	(% style="color:blue" %)99 (%%) Not known or not detectable
65.13	404	)))
57.6	405
	406
	407
	408	=== 2.4.5 Soil Moisture ===
	409
32.10	410	(((
65.13	411	(((
4.2	412	Get the moisture content of the soil. The value range of the register is 0-10000(Decimal), divide this value by 100 to get the percentage of moisture in the soil.
32.10	413	)))
65.13	414	)))
4.2	415
32.10	416	(((
65.13	417	(((
57.6	418	For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
32.10	419	)))
65.13	420	)))
4.2	421
32.10	422	(((
	423
	424	)))
4.2	425
32.10	426	(((
22.4	427	(% style="color:#4f81bd" %)05DC(H) = 1500(D) /100 = 15%.
32.10	428	)))
4.2	429
22.4	430
4.2	431
57.6	432	=== 2.4.6 Soil Temperature ===
22.5	433
32.11	434	(((
65.14	435	Get the temperature in the soil. The value range of the register is -4000 - +800(Decimal), divide this value by 100 to get the temperature in the soil. For example, if the data you get from the register is __0x09 0xEC__, the temperature content in the soil is
32.11	436	)))
4.2	437
32.11	438	(((
4.2	439	Example:
32.11	440	)))
4.2	441
32.11	442	(((
4.2	443	If payload is 0105H: ((0x0105 & 0x8000)>>15 === 0),temp = 0105(H)/100 = 2.61 °C
32.11	444	)))
4.2	445
32.11	446	(((
4.2	447	If payload is FF7EH: ((FF7E & 0x8000)>>15 ===1),temp = (FF7E(H)-FFFF(H))/100 = -1.29 °C
32.11	448	)))
4.2	449
	450
	451
57.6	452	=== 2.4.7 Soil Conductivity (EC) ===
22.6	453
23.2	454	(((
	455	Obtain (% style="color:#4f81bd" %)__soluble salt concentration__(%%) in soil or (% style="color:#4f81bd" %)__soluble ion concentration in liquid fertilizer__(%%) or (% style="color:#4f81bd" %)__planting medium__(%%). The value range of the register is 0 - 20000(Decimal)( Can be greater than 20000).
	456	)))
4.2	457
23.2	458	(((
57.6	459	For example, if the data you get from the register is __0x00 0xC8__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
23.2	460	)))
4.2	461
23.2	462	(((
4.2	463	Generally, the EC value of irrigation water is less than 800uS / cm.
23.2	464	)))
4.2	465
23.2	466	(((
	467
	468	)))
4.2	469
23.2	470	(((
	471
	472	)))
	473
57.6	474	=== 2.4.8 Digital Interrupt ===
23.2	475
65.15	476	(((
57.8	477	Digital Interrupt refers to pin (% style="color:blue" %)GPIO_EXTI(%%), and there are different trigger methods. When there is a trigger, the NSE01 will send a packet to the server.
65.15	478	)))
4.2	479
65.15	480	(((
57.6	481	The command is:
65.15	482	)))
4.2	483
65.15	484	(((
57.8	485	(% 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	486	)))
4.2	487
	488
65.15	489	(((
65.6	490	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	491	)))
4.2	492
	493
65.15	494	(((
57.6	495	Example:
65.15	496	)))
4.2	497
65.15	498	(((
57.6	499	0x(00): Normal uplink packet.
65.15	500	)))
4.2	501
65.15	502	(((
57.6	503	0x(01): Interrupt Uplink Packet.
65.15	504	)))
23.2	505
4.2	506
	507
57.6	508	=== 2.4.9 +5V Output ===
4.2	509
65.16	510	(((
57.7	511	NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
65.16	512	)))
4.2	513
57.6	514
65.16	515	(((
57.6	516	The 5V output time can be controlled by AT Command.
65.16	517	)))
57.6	518
65.16	519	(((
57.7	520	(% style="color:blue" %)AT+5VT=1000
65.16	521	)))
57.6	522
65.16	523	(((
57.6	524	Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
65.16	525	)))
57.6	526
	527
	528
58.2	529	== 2.5 Downlink Payload ==
4.2	530
60.2	531	By default, NSE01 prints the downlink payload to console port.
4.2	532
58.2	533	[[image:image-20220708133731-5.png]]
4.2	534
	535
32.14	536	(((
40.4	537	(% style="color:blue" %)Examples:
32.14	538	)))
4.2	539
32.14	540	(((
	541
	542	)))
4.2	543
32.14	544	* (((
40.4	545	(% style="color:blue" %)Set TDC
32.14	546	)))
4.2	547
32.14	548	(((
60.2	549	If the payload=0100003C, it means set the END Node's TDC to 0x00003C=60(S), while type code is 01.
32.14	550	)))
4.2	551
32.14	552	(((
4.2	553	Payload: 01 00 00 1E TDC=30S
32.14	554	)))
4.2	555
32.14	556	(((
4.2	557	Payload: 01 00 00 3C TDC=60S
32.14	558	)))
4.2	559
32.14	560	(((
	561
	562	)))
4.2	563
32.14	564	* (((
40.4	565	(% style="color:blue" %)Reset
32.14	566	)))
4.2	567
32.14	568	(((
60.2	569	If payload = 0x04FF, it will reset the NSE01
32.14	570	)))
4.2	571
	572
60.2	573	* (% style="color:blue" %)INTMOD
4.2	574
65.17	575	(((
60.2	576	Downlink Payload: 06000003, Set AT+INTMOD=3
65.17	577	)))
4.2	578
	579
26.2	580
60.2	581	== 2.6 LED Indicator ==
26.2	582
32.15	583	(((
60.2	584	The NSE01 has an internal LED which is to show the status of different state.
4.2	585
	586
60.2	587	* When power on, NSE01 will detect if sensor probe is connected, if probe detected, LED will blink four times. (no blinks in this step is no probe)
	588	* Then the LED will be on for 1 second means device is boot normally.
	589	* After NSE01 join NB-IoT network. The LED will be ON for 3 seconds.
	590	* For each uplink probe, LED will be on for 500ms.
32.15	591	)))
4.2	592
	593
	594
	595
60.2	596	== 2.7 Installation in Soil ==
4.2	597
60.2	598	__Measurement the soil surface__
4.2	599
65.18	600	(((
60.2	601	Choose the proper measuring position. Avoid the probe to touch rocks or hard things. Split the surface soil according to the measured deep. Keep the measured as original density. Vertical insert the probe into the soil to be measured. Make sure not shake when inserting. [[https:~~/~~/img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg>>url:https://img.alicdn.com/imgextra/i3/2005165265/O1CN010rj9Oh1olPsQxrdUK_!!2005165265.jpg]]
65.18	602	)))
4.2	603
60.2	604	[[image:1657259653666-883.png]]
4.2	605
	606
60.2	607	(((
	608
35.15	609
60.2	610	(((
	611	Dig a hole with diameter > 20CM.
	612	)))
4.2	613
60.2	614	(((
	615	Horizontal insert the probe to the soil and fill the hole for long term measurement.
	616	)))
	617	)))
4.2	618
60.2	619	[[image:1654506665940-119.png]]
4.2	620
60.2	621	(((
	622
	623	)))
4.2	624
	625
60.2	626	== 2.8 Firmware Change Log ==
4.2	627
	628
60.2	629	Download URL & Firmware Change log
4.2	630
60.2	631	[[www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/Firmware/]]
4.2	632
	633
65.6	634	Upgrade Instruction: [[Upgrade_Firmware>>\|\|anchor="H5.1200BHowtoUpgradeFirmware"]]
28.5	635
4.2	636
	637
60.2	638	== 2.9 Battery Analysis ==
4.2	639
60.2	640	=== 2.9.1 Battery Type ===
4.2	641
	642
65.18	643	(((
60.2	644	The NSE01 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	645	)))
4.2	646
	647
65.18	648	(((
62.3	649	The battery is designed to last for several years depends on the actually use environment and update interval.
65.18	650	)))
4.2	651
	652
65.18	653	(((
60.2	654	The battery related documents as below:
65.18	655	)))
4.2	656
60.2	657	* [[Battery Dimension>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
65.7	658	* [[Lithium-Thionyl Chloride Battery datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
60.2	659	* [[Lithium-ion Battery-Capacitor datasheet>>http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]
4.2	660
29.2	661	(((
60.2	662	[[image:image-20220708140453-6.png]]
29.2	663	)))
4.2	664
	665
35.18	666
62.2	667	=== 2.9.2 Power consumption Analyze ===
4.2	668
62.3	669	(((
60.2	670	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	671	)))
4.2	672
	673
62.3	674	(((
60.2	675	Instruction to use as below:
62.3	676	)))
4.2	677
62.3	678	(((
	679	(% 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/]]
	680	)))
4.2	681
	682
62.3	683	(((
	684	(% style="color:blue" %)Step 2: (%%) Open it and choose
	685	)))
4.2	686
62.3	687	* (((
	688	Product Model
	689	)))
	690	* (((
	691	Uplink Interval
	692	)))
	693	* (((
	694	Working Mode
	695	)))
4.2	696
62.3	697	(((
60.2	698	And the Life expectation in difference case will be shown on the right.
62.3	699	)))
4.2	700
62.2	701	[[image:image-20220708141352-7.jpeg]]
4.2	702
	703
62.2	704
60.2	705	=== 2.9.3 Battery Note ===
4.2	706
31.6	707	(((
4.2	708	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	709	)))
4.2	710
	711
	712
60.2	713	=== 2.9.4 Replace the battery ===
31.2	714
62.2	715	(((
60.2	716	The default battery pack of NSE01 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	717	)))
4.2	718
	719
	720
63.2	721	= 3. Access NB-IoT Module =
4.2	722
63.2	723	(((
	724	Users can directly access the AT command set of the NB-IoT module.
	725	)))
	726
	727	(((
64.2	728	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	729	)))
	730
64.2	731	[[image:1657261278785-153.png]]
63.2	732
	733
	734
64.2	735	= 4. Using the AT Commands =
63.2	736
64.2	737	== 4.1 Access AT Commands ==
9.2	738
64.2	739	See this link for detail: [[http:~~/~~/www.dragino.com/downloads/index.php?dir=NB-IoT/NSE01/>>url:http://www.dragino.com/downloads/index.php?dir=NB-IoT/NBSN50/]]
11.4	740
4.2	741
64.2	742	AT+<CMD>? : Help on <CMD>
4.2	743
64.2	744	AT+<CMD> : Run <CMD>
4.2	745
64.2	746	AT+<CMD>=<value> : Set the value
4.2	747
64.2	748	AT+<CMD>=? : Get the value
4.2	749
	750
11.6	751	(% style="color:#037691" %)General Commands(%%)
4.2	752
64.2	753	AT : Attention
4.2	754
64.2	755	AT? : Short Help
4.2	756
64.2	757	ATZ : MCU Reset
4.2	758
64.2	759	AT+TDC : Application Data Transmission Interval
4.2	760
64.2	761	AT+CFG : Print all configurations
4.2	762
64.2	763	AT+CFGMOD : Working mode selection
4.2	764
64.2	765	AT+INTMOD : Set the trigger interrupt mode
4.2	766
64.2	767	AT+5VT : Set extend the time of 5V power
4.2	768
64.2	769	AT+PRO : Choose agreement
4.2	770
64.2	771	AT+WEIGRE : Get weight or set weight to 0
4.2	772
64.2	773	AT+WEIGAP : Get or Set the GapValue of weight
4.2	774
64.2	775	AT+RXDL : Extend the sending and receiving time
4.2	776
64.2	777	AT+CNTFAC : Get or set counting parameters
4.2	778
64.2	779	AT+SERVADDR : Server Address
4.2	780
	781
64.2	782	(% style="color:#037691" %)COAP Management
4.2	783
64.2	784	AT+URI : Resource parameters
4.2	785
	786
64.2	787	(% style="color:#037691" %)UDP Management
4.2	788
64.2	789	AT+CFM : Upload confirmation mode (only valid for UDP)
4.2	790
	791
64.2	792	(% style="color:#037691" %)MQTT Management
4.2	793
64.2	794	AT+CLIENT : Get or Set MQTT client
4.2	795
64.2	796	AT+UNAME : Get or Set MQTT Username
4.2	797
64.2	798	AT+PWD : Get or Set MQTT password
4.2	799
64.2	800	AT+PUBTOPIC : Get or Set MQTT publish topic
4.2	801
64.2	802	AT+SUBTOPIC : Get or Set MQTT subscription topic
4.2	803
	804
64.2	805	(% style="color:#037691" %)Information
4.2	806
64.2	807	AT+FDR : Factory Data Reset
4.2	808
64.2	809	AT+PWORD : Serial Access Password
4.2	810
	811
	812
64.4	813	= 5. FAQ =
4.2	814
64.4	815	== 5.1 How to Upgrade Firmware ==
6.3	816
4.2	817
31.35	818	(((
64.4	819	User can upgrade the firmware for 1) bug fix, 2) new feature release.
31.35	820	)))
4.2	821
31.35	822	(((
64.4	823	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	824	)))
4.2	825
31.35	826	(((
64.5	827	(% style="color:red" %)Notice, NSE01 and LSE01 share the same mother board. They use the same connection and method to update.
31.35	828	)))
4.2	829
	830
	831
65.23	832	== 5.2 Can I calibrate NSE01 to different soil types? ==
	833
	834	(((
	835	NSE01 is calibrated for saline-alkali soil and loamy soil. If users want to use it for other soil, they can calibrate the value in the IoT platform base on the value measured by saline-alkali soil and loamy soil. The formula can be found at [[this link>>https://www.dragino.com/downloads/downloads/LoRa_End_Node/LSE01/Calibrate_to_other_Soil_20220605.pdf]].
	836	)))
	837
	838
64.5	839	= 6. Trouble Shooting =
4.2	840
64.5	841	== 6.1 Connection problem when uploading firmware ==
4.9	842
4.2	843
65.20	844	(((
	845	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]]
	846	)))
	847
64.5	848	(% class="wikigeneratedid" %)
31.29	849	(((
65.20	850
31.29	851	)))
4.2	852
	853
64.5	854	== 6.2 AT Command input doesn't work ==
4.2	855
31.30	856	(((
64.5	857	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	858
65.23	859
31.30	860	)))
4.2	861
	862
64.5	863	= 7. Order Info =
4.2	864
	865
64.5	866	Part Number: (% style="color:#4f81bd" %)NSE01
4.7	867
4.2	868
31.10	869	(% class="wikigeneratedid" %)
	870	(((
	871
	872	)))
	873
65.2	874	= 8. Packing Info =
4.2	875
4.3	876	(((
31.39	877
	878
31.40	879	(% style="color:#037691" %)Package Includes:
64.5	880
65.1	881	* NSE01 NB-IoT Soil Moisture & EC Sensor x 1
64.5	882	* External antenna x 1
4.3	883	)))
4.2	884
4.3	885	(((
31.40	886
	887
	888	(% style="color:#037691" %)Dimension and weight:
4.2	889
64.5	890	* Size: 195 x 125 x 55 mm
	891	* Weight: 420g
4.3	892	)))
31.11	893
64.5	894	(((
31.11	895
64.5	896
	897
	898
4.3	899	)))
4.2	900
64.5	901	= 9. Support =
4.2	902
	903	* 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.
	904	* 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 NDDS75 NB-IoT Distance Detect Sensor User Manual

Applications