Back

#power

2 APIs with this tag

Three-Phase Power API

Three-phase AC power maths as an API, computed locally and deterministically. The power endpoint solves the three-phase power triangle from the line-to-line voltage, the line current and the power factor — the apparent power S = √3·V_L·I_L in volt-amperes, the real power P = S·cosφ in watts, the reactive power Q = S·sinφ in VAR and the phase angle — or works backwards to find the line current a load draws for a given real power. The wye endpoint gives the star-connection relationships, where the line-to-line voltage is √3 times the phase voltage and the line and phase currents are equal. The delta endpoint gives the delta-connection relationships, where the line and phase voltages are equal and the line current is √3 times the phase current. Supply a line or phase quantity and it returns the rest. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical, motor, industrial-automation, solar-inverter and building-services app developers, switchboard and motor-sizing tools, and electrical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is balanced three-phase power; for the single-phase power triangle use a power-factor API and for voltage drop a voltage-drop API.

api.oanor.com/threephase-api

Cycling Performance API

Cycling performance maths as an API. The power endpoint estimates the power in watts needed to ride at a given speed on a given gradient, from a physical model — rolling resistance, gravity on the climb, and aerodynamic drag — with sensible defaults you can override (rolling-resistance coefficient, drag area CdA, air density, drivetrain efficiency and headwind), and breaks the power down into its rolling, gravity and aero components plus watts-per-kilogram. The ftp-zones endpoint turns a Functional Threshold Power into the seven Coggan training zones, from active recovery to neuromuscular power, as watt ranges. The vam endpoint computes VAM — vertical ascent metres per hour, the climbing-speed metric — either from elevation gained and time, or from speed and gradient. Everything is computed locally and deterministically, so it is instant and private. Ideal for cycling and training apps, bike computers and power-meter tools, coaching, and route and climb analysis. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 4 endpoints. This is cycling maths; for running pace use a pace API and for heart-rate training zones use a heart-rate API.

api.oanor.com/cycling-api