Wiki source code of LSPH01-LoRaWAN Soil pH Sensor User Manual

Version 34.25 by Xiaoling on 2022/06/07 16:35

version	line-number	content
2.2	1	(% style="text-align:center" %)
	2	[[image:1654574317295-380.png\|\|height="621" width="576"]]
1.1	3
	4
	5
	6
	7
14.8	8	Contents:
1.1	9
14.8	10	{{toc/}}
1.1	11
	12
	13
	14
	15
	16
	17
	18
	19
14.8	20
	21
	22
3.2	23	= 1. Introduction =
2.2	24
3.2	25	== 1.1 What is LoRaWAN Soil pH Sensor ==
2.2	26
3.2	27	The Dragino LSPH01 is a (% style="color:#4f81bd" %)LoRaWAN Soil pH Sensor(%%) for IoT of Agriculture. It is designed to measure the soil PH and soil temperature, so to send to the platform to analyze the soil acid or alkali level. The probe is IP68 waterproof.
2.2	28
3.2	29	LSPH01 probe is made by Solid AgCl reference electrode and Pure metal pH sensitive electrode. It can detect soil's (% style="color:#4f81bd" %)pH (%%)with high accuracy and stable value. The LSPH01 probe can be buried into soil for long time use.
2.2	30
	31	The LoRa wireless technology used in LSPH01 allows device to send data and reach extremely long ranges at low data-rates. It provides ultra-long range spread spectrum communication and high interference immunity whilst minimizing current consumption.
	32
3.2	33	LSPH01 is powered by (% style="color:#4f81bd" %)8500mAh Li-SOCI2 battery(%%), it is designed for long term use up to 5 years.
2.2	34
3.2	35	Each LSPH01 is pre-load with a set of unique keys for LoRaWAN registrations, register these keys to local LoRaWAN server and it will auto connect after power on.
2.2	36
	37
3.2	38	[[image:1654580186518-415.png]]
2.2	39
	40
	41
3.2	42	== 1.2 Features ==
	43
2.2	44	* LoRaWAN 1.0.3 Class A
	45	* Ultra-low power consumption
	46	* Monitor soil pH with temperature compensation.
	47	* Monitor soil temperature
	48	* Monitor Battery Level
	49	* Support pH calibration by end user
	50	* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
	51	* AT Commands to change parameters
	52	* Uplink on periodically
	53	* Downlink to change configure
	54	* IP66 Waterproof Enclosure
	55	* IP68 rate for the Sensor Probe
	56	* 8500mAh Battery for long term use
	57
34.15	58
	59
3.3	60	== 1.3 Probe Specification ==
2.2	61
	62
3.3	63	(% style="color:#4f81bd" %)Soil pH:
	64
	65	* Range: 3 ~~ 10 pH
	66	* Resolution: 0.01 pH
	67	* Accuracy: ±2% under (0~~50 ℃, Accuracy will poor under 0 due to frozen)
	68	* Temperature Compensation Range: 0 ~~ 50℃
2.2	69	* IP68 Protection
	70	* Length: 3.5 meters
	71
3.3	72	(% style="color:#4f81bd" %)Soil Temperature:
2.2	73
3.3	74	* Range -40℃～85℃
	75	* Resolution: 0.1℃
	76	* Accuracy: <±0.5℃(-10℃～40℃)，<±0.8℃ (others)
2.2	77	* IP68 Protection
	78	* Length: 3.5 meters
	79
34.16	80
3.3	81	== 1.4 Applications ==
	82
2.2	83	* Smart Agriculture
	84
34.17	85
3.3	86	== 1.5 Pin mapping and power on ==
	87
5.5	88	[[image:1654580482666-473.png]]
2.2	89
	90
	91
5.2	92	= 2. Configure LSPH01 to connect to LoRaWAN network =
2.2	93
5.5	94	== 2.1 How it works ==
2.2	95
5.3	96	(((
2.2	97	The LSPH01 is configured as LoRaWAN OTAA Class A mode by default. It has OTAA keys to join LoRaWAN network. To connect a local LoRaWAN network, you need to input the OTAA keys in the LoRaWAN IoT server and power on the LSPH01. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
5.3	98	)))
2.2	99
5.3	100	(((
34.18	101	In case you can’t set the OTAA keys in the LoRaWAN OTAA server, and you have to use the keys from the server, you can [[use AT Commands >>\|\|anchor="H5.UseATCommand"]]to set the keys in the LSPH01.
5.3	102	)))
2.2	103
	104
5.3	105	== 2.2 Quick guide to connect to LoRaWAN server (OTAA) ==
2.2	106
6.3	107	(((
2.2	108	Following is an example for how to join the [[TTN v3 LoRaWAN Network>>url:https://console.cloud.thethings.network/]]. Below is the network structure; we use the [[LG308>>url:http://www.dragino.com/products/lora/item/140-lg308.html]] as a LoRaWAN gateway in this example.
6.3	109	)))
2.2	110
6.3	111	(((
	112
	113	)))
2.2	114
6.3	115	(((
2.2	116	The LG308 is already set to connected to [[TTN network >>url:https://console.cloud.thethings.network/]], so what we need to now is configure the TTN server.
6.3	117	)))
2.2	118
6.3	119	(((
23.5	120	(% style="color:blue" %)Step 1(%%): Create a device in TTN with the OTAA keys from LSPH01.
6.3	121	)))
2.2	122
6.3	123	(((
2.2	124	Each LSPH01 is shipped with a sticker with the default device EUI as below:
6.3	125	)))
2.2	126
	127
6.3	128	[[image:image-20220607135531-1.jpeg]]
2.2	129
	130
	131	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
	132
	133
	134	Register the device
	135
9.2	136	[[image:1654581442672-605.png]]
2.2	137
	138
9.2	139
2.2	140	Add APP EUI and DEV EUI
	141
9.2	142	[[image:1654581465717-368.png]]
2.2	143
	144
	145
	146	Add APP EUI in the application
	147
9.2	148	[[image:1654581493871-516.png]]
2.2	149
	150
10.2	151
2.2	152	Add APP KEY
	153
10.2	154	[[image:1654581517630-991.png]]
2.2	155
	156
23.5	157	(% style="color:blue" %)Step 2(%%): Power on LSPH01
2.2	158
	159
	160	Put a Jumper on JP2 to power on the device. ( The Switch must be in FLASH position).
	161
11.2	162	[[image:image-20220607135918-2.png]]
2.2	163
	164
23.5	165	(% style="color:blue" %)Step 3(%%): The LSPH01 will auto join to the TTN network. After join success, it will start to upload messages to TTN and you can see the messages in the panel.
2.2	166
12.2	167	[[image:1654581590132-631.png]]
2.2	168
	169
	170
13.2	171	== 2.3 Uplink Payload ==
2.2	172
3.2	173	LSPH01 will uplink payload via LoRaWAN with below payload format:
2.2	174
	175	Uplink payload includes in total 11 bytes.
	176
	177	Normal uplink payload:
	178
13.2	179	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
2.2	180	\|(((
	181	Size
	182
	183	(bytes)
	184	)))\|2\|2\|2\|2\|1\|1\|1
14.5	185	\|Value\|[[BAT>>\|\|anchor="H2.3.1BatteryInfo"]]\|(((
14.6	186	[[Temperature>>\|\|anchor="H2.3.2DS18B20Temperaturesensor"]]
2.2	187
14.6	188	[[(Optional)>>\|\|anchor="H2.3.2DS18B20Temperaturesensor"]]
	189	)))\|[[Soil pH>>\|\|anchor="H2.3.3SoilpH"]]\|[[Soil Temperature>>\|\|anchor="H2.3.4SoilTemperature"]]\|(((
	190	[[Digital Interrupt (Optional)>>\|\|anchor="H2.3.5InterruptPin"]]
2.2	191	)))\|Reserve\|(((
14.6	192	[[Message Type>>\|\|anchor="H2.3.6MessageType"]]
2.2	193	)))
	194
13.2	195	[[image:1654581735133-458.png]]
2.2	196
	197
	198
13.2	199	=== 2.3.1 Battery Info ===
2.2	200
13.2	201
2.2	202	Check the battery voltage for LSPH01.
	203
	204	Ex1: 0x0B45 = 2885mV
	205
	206	Ex2: 0x0B49 = 2889mV
	207
	208
	209
13.2	210	=== 2.3.2 DS18B20 Temperature sensor ===
2.2	211
13.2	212	This is optional, user can connect external DS18B20 sensor to the +3.3v, 1-wire and GND pin . and this field will report temperature.
2.2	213
13.2	214
2.2	215	Example:
	216
	217	If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
	218
	219	If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
	220
	221
	222
13.3	223	=== 2.3.3 Soil pH ===
2.2	224
	225	Range: 0 ~~ 14 pH
	226
13.3	227	Example:
2.2	228
13.3	229	(% style="color:#037691" %) 0x02B7(H) = 695(D) = 6.95pH
2.2	230
	231
	232
13.3	233	=== 2.3.4 Soil Temperature ===
	234
2.2	235	Get Soil Temperature
	236
	237
	238	Example:
	239
13.3	240	If payload is: 0105H: (0105 & FC00 == 0), temp = 0105H /10 = 26.1 degree
2.2	241
13.3	242	If payload is: FF3FH : (FF3F & FC00 == 1) , temp = (FF3FH - 65536)/10 = -19.3 degrees.
2.2	243
	244
	245
13.3	246	=== 2.3.5 Interrupt Pin ===
2.2	247
13.4	248	This data field shows if this packet is generated by interrupt or not. [[Click here>>\|\|anchor="H3.2SetInterruptMode"]] for the hardware and software set up.
2.2	249
	250
13.3	251	Example:
2.2	252
	253	0x00: Normal uplink packet.
	254
	255	0x01: Interrupt Uplink Packet.
	256
	257
	258
13.3	259	=== 2.3.6 Message Type ===
	260
2.2	261	For a normal uplink payload, the message type is always 0x01.
	262
	263	Valid Message Type:
	264
	265
13.4	266	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
	267	\|Message Type Code\|Description\|Payload
34.21	268	\|0x01\|Normal Uplink\|[[Normal Uplink Payload>>\|\|anchor="H2.3200BUplinkPayload"]]
13.5	269	\|0x02\|Reply configures info\|[[Configure Info Payload>>\|\|anchor="H3.4GetFirmwareVersionInfo"]]
13.6	270	\|0x03\|Reply Calibration Info\|[[Calibration Payload>>\|\|anchor="H2.7Calibration"]]
2.2	271
34.22	272
	273
13.6	274	=== 2.3.7 Decode payload in The Things Network ===
	275
2.2	276	While using TTN network, you can add the payload format to decode the payload.
	277
	278
14.2	279	[[image:1654582541848-906.png]]
2.2	280
14.2	281	(((
2.2	282	The payload decoder function for TTN is here:
14.2	283	)))
2.2	284
14.2	285	(((
2.2	286	LSPH01 TTN Payload Decoder: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]
14.2	287	)))
2.2	288
	289
	290
14.3	291	== 2.4 Uplink Interval ==
	292
14.4	293	The LSPH01 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"]]
2.2	294
	295
	296
16.2	297	== 2.5 Show Data in DataCake IoT Server ==
2.2	298
	299	[[DATACAKE>>url:https://datacake.co/]] provides a human friendly interface to show the sensor data, once we have data in TTN, we can use [[DATACAKE>>url:https://datacake.co/]] to connect to TTN and see the data in DATACAKE. Below are the steps:
	300
	301
23.5	302	(% style="color:blue" %)Step 1(%%): Be sure that your device is programmed and properly connected to the network at this time.
2.2	303
23.5	304	(% style="color:blue" %)Step 2(%%): To configure the Application to forward data to DATACAKE you will need to add integration. To add the DATACAKE integration, perform the following steps:
2.2	305
	306
16.2	307	[[image:1654583683416-869.png]]
2.2	308
	309
16.2	310	[[image:1654583694084-878.png]]
2.2	311
	312
23.5	313	(% style="color:blue" %)Step 3(%%): Create an account or log in Datacake.
2.2	314
23.5	315	(% style="color:blue" %)Step 4(%%): Create LSPH01 product.
2.2	316
17.2	317	[[image:1654583711590-413.png]]
2.2	318
	319
	320
19.2	321	[[image:1654583732798-193.png]]
2.2	322
	323
19.2	324	[[image:1654583749683-259.png]]
2.2	325
	326
23.5	327	(% style="color:blue" %)Step 5(%%): add payload decode
2.2	328
	329	Download Datacake decoder from: [[https:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Decoder/>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSNPK01/Decoder/]]
	330
	331
23.2	332	[[image:1654583770974-935.png]]
2.2	333
23.2	334	[[image:1654583781517-146.png]]
2.2	335
	336
23.2	337	[[image:1654583791351-557.png]]
2.2	338
	339
	340	After added, the sensor data arrive TTN, it will also arrive and show in Mydevices.
	341
	342
23.2	343	[[image:1654583805491-713.png]]
2.2	344
	345
	346
24.2	347	== 2.6 Installation and Maintain ==
2.2	348
24.2	349	=== 2.6.1 Before measurement ===
	350
	351	(((
3.2	352	If the LSPH01 has more than 7 days not use or just clean the pH probe. User should put the probe inside pure water for more than 24 hours for activation. If no put in water, user need to put inside soil for more than 24 hours to ensure the measurement accuracy.
24.2	353	)))
2.2	354
	355
	356
24.2	357	=== 2.6.2 Measurement ===
2.2	358
	359
24.2	360	(% style="color:#4f81bd" %)Measurement the soil surface:
2.2	361
24.2	362	[[image:1654584128046-287.png]]
2.2	363
24.2	364	Choose the proper measuring position. Split the surface soil according to the measured deep.
	365
2.2	366	Put pure water, or rainwater to make the soil of measurement point to moist mud. Remove rocks or hard things.
	367
	368	Slowly insert the probe to the measure point. Don’t use large force which will break the probe. Make sure not shake when inserting.
	369
	370	Put soil over the probe after insert. And start to measure.
	371
	372
24.2	373	(% style="color:#4f81bd" %)Measurement inside soil:
2.2	374
24.2	375	Dig a hole with diameter > 20CM.
2.2	376
24.2	377	Insert the probe inside, method like measure the surface.
2.2	378
	379
	380
24.2	381	=== 2.6.3 Maintain Probe ===
2.2	382
24.2	383	1. (((
	384	pH probe electrode is fragile and no strong. User must avoid strong force or hitting it.
	385	)))
	386	1. (((
	387	After long time use (3~~ 6 months). The probe electrode needs to be clean; user can use high grade sandpaper to polish it or put in 5% hydrochloric acid for several minutes. After the metal probe looks like new, user can use pure water to wash it.
	388	)))
	389	1. (((
	390	Probe reference electrode is also no strong, need to avoid strong force or hitting.
	391	)))
	392	1. (((
	393	User should keep reference electrode wet while not use.
	394	)))
	395	1. (((
	396	Avoid the probes to touch oily matter. Which will cause issue in accuracy.
	397	)))
	398	1. (((
	399	The probe is IP68 can be put in water.
2.2	400
	401
25.2	402
	403	)))
2.2	404
24.3	405	== 2.7 Calibration ==
24.2	406
2.2	407	User can do calibration for the probe. It is limited to use below pH buffer solution to calibrate: 4.00, 6.86, 9.18. When calibration, user need to clean the electrode and put the probe in the pH buffer solution to wait the value stable ( a new clean electrode might need max 24 hours to be stable).
	408
26.2	409	After stable, user can use below command to calibrate.
2.2	410
25.2	411	[[image:image-20220607144936-3.png]]
2.2	412
	413
25.2	414	(% style="color:#037691" %)Calibration Payload
2.2	415
25.2	416	(% border="1" cellspacing="10" style="background-color:#ffffcc; width:510px" %)
2.2	417	\|(((
	418	Size
	419
	420	(bytes)
	421	)))\|1\|1\|1\|7\|1
	422	\|Value\|(((
	423	PH4
	424
	425	Calibrate value
	426	)))\|PH6.86 Calibrate value\|(((
	427	PH9.18
	428
	429	Calibrate value
	430	)))\|Reserve\|(((
25.3	431	[[Message Type>>\|\|anchor="H2.3.6MessageType"]]
	432
	433	Always 0x03
2.2	434	)))
	435
	436	User can also send 0x14 downlink command to poll the current calibration payload.
	437
26.2	438	[[image:image-20220607145603-4.png]]
2.2	439
	440	* Reply to the confirmation package: 14 01
	441	* Reply to non-confirmed packet: 14 00
	442
34.23	443
	444
26.5	445	== 2.8 Frequency Plans ==
26.2	446
26.6	447	(((
2.2	448	The LSPH01 uses OTAA mode and below frequency plans by default. If user want to use it with different frequency plan, please refer the AT command sets.
26.6	449	)))
2.2	450
	451
26.5	452	=== 2.8.1 EU863-870 (EU868) ===
2.2	453
26.5	454	(% style="color:blue" %)Uplink:
	455
2.2	456	868.1 - SF7BW125 to SF12BW125
	457
	458	868.3 - SF7BW125 to SF12BW125 and SF7BW250
	459
	460	868.5 - SF7BW125 to SF12BW125
	461
	462	867.1 - SF7BW125 to SF12BW125
	463
	464	867.3 - SF7BW125 to SF12BW125
	465
	466	867.5 - SF7BW125 to SF12BW125
	467
	468	867.7 - SF7BW125 to SF12BW125
	469
	470	867.9 - SF7BW125 to SF12BW125
	471
	472	868.8 - FSK
	473
	474
26.5	475	(% style="color:blue" %)Downlink:
2.2	476
	477	Uplink channels 1-9 (RX1)
	478
	479	869.525 - SF9BW125 (RX2 downlink only)
	480
	481
	482
26.5	483	=== 2.8.2 US902-928(US915) ===
	484
	485	(((
2.2	486	Used in USA, Canada and South America. Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
26.5	487	)))
2.2	488
26.5	489	(((
2.2	490	To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
26.5	491	)))
2.2	492
26.5	493	(((
2.2	494	After Join success, the end node will switch to the correct sub band by:
26.5	495	)))
2.2	496
	497	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	498	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
	499
34.24	500
	501
26.5	502	=== 2.8.3 CN470-510 (CN470) ===
	503
2.2	504	Used in China, Default use CHE=1
	505
26.5	506	(% style="color:blue" %)Uplink:
2.2	507
	508	486.3 - SF7BW125 to SF12BW125
	509
	510	486.5 - SF7BW125 to SF12BW125
	511
	512	486.7 - SF7BW125 to SF12BW125
	513
	514	486.9 - SF7BW125 to SF12BW125
	515
	516	487.1 - SF7BW125 to SF12BW125
	517
	518	487.3 - SF7BW125 to SF12BW125
	519
	520	487.5 - SF7BW125 to SF12BW125
	521
	522	487.7 - SF7BW125 to SF12BW125
	523
	524
26.5	525	(% style="color:blue" %)Downlink:
2.2	526
	527	506.7 - SF7BW125 to SF12BW125
	528
	529	506.9 - SF7BW125 to SF12BW125
	530
	531	507.1 - SF7BW125 to SF12BW125
	532
	533	507.3 - SF7BW125 to SF12BW125
	534
	535	507.5 - SF7BW125 to SF12BW125
	536
	537	507.7 - SF7BW125 to SF12BW125
	538
	539	507.9 - SF7BW125 to SF12BW125
	540
	541	508.1 - SF7BW125 to SF12BW125
	542
	543	505.3 - SF12BW125 (RX2 downlink only)
	544
	545
	546
26.5	547	=== 2.8.4 AU915-928(AU915) ===
	548
	549	(((
2.2	550	Frequency band as per definition in LoRaWAN 1.0.3 Regional document.
26.5	551	)))
2.2	552
26.5	553	(((
2.2	554	To make sure the end node supports all sub band by default. In the OTAA Join process, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join.
26.5	555	)))
2.2	556
26.5	557	(((
	558
	559	)))
2.2	560
26.5	561	(((
2.2	562	After Join success, the end node will switch to the correct sub band by:
26.5	563	)))
2.2	564
	565	* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
	566	* Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
	567
34.25	568
	569
26.5	570	=== 2.8.5 AS920-923 & AS923-925 (AS923) ===
	571
26.7	572	(% style="color:blue" %)Default Uplink channel:
2.2	573
	574	923.2 - SF7BW125 to SF10BW125
	575
	576	923.4 - SF7BW125 to SF10BW125
	577
	578
26.7	579	(% style="color:blue" %)Additional Uplink Channel:
2.2	580
	581	(OTAA mode, channel added by JoinAccept message)
	582
	583
26.7	584	(% style="color:blue" %)AS920~~AS923 for Japan, Malaysia, Singapore:
	585
2.2	586	922.2 - SF7BW125 to SF10BW125
	587
	588	922.4 - SF7BW125 to SF10BW125
	589
	590	922.6 - SF7BW125 to SF10BW125
	591
	592	922.8 - SF7BW125 to SF10BW125
	593
	594	923.0 - SF7BW125 to SF10BW125
	595
	596	922.0 - SF7BW125 to SF10BW125
	597
	598
26.7	599	(% style="color:blue" %)AS923 ~~ AS925 for Brunei, Cambodia, Hong Kong, Indonesia, Laos, Taiwan, Thailand, Vietnam:
2.2	600
	601	923.6 - SF7BW125 to SF10BW125
	602
	603	923.8 - SF7BW125 to SF10BW125
	604
	605	924.0 - SF7BW125 to SF10BW125
	606
	607	924.2 - SF7BW125 to SF10BW125
	608
	609	924.4 - SF7BW125 to SF10BW125
	610
	611	924.6 - SF7BW125 to SF10BW125
	612
	613
26.7	614	(% style="color:blue" %)Downlink:
2.2	615
	616	Uplink channels 1-8 (RX1)
	617
	618	923.2 - SF10BW125 (RX2)
	619
	620
	621
26.7	622	=== 2.8.6 KR920-923 (KR920) ===
2.2	623
26.7	624	(% style="color:blue" %)Default channel:
	625
2.2	626	922.1 - SF7BW125 to SF12BW125
	627
	628	922.3 - SF7BW125 to SF12BW125
	629
	630	922.5 - SF7BW125 to SF12BW125
	631
	632
26.7	633	(% style="color:blue" %)Uplink: (OTAA mode, channel added by JoinAccept message)
2.2	634
	635	922.1 - SF7BW125 to SF12BW125
	636
	637	922.3 - SF7BW125 to SF12BW125
	638
	639	922.5 - SF7BW125 to SF12BW125
	640
	641	922.7 - SF7BW125 to SF12BW125
	642
	643	922.9 - SF7BW125 to SF12BW125
	644
	645	923.1 - SF7BW125 to SF12BW125
	646
	647	923.3 - SF7BW125 to SF12BW125
	648
	649
26.7	650	(% style="color:blue" %)Downlink:
2.2	651
	652	Uplink channels 1-7(RX1)
	653
	654	921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
	655
	656
26.7	657	=== 2.8.7 IN865-867 (IN865) ===
2.2	658
26.7	659	(% style="color:blue" %)Uplink:
2.2	660
	661	865.0625 - SF7BW125 to SF12BW125
	662
	663	865.4025 - SF7BW125 to SF12BW125
	664
	665	865.9850 - SF7BW125 to SF12BW125
	666
	667
26.7	668	(% style="color:blue" %)Downlink:
2.2	669
	670	Uplink channels 1-3 (RX1)
	671
	672	866.550 - SF10BW125 (RX2)
	673
	674
	675
26.7	676	== 2.9 LED Indicator ==
	677
2.2	678	The LSPH01 has an internal LED which is to show the status of different state.
	679
	680	* The sensor is detected when the device is turned on, and it will flash 4 times quickly when it is detected.
	681	* Blink once when device transmit a packet.
	682
34.9	683
	684
26.9	685	== 2.10 Firmware Change Log ==
2.2	686
26.15	687
2.2	688	Firmware download link:
	689
	690	[[http:~~/~~/www.dragino.com/downloads/index.pHp?dir=LoRa_End_Node/LSPH01/Firmware/>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_End_Node/LSE01/Firmware/]]
	691
	692
26.14	693	Firmware Upgrade Method: [[Firmware Upgrade Instruction>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]]
2.2	694
	695
	696
26.16	697	= 3. Configure LSPH01 via AT Command or LoRaWAN Downlink =
2.2	698
	699	Use can configure LSPH01 via AT Command or LoRaWAN Downlink.
	700
26.17	701	* AT Command Connection: See [[FAQ>>\|\|anchor="H6.FAQ"]].
	702	* LoRaWAN Downlink instruction for different platforms: [[IoT LoRaWAN Server>>doc:Main.WebHome]]
2.2	703
	704	There are two kinds of commands to configure LSPH01, they are:
	705
27.2	706	* (% style="color:#4f81bd" %) General Commands.
2.2	707
	708	These commands are to configure:
	709
	710	* General system settings like: uplink interval.
	711	* LoRaWAN protocol & radio related command.
	712
26.17	713	They are same for all Dragino Device which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:[[End Device AT Commands and Downlink Command>>doc:Main.End Device AT Commands and Downlink Command.WebHome]]
2.2	714
	715
27.2	716	* (% style="color:#4f81bd" %) Commands special design for LSPH01
2.2	717
	718	These commands only valid for LSPH01, as below:
	719
	720
	721
27.2	722	== 3.1 Set Transmit Interval Time ==
	723
2.2	724	Feature: Change LoRaWAN End Node Transmit Interval.
	725
27.2	726	(% style="color:#037691" %)AT Command: AT+TDC
2.2	727
27.2	728
	729	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:710px" %)
	730	\|(% style="width:154px" %)Command Example\|(% style="width:223px" %)Function\|(% style="width:330px" %)Response
	731	\|(% style="width:154px" %)AT+TDC=?\|(% style="width:223px" %)Show current transmit Interval\|(% style="width:330px" %)(((
2.2	732	30000
	733
	734	OK
	735
	736	the interval is 30000ms = 30s
	737	)))
27.2	738	\|(% style="width:154px" %)AT+TDC=60000\|(% style="width:223px" %)Set Transmit Interval\|(% style="width:330px" %)(((
2.2	739	OK
	740
	741	Set transmit interval to 60000ms = 60 seconds
	742	)))
	743
27.2	744	(% style="color:#037691" %)Downlink Command: 0x01
2.2	745
	746	Format: Command Code (0x01) followed by 3 bytes time value.
	747
	748	If the downlink payload=0100003C, it means set the END Node’s Transmit Interval to 0x00003C=60(S), while type code is 01.
	749
	750	* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	751	* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
	752
27.3	753	== 3.2 Set Interrupt Mode ==
	754
2.2	755	Feature, Set Interrupt mode for GPIO_EXIT.
	756
27.3	757	(% style="color:#037691" %)AT Command: AT+INTMOD
2.2	758
28.2	759	[[image:image-20220607153759-6.png]]
2.2	760
	761
27.3	762	(% style="color:#037691" %)Downlink Command: 0x06
2.2	763
	764	Format: Command Code (0x06) followed by 3 bytes.
	765
	766	This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	767
	768	* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	769	* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
	770
27.3	771	== 3.3 Calibrate Sensor ==
	772
28.4	773	Detail See [[Calibration Guide>>\|\|anchor="2.7Calibration"]] for the user of 0x13 and 0x14 downlink commands
2.2	774
	775
	776
28.3	777	== 3.4 Get Firmware Version Info ==
	778
2.2	779	Feature: use downlink to get firmware version.
	780
27.3	781	(% style="color:#037691" %)Downlink Command: 0x26
2.2	782
29.2	783	[[image:image-20220607154718-7.png]]
2.2	784
	785	* Reply to the confirmation package: 26 01
	786	* Reply to non-confirmed packet: 26 00
	787
34.10	788
2.2	789	Device will send an uplink after got this downlink command. With below payload:
	790
	791	Configures info payload:
	792
29.4	793	(% border="1" cellspacing="10" style="background-color:#ffffcc; color:green; width:510px" %)
	794	\|=(((
	795	Size(bytes)
	796	)))\|=1\|=1\|=1\|=1\|=1\|=5\|=1
2.2	797	\|Value\|Software Type\|(((
	798	Frequency
	799
	800	Band
	801	)))\|Sub-band\|(((
	802	Firmware
	803
	804	Version
	805	)))\|Sensor Type\|Reserve\|(((
29.4	806	[[Message Type>>\|\|anchor="H2.3.6MessageType"]]
2.2	807	Always 0x02
	808	)))
	809
	810	Software Type: Always 0x03 for LSPH01
	811
	812
	813	Frequency Band:
	814
	815	*0x01: EU868
	816
	817	*0x02: US915
	818
	819	*0x03: IN865
	820
	821	*0x04: AU915
	822
	823	*0x05: KZ865
	824
	825	*0x06: RU864
	826
	827	*0x07: AS923
	828
	829	*0x08: AS923-1
	830
	831	*0x09: AS923-2
	832
	833	*0xa0: AS923-3
	834
	835
	836	Sub-Band: value 0x00 ~~ 0x08
	837
	838
	839	Firmware Version: 0x0100, Means: v1.0.0 version
	840
	841
	842	Sensor Type:
	843
	844	0x01: LSE01
	845
	846	0x02: LDDS75
	847
	848	0x03: LDDS20
	849
	850	0x04: LLMS01
	851
	852	0x05: LSPH01
	853
	854	0x06: LSNPK01
	855
	856	0x07: LDDS12
	857
	858
	859
29.9	860	= 4. Battery & How to replace =
2.2	861
29.9	862	== 4.1 Battery Type ==
2.2	863
30.2	864	(((
2.2	865	LSPH01 is equipped with a [[8500mAH ER26500 Li-SOCI2 battery>>url:https://www.dragino.com/downloads/index.php?dir=datasheet/Battery/ER26500/]]. The battery is un-rechargeable battery with low discharge rate targeting for 8~~10 years use. This type of battery is commonly used in IoT target for long-term running, such as water meter.
30.2	866	)))
2.2	867
30.2	868	(((
2.2	869	The discharge curve is not linear so can’t simply use percentage to show the battery level. Below is the battery performance.
30.2	870	)))
2.2	871
30.2	872	[[image:1654588469844-778.png]]
2.2	873
	874
	875	Minimum Working Voltage for the LSPH01:
	876
	877	LSPH01: 2.45v ~~ 3.6v
	878
	879
	880
30.3	881	== 4.2 Replace Battery ==
	882
30.5	883	(((
2.2	884	Any battery with range 2.45 ~~ 3.6v can be a replacement. We recommend to use Li-SOCl2 Battery.
30.5	885	)))
2.2	886
30.5	887	(((
2.2	888	And make sure the positive and negative pins match.
30.5	889	)))
2.2	890
	891
	892
30.4	893	== 4.3 Power Consumption Analyze ==
2.2	894
30.5	895	(((
2.2	896	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.
30.5	897	)))
2.2	898
30.5	899	(((
2.2	900	Instruction to use as below:
30.5	901	)))
2.2	902
	903
32.3	904	Step 1: Downlink the up-to-date DRAGINO_Battery_Life_Prediction_Table.xlsx from:
2.2	905
	906	[[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/]]
	907
	908
32.3	909	Step 2: Open it and choose
2.2	910
	911	* Product Model
	912	* Uplink Interval
	913	* Working Mode
	914
	915	And the Life expectation in difference case will be shown on the right.
	916
32.2	917	[[image:1654588577573-122.png]]
2.2	918
	919
	920	The battery related documents as below:
	921
32.2	922	* (((
	923	[[Battery Dimension>>url:http://www.dragino.com/downloads/index.php?dir=datasheet/Battery/&file=LSN50-Battery-Dimension.pdf]],
2.2	924	)))
32.2	925	* (((
	926	[[Lithium-Thionyl Chloride Battery datasheet>>url:https://www.dragino.com/downloads/downloads/datasheet/Battery/ER26500/ER26500_Datasheet-EN.pdf]],
	927	)))
	928	* (((
	929	[[Lithium-ion Battery-Capacitor datasheet>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC_1520_datasheet.jpg]], [[Tech Spec>>url:http://www.dragino.com/downloads/downloads/datasheet/Battery/SPC1520%20Technical%20Specification20171123.pdf]]
	930	)))
2.2	931
32.2	932	[[image:image-20220607155856-8.png]]
2.2	933
	934
	935
32.4	936	=== 4.3.1 Battery Note ===
2.2	937
32.4	938	(((
2.2	939	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.
32.4	940	)))
2.2	941
	942
	943
32.4	944	=== 4.3.2 Replace the battery ===
	945
2.2	946	You can change the battery in the LSPH01.The type of battery is not limited as long as the output is between 3v to 3.6v. On the main board, there is a diode (D1) between the battery and the main circuit. If you need to use a battery with less than 3.3v, please remove the D1 and shortcut the two pads of it so there won’t be voltage drop between battery and main board.
	947
	948	The default battery pack of LSPH01 includes a ER26500 plus super capacitor. If user can’t find this pack locally, they can find ER26500 or equivalence, which will also work in most case. The SPC can enlarge the battery life for high frequency use (update period below 5 minutes)
	949
	950
	951
33.2	952	= 5. Use AT Command =
2.2	953
33.2	954	== 5.1 Access AT Commands ==
2.2	955
	956	LSPH01 supports AT Command set in the stock firmware. You can use a USB to TTL adapter to connect to LSPH01 for using AT command, as below.
	957
33.2	958	[[image:1654589001411-343.png]]
2.2	959
34.6	960	Connection:
2.2	961
34.2	962	(% style="background-color:yellow" %) USB TTL GND <~-~-~-~-> GND
2.2	963
34.2	964	(% style="background-color:yellow" %) USB TTL TXD <~-~-~-~-> UART_RXD
2.2	965
34.2	966	(% style="background-color:yellow" %) USB TTL RXD <~-~-~-~-> UART_TXD
2.2	967
	968
34.6	969	In the PC, you need to set the serial baud rate to (% style="color:green" %)9600(%%) to access the serial console for LSPH01. LSPH01 will output system info once power on as below:
2.2	970
	971
34.2	972	[[image:1654589062541-567.png]]
2.2	973
	974	Valid AT Command please check [[Configure Device>>path:#Configure_Device]].
	975
	976
	977
34.7	978	= 6. FAQ =
2.2	979
34.7	980	== 6.1 How to change the LoRa Frequency Bands/Region ==
	981
34.8	982	You can follow the instructions for [[how to upgrade image>>\|\|anchor="H2.10200BFirmwareChangeLog"]].
2.2	983	When downloading the images, choose the required image file for download.
	984
	985
	986
34.7	987	= 7. Trouble Shooting =
2.2	988
34.7	989	== 7.1 AT Commands input doesn’t work ==
	990
34.9	991	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.
2.2	992
	993
	994
34.9	995	= 8. Order Info =
2.2	996
34.9	997	Part Number: (% style="color:blue" %)LSPH01-XX
2.2	998
	999
34.9	1000	(% style="color:blue" %)XX(%%): The default frequency band
2.2	1001
34.13	1002	* (% style="color:red" %)AS923(%%): LoRaWAN AS923 band
34.9	1003	* (% style="color:red" %)AU915(%%): LoRaWAN AU915 band
	1004	* (% style="color:red" %)EU433(%%): LoRaWAN EU433 band
	1005	* (% style="color:red" %)EU868(%%): LoRaWAN EU868 band
	1006	* (% style="color:red" %)KR920(%%): LoRaWAN KR920 band
	1007	* (% style="color:red" %)US915(%%): LoRaWAN US915 band
34.13	1008	* (% style="color:red" %)IN865(%%): LoRaWAN IN865 band
34.9	1009	* (% style="color:red" %)CN470(%%): LoRaWAN CN470 band
2.2	1010
34.9	1011	= 9. Packing Info =
	1012
	1013
2.2	1014	Package Includes:
	1015
	1016	* LSPH01 LoRaWAN Soil Ph Sensor x 1
	1017
	1018	Dimension and weight:
	1019
	1020	* Device Size: cm
	1021	* Device Weight: g
	1022	* Package Size / pcs : cm
	1023	* Weight / pcs : g
	1024
34.11	1025
2.4	1026	= 10. Support =
2.2	1027
	1028	* 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.
34.12	1029	* 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]].
2.2	1030
23.4	1031

Wiki source code of LSPH01-LoRaWAN Soil pH Sensor User Manual

Applications

Navigation