Ok, Thanks very much.

Now I can work setting up the 1st layer and so on.

Oh yes, retract on layer change. That would do it.

Now running the printer with the new belt without issues (so far).

The testprints came out perfect now 😄
Just how I am used to see with a Duet powered Printer.
Thank you for being here in the Forum 🙂

That's with everything put back. Going to tune it all in properly and get a mesh compensation run once I have it a bit tighter

Thanks. I'll bare the numbering in mind!

That worked thanks number40!

Nevermind, I see the behavior of M104/M109 was changed to do that in the latest firmware.

@number40fan:

Get the nozzle to grip a piece of paper.

Run G92 Z0
G1 Z5
G30 S-1
G1 Z5
G30 S-1
G1 Z5
G30 S-1

After running the above a few times, make sure you get consistent numbers on the reply from running G30 S-1.

https://preview.ibb.co/geASRv/TgttPSy.png

That will be your number you put in here.

https://preview.ibb.co/dE3aDa/Y3uSKMV.png

Thanks for help. It working good now.
I'll make chinese version document all i can do.

That does look better. Good to see results.

Thanks for tips 🙂 So if the limit switches trigger 20mm past the bed in X and Y there is no way to specify the "real" limits on both the high and low ends? My X triggers on negative and my Y triggers on the positive end. I guess it's easy enough to restrict in the slicer. That or fix the mechanical trigger points.

Now my bed thermistor in the heat pad is open circuit, but I'll get printing one of these days 😞

The firmware will attempt to put the probe (not the nozzle) at the XY offsets you specify, taking into account the probe offsets that you declare in the G31 command. The offsets are the X and Y distances from the nozzle to the probe, not the other way around.

Oh, i got it. Off course this is how it should be…. sometimes I'm so....... Thanks alot!

Starting a print and then setting the the threshold temporarily to a voltage higher than your PSU voltage is a way of triggering the power down functionality, to check that it is working.

ok thanks for your help
have a great day

ok
Thanks you

@bananas:

Solved!

I had changed the original H-Bar ends from a 4 wheel version to a 3 wheel version when building the D-Bot. The 3 wheel version moved well and there was no play at all. What I suspect happened was the H-Bar was twisting or flexing slightly as the belts applied force at either end.

Going back to the 4 wheel version solved the problem.

Thanks everyone for your help.

Can I ask which 3 wheel z carriage mod you were using?

Thanks. After PID Tuning a second time and setting a larger D value, the fluctuation has been fixed.

You can also use tpre_.g and tpost_.g (and tfree_.g) macros (where _ is the num of the tool) to execute G-Codes before a tool is selected, after it is selected, and when it is released.

I think you are right. I tried moving the leadscrew by hand and only got 20% of the movement on the bed. Likely the bed resists torque around the x axis enough that the motor mounts (which are printed) deflects more than the bed rotates.

Thanks alot deckingman. Problem solved. I passed over that page , I'm sorry for this. So the thread can be closed as solved so others can learn.

Thanks alot!