klipper-voron-V2 | Generic Klipper configuration for CoreXY printers
kandi X-RAY | klipper-voron-V2 Summary
kandi X-RAY | klipper-voron-V2 Summary
klipper-voron-V2 is a Python library. klipper-voron-V2 has no bugs, it has no vulnerabilities, it has a Strong Copyleft License and it has low support. However klipper-voron-V2 build file is not available. You can download it from GitHub.
Generic Klipper configuration for CoreXY printers
Generic Klipper configuration for CoreXY printers
Support
Quality
Security
License
Reuse
Support
klipper-voron-V2 has a low active ecosystem.
It has 211 star(s) with 81 fork(s). There are 18 watchers for this library.
It had no major release in the last 12 months.
There are 16 open issues and 27 have been closed. On average issues are closed in 15 days. There are 7 open pull requests and 0 closed requests.
It has a neutral sentiment in the developer community.
The latest version of klipper-voron-V2 is v2.0
Quality
klipper-voron-V2 has no bugs reported.
Security
klipper-voron-V2 has no vulnerabilities reported, and its dependent libraries have no vulnerabilities reported.
License
klipper-voron-V2 is licensed under the GPL-3.0 License. This license is Strong Copyleft.
Strong Copyleft licenses enforce sharing, and you can use them when creating open source projects.
Reuse
klipper-voron-V2 releases are available to install and integrate.
klipper-voron-V2 has no build file. You will be need to create the build yourself to build the component from source.
Installation instructions, examples and code snippets are available.
Top functions reviewed by kandi - BETA
kandi's functional review helps you automatically verify the functionalities of the libraries and avoid rework.
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of klipper-voron-V2
Currently covering the most popular Java, JavaScript and Python libraries. See a Sample of klipper-voron-V2
klipper-voron-V2 Key Features
No Key Features are available at this moment for klipper-voron-V2.
klipper-voron-V2 Examples and Code Snippets
No Code Snippets are available at this moment for klipper-voron-V2.
Community Discussions
No Community Discussions are available at this moment for klipper-voron-V2.Refer to stack overflow page for discussions.
Community Discussions, Code Snippets contain sources that include Stack Exchange Network
Vulnerabilities
No vulnerabilities reported
Install klipper-voron-V2
The install of this config folder should not be too complicated if you are already familiar with the klipper configuration system. Here are the steps:.
Use an SSH connection to connect to your printer
Check if you already have a config folder in the ~/printer_data directory and remove it (or rename it to keep a backup).
Clone this config in the ~/printer_data/config directory. You can use the following command: git clone https://github.com/Frix-x/klipper-voron-V2.git ~/printer_data/config
Open and configure the printer.cfg file: you just need to uncomment the lines that suit your printer hardware configuration. Basically start by selecting the board_pins coresponding to your MCU, then select the components used and software config needed (such as extruder type, XY motors, Z motors, QGL vs Z_TILT, etc...).
Then, open the selected board_pins file in the config/mcus folder and add your MCU(s) serial port(s). Please follow the official klipper documentation to find it.
Check your wiring and verify that the selected board_pins file is correct. See pinout.md for more info
Now, open all the selected files in your printer.cfg and check that the pins are ok for your machine (regarding the board prefix name, the direction !, the pull-ups ^ or pull-downs ~). Note: this step is necessary because of a current Klipper limitation that doesn't allow me to put these symbols directly in the board_pins files... I'm still looking for alternatives.
Also, in the same way, open all the selected files in your printer.cfg and check the dimensions, the limits, the currents, and all the other values in every config sections. Pay a special attention to the axis limits in the [stepper_...] sections from the files located in config/hardware/XY or config/hardware/Z. Also check the thermistor types in [extruder] and [heated_bed], size of the plate in [bed_mesh], etc... Note: this step is necessary because of a current Klipper limitation that doesn't allow the use of variables in the config files... I'm still looking for alternatives.
Modify and adapt the variables.cfg file to suit the configuration of your machine. This file helps to configure and customize how all the macros should behave (coordinates of everythings, enabling/disabling software features, etc...).
Check very carefully all the features! This step is very important to avoid any problem on your machine. You can start by following the config checks from the official Klipper documentation. Then also verify that you are able to attach/detach the mechanical probe, do the QGL/Z_TILT, have the correct coordinates for all the used components (purge bucket, physical Z endstop, etc...). You should also verify your first layer calibration (and the switch_offset parameter from the automatic z calibration plugin if using it), etc...
Finally when everything looks to be working, you need to add the custom print start gcode in your slicer. Here is an example for SuperSlicer: START_PRINT EXTRUDER_TEMP={first_layer_temperature[initial_extruder] + extruder_temperature_offset[initial_extruder]} BED_TEMP=[first_layer_bed_temperature] MATERIAL=[filament_type] CHAMBER=[chamber_temperature] SIZE={first_layer_print_min[0]}_{first_layer_print_min[1]}_{first_layer_print_max[0]}_{first_layer_print_max[1]} Also add to your custom print end gcode in your slicer: END_PRINT
Use an SSH connection to connect to your printer
Check if you already have a config folder in the ~/printer_data directory and remove it (or rename it to keep a backup).
Clone this config in the ~/printer_data/config directory. You can use the following command: git clone https://github.com/Frix-x/klipper-voron-V2.git ~/printer_data/config
Open and configure the printer.cfg file: you just need to uncomment the lines that suit your printer hardware configuration. Basically start by selecting the board_pins coresponding to your MCU, then select the components used and software config needed (such as extruder type, XY motors, Z motors, QGL vs Z_TILT, etc...).
Then, open the selected board_pins file in the config/mcus folder and add your MCU(s) serial port(s). Please follow the official klipper documentation to find it.
Check your wiring and verify that the selected board_pins file is correct. See pinout.md for more info
Now, open all the selected files in your printer.cfg and check that the pins are ok for your machine (regarding the board prefix name, the direction !, the pull-ups ^ or pull-downs ~). Note: this step is necessary because of a current Klipper limitation that doesn't allow me to put these symbols directly in the board_pins files... I'm still looking for alternatives.
Also, in the same way, open all the selected files in your printer.cfg and check the dimensions, the limits, the currents, and all the other values in every config sections. Pay a special attention to the axis limits in the [stepper_...] sections from the files located in config/hardware/XY or config/hardware/Z. Also check the thermistor types in [extruder] and [heated_bed], size of the plate in [bed_mesh], etc... Note: this step is necessary because of a current Klipper limitation that doesn't allow the use of variables in the config files... I'm still looking for alternatives.
Modify and adapt the variables.cfg file to suit the configuration of your machine. This file helps to configure and customize how all the macros should behave (coordinates of everythings, enabling/disabling software features, etc...).
Check very carefully all the features! This step is very important to avoid any problem on your machine. You can start by following the config checks from the official Klipper documentation. Then also verify that you are able to attach/detach the mechanical probe, do the QGL/Z_TILT, have the correct coordinates for all the used components (purge bucket, physical Z endstop, etc...). You should also verify your first layer calibration (and the switch_offset parameter from the automatic z calibration plugin if using it), etc...
Finally when everything looks to be working, you need to add the custom print start gcode in your slicer. Here is an example for SuperSlicer: START_PRINT EXTRUDER_TEMP={first_layer_temperature[initial_extruder] + extruder_temperature_offset[initial_extruder]} BED_TEMP=[first_layer_bed_temperature] MATERIAL=[filament_type] CHAMBER=[chamber_temperature] SIZE={first_layer_print_min[0]}_{first_layer_print_min[1]}_{first_layer_print_max[0]}_{first_layer_print_max[1]} Also add to your custom print end gcode in your slicer: END_PRINT
Support
For any new features, suggestions and bugs create an issue on GitHub.
If you have any questions check and ask questions on community page Stack Overflow .
Find more information at:
Reuse Trending Solutions
Find, review, and download reusable Libraries, Code Snippets, Cloud APIs from over 650 million Knowledge Items
Find more librariesStay Updated
Subscribe to our newsletter for trending solutions and developer bootcamps
Share this Page