Ok, here's one I have been unable to find any info on. Everything has been working fine with my setup for a while now. It's a leadscrew router using an Openbuilds BlackBox and a Windows 10 machine with the current version of Openbuilds Control. Firmware on the blackbox is also current. The last two jobs I ran both failed with the router running, no motion/no gcode being sent, and the pc still connected. First time was the popup box and the second time was with no popup, just the werror:255. First time it was running for about 75min with 15 to go. Seems like there may be a communication error but nothing has changed with the setup and I'm using the FTDI drivers. Windows is giving no USB errors. Could it be a problem with the blackbox? Any ideas?
Could be but doesn't explain why this just started after months of no problems. All the wires are shielded and grounded on box end, ferrite cores on all cables, and openbuilds limit switches. Dust collection has a ground wire.
Run some air-cut tests with router/dust off. The symptoms are clear (at this time), werror is not a string Grbl emits, but scrambled bits could mess up a different character to look like a w, the error would be in response to the corrupted data going the other way
