How PIDSnap works
A photograph of the trend, a photograph of the faceplate, a verdict from code, and a number to type. Nothing is written to the controller. The first session is free.
1. Photograph the trend
On the homepage, photograph the trend screen so the traces fill the frame. PIDSnap names the shape and says whether tuning can help. A settled trend, a sticking valve, or a saturated output is not a session. A hunting or sluggish loop that tuning can reach is.
2. Confirm the faceplate
If the shape is tunable, add the loop from a faceplate photograph or by typing the values. Nothing is used until you confirm it. The next instruction is computed from those confirmed numbers, in the units on that controller, not invented by the model.
3. Type the next value
Each step is one change, in the plant's own convention. Photograph the result, and the next instruction is computed from what actually happened. If the problem is mechanical, the session stops and the payment comes back.
What it does not do
- It does not connect to any DCS, historian, or plant network.
- It does not write a value to a controller.
- It does not invent a tuning number from a photograph.
- It does not ask you to drive a loop into sustained oscillation.
Photograph a trend Or run a free check
Pricing, refunds, and what happens to photographs are on pricing, refunds, and security.