Use bed_mesh bounds instead of hardcoded 0,0 for purge positioning

[loss-and-quick]

Use actual bed mesh min coordinates instead of hardcoded 0,0 to properly
position purge lines on printers with centered bed origins.

[danielschwab]

I tried this with a test print of a square starting in the front left corner (x=10, y=10) and the purge line was connected to my print object. So it's quite working as expected.

[loss-and-quick]

I tried this with a test print of a square starting in the front left corner (x=10, y=10) and the purge line was connected to my print object. So it's quite working as expected.

Fixed in the latest commit, thanks for testing!

[danielschwab]

It still is connected and I guess it is because of the width of the purge line. The test objects starts at x=10 and this is the log of the purge line:

// KAMP purge starting at 10.0, 21.0 and purging 30.0mm of filament, requested flow rate is 15.0mm3/s.

So for the script it is not overlapping but in reality it is.

[loss-and-quick]

It still is connected and I guess it is because of the width of the purge line. The test objects starts at x=10 and this is the log of the purge line:

// KAMP purge starting at 10.0, 21.0 and purging 30.0mm of filament, requested flow rate is 15.0mm3/s.

So for the script it is not overlapping but in reality it is.

Is this a problem of pr?

[danielschwab]

You're right. It's not a problem of your PR (So the last change is unnecessary). In my case purge_x_origin and purge_x_origin are both zero and this is not handled nicely in the original script.

[loss-and-quick]

You're right. It's not a problem of your PR (So the last change is unnecessary). In my case purge_x_origin and purge_x_origin are both zero and this is not handled nicely in the original script.

In my opinion, for now it is better to setup kamp and purge through orca slicer, because klipper doesn't know what type of filament, diameter of nozzle currently used