How to Trigger SP+ Actions from Quicklime Using SNMP Traps
Quicklime desktop buttons give operators a convenient way to control equipment. When that equipment uses Modbus RS485 connected to a sensorProbe+ (SP+) device, the control actions are stored on the SP+. SNMP Traps provide a way to connect those actions to buttons in Quicklime.
In this tutorial, we show how to send an SNMP Trap from Quicklime, receive it with an SNMP Trap virtual sensor on an SP+, and use the sensor’s status change to trigger a saved Modbus RS485 action.
Our example uses a control valve with positions from 0% to 100%. The same approach can be adapted to other saved SP+ actions.
Watch the Video Tutorial
Follow the video below for a walkthrough of the Quicklime and SP+ configuration, then use the steps below as a reference.
How It Works
Each Quicklime button runs an SNMP Trap action containing a unique text tag, such as VALVE_10 or VALVE_20.
On the SP+, a Switch-style SNMP Trap virtual sensor listens for its matching tag. When it receives that tag, the sensor changes to High Critical. An SP+ notification rule then runs the Modbus RS485 Write action assigned to that valve position.
The sequence is:
Quicklime desktop button → SNMP Trap → SP+ virtual sensor → SP+ notification rule → Modbus RS485 Write action
This setup uses virtual sensors, so you do not need to dedicate physical dry contact ports to triggering the actions.
Before You Start
You will need:
Quicklime and an SP+ device with network connectivity between them.
The IP addresses of the Quicklime server and SP+ device.
The SP+ SNMP Write Community.
Saved Modbus RS485 Write actions on the SP+ for the required valve positions.
Sufficient available virtual sensors on the SP+.
Quicklime must be able to send SNMP Traps to the SP+ on UDP port 162. Check that network routing and firewall settings allow this traffic.
Step 1: Create an SNMP Trap Action in Quicklime
In Quicklime, go to Actions → SNMP Trap and create an action for the first valve position.
Configure the following settings:
| Setting | Value |
|---|---|
| Trap Version | v1 |
| Port | 162 |
| Destination IP | SP+ device IP address |
| Community | Match the SP+ SNMP Write Community |
| Data to include | Enable Event Class Name |
| Event Class Name | A unique tag, such as VALVE_10 |
Create a separate action for each required valve position. For example, use VALVE_20 for 20% and VALVE_100 for 100%. Include VALVE_0 if you need a fully closed position.
Assign each action to its corresponding Quicklime desktop button.
Step 2: Create the SP+ SNMP Trap Virtual Sensors
On the SP+, go to Virtual Sensors → SNMP Trap. Create one virtual sensor for each valve position.
Under the Advanced tab, configure:
| Setting | Value |
|---|---|
| Sensor Style | Switch |
| Normal State Value | 0 |
Under the Virtual Sensor Setting tab, configure:
| Setting | Value |
|---|---|
| IP Address | Quicklime server IP address |
| OID | 1.3.6.1.4.1.3854.1.7.15 |
| Trap Code | 1000 |
| Critical State String Value | The matching tag, such as VALVE_10 |
| Normal State String Value | Leave blank |
The OID identifies the Event Class Name included in the Quicklime trap. The Critical State String Value determines which tag activates that particular virtual sensor.
Why Leave the Normal String Blank?
Leaving the Normal State String Value blank allows other received strings to return the sensor to Normal.
For example, clicking the 20% button sends VALVE_20. The virtual sensor for 20% enters High Critical, while the other valve-position virtual sensors return to Normal. This prepares the previous selection to trigger again when you return to it.
Use one Switch-style virtual sensor per valve position. This provides a separate status-based trigger for each step.
Step 3: Link Each Virtual Sensor to Its Modbus Action
On the SP+, open Notifications and create a rule for each valve-position virtual sensor.
Set each rule to:
Monitor the corresponding virtual sensor.
Trigger on High Critical.
Use Continuous Time = 0 seconds.
Run the matching saved Modbus RS485 Write action.
For example, the virtual sensor matching VALVE_10 should trigger the action that sets the valve to 10%.
Repeat this for every required position.
Step 4: Test the Controls
Click a valve-position button in Quicklime and confirm that the matching SP+ virtual sensor enters High Critical and the correct Modbus action runs.
Next, select a different position. Verify that the new virtual sensor enters High Critical and the previous sensor returns to Normal. Then switch back to confirm that the earlier position can trigger again.
Because this setup relies on sensor status changes, pressing the same button again while its virtual sensor remains High Critical does not create a new status-change trigger.
The virtual sensor indicates the selected command. To confirm the valve’s actual position, monitor feedback from the valve where available.
Bring SP+ Control Actions into Your Quicklime Desktop
SNMP Trap actions and SP+ virtual sensors provide a practical way to run saved SP+ control actions from Quicklime. With a unique tag for each command and a matching notification rule, operators can select valve positions from their Quicklime desktop while the SP+ handles the Modbus RS485 communication.
- About the Author
- Latest Posts
For over two decades at AKCP, I have been focused on a single mission: bringing complete visibility, security, and efficiency to the world’s critical infrastructure.
I believe that in the modern data center, AI is only as good as the data it receives. My goal is to ensure facilities have the precise sensor facts needed to control AI opinions, ultimately reducing PUE, releasing stranded capacity, and ensuring maximum uptime.
