Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -172,10 +172,10 @@
172	172
173	173	In the PC, use below serial tool settings:
174	174
175		-* Baud: (% style="color:green" %)**9600**
	175	+* Baud:  (% style="color:green" %)**9600**
176	176	* Data bits:** (% style="color:green" %)8(%%)**
177	177	* Stop bits: (% style="color:green" %)**1**
178		-* Parity: (% style="color:green" %)**None**
	178	+* Parity:  (% style="color:green" %)**None**
179	179	* Flow Control: (% style="color:green" %)**None**
180	180
181	181	(((
...	...	@@ -222,7 +222,6 @@
222	222	[[image:1657249864775-321.png]]
223	223
224	224
225		-
226	226	[[image:1657249930215-289.png]]
227	227
228	228
...	...	@@ -246,7 +246,6 @@
246	246	[[image:1657249990869-686.png]]
247	247
248	248
249		-
250	250	(((
251	251	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.
252	252	)))
...	...	@@ -267,6 +267,7 @@
267	267	[[image:1657250255956-604.png]]
268	268
269	269
	268	+
270	270	=== 2.2.8 Change Update Interval ===
271	271
272	272	User can use below command to change the (% style="color:green" %)**uplink interval**.
...	...	@@ -314,15 +314,14 @@
314	314	* Interrupt: 0x00 = 0
315	315
316	316
317		-
318		-
319	319	== 2.4  Payload Explanation and Sensor Interface ==
320	320
321		-2.4.1  Device ID
322	322
	319	+=== 2.4.1  Device ID ===
	320	+
323	323	By default, the Device ID equal to the last 6 bytes of IMEI.
324	324
325		-User can use **(% style="color:blue" %)AT+DEUI**(%%) to set Device ID
	323	+User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
326	326
327	327	**Example:**
328	328
...	...	@@ -331,8 +331,9 @@
331	331	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
332	332
333	333
334		-2.4.2  Version Info
335	335
	333	+=== 2.4.2  Version Info ===
	334	+
336	336	Specify the software version: 0x64=100, means firmware version 1.00.
337	337
338	338	For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
...	...	@@ -339,7 +339,7 @@
339	339
340	340
341	341
342		-=== 2.3.3 Battery Info ===
	341	+=== 2.4.3  Battery Info ===
343	343
344	344	(((
345	345	Check the battery voltage for LSE01.
...	...	@@ -355,14 +355,32 @@
355	355
356	356
357	357
358		-=== 2.3.4 Soil Moisture ===
	357	+=== 2.4.4  Signal Strength ===
359	359
	359	+NB-IoT Network signal Strength.
	360	+
	361	+**Ex1: 0x1d = 29**
	362	+
	363	+(% style="color:blue" %)**0**(%%)  -113dBm or less
	364	+
	365	+(% style="color:blue" %)**1**(%%)  -111dBm
	366	+
	367	+(% style="color:blue" %)**2...30**(%%) -109dBm... -53dBm
	368	+
	369	+(% style="color:blue" %)**31**  (%%) -51dBm or greater
	370	+
	371	+(% style="color:blue" %)**99**   (%%) Not known or not detectable
	372	+
	373	+
	374	+
	375	+=== 2.4.5  Soil Moisture ===
	376	+
360	360	(((
361	361	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.
362	362	)))
363	363
364	364	(((
365		-For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
	382	+For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
366	366	)))
367	367
368	368	(((
...	...	@@ -375,10 +375,10 @@
375	375
376	376
377	377
378		-=== 2.3.5 Soil Temperature ===
	395	+=== 2.4.6  Soil Temperature ===
379	379
380	380	(((
381		- 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
	398	+ 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
382	382	)))
383	383
384	384	(((
...	...	@@ -395,7 +395,7 @@
395	395
396	396
397	397
398		-=== 2.3.6 Soil Conductivity (EC) ===
	415	+=== 2.4.7  Soil Conductivity (EC) ===
399	399
400	400	(((
401	401	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).
...	...	@@ -402,7 +402,7 @@
402	402	)))
403	403
404	404	(((
405		-For example, if the data you get from the register is 0x00 0xC8, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
	422	+For example, if the data you get from the register is __**0x00 0xC8**__, the soil conductivity is 00C8(H) = 200(D) = 200 uS/cm.
406	406	)))
407	407
408	408	(((
...	...	@@ -417,39 +417,41 @@
417	417
418	418	)))
419	419
420		-=== 2.3.7 MOD ===
	437	+=== 2.4.8  Digital Interrupt ===
421	421
422		-Firmware version at least v2.1 supports changing mode.
	439	+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.
423	423
424		-For example, bytes[10]=90
	441	+The command is:
425	425
426		-mod=(bytes[10]>>7)&0x01=1.
	443	+(% 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]])**.**
427	427
428	428
429		-**Downlink Command:**
	446	+The lower four bits of this data field shows if this packet is generated by interrupt or not. [[Click here>>||anchor="H"]] for the hardware and software set up.
430	430
431		-If payload = 0x0A00, workmode=0
432	432
433		-If** **payload =** **0x0A01, workmode=1
	449	+Example:
434	434
	451	+0x(00): Normal uplink packet.
435	435
	453	+0x(01): Interrupt Uplink Packet.
436	436
437		-=== 2.3.8 ​Decode payload in The Things Network ===
438	438
439		-While using TTN network, you can add the payload format to decode the payload.
440	440
441	441
442		-[[image:1654505570700-128.png]]
	458	+=== 2.4.9  ​+5V Output ===
443	443
444		-(((
445		-The payload decoder function for TTN is here:
446		-)))
447	447
448		-(((
449		-LSE01 TTN Payload Decoder: [[https:~~/~~/www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0>>https://www.dropbox.com/sh/si8icbrjlamxqdb/AAACYwjsxxr5fj_vpqRtrETAa?dl=0]]
450		-)))
	461	+NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
451	451
452	452
	464	+The 5V output time can be controlled by AT Command.
	465	+
	466	+(% style="color:blue" %)**AT+5VT=1000**
	467	+
	468	+Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
	469	+
	470	+
	471	+
453	453	== 2.4 Uplink Interval ==
454	454
455	455	The LSE01 by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[Change Uplink Interval>>doc:Main.End Device AT Commands and Downlink Command.WebHome||anchor="H4.1ChangeUplinkInterval"]]