I don't know if this means that the M557 must be the entire size of the bed and therefore provoke the skipped points for it to get entered into the heightmap as 0 and cause it to extrapolate, or if it will automatically extrapolate any bed area outside of the M557 defined area.
I used to have my home call in my config.g but I was advised to not do that. So I have removed it. I just put the G30 and G29 in my starting script for my slicer. I also usually home at the start of my print files.
I was able to write a macro to actually use the stall detection to automatically calculate the probe trigger height. So I may change how I do a few things now too. But I literally figured that out last night so I haven’t really had a chance to figure out how I’ll implement it.
@dc42 Thanks for the reply, how would i designate that pin as the output in the configuration files. Like i said earlier im used to smoothieware where i have one config file where i specify the pin output and whether its pwm or not.
For maximum flexibility in allocating pins, I suggest you use RepRapFirmware 3.01. This is close to release now and the release candidate is stable.