grbl/grbl — Issue #74: Possible abort error
Author: mike-holmes
Created: 2012-03-06 19:49:16+00:00
State: open

I've found a bug in the abort function. I *think* it's caused if a lot of long commands (say, comments in brackets, or commands to 6 decimal places) are sent & acked, and an abort command is issued after this, then grbl stops responding.

What I mean by 'stops responding' is that any commands sent to the Arduino after the reset are received, but nothing is transmitted back.

This is the streaming file I used which gave me this error:

```python
import serial
import time

s = serial.Serial("com3",9600)

s.write('\n')
time.sleep(2)
s.flushInput()

f = "C:/Users/Michael/Desktop/Python/Corners.nc"
file = open(f)

idx=1
for line in file:
s.write(line)
print idx, s.readline()
if line.find("(End cutting path id: path3811)") >=0:
s.write('>\n')
print "aborted"
time.sleep(2)
break
idx += 1

while s.inWaiting():
print s.readline()

# Commands from here onwards cause Uno RX LED to light, but not TX LED
while(1):
s.write('\n')
time.sleep(1)
```

And here is the file I used which gives this error:
http://www.mediafire.com/?hsgrb5gy59km1h4

I have less verbose versions of this file which don't cause this bug but I thought this issue would be worth raising.

(Apologies if it's just my poor coding/understanding of grbl, by the way!)