Destruction and how to prevent it

[Phaedrux]

@dc42 could the button on the paneldue be hidden when a print starts at least?

[dc42]

@phaedrux said in Destruction and how to prevent it:

@dc42 could the button on the paneldue be hidden when a print starts at least?

Which button or buttons? The Pause button is needed, so are the buttons to adjust fan speeds and temperatures. Macro buttons may or may not be needed depending on what they do.

[Phaedrux]

@dc42 no, not all the buttons, I just mean the bed level button, since it seems to have a very immediate and damaging effect mid print.

This must be possible since the baby stepping button only appears when a print is started and disappears when finished.

[dc42]

I guess I could disable the bed comp and homing buttons while a print is active and not paused, but I suspect that once I have done that, there will be complaints that other functions should be disabled too. This is the sort of change that needs to be thought out properly in advance.

[Phaedrux]

I haven't used that bed button on the PanelDue. Does it just run a macro? If so, the user could protect themselves by adding a block M291 prompt at the beginning that asks if they are sure they wish to run it. Would that still interrupt the print?

[DocTrucker]

I'd suggest something similar to the user access control linux has. At least during a print refuse commands that aren't encapsulated in another gcode ie:

M[unused number] "G1 X50 Y50 Z50" P[sudo like password]

Duet and web control could be adapted to use sudo gcode for a configurable time period and Duet could respond with permission denied to normal gcode mid print. E-Stop commands should probably be accepted without encapsulation.

Edit: If this feature was disabled by default when added it would be completely unintrusive for users who don't want it. Likewise the password section should probably default to no password.

[fma]

sudo-like command is interesting, but if the use of a blocking macro with M291 does not interrupt the print, it seems to me a much simpler (and already implemented) option.

[DocTrucker]

I've not tried to use M291, but from what I can see it doesn't help when more atomic, or single line commands are used or triggered by mistake such as G1. Likewise whilst the blocking macro may save from damage wouldn't this also potentially cause an artefact inducing pause?

[Phaedrux]

Would it be possible to simply have a timed lockout for the panel due similar to the screen dimming? After which time a long press would need to be entered to regain control? At least that way you're guarded against inadvertent presses and probably also protect against strangers just pressing buttons.

[T3P3Tony]

I have moved this to the firmware wish list as it will probably require firmware changes to implement.

@Phaedrux having a lock screen for the paneldue is on the wishlist.