@Wilber Please start a thread for your issue and provide some detail on your setup and configuration.

Apropos extrapolation, my DWC shows a misleading view of the heatmap, truncating the bed area to the probed region. A more intuitive visualization would be to show the probed area in the context of the entire bed, with an option to show also extrapolated areas.

This was captured with a 300x300 bed, DWC truncate the bed view to the probed area.

96f6b98d-fd62-4d70-87ca-49784d635b38-image.png

@Nightreaver said in Improvement to M558 (Bed Temperature Threshold):

H6

6mm is quite high dive height for the BLtouch. Reducing the dive height to be just above the trigger height would reduce the amount of time spent probing and the heater will be off for less time. Try H3.

Pressure advance can help negate the need for wiping somewhat.

Sounds like a plugin possibility.

So, any news on this one? I would really like to see the status of heaters via gcode commands. @dc42

Hi forum-member, if you´ve read that far, you can continue for ongoing forum-discussion here: https://forum.duet3d.com/topic/21649/command-to-turn-heaters-active-standby-off

@chrishamm awesome! I will make both PRs. I don't think its very complicated at all, and from what I read in the C code there wont be any side effects. It doesn't cause a memory leak or anything like that.

https://forum.duet3d.com/topic/15302/cura-script-to-automatically-probe-only-printed-area

@Mac3D-FPV You mean this?

@dc42 said in v3 firmware treats Fan 0 as "special"?:

@fcwilt said in v3 firmware treats Fan 0 as "special"?:

It's not a big deal as I can re-assign that fans to be sure fan 0 is my part cooling fan...

That is exactly what we advise in the documentation. https://duet3d.dozuki.com/Wiki/Connecting_and_configuring_fans#Section_General_recommendations

That is also understood.

And back when all the boards had outputs labeled "fan 0" and needed pin names "fan 0" it made a certain sense.

But with the new boards with generic names for outputs and pins attaching a special significance to fan 0 seems odd to me, particularly with multiple tool setups.

Would it be difficult to have something along the lines of M565 P-1 Fnnn?

However that's just my two cents.

Frederick

As @fcwilt says, it could be dangerous on other machines if RRF arbitrarily changed the state of outputs when updating firmware.

I think the real solution is for us to add a mechanism to allow axis brake outputs to be configured, so that brakes are automatically released when an axis is enabled, and vice versa. This is already on the firmware wishlist.

Not yet. Moved to the wishlist.

Beta release now available, see https://forum.duet3d.com/topic/21597/reprapfirmware-3-3beta1-now-available.

@fcwilt Yes, I print tiny parts ( custom gears and connectors), and I need minimal entry points on my objects to allow best external mechanical interface possible.

Therefore I need to purge my nozzle between each part to ensure identical start conditions.

And since I need many parts, I stuff my printing bed with as much as possible parts.

The new algorithm is geared for accuracy rather than speed. 1.5 hours may actually be pretty short compared to that on a very large thick bed. Best to just leave it do what it needs to do?