UGS: "Error While Processing Response"

[easyar15dotcom]

Looking for some help with a UGS error.

Quick background:

-Initially installed UGS with a new M3 purchase.
-Worked fine for a short time then started to receive a looping "Error While Processing Response" when connecting the COM/baud.
-Only way to clear the issue is with a full restart of the computer.
-Couldn't find a clear solution with internet searches and switched to the paid version of PicSender.


I would like to go back to UGS and am wondering if anyone else has seen this issue before?  Wondering if its a $$ issue because the same error occurs no matter what UGS build I am running (UGS vs Platform vs Stable vs Classic).
*If this seems like a GRBL/UNO issue to any of you, is there a way to update my UNO board to a more compatible version?  I have seen comments about "flashing" but I'm totally lost on what that is or how to do it.

Attached below are my $$ settings:


$0=10 (step pulse, usec)


$1=255 (step idle delay, msec)


$2=0 (step port invert mask:00000000)


$3=0 (dir port invert mask:00000000)


$4=0 (step enable invert, bool)


$5=0 (limit pins invert, bool)


$6=0 (probe pin invert, bool)


$10=2 (status report mask:00000010)


$11=0.010 (junction deviation, mm)


$12=0.002 (arc tolerance, mm)


$13=1 (report inches, bool)


$20=0 (soft limits, bool)


$21=0 (hard limits, bool)


$22=0 (homing cycle, bool)


$23=0 (homing dir invert mask:00000000)


$24=25.000 (homing feed, mm/min)


$25=600.000 (homing seek, mm/min)


$26=244 (homing debounce, msec)


$27=4.000 (homing pull-off, mm)


$100=40.000 (x, step/mm)


$101=40.000 (y, step/mm)


$102=40.000 (z, step/mm)


$110=8000.000 (x max rate, mm/min)


$111=8000.000 (y max rate, mm/min)


$112=6000.000 (z max rate, mm/min)


$120=250.000 (x accel, mm/sec^2)


$121=250.000 (y accel, mm/sec^2)


$122=500.000 (z accel, mm/sec^2)


$130=264.000 (x max travel, mm)


$131=264.000 (y max travel, mm)


$132=69.000 (z max travel, mm)


ok

[Derek the Admin]

When do you get this error? Also, your settings are wrong.

10 should be 3
13 should be 0 (This should be okay this is the flag to report inches instead of mm). I would suggest doing that back to 0 though for a bit just to see if it is related.
102 should be 80
112 should be 3000
122 should be 250

[easyar15dotcom]

The error appears as soon as I connect to the COM.

I will open my $$ settings in PicSender and make those edits you suggested.

[Bruce]

I found this on the UGS issues forum: github.com/winder/Universal-G-Code-Sender/issues/974

Are you using Win10? What GRBL version are you using also?