oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /rtd-api

RTD Pt100 Sensor API

salutare 4,661 Abbonati

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.

#rtd #pt100 #temperature-sensor #instrumentation #electronics #developer-tools
api.oanor.com/rtd-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

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

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

RTD Pt100 Sensor 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
84 ms
Sondaggi del server · 24 ore su 24
Abbonati
4,661
attiva
Chiamate totali
72
ultimi 7 giorni
status Pagina di stato completa → · 8 sonde/24h

Prezzi

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

Free

Gratis

  • 6,050 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 6.050 Aufrufe/Monat
  • 2 req/sec
  • Widerstand + Temperatur + Toleranz
  • Keine Kreditkarte
Accedi per abbonarti

Starter

€10.90 /mese

  • 61,500 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 61.500 Aufrufe/Monat
  • 6 req/sec
  • Pt100/Pt1000 & IEC 60751 Klassen
  • E-Mail-Support
Accedi per abbonarti

Pro

€34.60 /mese

  • 253,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 253.000 Aufrufe/Monat
  • 15 req/sec
  • Transmitter- & Kalibrierungspipelines
  • Prioritäts-Support
Accedi per abbonarti

Mega

€107.00 /mese

  • 1,255,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1.255.000 Aufrufe/Monat
  • 40 req/sec
  • Industrial-IoT-Skalierung
  • Dedizierte SLA
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

Thermocouple API — oanor API marketplace

Thermocouple API

Type-K thermocouple temperature/voltage conversion as an API, computed locally and deterministically from the official NIST ITS-90 reference functions. The voltage endpoint converts a junction temperature in °C to the thermo-electromotive force in millivolts using the NIST type-K direct polynomial (with its Gaussian correction term above 0 °C), and performs cold-junction compensation by subtracting the reference-junction EMF, so a hot junction at 200 °C against a 25 °C terminal block gives the EMF your meter actually reads; a type-K junction produces 4.096 mV at 100 °C and 41.276 mV at 1000 °C against a 0 °C reference. The temperature endpoint does the inverse: it takes the measured EMF in millivolts and the reference-junction temperature, refers the reading back to 0 °C by adding the cold-junction EMF, and returns the hot-junction temperature in °C and K — obtained by numerically inverting the same monotonic forward polynomial, so it is exactly consistent with the forward conversion. Type K (chromel–alumel) covers −270 to 1372 °C. Everything is computed locally and deterministically, so it is instant and private. Ideal for industrial-automation, process-control, data-acquisition, IoT-sensor, furnace and lab-instrument app developers, sensor-linearization and cold-junction-compensation tools, and embedded firmware. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 2 endpoints. This is the type-K thermocouple; for resistance-temperature detectors use an RTD/PT100 API.

api.oanor.com/thermocouple-api

 Load Cell API — oanor API marketplace

Load Cell API

Load-cell (weighing-transducer) maths as an API, computed locally and deterministically. The output endpoint computes the bridge output voltage a strain-gauge load cell produces under a given load, Vout = (load/capacity)·sensitivity·excitation, where the full-scale output FSO = sensitivity(mV/V)·excitation(V) is reached at the rated capacity — it returns the output in millivolts, the equivalent mV/V at that load and the capacity utilization, and flags overload. The load endpoint inverts this to recover the applied load from a measured bridge output, load = (Vout/FSO)·capacity. The array endpoint sizes a multi-cell weighing platform: from the number of identical cells, the per-cell capacity and the live and dead (tare) load it returns the evenly distributed per-cell load, its output and utilization and the total system capacity, so cells can be chosen to stay under capacity in the worst case. Sensitivity is in mV/V, excitation in volts (default 10), output in millivolts; load and capacity share any consistent unit. Everything is computed locally and deterministically, so it is instant and private. Ideal for industrial-weighing, scale, force-measurement, silo and process-control app developers, load-cell sizing and calibration tools, and instrumentation education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is load-cell transducer output; for the underlying Wheatstone-bridge and strain maths use a Wheatstone-bridge API.

api.oanor.com/loadcell-api

 Wheatstone Bridge API — oanor API marketplace

Wheatstone Bridge API

Wheatstone-bridge and strain-gauge maths as an API, computed locally and deterministically. The bridge endpoint takes the four arm resistances R1–R4 and an excitation voltage and returns the bridge output voltage between the two midpoints, Vout = Vin·(R2/(R1+R2) − R4/(R3+R4)), in volts and millivolts, the voltage at each midpoint, and whether the bridge is balanced (Vout = 0 when R1·R4 = R2·R3). The balance endpoint inverts it: give any three arms and it solves the fourth resistance that balances the bridge, the classic way a Wheatstone bridge measures an unknown resistance. The strain endpoint models a strain-gauge bridge — quarter, half or full — and converts in both directions between mechanical strain and electrical output: from a gauge factor and a strain (given directly, as microstrain or as a relative resistance change ΔR/R = GF·ε) it returns the output ratio and voltage Vout/Vin = (k/4)·GF·ε where k is the number of active arms, and from an output voltage and excitation it returns the strain and microstrain. Everything is computed locally and deterministically, so it is instant and private. Ideal for instrumentation and sensor tools, load-cell, pressure-sensor and RTD measurement design, strain-gauge and data-acquisition apps, and electronics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bridge and strain-gauge measurement; for Ohm's law, voltage dividers and series/parallel resistor combinations use an Ohm's-law API.

api.oanor.com/wheatstone-api

 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

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

Come ottengo una chiave API per RTD Pt100 Sensor API?
Registrati gratuitamente su oanor.com, genera una chiave API dalla dashboard sviluppatore e chiama RTD Pt100 Sensor API con l'header x-oanor-key. Nessuna carta di credito richiesta per il piano gratuito.
Qual è il limite di velocità di RTD Pt100 Sensor 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 RTD Pt100 Sensor API?
RTD Pt100 Sensor API ha un piano gratuito con 100 chiamate / mese. I piani a pagamento partono da €10.90 / 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.
RTD Pt100 Sensor API è conforme al GDPR?
Tutte le richieste a RTD Pt100 Sensor 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/rtd-api/SOME_PATH \
  -H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/rtd-api/SOME_PATH", {
  headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/rtd-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/rtd-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.