Wiki source code of PS-LB/LS -- LoRaWAN Air Water Pressure Sensor User Manual

Version 148.3 by Xiaoling on 2025/07/10 16:20

version	line-number	content
70.2	1
6.2	2
	3
142.2	4	[[image:image-20240109154731-4.png\|\|data-xwiki-image-style-alignment="center" height="546" width="769"]]
6.2	5
66.2	6
	7
70.3	8
	9
	10
	11
70.4	12	Table of Contents :
70.3	13
42.4	14	{{toc/}}
6.2	15
	16
	17
42.5	18
	19
	20
16.2	21	= 1. Introduction =
6.2	22
9.2	23	== 1.1 What is LoRaWAN Pressure Sensor ==
	24
	25
42.31	26	(((
72.7	27	The Dragino PS-LB/LS series sensors are (% style="color:blue" %)LoRaWAN Pressure Sensor(%%) for Internet of Things solution. PS-LB/LS can measure Air, Water pressure and liquid level and upload the sensor data via wireless to LoRaWAN IoT server.
42.31	28	)))
6.2	29
42.31	30	(((
72.7	31	The PS-LB/LS series sensors include (% style="color:blue" %)Thread Installation Type(%%) and (% style="color:blue" %)Immersion Type(%%), it supports different pressure range which can be used for different measurement requirement.
42.31	32	)))
6.2	33
42.31	34	(((
72.7	35	The LoRa wireless technology used in PS-LB/LS 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.
42.31	36	)))
6.2	37
42.31	38	(((
72.7	39	PS-LB/LS supports BLE configure and wireless OTA update which make user easy to use.
42.31	40	)))
6.2	41
42.31	42	(((
97.1	43	PS-LB/LS is powered by (% style="color:blue" %)8500mAh Li-SOCI2 battery (%%)or (% style="color:blue" %)solar powered + Li-ion battery (%%), it is designed for long term use up to 5 years.
42.31	44	)))
6.2	45
42.31	46	(((
72.7	47	Each PS-LB/LS 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.
42.31	48	)))
6.2	49
	50
9.2	51	== 1.2 Features ==
6.2	52
	53
	54	* LoRaWAN 1.0.3 Class A
	55	* Ultra-low power consumption
	56	* Measure air / gas or water pressure
	57	* Different pressure range available
	58	* Thread Installation Type or Immersion Type
	59	* Monitor Battery Level
	60	* Bands: CN470/EU433/KR920/US915/EU868/AS923/AU915/IN865
	61	* Support Bluetooth v5.1 and LoRaWAN remote configure
	62	* Support wireless OTA update firmware
	63	* Uplink on periodically
	64	* Downlink to change configure
47.1	65	* Controllable 3.3v,5v and 12v output to power external sensor
70.6	66	* 8500mAh Li/SOCl2 Battery (PS-LB)
97.1	67	* Solar panel + 3000mAh Li-ion battery (PS-LS)
6.2	68
9.2	69	== 1.3 Specification ==
	70
	71
42.17	72	(% style="color:#037691" %)Micro Controller:
6.2	73
	74	* MCU: 48Mhz ARM
	75	* Flash: 256KB
	76	* RAM: 64KB
	77
42.17	78	(% style="color:#037691" %)Common DC Characteristics:
6.2	79
72.5	80	* Supply Voltage: Built-in Battery , 2.5v ~~ 3.6v
6.2	81	* Operating Temperature: -40 ~~ 85°C
	82
42.17	83	(% style="color:#037691" %)LoRa Spec:
6.2	84
57.1	85	* Frequency Range, Band 1 (HF): 862 ~~ 1020 Mhz,Band 2 (LF): 410 ~~ 528 Mhz
6.2	86	* Max +22 dBm constant RF output vs.
	87	* RX sensitivity: down to -139 dBm.
	88	* Excellent blocking immunity
	89
42.17	90	(% style="color:#037691" %)Current Input Measuring :
6.2	91
	92	* Range: 0 ~~ 20mA
	93	* Accuracy: 0.02mA
	94	* Resolution: 0.001mA
	95
42.17	96	(% style="color:#037691" %)Voltage Input Measuring:
6.2	97
	98	* Range: 0 ~~ 30v
	99	* Accuracy: 0.02v
	100	* Resolution: 0.001v
	101
42.17	102	(% style="color:#037691" %)Battery:
6.2	103
	104	* Li/SOCI2 un-chargeable battery
	105	* Capacity: 8500mAh
	106	* Self-Discharge: <1% / Year @ 25°C
	107	* Max continuously current: 130mA
	108	* Max boost current: 2A, 1 second
	109
42.17	110	(% style="color:#037691" %)Power Consumption
6.2	111
	112	* Sleep Mode: 5uA @ 3.3v
	113	* LoRa Transmit Mode: 125mA @ 20dBm, 82mA @ 14dBm
	114
9.2	115	== 1.4 Probe Types ==
6.2	116
9.2	117	=== 1.4.1 Thread Installation Type ===
6.2	118
	119
9.2	120	[[image:1675071448299-229.png]]
6.2	121
9.2	122	* Hersman Pressure Transmitter
	123	* Measuring Range: -0.1 ~~ 0 ~~ 60MPa, see order info.
	124	* Accuracy: 0.2% F.S
	125	* Long-Term Stability: 0.2% F.S ±0.05%
	126	* Overload 200% F.S
	127	* Zero Temperature Drift: 0.03% FS/℃(≤100Kpa), 0.02%FS/℃(＞100Kpa)
	128	* FS Temperature Drift: 0.003% FS/℃(≤100Kpa), 0.002%FS/℃(＞100Kpa)
	129	* Storage temperature: -30℃~~80℃
	130	* Operating temperature: -20℃~~60℃
	131	* Connector Type: Various Types, see order info
6.2	132
9.2	133	=== 1.4.2 Immersion Type ===
6.2	134
	135
129.2	136	[[image:image-20240109160445-5.png\|\|height="199" width="150"]]
9.2	137
	138	* Immersion Type, Probe IP Level: IP68
	139	* Measuring Range: Measure range can be customized, up to 100m.
	140	* Accuracy: 0.2% F.S
	141	* Long-Term Stability: ±0.2% F.S / Year
98.3	142	* Storage temperature: -30°C~~80°C
	143	* Operating temperature: 0°C~~50°C
139.1	144	* Probe Material: 316 stainless steels
	145	* Cable model specifications： CGYPU 5*0.2mm2
	146	* Usage characteristics of Cable
	147	1） Operating temperature：-40℃— +70℃
	148	2） -30℃ bending cable 15 times of outer diameter can work normally
9.2	149
80.1	150	=== 1.4.3 Wireless Differential Air Pressure Sensor ===
	151
129.2	152	[[image:image-20240511174954-1.png\|\|height="193" width="193"]]
80.1	153
90.1	154	* Measuring Range: -100KPa~~0~~100KPa(Optional measuring range).
80.1	155	* Accuracy: 0.5% F.S, resolution is 0.05%.
	156	* Overload: 300% F.S
	157	* Zero temperature drift: ±0.03%F.S/°C
98.3	158	* Operating temperature: -20°C~~60°C
	159	* Storage temperature: -20°C~~60°C
80.1	160	* Compensation temperature: 0~~50°C
	161
72.4	162	== 1.5 Application and Installation ==
13.2	163
72.4	164	=== 1.5.1 Thread Installation Type ===
13.2	165
	166
126.2	167	(% style="color:blue" %)Application:
6.2	168
	169	* Hydraulic Pressure
	170	* Petrochemical Industry
	171	* Health and Medical
	172	* Food & Beverage Processing
	173	* Auto-controlling house
	174	* Constant Pressure Water Supply
	175	* Liquid Pressure measuring
	176
	177	Order the suitable thread size and install to measure the air / liquid pressure
	178
13.2	179	[[image:1675071670469-145.png]]
6.2	180
	181
72.4	182	=== 1.5.2 Immersion Type ===
6.2	183
	184
126.2	185	(% style="color:blue" %)Application:
6.2	186
	187	Liquid & Water Pressure / Level detect.
	188
13.2	189	[[image:1675071725288-579.png]]
6.2	190
	191
89.1	192	Below is the wiring to for connect the probe to the device.
6.2	193
74.1	194	The Immersion Type Sensor has different variant which defined by Ixx. For example, this means two points:
6.2	195
74.1	196	* Cable Length: 10 Meters
	197	* Water Detect Range: 0 ~~ 10 Meters.
	198
13.2	199	[[image:1675071736646-450.png]]
6.2	200
	201
13.2	202	[[image:1675071776102-240.png]]
6.2	203
119.1	204	Size of immersion type water depth sensor:
6.2	205
119.1	206	[[image:image-20250401102131-1.png\|\|height="268" width="707"]]
88.1	207
119.1	208
88.1	209	=== 1.5.3 Wireless Differential Air Pressure Sensor ===
	210
	211
126.2	212	(% style="color:blue" %)Application:
88.1	213
	214	Indoor Air Control & Filter clogging Detect.
	215
	216	[[image:image-20240513100129-6.png]]
	217
	218	[[image:image-20240513100135-7.png]]
	219
	220
89.1	221	Below is the wiring to for connect the probe to the device.
88.1	222
	223	[[image:image-20240513093957-1.png]]
	224
	225
	226	Size of wind pressure transmitter:
	227
128.2	228	[[image:image-20240513094047-2.png\|\|height="462" width="518"]]
88.1	229
126.2	230	(% style="color:red" %)Note: The above dimensions are measured by hand, and the numerical error of the shell is within ±0.2mm.
88.1	231
	232
72.4	233	== 1.6 Sleep mode and working mode ==
6.2	234
	235
128.2	236	Deep Sleep Mode: Sensor doesn't have any LoRaWAN activate. This mode is used for storage and shipping to save battery life.
6.2	237
128.2	238	Working Mode: In this mode, Sensor will work as LoRaWAN Sensor to Join LoRaWAN network and send out sensor data to server. Between each sampling/tx/rx periodically, sensor will be in IDLE mode), in IDLE mode, sensor has the same power consumption as Deep Sleep mode.
6.2	239
	240
72.4	241	== 1.7 Button & LEDs ==
6.2	242
	243
128.2	244	[[image:image-20250419092225-1.jpeg]]
6.2	245
53.28	246	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
123.2	247	\|=(% style="width: 167px;background-color:#4F81BD;color:white" %)Behavior on ACT\|=(% style="width: 117px;background-color:#4F81BD;color:white" %)Function\|=(% style="width: 226px;background-color:#4F81BD;color:white" %)Action
146.1	248	\|[[image:1749540420016-961.png]] 1~~3s\|(% style="background-color:#f2f2f2; width:117px" %)Send an uplink\|(% style="background-color:#f2f2f2; width:225px" %)(((
123.2	249	If sensor is already Joined to LoRaWAN network, sensor will send an uplink packet, blue led will blink once.
6.2	250	Meanwhile, BLE module will be active and user can connect via BLE to configure device.
	251	)))
146.1	252	\|[[image:1749540423574-437.png]] >3s\|(% style="background-color:#f2f2f2; width:117px" %)Active Device\|(% style="background-color:#f2f2f2; width:225px" %)(((
123.2	253	Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to JOIN LoRaWAN network.
	254	Green led will solidly turn on for 5 seconds after joined in network.
6.2	255	Once sensor is active, BLE module will be active and user can connect via BLE to configure device, no matter if device join or not join LoRaWAN network.
	256	)))
146.1	257	\|[[image:1749540397649-875.png]] x5\|(% style="background-color:#f2f2f2; width:117px" %)Deactivate Device\|(% style="background-color:#f2f2f2; width:225px" %)Red led will solid on for 5 seconds. Means PS-LB is in Deep Sleep Mode.
6.2	258
72.4	259	== 1.8 Pin Mapping ==
6.2	260
	261
15.2	262	[[image:1675072568006-274.png]]
6.2	263
	264
72.4	265	== 1.9 BLE connection ==
6.2	266
	267
72.7	268	PS-LB/LS support BLE remote configure.
6.2	269
	270
	271	BLE can be used to configure the parameter of sensor or see the console output from sensor. BLE will be only activate on below case:
	272
	273	* Press button to send an uplink
	274	* Press button to active device.
	275	* Device Power on or reset.
	276
	277	If there is no activity connection on BLE in 60 seconds, sensor will shut down BLE module to enter low power mode.
	278
	279
72.4	280	== 1.10 Mechanical ==
6.2	281
98.3	282	=== 1.10.1 for LB version ===
6.2	283
	284
123.2	285	[[image:image-20250401163530-1.jpeg]]
6.2	286
	287
72.4	288	=== 1.10.2 for LS version ===
6.2	289
72.2	290
123.2	291	[[image:image-20250401163539-2.jpeg]]
72.2	292
	293
72.8	294	= 2. Configure PS-LB/LS to connect to LoRaWAN network =
26.2	295
	296	== 2.1 How it works ==
	297
	298
123.2	299	The PS-LB/LS 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 activate the PS-LB/LS. It will automatically join the network via OTAA and start to send the sensor value. The default uplink interval is 20 minutes.
6.2	300
	301
26.2	302	== 2.2 Quick guide to connect to LoRaWAN server (OTAA) ==
	303
	304
6.2	305	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 [[LPS8v2>>url:https://www.dragino.com/products/lora-lorawan-gateway/item/228-lps8v2.html]] as a LoRaWAN gateway in this example.
	306
129.2	307	[[image:image-20250419162538-1.png]]
6.2	308
	309
	310	The LPS8V2 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.
	311
	312
130.3	313	(% style="color:blue" %)Step 1: Create a device in TTN with the OTAA keys from PS-LB/LS.
6.2	314
72.8	315	Each PS-LB/LS is shipped with a sticker with the default device EUI as below:
6.2	316
54.3	317	[[image:image-20230426085320-1.png\|\|height="234" width="504"]]
6.2	318
	319
	320	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
	321
130.2	322	Create the application.
6.2	323
130.2	324	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/SAC01L_LoRaWAN_Temperature%26Humidity_Sensor_User_Manual/WebHome/image-20250423093843-1.png?width=756&height=264&rev=1.1\|\|alt="image-20250423093843-1.png"]]
6.2	325
130.2	326	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111305-2.png?width=1000&height=572&rev=1.1\|\|alt="image-20240907111305-2.png"]]
6.2	327
	328
130.2	329	Add devices to the created Application.
6.2	330
130.2	331	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111659-3.png?width=977&height=185&rev=1.1\|\|alt="image-20240907111659-3.png"]]
6.2	332
130.2	333	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907111820-5.png?width=975&height=377&rev=1.1\|\|alt="image-20240907111820-5.png"]]
6.2	334
	335
130.2	336	Enter end device specifics manually.
6.2	337
130.2	338	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112136-6.png?width=697&height=687&rev=1.1\|\|alt="image-20240907112136-6.png"]]
6.2	339
	340
130.2	341	Add DevEUI and AppKey. Customize a platform ID for the device.
6.2	342
130.2	343	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LTC2-LB--LoRaWAN_Temperature_Transmitter_User_Manual/WebHome/image-20240907112427-7.png?rev=1.1\|\|alt="image-20240907112427-7.png"]]
6.2	344
	345
130.3	346	(% style="color:blue" %)Step 2: Add decoder.
6.2	347
130.2	348	In TTN, user can add a custom payload so it shows friendly reading.
	349
	350	Click this link to get the decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder/tree/main/>>url:https://github.com/dragino/dragino-end-node-decoder/tree/main/]]
	351
	352	Below is TTN screen shot:
	353
	354	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140556-1.png?width=1184&height=488&rev=1.1\|\|alt="image-20241009140556-1.png" height="488" width="1184"]]
	355
	356	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/LDS25-LBLDS25-LS--LoRaWAN_LiDAR_Distance_Auto-Clean_Sensor_User_Manual/WebHome/image-20241009140603-2.png?width=1168&height=562&rev=1.1\|\|alt="image-20241009140603-2.png" height="562" width="1168"]]
	357
	358
130.3	359	(% style="color:blue" %)Step 3: Activate on PS-LB/LS
130.2	360
72.8	361	Press the button for 5 seconds to activate the PS-LB/LS.
6.2	362
123.2	363	Green led will fast blink 5 times, device will enter OTA mode for 3 seconds. And then start to JOIN LoRaWAN network. Green led will solidly turn on for 5 seconds after joined in network.
6.2	364
	365	After join success, it will start to upload messages to TTN and you can see the messages in the panel.
	366
	367
27.2	368	== 2.3 Uplink Payload ==
6.2	369
27.2	370	=== 2.3.1 Device Status, FPORT~=5 ===
6.2	371
	372
72.8	373	Include device configure status. Once PS-LB/LS Joined the network, it will uplink this message to the server.
6.2	374
72.8	375	Users can also use the downlink command(0x26 01) to ask PS-LB/LS to resend this uplink.
6.2	376
53.28	377	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
130.5	378	\|(% colspan="6" style="background-color:#4f81bd; color:white" %)Device Status (FPORT=5)
123.2	379	\|(% style="background-color:#f2f2f2; width:103px" %)Size (bytes)\|(% style="background-color:#f2f2f2; width:72px" %)1\|(% style="background-color:#f2f2f2" %)2\|(% style="background-color:#f2f2f2; width:91px" %)1\|(% style="background-color:#f2f2f2; width:86px" %)1\|(% style="background-color:#f2f2f2; width:44px" %)2
	380	\|(% style="background-color:#f2f2f2; width:103px" %)Value\|(% style="background-color:#f2f2f2; width:72px" %)Sensor Model\|(% style="background-color:#f2f2f2" %)Firmware Version\|(% style="background-color:#f2f2f2; width:91px" %)Frequency Band\|(% style="background-color:#f2f2f2; width:86px" %)Sub-band\|(% style="background-color:#f2f2f2; width:44px" %)BAT
6.2	381
	382	Example parse in TTNv3
	383
27.2	384	[[image:1675144504430-490.png]]
6.2	385
	386
123.2	387	Sensor Model: For PS-LB/LS, this value is 0x16
6.2	388
123.2	389	Firmware Version: 0x0100, Means: v1.0.0 version
6.2	390
123.2	391	Frequency Band:
6.2	392
	393	*0x01: EU868
	394
	395	*0x02: US915
	396
	397	*0x03: IN865
	398
	399	*0x04: AU915
	400
	401	*0x05: KZ865
	402
	403	*0x06: RU864
	404
	405	*0x07: AS923
	406
	407	*0x08: AS923-1
	408
	409	*0x09: AS923-2
	410
	411	*0x0a: AS923-3
	412
	413	*0x0b: CN470
	414
	415	*0x0c: EU433
	416
	417	*0x0d: KR920
	418
	419	*0x0e: MA869
	420
	421
123.2	422	Sub-Band:
6.2	423
	424	AU915 and US915:value 0x00 ~~ 0x08
	425
	426	CN470: value 0x0B ~~ 0x0C
	427
	428	Other Bands: Always 0x00
	429
	430
123.2	431	Battery Info:
6.2	432
	433	Check the battery voltage.
	434
	435	Ex1: 0x0B45 = 2885mV
	436
	437	Ex2: 0x0B49 = 2889mV
	438
	439
42.11	440	=== 2.3.2 Sensor value, FPORT~=2 ===
6.2	441
	442
	443	Uplink payload includes in total 9 bytes.
	444
	445
123.2	446	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
73.2	447	\|(% style="background-color:#4f81bd; color:white; width:97px" %)(((
130.5	448	Size(bytes)
	449	)))\|(% style="background-color:#4f81bd; color:white; width:50px" %)2\|(% style="background-color:#4f81bd; color:white; width:71px" %)2\|(% style="background-color:#4f81bd; color:white; width:98px" %)2\|(% style="background-color:#4f81bd; color:white; width:73px" %)2\|(% style="background-color:#4f81bd; color:white; width:122px" %)1
60.4	450	\|(% style="width:97px" %)Value\|(% style="width:48px" %)[[BAT>>\|\|anchor="H2.3.3BatteryInfo"]]\|(% style="width:71px" %)[[Probe Model>>\|\|anchor="H2.3.4ProbeModel"]]\|(% style="width:98px" %)[[0 ~~~~ 20mA value>>\|\|anchor="H2.3.507E20mAvalue28IDC_IN29"]]\|(% style="width:73px" %)[[0 ~~~~ 30v value>>\|\|anchor="H2.3.607E30Vvalue28pinVDC_IN29"]]\|(% style="width:122px" %)[[IN1 &IN2 Interrupt flag>>\|\|anchor="H2.3.7IN126IN226INTpin"]]
6.2	451
37.2	452	[[image:1675144608950-310.png]]
6.2	453
	454
47.1	455	=== 2.3.3 Battery Info ===
45.1	456
	457
72.8	458	Check the battery voltage for PS-LB/LS.
6.2	459
	460	Ex1: 0x0B45 = 2885mV
	461
	462	Ex2: 0x0B49 = 2889mV
	463
	464
47.1	465	=== 2.3.4 Probe Model ===
45.1	466
6.2	467
72.8	468	PS-LB/LS has different kind of probe, 4~~20mA represent the full scale of the measuring range. So a 12mA output means different meaning for different probe.
6.2	469
123.2	470	For example.
6.2	471
53.28	472	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
130.5	473	\|(% style="background-color:#4f81bd; color:white" %)Part Number\|(% style="background-color:#4f81bd; color:white" %)Probe Used\|(% style="background-color:#4f81bd; color:white" %)4~~20mA scale\|(% style="background-color:#4f81bd; color:white" %)Example: 12mA meaning
72.8	474	\|(% style="background-color:#f2f2f2" %)PS-LB/LS-I3\|(% style="background-color:#f2f2f2" %)immersion type with 3 meters cable\|(% style="background-color:#f2f2f2" %)0~~3 meters\|(% style="background-color:#f2f2f2" %)1.5 meters pure water
	475	\|(% style="background-color:#f2f2f2" %)PS-LB/LS-I5\|(% style="background-color:#f2f2f2" %)immersion type with 5 meters cable\|(% style="background-color:#f2f2f2" %)0~~5 meters\|(% style="background-color:#f2f2f2" %)2.5 meters pure water
	476	\|(% style="background-color:#f2f2f2" %)PS-LB/LS-T20-B\|(% style="background-color:#f2f2f2" %)T20 threaded probe\|(% style="background-color:#f2f2f2" %)0~~1MPa\|(% style="background-color:#f2f2f2" %)0.5MPa air / gas or water pressure
6.2	477
47.1	478	The probe model field provides the convenient for server to identical how it should parse the 4~~20mA sensor value and get the correct value.
6.2	479
	480
135.1	481	When connecting to current sensors sold by our company, you can convert current readings to corresponding values by simply configuring the [[AT+PROBE>>\|\|anchor="H3.3.4SettheProbeModel"]] command. If you prefer not to configure this command on the sensor, you can uniformly handle the conversion in the payload decoder instead.
134.1	482
	483	Examples for decoder implementation:
	484
136.1	485	~1. For AT+PROBE=0005, add the following processing in your decoder:
134.1	486
	487	[[image:image-20250512144042-1.png]]
	488
	489	[[image:image-20250512144122-2.png]]
	490
	491	2. For AT+PROBE=0102, add the following processing in your decoder(Corresponding to the position shown in the above screenshot).
	492
	493	bytes[i]=0x01;bytes[1+i]=0x02;
	494
	495	bytes[2]=0x01;bytes[3]=0x02;
	496
	497
47.1	498	=== 2.3.5 0~~20mA value (IDC_IN) ===
37.2	499
47.1	500
123.2	501	The output value from Pressure Probe, use together with Probe Model to get the pressure value or water level.
6.2	502
123.2	503	Example:
6.2	504
	505	27AE(H) = 10158 (D)/1000 = 10.158mA.
	506
	507
50.1	508	Instead of pressure probe, User can also connect a general 4~~20mA in this port to support different types of 4~~20mA sensors. below is the connection example:
	509
	510	[[image:image-20230225154759-1.png\|\|height="408" width="741"]]
	511
	512
99.2	513	=== 2.3.6 0~~30V value (pin VDC_IN) ===
6.2	514
37.2	515
6.2	516	Measure the voltage value. The range is 0 to 30V.
	517
123.2	518	Example:
6.2	519
	520	138E(H) = 5006(D)/1000= 5.006V
	521
	522
47.1	523	=== 2.3.7 IN1&IN2&INT pin ===
6.2	524
37.2	525
6.2	526	IN1 and IN2 are used as digital input pins.
	527
123.2	528	Example:
6.2	529
42.17	530	09 (H): (0x09&0x08)>>3=1 IN1 pin is high level.
6.2	531
42.17	532	09 (H): (0x09&0x04)>>2=0 IN2 pin is low level.
6.2	533
	534
123.2	535	This data field shows if this packet is generated by Interrupt Pin or not. [[Click here>>\|\|anchor="H3.3.2SetInterruptMode"]] for the hardware and software set up. Note: The Internet Pin is a separate pin in the screw terminal.
6.2	536
123.2	537	Example:
6.2	538
42.17	539	09 (H): (0x09&0x02)>>1=1 The level of the interrupt pin.
6.2	540
42.17	541	09 (H): 0x09&0x01=1 0x00: Normal uplink packet.
6.2	542
	543	0x01: Interrupt Uplink Packet.
	544
50.2	545
72.10	546	=== 2.3.8 Sensor value, FPORT~=7 ===
6.2	547
47.1	548
72.12	549	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:500px" %)
73.2	550	\|(% style="background-color:#4f81bd; color:white; width:65px" %)(((
130.5	551	Size(bytes)
	552	)))\|(% style="background-color:#4f81bd; color:white; width:35px" %)2\|(% style="background-color:#4f81bd; color:white; width:400px" %)n
60.3	553	\|(% style="width:94px" %)Value\|(% style="width:43px" %)[[BAT>>\|\|anchor="H2.3.3BatteryInfo"]]\|(% style="width:367px" %)(((
47.1	554	Voltage value, each 2 bytes is a set of voltage values.
	555	)))
	556
	557	[[image:image-20230220171300-1.png\|\|height="207" width="863"]]
	558
	559	Multiple sets of data collected are displayed in this form：
	560
48.1	561	[voltage value1], [voltage value2], [voltage value3],…[voltage value n/2]
47.1	562
	563
45.2	564	=== 2.3.9 Decode payload in The Things Network ===
6.2	565
	566
37.2	567	While using TTN network, you can add the payload format to decode the payload.
6.2	568
37.2	569	[[image:1675144839454-913.png]]
6.2	570
	571
72.8	572	PS-LB/LS TTN Payload Decoder: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
6.2	573
	574
37.2	575	== 2.4 Uplink Interval ==
6.2	576
	577
72.8	578	The PS-LB/LS by default uplink the sensor data every 20 minutes. User can change this interval by AT Command or LoRaWAN Downlink Command. See this link: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.1ChangeUplinkInterval>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.1ChangeUplinkInterval\|\|style="background-color: rgb(255, 255, 255);"]]
6.2	579
	580
37.2	581	== 2.5 Show Data in DataCake IoT Server ==
6.2	582
	583
	584	[[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:
	585
123.2	586	Step 1: Be sure that your device is programmed and properly connected to the network at this time.
6.2	587
123.2	588	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:
6.2	589
37.2	590	[[image:1675144951092-237.png]]
6.2	591
	592
37.2	593	[[image:1675144960452-126.png]]
6.2	594
	595
123.2	596	Step 3: Create an account or log in Datacake.
6.2	597
123.2	598	Step 4: Create PS-LB/LS product.
6.2	599
37.2	600	[[image:1675145004465-869.png]]
6.2	601
	602
37.2	603	[[image:1675145018212-853.png]]
6.2	604
	605
37.2	606	[[image:1675145029119-717.png]]
6.2	607
	608
123.2	609	Step 5: add payload decode
6.2	610
37.2	611	[[image:1675145051360-659.png]]
6.2	612
	613
37.2	614	[[image:1675145060812-420.png]]
6.2	615
	616
	617	After added, the sensor data arrive TTN, it will also arrive and show in Datacake.
	618
37.2	619	[[image:1675145081239-376.png]]
6.2	620
	621
93.1	622	== 2.6 Datalog Feature (Since V1.1) ==
6.2	623
99.2	624
146.3	625	Datalog Feature is to ensure IoT Server can get all sampling data from Sensor even if the LoRaWAN network is down. For each sampling, PS-LB will store the reading for future retrieving purposes.
6.2	626
93.1	627
147.1	628	=== 2.6.1 How datalog works ===
93.1	629
99.2	630
146.3	631	PS-LB will wait for ACK for every uplink, when there is no LoRaWAN network,PS-LB will mark these records with non-ack messages and store the sensor data, and it will send all messages (10s interval) after the network recovery.
93.1	632
146.2	633	* (((
146.3	634	a) PS-LB will do an ACK check for data records sending to make sure every data arrive server.
146.2	635	)))
	636	* (((
146.3	637	b) PS-LB will send data in CONFIRMED Mode, but PS-LB won't re-transmit the packet if it doesn't get ACK, it will just mark it as a NONE-ACK message. In a future uplink if PS-LB gets a ACK, PS-LB will consider there is a network connection and resend all NONE-ACK messages.
93.1	638
146.2	639
	640	)))
93.1	641
147.1	642	=== 2.6.2 Enable Datalog ===
93.1	643
	644
146.2	645	User need to make sure below two settings are enable to use datalog;
93.1	646
146.2	647	* (% style="color:blue" %)SYNCMOD=1(Default)(%%) to enable sync time via LoRaWAN MAC command, click here ([[AT+SYNCMOD>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H4.6Settimesynchronizationmethod28ThenetworkservermustsupportLoRaWANv1.0.329]]) for detailed instructions.
	648	* (% style="color:blue" %)PNACKMD=1(%%) to enable datalog feature, click here ([[AT+PNACKMD>>https://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.26RequesttheservertosendanACK]]) for detailed instructions.
93.1	649
99.2	650
93.1	651
146.3	652	Once PS-LB Joined LoRaWAN network, it will send the MAC command (DeviceTimeReq) and the server will reply with (DeviceTimeAns) to send the current time to PS-LB. If PS-LB fails to get the time from the server, PS-LB will use the internal time and wait for next time request (AT+SYNCTDC to set the time request period, default is 10 days).
93.1	653
146.2	654	(% style="color:red" %)Note: LoRaWAN Server need to support LoRaWAN v1.0.3(MAC v1.0.3) or higher to support this MAC command feature, Chirpstack,TTN V3 v3 and loriot support but TTN V3 v2 doesn't support. If server doesn't support this command, it will through away uplink packet with this command, so user will lose the packet with time request for TTN V3 v2 if SYNCMOD=1.
93.1	655
	656
147.1	657	=== 2.6.3 Unix TimeStamp ===
93.1	658
	659
146.2	660	PS-LB uses Unix TimeStamp format based on
93.1	661
146.2	662	[[image:image-20250401163826-3.jpeg]]
93.1	663
146.2	664	Users can get this time from the link: [[https:~~/~~/www.epochconverter.com/>>url:https://www.epochconverter.com/]] :
93.1	665
146.2	666	Below is the converter example:
93.1	667
146.2	668	[[image:image-20250401163906-4.jpeg]]
	669
	670
147.1	671	=== 2.6.4 Poll sensor value ===
93.1	672
	673	Users can poll sensor values based on timestamps. Below is the downlink command.
	674
116.1	675	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:470px" %)
123.2	676	\|=(% colspan="4" style="width: 160px; background-color:#4F81BD;color:white" %)Downlink Command to poll Open/Close status (0x31)
	677	\|(% style="background-color:#f2f2f2; width:67px" %)1byte\|(% style="background-color:#f2f2f2; width:145px" %)4bytes\|(% style="background-color:#f2f2f2; width:133px" %)4bytes\|(% style="background-color:#f2f2f2; width:163px" %)1byte
116.1	678	\|(% style="background-color:#f2f2f2; width:67px" %)31\|(% style="background-color:#f2f2f2; width:145px" %)Timestamp start\|(% style="background-color:#f2f2f2; width:133px" %)(((
	679	Timestamp end
	680	)))\|(% style="background-color:#f2f2f2; width:163px" %)Uplink Interval
	681
	682	Timestamp start and Timestamp end-use Unix TimeStamp format as mentioned above. Devices will reply with all data logs during this period, using the uplink interval.
	683
	684	For example, downlink command[[image:image-20250117104812-1.png]]
	685
	686	Is to check 2024/12/20 09:34:59 to 2024/12/20 14:34:59's data
	687
	688	Uplink Internal =5s，means PS-LB will send one packet every 5s. range 5~~255s.
	689
	690
147.1	691	=== 2.6.5 Datalog Uplink payload (FPORT~=3) ===
116.1	692
	693
	694	The Datalog uplinks will use below payload format.
	695
123.2	696	Retrieval data payload:
116.1	697
123.2	698	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
116.1	699	\|=(% style="width: 60px;background-color:#4F81BD;color:white" %)(((
123.2	700	Size(bytes)
	701	)))\|=(% style="width: 70px; background-color:#4F81BD;color:white" %)2\|=(% style="width: 70px; background-color:#4F81BD;color:white" %)2\|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)2\|=(% style="width: 150px; background-color: rgb(79, 129, 189); color: white;" %)1\|=(% style="width: 80px; background-color: rgb(79, 129, 189); color: white;" %)4
116.1	702	\|(% style="width:103px" %)Value\|(% style="width:68px" %)(((
123.2	703	Probe_mod
116.1	704	)))\|(% style="width:104px" %)(((
123.2	705	VDC_intput_V
116.1	706	)))\|(% style="width:83px" %)(((
123.2	707	IDC_intput_mA
116.1	708	)))\|(% style="width:201px" %)(((
	709	IN1_pin_level& IN2_pin_level& Exti_pin_level&Exti_status
	710	)))\|(% style="width:86px" %)Unix Time Stamp
123.4	711
123.2	712	IN1_pin_level & IN2_pin_level & Exti_pin_level & Exti_status:
116.1	713
	714	[[image:image-20250117104847-4.png]]
	715
	716
123.2	717	No ACK Message: 1: This message means this payload is fromn Uplink Message which doesn't get ACK from the server before ( for PNACKMD=1 feature)
116.1	718
123.2	719	Poll Message Flag: 1: This message is a poll message reply.
116.1	720
	721	* Poll Message Flag is set to 1.
	722
	723	* Each data entry is 11 bytes, to save airtime and battery, devices will send max bytes according to the current DR and Frequency bands.
	724
	725	For example, in US915 band, the max payload for different DR is:
	726
123.2	727	a) DR0: max is 11 bytes so one entry of data
116.1	728
123.2	729	b) DR1: max is 53 bytes so devices will upload 4 entries of data (total 44 bytes)
116.1	730
123.2	731	c) DR2: total payload includes 11 entries of data
116.1	732
123.2	733	d) DR3: total payload includes 22 entries of data.
116.1	734
	735	If devise doesn't have any data in the polling time. Device will uplink 11 bytes of 0
	736
123.2	737	Example:
116.1	738
	739	If PS-LB-NA has below data inside Flash:
	740
	741	[[image:image-20250117104837-3.png]]
	742
	743
	744	If user sends below downlink command: 316788D9BF6788DB6305
	745
	746	Where : Start time: 6788D9BF = time 25/1/16 10:04:47
	747
	748	Stop time: 6788DB63 = time 25/1/16 10:11:47
	749
	750
123.2	751	PA-LB-NA will uplink this payload.
116.1	752
	753	[[image:image-20250117104827-2.png]]
	754
123.2	755
116.1	756	00001B620000406788D9BF 00000D130000406788D9FB 00000D120000406788DA37 00000D110000406788DA73 00000D100000406788DAAF 00000D100000406788DAEB 00000D0F0000406788DB27 00000D100000406788DB63
93.1	757
123.2	758
116.1	759	Where the first 11 bytes is for the first entry :
98.4	760
123.2	761
116.1	762	0000 0D10 0000 40 6788DB63
93.1	763
	764
123.2	765	Probe_mod = 0x0000 = 0000
93.1	766
	767
123.2	768	VDC_intput_V = 0x0D10/1000=3.344V
93.1	769
123.2	770	IDC_intput_mA = 0x0000/1000=0mA
93.1	771
	772
123.2	773	IN1_pin_level = (0x40& 0x08)? "High":"Low" = 0(Low)
116.1	774
123.2	775	IN2_pin_level = (0x40& 0x04)? "High":"Low" = 0(Low)
116.1	776
123.2	777	Exti_pin_level = (0x40& 0x02)? "High":"Low" = 0(Low)
116.1	778
123.2	779	Exti_status = (0x40& 0x01)? "True":"False" = 0(False)
117.1	780
	781
123.2	782	Unix time is 0x6788DB63 = 1737022307s = 2025/1/16 10:11:47
117.1	783
123.2	784	Its data format is:
	785
	786	[Probe_mod, VDC_intput_V, IDC_intput_mA, IN1_pin_level, IN2_pin_level, Exti_pin_level, water_deep, Data_time],[Probe_mod, VDC_intput_V, IDC_intput_mA, IN1_pin_level, IN2_pin_level, Exti_pin_level, water_deep, Data_time],...
	787
	788	Note: water_deep in the data needs to be converted using decoding to get it.
	789
	790
147.1	791	=== 2.6.6 Decoder in TTN V3 ===
116.1	792
93.1	793	[[image:http://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/CPL01%20LoRaWAN%20Outdoor%20PulseContact%20%20Sensor%20Manual/WebHome/1652862574387-195.png?width=722&height=359&rev=1.1\|\|alt="1652862574387-195.png" height="359" width="722"]]
	794
	795	Please check the decoder from this link: [[https:~~/~~/github.com/dragino/dragino-end-node-decoder>>url:https://github.com/dragino/dragino-end-node-decoder]]
	796
	797
	798	== 2.7 Frequency Plans ==
	799
	800
73.4	801	The PS-LB/LS uses OTAA mode and below frequency plans by default. Each frequency band use different firmware, user update the firmware to the corresponding band for their country.
6.2	802
98.1	803	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/a>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20Frequency%20Band/]]
6.2	804
	805
101.1	806	== 2.8 Report on Change Feature (Since firmware V1.2) ==
6.2	807
98.1	808	=== 2.8.1 Uplink payload(Enable ROC) ===
	809
	810
	811	Used to Monitor the IDC and VDC increments, and send ROC uplink when the IDC or VDC changes exceed.
	812
	813	With ROC enabled, the payload is as follows:
	814
98.5	815	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
98.1	816	\|(% style="background-color:#4f81bd; color:white; width:97px" %)(((
123.2	817	Size(bytes)
	818	)))\|(% style="background-color:#4f81bd; color:white; width:48px" %)2\|(% style="background-color:#4f81bd; color:white; width:71px" %)2\|(% style="background-color:#4f81bd; color:white; width:98px" %)2\|(% style="background-color:#4f81bd; color:white; width:73px" %)2\|(% style="background-color:#4f81bd; color:white; width:122px" %)1
123.6	819	\|(% style="width:98px" %)Value\|(% style="width:48px" %)[[BAT>>\|\|anchor="H2.3.3BatteryInfo"]]\|(% style="width:71px" %)[[Probe Model>>\|\|anchor="H2.3.4ProbeModel"]]\|(% style="width:98px" %)[[0 ~~~~ 20mA value>>\|\|anchor="H2.3.507E20mAvalue28IDC_IN29"]]\|(% style="width:73px" %)[[0 ~~~~ 30v value>>\|\|anchor="H2.3.607E30Vvalue28pinVDC_IN29"]]\|(% style="width:122px" %)(((
98.5	820	[[IN1 &IN2 Interrupt flag>>\|\|anchor="H2.3.7IN126IN226INTpin"]] & ROC_flag
98.1	821	)))
	822
123.2	823	IN1 &IN2 , Interrupt flag , ROC_flag:
98.1	824
98.5	825	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:515px" %)
123.2	826	\|(% style="background-color:#4f81bd; color:white; width:50px" %)Size(bit)\|(% style="background-color:#4f81bd; color:white; width:60px" %)bit7\|(% style="background-color:#4f81bd; color:white; width:62px" %)bit6\|(% style="background-color:#4f81bd; color:white; width:62px" %)bit5\|(% style="background-color:#4f81bd; color:white; width:65px" %)bit4\|(% style="background-color:#4f81bd; color:white; width:56px" %)bit3\|(% style="background-color:#4f81bd; color:white; width:55px" %)bit2\|(% style="background-color:#4f81bd; color:white; width:55px" %)bit1\|(% style="background-color:#4f81bd; color:white; width:50px" %)bit0
98.1	827	\|(% style="width:75px" %)Value\|(% style="width:89px" %)IDC_Roc_flagL\|(% style="width:46.5834px" %)IDC_Roc_flagH\|(% style="width:1px" %)VDC_Roc_flagL\|(% style="width:89px" %)VDC_Roc_flagH\|(% style="width:89px" %)IN1_pin_level\|(% style="width:103px" %)IN2_pin_level\|(% style="width:103px" %)Exti_pin_level\|(% style="width:103px" %)Exti_status
	828
123.2	829	* IDC_Roc_flagL
98.1	830
123.2	831	80 (H): (0x80&0x80)=80(H)=1000 0000(B) bit7=1, "TRUE", This uplink is triggered when the decrease in the IDC compared to the last ROC refresh exceeds the set threshold.
98.1	832
	833	60 (H): (0x60&0x80)=0 bit7=0, "FALSE", This uplink is not triggered when the decrease in the IDC compared to the last ROC refresh exceeds the set threshold.
	834
	835
123.2	836	* IDC_Roc_flagH
98.1	837
123.2	838	60 (H): (0x60&0x40)=60(H)=01000 0000(B) bit6=1, "TRUE", This uplink is triggered when the increase in the value of the IDC compared to the last ROC refresh exceeds the set threshold.
98.1	839
	840	80 (H): (0x80&0x40)=0 bit6=0, "FALSE", This uplink is not triggered when the increase in the value of the IDC compared to the last ROC refresh exceeds the set threshold.
	841
	842
123.2	843	* VDC_Roc_flagL
98.1	844
123.2	845	20 (H): (0x20&0x20)=20(H)=0010 0000(B) bit5=1, "TRUE", This uplink is triggered when the decrease in the VDC compared to the last ROC refresh exceeds the set threshold.
98.1	846
	847	90 (H): (0x90&0x20)=0 bit5=0, "FALSE", This uplink is not triggered when the decrease in the VDC compared to the last ROC refresh exceeds the set threshold.
	848
	849
123.2	850	* VDC_Roc_flagH
98.1	851
123.2	852	90 (H): (0x90&0x10)=10(H)=0001 0000(B) bit4=1, "TRUE", This uplink is triggered when the increase in the value of the VDC compared to the last ROC refresh exceeds the set threshold.
98.1	853
	854	20 (H): (0x20&0x10)=0 bit4=0, "FALSE", This uplink is not triggered when the increase in the value of the VDC compared to the last ROC refresh exceeds the set threshold.
	855
	856
123.2	857	* IN1_pin_level & IN2_pin_level
98.1	858
	859	IN1 and IN2 are used as digital input pins.
	860
	861	80 (H): (0x80&0x08)=0 IN1 pin is low level.
	862
	863	80 (H): (0x09&0x04)=0 IN2 pin is low level.
	864
	865
123.2	866	* Exti_pin_level &Exti_status
98.1	867
	868	This data field shows whether the packet is generated by an interrupt pin.
	869
123.2	870	Note: The Internet pin of the old motherboard is a separate pin in the screw terminal, and the interrupt pin of the new motherboard(SIB V1.3) is the GPIO_EXTI pin.
98.1	871
123.2	872	Exti_pin_level: 80 (H): (0x80&0x02)=0 "low", The level of the interrupt pin.
98.1	873
123.2	874	Exti_status: 80 (H): (0x80&0x01)=0 "False", Normal uplink packet.
98.1	875
	876
	877	=== 2.8.2 Set the Report on Change ===
	878
	879
103.1	880	Feature: Get or Set the Report on Change.
	881
	882
	883	==== 2.8.2.1 Wave alarm mode ====
	884
123.11	885
103.1	886	Feature: By setting the detection period and a change value, the IDC/VDC variable is monitored whether it exceeds the set change value. If this change value is exceeded, the ROC uplink is sent and the comparison value is flushed.
	887
123.2	888	* Change value: The amount by which the next detection value increases/decreases relative to the previous detection value.
	889	* Comparison value: A parameter to compare with the latest ROC test.
103.1	890
123.2	891	AT Command: AT+ROC
98.1	892
103.1	893	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
123.13	894	\|=(% style="width: 163px; background-color: rgb(79, 129, 189); color: white;" %)Command Example\|=(% style="width: 154px; background-color: rgb(79, 129, 189); color: white;" %)Parameters\|=(% style="width: 193px; background-color: rgb(79, 129, 189); color: white;" %)Response/Explanation
103.1	895	\|(% style="width:143px" %)AT+ROC=?\|(% style="width:154px" %)Show current ROC setting\|(% style="width:197px" %)(((
98.1	896	0,0,0,0(default)
	897	OK
	898	)))
	899	\|(% colspan="1" rowspan="4" style="width:143px" %)(((
	900	AT+ROC=a,b,c,d
103.1	901	)))\|(% style="width:154px" %)(((
123.11	902	a: Enable or disable the ROC
103.1	903	)))\|(% style="width:197px" %)(((
123.11	904	0: off
	905	1: Turn on the wave alarm mode, send the ROC uplink when the increment exceeds the set parameter and refresh the comparison value.
	906	2: Turn on the wave alarm mode, send the ROC uplink when the increment exceeds the set parameter and refresh the comparison value. In addition, the comparison value is refreshed when the device sends packets ([[TDC>>\|\|anchor="H3.3.1SetTransmitIntervalTime"]] or [[ACT>>\|\|anchor="H1.7Button26LEDs"]]).
98.1	907	)))
123.11	908	\|(% style="width:154px" %)b: Set the detection interval\|(% style="width:197px" %)(((
103.1	909	Range: 0~~65535s
	910	)))
123.11	911	\|(% style="width:154px" %)c: Setting the IDC change value\|(% style="width:197px" %)Unit: uA
	912	\|(% style="width:154px" %)d: Setting the VDC change value\|(% style="width:197px" %)Unit: mV
98.1	913
123.2	914	Example:
98.1	915
123.11	916	* AT+ROC=0,0,0,0 ~/~/ The ROC function is not used.
103.1	917	* AT+ROC=1,60,3000, 500 ~/~/ Check value every 60 seconds. lf there is change in IDC (>3mA) or VDC (>500mV), sends an ROC uplink, and the comparison value is refreshed.
	918	* AT+ROC=1,60,3000,0 ~/~/ Check value every 60 seconds. lf there is change in IDC (>3mA), send an ROC uplink and the comparison value of IDC is refreshed. dd=0 Means doesn't monitor Voltage.
	919	* AT+ROC=2,60,3000,0 ~/~/ Check value every 60 seconds. lf there is change in IDC (>3mA), send an ROC uplink and the comparison value of IDC is refreshed. dd=0 Means doesn't monitor Voltage. In addition, if the change in the IDC does not exceed 3mA, then the ROC uplink is not sent, and the comparison value is not refreshed by the ROC uplink packet. However, if the device TDC time arrives, or if the user manually sends packets, then the IDC comparison value is also refreshed.
98.1	920
123.2	921	Downlink Command: 0x09 aa bb cc dd
98.1	922
	923	Format: Function code (0x09) followed by 4 bytes.
	924
123.2	925	aa: 1 byte; Set the wave alarm mode.
98.1	926
123.2	927	bb: 2 bytes; Set the detection interval. (second)
98.1	928
123.2	929	cc: 2 bytes; Setting the IDC change threshold. (uA)
98.1	930
123.2	931	dd: 2 bytes; Setting the VDC change threshold. (mV)
98.1	932
123.2	933	Example:
98.1	934
123.11	935	* Downlink Payload: 09 01 00 3C 0B B8 01 F4 ~/~/ Equal to AT+ROC=1,60,3000, 500
	936	* Downlink Payload: 09 01 00 3C 0B B8 00 00 ~/~/ Equal to AT+ROC=1,60,3000,0
	937	* Downlink Payload: 09 02 00 3C 0B B8 00 00 ~/~/ Equal to AT+ROC=2,60,3000,0
98.1	938
123.2	939	Screenshot of parsing example in TTN:
98.1	940
	941	* AT+ROC=1,60,3000, 500.
	942
99.2	943	[[image:https://wiki.dragino.com/xwiki/bin/download/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB-NA--LoRaWAN_Analog_Sensor_User_Manual/WebHome/image-20241019170902-1.png?width=1454&height=450&rev=1.1\|\|alt="image-20241019170902-1.png"]]
98.1	944
	945
103.1	946	==== 2.8.2.2 Over-threshold alarm mode ====
	947
123.11	948
103.1	949	Feature: Monitors whether the IDC/VDC exceeds the threshold by setting the detection period and threshold. Alarm if the threshold is exceeded.
	950
123.2	951	AT Command: AT+ROC=3,a,b,c,d,e
103.1	952
	953	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
123.13	954	\|=(% style="width: 163px; background-color: rgb(79, 129, 189); color: white;" %)Command Example\|=(% style="width: 160px; background-color: rgb(79, 129, 189); color: white;" %)Parameters\|=(% style="width: 187px; background-color: rgb(79, 129, 189); color: white;" %)Response/Explanation
103.1	955	\|(% style="width:143px" %)AT+ROC=?\|(% style="width:160px" %)Show current ROC setting\|(% style="width:185px" %)(((
	956	0,0,0,0(default)
	957	OK
	958	)))
	959	\|(% colspan="1" rowspan="5" style="width:143px" %)(((
123.2	960	AT+ROC=3,a,b,c,d,e
103.1	961	)))\|(% style="width:160px" %)(((
123.11	962	a: Set the detection interval
103.1	963	)))\|(% style="width:185px" %)(((
	964	Range: 0~~65535s
	965	)))
123.11	966	\|(% style="width:160px" %)b: Set the IDC alarm trigger condition\|(% style="width:185px" %)(((
	967	0: Less than the set IDC threshold, Alarm
	968	1: Greater than the set IDC threshold, Alarm
103.1	969	)))
108.1	970	\|(% style="width:160px" %)(((
123.11	971	c: IDC alarm threshold
108.1	972	)))\|(% style="width:185px" %)(((
	973	Unit: uA
	974	)))
123.11	975	\|(% style="width:160px" %)d: Set the VDC alarm trigger condition\|(% style="width:185px" %)(((
	976	0: Less than the set VDC threshold, Alarm
	977	1: Greater than the set VDC threshold, Alarm
103.1	978	)))
123.11	979	\|(% style="width:160px" %)e: VDC alarm threshold\|(% style="width:185px" %)Unit: mV
103.1	980
123.2	981	Example:
103.1	982
123.11	983	* AT+ROC=3,60,0,3000,0,5000 ~/~/ The data is checked every 60 seconds. If the IDC is less than 3mA or the VDC is less than 5000mV, an alarm is generated.
	984	* AT+ROC=3,180,1,3000,1,5000 ~/~/ The data is checked every 180 seconds. If the IDC is greater than 3mA or the VDC is greater than 5000mV, an alarm is generated.
	985	* AT+ROC=3,300,0,3000,1,5000 ~/~/ The data is checked every 300 seconds. If the IDC is less than 3mA or the VDC is greater than 5000mV, an alarm is generated.
103.1	986
123.2	987	Downlink Command: 0x09 03 aa bb cc dd ee
103.1	988
	989	Format: Function code (0x09) followed by 03 and the remaining 5 bytes.
	990
123.2	991	aa: 2 bytes; Set the detection interval.(second)
103.1	992
123.2	993	bb: 1 byte; Set the IDC alarm trigger condition.
103.1	994
123.2	995	cc: 2 bytes; IDC alarm threshold.(uA)
103.1	996
	997
123.2	998	dd: 1 byte; Set the VDC alarm trigger condition.
108.1	999
123.2	1000	ee: 2 bytes; VDC alarm threshold.(mV)
103.1	1001
123.2	1002	Example:
103.1	1003
123.11	1004	* Downlink Payload: 09 03 00 3C 00 0B B8 00 13 38 ~/~/ Equal to AT+ROC=3,60,0,3000,0,5000
	1005	* Downlink Payload: 09 03 00 b4 01 0B B8 01 13 38 ~/~/ Equal to AT+ROC=3,60,1,3000,1,5000
	1006	* Downlink Payload: 09 03 01 2C 00 0B B8 01 13 38 ~/~/ Equal to AT+ROC=3,60,0,3000,1,5000
103.1	1007
123.2	1008	Screenshot of parsing example in TTN:
103.1	1009
108.1	1010	* AT+ROC=3,60,0,3000,0,5000
103.1	1011
111.1	1012	[[image:image-20250116180030-2.png]]
103.1	1013
108.1	1014
98.1	1015	== 2.9 Firmware Change Log ==
	1016
	1017
123.2	1018	Firmware download link:
6.2	1019
	1020	[[https:~~/~~/www.dropbox.com/sh/gf1glloczbzz19h/AABbuYI4WY6VdAmpXo6o1V2Ka?dl=0>>url:https://www.dropbox.com/sh/gf1glloczbzz19h/AABbuYI4WY6VdAmpXo6o1V2Ka?dl=0]]
	1021
	1022
72.8	1023	= 3. Configure PS-LB/LS =
6.2	1024
53.1	1025	== 3.1 Configure Methods ==
37.4	1026
53.7	1027
72.8	1028	PS-LB/LS supports below configure method:
6.2	1029
123.2	1030	* AT Command via Bluetooth Connection (Recommand Way): [[BLE Configure Instruction>>url:http://wiki.dragino.com/xwiki/bin/view/Main/BLE%20Bluetooth%20Remote%20Configure/]].
53.20	1031	* AT Command via UART Connection : See [[FAQ>>\|\|anchor="H6.FAQ"]].
53.1	1032	* LoRaWAN Downlink. Instruction for different platforms: See [[IoT LoRaWAN Server>>url:http://wiki.dragino.com/xwiki/bin/view/Main/]] section.
6.2	1033
53.1	1034	== 3.2 General Commands ==
6.2	1035
53.7	1036
6.2	1037	These commands are to configure:
	1038
	1039	* General system settings like: uplink interval.
	1040	* LoRaWAN protocol & radio related command.
	1041
53.1	1042	They are same for all Dragino Devices which support DLWS-005 LoRaWAN Stack. These commands can be found on the wiki:
6.2	1043
53.1	1044	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
6.2	1045
	1046
72.8	1047	== 3.3 Commands special design for PS-LB/LS ==
53.1	1048
53.15	1049
72.8	1050	These commands only valid for PS-LB/LS, as below:
6.2	1051
	1052
53.1	1053	=== 3.3.1 Set Transmit Interval Time ===
6.2	1054
37.5	1055
6.2	1056	Feature: Change LoRaWAN End Node Transmit Interval.
	1057
123.2	1058	AT Command: AT+TDC
6.2	1059
123.15	1060	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
123.2	1061	\|=(% style="width: 160px; background-color:#4F81BD;color:white" %)Command Example\|=(% style="width: 160px; background-color:#4F81BD;color:white" %)Function\|=(% style="width: 190px;background-color:#4F81BD;color:white" %)Response
53.8	1062	\|(% style="background-color:#f2f2f2; width:157px" %)AT+TDC=?\|(% style="background-color:#f2f2f2; width:166px" %)Show current transmit Interval\|(% style="background-color:#f2f2f2" %)(((
6.2	1063	30000
	1064	OK
	1065	the interval is 30000ms = 30s
	1066	)))
53.8	1067	\|(% style="background-color:#f2f2f2; width:157px" %)AT+TDC=60000\|(% style="background-color:#f2f2f2; width:166px" %)Set Transmit Interval\|(% style="background-color:#f2f2f2" %)(((
6.2	1068	OK
	1069	Set transmit interval to 60000ms = 60 seconds
	1070	)))
	1071
123.2	1072	Downlink Command: 0x01
6.2	1073
	1074	Format: Command Code (0x01) followed by 3 bytes time value.
	1075
43.2	1076	If the downlink payload=0100003C, it means set the END Node's Transmit Interval to 0x00003C=60(S), while type code is 01.
6.2	1077
43.2	1078	* Example 1: Downlink Payload: 0100001E ~/~/ Set Transmit Interval (TDC) = 30 seconds
	1079	* Example 2: Downlink Payload: 0100003C ~/~/ Set Transmit Interval (TDC) = 60 seconds
6.2	1080
53.1	1081	=== 3.3.2 Set Interrupt Mode ===
52.2	1082
6.2	1083
	1084	Feature, Set Interrupt mode for GPIO_EXIT.
	1085
123.2	1086	AT Command: AT+INTMOD
6.2	1087
123.15	1088	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
123.2	1089	\|=(% style="width: 154px;background-color:#4F81BD;color:white" %)Command Example\|=(% style="width: 196px;background-color:#4F81BD;color:white" %)Function\|=(% style="width: 160px;background-color:#4F81BD;color:white" %)Response
53.9	1090	\|(% style="background-color:#f2f2f2; width:154px" %)AT+INTMOD=?\|(% style="background-color:#f2f2f2; width:196px" %)Show current interrupt mode\|(% style="background-color:#f2f2f2; width:157px" %)(((
6.2	1091	0
	1092	OK
47.1	1093	the mode is 0 =Disable Interrupt
6.2	1094	)))
53.9	1095	\|(% style="background-color:#f2f2f2; width:154px" %)AT+INTMOD=2\|(% style="background-color:#f2f2f2; width:196px" %)(((
6.2	1096	Set Transmit Interval
47.1	1097	0. (Disable Interrupt),
	1098	~1. (Trigger by rising and falling edge)
	1099	2. (Trigger by falling edge)
	1100	3. (Trigger by rising edge)
53.9	1101	)))\|(% style="background-color:#f2f2f2; width:157px" %)OK
6.2	1102
123.2	1103	Downlink Command: 0x06
6.2	1104
	1105	Format: Command Code (0x06) followed by 3 bytes.
	1106
	1107	This means that the interrupt mode of the end node is set to 0x000003=3 (rising edge trigger), and the type code is 06.
	1108
43.2	1109	* Example 1: Downlink Payload: 06000000 ~/~/ Turn off interrupt mode
	1110	* Example 2: Downlink Payload: 06000003 ~/~/ Set the interrupt mode to rising edge trigger
6.2	1111
53.1	1112	=== 3.3.3 Set the output time ===
52.2	1113
37.5	1114
6.2	1115	Feature, Control the output 3V3 , 5V or 12V.
	1116
123.2	1117	AT Command: AT+3V3T
6.2	1118
123.16	1119	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:474px" %)
123.2	1120	\|=(% style="width: 154px;background-color:#4F81BD;color:white" %)Command Example\|=(% style="width: 201px;background-color:#4F81BD;color:white" %)Function\|=(% style="width: 119px;background-color:#4F81BD;color:white" %)Response
53.10	1121	\|(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=?\|(% style="background-color:#f2f2f2; width:201px" %)Show 3V3 open time.\|(% style="background-color:#f2f2f2; width:116px" %)(((
6.2	1122	0
	1123	OK
	1124	)))
53.10	1125	\|(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=0\|(% style="background-color:#f2f2f2; width:201px" %)Normally open 3V3 power supply.\|(% style="background-color:#f2f2f2; width:116px" %)(((
6.2	1126	OK
	1127	default setting
	1128	)))
53.10	1129	\|(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=1000\|(% style="background-color:#f2f2f2; width:201px" %)Close after a delay of 1000 milliseconds.\|(% style="background-color:#f2f2f2; width:116px" %)(((
6.2	1130	OK
	1131	)))
53.10	1132	\|(% style="background-color:#f2f2f2; width:154px" %)AT+3V3T=65535\|(% style="background-color:#f2f2f2; width:201px" %)Normally closed 3V3 power supply.\|(% style="background-color:#f2f2f2; width:116px" %)(((
6.2	1133	OK
	1134	)))
	1135
123.2	1136	AT Command: AT+5VT
6.2	1137
123.16	1138	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:470px" %)
123.2	1139	\|=(% style="width: 155px;background-color:#4F81BD;color:white" %)Command Example\|=(% style="width: 196px;background-color:#4F81BD;color:white" %)Function\|=(% style="width: 119px;background-color:#4F81BD;color:white" %)Response
53.10	1140	\|(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=?\|(% style="background-color:#f2f2f2; width:196px" %)Show 5V open time.\|(% style="background-color:#f2f2f2; width:114px" %)(((
6.2	1141	0
	1142	OK
	1143	)))
53.10	1144	\|(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=0\|(% style="background-color:#f2f2f2; width:196px" %)Normally closed 5V power supply.\|(% style="background-color:#f2f2f2; width:114px" %)(((
6.2	1145	OK
	1146	default setting
	1147	)))
53.10	1148	\|(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=1000\|(% style="background-color:#f2f2f2; width:196px" %)Close after a delay of 1000 milliseconds.\|(% style="background-color:#f2f2f2; width:114px" %)(((
6.2	1149	OK
	1150	)))
53.10	1151	\|(% style="background-color:#f2f2f2; width:155px" %)AT+5VT=65535\|(% style="background-color:#f2f2f2; width:196px" %)Normally open 5V power supply.\|(% style="background-color:#f2f2f2; width:114px" %)(((
6.2	1152	OK
	1153	)))
	1154
123.2	1155	AT Command: AT+12VT
6.2	1156
123.16	1157	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:443px" %)
123.2	1158	\|=(% style="width: 156px;background-color:#4F81BD;color:white" %)Command Example\|=(% style="width: 199px;background-color:#4F81BD;color:white" %)Function\|=(% style="width: 88px;background-color:#4F81BD;color:white" %)Response
53.10	1159	\|(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=?\|(% style="background-color:#f2f2f2; width:199px" %)Show 12V open time.\|(% style="background-color:#f2f2f2; width:83px" %)(((
6.2	1160	0
	1161	OK
	1162	)))
53.10	1163	\|(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=0\|(% style="background-color:#f2f2f2; width:199px" %)Normally closed 12V power supply.\|(% style="background-color:#f2f2f2; width:83px" %)OK
	1164	\|(% style="background-color:#f2f2f2; width:156px" %)AT+12VT=500\|(% style="background-color:#f2f2f2; width:199px" %)Close after a delay of 500 milliseconds.\|(% style="background-color:#f2f2f2; width:83px" %)(((
6.2	1165	OK
	1166	)))
	1167
123.2	1168	Downlink Command: 0x07
6.2	1169
	1170	Format: Command Code (0x07) followed by 3 bytes.
	1171
	1172	The first byte is which power, the second and third bytes are the time to turn on.
	1173
123.2	1174	* Example 1: Downlink Payload: 070101F4 ~-~--> AT+3V3T=500
	1175	* Example 2: Downlink Payload: 0701FFFF ~-~--> AT+3V3T=65535
	1176	* Example 3: Downlink Payload: 070203E8 ~-~--> AT+5VT=1000
	1177	* Example 4: Downlink Payload: 07020000 ~-~--> AT+5VT=0
	1178	* Example 5: Downlink Payload: 070301F4 ~-~--> AT+12VT=500
	1179	* Example 6: Downlink Payload: 07030000 ~-~--> AT+12VT=0
6.2	1180
123.2	1181	Note: Before v1.2, the maximum settable time of 3V3T, 5VT and 12VT is 65535 milliseconds. After v1.2, the maximum settable time of 3V3T, 5VT and 12VT is 180 seconds.
101.1	1182
123.2	1183	Therefore, the corresponding downlink command is increased by one byte to five bytes.
101.1	1184
123.2	1185	Example:
101.1	1186
123.2	1187	* 120s=120000ms(D) =0x01D4C0(H), Downlink Payload: 07 01 01 D4 C0 ~-~--> AT+3V3T=120000
	1188	* 100s=100000ms(D) =0x0186A0(H), Downlink Payload: 07 02 01 86 A0 ~-~--> AT+5VT=100000
	1189	* 80s=80000ms(D) =0x013880(H), Downlink Payload: 07 03 01 38 80 ~-~--> AT+12VT=80000
101.1	1190
53.1	1191	=== 3.3.4 Set the Probe Model ===
52.2	1192
37.5	1193
47.1	1194	Users need to configure this parameter according to the type of external probe. In this way, the server can decode according to this value, and convert the current value output by the sensor into water depth or pressure value.
6.2	1195
123.2	1196	AT Command: AT +PROBE
47.1	1197
	1198	AT+PROBE=aabb
	1199
	1200	When aa=00, it is the water depth mode, and the current is converted into the water depth value; bb is the probe at a depth of several meters.
	1201
	1202	When aa=01, it is the pressure mode, which converts the current into a pressure value;
	1203
	1204	bb represents which type of pressure sensor it is.
	1205
	1206	(A->01,B->02,C->03,D->04,E->05,F->06,G->07,H->08,I->09,J->0A,K->0B,L->0C)
	1207
96.1	1208	When aa=02, it is the Differential Pressure Sensor , which converts the current into a pressure value;
	1209
	1210	bb represents which type of pressure sensor it is.
	1211
	1212	(0~~100Pa->01,0~~200Pa->02,0~~300Pa->03,0~~1KPa->04,0~~2KPa->05,0~~3KPa->06,0~~4KPa->07,0~~5KPa->08,0~~10KPa->09,-100~~ 100Pa->0A,-200~~ 200Pa->0B,-1~~ 1KPa->0C)
	1213
53.28	1214	(% border="1" cellspacing="4" style="background-color:#f2f2f2; width:510px" %)
148.2	1215	\|(% style="background-color:#4f81bd; color:white; width:154px" %)Command Example\|(% style="background-color:#4f81bd; color:white; width:269px" %)Function\|(% style="background-color:#4f81bd; color:white" %)Response
61.1	1216	\|(% style="background-color:#f2f2f2; width:154px" %)AT+PROBE=?\|(% style="background-color:#f2f2f2; width:269px" %)Get or Set the probe model.\|(% style="background-color:#f2f2f2" %)0
6.2	1217	OK
61.1	1218	\|(% style="background-color:#f2f2f2; width:154px" %)AT+PROBE=0003\|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 3m type.\|(% style="background-color:#f2f2f2" %)OK
53.12	1219	\|(% style="background-color:#f2f2f2; width:154px" %)(((
61.1	1220	AT+PROBE=000A
53.12	1221	)))\|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 10m type.\|(% style="background-color:#f2f2f2" %)OK
62.1	1222	\|(% style="background-color:#f2f2f2; width:154px" %)AT+PROBE=0064\|(% style="background-color:#f2f2f2; width:269px" %)Set water depth sensor mode, 100m type.\|(% style="background-color:#f2f2f2" %)OK
61.1	1223	\|(% style="background-color:#f2f2f2; width:154px" %)AT+PROBE=0101\|(% style="background-color:#f2f2f2; width:269px" %)Set pressure transmitters mode, first type(A).\|(% style="background-color:#f2f2f2" %)OK
	1224	\|(% style="background-color:#f2f2f2; width:154px" %)AT+PROBE=0000\|(% style="background-color:#f2f2f2; width:269px" %)Initial state, no settings.\|(% style="background-color:#f2f2f2" %)OK
6.2	1225
123.2	1226	Downlink Command: 0x08
47.1	1227
6.2	1228	Format: Command Code (0x08) followed by 2 bytes.
	1229
123.2	1230	* Example 1: Downlink Payload: 080003 ~-~--> AT+PROBE=0003
	1231	* Example 2: Downlink Payload: 080101 ~-~--> AT+PROBE=0101
6.2	1232
75.2	1233	=== 3.3.5 Multiple collections are one uplink (Since firmware V1.1) ===
52.2	1234
43.3	1235
94.1	1236	Added AT+STDC command to collect the voltage of VDC_INPUT/IDC_INPUT multiple times and upload it at one time.
45.1	1237
123.2	1238	AT Command: AT +STDC
45.1	1239
138.1	1240	AT+STDC=aa,bb,cc
47.1	1241
123.2	1242	aa:
	1243	0: means disable this function and use TDC to send packets.
	1244	1: means that the function is enabled to send packets by collecting VDC data for multiple times.
	1245	2: means that the function is enabled to send packets by collecting IDC data for multiple times.
	1246	bb: Each collection interval (s), the value is 1~~65535
	1247	cc: the number of collection times, the value is 1~~120
47.1	1248
123.16	1249	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
148.2	1250	\|(% style="background-color:#4f81bd; color:white; width:160px" %)Command Example\|(% style="background-color:#4f81bd; color:white; width:215px" %)Function\|(% style="background-color:#4f81bd; color:white" %)Response
53.13	1251	\|(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=?\|(% style="background-color:#f2f2f2; width:215px" %)Get the mode of multiple acquisitions and one uplink.\|(% style="background-color:#f2f2f2" %)1,10,18
45.1	1252	OK
53.13	1253	\|(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=1,10,18\|(% style="background-color:#f2f2f2; width:215px" %)Set the mode of multiple acquisitions and one uplink, collect once every 10 seconds, and report after 18 times.\|(% style="background-color:#f2f2f2" %)(((
47.1	1254	Attention:Take effect after ATZ
	1255	OK
45.1	1256	)))
53.13	1257	\|(% style="background-color:#f2f2f2; width:160px" %)AT+STDC=0, 0,0\|(% style="background-color:#f2f2f2; width:215px" %)(((
123.2	1258
	1259
47.1	1260	Use the TDC interval to send packets.(default)
	1261
	1262
53.13	1263	)))\|(% style="background-color:#f2f2f2" %)(((
47.1	1264	Attention:Take effect after ATZ
45.1	1265	OK
	1266	)))
	1267
123.2	1268	Downlink Command: 0xAE
45.1	1269
94.1	1270	Format: Command Code (0xAE) followed by 4 bytes.
45.1	1271
123.2	1272	* Example 1: Downlink Payload: AE 01 02 58 12 ~-~--> AT+STDC=1,600,18
45.1	1273
137.1	1274	== 3.4 Print data entries base on page(Since v1.1.0) ==
	1275
	1276
	1277	Feature: Print the sector data from start page to stop page (max is 416 pages).
	1278
	1279	(% style="color:#4f81bd" %)AT Command: AT+PDTA
	1280
	1281	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
	1282	\|(% style="background-color:#4f81bd; color:white; width:158px" %)Command Example\|(% style="background-color:#4f81bd; color:white; width:352px" %)Function
	1283	\|(% style="width:156px" %)(((
	1284	AT+PDTA=1,1
	1285	Print page 1 to 1
	1286	)))\|(% style="width:311px" %)(((
	1287	Stop Tx events when read sensor data
	1288
	1289	8031000 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1290
	1291	8031010 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1292
	1293	8031020 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1294
	1295	8031030 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1296
	1297	8031040 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1298
	1299	8031050 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1300
	1301	8031060 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1302
	1303	8031070 1970/1/1 00:00:00 0 in1:low in2:low exti:low status:false vdc:0.000 idc:0.000 proble:0000 water_deep:0.000
	1304
	1305	Start Tx events
	1306
	1307
	1308	OK
	1309	)))
	1310
	1311	(% style="color:#4f81bd" %)Downlink Command:
	1312
	1313	No downlink commands for feature
	1314
	1315
	1316	== 3.5 Print last few data entries(Since v1.1.0) ==
	1317
	1318
	1319	Feature: Print the last few data entries
	1320
	1321
	1322	(% style="color:#4f81bd" %)AT Command: AT+PLDTA
	1323
	1324	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:510px" %)
	1325	\|(% style="background-color:#4f81bd; color:white; width:158px" %)Command Example\|(% style="background-color:#4f81bd; color:white; width:352px" %)Function
	1326	\|(% style="width:156px" %)(((
	1327	AT+PLDTA=10
	1328	Print last 10 entries
	1329	)))\|(% style="width:311px" %)(((
	1330	Stop Tx events when read sensor data
	1331
	1332	0001 2025/5/19 06:16:50 3246 in1:low in2:low exti:low status:false vdc:3.352 idc:0.000 proble:0000 water_deep:0.000
	1333
	1334	0002 2025/5/19 06:17:50 3246 in1:low in2:low exti:low status:false vdc:3.352 idc:0.000 proble:0000 water_deep:0.000
	1335
	1336	0003 2025/5/19 06:18:50 3246 in1:low in2:low exti:low status:false vdc:3.352 idc:0.000 proble:0000 water_deep:0.000
	1337
	1338	0004 2025/5/19 06:19:50 3246 in1:low in2:low exti:low status:false vdc:3.352 idc:0.000 proble:0000 water_deep:0.000
	1339
	1340	0005 2025/5/19 06:20:50 3246 in1:low in2:low exti:low status:false vdc:3.352 idc:0.000 proble:0000 water_deep:0.000
	1341
	1342	0006 2025/5/19 06:21:50 3246 in1:low in2:low exti:low status:false vdc:3.351 idc:0.000 proble:0000 water_deep:0.000
	1343
	1344	0007 2025/5/19 06:22:50 3240 in1:low in2:low exti:low status:false vdc:3.351 idc:0.000 proble:0000 water_deep:0.000
	1345
	1346	0008 2025/5/19 06:26:44 3276 in1:low in2:low exti:low status:false vdc:3.385 idc:0.000 proble:0000 water_deep:0.000
	1347
	1348	0009 2025/5/19 06:27:36 3246 in1:low in2:low exti:low status:false vdc:3.351 idc:0.000 proble:0000 water_deep:0.000
	1349
	1350	0010 2025/5/19 06:28:36 3240 in1:low in2:low exti:low status:false vdc:3.351 idc:0.000 proble:0000 water_deep:0.000
	1351
	1352	Start Tx events
	1353
	1354	OK
	1355	)))
	1356
	1357	(% style="color:#4f81bd" %)Downlink Command:
	1358
	1359	No downlink commands for feature
	1360
	1361
	1362	== 3.6 Clear Flash Record(Since v1.1.0) ==
	1363
	1364
	1365	Feature: Clear flash storage for data log feature.
	1366
	1367	(% style="color:#4f81bd" %)AT Command: AT+CLRDTA
	1368
	1369	(% border="1" cellspacing="3" style="background-color:#f2f2f2; width:503px" %)
	1370	\|(% style="background-color:#4f81bd; color:white; width:157px" %)Command Example\|(% style="background-color:#4f81bd; color:white; width:137px" %)Function\|(% style="background-color:#4f81bd; color:white; width:209px" %)Response
	1371	\|(% style="width:155px" %)AT+CLRDTA \|(% style="width:134px" %)Clear date record\|(% style="width:209px" %)(((
	1372	Clear all stored sensor data…
	1373
148.2	1374	OK
137.1	1375	)))
	1376
	1377	(% style="color:#4f81bd" %)Downlink Command: 0xA3
	1378
	1379	* Example: 0xA301 ~/~/ Same as AT+CLRDTA
	1380
53.1	1381	= 4. Battery & Power Consumption =
52.2	1382
53.13	1383
72.3	1384	PS-LB use ER26500 + SPC1520 battery pack and PS-LS use 3000mAh Recharable Battery with Solar Panel. See below link for detail information about the battery info and how to replace.
6.2	1385
123.2	1386	[[Battery Info & Power Consumption Analyze>>url:http://wiki.dragino.com/xwiki/bin/view/Main/How%20to%20calculate%20the%20battery%20life%20of%20Dragino%20sensors%3F/]] .
37.6	1387
	1388
53.1	1389	= 5. OTA firmware update =
6.2	1390
	1391
42.2	1392	Please see this link for how to do OTA firmware update: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/>>url:http://wiki.dragino.com/xwiki/bin/view/Main/Firmware%20OTA%20Update%20for%20Sensors/]]
6.2	1393
	1394
53.1	1395	= 6. FAQ =
6.2	1396
53.1	1397	== 6.1 How to use AT Command via UART to access device? ==
6.2	1398
	1399
42.2	1400	See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]
6.2	1401
	1402
53.1	1403	== 6.2 How to update firmware via UART port? ==
6.2	1404
	1405
42.2	1406	See: [[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware>>url:http://wiki.dragino.com/xwiki/bin/view/Main/UART%20Access%20for%20LoRa%20ST%20v4%20base%20model/#H1.LoRaSTv4baseHardware]]
6.2	1407
	1408
53.1	1409	== 6.3 How to change the LoRa Frequency Bands/Region? ==
6.2	1410
	1411
42.3	1412	You can follow the instructions for [[how to upgrade image>>doc:Main.Firmware Upgrade Instruction for STM32 base products.WebHome]].
6.2	1413	When downloading the images, choose the required image file for download.
	1414
	1415
76.2	1416	== 6.4 How to measure the depth of other liquids other than water? ==
76.1	1417
	1418
76.2	1419	Test the current values at the depth of different liquids and convert them to a linear scale.
	1420	Replace its ratio with the ratio of water to current in the decoder.
76.1	1421
123.2	1422	Example:
76.1	1423
78.1	1424	Measure the corresponding current of the sensor when the liquid depth is 2.04m and 0.51m.
	1425
123.18	1426	Calculate scale factor:
78.1	1427	Use these two data to calculate the current and depth scaling factors：(7.888-5.035)/(2.04-0.51)=1.86470588235294
	1428
123.18	1429	Calculation formula:
78.1	1430
	1431	Use the calibration formula：(Current current - Minimum calibration current)/Scale factor + Minimum actual calibration height
	1432
123.18	1433	Actual calculations:
78.1	1434
	1435	Use this formula to calculate the value corresponding to the current at a depth of 1.5 meters: (6.918-5.035)/1.86470588235294+0.51=1.519810726
	1436
123.18	1437	Error:
78.1	1438
	1439	0.009810726
	1440
	1441
	1442	[[image:image-20240329175044-1.png]]
	1443
125.4	1444
142.1	1445	== 6.5 Cable & Probe Material Compatibility(Immersion type) ==
	1446
	1447
	1448	Since the installation method of immersion sensors requires immersion in a liquid environment, the discussion of liquids that can be safely installed is very important.
	1449
	1450	(% style="color:blue" %)The material of the immersed part of the immersion sensor:
	1451
	1452	* Cable Jacket: Black polyurethane (PU) – Resistant to water, oils, and mild chemicals.
	1453	* Probe Material: 316 stainless steel – Corrosion-resistant in most industrial/marine environments.
	1454
	1455	(% style="color:blue" %)Chemical Compatibility:
	1456
	1457	* Polyurethane (PU) Cable: Resists water, oils, fuels, and mild chemicals but may degrade with prolonged exposure to strong acids, bases, or solvents (e.g., acetone, chlorinated hydrocarbons).
	1458	* 316 Stainless Steel Probe: Suitable for water, seawater, mild acids/alkalis, and industrial fluids. Avoid highly concentrated acids (e.g., hydrochloric acid) or chlorides at high temperatures.
	1459
	1460	Chemical Resistance Chart for Polyurethane (PU) Cable
	1461
	1462	[[image:image-20250603171424-1.png\|\|height="429" width="625"]]
	1463
	1464	Chemical Resistance Chart for 316 Stainless Steel Probe
	1465
	1466	[[image:image-20250603171503-2.png\|\|height="350" width="616"]]
	1467
	1468
62.3	1469	= 7. Troubleshooting =
6.2	1470
62.3	1471	== 7.1 Water Depth Always shows 0 in payload ==
6.2	1472
	1473
56.1	1474	If your device's IDC_intput_mA is normal, but your reading always shows 0, please refer to the following points:
	1475
55.1	1476	~1. Please set it to mod1
62.3	1477
55.1	1478	2. Please set the command [[AT+PROBE>>http://wiki.dragino.com/xwiki/bin/view/Main/User%20Manual%20for%20LoRaWAN%20End%20Nodes/PS-LB%20--%20LoRaWAN%20Pressure%20Sensor/#H3.3.4SettheProbeModel]] according to the model of your sensor
62.3	1479
55.1	1480	3. Check the connection status of the sensor
6.2	1481
56.2	1482
62.3	1483	= 8. Order Info =
	1484
125.2	1485	== 8.1 Thread Installation Type & Immersion Type Pressure Sensor ==
62.3	1486
	1487
148.1	1488	Part Number: (% style="color:blue" %)PS-LB/LS-Txx-YY or PS-LB/LS-Ixx-YY
125.2	1489
125.4	1490	(% style="color:blue" %)XX:(%%) Pressure Range and Thread Type
125.2	1491
125.4	1492	(% style="color:blue" %)YY:(%%) The default frequency band
125.2	1493
	1494	* YY: Frequency Bands, options: EU433,CN470,EU868,IN865,KR920,AS923,AU915,US915
	1495
99.2	1496	[[image:image-20241021093209-1.png]]
62.3	1497
125.2	1498
	1499	== 8.2 Wireless Differential Air Pressure Sensor ==
	1500
	1501
125.4	1502	Part Number: (% style="color:blue" %)PS-LB-Dxx-YY or PS-LS-Dxx-YY
125.2	1503
125.4	1504	(% style="color:blue" %)XX:(%%) Differential Pressure Range
125.2	1505
125.4	1506	(% style="color:blue" %)YY:(%%) The default frequency band
125.2	1507
	1508	* YY: Frequency Bands, options: EU433,CN470,EU868,IN865,KR920,AS923,AU915,US915
	1509
	1510	[[image:image-20250401174215-1.png\|\|height="486" width="656"]]
	1511
	1512
55.1	1513	= 9. Packing Info =
	1514
	1515
123.2	1516	Package Includes:
6.2	1517
125.5	1518	* PS-LB/LS-Txx/Ixx, PS-LB/LS-Dxx LoRaWAN Pressure Sensor
6.2	1519
123.2	1520	Dimension and weight:
6.2	1521
	1522	* Device Size: cm
	1523	* Device Weight: g
	1524	* Package Size / pcs : cm
	1525	* Weight / pcs : g
	1526
55.1	1527	= 10. Support =
54.3	1528
52.2	1529
6.2	1530	* 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.
42.20	1531
54.3	1532	* 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.cc>>mailto:Support@dragino.cc]].

Wiki source code of PS-LB/LS -- LoRaWAN Air Water Pressure Sensor User Manual

Applications

Navigation