Smoothing-capacitor sizing
API · /rectifier-api
Rectifier Ripple API
Rectifier ripple and smoothing-capacitor maths as an API, computed locally and deterministically. The ripple endpoint computes the peak-to-peak ripple voltage left on a reservoir (smoothing) capacitor after a rectifier, Vr = I_load/(f_ripple·C), where the ripple frequency is the line frequency for a half-wave rectifier and twice it for a full-wave or bridge rectifier — and it solves for whichever of the load current, the capacitance or the ripple you leave out, also giving the RMS ripple. The capacitor endpoint sizes the smoothing capacitor for a target ripple, C = I_load/(f_ripple·Vr), and the energy it stores. The output endpoint gives the DC output of the rectifier from the transformer RMS voltage: the peak Vrms·√2, minus the diode drops in the conduction path (one for half-wave and centre-tapped, two for a bridge), the average DC voltage and, given the ripple, the ripple factor. Everything is computed locally and deterministically, so it is instant and private. Ideal for power-supply and electronics-design tools, linear PSU, charger and audio-amplifier design, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is rectifier ripple and filtering; for Ohm's law, reactance and RC time constants use an Ohm's-law API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 80 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,340
- attiva
- Chiamate totali
- 76
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 2,000 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 19,935 calls/month
- 2 req/sec
- Ripple + capacitor + output
- No credit card
Starter
€9.00 /mese
- 25,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 31.25k llamadas/mes
- 8 req/seg
- Medio/completo/puente, factor de ondulación
- Soporte por correo electrónico
Pro
€24.00 /mese
- 150,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 346.5k calls/month
- 20 req/sec
- Power-supply design pipelines
- Priority support
Mega
€74.00 /mese
- 793,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.775M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
XRP Ledger (XRPL) API
Live on-chain data from the XRP Ledger (XRPL), the decentralized blockchain behind XRP, served straight from public XRPL nodes by JSON-RPC — no key, nothing cached. The account endpoint returns any address's core state: its XRP balance, transaction sequence, the number of objects it owns, and its account flags and domain — the genesis-era account rHb9CJAWyB4rj91VRWn96DkukG4bwdtyTh holds tens of thousands of XRP. The balances endpoint returns the full wallet: the XRP balance plus every issued-currency trustline (token or stablecoin) the account holds, with the issuer, currency and amount, decoding hex currency codes to readable tickers. The transactions endpoint returns the account's most recent ledger activity — payments, DEX offers, trustline changes — each with its hash, type, amount, fee, result and time. The server endpoint returns the state of the ledger itself: the latest validated ledger index and age, the base and per-object XRP reserves, the current fee and the node software version — the network health a wallet or explorer needs. Everything is read live from the XRPL, nothing stored. This is the XRP Ledger on-chain layer for any wallet, explorer, exchange, payments or analytics app. Distinct from EVM and Solana on-chain APIs and from price feeds — this is XRPL account state, token balances, transactions and ledger health. 4 endpoints, no key on our side.
api.oanor.com/xrpl-api
Zener Regulator API
Zener-diode voltage-regulator electronics maths as an API, computed locally and deterministically. The series-resistor endpoint sizes the series (dropping) resistor for a shunt Zener regulator, Rs = (Vin − Vz)/(Iz + Il), from the input voltage, the Zener voltage, the load current and the desired Zener (knee) current, and gives the power the resistor and the Zener must dissipate — the core design step so the diode stays in regulation at maximum load. The regulator endpoint analyses an existing regulator: from the input voltage, the Zener voltage, the series resistor and the load (as a current or a resistance) it computes the total current, the Zener current Iz = (Vin − Vz)/Rs − Il, the load current, the output voltage and whether the regulator is still regulating (Iz > 0) or has dropped out under heavy load. The power endpoint computes the Zener power dissipation P = Vz·Iz and the maximum safe current Iz_max = Pz_max/Vz from the diode's power rating. Voltages are in volts, currents in amperes, resistances in ohms and power in watts. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, power-supply, hobbyist and embedded app developers, regulator-design and reference-voltage tools, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the Zener shunt regulator; for BJT biasing use a transistor API and for an LED series resistor an LED-resistor API.
api.oanor.com/zener-api
Newegg API
Live-Produktsuche von Newegg.com, dem großen Elektronik- und Technikhändler. Suchen Sie nach einem beliebigen Schlüsselwort – Laptop, rtx 4070, SSD – und erhalten Sie die Produktlisten mit Titel, Marke, Modell, aktuellem Preis, Originalpreis, Bild, Bewertung, Anzahl der Bewertungen, Lagerbestand, Verkäufer und der Newegg-Produkt-URL. Die Preise sind live in USD. Ideal für Shopping, Preisvergleiche, Angebotsverfolgung und E-Commerce-Dashboards.
api.oanor.com/newegg-api
RTD Pt100 Sensor API
RTD (Widerstands-Temperatur-Detektor) Sensor-Mathematik als API, lokal und deterministisch mit der IEC 60751 Callendar-Van Dusen Gleichung berechnet – die Widerstands-, Temperatur- und Toleranzzahlen, die ein Instrumentierungs- oder Steuerungsingenieur von einem Pt100 oder Pt1000 abliest. Der Widerstands-Endpunkt gibt den Sensorwiderstand aus der Temperatur: über 0 °C, R = R₀·(1 + A·T + B·T²) mit A = 3,9083×10⁻³ und B = −5,775×10⁻⁷; unter 0 °C fügt ein dritter Term C·(T−100)·T³ hinzu – ein Standard-Pt100 (100 Ω bei 0 °C) zeigt 138,51 Ω bei 100 °C und 80,31 Ω bei −50 °C, und ein Pt1000 ist das Zehnfache. Der Temperatur-Endpunkt kehrt dies um, um einen gemessenen Widerstand wieder in Temperatur umzuwandeln – analytisch über 0 °C, iterativ darunter – genau das, was ein Messumformer mit der Brückenablesung macht, und eine Erinnerung daran, dass eine 3- oder 4-Leiter-Verbindung den Leitungswiderstand aufhebt, sodass er nicht als zusätzliche Grad gelesen wird. Der Toleranz-Endpunkt gibt die IEC 60751 Genauigkeitsband in °C und Ω nach Klasse an – AA ±(0,10 + 0,0017·|T|), A ±(0,15 + 0,002·|T|), B ±(0,30 + 0,005·|T|), C ±(0,60 + 0,010·|T|) – der Fehler wächst mit der Entfernung von 0 °C. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Instrumentierungs- und Steuerungssoftware, Datenlogger- und Messumformer-Firmware, Kalibrierungs- und industrielle IoT-Tools. Reine lokale Berechnung – kein Key, kein Drittanbieter-Dienst, sofort. 3 Compute-Endpunkte. Für NTC-Thermistoren verwenden Sie eine Thermistor-API; für Thermoelemente eine Thermoelement-API.
api.oanor.com/rtd-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Rectifier Ripple API?
Qual è il limite di velocità di Rectifier Ripple API?
Quanto costa Rectifier Ripple API?
Posso cancellare l'abbonamento in qualsiasi momento?
Rectifier Ripple API è conforme al GDPR?
Scegli un endpoint dall'elenco a sinistra per visualizzarne i dettagli e provarlo.
Frammenti di codice
Iscriviti per ottenere una chiave API, quindi chiama qualsiasi percorso sotto il tuo slug.
curl https://api.oanor.com/rectifier-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/rectifier-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/rectifier-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/rectifier-api/SOME_PATH",
headers={"x-oanor-key": "oanor_test_..."},
)
print(r.json())
Valutazioni
Accedi per votare.
Nessuna recensione ancora.
Discussione
Fai domande, condividi consigli, ricevi risposte dal provider e dagli altri sviluppatori. Pubblico — chiunque può leggere.
Accedi per scrivere o rispondere.
AccediNuova discussione
·
-
Risposta del provider
🔒 Discussione bloccata — non si può più rispondere.
-
·
- Nessuna discussione — inizia tu.
Supporto
Supporto privato 1:1 con il provider — fatturazione, integrazione, account. Solo tu e il team del provider vedete questi thread.
Accedi per aprire un ticket di supporto.
AccediApri nuovo ticket
Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.
-
·
Urgente - Nessun ticket per questa API.