Is it possible to get the data from the auto bed level and put it into the startup g-code, so I don't have to auto level at the start of every print?
I'm wondering because I'm having a few issues when trying to print the first layer of any print, mostly around the filament oozing from the nozzle, even when I've retracted the filament slightly. The filament oozes a bit, then the auto level basically dabs the filament onto the board which squidges it back onto the nozzle. I'm having to clean this on the fly as the bed level is happening or else the first layer never prints well enough to continue with a print. I think this problem is worse with the new aluminium headed bed because the induction sensor doesn't pick it up from so far away, so my Z offset is only 0.2, which means I can only have 0.2mm of filament (currently PLA+) oozing before the problem starts.
Tips on tacklign the oozing also appreciated, even if I can fix that I'd still like to avoid the wait for the auto level before every print if this can be saved. I've tried running M500 but I presume the Proforge control board doesn't have any EEPROM to save to?
You can enable EEPROM for settings by modifying configuration.h
Find and uncomment the following line
>#define EEPROM_SETTINGS // Enable for M500 and M501 commands
Once that's done, and you have autoleveled you can M500 to save the offsets for future use so you don't need to do it every time if you have no changes in your print environment.
If you don't want to enable eeprom, you could just run a G29 autolevel from console, then M503 and find the settings in there. I can't remember offhand what they are, but there should be a cluster of 9/12 rather similar lines with very small Z offset differences.
Just keep in mind that once eeprom is enabled, you need to either modify via console and M500 to make changes to pretty much everything, or do an M502 to M500 to load defaults from the config files and resave them to the eeprom after you reflash or you'll get some wonky issues - this does mean you'll have to put in all your non-config-file stored changes again though.
+1
I have this same issue, I have to stalk it with a scalpel / pair of pliers to grab the filament ooze prior to the initial line. If I don't, I have to restart the print as it's likely to ruin the first layer.