Aerobar clamp and extension compatibility: identify every receiving interface
A basebar clamp, extension receiver and armrest assembly have different requirements. Keep exact model permissions and unresolved physical checks separate before reading an aero cockpit dimension.
Published 11 October 2026 · OpenBikeFit
Aero contact reference · not to scale
Different receivers. Independent permission.
The linked Vuka Clip manual separately names 31.8 mm basebar and 22.2 mm extension interfaces; it excludes 22 mm extensions for that system.
Receiving-bar permission, actual contact region and the complete pad/riser support remain separate checks.
0.2 mm arithmetic is not a tolerance, shim design or approved assembly.
On this page
- 01Start at the basebar and its intended mounting region
- 02The extension receiver is a second interface
- 03Keep the support chain visible
- 04A dimension list is not a permission list
- 05Matching one requirement does not clear the others
- 06Build a reference ledger without customer data
- 07Continue to coordinates only after naming the assembly
Free blank worksheet
Keep a technical paper reference
Use reference and question spaces for extra armrest fields. Fixed digital slots do not replace these distinct endpoints.
Open toolAn aero cockpit can add several receiving interfaces between the bicycle and the named armrest or grip point. A single familiar diameter on a product page cannot resolve all of them. Identify the existing basebar, clips or integrated receiver, extensions, armrest holders, pads and any risers as separate parts before turning a dimension into a comparison.
This guide is an identification ledger, not a purchase recommendation or installation procedure. It does not ask you to loosen a clamp, remove a cover, cut a tube or test an unsupported arrangement. Missing documentation remains missing. Physical inspection and any separately authorised work require the exact applicable instructions and a competent mechanic; reading a source link does not complete that work.
Start at the basebar and its intended mounting region
The basebar is the receiving handlebar or cockpit, not the extension tube held farther forward. Record its exact model, generation and material, then the identity of the clip or integrated mount. A round diameter at the stem does not prove there is a permitted round clamping region for an accessory beside it. A shaped or one-piece cockpit can have different restrictions from another bar carrying the same brand name.
ENVE publishes a model-specific compatibility table for its clip-on families, including named bars that are excluded. Its product description conditions a 31.8 mm arrangement on a clip-on-compatible handlebar. Those statements illustrate why the receiving bar permission is an independent question. They are not permission for another generation, an apparently similar carbon shape or every handlebar with that number.
The extension receiver is a second interface
An extension tube fits a receiver in the aerobar assembly. That junction has its own dimension, contact region and approved configuration. It is not the diameter of the basebar. The linked SRAM Vuka Clip Rev B manual names 31.8 mm handlebars and 22.2 mm extensions separately, and explicitly excludes 22 mm extensions for that system. Preserve the distinction and the manual revision, not merely a rounded description from a listing.
The arithmetic difference 22.2 − 22 = 0.2 mm is not an allowable tolerance, an engineering assessment or a sleeve specification. This guide supplies no workaround. Do not round one interface into another, infer that tightening harder resolves the difference, or treat a nominal diameter as evidence of correct engagement and load support. A dimension can identify a question without answering it.
Keep the support chain visible
Follow the support chain from the receiving basebar through the clip or bracket, any riser or bridge, the armrest holder and the actual pad. Each link can require an exact part, orientation and associated hardware. A pad that appears to sit at the desired height does not document what supports it underneath. An extension that enters a receiver does not identify the permitted support arrangement for the armrest.
Record left and right identities rather than assuming a mirrored assembly. Preserve part numbers, source revisions and any known differences; keep unknown hardware unknown. Do not derive bolt engagement, load capacity or a permitted riser height from the outside appearance of an assembled cockpit. There is no universal stack ceiling, tightening value or washer sequence in this article.
A dimension list is not a permission list
A source can list armrest offset, width, local stack and extension length for one named configuration. Profile Design lists these as separate fields for its Subsonic/Ergo/39a assembly. Their presence establishes that several quantities exist, not that the largest number in one row can be combined with the largest number in every other row. Position ranges can depend on particular parts and arrangements.
Keep a source dimension beside its original origin, endpoint and conditions. Do not use a local armrest stack as BB-relative pad height, or an extension stock length as hand reach. If an applicable drawing or convention is unavailable, label the interpretation unresolved. A browser diagram cannot supply missing manufacturer geometry or approve a combination of parts from separate tables.
Matching one requirement does not clear the others
Consider a fictional ledger with basebar diameter recorded, extension diameter recorded, but receiving-bar accessory permission and riser identity unknown. The result is two recorded dimensions and two unresolved questions, not a compatible assembly. A successful dimensional comparison has no authority to change the unknown entries into yes. An expressly excluded combination likewise remains excluded rather than becoming an uncertainty that can be averaged away.
Even complete documentation does not inspect the actual condition of parts, their contact surfaces or the assembled control and clearance situation. Keep documentary permission separate from a physical check. Nothing here certifies material condition, correct fastening, steering, braking, riding suitability or a competition rule. The educational journey describes references, not a ready-to-ride badge.
Build a reference ledger without customer data
Use separate lines for receiving basebar, clip or integrated mount, each extension, each receiver, armrest holder, pad, riser and associated unresolved questions. On each line preserve exact identity, declared interface, applicable source, revision and what has not been checked. A photograph or catalogue number can support identification without proving hidden engagement or permission.
Use technical part references rather than rider names, contact or health details. A blank paper worksheet has reference and open-question spaces, but its fixed digital whole-sheet fields do not include dedicated aerobar dimensions. Do not put an armrest coordinate into frame stack or a grip point into bar-clamp reach just to fill a slot. Keep the additional technical ledger under your own controlled workflow.
Continue to coordinates only after naming the assembly
The next guide separates BB-relative pad coordinates from frame geometry and local hardware offsets. Then the width guide names each pad station and the extension guide identifies a grip point. You can learn those definitions while every physical permission remains unresolved; the drawings are hypothetical geometry, not evidence that an unknown assembly is acceptable.
The existing cockpit calculator concerns a bar-clamp point under its declared model. It does not validate clip-on permission, calculate an ideal armrest setting or reconstruct a complete aero cockpit. Keep that boundary at the hand-off. A source visit or worksheet opening is an ordinary page request, not a component choice, installation, completed inspection or fit result.
Practical questions
Frequently asked questions
Does a 31.8 mm label mean any clip-on fits?
No. Identify the receiving model, permitted mounting region, material and the exact clip-on requirements. A nominal diameter is only one question.
Can I round 22.2 mm to 22 mm?
Not as a compatibility decision. The linked Vuka Clip manual expressly excludes 22 mm extensions for that system; 0.2 mm arithmetic is not a tolerance or shim design.
Does reaching the stated pad height approve the risers?
No. Height and the identity and permission of the complete support assembly are independent records.
Should I loosen the parts to fill this guide?
This guide provides no disassembly or installation procedure. Retain unresolved identities and physical questions for the exact instructions and mechanic.