Hello Casper the Ghost! I doubt that duncing has anything to do with your recurring problem, because there are lots of ways for such problems to crop up, and many of them aren’t easy to figure out without some experienced assistance. I’m just barely an amateur from the CNC woodworking realm, but let me enlighten you on just a FEW of the “hidden” possibilities that I’ve heard:
• Shielding on the communications cable between PC and CNC MIGHT be faulty.
• Communications between PC and CNC on USB MIGHT be too slow.
• A configuration setting (like Lookahead) MIGHT be too small.
• A version upgrade of windows 10 MIGHT upset the CNC software.
• An incomplete upgrade of a new windows version MIGHT upset the CNC software.
• Using a memory stick instead of hooking a PC directly to the CNC MIGHT be the culprit.
While my suggestion list below might be incomplete, let’s see if it gets others with tons more smarts a place to begin with some serious help:
• Share what operating system your PC is using, what software is generating the gcode (i.e. Aspire 9), and what software is reading and converting that gcode into CNC machine movements.
• Let us know what brand and model your CNC is, and whether you’ve talked to the manufacturer.
• When your gcode “corrupts”, does it always do so at the same line of code?
• Can you provide a screen snapshot and/or more info about the “crash” occurs?
Thanks for your patience - and hang in there!