Filament Runout output to serial

tigercjn commented 3 years ago

When the Snapmaker 2.0 detects the filament runout by the sensor going open could it send a message out the serial port so Octoprint could detect it? If it sent "echo:busy: paused for user" then the plugin called "OctoPrint-PauseForUserEvent" could be used to detect that user intervention is required.

GeraldPape commented 3 years ago

Second that

scotthsl commented 3 years ago

When the Snapmaker 2.0 detects the filament runout by the sensor going open could it send a message out the serial port so Octoprint could detect it? If it sent "echo:busy: paused for user" then the plugin called "OctoPrint-PauseForUserEvent" could be used to detect that user intervention is required.

Sorry we don't know much about the plugin "OctoPrint-PauseForUserEvent". Do you have a requirement to be able to resume a job that was paused due to filament runout when working online with OctoPrint?

tigercjn commented 3 years ago

The problem at the moment is if you are running Octoprint on the Snapmaker 2.0 and you run out of filament it just keeps printing, the filament run-out detection does not flag any problem. The machine does not pause.

scotthsl commented 3 years ago

Got it. Just want to confirm 2 points firstly:

Did you disable filament runout checking by "M412 S0" in the Gcode?
If you try to print the model with touch screen? if no, please help confirm if the issue also occurs in printing with touch screen. thanks.

tigercjn commented 3 years ago

A few people are having the same problem and its mentioned in a few areas, here is one https://community.octoprint.org/t/snapmaker-2-0-a350/27455 [image: image.png]

I will do some testing when it finishes the current print and confirm what happens.

I did check the hardware switch and it does change state when the filament it runs out, changes from Triggered to Open.

On Wed, 6 Jan 2021 at 19:17, scotthsl notifications@github.com wrote:

Got it. Just want to confirm 2 points firstly:

Did you disable filament runout checking by "M412 S0" in the Gcode?

If you try to print the model with touch screen? if no, please help confirm if the issue also occurs in printing with touch screen. thanks.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Snapmaker/Snapmaker2-Controller/issues/50#issuecomment-755154443, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ35Q4ML6I7XV35FG6SP2Z3SYQL77ANCNFSM4VUUY32A .

tigercjn commented 3 years ago

There are some more comments here. https://forum.snapmaker.com/t/sm2-0-no-filament-runout-with-octoprint/6725

tigercjn commented 3 years ago

I tested the filament runout and it works ok if the file is sent to the screen and recovers ok. would be better if it wiped the purge off. If running from Luban over wireless no notifications on the screen or on Luban and the head goes to the home position to load. If running Luban connected directly it does not sense the runout and just keeps printing in mid-air. This is the same problem with running direct from Octoprint.

tigercjn commented 3 years ago

I think we need this part of Configuration_adv.h uncommented.

Temennigru commented 3 years ago

I'm copying my comment from the snapmaker forum.

It looks like it's standard practice for marlin machines with built in filament sensors to pause the print and send an action command back to the host when printing through serial

It’s really going to be dependent on the firmware that the printer is using. If the filament runout sends an action command back to connected clients (like octoprint) that a pause has been done, then yes, OctoPrint will actually pause as long as the bundled Action Command Prompt Support plugin is not disabled.

From https://plugins.octoprint.org/plugins/actioncommands/ 1

As of the latest Marlin bugfix-1.1.x version, the command M118 can be used to echo output to serial, meaning that M118 //action:dostuff would cause this plugin to try to handle the dostuff command when //action:dostuff was echoed back on the serial console.

A future application of the plugin would be to add actions in the RepRap machine’s firmware so that hosts could respond. For example, when Marlin is killed because something is wrong it would echo //action:poweroff and the attached OctoPrint instance could use this action command to trigger the printer’s power outlet to switch off.

From the octoprint action commands plugin:

OctoPrint will, by default, respond to three action commands: action:disconnect (disconnects the printer), action:pause (pauses streaming the print job), and action:resume (resumes streaming the print job).

so you would want something like M118 //action:pause, then the machine itself would prompt the user to change the filament

tigercjn commented 3 years ago

We just want the marlin firmware in the firmware to send out a message, using the host action commands that Marlin has would be great. It's then up to the host, in this case, Octoprint to stop sending, alert the user and wait for the go ahead.

Schnapsmaker commented 3 years ago

I think its nessecary to react of filament runout almost in Luban and therewith octoprint as well.

tigercjn commented 3 years ago

Yes if you are driving the Snapmaker from a laptop running Luban this should be able to handle filament runout, any features should be kept in line with the Marlin standard. Then it would work with any other complaint product like Octoprint.

On Thu, 21 Jan 2021 at 01:29, Schnapsmaker notifications@github.com wrote:

I think its nessecary to react of filament runout almost in Luban and therewith octoprint as well.

— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub https://github.com/Snapmaker/Snapmaker2-Controller/issues/50#issuecomment-763643349, or unsubscribe https://github.com/notifications/unsubscribe-auth/AJ35Q4KUBWUSOTH7KBSNYRDS23SBTANCNFSM4VUUY32A .