search

prusa3d / Prusa-Firmware-Buddy

Firmware for the Original Prusa MINI, Original Prusa MK4 and the Original Prusa XL 3D printers by Prusa Research.
Other
1.09k stars 214 forks source link

[FEATURE REQUEST] Enable EMERGENCY_PARSER #1364

Open hasechris opened 3 years ago

hasechris commented 3 years ago

Please, before you create a new feature request, please make sure you searched in open and closed issues and couldn't find anything that matches. searched and found nothing

If it makes sense, enter what type of printer or upgrade the feature request applies to. Printer type - [MINI] Optional upgrades - none

Is your feature request related to an existing problem? Please describe. Printer Dialouges wont be processed on Octoprint because of not enabled EMERGENCY_PARSER Capability.

Describe the expected functionality With the Capability EMERGENCY_PARSER we can send M-Codes like M876 (Dialoge Handling) to the printer while it is sending "busy:xx" Messages to the octopi.

Also please have a look at the Issue on Octoprint https://github.com/OctoPrint/OctoPrint/issues/3699. There is also a comment at the bottom of the discussion, that emergency_parser should be supported on STM32.

hasechris commented 2 years ago

sorry but Bump. This feature is really needed for good octoprint handling...

Thynix commented 1 year ago

As of this writing, enabling EMERGENCY_PARSER encounters

#error "EMERGENCY_PARSER is not yet implemented for STM32F4/7. Disable EMERGENCY_PARSER to continue."
Prusa-Support commented 1 year ago

Hello! Thank you for the report, sorry for the late response from my side. From what I could see internally, this aspect is known to us and it is currently in the works. In case of more info on this, we'll update on this thread, although I can't guarantee a possible timeframe for now.

Alessandro Pantaleo Prusa Research

hasechris commented 1 year ago

As of this writing, enabling EMERGENCY_PARSER encounters

#error "EMERGENCY_PARSER is not yet implemented for STM32F4/7. Disable EMERGENCY_PARSER to continue."

Hi :-)

maybe the error is only for the version in this repo? In this octoprint issue [0] someone mentions that there seems to be support for EMERGENCY_PARSER in STM32. But sadly i dont have more information regarding this so i could be wrong.

[0] https://github.com/OctoPrint/OctoPrint/issues/3699#issuecomment-729134784

hasechris commented 1 year ago

Hello! Thank you for the report, sorry for the late response from my side. From what I could see internally, this aspect is known to us and it is currently in the works. In case of more info on this, we'll update on this thread, although I can't guarantee a possible timeframe for now.

Alessandro Pantaleo Prusa Research

Hey Alessandro,

that sounds really cool :-) Would be so great to use my mini+ remotely from octoprint.

sorry for the late response from my side.

happens from time to time :-) But considering the amount of issues and the response times from Prusa (really, not you. I'm not mad or anything) here on github maybe prusa could devote more workhours from you guys into the mini+ repo management? That would help immensly.

Best regards hasechris

github-actions[bot] commented 1 month ago

This issue has been flagged as stale because it has been open for 60 days with no activity. The issue will be closed in 7 days unless someone removes the "stale" label or adds a comment.

hasechris commented 1 month ago

ugh - stale bot things. @Prusa-Support please remove the stale label - you said you are working in this?

btw: stale bot is really not helping. Just shoving a wall into the faces of the community with the label "issue is stale" is really bad if you are the cause for stalling.