Not sure how to detail this so I’ll begin:
Things appeared to be working with jog commands from UGCS and hand typed M4 commands to test the laser.
So I attempted to send a gcode file that had a simple square, very short.
But, now grbl just goes into hold state.
Using Putty and sending ? gets
![[gnea/grbl-Mega Issue#1] $ command extentions](https://www.grblhal.com/wp-content/themes/gitphp/timthumb.php?src=https://www.grblhal.com/wp-content/themes/gitphp/assets/img/pic/3.jpg&h=110&w=185&q=90&zc=1&ct=1)
![[gnea/grbl-Mega Issue#2] Better interrupt priorities](https://www.grblhal.com/wp-content/themes/gitphp/timthumb.php?src=https://www.grblhal.com/wp-content/themes/gitphp/assets/img/pic/2.jpg&h=110&w=185&q=90&zc=1&ct=1)
![[gnea/grbl-Mega Issue#3] ATMega16U2 virtual com port on ATMega2560](https://www.grblhal.com/wp-content/themes/gitphp/timthumb.php?src=https://www.grblhal.com/wp-content/themes/gitphp/assets/img/pic/4.jpg&h=110&w=185&q=90&zc=1&ct=1)
#1 – bdurbrow 于 2018-11-22
From report.c: 0 means it’s “ready to resume”; 1 means it’s “actively holding”… I’m suspicious that you may have something triggering the feed hold pin.