PID form conversion
API · /pid-api
PID Tuning API
PID-controller-tuning maths as an API, computed locally and deterministically. The ziegler-nichols endpoint computes controller gains with the closed-loop (ultimate-gain) method: from the ultimate gain Ku at which the loop sustains oscillation and its period Tu it returns the proportional, integral and derivative gains for a P, PI, PD or PID controller using the classic table (PID: Kp = 0.6·Ku, Ti = 0.5·Tu, Td = 0.125·Tu), in both the standard (Ti, Td) and parallel (Ki, Kd) parameters. The reaction-curve endpoint computes gains with the open-loop method from a step-response process model — the process gain K, the dead time L and the time constant T — using the Ziegler-Nichols reaction-curve table (PID: Kp = 1.2·T/(K·L), Ti = 2L, Td = 0.5L). The convert endpoint translates between the parallel form (Kp, Ki, Kd) and the standard form (Kp, Ti, Td) using Ki = Kp/Ti and Kd = Kp·Td. Everything is computed locally and deterministically, so it is instant and private. Ideal for industrial-automation, robotics, process-control, motor-control and IoT app developers, controller-tuning and loop-design tools, and control-systems education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is PID controller tuning; for op-amp circuits use an op-amp API and for resonance and reactance a resonance API.
API health
healthy- Uptime
- 100.00%
- Server probes · 24h
- Avg latency
- 84 ms
- Server probes · 24h
- Subscribers
- 4,305
- active
- Total calls
- 28
- last 7 days
Pricing
Pick a tier — billed monthly, cancel anytime.
Free
Free
- 2,850 calls / month
- 2 requests / second
- Hard cap (429 above quota, no overage)
- 2,850 calls/month
- 2 req/sec
- Closed-loop + reaction curve + convert
- No credit card
Starter
€10.00 /month
- 41,000 calls / month
- 6 requests / second
- Hard cap (429 above quota, no overage)
- 41,000 calls/month
- 6 req/sec
- P/PI/PD/PID, parallel & standard forms
- Email support
Pro
€25.00 /month
- 249,000 calls / month
- 15 requests / second
- Hard cap (429 above quota, no overage)
- 249,000 calls/month
- 15 req/sec
- Automation & robotics pipelines
- Priority support
Mega
€72.00 /month
- 1,730,000 calls / month
- 40 requests / second
- Hard cap (429 above quota, no overage)
- 1,730,000 calls/month
- 40 req/sec
- Platform scale
- Dedicated SLA
Built by
Related APIs
Other APIs with overlapping tags.
Suspension Tuning API
Vehicle-suspension maths as an API, computed locally and deterministically — the spring and frequency numbers a racer, tuner or chassis engineer sets a car up with. The wheel-rate endpoint converts a spring rate to the rate the wheel actually feels: wheel rate = spring rate × motion ratio², where the motion ratio is the spring's travel per unit of wheel travel — a 200 lb/in spring at a 0.7 motion ratio gives a 98 lb/in wheel rate, because the spring's leverage softens it. The frequency endpoint gives the ride (natural) frequency at a corner, f = (1/2π)·√(wheel rate × g ÷ corner sprung weight), the number that really sets the ride: luxury cars run about 0.5–1.2 Hz, sporty street 1.2–1.7, race cars 2 Hz and up. The spring-rate endpoint inverts it — the spring rate needed to hit a target frequency for a corner weight and motion ratio — so you can pick the frequency for the car's job and get the spring straight out. Everything is computed locally and deterministically, so it is instant and private. Ideal for motorsport and tuning apps, chassis-setup and corner-balancing tools, suspension-design calculators, and engineering study aids. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — real ride also depends on damping and tyres.
api.oanor.com/suspension-api
Drone Build API
Multirotor (drone) flight maths as an API, computed locally and deterministically — the thrust, efficiency and hover numbers an FPV builder or UAV designer dials a quadcopter in with. The thrust-weight endpoint gives the thrust-to-weight ratio, total motor thrust ÷ all-up weight: aim for at least 2:1 so the craft has authority to hold position and fight wind, with freestyle wanting 3–5:1 and heavy-lift living near 1.5:1 — four 800-gram motors on a 1,200-gram quad is a punchy 2.67:1. The disk-loading endpoint gives the rotor disk loading, weight ÷ total prop disk area, where lower is more efficient: big slow props move more air for less power, which is why endurance and cinematic rigs run large props at low disk loading. The hover-throttle endpoint gives the hover throttle, all-up weight ÷ total thrust — a good build hovers near 40–50 % leaving headroom for manoeuvres, while hovering above ~60 % means it is overweight, sluggish and runs hot. Everything is computed locally and deterministically, so it is instant and private. Ideal for FPV and drone-build apps, UAV-design and motor-selection tools, hobbyist calculators, and maker sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — bench-test motors at your voltage and prop. For battery runtime use a battery API.
api.oanor.com/drone-api
Pressure Washer API
Pressure-washer maths as an API, computed locally and deterministically — the cleaning-power, nozzle and water numbers a buyer or pro sizes and runs a machine by. The cleaning-units endpoint gives the cleaning power, PSI × GPM, with a duty class — both matter because pressure breaks the dirt loose and flow flushes it away, so a 3,000 PSI / 2.5 GPM machine (7,500 cleaning units) cleans far faster than the same pressure at 1.5 GPM. The nozzle endpoint gives the flow at a different pressure (a fixed nozzle flows with the square root of pressure) and the nozzle reaction force you feel, ≈ 0.0526 × GPM × √PSI in pounds — a few pounds on a consumer unit, enough on a big machine to need two hands. The water-usage endpoint gives the water used over a run, flow × time, in gallons and litres with an optional cost — a pressure washer actually uses far less water than a garden hose for the same cleaning. Everything is computed locally and deterministically, so it is instant and private. Ideal for pressure-washer shops and rental apps, cleaning-contractor and buying-guide tools, equipment calculators, and DIY sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. Estimates — surface and detergent matter as much as the numbers.
api.oanor.com/pressurewasher-api
Solar Thermal API
Solar-thermal (solar hot water) maths as an API, computed locally and deterministically — the collector, sizing and storage numbers a solar installer or homeowner designs a hot-water system with. The output endpoint gives the useful daily heat a collector makes: area × the daily solar energy on it × the collector efficiency (flat-plate ~40–60 %, evacuated tubes higher), so a 40 ft² collector under 1,800 BTU/ft²/day at 50 % delivers about 36,000 BTU (10.5 kWh) — a family's hot water on a good day. The area endpoint sizes the collector for a demand: area = (daily gallons × 8.34 × the temperature rise) ÷ (irradiance × efficiency), so 60 gallons raised 70 °F needs about 39 ft² — sized for an average day with a backup heater, since a 60–80 % solar fraction is the economic sweet spot. The tank endpoint sizes solar storage at about 1.5 gallons per square foot of collector, big enough to bank a sunny afternoon without stalling the collector. Everything is computed locally and deterministically, so it is instant and private. Ideal for solar-installer and renewable-energy apps, hot-water-system design tools, home-energy calculators, and sustainability sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 compute endpoints. For the local solar resource use a solar-irradiance API; for pool heating use a pool API.
api.oanor.com/solarthermal-api
Frequently asked questions
Quick answers about pricing, quotas, and integration.
How do I get an API key for PID Tuning API?
What's the rate limit for PID Tuning API?
How much does PID Tuning API cost?
Can I cancel my subscription anytime?
Is PID Tuning API GDPR-compliant?
Pick an endpoint from the list on the left to see its details and try it.
Code snippets
Sign up to get an API key, then call any path under your slug.
curl https://api.oanor.com/pid-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/pid-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/pid-api/SOME_PATH");
curl_setopt($ch, CURLOPT_RETURNTRANSFER, true);
curl_setopt($ch, CURLOPT_HTTPHEADER, ["x-oanor-key: oanor_test_..."]);
$response = curl_exec($ch);
import requests
r = requests.get(
"https://api.oanor.com/pid-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Ratings
Sign in to rate.
No reviews yet.
Discussion
Ask questions, share usage tips, get answers from the provider and other developers. Public — anyone can read.
Sign in to start a thread or reply.
Sign inNew thread
·
-
Provider answer
🔒 This thread is locked — no new replies.
-
·
- No threads yet — start the discussion.
Support
Private 1:1 support with the provider — billing questions, integration issues, account problems. Only you and the provider team can see these threads.
Sign in to open a support ticket.
Sign inOpen new ticket
Describe what you need help with. The provider team gets an email and replies on the ticket page.
-
·
Urgent - No tickets yet for this API.