Orbiter Filament Sensor 2.2 not working properly
I used this guide to install the filament sensor on my Orbiter V2: https://www.orbiterprojects.com/orbiter-filament-sensor/
I used my EBB42 1.2v for wiring the filament sensor. Namely the I2C port (https://github.com/bigtreetech/EBB).
Image: Colors from top to bottom are red, blue, green and yellow.
24 Replies
please share your printer.cfg
unwilling-turquoiseOP•2y ago
Wiring
unwilling-turquoiseOP•2y ago
well, and the OrbiterSensor.cfg
unwilling-turquoiseOP•2y ago
It seems to me that the wiring is correct but I may understood the sensor functionality wrong. Meaning I will need to change line 262 into "switch_pin: !toolboard:PB3"
But shouldn't the filament running out have triggered the runout anyway?
remnove that part again, that was from my config
[filament_switch_sensor my_sensor]
event_delay: 0.1
pause_on_runout: True
runout_gcode:
UNLOAD_FILAMENT
insert_gcode:
LOAD_FILAMENT
switch_pin: !toolboard:PB4
i need the actual content of this file OrbiterSensor.cfgunwilling-turquoiseOP•2y ago
I have deleted it from my printer in the meantime.
omg whts this
unwilling-turquoiseOP•2y ago
That's what I thought lol
Your approach works partly and there can't be missing much. I try now the switch_pin change, maybe it was already the issue
one sec
i make a new file for you
[filament_switch_sensor filament_sensor]
event_delay: 0.1
pause_on_runout: True
runout_gcode:
UNLOAD_FILAMENT
insert_gcode:
LOAD_FILAMENT
switch_pin: ^!toolboard:PB4
[gcode_button sensor_button]
pin: ^PC7
press_gcode:
UNLOAD_FILAMENT
this is all you need
make sure to use the correct pin numbers
the button works as a eject button, to unload filament
if you enter new filament it gets automatically loaded
if a runout happnes it gets unloaded
make sure to always use a ^ sign in front of the pinsunwilling-turquoiseOP•2y ago
Ok I will try. What does "switch_pin" do?
the switch pin is the actual filament sensor pin
unwilling-turquoiseOP•2y ago
I have it like this now (PB4 is definitely to unload):
[filament_switch_sensor filament_sensor]
event_delay: 0.1
pause_on_runout: True
runout_gcode:
UNLOAD_FILAMENT
insert_gcode:
LOAD_FILAMENT
switchpin: !toolboard:PB4 (to be changed__)
[gcode_button sensor_button]
pin: ^!toolboard:PB4
press_gcode:
UNLOAD_FILAMENT
Ok then it's final form is this:
[filament_switch_sensor filament_sensor]
event_delay: 0.1
pause_on_runout: True
runout_gcode:
UNLOAD_FILAMENT
insert_gcode:
LOAD_FILAMENT
switchpin: ^!toolboard:PB3
[gcode_button sensor_button]
pin: ^!toolboard:PB4
press_gcode:
UNLOAD_FILAMENT
you may need to invert the
pin: ^!toolboard:PB4
to
pin: ^toolboard:PB4
depending on how you have it connectedunwilling-turquoiseOP•2y ago
Connected like on the Orbiter page advised
trust me, you want
^unwilling-turquoiseOP•2y ago
I have. What does it do? lol
thats a resistor
like a pullup/pulldown resistor
unwilling-turquoiseOP•2y ago
Ok, did not know that. Will have to read up on that!
it makes sure you dont get false alerts
unwilling-turquoiseOP•2y ago
It's working. Why the hell do they have 100s lines of code in the Orbiter sensor.cfg ^^
thats the magic of RatOS
conscious-sapphire•2y ago
@maxmueller89 when you runout of filament or unload it manually, does the extruder try to unload it 2 times? i have the same thing and its happening to me
unwilling-turquoiseOP•2y ago
@pmelim as you mention it right now, yes I got the same result lol
I didn‘t have time to look into it as it was not removing any functionality .. I assume it comes from this: filament runs out, sensor triggers, filament is below sensor, filament gets retracted, sensor triggers again (!) and this causes the 2nd unload. May I be correct Mr. @Helge Keck? 😁
I didn‘t have time to look into it as it was not removing any functionality .. I assume it comes from this: filament runs out, sensor triggers, filament is below sensor, filament gets retracted, sensor triggers again (!) and this causes the 2nd unload. May I be correct Mr. @Helge Keck? 😁