Frequently asked questions
The questions that actually stop a purchase, answered plainly.
Do I have to connect it to my DCS?
No. PIDSnap has no connection to any control system, in either direction. It works from photographs of trend screens and faceplates.
Can it write values to the controller?
No. It tells you what to type. Every instruction is phrased in your controller's own convention, but nothing is written back automatically.
Which systems are supported?
The guidance is phrased for the platform you name — DeltaV, Ovation, PCS 7, Rockwell, Yokogawa, Honeywell, Foxboro, ABB and others. See the systems list for the full set.
What if the photo cannot be read?
It tells you so and asks for a clearer one. Nothing is guessed from an unreadable photo, and it costs nothing to try again.
Is the first session really free?
Yes. Sign in, add a loop, and your first tuning session costs nothing. After that a session is paid per loop or by pack.
What if the problem is not tuning?
If the trend shows stiction, backlash or a saturated output, PIDSnap says so rather than selling a session against it, and the payment is returned. See how refunds work.
Can I use it on a safety-instrumented system?
No. PIDSnap is software and has no part in your management-of-change process. Changing a loop that forms part of a verified safety function requires a management-of-change record and re-validation, none of which PIDSnap performs.
What does it do with my photographs?
They are stored as authenticated assets with signed, short-lived delivery URLs, and sent to the vision model that reads shapes out of them. The deterministic engine never receives a photograph. See security and data handling.