You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
If an user click pause button on a printing, and then quickly click resume, the printer may took some time to physically move its bed/extruder for the first command (pause), so its state will change again, but the command won't work. Thill will invert the pause/resume control.
- Fix Information
Now the printer don't send any event or change its state once is completely paused. Every printer take different time to finish moving its parts, but they may have an intern event due a bip sound some emit.
The ideal would be capture that event and wait for it before the websocket send the data changed, so the only change would be here in AstroBox, and anybody listening the socket would listen the paused/resume change once the printer is ready for real.
Note: This may be related to the extruder control behaviour, if an user click several times a direction button(for example:left), all the commands will be send, and acumulated.I think it shouldn't accept commands while its moving.
The text was updated successfully, but these errors were encountered:
julianCast
changed the title
AstroBox don't listen when the printer has finished some commands
AstroBox don't listen when the printer has completely finished pausing/resuming
Aug 31, 2017
julianCast
changed the title
AstroBox don't listen when the printer has completely finished pausing/resuming
AstroBox don't listen when the printer has completely paused/resumed
Sep 1, 2017
- Problem
If an user click pause button on a printing, and then quickly click resume, the printer may took some time to physically move its bed/extruder for the first command (pause), so its state will change again, but the command won't work. Thill will invert the pause/resume control.
- Fix Information
Now the printer don't send any event or change its state once is completely paused. Every printer take different time to finish moving its parts, but they may have an intern event due a bip sound some emit.
The ideal would be capture that event and wait for it before the websocket send the data changed, so the only change would be here in AstroBox, and anybody listening the socket would listen the paused/resume change once the printer is ready for real.
Note: This may be related to the extruder control behaviour, if an user click several times a direction button(for example:left), all the commands will be send, and acumulated.I think it shouldn't accept commands while its moving.
The text was updated successfully, but these errors were encountered: