I've been trying for 2 nights now to get a simple gcode file to

(Tristan Escalada) #1

I’ve been trying for 2 nights now to get a simple gcode file to execute. I can jog the spindle around, zero it out, and home it just fine. But nothing I do seems to get it to run the gcode. I noticed next to the play button there is a little clock icon that says that it is being asked to pause sending commands to not overrun the buffer. However, on the grbl panel it says the state is idle and it responds right away while jogging the spindle, and that panel also has the clock icon.

I moved the spindle into position, zeroed my axes, loaded my gcode and hit play. I expect it to begin cutting but nothing happens.

Where can I look for debugging information? It seems like somewhere it is getting the idea that the cnc is busy, but it is idle.

Any pointers would be greatly appreciated.

(Justin Adie) #2

You’ve not provided much information.

What controller are you using? What workspace? What version of spjs? What browser? What OS?

Since you are getting some movement from the controller using cp then logically you have some communication. Have you analysed the serial traffic or checked for JavaScript errors?


Screenshots help convey tons of data. I suggest turn off filter/funnel icon in serial port console to show all info from your controller.

(Tristan Escalada) #4

Sorry, been a long day…

controller: grbl 1.1f
workspace: jpadie
spjs: 1.95 running on a raspberry pi
browser: chrome 70.0.3538.110 (64-bit) on macos.

I haven’t checked the serial traffic. Is there a recommended way of doing that? In the browser there are several js errors but I’m not sure if they are related.

I think they are all errors relating to 404s on several items.

This error seems maybe interesting
require.js:166 Uncaught Error: Load timeout for modules: inline:com-chilipeppr-elem-zipwhip,inline:org-jscut-gcode-widget,inline:com-chilipeppr-elem-gcodedata


Those JavaScript errors are ok. They’re for modules that aren’t critical and wouldn’t hurt anything if they don’t load.

(Tristan Escalada) #6

missing/deleted image from Google+

(Tristan Escalada) #7

missing/deleted image from Google+

(Tristan Escalada) #8

missing/deleted image from Google+


Ok, serial port console info looks good. Now what does it look like when you hit play in the Gcode widget?

(Justin Adie) #10

I tend to use the verbose mode in spjs to check serial traffic.

(Justin Adie) #11

But as John says. That looks fine. You have comms.

(Tristan Escalada) #12

missing/deleted image from Google+

(Tristan Escalada) #13

Not sure if the gcode matters, but here it is.

(T1 D=2.38 CR=0 - ZMIN=-5.5 - flat end mill)
G90 G94
G28 G91 Z0

T1 M6
S5000 M3
G0 X0 Y55
G1 Z-5.5 F333.3
G0 Z5
G1 Z-5.5 F333.3
G0 Z5
G28 G91 Z0
G28 G91 X0 Y0

(Tristan Escalada) #14

I think the second screenshot I did hit play. It seems to have no effect on the output being generated.


Hmm. Yeah, I see no gcode being sent in that serial port console in the screenshot if indeed you took that after hitting play. What happens if you expand the Gcode widget (use the down arrow 2nd button from right) and see if it follows the lines of gcode as it sends them.

(Justin Adie) #16

@jlauer do you know which widget is pulling in those dead links? I can fix them if so.

(Tristan Escalada) #17

That button does nothing. The one on the far right opens a blank box just below.
missing/deleted image from Google+

(Tristan Escalada) #18

Here are all the js errors. I set it to show error level only, theres a ton of info in debug.
missing/deleted image from Google+

(Tristan Escalada) #19

missing/deleted image from Google+

(Tristan Escalada) #20

I got spjs running in the foreground with -v. heres the gist of the part of the logs that keeps repeating in a decently fast loop. https://gist.github.com/tescalada/233919bc2dd59b379f3b891b302f5b22