TinyG/CoolTerm crashing NOT solved

Not saying that you shouldn't spend time attempting to find bugs, and I'm sure Riley/Alden appreciate any help they can get etc..
BUT..
I said... "It hurts when I touch my eye"..
My mom said.. "Then don't touch your eye..

Maybe you should just use the e-stop button or find another way to stop the machine mid cycle instead of repeatedly breaking bits over and over again.

OR take a few days off and send your board back to Synthetos and let them upgrade your firmware.. I'm sure they would be happy to do that for you since you have repeatedly complained about not being able to do so..
Then you can run tgfx or whatever you want and not have to mess with coolterm that is obviously causing you problems over and over again..

And now the exclamation point does nothing.

posx:11.180,posy:-6.653,vel:199.995
posx:11.582,posy:-5.929,vel:199.995
posx:11.928,posy:-5.196,vel:199.995
posx:12.230,posy:-4.443,vel:199.995
!
posx:12.487,posy:-3.657,vel:199.995
posx:12.692,posy:-2.872,vel:199.995
posx:12.846,posy:-2.076,vel:199.995
!
posx:12.952,posy:-1.271
posx:13.006,posy:-0.446
posx:13.010,posy:0.365,vel:199.995
!
posx:12.962,posy:1.175,vel:199.995
posx:12.864,posy:1.980,vel:199.995
posx:12.712,posy:2.793,vel:199.995
!
posx:12.515,posy:3.580,vel:199.995
posx:12.267,posy:4.353
posx:11.973,posy:5.108,vel:199.995
!
posx:11.625,posy:5.859,vel:199.995
posx:11.238,posy:6.572,vel:199.995
posx:10.807,posy:7.259,vel:199.994
posx:10.335,posy:7.931,vel:199.995
!
posx:9.811,posy:8.559,vel:199.995
posx:9.259,posy:9.153,vel:199.995
posx:8.672,posy:9.712,vel:199.994
posx:8.038,posy:10.244,vel:199.995
!
posx:7.385,posy:10.725,vel:199.994
posx:6.703,posy:11.164,vel:199.995
posx:5.995,posy:11.560,vel:199.995

>Not saying that you shouldn’t spend time attempting to find bugs

Thanks for responding Mcgyvr. You have the wrong idea. I'm certainly not looking for bugs. I'm just trying to get an important project done. Ought to be pretty simple.

>My mom said.. “Then don’t touch your eye..

Yes, I'd like to stop poking myself in the eye. But I have a project I started in November, the reason I bought the TinyG, is DUE next week. Due as in I'm royally screwed if this isn't done. I'm talking "thousands down the toilet" screwed.

>Maybe you should just use the e-stop button or find another way

Certainly a fine idea, except, this is the best I have found. If Riley or Alden have suggested a solution, I didn't see it.

> I’m sure they would be happy to do that for you since you have repeatedly complained about not being able to do so..

If that was an option, why didn't someone say so two months ago? Have I not made it clear there is something very wrong here?

Anyway, I appreciate that you wrote back. Sometimes I feel like I'm all alone here.

>Gcode is modal – the gcode interpreter must have been in a G2 or G3 arc command before entering the z5′s.

Yes, I said this gcode draws 24mm circles. That's all there are are G3s.

>The arc specification error is Gcode telling you that the command is not a full specified arc.

That was my assumption.

>When you entered the G0 Z0 command you changed to traverse mode.

Yes, it should have. So then why didn't it go to X5? That has been the behavior until today. IF I enter a malformed G3, I get an error. After that, it should respond normally to commands, but didn't.

>Was X5 Y11.336 a target of the previous arc?

I posted the gcode in the previous message on this topic. It is:

G0 X13.015 Y0.0
G1 F333.0 Z-0.9
G3 F200.0 X-6.5075 Y11.2713 I-13.015 J0.0
G3 Y-11.2713 I6.5075 J-11.2713
G3 X13.015 Y0.0 I6.5075 J11.2713
G1 F333.0 Z-1.8
G3 F200.0 X-6.5075 Y11.2713 I-13.015 J0.0
G3 Y-11.2713 I6.5075 J-11.2713
G3 X13.015 Y0.0 I6.5075 J11.2713
G1 F333.0 Z-2.7

And forgive me for pointing out that you did not address the substance of my message. Quote: "Note at the bottom, when I manually enter a “G0Z0″, and TinyG responded by sending my cutter to x5y11 at high speed, breaking the bit!"