andrey
/
Marlin_FB4S
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity
Marlin 2.0 for Flying Bear 4S/5
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.
12015 Commits
4 Branches
6 Tags
134 MiB
 
 
 
 
 
 
Tree: 4900c28bf6
Branches Tags
${ item.name }
Create tag ${ searchTerm }
Create branch ${ searchTerm }
from '4900c28bf6'
${ noResults }
Marlin_FB4S/config/examples/BQ/Hephestos_2
Scott Lahteine 5e38d70697
Fix M217 report label, general cleanup 		6 years ago
..
Configuration.h Fix M217 report label, general cleanup 6 years ago
Configuration_adv.h Confirm before starting SD print (#13616) 6 years ago
README.md Relocate configs above Marlin/src folder (#13299) 6 years ago
_Bootscreen.h Relocate configs above Marlin/src folder (#13299) 6 years ago

README.md

Example Configuration for BQ Hephestos 2

Based on the original configuration file shipped with the heavily modified Marlin fork by BQ. The forked firmware and configuration files can be found at the BQ Github repository.

NOTE: The look and feel of the LCD menu will change dramatically when using the original Marlin firmware.

Changelog

  • 2018/05/30 - Configuration updated to the latest Marlin version (43a55a9af). ABL Bilinear 5x5 is active by default.

  • 2017/07/06 - Configuration updated to the latest Marlin version and added support for the official BQ heated bed upgrade kit.

  • 2016/12/13 - Configuration updated to the latest Marlin version.

  • 2016/07/13 - Configuration updated to the latest Marlin version.

  • 2016/06/21 - Disabled heated bed related options, activated software endstops and SD printing now disables the heater when finishes printing.

  • 2016/03/21 - Activated 4-point auto leveling by default and updated miscellaneous z-probe values.

  • 2016/03/01 - The first release of Marlin's configuration file for the BQ Hephestos 2 3D printer.

Support

This configuration should work easily with the stock Hephestos 2, nevertheless if you encounter any issues you may contact me on Github, Twitter or by mail.