stop.g now automatic
-
Can the 3.5 release notes highlight that stop.g runs automatically now at the end of a print job, regardless of M0 or not. It has caused me some aggravation and I've eventually found the italics note at https://docs.duet3d.com/User_manual/Reference/Gcodes#m0-stop-or-unconditional-stop but I don't think it is mentioned in the changelog at https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x-RC .
Arguably the statement "When the job completes the secondary file stream is closed and commands in the stop.g file for both motion systems are executed by the primary stream." could be interpreted as indicating this, but firstly I read it as being about independent motion streams and not relevant if you only have one, and secondly I'd probably still read it as having an implicit 'if you asked for it' rather than a 'whether you ask for it or not'.
Adding When a print file completes normally then file stop.g is run automatically even if the print file did not end with a M0 command to the changelog would help.
-
it's documented in https://github.com/Duet3D/RepRapFirmware/wiki/Changelog-RRF-3.x#reprapfirmware-351-stable-changes-since-346 as a standalone bullet point:
When a print file completes normally then file stop.g is run automatically even if the print file did not end with a M0 command
-
@oliof OK, my mistake. Thanks.
I assume the 'not' in the very next bullet is intended to be 'now'?
-
@achrn no, it means "not". Previously, M0 was needed, now it's not.
-
@oliof It said "File stop.g is not only run when a print completes."
It has been corrected to "File stop.g is now only run when a print completes."
-
@achrn sorry I thought you were referring to my quote.
