Bed leveling in sliced G-code instead of firmware?
Is there some easy method to do the bed leveling based on the sliced model instead of probing the whole bed in the firmware? It feels unnecessary to probe the whole bed when you're printing a small model, say 2cm * 2cm, in the center of the bed, or even 10cm * 10cm. For example, if I'm printing a 10cm * 10cm model, wouldn't it be better and faster to do a 3 * 3 probe around that 10cm * 10cm instead of doing a 3 * 3 or 6 * 6 probe on the whole bed?
Sure I could add the GCode in the model myself and disable it in the printer, but is there, or could there be, an option in PrusaSlicer that does this for me? If not, would there be any issues or downsides with such an option?
(I tried search the forum, but I have an issue that I only can see the first page of results. When I click to the see the next page I'm returned to the main forum page.)
RE: Bed leveling in sliced G-code instead of firmware?
A lot depends upon the printer, Mk4 and XL Printers both reduce the sensed area, based on model geometry.
You don't seem to indicate which printer you have.
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Bed leveling in sliced G-code instead of firmware?
You don't seem to indicate which printer you have.
Yes, I should I have mentioned I have the MK3S.
I wrongly assumed they all behave the same way. Why isn't this done in the slicing process instead of in the device, if that's what the MK4 and XL do? I'm sure there's a reason, but what?
RE: Bed leveling in sliced G-code instead of firmware?
the mk4 and XL have 32 bit processors, with relatively speaking loads of memory
the mk3 has a much older 8 bit processor. the 8 bit processor has very little spare memory, for extra features.
I suspect prusa cannot get the variable size mesh bed levelling into the available space
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Bed leveling in sliced G-code instead of firmware?
What I'm asking is why are the bed leveling commands not generated in PrusaSlicer (instead of in the firmware)? That would make no difference to what processor is used in the controller.
RE: Bed leveling in sliced G-code instead of firmware?
That is a question that the Developers would need to answer.
As users, we can only guess.
I suspect Prusa decided to put Mesh Bed levelling, into firmware, so that you can use any slicer you wish to take advantage of.
As I said, this is a total guess.
Maybe someone else knows better
regards Joan
I try to make safe suggestions,You should understand the context and ensure you are happy that they are safe before attempting to apply my suggestions, what you do, is YOUR responsibility. Location Halifax UK
RE: Bed leveling in sliced G-code instead of firmware?
I suspect Prusa decided to put Mesh Bed levelling, into firmware, so that you can use any slicer you wish to take advantage of.
I thought about this too, that that could be a reason, but one doesn't exclude the other. You could disable it in the printer and enable it in the slicer, or vice versa, depending on your preferences.
RE: Bed leveling in sliced G-code instead of firmware?
I thought I saw somewhere here that someone had managed to get the MK4 probe function to work with the MK3s.