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
It is a serial communicator(controller, receiver...), communicate with sensor LP20 which is a laser ranger.

Intro It is a serial communicator(controller, receiver...), communicate with sensor LP20 which is a laser ranger. Its datasheet is contained in this r

3 Sep 19, 2022
A simple program to make MSI Modern 15 speaker and microphone mute led work.

MSI Modern 15 sound led fixup for linux A simple program to fix the MSI Modern 15 speaker and microphone mute LEDs. Installation Requirements pulsectl

Seyed Danial Movahed 4 Oct 18, 2022
OPNsense integration with Home Assistant

hass-opnsense Join OPNsense with home-assistant! hass-opnsense uses the built-in xmlrpc service of OPNsense for all interactions. This project is curr

Travis Glenn Hansen 54 Jan 03, 2023
The robot is an autonomous small scale racing car using NVIDIA Jetson Nano.

The robot is an autonomous small scale racing car using NVIDIA Jetson Nano. This project utilizes deep learning neural network framework Keras/Tensorflow, together with computer vision library OpenCV

1 Dec 08, 2021
Imbalaced Classification and Robust Semantic Segmentation

Imbalaced Classification and Robust Semantic Segmentation This repo implements two algoritms. The imbalance clibration (IC) algorithm for image classi

24 Jul 23, 2022
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
The main aim of this project is to avoid the accidents in shredding ( Waste Recycling Industry )

shredder-Machine-Hand-Safety The main aim of this project is to avoid the accidents in shredding ( Waste Recycling Industry ) . The Basic function of

Shubham Chaudhari 1 Nov 15, 2021
Small Robot, with LIDAR and DepthCamera. Using ROS for Maping and Navigation

🤖 RoboCop 🤖 Small Robot, with LIDAR and DepthCamera. Using ROS for Maping and Navigation Made by Clemente Donoso, 📍 Chile 🇨🇱 RoboCop Lateral Fron

Clemente Donoso Krauss 2 Jan 04, 2022
Estimation of whether or not the persons given information will have diabetes.

Diabetes Business Problem : It is desired to develop a machine learning model that can predict whether people have diabetes when their characteristics

Barış TOKATLIOĞLU 0 Jan 20, 2022
The software that powers the sPot: a 4th generation

This code is meant to accompany this project in which a Spotify client is built into an iPod "Classic" from 2004. Everything is meant to run on a Raspberry Pi Zero W.

Guy Dupont 683 Dec 28, 2022
ModbusTCP2MQTT - Sungrow & SMA Solar Inverter addon for Home Assistant

ModbusTCP2MQTT Sungrow & SMA Solar Inverter addon for Home Assistant This addon will connect directly to your Inverter using Modbus TCP. Support model

Teny Smart 40 Dec 21, 2022
OpenStickFirmware is open source software designed to handle any and all tasks required in a custom Fight Stick

OpenStickFirmware is open source software designed to handle any and all tasks required in a custom Fight Stick. It can handle being the brains of your entire stick, or just handling the bells and wh

Sleep Unit 23 Nov 24, 2022
Monitor an EnvisaLink alarm module running Honeywell firmware, and set a Nest device to Home/Away depending on whether the alarm is Disarmed/Away.

Nestalarm Monitor an EnvisaLink alarm module running Honeywell firmware, and set a Nest device to Home/Away depending on whether the alarm is Disarmed

1 Dec 30, 2021
A script that publishes power usage data of iDrac enabled servers to an MQTT broker for integration into automation and power monitoring systems

iDracPowerMonitorMQTT This script publishes iDrac power draw data for iDrac 6 enabled servers to an MQTT broker. This can be used to integrate the pow

Lucas Zanchetta 10 Oct 06, 2022
GUI wrapper designed for convenient service work with TI CC1352/CC2538/CC2652 based Zigbee sticks or gateways. Packed into single executable file

ZigStar GW Multi tool is GUI wrapper firtsly designed for convenient service work with Zig Star LAN GW, but now supports any TI CC1352/CC2538/CC2652 b

133 Jan 01, 2023
Raspberry Pi & Accelerometer with Losant's EEA

Raspberry Pi & Accelerometer with Losant's EEA This is a repository that contains companion code to this EEA How To guide. Each folder is named accord

Losant 1 Oct 29, 2021
LifeSaver automatically, periodically saves USB flash drive data into the PC

LifeSaver automatically, periodically saves USB flash drive data into the PC. Theoriticaly it will work with any any connected drive ex - Hard Disk ,SSD ... But, can't handle Backing up multipatition

siddharth dhaka 4 Sep 26, 2021
Segger Embedded Studio project for building & debugging Flipper Zero firmware.

Segger Embedded Studio project for Flipper Zero firmware Установка Добавить данный репозиторий в качестве сабмодуля в корень локальной копии репозитор

25 Dec 28, 2022
Drobo Status is a python program that will connect to your Drobo and return JSON data regarding your Drobo

This is a simple python script that will run a docker container to pull data from Drobo. It will give information like (Name, serial, firmware, disk-total, disk-used, disk-free and individual disk st

Biofects 1 Jan 15, 2022
ArduinoWaterHeaterIOT - IoT Probe of a solar PV water heating system - Arduino, Python, MQTT, MySQL

ArduinoWaterHeaterIOT IoT Probe of a solar PV water heating system - Arduino, Raspberry Pi, Python, MQTT, MySQL The Arduino sends the AC and DC watts

Jacques Fourie 1 Jan 11, 2022