Error evaluating 'gcode_macro START_PRINT:gcode': gcode.CommandError: Filament not detected! Toolhea

I tried to configure the Orbiter Filament Sensor using the below in printer.cfg and anytime I print I get this error. [filament_switch_sensor toolhead_filament_sensor_t0] pause_on_runout: False event_delay: 0.1 switch_pin: ^!toolboard_t0:PB3 runout_gcode: _ON_TOOLHEAD_FILAMENT_SENSOR_RUNOUT TOOLHEAD=0 insert_gcode: _ON_TOOLHEAD_FILAMENT_SENSOR_INSERT TOOLHEAD=0 [gcode_button toolhead_filament_sensor_button_t0] pin: ^!toolboard_t0:PB4 release_gcode:
_ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=0 press_gcode: #[include OrbiterSensor.cfg] BTW, removing the negation on the switch_pin seems to work.
20 Replies
miklschmidt
miklschmidt•6mo ago
Did you wire the sensor to PB3 on the toolboard?
jhorn68 (V-Core 3.1 400)
jhorn68 (V-Core 3.1 400)OP•6mo ago
Yes, changing it to switch_pin: ^toolboard_t0:PB3 worked for me
miklschmidt
miklschmidt•6mo ago
BTW, removing the negation on the switch_pin seems to work.
It might just look like it's working because that inverts the signal (so it thinks there's always filament in there), did you test if it works if you unload the filament? Does it then say it's not detected? (you can see the status in mainsail)
jhorn68 (V-Core 3.1 400)
jhorn68 (V-Core 3.1 400)OP•6mo ago
Yes, it is empty when it should be empty and detected when it should be detected.
miklschmidt
miklschmidt•6mo ago
Aight, will ask helge to fix the guide (i'm assuming that's where you got it from, because all the names are correct 😅)
Helge Keck
Helge Keck•6mo ago
this is like the motor directions, there is no default pin invertion, depends on the filament sensors
jhorn68 (V-Core 3.1 400)
jhorn68 (V-Core 3.1 400)OP•6mo ago
Yessir, I am more than happy to test things if you need to. I also am about to report an issue with unloading filament with the sensor separately. I think I may have to play with temp or retraction length as it gets caught in the geat since the sensor has a smaller passthrough area. Need to get a video.
Helge Keck
Helge Keck•6mo ago
this is not an issue, this is just tip forming will write a doc in the next days on how to tune tip forming
jhorn68 (V-Core 3.1 400)
jhorn68 (V-Core 3.1 400)OP•6mo ago
Great. You guys are awesome man. Keep up the good work.
miklschmidt
miklschmidt•6mo ago
You have a specific example for the orbiter filament sensor using what looks like the EBB, so i went ahead and corrected it
jhorn68 (V-Core 3.1 400)
jhorn68 (V-Core 3.1 400)OP•6mo ago
Correct, EBB42 and Orbiter Sensor v2
Helge Keck
Helge Keck•6mo ago
well, in fact thats from my oprbiter sensors will make it clearer how to. test this an set it correctly
miklschmidt
miklschmidt•6mo ago
oh well then i'm confused 😂 Can you choose between NC/NO on the orbiter sensor? Because if not, then you guys have 2 different versions of the orbiter sensor.
Helge Keck
Helge Keck•6mo ago
im not sure whdre i bought these pair, maybe ripoffs, no idea
miklschmidt
miklschmidt•6mo ago
fair Prolly best to explain the switch stuff then
Helge Keck
Helge Keck•6mo ago
i think we just need to explain it better, like endsopts or motor directions
miklschmidt
miklschmidt•6mo ago
yep
Helge Keck
Helge Keck•6mo ago
also, sometimes you want to deactivate that sanity check, you can do it by disable the sensor in the mainsail ui with that swizch button. in the main ui
jhorn68 (V-Core 3.1 400)
jhorn68 (V-Core 3.1 400)OP•6mo ago
Yeah, maybe say in the docs to run a validation that the switch works as expected by loading and unloading filament. I am a dumbass so I had to think about it to validate it. 🙂 The V1 and V2 Oribiter code does show a different negation depending on the V1 or V2 sensor.
Want results from more Discord servers?
Add your server