Advanced Search

Great to hear you are making progress.

No need for the SPI_clk_div=32 in the loadrt command line, that is for the RPi4/3.

What fault / error is generated when the machine stops? I've still got the Octopus and RPi setup on the bench, will look to try your config again over the weekend.

Today, after updates, i am not able to start any flexgui ui .  Error: No module named 'psutil'

Wasn't exactly sure where to put this question. But this is like the third time it happened to me. Upon the initial startup I'll home out the axis, go to MEM, select a g-code file, then I hit start. And it'll race through the g code like the entire program was full of G0 commands. If I had a part in the machine it would have crashed.  It's like it ignored every G1 command. Once the cycle is done, If I hit start cycle again, it'll go through like it's supposed to. The strange part is, it does not do it every time. Is this a configuration issue or a G-Code issue or a Linux issue? 

It's also known as chip breaking in mill G-Code. G83 and G73
The cycle sets final depth (X), retract position (R), peck depth (Q), and feed rate (F) normally used for drilling process. It's also handy for breaking stainless steel instead of getting birds nests or for live lathe tooling. Since my setup utilizes a grinder, without a pecking cycle it can stall the grinder out.
Right now I have to program a "peck" cycle manually. An example of this is:
G1 X2.02 F1
G0 X2.01
G1 X2.03 F1
G0 X2.02
G1 X2.04 F1
G0 X2.03