M564 doesn't seem to apply when creating height map
-
Hi,
To create the height map I desire, the print head has to move outside of normal axis limits.
I tried to allow for this in the macro that creates the height map by using M564 S0.
It didn't work.
I had to use M208 to change the axis limits.
It seems odd that M564 didn't work.
Any ideas why?
Thanks.
Frederick
-
Hmm, that's an interesting use case. I'm not sure if that was ever considered for M564. The heightmap is following the limits set by M208, M557 and G31.
Since you're doing it all in a macro already I think temporarily modifying M208 is probably the way to go.
Some people use M564 as a matter of course in their config.g and if it was allowed to override limits during G29 I think people might have some unexpected crashes. But that's not really here nor there.
-
@Phaedrux said in M564 doesn't seem to apply when creating height map:
Since you're doing it all in a macro already I think temporarily modifying M208 is probably the way to go.
Well my thinking was that if M564 worked then the macro needed no knowledge of the axis min/max values.
It works now, with M208, but I will need to be sure they stay in sync with the M208 in config.g if I were to make changes in config.g.
Frederick
Printers: A FT-5 with the 713 upgrade bits, a custom MarkForged style, a small Utilmaker style, a small CoreXY from kit and a E3D MS/TC setup. Various hotends. Using Duets (2 and 3) running 3.4.6
-
I'll move this to the wishlist section for consideration.
-
@fcwilt guessing you've thought of this, but you could make a macro for your axis limits then call that from config. You can then recall it from the end of your heightmap creation macro to reset everything. That way you only have one source for the setting (but have to remember to call it...)
I've started doing this for motor settings etc as I like to change them during homing. Eventually I can see not having any configuration in my config.g file!Home-built CoreXY, Duet Wifi, Chimera direct drive, 2x BMG, 300x300x300 build volume
i3 clone with a bunch of mods -
@engikeneer said in M564 doesn't seem to apply when creating height map:
@fcwilt guessing you've thought of this, but you could make a macro for your axis limits then call that from config. You can then recall it from the end of your heightmap creation macro to reset everything. That way you only have one source for the setting (but have to remember to call it...)
I've started doing this for motor settings etc as I like to change them during homing. Eventually I can see not having any configuration in my config.g file!That is an idea worth considering. Thanks.
Frederick
-
@engikeneer said in M564 doesn't seem to apply when creating height map:
Eventually I can see not having any configuration in my config.g file!
This is one way to go, but it does have downsides if taken to the extreme in the form of reduced editability. Trying to track down something through multiple files can become tedious. See the Voron config files on github as an example, or the M3D printer configs.
-
This is somewhat related to this topic.
I was trying out the bed leveling assistant feature of the firmware.
I entered the location of the adjustment screws, I created the bed.g with the appropriate probing.
It worked just fine.
The ODD thing was that I specified probe points that required the nozzle to go outside the Y axis min limit.
But with G32 I didn't have to use M208 to allow that to happen. It happily probed the points I specified moving past the Y min limit as needed.
I double checked after it was done to see if the axis limits were still in effect and they were.
Very curious. It would seem that if G32 "understands" that the axis limits can be temporarily extended to allow for the probe offsets than G29, when creating a height map, could do the same.
Frederick
