I have a NC roller switch attached to PIN 3. I've verified via command line and a quick python script that the pin and switch work as expected. Settings in the plugin UI are:
Pin: 3
Debounce Time: 400ms
Switch Type: Normally Closed
Board Pin Mode: Board Mode
Pause print when out of filament: checked
When a job starts, this is all I see in the octoprint.log:
2017-11-13 06:27:21,179 - octoprint.filemanager.analysis - INFO - Starting analysis of test.gcode
2017-11-13 06:27:21,186 - octoprint.filemanager.analysis - INFO - Invoking analysis command: /home/pi/oprint/bin/python -m octoprint analysis gcode --speed-x=6000 --speed-y=6000 --max-t=10 --throttle=0.0 --throttle-lines=100 /home/pi/.octoprint/uploads/test.gcode
2017-11-13 06:27:44,439 - octoprint.filemanager.analysis - INFO - Analysis of entry local:test.gcode finished, needed 23.26s
2017-11-13 06:27:48,514 - octoprint.plugins.filamentreload - INFO - PrintStarted: Enabling filament sensor.
2017-11-13 06:27:48,628 - octoprint.util.comm - INFO - M110 detected, setting current line number to 0
When the filament runs out and the switch is released, nothing happens. The job just keeps going.
Is there some other spot I can check for some kind of debugging/verbose log?
I have a NC roller switch attached to PIN 3. I've verified via command line and a quick python script that the pin and switch work as expected. Settings in the plugin UI are:
Pin: 3 Debounce Time: 400ms Switch Type: Normally Closed Board Pin Mode: Board Mode Pause print when out of filament: checked
When a job starts, this is all I see in the octoprint.log:
When the filament runs out and the switch is released, nothing happens. The job just keeps going.
Is there some other spot I can check for some kind of debugging/verbose log?