Host Action Commands doesn't work as expected
Does anyone have any experience getting host_action_commands to work on a prusa mini? Starting with stock Ender 3, I enabled Advanced_pause and Host_action_commands, so I could get OctoPrint's action commands and TSD to notify me that I need a filament change. Enabling these features worked on the ender 3, letting me see filament notifications from my printer on the OctoPrint interface and get a notification from TSD for a color change or filament runout. This should work on any printer running marlin.
The first image shows a color change triggered on ender 3 (triggered with m600). TSD and OctoPrint both show status as pausing. This is as expected. Second image shows a color change happens on Prusa Mini, OctoPrint and TSD still show "printing"
I went into the Prusa Mini firmware found here: https://github.com/prusa3d/Prusa-Firmware-Buddy and it shows that Advanced_pause and host_action_commands are already enabled, so I am not sure why the Prusa mini doesn't exhibit the same behavior as the Ender 3.
Appreciate any help in advance!
RE: Host Action Commands doesn't work as expected
host_action_commands
Don't know if its an issue but aren't there a couple of dependencies?
RE: Host Action Commands doesn't work as expected
I think the only dependencies that apply should be:
Action commands
host_action_commands enabled
host_prompt_support enabled
M600
Advanced_Pause_feature enabled
There was a known issue with something in the firmware not working with OctoPrint previously, but that has been fixed. With my current setup, the filament sensor does work with OctoPrint, and action commands do seem to be passed from the printer (I get a filament change notification from TSD), but OctoPrint shows the printer as "printing" throughout the entire filament change process. I am waiting to hear back from Prusa but figured I would ask here in case anyone else had a similar experience.
RE: Host Action Commands doesn't work as expected
Hi Neil. How did you go?
Sadly Prusa is having issues with everything from website to model database to printer quality at the moment. Support is non-existent.
Ender 3 works (as you have seen) when Prusa doesnt. The older Prusa printers seem to have been more reliable but lately Prusa seem to have picked poor quality components because things just dont seem to work any more. The Prusa mini is supposed to be the most reliable printer in their line-up at the moment (dont go near the Mk3s+) so hopefully support will get you sorted soon. You can try them at [email protected] but dont expect them to answer for a few weeks. Alternatively, go to the 'shop' and use the chat functionality in the bottom right corner but bear in mind the support people on that chat are pretty clueless.
Good luck
RE: Host Action Commands doesn't work as expected
@dontbuyprusa: we generally say: "you did it in slices" when too much is too much.
DISCLAIMER:
I am not and will never be an employee of Prusa Research unless they offer me 100K € gross per year. I have friends who built the printer starting from a wooden frame ... that says a lot.
1+1=10 - take a look at my disgusting and useless models
RE: Host Action Commands doesn't work as expected
@funcoolio, "you did it in slices"
RE: Host Action Commands doesn't work as expected
Ender 3 works (as you have seen) when Prusa doesnt.
Fairly simple explanation, your Ender3 is running vanilla Marlin but the Prusa is a fork. I've seen posts on the Octoprint board that suggest that Prusa use non standard gcode for some function. Perhaps if you monitor the dialog during a filament change all might be revealed.