The repository contains a mix of STL files (3D models), firmware code, and documentation. The STL files are well-organized into folders based on their function or the part of the printer they belong to.
The firmware code is written in Python, which is a popular choice for 3D printer firmware due to its simplicity and flexibility. The code appears to be well-structured and commented, making it easy to understand what each part does.
The README file is comprehensive and provides a good overview of the project, including its purpose, features, and how to get started. It also includes a detailed Bill of Materials (BOM), which is essential for anyone looking to build their own version of this printer.
The project seems to have an active community, with a number of contributors and a steady stream of commits. The issues and pull requests are generally responded to in a timely manner, suggesting that the maintainers are actively engaged with the project.
The project also has a Discord server, which is a good sign of an active community. This provides a platform for users to ask questions, share their experiences, and contribute to the project.
The project appears to be in active development, with regular commits and updates. The upcoming features mentioned in the README suggest that the maintainers have a clear roadmap for the project's future.
However, the number of open issues and pull requests suggests that there may be some challenges in managing the project's growth. The maintainers may need to consider implementing more formal project management practices, such as using a project board or assigning specific roles to contributors.
Overall, the ERCF v2 project appears to be in a healthy state, with an active community and a clear direction for future development. However, the maintainers may need to address the open issues and pull requests to ensure the project continues to progress smoothly.
Issue #24 raises a potential conflict in the documentation regarding the use of GPIOs (PA3 / PA4) for both MMB connectors STP1 - STP2 and DIAG1 / DIAG2. This could lead to confusion or incorrect wiring by users.
Issue #23 discusses a problem with the CottonTail buffer model, where the rabbit in the middle starts on the second layer, making it difficult to print. This issue has received several comments, including suggestions for a two-part object for easier multicolor printing.
Issue #22 points out a missing piece in the CW2 main body for Filametrix, where the cable/board cover goes. This could affect the assembly or functionality of the device.
Issue #21 requests cuts in the 2020 mounting parts for the T-Nuts, as the parts don't hold in the 2020 extrusion. This issue has received several comments, including a discussion about the types of nuts being used.
Issue #16 reports that the part Supports/EASY-BRD/[a]_ERCF_Easy_Brd_Bracket_Bottom.stl is missing the built-in support material in the repo. This could affect the printability or functionality of the part.
Issue #13 points out that two little conical holes are missing from the Filament_Block_End.stl in the Reinforced Block End Mod. This could affect the assembly or functionality of the mod.
Issue #10 requests the addition of a cutter and/or filament sensor to XOL's current build. This could enhance the functionality of the software.
Issue #9 reports that the file [c]_Coupler_Block_180_xN.stl is missing the Male + Female keyways to lock it into the main body. This could affect the assembly or functionality of the device.
Issue #2 points out that the BOM is short on Omron microswitches, which could lead to users not having enough parts for their build.
Issue #8 asks if it's possible to print a specific test pattern with just 48 changes. It's unclear whether this is a feature request, a question about the software's capabilities, or something else.
Issue #1 and Issue #17 report typographical errors in the manual. While these are not major issues, they could cause confusion for users.
Issue #19 discussed a potential issue with the placement of a rabbit figure in the Support Arm file, but it was closed after it was clarified that the placement was intentional.
Issue #18 reported a missing file, but the issue was closed after it was fixed.
Issue #14 requested a note in the FAQ about what can be "carried forward" from V1.1 + the popular mods, and was closed after the requested information was added.
Issue #12 reported that the BTT MBB does not fit the case, but the issue was closed after the repository was updated with the correct files.
This is a simple PR that fixes a typo in the README.md file. It's a minor change that should not affect the functionality of the project.
This PR is more substantial, adding a filament cutting mount for the Crazy Dragon hotend. It includes several new files and modifications. It's worth noting that this PR was created 4 days ago and has not been merged yet.
This PR applies changes done to the CW2 motor plate in July 2023 to all Clockwork2 main bodies. It also adds a M6 bowden fitting version of the main body without sensor and a stronger latch. There is an ongoing discussion in the comments about the thickness of the mid plates. This PR includes a large number of changes and additions, and it seems to be a significant update to the project.
This PR adds support for StealthOrbiter Extruder. However, there is a comment from the author stating that there is currently some interference with the cutting arm. This PR is still open and might require further testing and updates.
This PR adds support for Phaetus Dragon UHF and Phaetus Dragon UHF mini hotend. It includes several new files and modifications. This PR was created 4 days ago and has not been merged yet.
This is a simple PR that fixes a typo in the Filametrix STL link. It's a minor change that should not affect the functionality of the project.
This is a simple PR that fixes a typo in the User mods link. It's a minor change that should not affect the functionality of the project.
This PR was closed without being merged. The author wanted to add a note to the FAQ about reprinting parts from the V1.1 mods. However, it was closed by another user who noted that another commit accomplishes the same goal. This suggests that the project maintainers are actively monitoring the PRs and ensuring that there is no duplication of effort.
The Enraged Rabbit Community Project is a software project focused on developing an expandable Multi-Material Unit (MMU) for Klipper based 3D printers. The project, also known as ERCF v2, is a community-driven major update to the Voron ERCF MMU. It aims to refine the existing MMU design to improve reliability, simplify construction, and align as closely as possible to v1.1 BOM.
The project includes an optional integrated filament buffer system (ERCT), filament cutter option (ERF), a collection of recommended toolhead sensor modifications, and LED status indication. It leverages the Happy Hare firmware MMU control software with Klipper Screen extensions.
The repository has a size of 1765315 kB and has been forked 32 times. It has 334 stars, suggesting a fair amount of interest in the project. There are 19 open issues, indicating some ongoing problems or enhancements that need to be addressed. The project has a total of 568 commits, and the most recent push was on 2023-12-26.
The project is licensed under the GNU General Public License v3.0, which allows others to copy, distribute and modify the software.
Open Issues: There are 19 open issues in the project. These need to be addressed to improve the software.
Single Branch: The project only has a single branch (master). For a project of this size, it might be beneficial to use feature branches or a dev branch to better manage changes and prevent potential issues in the master branch.
Recent Commits: The recent commits show a lot of changes to README and other documentation files. This suggests that the project is in active development and that the documentation is being kept up to date. However, it also indicates that there might be ongoing changes and potential instability in the project.
Upcoming Features: The README mentions an upcoming feature, the Purge System (ERPS), which is yet to be implemented. This is a TODO for the project.
Vendor List: The README mentions a list of vendors for kits and specialty parts that meet quality standards. However, the list is currently empty, indicating that this is an area that needs to be populated.
FAQ: The FAQ section is mentioned in the README, but it is currently in the RC1 phase, indicating that it might not be complete or fully polished. This is an area that might need further work.
User Print Showroom: The User Print Showroom section in the README is populated with images, but it's unclear if these are examples of what users can achieve with the project or if they are meant to be examples of specific features or capabilities. This could be clarified.
Commit Messages: Some commit messages are not very descriptive, making it hard to understand what changes were made. Improving the clarity of commit messages could make it easier for others to understand the changes and contribute to the project.
Summary
Detailed Reports