Websockets
-
Maybe not for Duet2 and earlier but having the ability to do an UPGRADE and open a websocket for status reports and async gcode responses would prevent the need to keep issuing rr_status and rr_reply commands. Actually, the Duet2 could probably handle this given that it wouldn't have to handle those rr_ commands coming in every 250ms (or whatever).
Just thought of something else... The PanelDue could be serviced by the same loop preventing it from having to issue M408 commands repeatedly. Maybe an M409 command that specifies the response type and frequency.
-
I like this idea!
-
The firmware being written for Duet 3 uses websockets.
Under some conditions (e.g. when waiting for heaters to reach temperature), the Duet already sends regular status updates to PanelDue. I may extend the number of situations in which this occurs, for example to send regular status updates when running macro files or doing long moves.
-
@dc42 said in Websockets:
The firmware being written for Duet 3 uses websockets.
Under some conditions (e.g. when waiting for heaters to reach temperature), the Duet already sends regular status updates to PanelDue. I may extend the number of situations in which this occurs, for example to send regular status updates when running macro files or doing long moves.
Good deal David!
/me anxiously awaits the Duet 3
