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

[beerdart]

Quick questions.
1. When I run G29 does the topo get storied for the next prints?
2. How do I change the number of probe points I know there are several probe maps in the config but how do I select?

Thanks

[Roxy]

Quick questions.
1. When I run G29 does the topo get storied for the next prints?
2. How do I change the number of probe points I know there are several probe maps in the config but how do I select?

Thanks

If you get the Enhanced G29 stuff going... You can go look in the 'Firmware Enhancements for Marlin' folder for the M499 feature. That will store the bed level correction matrix and allow you to avoid doing G29's until things change enough that it makes sense to do it again.

[pichuete]

ok i found my issue i was missing the Board.h File . any particular reason why this file is not included? i copied from the firmware im currently using..

hi,

im trying to upload the firmware to my rambo board and im getting this error, i already changed the motheboard to 301 . changed my ABL, servo settings and E-steps .. but for some reason im getting this error . any ideas what im doing wrong? im currently running the latest marlin firmware but im having some trouble with extrution, temperature and inconsistency .

This report would have more information with
"Show verbose output during compilation"
enabled in File > Preferences.
Arduino: 1.0.6 (Windows NT (unknown)), Board: "Arduino Mega 2560 or Mega ADK"
In file included from /Marlin.h:23,
from BlinkM.cpp:5:
/pins.h:4:20: error: boards.h: No such file or directory
/pins.h:6:8: error: missing binary operator before token "("
/pins.h:2523:7: error: missing binary operator before token "("
/pins.h:2625:7: error: missing binary operator before token "("
/pins.h:2736:7: error: missing binary operator before token "("
/pins.h:2831:7: error: missing binary operator before token "("
/pins.h:2931:2: error: #error Unknown MOTHERBOARD value in configuration.h

[tsteever]

So excited to find this thread. Thanks Roxy for pointing it out to me. So Far I have been trying to get the firmware I downloaded from this post up and running and I had a few issues. Particularly the weird G28 behavior where is ends its movements above the bed.

My question is which should I be using? The link in the first post of this thread, or the other one. This seems to be more "maker farm" specific. How do I know which it the correct, most current "fixed" firmware to be using? Does the link on the first page always get updated with the preferred firmware?

How come this thread is not linked and stickied in the MakerFarm section?

[Roxy]

ok i found my issue i was missing the Board.h File . any particular reason why this file is not included? i copied from the firmware im currently using..

...

Arduino: 1.0.6 (Windows NT (unknown)), Board: "Arduino Mega 2560 or Mega ADK"
In file included from /Marlin.h:23,
from BlinkM.cpp:5:
/pins.h:4:20: error: boards.h: No such file or directory
/pins.h:6:8: error: missing binary operator before token "("
/pins.h:2523:7: error: missing binary operator before token "("

It is almost as if you did not specify the correct board in the 'Tools' section of Arduino. But any Marlin archive you grab should have a complete set of files that will compile if you have your environment setup correctly.

[Roxy]

So excited to find this thread. Thanks Roxy for pointing it out to me. So Far I have been trying to get the firmware I downloaded from this post up and running and I had a few issues. Particularly the weird G28 behavior where is ends its movements above the bed.

That is a feature. And in fact, that may be in the main Erik Zalm branch of the tree now. The reason that is a 'feature' is because some people have Z Probes that rotate when they disengage and actually go lower than what the Z_PROBE_OFFSET is specified at. You want to have some clearance so the probes don't strike the bed when engaging or disengaging.

My question is which should I be using? The link in the first post of this thread, or the other one. This seems to be more "maker farm" specific. How do I know which it the correct, most current "fixed" firmware to be using? Does the link on the first page always get updated with the preferred firmware?

MakerFarm had a few things that needed to be smoothed over and that was the reason for the thread. But the smoothed over version for MakerFarm also included the Enhanced G29. MakerFarm is a very generic RepRap printer. If you take the MakerFarm fork and put your configuration.h settings in it, you will be at a very similar place to if you took the most recent Erik Zalm Marlin fork, added your configuration.h settings and then did the work to add the Enhanced G29 code. Going with the MakerFarm version is more straight forward.

How come this thread is not linked and stickied in the MakerFarm section?

Perhaps it should be... I don't know how many MakerFarm people are using DACB's Marlin fork. If it is enough, maybe we should stickie the thread???

[hernejj]

I am using it, just not with ABL. Works great.

[voodoo28]

The link on the first page is broken.. (Feature: Added a modified version of the dynamic ABL probe area code from here: https://github.com/ErikZalm/Marlin/pull/1022)

[tsteever]

I tried to follow the link you posted and it leads no where. As I stated, I downloaded the firmware from the link I posted my post above (#204) and have it limping along. It is the Erikzalm firmware. What I am wondering is what would have been the better firmware to spend my time on.

It is my understanding that the ErikZalm firmware is a generic Marlin Firmware while the BeckDac is more in line with the Makerfarm printers.

Or, in rereading the first post, am I misunderunderstanding it? Does the https://github.com/beckdac/Marlin linked firmware include the dynamic ABL probe area?

[tsteever]

Whew! Just read all that. So, the question I have is then how to get the dynamic ABL scripts into Slic3r or Cura.