Jump to content

Tetra84

Dormant
  • Posts

    3
  • Joined

  • Last visited

Everything posted by Tetra84

  1. thanks smartavionics, using the material command was the thing to do! from an earlier reddit post I made, someone else suggested which worked: M140 S{material_bed_temperature} ; heat bed, nonblocking M104 S{material_print_temperature} ; heat hotend in parallel ; DO THE RGB THING HERE M190 S{material_bed_temperature} ; heat bed, blocking M109 S{material_print_temperature} ; heat hot end, blocking
  2. additional screenshot showing that it still adds heating commands even when I add the custom code in Cura. How to make it not do that?
  3. Hi, Hoping someone can help me figure this out. I'm trying to set up RGB lighting for my printer, I've got it mostly figured out, however, I'm trying to get a red light to come on when the printer starts heating up. As it is, I can only add that code in Octoprint, since Cura doesn't seem to show the bed and tool heating code in the start gcode section. I can see this code when I look at it in OctoPrint, but how do I access it in my slicer program? I don't want to have to modify each individual gcode before I print every time in OctoPrint. Is there a way to put custom temp code in the start gcode of Cura and not have it auto-generated? Basically, why is the boxed g code (M190, M104, M109) not by default in the start g-code of Cura? and is there a way I can put it in there? I'd like to add a M150 command at the very start, but I can't because it will put the bed and tool heating code before that. I've tried adding the below code at the start g-code section: M150 R255; turn on red LEDs M190 S{first_layer_bed_temperature} ; set bed temp M104 S{first_layer_temperature} ; set extruder temp M109 S{first_layer_temperature} ; wait for extruder temp M82 ; absolute extrusion mode however, it still adds additional M190, M104, M109 before it when I look at the gcode in OctoPrint. Help?
×
×
  • Create New...