Problems with Orbiter Smart Sensor
I installed an orbiter smart sensor on the toolhead. Seems to work fine. I configured printer.cfg according to: https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/filament_sensors.md#orbiter-smart-filament-sensor-example-configuration
but shouldn't pressing the button unload the filament? On my machine nothing happens. No heating and unloading of hotend.
For testing I changed in my printer.cfg:
[filament_switch_sensor toolhead_filament_sensor_t0]
pause_on_runout: False
event_delay: 0.1
switch_pin: ^toolboard_t0:PB3
runout_gcode:
RATOS_ECHO MSG="runout"
insert_gcode:
RATOS_ECHO MSG="insert"
[gcode_button toolhead_filament_sensor_button_t0]
pin: ^toolboard_t0:PB4
release_gcode:
RATOS_ECHO MSG="pressed"
press_gcode:
Only inserting the filament gives the message "insert". Removing it should normally give "runout" as I simulate a runout, but nothing happens. When pressing the button nothing happens.
The sensor status "empty" and "detected" is correctly shown under Tab "Miscellaneous"
Any ideas?
Im running RatOS2.1RC3-0
I got this version: https://de.aliexpress.com/item/1005007527028984.htmlGitHub
RatOS/site/docs/configuration/filamentsensors.md at documentation...
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - HelgeKeck/RatOS
9 Replies
OK changed code a bit to get every event (hopefully)
[filament_switch_sensor toolhead_filament_sensor_t0]
pause_on_runout: False
event_delay: 0.1
switch_pin: ^toolboard_t0:PB3
runout_gcode:
RATOS_ECHO MSG="runout"
insert_gcode:
RATOS_ECHO MSG="insert"
[gcode_button toolhead_filament_sensor_button_t0]
pin: ^toolboard_t0:PB4
release_gcode:
RATOS_ECHO MSG="released"
press_gcode:
RATOS_ECHO MSG="pressed"
I did some tests:
OK results: =>
inserting filament -> "insert"
OK results, but wrong documentation: =>
filament inserted & pressing button -> "pressed"
filament inserted & pressing button & filament removed -> "released"
filament inserted & simulated tangle -> "pressed"
filament inserted & simulated tangle & filament removed -> "released"
NOT OK result:
removing filament -> <nothing>you need to change the configuration for the button
According to https://github.com/RobertLorincz/Orbiter-2-Smart-Sensor/blob/main/Klipper%20Config/Orbiter2_SmartSensor.cfg
the button section should be:
[gcode_button toolhead_filament_sensor_button_t0]
pin: ^toolboard_t0:PB4
press_gcode:
UNLOAD_FILAMENT
release_gcode:GitHub
Orbiter-2-Smart-Sensor/Klipper Config/Orbiter2_SmartSensor.cfg at m...
Orbiter 2 Smart Sensor. Contribute to RobertLorincz/Orbiter-2-Smart-Sensor development by creating an account on GitHub.
use the ratos documentation
GitHub
RatOS/site/docs/configuration/filamentsensors.md at documentation...
The preconfigured Raspberry Pi image that makes it easy to run Klipper + Moonraker + Mainsail on your printer. - HelgeKeck/RatOS
Yes ,I used the documentation. But did not work as it was. Now I'm searching the problem.
Regarding runout: I did testing without printing when removing the filament from the sensor, so the "runout_gcode" is correctly not triggered. User error 🙂
Hm, but I'm still not sure how to change the button configuration as it doesn't do anything when pressing the button.
Should I negate the pin like this?
[gcode_button toolhead_filament_sensor_button_t0]
pin: !^toolboard_t0:PB4
release_gcode:
UNLOAD_FILAMENT
press_gcode:read the documentation, its descirbed there exactly
https://github.com/HelgeKeck/RatOS/blob/documentation_v2.1/site/docs/configuration/filament_sensors.md#action-button
Aaah, there it is....
pin: ^!toolboard_t0:PB4
sorry, was blind, did not see the exclamation mark.
Thank you for your help and patience.
Just a comment: using "press_gcode" makes more sense to me when pressing the button in reality.For me, with the Orbiter Sensor (so V1) I had to move the gcode for toolhead_filament_sensor_button_t0 from release_gcode to press_gcode. Now I installed the Smart Sensor and If I keep it as described in your docs, the behaviour is just wrong (wherein it behaves weird). Again I had to move the code to the release_gcode to make it work properly (fyi)
