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,6 +222,7 @@
222	222	[[image:1657249864775-321.png]]
223	223
224	224
	225	+
225	225	[[image:1657249930215-289.png]]
226	226
227	227
...	...	@@ -245,6 +245,7 @@
245	245	[[image:1657249990869-686.png]]
246	246
247	247
	249	+
248	248	(((
249	249	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.
250	250	)))
...	...	@@ -265,7 +265,6 @@
265	265	[[image:1657250255956-604.png]]
266	266
267	267
268		-
269	269	=== 2.2.8 Change Update Interval ===
270	270
271	271	User can use below command to change the (% style="color:green" %)**uplink interval**.
...	...	@@ -313,14 +313,15 @@
313	313	* Interrupt: 0x00 = 0
314	314
315	315
316		-== 2.4  Payload Explanation and Sensor Interface ==
317	317
318	318
319		-=== 2.4.1  Device ID ===
	319	+== 2.4  Payload Explanation and Sensor Interface ==
320	320
	321	+2.4.1  Device ID
	322	+
321	321	By default, the Device ID equal to the last 6 bytes of IMEI.
322	322
323		-User can use (% style="color:blue" %)**AT+DEUI**(%%) to set Device ID
	325	+User can use **(% style="color:blue" %)AT+DEUI**(%%) to set Device ID
324	324
325	325	**Example:**
326	326
...	...	@@ -329,9 +329,8 @@
329	329	The Device ID is stored in a none-erase area, Upgrade the firmware or run AT+FDR won't erase Device ID.
330	330
331	331
	334	+2.4.2  Version Info
332	332
333		-=== 2.4.2  Version Info ===
334		-
335	335	Specify the software version: 0x64=100, means firmware version 1.00.
336	336
337	337	For example: 0x00 64 : this device is NSE01 with firmware version 1.0.0.
...	...	@@ -338,7 +338,7 @@
338	338
339	339
340	340
341		-=== 2.4.3  Battery Info ===
	342	+=== 2.3.3 Battery Info ===
342	342
343	343	(((
344	344	Check the battery voltage for LSE01.
...	...	@@ -354,32 +354,14 @@
354	354
355	355
356	356
357		-=== 2.4.4  Signal Strength ===
	358	+=== 2.3.4 Soil Moisture ===
358	358
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		-
377	377	(((
378	378	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.
379	379	)))
380	380
381	381	(((
382		-For example, if the data you get from the register is **__0x05 0xDC__**, the moisture content in the soil is
	365	+For example, if the data you get from the register is __0x05 0xDC__, the moisture content in the soil is
383	383	)))
384	384
385	385	(((
...	...	@@ -392,10 +392,10 @@
392	392
393	393
394	394
395		-=== 2.4.6  Soil Temperature ===
	378	+=== 2.3.5 Soil Temperature ===
396	396
397	397	(((
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
	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
399	399	)))
400	400
401	401	(((
...	...	@@ -412,7 +412,7 @@
412	412
413	413
414	414
415		-=== 2.4.7  Soil Conductivity (EC) ===
	398	+=== 2.3.6 Soil Conductivity (EC) ===
416	416
417	417	(((
418	418	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).
...	...	@@ -419,7 +419,7 @@
419	419	)))
420	420
421	421	(((
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.
	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.
423	423	)))
424	424
425	425	(((
...	...	@@ -434,39 +434,39 @@
434	434
435	435	)))
436	436
437		-=== 2.4.8  Digital Interrupt ===
	420	+=== 2.3.7 MOD ===
438	438
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.
	422	+Firmware version at least v2.1 supports changing mode.
440	440
441		-The command is:
	424	+For example, bytes[10]=90
442	442
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]])**.**
	426	+mod=(bytes[10]>>7)&0x01=1.
444	444
445	445
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.
	429	+**Downlink Command:**
447	447
	431	+If payload = 0x0A00, workmode=0
448	448
449		-Example:
	433	+If** **payload =** **0x0A01, workmode=1
450	450
451		-0x(00): Normal uplink packet.
452	452
453		-0x(01): Interrupt Uplink Packet.
454	454
	437	+=== 2.3.8 ​Decode payload in The Things Network ===
455	455
	439	+While using TTN network, you can add the payload format to decode the payload.
456	456
457		-=== 2.4.9  ​+5V Output ===
458	458
459		-NSE01 will enable +5V output before all sampling and disable the +5v after all sampling.
	442	+[[image:1654505570700-128.png]]
460	460
	444	+(((
	445	+The payload decoder function for TTN is here:
	446	+)))
461	461
462		-The 5V output time can be controlled by AT Command.
	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	+)))
463	463
464		-(% style="color:blue" %)**AT+5VT=1000**
465	465
466		-Means set 5V valid time to have 1000ms. So the real 5V output will actually have 1000ms + sampling time for other sensors.
467		-
468		-
469		-
470	470	== 2.4 Uplink Interval ==
471	471
472	472	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"]]