Forum Navigation
Observation on errors
#1 · May 23, 2018, 4:18 pm
It seems that if there's a problem transmitting code to the cutter the underlying python process doesn't necessarily exit, but hangs around.
Subsquent attempts to access the grbl interface can fail because this process still has the com port open. Killing the process will restore things to normal.
#2 · July 13, 2018, 8:55 pm
This must be due to comms errors. Check for ground loops via the USB cable. K40s chassis need to be grounded (some are floating and potential dangerous). We have seen plastic washers under the ground connection (who assembles these?).
Cheers,
Paul
awesome.tech