Jump to content

Start.gcode: Bed and heater is turned on before you get a chance to fire M80


dumle29

Recommended Posts

Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

So, I am currently setting up an i3 with RAMPS 1.4, and an ATX PSU. The ATX standard calls for at least 500mA standby current, and the PS_on wire is hooked up to the PS_on connector on the RAMPS board. M80 and M81 successfully turns on and off the PSU with manual control, but when your Gcode comes along and tries to turn on the heated bed and hotend on your 500mA standby current, well you loose power.

So request: Have the start.gcode actually be put in the beginning of the gcode, and have the default contents of start.gcode to be:

 


;Generated with {slicer}
M140 S{bed_temp}
M109 T{extruder0} S{hotend0_temp}
T{extruder}
M190 S{bed_temp}
;Sliced at: {day} {date} {time}
;Basic settings: Layer height: {layer_height} Walls: {wall_thickness} Fill: {fill_density}
;Print time: {print_time}
;Filament used: {filament_amount}m {filament_weight}g
;Filament cost: {filament_cost}
G21 ;metric values
G90 ;absolute positioning
M107 ;start with the fan off
G28 X0 Y0 ;move X/Y to min endstops
G28 Z0 ;move Z to min endstops
G1 Z15.0 F{travel_speed} ;move the platform down 15mm
G92 E0 ;zero the extruded length
G1 F200 E5 ;extrude 3mm of feed stock
G92 E0 ;zero the extruded length again
G1 F{travel_speed}
M117 Printing...

Where {slicer} would output something like: Cura_SteamEngine 13.10

 

  • Link to post
    Share on other sites

    Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

    The start gcode is included in the output file (unless you specify Ultigcode as your machine type, iirc). And you're free to edit the start gcode in Cura and have it do whatever you want in your particular case.

    What I don't entirely understand is what you are trying to achieve by editing the start gcode in this way - how is this practically different from the standard start gcode?

     

  • Link to post
    Share on other sites

    Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

    You can add:

    M104 S{print_temperature}

    M190 S{print_bed_temperature}

    M109 S{print_temperature}

     

    To the start code, and get the behaviour you want. And it will no longer add the own temperture commands as it sees you have the proper tags in the start code.

     

    Why this is not default? Well, because not everyone has a heated bed or uses a heated bed, at which point the M190 commands do not need to be added or the printer will hang on that.

    (Yes, there is logic to the mess, really)

     

  • Link to post
    Share on other sites

    Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

    Ahh thanks Daid: It is late, and for some reason I read the commented out section as a sort of legend for available {tags}

    :p

    Thanks for the help :)

     

  • Link to post
    Share on other sites

    Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

    If you save your profile as an ini file and look in there - pretty much anything in there can be a {} tag in your stat or end gcode settings.

     

  • Link to post
    Share on other sites

    Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

    I've patched up the default code to have commented M109, M190 commands explaining that you can uncomment those to use them. As this has been asked multiple times.

    (Basic rule, if multiple people ask for the same feature that is already in the software, then the feature is not accessible enough)

     

  • Link to post
    Share on other sites

    Posted · Start.gcode: Bed and heater is turned on before you get a chance to fire M80

    Sounds great :)

    As a little note, it turned out that standby current is actually available on a seperate 5v standby rail, which I hadn't checked prior to posting this :/ silly me. Still I learned what can be done with the start / end gcode files :)

     

  • Link to post
    Share on other sites

    Create an account or sign in to comment

    You need to be a member in order to leave a comment

    Create an account

    Sign up for a new account in our community. It's easy!

    Register a new account

    Sign in

    Already have an account? Sign in here.

    Sign In Now
    • Our picks

      • UltiMaker Cura 5.7 stable released
        Cura 5.7 is here and it brings a handy new workflow improvement when using Thingiverse and Cura together, as well as additional capabilities for Method series printers, and a powerful way of sharing print settings using new printer-agnostic project files! Read on to find out about all of these improvements and more. 
         
          • Like
        • 18 replies
      • S-Line Firmware 8.3.0 was released Nov. 20th on the "Latest" firmware branch.
        (Sorry, was out of office when this released)

        This update is for...
        All UltiMaker S series  
        New features
         
        Temperature status. During print preparation, the temperatures of the print cores and build plate will be shown on the display. This gives a better indication of the progress and remaining wait time. Save log files in paused state. It is now possible to save the printer's log files to USB if the currently active print job is paused. Previously, the Dump logs to USB option was only enabled if the printer was in idle state. Confirm print removal via Digital Factory. If the printer is connected to the Digital Factory, it is now possible to confirm the removal of a previous print job via the Digital Factory interface. This is useful in situations where the build plate is clear, but the operator forgot to select Confirm removal on the printer’s display. Visit this page for more information about this feature.
        • 0 replies
    ×
    ×
    • Create New...