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

Version 68.2 by Xiaoling on 2022/07/09 08:41

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

Navigation