Marlin firmware fork for MakerFarm i3v w/ auto bed level & Roxy's enhancements

[printbus]

...Can you post them here? How about we start a whole new thread for this purpose? Maybe call it something like Marlin RC-7 on MakerFarm ? ...

There was a short "how should we go about this" discussion some time ago that led to no clear scheme, and the problem is worse now than ever. All need to remember that the MakerFarm product line is far more complex than it used to be. Long gone are the days where a single set of files works for everyone with a MakerFarm printer, at least not without some adjustments.

Don't get me wrong - I'm all about sharing lessons learned and helping out the next user. As a minimum, things like thread posts, comments, descriptions, filenames, and foldernames should probably clarify what the content applies to. Even without factoring user modifications, the type of electronics (RAMPS, RUMBA, RAMBO), type of LCD (character vs graphic), type of extruder (Greg's Wade, bulldog, Pegasus, Titan single vs dual), and bed compensation scheme are examples of ways MakerFarm printers can differ as far as a firmware build and configuration parameters. Many users can readily deal with tailoring standard files for their unique configuration, but history has shown that some, especially new users still somewhat unfamiliar with the firmware and lacking confidence in what they are doing, will struggle in doing this. If that is considered somehow from the beginning, maybe it'll be easier for all in the long-run.

[tsteever]

I picture myself the person you are talking about here! I know there is a new firmware out but have not adopted due to the reasons you mention. First, I am not 100% sure what needs to be done to make the RC-7 work on my machine.

Perhaps a checklist of things that need to be changed in the RC-7 to fit your machine could be made? That would perhaps give the user the confidence to at least try it out.

With that in mind, what changes need to be made?
*change esteps to fit your chassis, X,Y,Z,E
*Activate ABL if using
-define pins in pins.h is using ABS
-Set probe extend retract degrees
-set probe points
-define offsets
*define motherboard
*Define temp probe
*adjust PIDs


What else would a user need to change in RC-7 to fit their machine? Also, where can one find the current stable RC-7 file for use? Link?

There was a short "how should we go about this" discussion some time ago that led to no clear scheme, and the problem is worse now than ever. All need to remember that the MakerFarm product line is far more complex than it used to be. Long gone are the days where a single set of files works for everyone with a MakerFarm printer, at least not without some adjustments.

Don't get me wrong - I'm all about sharing lessons learned and helping out the next user. As a minimum, things like thread posts, comments, descriptions, filenames, and foldernames should probably clarify what the content applies to. Even without factoring user modifications, the type of electronics (RAMPS, RUMBA, RAMBO), type of LCD (character vs graphic), type of extruder (Greg's Wade, bulldog, Pegasus, Titan single vs dual), and bed compensation scheme are examples of ways MakerFarm printers can differ as far as a firmware build and configuration parameters. Many users can readily deal with tailoring standard files for their unique configuration, but history has shown that some, especially new users still somewhat unfamiliar with the firmware and lacking confidence in what they are doing, will struggle in doing this. If that is considered somehow from the beginning, maybe it'll be easier for all in the long-run.

[Roxy]

There was a short "how should we go about this" discussion some time ago that led to no clear scheme, and the problem is worse now than ever. All need to remember that the MakerFarm product line is far more complex than it used to be. Long gone are the days where a single set of files works for everyone with a MakerFarm printer, at least not without some adjustments.

At worst case, we could have a MakerFarm folder with 3 or 4 different models in it. And a Configuration.h file for each flavor. That would be OK and still help people.