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

Version 74.2 by Xiaoling on 2022/07/09 08:52

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