1 Topic by dkeeling728

  • dkeeling728
  • Member
  • Offline
  • Registered: 2013-05-20
  • Posts: 148

Topic: any gcode command to turn off/change heated bed temp?

Maybe im just not seeing it in settings. but it seems like theres no working way to control the heated bed besides with the manual button. id like a way, perhaps a gcode i could insert at the end of the program, to turn off the headed bed after a print.

would like to run some longer prints overnight, but i dont want the heated bed to sit there cooking for hours for no reason and possibly burn out itself or my power supply. .

anyone know if this is possible with stock firmware or is this something i would need to brush up on my C++ to accomplish? i know the command is there because the manual control works in repetier, just dont know how to make it automatic.

2 Reply by cckens (edited by cckens 2013-06-12 22:29:37)

  • cckens
  • Member
  • Offline
  • Registered: 2012-09-13
  • Posts: 591

Re: any gcode command to turn off/change heated bed temp?

M140 S0 ; kill bed temperature

Reference this for all sorts of useful info...
http://www.soliforum.com/topic/231/impr … end-gcode/

3 Reply by dkeeling728

  • dkeeling728
  • Member
  • Offline
  • Registered: 2013-05-20
  • Posts: 148

Re: any gcode command to turn off/change heated bed temp?

awesome, just what i was looking for. will change over to the new gcode.

next question is: is there a code to make it pause processing of code until bed temperature is reached? for instance, make it wait till the bed gets to 95 before starting to heat the extruder. i dont want my extruder to sit there cooking at 200c for 10 minutes with no plastic moving through it while the bed gets up to temp. lol

can always manually heat bed as usual, just thought it would be cool to have it all automated so all i have to do is push the run button and go back to my CAD program to work on the next part! haha.

4 Reply by elmoret

  • elmoret
  • Filastruder
  • Offline
  • Registered: 2012-10-11
  • Posts: 6,048

Re: any gcode command to turn off/change heated bed temp?

http://reprap.org/wiki/G-code#M190:_Wai … arget_temp

Just search in there is you have other questions.

Filastruder - the robust, inexpensive filament extruder
E3Dv6 All Metal Hotend - the premier 3D printing hotend

5 Reply by adrian

  • adrian
  • Member
  • Offline
  • From: Canberra, Australia
  • Registered: 2013-01-15
  • Posts: 1,623

Re: any gcode command to turn off/change heated bed temp?

What elmoret said; go to the full list of gcode and all answers should be there.
http://reprap.org/wiki/G-code

Of course, the scenario you outlined is already dealt with in Repetier-Host.. under Printer Settings, simply tick "Disable Bed after Print is Finished" .

6 Reply by dkeeling728

  • dkeeling728
  • Member
  • Offline
  • Registered: 2013-05-20
  • Posts: 148

Re: any gcode command to turn off/change heated bed temp?

adrian wrote:

What elmoret said; go to the full list of gcode and all answers should be there.
http://reprap.org/wiki/G-code

Of course, the scenario you outlined is already dealt with in Repetier-Host.. under Printer Settings, simply tick "Disable Bed after Print is Finished" .

yeah, i tried that, but it didn't seem to work properly. adding the kill line in end g code did the trick. now all i gotta do is find a way to get the bed up to temp quicker and automatically. big_smile

7 Reply by cckens

  • cckens
  • Member
  • Offline
  • Registered: 2012-09-13
  • Posts: 591

Re: any gcode command to turn off/change heated bed temp?

Try here:
http://www.soliforum.com/topic/1292/aut … bed-cover/

8 Reply by adrian (edited by adrian 2013-06-14 13:18:48)

  • adrian
  • Member
  • Offline
  • From: Canberra, Australia
  • Registered: 2013-01-15
  • Posts: 1,623

Re: any gcode command to turn off/change heated bed temp?

dkeeling728 wrote:

yeah, i tried that, but it didn't seem to work properly. adding the kill line in end g code did the trick. now all i gotta do is find a way to get the bed up to temp quicker and automatically. big_smile

Odd - seems to work fine on 100's of other printers. Maybe you should investigate that further, as its unusual for the printer to ignore a GCODE command from its print host... might be a sign of more serious goings on or something else not being done correctly since ticking that box simply adds the same GCODE to the end of print that your kill section does

If its ignoring a simple standard command that seems to operate on many many other printers... then one should surely get concerned as to what else its 'missing' in its normal operations?

Never been a fan of selective command execution... knowing that solid state electronics are certainly not 'selective' in their execution of code, if I don't get the same behaviour as 100's of others, I always stop and ask 'what am I doing different, or what is different with my hardware'.

Band-aid solutions are great... but like real-life Band-Aids... they tend to eventually fall off at the most inappropriate times...