Frequently asked
The questions that actually arrive by email, answered plainly. If yours is not here, support@flintloop.app reads everything and answers within a working day.
Is the trial crippled in any way?
No. The trial is the full program for 30 days – every connection type, every rule, the write-back. After 30 days a reminder appears on launch and nothing else changes; your work keeps opening.
Does it need internet or an account?
Neither. It runs fully offline and makes no connection except to the controller you point it at. There is no account to create and no licensing server to be down.
What does a licence actually unlock?
It removes the trial reminder and marks the build as yours, plus twelve months of updates. It adds no features, because the trial already has them all.
My key says invalid – now what?
A key is tied to the version series you bought and can expire for updates. If a current build rejects it, the update window has likely lapsed; write to support with the key and we sort it out. See the register page for the exact message.
Which controllers are supported?
Families, not brands – if yours speaks Modbus TCP/RTU, OPC UA or a plain ASCII line protocol and exposes PV, setpoint and output, it works. The controllers page lists what is read and written for each class.
It says my loop will not fit. Is that a bug?
No, it is the point. Integrating and strongly nonlinear loops do not sit under a first-order model; Flintloop refuses to fit one rather than hand you gains that oscillate. The theory pages explain which loops those are.
Can it tune a loop automatically while running?
No. It reads a step, proposes gains, and writes them on your say-so. It is not an adaptive online controller and does not pretend to be.
Do you take phone orders?
No phone. Orders and support are by email so there is one written trail – sales@ for buying, support@ for problems, usually answered within a working day.