My Marlin configs for Fabrikator Mini and CTC i3 Pro B
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.
Scott Lahteine 7e42c7563c Move build files into place 6 年之前
.github Give a more detailed issue template 7 年之前
Marlin Move build files into place 6 年之前
buildroot PlatformIO Travis test 6 年之前
.gitattributes Add hidden option to output Bilinear grids in JSON 7 年之前
.gitignore Add VSCode to .gitignore 6 年之前
.travis.yml Support travis new "trusty" build environment 6 年之前
LICENSE Update LICENSE 8 年之前
README.md Marlin bugfix-2.0.x Version/README 6 年之前
platformio.ini Move build files into place 6 年之前

README.md

Marlin 3D Printer Firmware

Build Status Coverity Scan Build Status

Additional documentation can be found at the Marlin Home Page. Please test this firmware and let us know if it misbehaves in any way. Volunteers are standing by!

Marlin 2.0 Bugfix Branch

Not for production use. Use with caution!

This branch is used to accumulate patches to the latest 2.0.x release version. Periodically this branch will form the basis for the next minor 2.0.x release.

Download earlier versions of Marlin on the Releases page.

Recent Changes

  • Add a Hardware Abstraction Layer (HAL) supporting current AVR platforms
  • Planning a HAL for Re:Arm
  • Planning a HAL for STM32

Submitting Patches

Proposed patches should be submitted as a Pull Request against this branch (bugfix-2.0.x).

  • This branch is for fixing bugs and integrating any new features for the duration of the Marlin 2.0.x life-cycle.
  • Follow the Coding Standards to gain points with the maintainers.
  • Please submit your questions and concerns to the Issue Queue.

RepRap.org Wiki Page

Credits

The current Marlin dev team consists of:

License

Marlin is published under the GPL license because we believe in open development. The GPL comes with both rights and obligations. Whether you use Marlin firmware as the driver for your open or closed-source product, you must keep Marlin open, and you must provide your compatible Marlin source code to end users upon request. The most straightforward way to comply with the Marlin license is to make a fork of Marlin on Github, perform your modifications, and direct users to your modified fork.

While we can’t prevent the use of this code in products (3D printers, CNC, etc.) that are closed source or crippled by a patent, we would prefer that you choose another firmware or, better yet, make your own.