Traveling Z offset

[jstevewhite]

@dc42

Is this intentional behavior? I ask because it seems to leave out anyone who might manually configure multiple tools. I see why mine is working (because i tested touch-off G10 settings for our eventual implementation of the E3D toolchanger on RailCore 2), and it's worked ever since (because it was already there, I suppose).

So in order to make this work manually, you have to manually enter it into config-override.g once, reboot, and then changes will be written?

[cts5191]

Bump (curious to see reply from dc42)

[dc42]

@jstevewhite said in Traveling Z offset:

@dc42

Is this intentional behavior? I ask because it seems to leave out anyone who might manually configure multiple tools. I see why mine is working (because i tested touch-off G10 settings for our eventual implementation of the E3D toolchanger on RailCore 2), and it's worked ever since (because it was already there, I suppose).

So in order to make this work manually, you have to manually enter it into config-override.g once, reboot, and then changes will be written?

The behaviour is designed to give you this choice:

1. Measure your tool offsets and put them in G10 commands in config.g. Check that you have no G10 commands in config-override.g. This is the recommended solution if you do not manually change tools very often.

2. Measure all your tool offsets by probing, and use M500 to write the to config-override.g.

If you prefer to hold all the tool offsets in config-override.g even if you didn't measure them by probing, then you can add G10 commands manually to config-override.g as you suggest, so that M500 always rewrites them.

[jstevewhite]

@dc42

Ah, ok, that makes sense. Add it to the config-override.g manually. I just wanted to make sure that was an appropriate way to achieve the behavior I'm looking for.

Thanks!