3D models of components for kite control bars
This repository is a collection of 3D models for components that could be used in the construction of kite control bars. The models were created with OpenSCAD, a programming language and development environment for 3D modelling. Some of these modules are complete components that have been used in actual gear. Some are speculative designs. Other are primitives used as part of a complete component.
How to view and manipulate these models
These OpenSCAD models can be opened, viewed, and revised using free software found at www.openscad.org. The software is available for Mac OS X, Windows, and Linux.
For the most basic use, download and install OpenSCAD. Open a model and preview it. Use the viewer controls to examine the model from all sides.
To make changes you need only basic programming skills. The editor window of OpenSCAD will show the code that generates the model. Revise the values of variables defined in the file and preview the revised model to understand how each variable affects the model. Note that all dimensions are in millimeters.
How to print these models
To print a model, use OpenSCAD to generate a vector file in STL format. Most 3D printers can use an STL file as input.
Default 3D printer settings often use a minimal number of shells and a sparse infill that is too weak to handle the loads required for these components. To address this, use at least 3 shells and a high infill. 80% infill is not unreasonable.
Most of these designs do not need supports. In some cases overhangs have been specifically tailored to meet the Makerbot's maximum overhang recommendation of no more than 68 degrees off vertical.
About the models
stopper_ball - The ball used in a moveable stopper on a kite bar trim line. STL files have been generated for 4mm_amsteel_blue_trimline and 5mm_amsteel_blue_trimline. The previous iteration of this ball was field tested and worked very well. This iteration removes a twist in the bungie path. To print it reliably, use a support structure that surrounds the base.
stopper_block_v4 - This block is used in tandem with the stopper ball to form a moveable stopper. A slightly earlier version of this design has been field tested. This version should be easier to print than the previous version. STL files have been generated for 4mm_amsteel_blue_trimline and 5mm_amsteel_blue_trimline.
separation_block_v1 - This component transfers load from the main flying lines by providing a pair of parallel bore holes. Each flying line passes through a bore hole. The flying line is trapped on the lower side of the block via a larks head of relatively fat line. The pair of bore holes surround a larger, central bore hole. The central bore hole allows a heavier line to be secured to the separation block. The upper end is secured via an overhand knot. The lower end of the central line entraps a low friction ring that acts as a pulley for the trim line. An STL File is available.
cleat_bead - This component is meant to mate on to the pilot-end of Clamcleat® CL826-11. It fits tightly onto the end of the cleat with a positive rotational lock. The spherical shape conforms to the circular hole in the kite-side of the bar and allows for easy bar spinning. The rotational lock allows for a flag-line guide path to be routed away from the jaws of the cleat to reduce the risk of cleating the flag line. STL files have been generated for 5mm trim lines.
separation_block_v2 - This component transfers load from the main flying lines by providing a pair of parallel bore holes. Each flying line passes through a bore hole. The flying line is trapped on the lower side of the block via a larks head of relatively fat line. The pair of bore holes surround a larger, toroidal central bore hole. The curved central bore provides a low friction path for the trim line. An 80-facet-count STL files has been generated with a [6mm](printable/separation_block_v2_6mm_trimline_bore_7e61bdd.stl trim line bore. This design is untested.
If you would like to contribute revisions to these models or add new models feel free to fork this repo, make changes and submit a pull request. You are also welcome to open an issue and attach a file or send me files at firstname.lastname@example.org. All contributions should include a Creative Commons Public Domain license.