Disc brake torque & stopping
API · /clutch-api
API de Torque de Embreagem e Freio
Torque de embreagem de fricção e freio a disco como uma API, calculado local e deterministicamente. O endpoint de embreagem calcula o torque que uma embreagem de placa (disco) pode transmitir a partir do coeficiente de atrito, da força de aperto axial e dos raios interno e externo da face de atrito, por ambas as teorias padrão — desgaste uniforme, T = n·μ·F·(Ro+Ri)/2, e pressão uniforme, T = ⅔·n·μ·F·(Ro³−Ri³)/(Ro²−Ri²) — para qualquer número de superfícies de atrito (uma embreagem multi-disco multiplica o torque), além da potência máxima em uma dada velocidade. O endpoint cônico faz o mesmo para uma embreagem cônica, T = n·μ·F·Rm/sin α, onde o ângulo de cunha amplifica a força normal por 1/sin α. O endpoint de freio fornece o torque de frenagem de um freio a disco, T = n·μ·F·R_eff, a potência dissipada em uma velocidade e — dada uma inércia rotativa e sua velocidade — a desaceleração angular, o tempo e o número de revoluções para parar, e a energia cinética convertida em calor. Tudo é calculado local e deterministicamente, portanto é instantâneo e privado. Ideal para ferramentas de trem de força, automotivas e de projeto de máquinas, engenharia de embreagens, freios e guinchos, e educação em engenharia mecânica. Cálculo puramente local — sem chave, sem serviço de terceiros, instantâneo. Ao vivo, nada armazenado. 3 endpoints. Este é o torque de embreagem e freio de fricção rotativa; para tensão de torção de eixo, use uma API de torção e para fricção de cabo/correia em tambor, use uma API de capstan.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 89 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 3,678
- attiva
- Chiamate totali
- 36
- 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,835 calls/month
- 2 req/sec
- Clutch + cone + brake
- No credit card
Starter
€9.00 /mese
- 20,000 chiamate/mese
- 5 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 31.15k calls/month
- 8 req/sec
- Multi-plate, wear & pressure, stopping
- Email support
Pro
€24.00 /mese
- 120,000 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 345.5k calls/month
- 20 req/sec
- Drivetrain / automotive pipelines
- Priority support
Mega
€74.00 /mese
- 603,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.77M llamadas/mes
- 50 req/seg
- Escala de plataforma
- SLA dedicado
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Gear Ratio API
Gear-train ratio, speed and torque maths as an API, computed locally and deterministically. The ratio endpoint computes the gear ratio of a single pair from the driver and driven tooth counts (or pitch diameters), ratio = N_driven/N_driver, classifies it as a reduction (more torque, less speed) or an overdrive, and — given an input speed and torque — returns the output speed (input/ratio) and the output torque (input·ratio·efficiency). The train endpoint computes a compound gear train: the overall ratio is the product of the individual stage ratios, and it returns each stage ratio, the output speed and torque, noting that idler gears change only the direction of rotation, not the ratio. The solve endpoint finds the missing one of the input speed, the output speed and the ratio from the other two — for example, the ratio needed to drop a 1500 rpm motor to a 500 rpm output. Everything is computed locally and deterministically, so it is instant and private. Ideal for drivetrain, robotics and machine-design tools, gearbox and transmission selection, bicycle and vehicle gearing, and mechanical-engineering education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is gear-train ratio and torque; for spur-gear tooth geometry use a spur-gear API.
api.oanor.com/gearratio-api
Shaft Torsion API
Shaft torsion as an API, computed locally and deterministically. The stress endpoint computes the maximum torsional shear stress in a circular shaft, τ = T·r/J — torque times the outer radius divided by the polar moment of inertia — for a solid shaft (J = π·d⁴/32) or a hollow tube (J = π·(D⁴−d⁴)/32), and solves the torque a shaft can carry for an allowable stress. The twist endpoint computes the angle of twist along the shaft, θ = T·L/(G·J), in radians and degrees, from the torque, length and the shear modulus (given directly or from a built-in material table — steel, aluminium, copper, titanium and more), plus the torsional stiffness G·J/L. The power endpoint relates the power a rotating shaft transmits to its torque and speed, P = T·ω = T·2πN/60, and solves any of the three, reporting power in watts, kilowatts and horsepower. Everything is computed locally and deterministically, so it is instant and private. Ideal for mechanical and drivetrain engineering tools, shaft, axle and coupling design, motor and gearbox apps, and machine-design education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is circular-shaft torsion; for axial stress-strain use a Young's-modulus API and for the 2D stress state use a Mohr-circle API.
api.oanor.com/torsion-api
Bicycle Gear API
Bicycle gearing maths as an API, computed locally and deterministically. The gear endpoint takes a chainring and cog tooth count and a wheel size and returns every common gearing metric: the gear ratio, gear inches (the classic measure — ratio times wheel diameter in inches), the gain ratio (Sheldon Brown's crank-length-aware measure), the development or rollout (metres travelled per crank revolution), and the road speed at a chosen cadence in km/h and mph. The speed endpoint converts between a gear-and-cadence and road speed in either direction — the speed at a cadence, or the cadence needed for a target speed. The table endpoint builds a gear chart: give one or more chainrings and a cassette of cogs and it returns a matrix of gear inches, development, gain ratio or ratio for every combination — ideal for visualising a drivetrain. Wheel size can be a preset (700x25c, 26-inch, 29er and more) or an exact rolling circumference in millimetres, and crank length is configurable for the gain ratio. Everything is computed locally and deterministically, so it is instant and private. Ideal for cycling apps and bike-fit tools, drivetrain and gear-ratio planners, and bike-shop and component sites. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is bicycle gearing; for cycling power, FTP and training zones use a cycling API.
api.oanor.com/bikegear-api
O-Ring Seal API
O-Ring-Dichtungs-Design-Mathematik als API, lokal und deterministisch berechnet – die Squeeze-, Gland- und Stretch-Werte, die ein Ingenieur oder Hersteller für eine Dichtung entwirft. Der Squeeze-Endpunkt liefert die Kompression, die die Dichtung bewirkt: Squeeze = (Querschnitt − Nuttiefe) ÷ Querschnitt, also wird eine 0,139-Zoll-Schnur in einer 0,113-Zoll-tiefen Nut um 18,7 % gequetscht, und bewertet das Ergebnis – etwa 10–16 % eignet sich für dynamische (hin- und hergehende) Dichtungen und 15–30 % für statische – und, bei gegebener Nutbreite, den Nutfüllgrad, der unter etwa 85 % bleiben sollte, damit der Gummi Platz zum Ausdehnen durch Hitze oder Flüssigkeitsquellung hat. Der Gland-Endpunkt arbeitet umgekehrt: Aus dem Querschnitt und ob die Dichtung statisch oder dynamisch ist (oder einem Ziel-Squeeze) gibt er die Nuttiefe und eine Breite zurück, die für etwa 70 % Füllung ausgelegt ist – typischerweise das 1,3- bis 1,5-fache des Querschnitts – plus einen Eckradius. Der Stretch-Endpunkt prüft die Installation: Stretch = (Paarungsdurchmesser − O-Ring-ID) ÷ ID, der unter etwa 5 % auf einer Stange bleiben sollte, da Dehnung den Querschnitt verringert und Squeeze stiehlt. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für App-Entwickler im Maschinenbau, Hydraulik, Pneumatik, Vakuum- und Produktdesign, Dichtungsauswahl- und Nutdesign-Tools sowie CAD-Plugins. Reine lokale Berechnung – kein Key, kein Drittanbieter-Service, sofort. Zoll oder Millimeter. Live, nichts gespeichert. 3 Compute-Endpunkte.
api.oanor.com/oring-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per API de Torque de Embreagem e Freio?
Qual è il limite di velocità di API de Torque de Embreagem e Freio?
Quanto costa API de Torque de Embreagem e Freio?
Posso cancellare l'abbonamento in qualsiasi momento?
API de Torque de Embreagem e Freio è 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/clutch-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/clutch-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/clutch-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/clutch-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.