search

vitormhenrique / OctoPrint-Enclosure

OctoPrint Enclosure Plugin
GNU General Public License v3.0
399 stars 203 forks source link

Filament sensor time delay #193

Open sajovicd opened 6 years ago

sajovicd commented 6 years ago

Hello,

I have working filament sensor and it works when filament runs out it call's M600 gcode and it did its job. The problem is that I cant setup delay for activating g code. No matter what I enter in delay field, the command is executed immediately.

Biggest problem with that is that sometimes I trigger sensor several times during filament change and then printer execute M600 as many times as I triggered, so I just inserd new filament and confirmed and he goes to printing position and back to filament change and retract new filament out... So I have to play back and forth with printer :)

image

image

Any suggestion?

vitormhenrique commented 5 years ago

I suggest increasing the delay time, I don't have time to look into this right now, but I'll investigate when possible. I'm going out on vacations for 30 days and so honestly I'll only have time next year...

sajovicd commented 5 years ago

No problem, Vitor. Have a perfect vacation, 30 days.... Waaaoouuuu.

When you will have time, next year, please take a look.

Thank you

sajovicd commented 5 years ago

Hello Vitor, I just upgrade octopi, to 0.16.0 and Octoprint is 1.3.10, from the scratch and now the delay seems to work, but I have problem with repeated M600 command. It happen that printer run out of filament in the evening and in the morning I go to change the spoil and I have to repeat change sequence, I think more than 30 times, before print continue printing. So I think that plugin is looking for the correct signal after every delay time is over. In filament change GCODE, I have only M600 command

gcode

What am I doing wrong?

Thanks for your support.