Filament sensor time delay #193

New Issue

2018-10-06T10:39:53+01:00

sajovicd commented

2018-10-06 10:39:53 +01:00

(Migrated from github.com)

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 :)

Any suggestion?

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](https://user-images.githubusercontent.com/25117093/46569878-d9517000-c95b-11e8-81f0-4c54b55faea5.png) ![image](https://user-images.githubusercontent.com/25117093/46569873-d35b8f00-c95b-11e8-87b5-bb7d0138d96b.png) Any suggestion?

vitormhenrique commented

2018-11-08 04:58:24 +00:00

(Migrated from github.com)

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...

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...

👍 1

sajovicd commented

2018-11-08 05:19:49 +00:00

(Migrated from github.com)

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

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

Thank you

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

2019-04-30 08:22:34 +01:00

(Migrated from github.com)

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

What am I doing wrong?

Thanks for your support.

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](https://user-images.githubusercontent.com/25117093/56945914-00a2a100-6b29-11e9-9346-cb7577380f09.jpg) What am I doing wrong? Thanks for your support.

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: Gandalf/OctoPrint-Enclosure#193