-
-
Notifications
You must be signed in to change notification settings - Fork 33
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
MMU vs D6 Branch Clarification #8
Comments
Initially this branch and the branch for my personal D6 (located in another repository) were used to develop initial support for the duplicator 6 in mainline. This branch is setup for those who have a stock duplicator 6 and don't want to mess with compiling code or want something that works off the bat. I have it setup to automatically build when I commit changes. The branch is a little behind the development branch in mainline as I try to only update when there is something worthwhile and the firmware feels stable. I usually update it alongside my personal branch so I can test most of the features as my D6 isn't stock anymore. If you are the type that wants bleeding edge I encourage you to use mainline and the configuration located in the examples included with mainline. |
Thanks for the reply dot-bob! As a starting point, can you confirm if there is any hardware differences between the D6 & MMU that would require a configuration change? For now i'd like to just get the latest stable branch you have tuned for a stock D6 and make any mods required for the MMU. Which repo/branch would that be? Thanks Again! |
Hardware wise the Duplicator 6 (D6) and the Monoprice Maker Ultimate (MMU) are the same. The only difference is the firmware on the MMU has been rebranded. As far as branches I would go with bugfix-2.0.x. The branch 1.1.x is end of life and receives few updates. I will be updating my branch to mainline bugfix-2.0.x in the next week after I have run it a while on my MMU. |
It sounds like it should be safe to install on my MMU. Has anyone tested this? |
@dot-bob Are you going to update this branch now that Marlin 2.0 stable is out? What changes have you made to your D6 that are different than stock. |
# This is the 1st commit message: Add Support for ADIMLab Granty # The commit message dot-bob#2 will be skipped: # Update Configuration.h # The commit message dot-bob#3 will be skipped: # Add files via upload # # Add Support for ADIMLab Granty # The commit message dot-bob#4 will be skipped: # Create Configuration.h # The commit message dot-bob#5 will be skipped: # Delete Configuration.h # The commit message dot-bob#6 will be skipped: # Create Test.h # The commit message dot-bob#7 will be skipped: # Add files via upload # The commit message dot-bob#8 will be skipped: # Delete Test.h # The commit message dot-bob#9 will be skipped: # Delete Configuration.h # The commit message dot-bob#10 will be skipped: # Delete Configuration_adv.h # The commit message dot-bob#11 will be skipped: # Add files via upload # # Add ADIMLab Pins # The commit message dot-bob#12 will be skipped: # Add files via upload # # Add Bootscreen # The commit message #13 will be skipped: # Update Configuration.h # # Add Bootscreen # The commit message #14 will be skipped: # Update pins.h # # Add ADIMLab Board # The commit message #15 will be skipped: # Update boards.h # # Add ADIMLab Granty # The commit message #16 will be skipped: # Update Makefile # # Add ADIMLab Granty # The commit message #17 will be skipped: # Update boards.h # The commit message #18 will be skipped: # Update Makefile
* # This is a combination of 18 commits. # This is the 1st commit message: Add Support for ADIMLab Granty # The commit message dot-bob#2 will be skipped: # Update Configuration.h # The commit message dot-bob#3 will be skipped: # Add files via upload # # Add Support for ADIMLab Granty # The commit message dot-bob#4 will be skipped: # Create Configuration.h # The commit message dot-bob#5 will be skipped: # Delete Configuration.h # The commit message dot-bob#6 will be skipped: # Create Test.h # The commit message dot-bob#7 will be skipped: # Add files via upload # The commit message dot-bob#8 will be skipped: # Delete Test.h # The commit message dot-bob#9 will be skipped: # Delete Configuration.h # The commit message dot-bob#10 will be skipped: # Delete Configuration_adv.h # The commit message dot-bob#11 will be skipped: # Add files via upload # # Add ADIMLab Pins # The commit message dot-bob#12 will be skipped: # Add files via upload # # Add Bootscreen # The commit message #13 will be skipped: # Update Configuration.h # # Add Bootscreen # The commit message #14 will be skipped: # Update pins.h # # Add ADIMLab Board # The commit message #15 will be skipped: # Update boards.h # # Add ADIMLab Granty # The commit message #16 will be skipped: # Update Makefile # # Add ADIMLab Granty # The commit message #17 will be skipped: # Update boards.h # The commit message #18 will be skipped: # Update Makefile * Add Support for ADIMLab Granty * Optimize bootscreen * Update Makefile Updated Description * Update boards.h Updated Description * Update pins_HJC2560C_REV2.h Updated Description * Update Configuration.h Added Author + Custom_Machine_Name * Create _Bootscreen.h Add Bootscreen * Add files via upload Add ADIMLab Granty v1 * Update boards.h Add ADIMLab Granty v1 * Update Makefile Add ADIMLab Granty v1 * Update pins_HJC2560C_REV2.h * Consolidate Granty configs * config updates
Hi dot-bob.
First, thanks for all your hard work and contributions to the MMU/D6 community!
I just received my MMU a few days ago and wanted to clarify a few things.
Looks like this is the latest repo for MMU/D6 marlin ports?
https://github.com/dot-bob/Marlin-Duplicator-6/
There is no MMU specific branch here which makes me wonder if there any actual difference between the MMU and D6 branches in the previous repo other than the CUSTOM_MACHINE_NAME in the configuration file?
What repo/branch do you recommend for someone generally new to MMU / 3D printing, but hardware/software engineering capable kind of person?
Thanks in advance for any info you can provide!
The text was updated successfully, but these errors were encountered: