Rope capacity, layers and turns
API · /winch-api
Winch Drum API
Winch and cable-drum maths as an API, computed locally and deterministically — the rope-capacity, line-pull and rope-out numbers a winch operator, rigger or recovery driver works a drum with. The capacity endpoint gives the rope a drum holds by exact layer geometry: the sum over every full layer of the turns per layer × π × that layer's mean wrap diameter, where turns per layer = drum width ÷ rope diameter and the number of layers = the flange-to-barrel depth ÷ rope diameter — a 10-inch barrel, 20-inch flange, 12-inch-wide drum on half-inch rope holds about 940 ft over 10 layers. The layer-pull endpoint shows why pull falls as the drum fills: the rated pull is for the bare-drum first layer, and as rope piles on, the growing lever arm cuts the line pull and raises the line speed in the same ratio — pull × (first-layer diameter ÷ this layer's diameter) — so the top layer of a deep drum can pull barely half the bottom-layer rating, which is why you spool off to bare drum for a hard pull or add a snatch block. The length-at-layer endpoint gives the rope wound after a number of full layers, for marking the rope or knowing how much line is out. Everything is computed locally and deterministically, so it is instant and private. Ideal for winch- and hoist-sizing tools, recovery and off-road apps, marine and industrial-rigging utilities, and engineering calculators. Pure local computation — no key, no third-party service, instant. Geometric estimate — allow for nesting and freeboard. 3 compute endpoints. For capstan friction use a capstan API; for block-and-tackle a pulley API.
API salute
salutare- Tempo di attività
- 100.00%
- Sondaggi del server · 24 ore su 24
- Latenza media
- 100 ms
- Sondaggi del server · 24 ore su 24
- Abbonati
- 4,761
- attiva
- Chiamate totali
- 0
- ultimi 7 giorni
Prezzi
Scegli un livello: fatturazione mensile, annullamento in qualsiasi momento.
Free
Gratis
- 4,850 chiamate/mese
- 2 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 4.850 Aufrufe/Monat
- 2 req/sec
- Kapazität + Layer Pull + Länge
- Keine Kreditkarte
Starter
€12.30 /mese
- 49,000 chiamate/mese
- 6 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 49.000 Aufrufe/Monat
- 6 req/sec
- Exakte Layer-Geometrie & Pull-Falloff
- E-Mail-Support
Pro
€39.60 /mese
- 205,500 chiamate/mese
- 15 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 205.500 Aufrufe/Monat
- 15 req/sec
- Windengrößen- und Takelage-Pipelines
- Prioritäts-Support
Mega
€122.00 /mese
- 1,108,000 chiamate/mese
- 40 richieste/secondo
- Tetto rigido (429 sopra la quota, nessuna eccedenza)
- 1.108.000 Aufrufe/Monat
- 40 req/sec
- Industrie- und OEM-Maßstab
- Dedizierte SLA
Costruito da
Correlato APIs
Altro APIs con tag sovrapposti.
Slackline Tension API
Tensioned-line point-load statics as an API, computed locally and deterministically — the line-tension and anchor-force numbers a slackliner, highliner or rigger works out before they weight a line. This is the V a loaded line makes under a person, not a self-weight catenary: the tension endpoint takes the span, the sag and the body load and returns the line tension and the horizontal anchor pull, because vertical balance is 2·T·sin(angle) = the body weight — so the flatter the line (the smaller the sag) the more the tension blows up, which is exactly why drum-tightening a line to kill the bounce can load the anchors to many times body weight. The sag endpoint inverts it: from a known line tension it returns the sag a mid-span load settles to (sin angle = weight ÷ twice the tension), and flags when the tension is too low to hold the load at all. The off-centre-load endpoint handles standing away from the middle, where the two halves carry different tensions: the horizontal pull is equal on both sides (H = weight × a × b ÷ (sag × span)) but the shorter, steeper segment runs at the higher tension and fails first — the reason a highliner near an anchor stresses that leash harder than one in the centre. Everything is computed locally and deterministically, so it is instant and private. Ideal for slackline and highline rigging tools, climbing and outdoor-gear apps, and tension-and-anchor calculators. Pure local computation — no key, no third-party service, instant. Geometric statics — combine with the real webbing and anchor ratings. 3 compute endpoints. For a self-weight hanging cable use a catenary API; for working-load-limit and safety factor a rigging API.
api.oanor.com/slackline-api
Mobile Crane Lift API
Mobile-Crane-Lift-Planungsmathematik als API, lokal und deterministisch berechnet – die Lastmoment-, Kippkapazitäts- und Abstützplattenzahlen, die ein Kranführer, Liftplaner oder Rigging-Ingenieur bei einem Hub überprüft. Der Lastmoment-Endpunkt gibt die Last × ihren Arbeitsradius (den horizontalen Abstand vom Drehzentrum zum Haken), die einzelne Zahl, die der Tragfähigkeitsbegrenzer eines Krans überwacht: Eine 5-Tonnen-Last bei 8 m ergibt ein Moment von 40 Tonnenmetern, dasselbe wie 10 Tonnen bei 4 m, weshalb die Diagrammkapazität steil abfällt, wenn der Ausleger ausfährt – das Moment, nicht das Gewicht, kippt den Kran. Der Kapazitätsendpunkt gibt eine vereinfachte Kippbilanz um den Drehpunkt: Die Last, die gerade kippt = Gegengewicht × sein Radius ÷ Lastradius, und die zulässige sichere Last ist ein Stabilitätsbruchteil davon (~75 % auf Abstützungen, ~66 % auf Raupen gemäß den Normen) – eine Lehr-/Plausibilitätszahl, die den Ausleger und das Überbaugerät ignoriert, niemals ein Ersatz für das Lastdiagramm. Der Abstützplattenendpunkt dimensioniert die Tellerplatte: Erforderliche Plattenfläche = Abstützbeinlast ÷ zulässiger Bodendruck (und die Seite einer quadratischen Matte), da Überlastung von schwachem Boden eine Hauptursache für Umkippen ist – ein 30-Tonnen-Bein auf 200 kPa benötigt etwa eine 1,2 m quadratische Matte. Alles wird lokal und deterministisch berechnet, daher ist es sofort und privat. Ideal für Liftplanungs- und Rigging-Tools, Bau- und Kranbetriebs-Apps sowie Baustellensicherheitsdienstprogramme. Reine lokale Berechnung – kein Key, kein Drittanbieterdienst, sofort. Vereinfacht – verwenden Sie immer das Lastdiagramm des Herstellers. 3 Compute-Endpunkte. Verwenden Sie für Anschlag- und WLL-Lasten eine Rigging-API.
api.oanor.com/crane-api
Pulley System API
Pulley and block-and-tackle mechanics as an API, computed locally and deterministically. The advantage endpoint computes the mechanical advantage of a pulley system — the ideal MA equals the number of rope parts supporting the load, which is also the velocity ratio — and returns the effort needed to hold or raise a load, effort = load/(n·efficiency), the length of rope that must be pulled (n times the lift height) and the work in and out. The friction endpoint models a real block and tackle where every sheave loses a little tension: the mechanical advantage becomes MA = e·(1−eⁿ)/(1−e) for a per-sheave efficiency e (≈0.96 for a plain bearing, ≈0.98 for a ball bearing), so it returns the true MA, the overall efficiency and the extra effort friction costs you. The solve endpoint takes any two of the load, the effort and the number of rope parts and returns the third — for example, how many parts you need so a given person can raise a given load, or the heaviest load a winch can lift. Everything is computed locally and deterministically, so it is instant and private. Ideal for rigging, lifting and hoist-design tools, sailing, climbing and theatre-rigging apps, crane and winch sizing, and physics education. Pure local computation — no key, no third-party service, instant. Live, nothing stored. 3 endpoints. This is pulley and block-and-tackle mechanics; for lever and moment balance use a lever API and for rope-around-a-drum capstan friction use a capstan API.
api.oanor.com/pulley-api
API de Fricción de Cabrestante y Correa
Matemáticas de fricción de cabrestante y correa (la ecuación de Euler-Eytelwein) como una API, calculada local y determinísticamente. El endpoint de cabrestante aplica T1/T2 = e^(μ·β) — la relación entre la tensión del lado tenso y el lado flojo de una cuerda o correa enrollada alrededor de un tambor depende solo del coeficiente de fricción y el ángulo de envoltura, no del diámetro del tambor — y resuelve para cualquiera de las dos tensiones, la fricción o el ángulo de envoltura que omitas, con el ángulo de envoltura dado en grados, radianes o vueltas completas. El endpoint de sujeción muestra el efecto cabrestante: cómo una fuerza pequeña sostiene o mueve una carga grande, fuerza de sujeción = Carga·e^(−μβ) y fuerza de tracción = Carga·e^(+μβ) — unas pocas vueltas de cuerda alrededor de una bita permiten que una persona sostenga un barco. El endpoint de correa dimensiona una transmisión por correa: a partir de la tensión máxima del lado tenso, la fricción y el ángulo de envoltura, proporciona la tensión del lado flojo, la tensión efectiva (neta) T1 − T2 que impulsa la carga y, con la velocidad de la correa, la potencia máxima transmisible antes de que la correa deslice. Todo se calcula local y determinísticamente, por lo que es instantáneo y privado. Ideal para herramientas de ingeniería mecánica y marina, diseño de transmisiones por correa, cabrestantes, polipastos y frenos de banda, aplicaciones de escalada y aparejos, y educación en física. Cálculo local puro — sin clave, sin servicio de terceros, instantáneo. En vivo, nada almacenado. 3 endpoints. Esto es fricción de correa y cuerda; para longitud de correa, ángulo de envoltura y relación de velocidad, usa una API de transmisión por correa.
api.oanor.com/capstan-api
Domande frequenti
Risposte rapide su prezzi, quote e integrazione.
Come ottengo una chiave API per Winch Drum API?
Qual è il limite di velocità di Winch Drum API?
Quanto costa Winch Drum API?
Posso cancellare l'abbonamento in qualsiasi momento?
Winch Drum 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/winch-api/SOME_PATH \
-H "x-oanor-key: oanor_test_..."
const res = await fetch("https://api.oanor.com/winch-api/SOME_PATH", {
headers: { "x-oanor-key": "oanor_test_..." }
});
const data = await res.json();
$ch = curl_init("https://api.oanor.com/winch-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/winch-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.