bdring

Results 480 comments of bdring

I am not sure what is happening. I was hoping you would do everything manually and not use a gcode sender's automated probing. It is hard to see what it...

Here is my run with $Gcode/Echo=on. ``` Grbl 3.9 [FluidNC v3.9.8 (wifi) '$' for help] [MSG:INFO: ALARM: Unhomed] ALARM:14 $H [echo: $H] [MSG:Homed:Z] [MSG:Homed:XY] ok $localfs/run=atc_demo.gcode [echo: $localfs/run=atc_demo.gcode] ok [echo:...

We need to see the gcode echo to see the probe command. The sender is doing so much that it is hard to tell where the commands are coming from.

G53 is supposed to be G91 independent. it appears that it is. ``` G91 G53 G0 Z-1 [echo: G53 G0 Z-1] ok G53 G0 Z-1 [echo: G53 G0 Z-1] ok...

- A good gcode sender should not leave you in G91 without you knowing about it. - A good post processors or gcode file should have a G90 at the...

A new PR makes this safe from G91 and Non G17 planes. https://github.com/bdring/FluidNC/pull/1570

It works fine on my machine. Here is the console session I suggested you do. ``` Grbl 3.9 [FluidNC v3.9.8 (wifi) '$' for help] $H [MSG:Homed:Z] [MSG:Homed:XY] ok $10=1 ok...

I think you might have a trailing space on `atc: atc_manual `. Try it without that space. My start messages show this. ``` [MSG:INFO: PWM Spindle Ena:gpio.13 Out:gpio.14 Dir:NO_PIN Freq:5000Hz...

I can have the code do this. I put it in single quotes, so you can better see the trailing blank. ``` [MSG:INFO: PWM Spindle Ena:gpio.13 Out:gpio.14 Dir:NO_PIN Freq:5000Hz Period:8191...