Toshiba Flashair SD Card Mapped in Windows

[ServiceXp]

I have 4 flashforges set up like this. It works ... kinda, I have issues with big files. The best thing I can think of is to not use mapped drives, but rather, dump the gcode 3xg files into a single directory and write a script to load the last written file to a network path - this keeps windows from accessing the drive when the printer is printing - which I think is a very valid concern - if the sd card is tied up talking with windows, the 3d printer controller may have an issue reading.

In the end, I'll likely write a program to manage printing - then again, I'll likely roll my own solution with a combination of optoprint controllers and flashair cards and a windows program to roll it all together - so I can manage afleet of printers.

Interesting, I've not run into any problems with big files yet, but I've only completed 9 or 10 prints using this method. At what size and what problems are you seeing with this mapped drive method? How long have you been using this method?

I just thought of a test to see what locks, if any, the firmware is placing on the files being used. I suspect there are no locks and hence the possibility of problem, just not sure of what those problems are. I've written/deleted both files and folders while the machine was printing, and rebooted the machine with the mapped drive, also let it sleep and have not seen any disruptions in the printer. I have not however messed with the current file being printed.

[ServiceXp]

Interesting, I've not run into any problems with big files yet, but I've only completed 9 or 10 prints using this method. At what size and what problems are you seeing with this mapped drive method? How long have you been using this method?

I just thought of a test to see what locks, if any, the firmware is placing on the files being used. I suspect there are no locks and hence the possibility of problem, just not sure of what those problems are. I've written/deleted both files and folders while the machine was printing, and rebooted the machine with the mapped drive, also let it sleep and have not seen any disruptions in the printer. I have not however messed with the current file being printed.

OK so after a bit of testing/experimenting this is what I've discovered. There are no file locks (at least none that Windows 10 honors) being placed on the current file being printed. Small files (not sure of the size breakpoint here) are completed loaded into memory, and can be deleted from the SD card after the print starts. This worked for the files under 1meg I tested.

Files over 10 megs:
1) there are no file locks (at least none that Windows 10 honor) being placed on the current file being printed.
2) Renaming the file, then renaming back does not effect printing.
3) Renaming the file and leaving it for 10 seconds does not effect printing.
4) Coping and pasting the same file that is being printed does not effect printing.
5) Renaming the file and leaving it causes the print to fail. (as would be expected)
6) Deleting the file after print has started causes the print to fail. (as would be expected)

All-In-all, fairly robust all things considered. It would be nice to have some file locks, but......

[Darsonval51]

16gb Flashair ordered.