oanor
Iscriviti gratis
Mercata Prezzi Caratteristiche Accedi

API · /loadcell-api

Load Cell API

salutare 4,972 Abbonati

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.

#load-cell #weighing #force #transducer #instrumentation #developer-tools
api.oanor.com/loadcell-api
Ottieni una chiave API Prova nel parco giochi → Contatta provider

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

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

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

API salute

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

Prezzi

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

Free

Gratis

  • 2,200 chiamate/mese
  • 2 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 2,200 llamadas/mes
  • 2 req/seg
  • Salida + carga + array
  • Sin tarjeta de crédito
Accedi per abbonarti

Starter

€10.00 /mese

  • 46,000 chiamate/mese
  • 6 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 46,000 calls/month
  • 6 req/sec
  • Full-scale output, utilization, overload
  • Email support
Accedi per abbonarti

Pro

€24.00 /mese

  • 270,000 chiamate/mese
  • 15 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 270,000 calls/month
  • 15 req/sec
  • Multi-cell platform & calibration pipelines
  • Priority support
Accedi per abbonarti

Mega

€74.00 /mese

  • 1,650,000 chiamate/mese
  • 40 richieste/secondo
  • Tetto rigido (429 sopra la quota, nessuna eccedenza)
  • 1,650,000 calls/month
  • 40 req/sec
  • Platform scale
  • Dedicated SLA
Accedi per abbonarti

Costruito da

P
PremiumApi

Correlato APIs

Altro APIs con tag sovrapposti.

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

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

Sailing & Hull Design API

Sailing and naval-architecture maths as an API, computed locally and deterministically — the hull-speed and design-ratio numbers a sailor, boat-shopper or yacht designer sizes a boat with. The hullspeed endpoint gives the theoretical displacement speed limit from the waterline: hull speed = 1.34 × √LWL (feet) in knots, so a 25-foot waterline tops out around 6.7 knots (7.7 mph, 12.4 km/h) — with a tunable coefficient up to about 1.5 for light, easily-driven hulls, since planing boats leave the formula behind entirely. The ratios endpoint computes the two classic performance numbers: the Sail Area/Displacement ratio, SA/D = sail area ÷ (displaced volume in ft³)^⅔ using displaced volume = displacement ÷ 64 lb/ft³ for seawater — around 16–18 is a typical cruiser and 20-plus is sporty — and the Displacement/Length ratio, DLR = (displacement in long tons) ÷ (0.01 × LWL)³, where under 200 is light and over 300 is heavy, each returned with a class label. The ballast endpoint gives the ballast ratio = ballast ÷ displacement × 100, a rough proxy for stiffness and sail-carrying power that most cruisers hit near 35–45 %. Everything is computed locally and deterministically, so it is instant and private. Ideal for sailing, boating, marine, yacht-brokerage and boat-design app developers, boat-comparison and rig-sizing tools, and naval-architecture calculators. Pure local computation — no key, no third-party service, instant. Imperial units. Live, nothing stored. 3 compute endpoints. Design-ratio estimates, not a velocity prediction program.

api.oanor.com/sailing-api

Archery & Arrow API

Archery and arrow maths as an API, computed locally and deterministically — the FOC, energy and arrow-weight numbers an archer or bowhunter tunes a setup with. The FOC endpoint finds the front-of-center balance, the share of an arrow’s weight that sits forward of the middle: FOC = ((balance point − length ÷ 2) ÷ length) × 100 measured from the throat of the nock, so a 28-inch arrow balancing at 16 inches is 7.1 % — and it bands the result, since target archers run about 7–12 % while hunters push 12–19 % for penetration and forgiveness. The energy endpoint turns arrow weight and speed into terminal performance: kinetic energy (ft-lb) = grains × fps² ÷ 450,240 and momentum (slug-fps) = grains × fps ÷ 225,218, so a 400-grain arrow at 280 fps carries about 69.7 ft-lb and 0.50 slug-fps, with a suggested game class — momentum, not KE, is the better penetration predictor for heavy arrows. The weight endpoint totals a finished arrow from its parts — shaft (grains-per-inch × length) plus point, insert, nock and fletching — and divides by draw weight for grains-per-pound, flagging the 5-GPP minimum that protects the bow. Everything is computed locally and deterministically, so it is instant and private. Ideal for archery, bowhunting, traditional-archery and outdoor-sports app developers, arrow-builder and bow-tuning tools, and pro-shop calculators. Pure local computation — no key, no third-party service, instant. Imperial archery units. Live, nothing stored. 3 compute endpoints. For sight marks or bow tuning use a different API.

api.oanor.com/archery-api

Domande frequenti

Risposte rapide su prezzi, quote e integrazione.

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