Parametric open source reconstructions of Voron printed parts

Overview

The Parametric Voron

This repository contains Fusion 360 reconstructions of various printed parts from the Voron printers (https://vorondesign.com/). Unlike the CAD files provided by the Voron team, which are essentially just STEP files in F3D format, these files have full parametric design history turned on, and are easy to edit.

This is a community effort and it may take months, or even years, to recreate the full set of parts. If you would like to contribute, feel free to open a pull request. Parts are organized per Voron release, with the same directory structure and naming conventions used by the original Voron parts.

For inspiration as to what this could eventually become, take a look at the Fusion 360 Models available for the Railcore project (https://railcore.org/). Every part is fully parametric with design history, and the parts are all linked together into a master assembly. (You will need to open in Fusion 360 directly to see the history, since the web version does not show that.)

Design Guidelines

  • All parts should match the Voron original parts as closely as possible. However, very small details that do not affect functionality do not need to be perfectly reconstructed. Examples:
    • If a complex shape could be constructed from a loft, an extruded cut, or a combination of fillets, please use whichever is most expedient. It's not necessary to choose the one which most exactly matches the result achieved in the original part.
    • Fillets and chamfers should have the same radius as the original part, but only within 0.05mm.
  • Including Voron logos and branding is optional, but preferred. All text should remain editable - no vector text please. The Voron logo is available in parametric F3D and rendered vector SVG formats in the assets folder. The font used for branding is Play from Google Fonts.
  • User parameters should be used where possible, for anything the user is very likely to want to change (e.g. the length of an extrude for something like a panel thickness), or for values which are reused frequently within the design and might need to be changed. However: a working part with no user parameters is preferable to no working part at all! Feel free to open a PR even if your F3D doesn't use them.
  • A pair of parts that are mirror images of each other only needs to have one F3D file uploaded, to avoid duplication. It is the user's responsibility to flip the part as needed before printing in the slicer.
  • Use millimeter measurements throughout.

Standard Parameter Names

For consistency across parts, where possible, please use the following names for various standard parameters (all units are millimeters):

Parameter Name Definition
ab_belt_width Width of the AB belts
chamfer Default chamfer, typically 0.4mm
extrusion_width Extrusion width
panel_thickness Panel thickness, including foam tape and VHB as needed
rail_width Linear rail width
tolerance Tolerance added for good fit, typically 0.2mm
z_belt_distance Distance between the Z belts
z_belt_width Width of the Z belts

Design Tips

An easy way to reconstruct a part is to import the original piece from the official Voron F3D CAD, center it, then start drawing sketches around it to capture the main dimensions. As you build up the part, you can hide or show the original body to compare against your component, and see what else you need to do.

To do this:

  • Open the original CAD F3D file in Fusion 360.
  • Find the part you are interested in in the heirarchy view.
  • Right click, and select "Save Copy As".
  • Open the new part and make it editable. Click on the body, go to MODIFY -> Align, and select the origin.

Before starting work, you MUST do the following, otherwise you will find yourself having to start all over again:

  • Turn on design history: right click the top level item in the heirarchy, and select "Capture Design History."
  • Create a new component: ASSEMBLE -> New Component.
  • Name the component to match the name of the part.
  • Activate the component in the heirarchy.
  • When starting your first sketch, be sure to select a plane that is part of the new component, and not a face of the imported body. Hiding the imported body temporarily is a good way to ensure this.

While working, you can capture measurements like distances, XYZ coordinates, and radii, by selecting appropriate points, lines, and curves, in the original component, and by using the INSPECT -> Measure tool as needed.

Don't forget to save your work often, since Fusion 360 can be unstable when used with certain graphics drivers. If you have an Nvidia graphics card and are running Windows, switch to the Studio driver using Geforce Experience (use the three dots icon at the top right of the DRIVERS tab), it is much more stable.

Before exporting, you can delete the imported body from the heirarchy.

Always follow the two golden rules of Fusion 360:

  1. Before doing anything, create a component and make sure it's activated.
  2. Name your components, sketches, and so on.

It's important to be aware of some shortcomings of Fusion 360 that require workarounds:

  • Extrudes in "join" mode combine bodies based on what is visible in the viewport at the time the designer does the join. However, this information is not captured in the design history! If you go back and edit the extrude, or modify a user parameter, Fusion may recombine bodies in a way that breaks the rest of the timeline. The solution is to put bodies that should stay separate into separate components: extrude will not join bodies from different components.

Progress (as of 2021-09-06 01:33AM EDT)

Voron-2 (46/131, 35%)

  • TEST_PRINTS (1/3, 33%)
    • Filament Card Caddy 25
    • Filament Card
    • Voron_Design_Cube_v7
  • VORON2.4 (45/128, 35%)
    • Electronics_Compartment (2/15, 13%)
      • DIN_Brackets (2/8, 25%)
        • duet_duex_bracket_x2
        • lrs_psu_bracket_clip
        • pcb_din_clip_x3
        • ramps_bracket_x2
        • raspberrypi_bracket
        • rs25_psu_bracket_clip
        • skr_1.3_1.4_bracket_x2
        • skr_mini_e3_bracket_x2
      • LCD_Module (0/4, 0%)
        • [a]_mini12864_case_hinge
        • mini12864_case_front
        • mini12864_case_rear
        • mini12864_spacer
      • Plug_Panel (0/3, 0%)
        • [a]_keystone_blank_insert
        • plug_panel
        • plug_panel_filtered_mains
    • Exhaust_Filter (2/4, 50%)
      • [a]_exhaust_filter_mount_x2
      • [a]_filter_access_cover
      • exhaust_filter_grill
      • exhaust_filter_housing
    • Gantry (15/54, 28%)
      • [a]_z_belt_clip_lower_x4
      • [a]_z_belt_clip_upper_x4
      • z_chain_bottom_anchor
      • z_chain_guide
      • AB_Drive_Units (1/6, 17%)
        • [a]_cable_cover
        • [a]_z_chain_retainer_bracket_x2
        • a_drive_frame_lower
        • a_drive_frame_upper
        • b_drive_frame_lower
        • b_drive_frame_upper
      • Front_Idlers (2/6, 33%)
        • [a]_tensioner_left
        • [a]_tensioner_right
        • front_idler_left_lower
        • front_idler_left_upper
        • front_idler_right_lower
        • front_idler_right_upper
      • X_Axis (7/35, 20%)
        • XY_Joints (0/8, 0%)
          • [a]_endstop_pod_hall_effect
          • [a]_endstop_pod_microswitch
          • [a]_xy_joint_cable_bridge_generic
          • [a]_xy_joint_cable_bridge_igus
          • xy_joint_left_lower
          • xy_joint_left_upper
          • xy_joint_right_lower
          • xy_joint_right_upper
        • X_Carriage (7/27, 26%)
          • [a]_belt_clamp_x2
          • [a]_blower_housing_front
          • blower_housing_rear
          • hotend_fan_mount
          • probe_retainer_bracket
          • x_carriage_frame_left
          • x_carriage_frame_right
          • x_carriage_pivot_block
          • Bowden (0/5, 0%)
            • bowden_module_front
            • bowden_module_rear_generic
            • bowden_module_rear_igus
            • bsp_adapter
            • tl_collet_adapter
          • Direct_Feed (4/8, 50%)
            • [a]_connector_cover
            • [a]_guidler
            • [a]_latch
            • chain_anchor_generic
            • chain_anchor_igus
            • extruder_body
            • extruder_motor_plate
            • latch_shuttle
          • Printheads (0/6, 0%)
            • E3D_V6 (0/2, 0%)
              • printhead_front_e3dv6
              • printhead_rear_e3dv6
            • Slice_Mosquito (0/2, 0%)
              • printhead_front_mosquito
              • printhead_rear_mosquito
            • TriangleLab_Dragon (0/2, 0%)
              • printhead_front_dragon
              • printhead_rear_dragon
      • Z_Joints (3/3, 100%)
        • z_joint_lower_x4
        • z_joint_upper_hall_effect
        • z_joint_upper_x4
    • Panel_Mounting (10/12, 83%)
      • bottom_panel_clip_x4
      • bottom_panel_hinge_x2
      • corner_panel_clip_3mm_x12
      • corner_panel_clip_6mm_x4
      • midspan_panel_clip_3mm_x12
      • midspan_panel_clip_6mm_x3
      • z_belt_cover_a_x2
      • z_belt_cover_b_x2
      • Front_Doors (4/4, 100%)
        • door_hinge_x4
        • handle_a_x2
        • handle_b_x2
        • latch_x2
    • Skirts (1/16, 6%)
      • [a]_60mm_fan_blank_insert_x2
      • [a]_belt_guard_a_x2
      • [a]_belt_guard_b_x2
      • side_fan_support_x2
      • 250 (0/4, 0%)
        • front_rear_skirt_a_250_x2
        • front_rear_skirt_b_250_x2
        • side_skirt_a_250_x2
        • side_skirt_b_250_x2
      • 300 (0/4, 0%)
        • front_rear_skirt_a_300_x2
        • front_rear_skirt_b_300_x2
        • side_skirt_a_300_x2
        • side_skirt_b_300_x2
      • 350 (0/4, 0%)
        • front_rear_skirt_a_350_x2
        • front_rear_skirt_b_350_x2
        • side_skirt_a_350_x2
        • side_skirt_b_350_x2
    • Spool_Management (2/2, 100%)
      • bowen_retainer
      • spool_holder
    • Tools (2/2, 100%)
      • bed_hole_marking_template_x1_Rev2
      • rail_installation_guide_center_x2
    • Z_Drive (6/11, 55%)
      • [a]_belt_tensioner_a_x2
      • [a]_belt_tensioner_b_x2
      • [a]_stopgap_80T_hubbed_gear
      • [a]_z_drive_baseplate_a_x2
      • [a]_z_drive_baseplate_b_x2
      • z_drive_main_a_x2
      • z_drive_main_b_x2
      • z_drive_retainer_a_x2
      • z_drive_retainer_b_x2
      • z_motor_mount_a_x2
      • z_motor_mount_b_x2
    • Z_Endstop (1/1, 100%)
      • nozzle_probe
    • Z_Idlers (4/4, 100%)
      • [a]_z_tensioner_x4_6mm
      • [a]_z_tensioner_x4_9mm
      • z_tensioner_bracket_a_x2
      • z_tensioner_bracket_b_x2
    • ZipChain (0/7, 0%)
      • XY (0/3, 0%)
        • zipchain2_xy_end
        • zipchain2_xy_link_a
        • zipchain2_xy_link_b
      • Z (0/4, 0%)
        • zipchain2_z_end
        • zipchain2_z_link_a
        • zipchain2_z_link_b
        • zipchain2_z_link_b_locking

License

All parts are licensed under the GPLv3. For the purposes of the GPL license:

  • "Source code" means:
    • Original parametric Fusion 360 (F3D) files, with design history enabled, fully visible, and editable.
    • Similar files from Autodesk Inventor, Solidworks, and any other parametric CAD tool.
    • DXFs and other editable vector-based graphics files.
    • Bitmap image files such as PNGs and JPGs.
    • Any other files which would normally be considered "source code" in a software project covered by GPLv3, such as scripts and source code in any programming language.
  • "Object code" means:
    • STEP files, STL files, 3MF files, F3D or other parametric CAD files which have had design history or original sketches removed or disabled.
    • Any bit sequence compiled from the "source code" or any derivative thereof, into a form from which the original "source code" cannot be directly retrieved.

Unless otherwise specified, copyright for each F3D file is owned collectively by the individual who committed (or is listed as an author in the commit for) the initial version of the file, and any individual who committed (or is listed as an author in the commit for) any modifications to it.

Owner
Matthew Lloyd
Matthew Lloyd
Raspberry Pi Pico Escape Room game.

Pico Escape Room Raspberry Pi Pico Escape Room game. Parts Raspberry Pi Pico Set of 2 x 20-pin Headers for Raspberry Pi Pico 4PCS Breadboards Kit Incl

Kevin Thomas 5 Feb 02, 2022
LUNA: a USB multitool & nMigen library

LUNA is a full toolkit for working with USB using FPGA technology; and provides hardware, gateware, and software to enable USB applications.

Great Scott Gadgets 750 Dec 28, 2022
Custom component for interacting with Octopus Energy

Home Assistant Octopus Energy ** WARNING: This component is currently a work in progress ** Custom component built from the ground up to bring your Oc

David Kendall 116 Jan 02, 2023
🐱🖨Cat printer is a portable thermal printer sold on AliExpress for around $20.

Cat printer is a portable thermal printer sold on AliExpress for around $20. This repository contains Python code for talking to the cat printer over

671 Jan 05, 2023
Detic ros - A simple ROS wrapper for Detic instance segmentation using pre-trained dataset

Detic ros - A simple ROS wrapper for Detic instance segmentation using pre-trained dataset

Hirokazu Ishida 12 Nov 19, 2022
Controlling fireworks with micropython

Controlling-fireworks-with-micropython How the code works line 1-4 from machine

Montso Mokake 1 Jan 08, 2022
Minimal and clean dashboard to visualize some stats of Pi-Hole with an E-Ink display attached to your Raspberry Pi

Clean Dashboard for Pi-Hole Minimal and clean dashboard to visualize some stats of Pi-Hole with an E-Ink display attached to your Raspberry Pi.

Alessio Santoru 104 Dec 14, 2022
Hotplugger: Real USB Port Passthrough for VFIO/QEMU!

Hotplugger: Real USB Port Passthrough for VFIO/QEMU! Welcome to Hotplugger! This app, as the name might tell you, is a combination of some scripts (py

DARKGuy (Alemar) 66 Nov 24, 2022
Terkin is a flexible data logger application for MicroPython and CPython environments.

Terkin Data logging for humans, written in MicroPython. Documentation: https://terkin.org/ Source Code: https://github.com/hiveeyes/terkin-datalogger

hiveeyes 45 Dec 15, 2022
A IC scan test interface for Arduino

ICSCAN_ARDUINO Prerequisites Python 3.6 or higher arduino uno or nano what is this It is a bitstream tranceiver to test IC chip It sends bitstream to

Nifty Chips Laboratory 0 Sep 15, 2022
Smart EQ connect - Custom Integration for Home Assistant

Smart EQ Connect platform as a Custom Component for Home Assistant.

Rene Nulsch 2 Jan 04, 2022
Run this code to blink your ThinkPad LED with a hidden mysterious Morse code! ;)

TMorse Run this code to blink your ThinkPad LED with a hidden mysterious Morse code! ;) Compatible with python3.9+. No third-party library is required

Mahyar 2 Jul 11, 2022
Playing diabolo with two robot arms in ROS + Gazebo

Playing diabolo with robots This repository holds the ROS packages for playing diabolo with two UR5e robot arms on ROS Melodic (Ubuntu 18.04). Read ou

23 Dec 18, 2022
An alternative to Demise-Assistant-Batch made entirely in Python for more capabilities.

Demise-Assistant-Python An alternative to Demise-Assistant-Batch made entirely in Python for more capabilities. IMPORTANT NOTE Demise-Assistant-Batch

SkelOrganisation 1 Nov 24, 2021
Python application, displaying currently played track from Spotify on OLED display connected via I2C

RaspberryPi Spotify OLED Display This application will display currently played track on SSD1306 OLED display connected to RaspberryPi. Displayed stuf

Wojciech Olech 2 Dec 30, 2021
PlatformIO development platform for GSM modules

PlatformIO development platform for GSM modules Supported Modules Quectel M66 OpenCPU Arduino - TODO other - in progress... Supported Boards Comet M66

Georgi Angelov 5 Aug 06, 2022
A Raspberry Pi Pico powered Macro board, like a Streamdeck but cheaper and simpler.

Env-MCRO A Raspberry Pi Pico powered Macro board, like a Streamdeck but cheaper and simpler. (btw this image is a bit outdated, some of the silkscreen

EnviousData 68 Oct 14, 2022
Setup DevTerm to be a cool non-GUI device

DevTerm hobby project I bought this amazing device: DevTerm A-0604. It has a beefy ARM processor, runs a custom version of Armbian, embraces Open Sour

Alex Shteinikov 9 Nov 17, 2022
emhass: Energy Management for Home Assistant

emhass EMHASS: Energy Management for Home Assistant Context This module was conceived as an energy management optimization tool for residential electr

David 70 Dec 24, 2022
Homeautomation system created with Raspberry Pi 3 and Firebase.

Homeautomation System - Raspberry Pi 3 Desenvolvido com Python, Flask com AJAX e Firebase permite o controle local e remoto Itens necessários Raspberr

Joselino Santos 0 Mar 09, 2022