Assistance with editing PAUSE.G and other files



  • Hello, I have encountered an issue regarding the usage of pause.g and filament-change.g.

    1. If during a pause there is a power cut the X and Y coordinates are saved but the Z coordinate gets an extra 5mm, therefore when the sending M916 the print continues well, except it pours filament 5mm too high over the model.

    2. If the print pauses due to a signal received from the filament runout sensor (Trianglelab), it doesn't invoke filament-change.g but it invokes pause.g. M600 does work properly and invokes filament-change.g. In addition, if an M291 is contained inside the pause.g the message of "Extruder # reports no filament" is not being shown. Furthermore, if an M291 with S2or3 is used, then the print resumes automatically when that message pops to the display. (without pressing on the resume)

    3. I would appreciate it if someone knowledgeable than me could advise how to edit the pause.g and resume.g thus it will cool down the hotend but remembers the standby and active temps and works well for dual colour prints with two tools.

    Perhaps a G60 would be useful?

    Printer Modix3d Big120Z
    The firmware version is 2.05
    Files are attached

    Hope my English has been understandable enough,
    Thank you very much

    resurrect-prologue.g resume.g pause.g Filament Change (during print).g config.g


  • Moderator

    I can see why if there was a power outage during a pause that the resume wouldn't return to the correct Z height because the pause raises the Z height by 5, and then that z height would be saved during the power outage, and then when it resumes, it has lost that original height. I'm not sure how to work around that.

    I don't think filament runout was every intended to trigger filament-change.g that was added along with M600 with the intention of being added by the slicer to allow for filament changes.

    I'm also not too sure about calling M291 during a pause.

    I'll see if DC42 can take a look.

    I see you are using firmware 2.05. You may want to look at upgrading to RRF3 so that you can take advantage of conditional gcode which may make what you want to do a lot easier.



  • At the moment I prefer to stick with 2.05.1, but I have already installed RRF3 on one of my printers and have started to get familiar with the new coding style.

    Thank you for the clarifications, I will try to re-edit once more both config.g and pause.g to see if I can walk around that.


  • Moderator

    @ELAD If your filament sensor is a simple switch, you could set it as an external trigger to run a filament change. See M581 https://duet3d.dozuki.com/Wiki/Gcode?revisionid=HEAD#Section_M581_Configure_external_trigger

    Ian


  • administrators

    @ELAD said in Assistance with editing PAUSE.G and other files:

    1. If during a pause there is a power cut the X and Y coordinates are saved but the Z coordinate gets an extra 5mm, therefore when the sending M916 the print continues well, except it pours filament 5mm too high over the model.

    That might be caused by the G1 Z5 move in your resurrect-prologue.g file, along with the fact that you are not homing Z. Try reversing that movement at the end of the file.

    1. If the print pauses due to a signal received from the filament runout sensor (Trianglelab), it doesn't invoke filament-change.g but it invokes pause.g.

    That is intentional. File filament-change.g is only invoked in response to M600, which is for use within a Gcode file where a manual change of filament colour is wanted. We are considering defining a separate macro file to be invoked when a filament sensor indicates a filament problem.

    In addition, if an M291 is contained inside the pause.g the message of "Extruder # reports no filament" is not being shown.

    Is this on PanelDue, or in DWC? PanelDue can only track and display a single popup message at a time.

    Furthermore, if an M291 with S2or3 is used, then the print resumes automatically when that message pops to the display. (without pressing on the resume)

    That sounds odd. I will see if I can reproduce it in firmware 3.1.1.

    1. I would appreciate it if someone knowledgeable than me could advise how to edit the pause.g and resume.g thus it will cool down the hotend but remembers the standby and active temps and works well for dual colour prints with two tools.

    I don't think there's a way to do that yet, although you can get close to it using conditional GCode in RRF3. The mechanism would be to command a reduction in temperature by a fixed amount (e.g. 200C) using conditional GCode. Then increase it again by the same amount in resume.g. When we introduce variables into RRF3 conditional GCode, it will be more straightforward.

    Meanwhile, in RRF2 you can set the active tool to standby using T-1 so that at least the temperature of the active tool drops to the standby temperature. Then use command T R1 in resume.g to active it again.

    Perhaps a G60 would be useful?

    In what way? G60 saves the current position, but not the temperatures.

    HTH David


Log in to reply