kiniad.
RRCRat Rig Community [Unofficial]
•Created by Kacer on 12/23/2024 in #fix-my-printer
IDEX Problem 2nd Layer move
Very strange. I now only work without any issues with Orca Slicer and IDEX, first use also the Hybrid Config of Orca and eventually created all the profiles for Orca, look at the slicer topic, I've published this profiles,
15 replies
RRCRat Rig Community [Unofficial]
•Created by fredbeauchamp on 12/2/2024 in #ratos-support
Load Unload Filament klipperscreen
I know klipperscreen is not made for idex, but so you could load and unload filament directly on the printer, that's all I need.
But long story short, I would appeciate the solution for klipperscreen, otherwise for me it's fine.
42 replies
RRCRat Rig Community [Unofficial]
•Created by fredbeauchamp on 12/2/2024 in #ratos-support
Load Unload Filament klipperscreen
Changing the toolhead on klipperscreen sends a T0 or T1, and this macro isn't changed at all.
42 replies
RRCRat Rig Community [Unofficial]
•Created by fredbeauchamp on 12/2/2024 in #ratos-support
Load Unload Filament klipperscreen
Yes, you are right, if the steppers are engaged, and you change the active toolhead/extruder, they are moving.
But this happens on klipperscreen anyway, if you change the toolhead, also with the -1-safety net. Only if you than try to use the unload/load buttons nothing happens.
42 replies
RRCRat Rig Community [Unofficial]
•Created by fredbeauchamp on 12/2/2024 in #ratos-support
Load Unload Filament klipperscreen
I would be happy to see how to change it in klipperscreen config. I don't know how, but I'm not familiar with klipperscreen.
Otherwise, if "to force the user to select" is only to prevent the user to load/unload the wrong filament accidently, I'll take the risk.
But there's no need to implement this in Ratos, it's working for me, as it is.
42 replies
RRCRat Rig Community [Unofficial]
•Created by fredbeauchamp on 12/2/2024 in #ratos-support
Load Unload Filament klipperscreen
Okay, are there any side effects for my implementation?
If the macro is called with toolhead=0 or 1 it worked as usual, only if it get's toolhead=-1 it uses the active extruder (this is what I mean with "toolhead selection")
I have tested this and it is working fine so far. but I haven't tested every situation. This is also what Klipperscreen needs for load and unload.
42 replies
RRCRat Rig Community [Unofficial]
•Created by Dor_Amboss on 12/1/2024 in #german-support
Filament Sensor Orbiter Release Button (das leidigliche Thema)
Achja nochwas: Unbedingt den Teil {% if (printer.print_stats.state == "printing") %} drinlassen, mit welcher Message auch immer.
Also dann:
press_gcode:
{% if (printer.print_stats.state == "printing") %}
RESPOND TYPE=error MSG="T0 Filament CANNOT UNLOAD!"
{% else %}
_ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=0
{% endif %}
Ohne diese printing Prüfung, wenn tatsächlich mal ein Clogging passiert, fängt der Drucker an, auf dem Objekt sofort Filament zu extrudieren und danach das Filament zu entladen. Das Druckobjekt ist dann damit garantiert zerstört.
Ein seltsames Verhalten, aber dieser press_gcode-Teil scheint, jedenfalls bei mir, auch beim Clogging ausgeführt zu werden.
6 replies
RRCRat Rig Community [Unofficial]
•Created by Dor_Amboss on 12/1/2024 in #german-support
Filament Sensor Orbiter Release Button (das leidigliche Thema)
Ist das Problem noch aktuell? Wie in der printer.cfg zu sehen ist der press-gcode leer, das ist in dem Beispiel nicht gefüllt.
Bei mir sieht es für T0 z.B. so aus und funktioniert auch:
[gcode_button toolhead_filament_sensor_button_t0]
pin: ^toolboard_t0:PB4
release_gcode:
{% if (printer.print_stats.state == "printing") %}
RESPOND TYPE=error MSG="T0 Filament CLOGGED!"
_ON_TOOLHEAD_FILAMENT_SENSOR_CLOG TOOLHEAD=0
{% else %}
_ON_FILAMENT_SENSOR_BUTTON_PRESSED TOOLHEAD=0
{% endif %}
press_gcode:
{% if (printer.print_stats.state == "printing") %}
RESPOND TYPE=error MSG="T0 Filament CANNOT UNLOAD!"
{% else %}
RESPOND TYPE=command MSG="T0 Unload Request!"
M117 T0 Unload Request!
UNLOAD_FILAMENT TEMP=240 TOOLHEAD=0
{% endif %}
6 replies