Cartesian (Prusa i3 steel) bed sensing ??

Phil Maddox

apologies if this has been asked before
I have a cartesian printer ( Prusa i3 steel)
I have got everything up and running including the DC42 IR probe …All good

My question is this
I have implemented the Prusa i3 config files that came on the on the SD card. I noted that the main "config" file contained probe coordinates.
Do i need a bed,g file as well ??
Do i also invoke bed sensing by using the G32 command. ( that appears to need/use a bed.g file )

All docs i've read seem to refer to Delta's and the online config tool is for deltas as well.
all a bit confusing
Looking for clarity ?

Thanks in advance

Phil

deckingman

Yes, if you want to perform bed plane compensation. You run G32 to probe the bed which invokes the bed.g file to find the coordinates of where on the bed to probe. Usually, on a cartesian one would probe the 4 corners.

You could try the configurator tool here https://configurator.reprapfirmware.org/ which will generate all the necessary files for you.

HTH

Ian

Phil Maddox

Thank you Ian
I used the G32 command and my bed was probed in the correct locations and my print went very well.
I still don't have a bed.g file thou ( as per the Prusa i3 config on the SD card that came with my board) I copied the files the the sys root, configured them to suit my machine and all is well. Im just not sure if i need the bed'g file or not. I guess that is my question.

Thanks again

dc42

G32 will run sys/bed.g if it is found. If not then it will use the probe coordinates defined by the M557 commands in config.g, if you have them.

Phil Maddox

Great thanks. Is there any advantage to having a bed.g file ??
I have the Duet installed on my main printer that i use for long prints and plan on probing the bed prior to each print.

deckingman

@Phil:

Great thanks. Is there any advantage to having a bed.g file ??
I have the Duet installed on my main printer that i use for long prints and plan on probing the bed prior to each print.

I don't think it matters much but if you edit config.g file, you have to restart the Duet for the changes to make effect whilst bed.g is effectively a macro. So you can alter the bed.g file without having to reboot the duet. Having the coordinates in a separate bed.g file also makes them a bit easier to find, rather than scrolling through the entire config.g file. Having said all that, changing the probe coordinates once they have been set is rarely, if ever done. Just my twopence worth…....