TEMPERATURE_WAIT

Hello people. I have what seems to be a silly error from my printer. Everytime I give the printer a file, the following message pops up in klipper console: RatOS | TEMPERATURE_WAIT: Waiting for sensor: extruder, MINIMUM: 0, MAXIMUM: 5 If these number are in Celsius, it makes no sense at all that RATOS demans that my extruder or bed should start between the freezing temperatures of 0 and 5 degrees for it to feel safe to start some printing. How do I reconfigure this to sensible and reasonable values or how do I avoid this new uncessary type of complication ? This error is making me start losing faith in my printer/ratos version. My printer is now a big paper weight until I solve this. Many thanks in advance to the comunity for helping people out with this discord server, we the users really need this to exist.
10 Replies
TheTik
TheTik•2mo ago
What slicer are you using, and what is your start print macro in it?
MISSION CRITICAL
MISSION CRITICALOP•2mo ago
I am using prusa slicer : START_PRINT ; G28 ; home all axes G1 Z5 F5000 ; lift nozzle M190 S[first_layer_bed_temperature] ; aquece cama M109 S[first_layer_temperature] ; aquece nozzle and at the end of the print: M104 S0 ; turn off temperature G28 X0 ; home X axis G28 Y300; home Y axis M84 ; disable motors its prusa slicer 2.9.2
TheTik
TheTik•2mo ago
This isn't an IDEX printer, correct? you should be using
START_PRINT EXTRUDER_TEMP={first_layer_temperature[0]} EXTRUDER_OTHER_LAYER_TEMP={temperature[0]} BED_TEMP=[first_layer_bed_temperature] START_CHAMBER_TEMP=[chamber_temperature] CHAMBER_TEMP=[chamber_temperature] TOTAL_LAYER_COUNT={total_layer_count} X0={first_layer_print_min[0]} Y0={first_layer_print_min[1]} X1={first_layer_print_max[0]} Y1={first_layer_print_max[1]}
START_PRINT EXTRUDER_TEMP={first_layer_temperature[0]} EXTRUDER_OTHER_LAYER_TEMP={temperature[0]} BED_TEMP=[first_layer_bed_temperature] START_CHAMBER_TEMP=[chamber_temperature] CHAMBER_TEMP=[chamber_temperature] TOTAL_LAYER_COUNT={total_layer_count} X0={first_layer_print_min[0]} Y0={first_layer_print_min[1]} X1={first_layer_print_max[0]} Y1={first_layer_print_max[1]}
per the documentation: https://os.ratrig.com/docs/slicers#prusa-slicer similarly, your end gcode should just be END_PRINT @MISSION CRITICAL Are you using ratos 2.0 or 2.1?
MISSION CRITICAL
MISSION CRITICALOP•2mo ago
Ratos 2.1 and aparently you have just solved that problem, thank you very much for that. I tried to print and that error no longer is there, at the moment but now my extruder is inverted in the direction, pulls filament instead or pushing it. Tried the ! thing in the printer.cfg and it did not work for the first time. In the past this has always solved the problem. The printer is completely capable of doing both directions because when I want to retract filament, it extrudes 😀 how can I invert the extruder, since the ! trick does not work ?
TheTik
TheTik•2mo ago
! should work, but does need to be in the right place. Show me the line in question?
MISSION CRITICAL
MISSION CRITICALOP•2mo ago
[extruder] dir_pin: !toolboard_t0:e_dir_pin # Remove ! in front of pin name to reverse the direction of extruder rotation_distance: 4.63 # Orbiter 2 default #pressure_advance: 0.05 # Check https://www.klipper3d.org/Pressure_Advance.html for pressure advance tuning. control: pid pid_kp: 28.413 pid_ki: 1.334 pid_kd: 151.300 min_temp: 180 max_temp: 300
TheTik
TheTik•2mo ago
Im trying to remember if it is supposed to go !toolboard_t0:e_dir_pin or toolboard_t0:!e_dir_pin Try the other, see what happens
MISSION CRITICAL
MISSION CRITICALOP•2mo ago
it does not work, I dont know what else to do.I don´t know if this could be defined elsewhere but the printer does not react to ! or no !, or ! like you said
TheTik
TheTik•2mo ago
printer.cfg is the thing that imports the rest. Only way it could be overriden is if something came after Trying to think of what else it could be, and how to troubleshoot hm. Try commenting out that line, see if it still works If the extruder still works and in the same direction, then the pin IS being defined elsewhere
MISSION CRITICAL
MISSION CRITICALOP•2mo ago
Thanks, will have a look

Did you find this page helpful?