@Russellfam：请发布您的 $$ Grbl 设置和 $I 构建信息字符串。此类问题通常与设置有关。或者，如果您使用的是山寨版 Arduino，它的 USB 串行芯片有问题。

$I
[VER:1.1e.20170114:]
[OPT:V]

$$

$0 = 10（步进脉冲时间，微秒）
$1 = 25（步进空闲延迟，毫秒）
$2 = 0（步进脉冲反转，掩码）
$3 = 7（步进方向反转，掩码）
$4 = 0（反转步进使能引脚，布尔值)
$5 = 1（反转限制引脚，布尔值）
$6 = 0（反转探针引脚，布尔值）
$10 = 3（状态报告选项，掩码）
$11 = 0.010（结偏差，毫米）
$12 = 0.002（电弧公差，毫米）
$13 = 0（以英寸为单位报告，布尔值）
$20 = 1（软限位启用，布尔值）
$21 = 0（硬限位启用，布尔值）
$22 = 1（归位循环启用，布尔值）
$23 = 3（归位方向反转，掩码）
$24 = 25.000（归位定位进给率，毫米/分钟）
$25 = 600.000（归位搜索寻道率，毫米/分钟）
$26 = 244（归位开关去抖延迟，毫秒）
$27 = 1.000（归位开关拉离距离，毫米）
$30 = 1000（最大主轴速度，RPM）
$31 = 0（最小主轴速度，RPM）
$32 = 0（激光模式启用，布尔值）
$100 = 1280.000（X 轴行程分辨率，步长/mm）
$101 = 1280.000（Y -轴行程分辨率，步/毫米）
$102 = 1600.000（Z 轴行程分辨率，步/毫米）
$110 = 650.000（X 轴最大速率，毫米/分钟）
$111 = 800.000（Y 轴最大速率，毫米/分钟)
$112 = 400.000 (Z轴最大速率, mm/min)
$120 = 50.000（X 轴加速度，毫米/秒^2）
$121 = 50.000（Y 轴加速度，毫米/秒^2）
$122 = 30.000（Z 轴加速度，毫米/秒^2）
$130 = 865.000（X -轴最大行程，毫米）
$131 = 575.000（Y 轴最大行程，毫米）
$132 = 100.000（Z 轴最大行程，毫米）

@Russellfam: 没什么特别的。在我开始测试之前还有几个问题。你如何闪烁 Grbl？如果您正在编译，请告诉我您的 Arduino IDE 版本。您的 Arduino 是真正的 Arduino Uno 吗？如果不是，它是什么以及它上面的USB串行芯片是什么。应标记为 atmega16U 或 FTDI 或 CH380。

My guess would be electrical noise from the spindle coupling through your USB cable and causing a disconnect.
Has this only just started happening? If so have you moved any of your cables around?
Do you have any noise filtering, in particular a ferrite on your USB cable? If not, dig around and see if you have a USB cable with a ferrite. The ferrite looks like a lump on the cable. You can also buy clip on ferrites from various electronics suppliers.
See https://www.google.com/search?q=ferrite+usb+cable&tbm=isch for sample images

Hey, thanks for the replies.
I flashed it from the hex file using Xloader
The board is an arduino uno Funduino and the serial is the WEGA16U2

I’ve recently upgraded the GRBL and the UGS. Since then I’ve cut several similr profiles with no issues. this problem started this afternoon and I’ve changed nothing on the system.

@Russellfam : I’ve been running your job on two different Arduinos with the same firmware build and your settings (with soft limits turned off). I’m streaming the program with the stream.py script in the Grbl repo to determine if it’s GUI related. So after 3 runs each for a total of 6, no locking up so far.

Grbl v1.1’s interface was updated to contain more realtime information, so

Whoops.. Accidental click.

Grbl v1.1’s interface was updated to contain more realtime information, so it might be a GUI bug. I’ll keep running the job and will report a lock-up, if I run across one.

thanks for the help…sure hope we can solve this

Are you using UGS platform? Have you tried Grbl Panel or BCNC? Any difference?

using UGS not UGS platform and I’ve not tried the others. I will do so today and let you know

OK so I’ve been running on the UGS platform and it seems ok on that. being a Sunday I cannot fire up the router and dust extractor I’ll check tomorrow and let you know.

I had a quick run now and I have some headway to the problem. If I turn the router on the arduino locks up within a few seconds (5 or 10 seconds). It would seem that there might be electrical interference from the router causing a break down in the serial communication. I’ll hunt around for a ferrite USB cable and see if that solves the problem…The laptop is running on battery and the arduino is running from the laptop USB and so isolated from any mains electricity.

I tried with a different cable a short while ago and that seems to have solved the issue. I dont have any with ferrite, but the one I used is a lot shorter.

@Russellfam : Thanks for the update. I think only UGS platform supports Grbl v1.1 so this was probably the likely cause.

@chamnit from everything @Russellfam describes this was an EMI issue. I’ve seen it several times on various machines with the USB just dropping communications when the spindle starts running. Sometimes the serial port disappears, but not always. Changing the cable, or adding a clip-on ferrite almost always fixes it, but sometimes it takes re-routing the wiring and fixing grounding.
The issues with old version of UGS wouldn’t have helped, and may have added to difficulty pinpointing the true issue. EMI is harder to debug than software

@electrokean: 我想，但如果它在更新到 v1.1 之前运行良好，那么它很可能与该更新有关。AFAIK，常规 UGS 不支持 Grbl v1.1，只有 UGS 平台支持。这可能会解释工作开始时的失败，当旧的 UGS 得到一些反馈时，新的 v1.1 界面没有预料到。无论哪种方式，USB EMI 始终是一个疑点，而且似乎已经解决了。