This is a great plug-in, and I am getting the config settings dialled in. I am still using the time detection, as the distance setting causes me some problems. Primarily it's because I have it mounted on the top rail of my CR-10, which is where I have the spool also mounted. My problems are just because the filament gets slack during printing, and the auto-rewind spool doesn't have enough force to pull the filament back through the optical sensor.
Anyway, my request is that with the data provided in the OctoPrint interface it would be useful to also include the time since the last detection. That would help dialling in the right time based detection.
I also wondered whether the time delay could be dynamic and set a larger value when the print speed is slow, but that might be too much to expect from the developer.
Anyway, many thanks for your work. It enabled my to actually bother with the optical sensor knowing that I could use the GPIO instead of wiring into the control box.
This is a great plug-in, and I am getting the config settings dialled in. I am still using the time detection, as the distance setting causes me some problems. Primarily it's because I have it mounted on the top rail of my CR-10, which is where I have the spool also mounted. My problems are just because the filament gets slack during printing, and the auto-rewind spool doesn't have enough force to pull the filament back through the optical sensor. Anyway, my request is that with the data provided in the OctoPrint interface it would be useful to also include the time since the last detection. That would help dialling in the right time based detection. I also wondered whether the time delay could be dynamic and set a larger value when the print speed is slow, but that might be too much to expect from the developer. Anyway, many thanks for your work. It enabled my to actually bother with the optical sensor knowing that I could use the GPIO instead of wiring into the control box.