#electrical-engineering

Cable voltage-drop and conductor-sizing maths as an API, computed locally and deterministically. The drop endpoint computes the voltage lost along a cable run from the current, the one-way run length, the conductor cross-section and the material: the conductor resistance R = ρ·L/A, the voltage drop Vd = k·I·R (k = 2 for single-phase, √3 for three-phase), the drop as a percentage of the supply and the voltage left at the load. The sizing endpoint works backwards: from an allowable percentage drop it returns the minimum conductor cross-section needed, A ≥ k·I·ρ·L/Vd_allow, rounds up to the next standard cable size (1.5, 2.5, 4, 6, 10, 16, 25 … mm²) and reports the actual drop at that size. The power endpoint computes the power dissipated as heat in the cable, P = N·I²·R (N = 2 or 3 current-carrying conductors), and the cable efficiency given a load power. Copper (ρ = 0.0172) and aluminium (ρ = 0.0282 Ω·mm²/m) are supported. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical-installation and panel-design tools, cable selection to wiring-regulation limits, solar, EV-charger and sub-main sizing, and electrical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is cable voltage drop and sizing; for Ohm's law, reactance and resonance use an Ohm's-law API and for transformer ratios use a transformer API.

api.oanor.com/voltagedrop-api

AC power triangle and power-factor maths as an API, computed locally and deterministically. The power-factor endpoint solves the power triangle: from any two of the apparent power S (volt-amperes), the real power P (watts), the reactive power Q (VAR), the power factor (cos φ) or the phase angle it returns all of them, using S = √(P²+Q²), P = S·cosφ, Q = S·sinφ and PF = P/S. The load endpoint computes the powers of a load directly from its voltage, current and power factor — single-phase S = V·I or three-phase S = √3·V·I from line values. The correction endpoint sizes power-factor correction: the reactive power a capacitor must supply to raise the power factor from a present value to a target, Qc = P·(tanφ1 − tanφ2), and — given the supply voltage and frequency — the capacitance, C = Qc/(2π·f·V²), the basis of cutting reactive demand and utility penalties. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical-engineering and power-systems tools, motor, industrial and HVAC load analysis, energy-billing and power-quality apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is AC power and power-factor correction; for Ohm's law, reactance and resonance use an Ohm's-law API.

api.oanor.com/powerfactor-api

Ideal-transformer relations as an API, computed locally and deterministically. The transformer endpoint works from the turns ratio a = Np/Ns = Vp/Vs = Is/Ip: give any ratio-defining pair — the primary and secondary turns, voltages or currents — and it derives the rest, classifies the transformer as step-up, step-down or 1:1 isolation, and reports the primary and secondary apparent power (which are equal for an ideal transformer, so a step-down in voltage is a step-up in current). The power endpoint applies the power balance with an efficiency, Ps = η·Pp, from the primary or secondary power (given directly or as voltage times current) and reports the power loss. The impedance endpoint reflects an impedance across the transformer, Zp/Zs = (Np/Ns)² = a² — the basis of impedance matching, so an 8 Ω speaker on a 10:1 transformer looks like 800 Ω to the source. Everything is computed locally and deterministically, so it is instant and private. Ideal for electrical and electronics-engineering tools, power-supply and audio-amplifier design, impedance-matching and EE-education apps. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is ideal-transformer ratios; for Ohm's law, reactance and series/parallel components use an Ohm's-law API.

api.oanor.com/transformer-api

Coulomb's-law electrostatics as an API, computed locally and deterministically. The force endpoint computes the electrostatic force between two point charges, F = k·q1·q2/(εr·r²) — Coulomb's law, with k = 8.9876×10⁹ N·m²/C² — from the two charges, their separation and an optional relative permittivity for a dielectric medium, and tells you whether the force is attractive (opposite signs) or repulsive (like signs). The field endpoint gives the electric field of a point charge, E = k·q/(εr·r²), its direction (away from a positive charge, toward a negative one), and the force on a test charge placed there, F = q_test·E. The potential endpoint gives the electric potential V = k·q/(εr·r) and, for a pair of charges, the electrostatic potential energy U = k·q1·q2/(εr·r) in joules and electron-volts. Charges may be entered in coulombs, microcoulombs or nanocoulombs. Everything is computed locally and deterministically, so it is instant and private. Ideal for physics and electrical-engineering education tools, electrostatics and field-theory apps, and laboratory and simulation software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is electrostatics; for Ohm's law and DC/AC circuits use an Ohm's-law API.

api.oanor.com/coulomb-api