Indication of print in progress

[DocTrucker]

I'd consider using the ps_on signl then. Either directly if your not making use the safety features to kill the heaters in a fault, or take a feed from that as an enable. I think there are start and stop macros on the duet? Trigger the ps_on from there, and it can also be dropped on a fault.

[DocTrucker]

Yeah, so perhaps call a start.g from your gcode and then drop or raise the signal in the pause/cancel/resume g code scrips:

https://duet3d.dozuki.com/Wiki/Macros#Section_Pause_stop_and_power_fail

It doesn't have to be the ps_on signal, I'd recommend keeping that for killing the VIN power supply. Perhaps just trigger a fan output between 0 and 100% duty.

[rubillos]

Are there start and stop macros? I didn't see them in the docs... if there are then that would solve my problem.

[DocTrucker]

I think you need to call the start macro but look at the link for pause cancel and resume. Edit: + stop and sleep.

[rubillos]

I guess I could do start and stop in the slicer gcode, but also have the codes in pause/cancel/resume.

Was hoping there was a start macro... there's always poking around in the source code and doing a custom build

[dc42]

Another way would be to configure the RPi as an HTTP client and have it make rr_status requests to the Duet. The response includes whether or not a file is being printed.

[DocTrucker]

The automatic call of an optional start.g gcode does seem like an ommision. @dc42 is there anything on the horizon?

[rubillos]

@dc42 has having start.g and end.g files ever been considered? Is there any reason not to have those?

[DocTrucker]

@rubillos end.g = stop.g

[rubillos]

And that is also called when a print is canceled?

[DocTrucker]

The http method @dc42 recommends has a few benefits.

• No extra wiring or failure points.
• If in the (unlikely) event of a process hang the http will stop responding and you can cancel your capture.

[DocTrucker]

@rubillos https://duet3d.dozuki.com/Wiki/Macros#Section_Pause_stop_and_power_fail

[dc42]

@doctrucker said in Indication of print in progress:

The automatic call of an optional start.g gcode does seem like an ommision. @dc42 is there anything on the horizon?

I implemented this many releases ago.

[dc42]

@rubillos said in Indication of print in progress:

And that is also called when a print is canceled?

No, cancel.g is called instead.

[DocTrucker]

@dc42 documentation hasn't caught up yet.

[rubillos]

@doctrucker True. That might be the way to go... I'll have a look at modifying my time-lapse code.

There are just so many I/O pins on the Duex5, seemed like an easy thing to hook up

[rubillos]

@dc42 So start.g is called when a print starts?

[dc42]

@rubillos said in Indication of print in progress:

@dc42 So start.g is called when a print starts?

Yes, whenever a print from SD card starts. I have updated the documentation at https://duet3d.dozuki.com/Wiki/Macros.

[rubillos]

@dc42 Awesome! Thank you!

[Phaedrux]

@resam has a raspberry pi camera solution as well, though I can't seem to find the thread at the moment.