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

Version 75.3 by Xiaoling on 2022/07/09 08:58

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