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

Version 73.1 by Xiaoling on 2022/07/09 08:47

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