Start G-code



  • Hi!

    Is there a way to execute some G-code juste before the file content is interpreted?

    I would like to add a purge/cleanup hotend cycle. I could use the Start G-code of the slicer, but I sometime use a different slicer, which means duplicating configs…

    A start.g file, as there are stop.g, cancel.g and so, would be nice.

    Thanks,


  • administrators

    You could create your own start.g file and then use M98 to invoke it from your slicer start gcode.



  • 😕 So simple… I don't have the reflex to use macros yet. This is new to me 🙂

    Thanks!



  • It would be nice to have a default start.g file that gets called automatically without the need to add anything to the slicer. This is especially useful for anyone selling a kit where they want to make the printer behave a specific way regardless of the end users slicer settings



  • While I understand the possible appeal Whitewolf describes, I think it is dangerous for the machine to do anything it is not explicitly commanded to do. The M98 in the start gCode in Slicer strikes a nice balance, because if a new user uses premade slicing profiles from the manufacturer, this can have the M98 line in it, but if a more advanced user wants to use their own slicer settings, they can have complete control and not have the machine perform additional unexpected actions.



  • @raykholo:

    While I understand the possible appeal Whitewolf describes, I think it is dangerous for the machine to do anything it is not explicitly commanded to do. The M98 in the start gCode in Slicer strikes a nice balance, because if a new user uses premade slicing profiles from the manufacturer, this can have the M98 line in it, but if a more advanced user wants to use their own slicer settings, they can have complete control and not have the machine perform additional unexpected actions.

    I underdstand what you are saying but the problem with that logic is it depends on a kit being added to every slicer.

    Advanced users can simply modify the start.g file if the start sequence does not perform as they wish.

    All of the XYZ davinci printers home all axes, move the head off to the side of the printable area and then heat and prime the nozzle then do a wipe down the edge of the bed before beginning any of the slicers gcode and of a kit developer wants to do any number of such things they should be able to.

    Advanced users are just that and have the ability to modify the printer to perform anyway they want to. they dont need a slicer to do so and we are not talking about a firmware that needs to be compiled … it is a single file they can modify or hit the delete button

    A kit developer can control the pause routine or the tool change routine through the firmware files or the slicers gcode scripts so it doesnt make much sense to say no to start routine unless you remove the ability for all... just like the advanced users can delete or modify any of the other available routines pause, resume, homeall etc


  • administrators

    If we did implement a start.g file, it would have to be executed before starting the file to be printed. Whereas operations such as bed probing are usually better done after the printer is up to temperature.



  • @dc42:

    If we did implement a start.g file, it would have to be executed before starting the file to be printed. Whereas operations such as bed probing are usually better done after the printer is up to temperature.

    Please do, its not needed in all situations for the bed to be up to temp.

    One question though, on the XYZ Davinci series before the slicer gcode the head is parked off to the side then the bed temp rises and the hotend temp rises then the head moves onto the bed then a prime and wipe down the edge of the bed.

    Are they reading the temps from the gcode ahead of time to accomplish this? and no this wasnt in my slicer start script it was part of the firmware


Locked
 

Looks like your connection to Duet3D was lost, please wait while we try to reconnect.