Results 71 to 80 of 156
Thread: Rumba and Auto-Bed level
-
03-02-2015, 10:00 AM #71
- Join Date
- Feb 2015
- Posts
- 371
Thanks! I think the most confusing in all this has been the info I find all over the place on this. I can't keep it all straight! My Printer with enhanced firmware seems to work, just not the G28. I guess I could always run a G29 command after it but sometimes I am only printing a very small part and don't need the G29. Oh well, got some reading to do!
-
03-02-2015, 10:51 AM #72
- Join Date
- Feb 2015
- Posts
- 371
Looking forward to following the thread that Roxy linked to. It can be found here. Looks like a good place that i should have found before all this!
Anyways, previously I had been reading the ABL and Enhanced Firmware thread in the firmware section and I came to this post. I am going to try and implement this tweak into my code to see if that helps. Basically it is adding another value to the G28 command which is what I thought may be missing. Hopefully it will work and Roxy has a chance to get the firmware sorted and streamlined. I think my confusion came from the so many different versions floating around. Would be nice to have a sticky "look here" thread.
-
03-02-2015, 06:21 PM #73
The more I think about it, the behavior of the G28 with Auto Bed Leveling is not a bug. The purpose of the G28 is to Home the axis. It does that. At the very end of the G29 the code compensates for the Z_PROBE_OFFSET. It would be very straight forward to make the G28 do that also.
-
03-02-2015, 08:56 PM #74
- Join Date
- Feb 2015
- Posts
- 371
Found this post from Abu in the other thread and it seems to fix the issue. Not sure if it is a band aid or not but I can get the nozzle on the bed after a g28 now.
Pasted from here...
Do a G28, then a G1 Z0. Find out at what distance above the bed the nozzle stops. Let's call that number X.
Look for this section in Marlin_main:
PHP Code:if(code_seen(axis_codes[Z_AXIS])) {
if(code_value_long() != 0) {
current_position[Z_AXIS]=code_value()+add_homing[2];
}
}
#ifdef ENABLE_AUTO_BED_LEVELING
if((home_all_axis) || (code_seen(axis_codes[Z_AXIS]))) {
current_position[Z_AXIS] += zprobe_zoffset; //Add Z_Probe offset (the distance is negative)
}
#endif
Change the "+= zprobe_zoffset;" to "+= zprobe_zoffset+X;" inputting the number you found earlier for X. On my printer, it was 4.
Last edited by tsteever; 03-02-2015 at 09:37 PM.
-
03-03-2015, 07:07 AM #75
Yes, this looks correct. This should get the G28 and the G29 synchronized in where they think the nozzle is relative to the bed. One small caution: If the bed is tilted at a noticeable angle, the nozzle will be at a different height than the probe because the probe is offset from the nozzle. The G29 corrects this 'error'. The G28 does not have the bed angle information and it can't do the more accurate correction.
-
03-03-2015, 08:33 AM #76
- Join Date
- Feb 2015
- Posts
- 371
Good to know! I'd really only be doing the solo G28 command on small prints that wouldn't need the ABL (Thin wall calibrations, etc...). I look forward to the dynamic build envelope settings being implemented if possible. Have the printer probe only the areas included in the Skirt would be a valuable addition to the feature. For now though it does appear to be working. This is with the Erik firmware not the beckdac firmware. I will see if I can't move these settings over to that as well.
What should be my next step? I know that there are some wondering/waiting to see if it was working. Should I just post my marlin folder in a zip?
-
03-03-2015, 10:53 AM #77
- Join Date
- Feb 2015
- Posts
- 211
-
03-03-2015, 11:37 AM #78
- Join Date
- Nov 2014
- Posts
- 522
marlin firmware is an ever evolving piece of software, with bug fixes and features being added all the time...
colin's firmware is like a snapshot in time, in the time since he made that copy of the firmware, many, many bugs have been fixed and features have been added not all of which will effect you or others but marlin is ever evolving into better and stronger code with features being added and refined daily
-
03-04-2015, 11:26 AM #79
I'm not sure what I think about the dynamic build envelope. I actually wrote a piece of C code to process the GCode and set the parameters. But I think we all agree it would be best to just have one standard script to do this that everybody uses. The big reason I'm not sure what to think about this topic is this:
Unless you have big imperfections in a few locations on your print bed, aren't you better off measuring the whole thing where you can get more accurate numbers that are spread out? Suppose you are only printing something with a 1" square foot print. Can you accurately measure a bunch of points withing that area to set the bed angle? Or would you be better off going way out to the edges to measure your points so you can set the bed level correction matrix more accurately?
-
03-04-2015, 12:29 PM #80
- Join Date
- Feb 2015
- Posts
- 371
That I don't know. For the small stuff I have just been turning off the ABL and just using G28 in my custom code. I need to get the BeckDac working and my fear was the dynamic ABL stuff might cause troubles if I wasn't using the slic3r part.
Can I just load this firmware and ignore the dynamic ABL stuff and assume that it will work?
Ender 3 Neo - Jam Problem
Today, 10:12 AM in Tips, Tricks and Tech Help