Hello, and thank you to everyone who has contributed to or supports this community. I am newish to cutting and have enjoyed my time with Inkscape and Inkcut.
I am having an issue though. Inkcut performs perfect cuts with my cutter until after 1.5 minutes or so. I have tried a range of things - I doubled graphics within a single SVG file. I have also tried using the duplicates tool within Inkcut. It cuts great at first, then randomly slows down, sounds almost glitchy and takes forever to finish the cut.
Lately I have been cutting smaller chunks, then exiting the app, relaunching it and continuing and this method works well for smaller graphics.
I read somewhere about a potential Python error for a ??MaxResource?? flag, or some limitation that was taking place against the user. I also had someone recommend that the memory of one cut was not getting dumped before the next, though I was not sure if this would be the case if there is a single SVG file containing multiple cuts because it would be seen as one file.
System & Setup:
Debian Linux, Python 3 / Python3.6 Pip3
Inkcut 2.* w/ Inkscape
Thinkpad; 8gb's RAM, 720gb HD, quad core processor w/ integrated graphics
Red Sail Vinyl Express R Series II
Vinyl Cutter using settings recommended from manual (baud rate 9800, 1 step, H protocol, XON/XOFF, etc)
Other things I have tried: I tried a few different drivers, protocols, etc - the error seems to be consistant no matter what settings I put into place (within Inkcut) and no matter which driver I choose. I also tried running the inkcut command in Linux as nice -n 18, for a higher priority, however I did not see any change - again, after about a minute or minute and a half, it will slow down substantially and sounds nearly glitchy.
It does seem to me like a resource is becoming full, or a limitation somewhere is being set, probably in the Linux system or with the user. I added the user to dialout group and adjusted the permissions for the ttyUSB0 port. I have great connectivity to the plotter - I can use Inkcut's virtual controls to adjust the blade, position, etc. Cuts also complete without error - even when the glitch takes place.
Any suggestions??? Anyone had this error before? I have been able to work around the error with smaller cuts, and I perform a cut - restart the app, and then I can reposition my blade and perform the next cut, reset the app and repeat. Though this has been daunting, and if I had any larger of graphics to cut it would be huge wait times. I find it interesting that relaunching the app stops the error momentarily. It certainly seems like a resource is getting filled up so to say..