I have seen this issue as well; sometimes only the first 2048 bytes of a file are written to the SD card, with no file error during the transfer. The file is just truncated at 2048 bytes. I've had this happen with several ftp apps.

FYI - I've started using a free app called GoodSync (https://www.goodsync.com) that can synchronize a folder tree on a computer with the folder tree on the Duet using ftp. It has the option to use file checksums to do the comparisons, so you're always sure that the files end up on the Duet correctly. It also has good filtering options to control which files get pushed.

I have seen this issue as well; sometimes only the first 2048 bytes of a file are written to the SD card, with no file error during the transfer. The file is just truncated at 2048 bytes. I've had this happen with several ftp apps.

FYI - I've started using a free app called GoodSync (https://www.goodsync.com) that can synchronize a folder tree on a computer with the folder tree on the Duet using ftp. It has the option to use file checksums to do the comparisons, so you're always sure that the files end up on the Duet correctly. It also has good filtering options to control which files get pushed.

@phaedrux Thanks for the link!

@dc42 That sounds like it will do exactly what I want, thanks!

(Assuming you meant M581 and M582? Those are listed in the current docs; is 2.03beta required, or will they work in the current release build?)

@dc42 Awesome! Thank you!

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

@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

And that is also called when a print is canceled?

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

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

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