Offset on height map

3DCloner

@fcwilt I used the assistant, but the problem persists, it seems that it has a tendency for the right side to be tight and the left side loose, both with the table level, with it not level, with the right side higher or the left higher, whatever, always the same result.

3DCloner

@fcwilt For sure!

In relation to the value it is correct, but it may be that I have inverted the meaning. But I've been trying a lot of things all day, and inverting the Z-Probe offsets was one of them.

In relation to the G30 S-1. I made a macro with some dots, follow the code.

G28

G1 X35 Y100 Z15
G30 S-1
G1 X85 Y100 Z15
G30 S-1
G1 X170 Y100 Z15
G30 S-1
G1 X255 Y100 Z15
G30 S-1
G1 X320 Y100 Z15
G30 S-1

G1 X35 Y200 Z15
G30 S-1
G1 X85 Y200 Z15
G30 S-1
G1 X170 Y200 Z15
G30 S-1
G1 X255 Y200 Z15
G30 S-1
G1 X320 Y200 Z15
G30 S-1

this was the result (the height map was loaded)

3DCloner

@phaedrux When I see the symptoms, it seems that the spindle pitch is wrong when it comes to X compensation, because the Y axis is right and the Z steps per mm are right, I even saw it on the dial indicator. Besides the direction of rotation of the spindle is right, when it has to lower it it lowers, but not enough, the same thing when it needs to lower (on the X axis).

Phaedrux

G31 P500 X-34.3 Y31 Z2.195

Based on your photo your G31 looks more or less correct.

Do you happen to have a M376 command anywhere in your startup gcode or elsewhere to configure some compensation taper?

https://duet3d.dozuki.com/Wiki/M376

3DCloner

@phaedrux Good morning, getting back to work! Good week to you!
About the G31 I even tried another configuration, as can be seen in config.g, but nothing changed.
About the M376, I don't use it, why?

3DCloner

@phaedrux I'm taking a look at the Gcode G30 and its H parameter, it could be a solution, but I don't quite understand how I use it, could you help me?

Phaedrux

@3dcloner said in Offset on height map:

M558 P9 C"^zprobe.in" H4 F240 T19800

I don't think G30 H is the solution. It seems as though your trigger heights are not consistent. I suggest modifying your M558 to try and improve it.

Try this line
M558 P9 C"^zprobe.in" H3 F60 T12000 A10 R0.2 S0.003 B0

In your homeall you can speed up the homing process by using a faster speed for the first homing and then slow down for a repeat. like this

M558 F240 A1
G30
M558 F60 A10
G30

fcwilt

@phaedrux said in Offset on height map:

In your homeall you can speed up the homing process by using a faster speed for the first homing and then slow down for a repeat. like this

M558 F240 A1
G30
M558 F60 A10
G30

Why that approach instead of Faaa:bbb?

Thanks.

Frederick

Phaedrux

@fcwilt Habit.

3DCloner

@phaedrux @fcwilt Got it, I can adopt this homing with two speeds, it might be useful since the machine is quite big, etc.

But I have good news, our team has been working here since Friday trying to find the problem and we did it. The y-axis rods were slightly bent, which made the X-axis twist,
which consequently changed the distance between the nozzle and the Z-Probe along the X axis. Before, we had no problems with this slight misalignment because we didn't use a Z-Probe, and that's why it took us a while to check this alignment.

Finally, thank you very much for your help and attention, I learned several new things in the process. Case closed.