Results 241 to 250 of 396
-
12-08-2015, 02:16 PM #241
- Join Date
- Jan 2015
- Posts
- 32
Alternatively, is it worth a shot to cherry pick lines from the version at your link and add them to my existing version of Marlin? If so, which lines?
-
12-08-2015, 02:25 PM #242
- Join Date
- Jan 2015
- Posts
- 32
Thank you Roxy. We cross posted, I just read your last response. I was hoping I could just change a few lines, but it sounds like it's better to use the latest version and copy over the #define values. I'll give it shot.
Last edited by inventabuild; 12-08-2015 at 02:32 PM.
-
12-13-2015, 06:34 PM #243
- Join Date
- Jan 2015
- Posts
- 32
Hello Roxy, it worked like a charm. Thank you.
One last sticking point though. I also tried working with the AUTO_BED_LEVELING_GRID and whether I put in a value of 2 or 5 for #define AUTO_BED_LEVELING_GRID_POINTS Marlin always probes 9 points. How do I get Marlin to vary the number of probe points, for example how do I get Marlin to probe only the four corners?
-
12-13-2015, 09:52 PM #244
Snicker... Snicker... You need to look at the code! That #define sets how the firmware is built and allocates storage for what it is going to do. Setting it to 5 allows up to a 5x5 grid to be probed. But usually, people don't want to do that. So the default (if you don't tell it how many points to do) is 3. Even a 3x3 grid takes a bit of time and a lot of people don't want to wait that long. Just because you allocate the storage to handle a 5x5 grid, it won't do that unless you tell it to do that. Give it a G29 n 5 T and you will get the full detail grid printed for what your bed looks like.
-
12-13-2015, 10:52 PM #245
- Join Date
- Jan 2015
- Posts
- 32
Oh, so if I give it a G29 n 3 T will it calculate the surface using 9 points and if I give it a G29 n 5 T will it calculate the surface using 25 points.
Also, how does Marlin determine what the surface looks like. Does it use all the points I tell it to use with G29 n ? T to define a single least squares plane or does it break up the surface into many different planes? I thought I read about some firmware out there doing this or trying to do this.
-
12-14-2015, 08:50 AM #246
Yes. That is correct. But you can only go as high as you have allocated storage using that #define.
In the Grid Based Bed Leveling, it will find the mean (average) of all the points and subtract that off of each point when doing the Topography report. That lets you easily see what is too high or too low and by how much. Independent of that, it will feed all the sampled points into a Least Square Fit algorithm to find the plane that most closely matches those points. The Mesh based leveling will do a bi-linear fit as it moves the nozzle from cell to cell. Soon, the Mesh based will have automatic sampling of the bed and it is possible the Delta's will be using the same bed leveling compensation that the Cartesian Mesh users are doing.
-
12-14-2015, 10:59 PM #247
- Join Date
- Jan 2015
- Posts
- 32
Hello Roxy,
When I comment out the AUTO_BED_LEVELING_GRID and try to upload the 3 point leveling to my TAZ I'm getting the following error message in Marlin_main.cpp $:
'retract_flag'was not declared in this scope
Please let me know how to declare this. Thank you.
-
12-15-2015, 12:37 PM #248
Can you post your Marlin_main.cpp file? I'll take a look at it.
-
12-15-2015, 02:45 PM #249
- Join Date
- Jan 2015
- Posts
- 32
-
12-15-2015, 06:08 PM #250
- Join Date
- Jan 2015
- Posts
- 32
My 3D Norn Emissary print
09-13-2024, 02:28 AM in 3D Printing Gallery