oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /zener-api

Zener Regulator API

salutare 4,754 Abbonati

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.

#zener #voltage-regulator #diode #electronics #power-supply #developer-tools
api.oanor.com/zener-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

Specifica leggibile dalle macchine, così gli agenti AI possono integrare questa API.

/api/zener-api/openapi.json
/api/zener-api/llms.txt

Individuazione: GET /api/index.json elenca ogni API.

Zener Regulator API — live data on the oanor API marketplace

API salute

salutare
Tempo di attività
100.00%
Sondaggi del server · 24 ore su 24
Latenza media
72 ms
Sondaggi del server · 24 ore su 24
Abbonati
4,754
attiva
Chiamate totali
76
ultimi 7 giorni
status Pagina di stato completa → · 12 sonde/24h

Prezzi

Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.

Free

Gratis

  • 2,720 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 2,720 calls/month
  • 2 req/sec
  • Series resistor + regulator + power
  • No credit card
Accedi per abbonarti

Starter

€8.00 /mese

  • 40,800 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 40,800 calls/month
  • 6 req/sec
  • Dropout check, dissipation, limits
  • Email support
Accedi per abbonarti

Pro

€20.00 /mese

  • 254,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 254,000 calls/month
  • 15 req/sec
  • Power-supply & reference pipelines
  • Priority support
Accedi per abbonarti

Mega

€63.00 /mese

  • 1,645,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1,645,000 llamadas/mes
  • 40 req/seg
  • Escala de plataforma
  • SLA dedicado
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

Newegg API — oanor API marketplace

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 — oanor API marketplace

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

 Voltage Divider API — oanor API marketplace

Voltage Divider API

Resistive voltage-divider circuit design as an API, computed locally and deterministically. The divide endpoint takes an input voltage and two resistors and returns the output voltage Vout = Vin·R2/(R1+R2), the current I = Vin/(R1+R2) that flows through the chain, and the power dissipated in each resistor and in total — a 12 V source with R1 = 1 kΩ and R2 = 2 kΩ gives 8 V at 4 mA. The loaded endpoint adds a load resistor across R2, computes the parallel combination R2′ = R2·RL/(R2+RL) and the loaded output Vout = Vin·R2′/(R1+R2′), and reports the droop in volts and percent against the unloaded value, the classic mistake when a divider feeds a real load. The resistor endpoint sizes the missing resistor for a target output — R2 = R1·Vout/(Vin−Vout) or R1 = R2·(Vin−Vout)/Vout — so you can pick parts for a reference or sensor-bias point. All quantities are volts, ohms, amps and watts. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, embedded, hardware, sensor-interfacing and EE-education app developers, reference-voltage and bias-network tools, and maker software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is the resistive divider; for a single Ohm’s-law relationship use an Ohm’s-law API and for RC/RL filters an RC-filter API.

api.oanor.com/voltagedivider-api

 RC Filter API — oanor API marketplace

RC Filter API

First-order RC and RL passive-filter design as an API, computed locally and deterministically. The lowpass and highpass endpoints take a resistor and capacitor (RC) or a resistor and inductor (RL) and return the −3 dB cutoff frequency (fc = 1/(2πRC) for RC, R/(2πL) for RL), the time constant (τ = RC or L/R) and the angular cutoff; pass a frequency as well and they add the magnitude response as a linear gain and in decibels and the phase shift in degrees — a 1 kΩ / 1 µF low-pass has fc ≈ 159.15 Hz, and right at the cutoff the gain is −3.01 dB with −45° phase for a low-pass or +45° for a high-pass. The component endpoint solves the missing one of fc, R and C from the other two (fc = 1/(2πRC)), so you can size a resistor or capacitor for a target cutoff. All quantities are SI: ohms, farads, henries and hertz. Everything is computed locally and deterministically, so it is instant and private. Ideal for electronics, audio, embedded, signal-processing and EE-education app developers, filter-design and circuit-sizing tools, and maker software. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is first-order single-pole filter design; for full RLC impedance and resonance use an impedance API and for stored capacitor energy a capacitor API.

api.oanor.com/rcfilter-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per Zener Regulator API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama Zener Regulator API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di Zener Regulator API?
Il piano gratuito consente 1 richiesta al secondo. I piani a pagamento arrivano fino a 50 richieste al secondo nel piano Mega. I limiti rigorosi restituiscono HTTP 429 oltre la quota — nessuna spesa imprevista.
Quanto costa Zener Regulator API?
Zener Regulator API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €8.00 / mese con quote più alte e limiti di velocità più rapidi.
Posso cancellare l'abbonamento in qualsiasi momento?
Sì. I piani sono fatturati mensilmente e puoi cancellare in qualsiasi momento dalla dashboard di fatturazione. Nessun contratto a lungo termine e nessuna penale di cancellazione.
Zener Regulator API è conforme al GDPR?
Tutte le richieste a Zener Regulator API passano attraverso il nostro gateway in UE. La tua chiave upstream non lascia mai il nostro server e nessun dato personale viene condiviso con il fornitore upstream oltre alla richiesta inviata.

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/zener-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/zener-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/zener-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/zener-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.

Accedi

Nuova discussione

/ 4000

📌 Fissato 🔒 Bloccato

·

· ·

/ 4000

🔒 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.

Accedi

Apri nuovo ticket

Descrivi cosa ti serve. Il team del provider riceve un'email e risponde sulla pagina del ticket.

  • Nessun ticket per questa API.

Abbonamento attivo: le chiamate possono iniziare subito.

Invia la tua prima richiesta —

Abbonamento attivo: copia uno snippet e avvia la tua prima chiamata.