Topics created by jp.douarvil 0

My profuse apologies for:

my (very) late answer digging up this old topic (Halloween trick or treat ?!)

but my answer is still relevant (based on the code base of the RRF 3.5.0 rc1 and 3.4.6).

@dc42 said in G30: unexpected probe dive motion range:

If you set the dive height to some value H [...] the code starts the dive at (trigger_height + H) and ends it if the probe is not triggered first at (trigger_height - H)

That is my expectation, but not what the G30 command currently does.

You will notice in the code of G30 command the mention of platform.AxisMinimum(Z_AXIS), variable which I can't make sense of:

ms.coords[Z_AXIS] = (IsAxisHomed(Z_AXIS)) ? platform.AxisMinimum(Z_AXIS) - zp->GetDiveHeight() + zp->GetActualTriggerHeight()

This is in contrast to the probing code of the G29 command, which works as you described without ever using platform.AxisMinimum(Z_AXIS):

ms.coords[Z_AXIS] = -zp->GetDiveHeight() + zp->GetActualTriggerHeight();

Hence my (old yet still relevant) pull request.

Hopefully this patch would not bring any regression, however it might save multiple RRF user from less than desirable unexpected nozzle crashes.

@jp-douarvil-0 one of the perils of being a beta-tester! But thanks for pointing this out, we appreciate the feedback. We also found a couple of other related bugs; active and standby temps not showing if set by Gcode commands and same issue with chambers. It does work correctly if you revert to DWC 3.4.5, but there may be other issues running that with the beta firmware.

Unless you need specific features of the beta version, running the release version may be better for you, though we appreciate the feedback.

Ian

@T3P3Tony I haven't been able to run beta4 because of the crashing issues i'm having with it for more than one print. But if I remeber correctly this specific issue was fixed.

@dc42 Thank you very much for your valuable answers. I will modify the wiring in accordance to your recommendations.

Regards,

@jp-douarvil-0 said in Save custom "Machine movement steps":

I use Firefox for browsing. The same behavior is experienced using Edge however.

Thanks, I can confirm this is a bug - move steps for additional axes are not correctly loaded.
I'll fix it in the next DWC version.