#linuxcnc-devel Logs

Sep 03 2018

02:42 AM rmu|w: pcw_home: i'm also stuck trying to get my own kernel to boot
02:45 AM rmu|w: pcw_home: my motivation is that in theory, you should have more direct control of the hardware and latencies on an arm core than on a PC where all sorts of strange layers of management code can interfere, and i'm just exploring a little bit ;-)
08:27 AM jepler: afk, goodnight
08:27 AM jepler: er good morning
08:29 AM Jin^eLD: ))
10:16 AM seb_kuzminsky: M66 interacts poorly with Abort
10:16 AM seb_kuzminsky: http://linuxcnc.org/docs/html/gcode/m-code.html#mcode:m66
10:17 AM seb_kuzminsky: if linuxcnc is waiting on an M66 and you Abort, and then Run, it immediately restarts the wait
10:18 AM seb_kuzminsky: before running the first g-code in the program
10:18 AM seb_kuzminsky: this is in master
10:18 AM seb_kuzminsky: dont know if it also happens in 2.7
10:19 AM jepler: yuck
10:20 AM seb_kuzminsky: i found this out while waiting for the "extruder and bed at temperature" signal on my 3d printer
10:20 AM seb_kuzminsky: restarting linuxcnc fixes it, of course
10:24 AM Tom_L: i wonder how it would affect 'run from here' if you used that to restart it
10:28 AM jepler: my marlin and sailfish 3d printers, I always just restart them in the case of an abort, they don't get it right
10:28 AM jepler: motors go the wrong directions towards the end-stops when "homing", that sort of thing