Probe execution raises the z axis

Troubleshooting
1

I am having a strange issue. I updated to firmware 1.12 and the applicable yaml and gz files. After turning on the probing (no aliens involved), the z axis increases, rather than going down. What am I doing wrong?

1 Like
2

This sounds like a perfect application to test out our new system for firmware fixes! Ive never used the probe feature of FluidNC so Im not the best person to test.

Would you be willing to make an issue here describing exactly what you are seeing and what you would expect?

The AI will then try to solve the issue and give you back a new version to test.

3

Sure. What do you want me to do?

1 Like
4

Just this. All you have to do is describe the issue that you are seeing and the rest should be automatic :grinning_face:

5

The AI got a little confused and didn’t find the right answer right away, but I learned a lot and was able to improve the process a little bit so thank you for making that issue!

If you have a chance will you give this firmware a try and let me know if it fixes the probe issue for you?

firmware.bin (1.9 MB)

6

I have replaced the .gz and .yaml with the files on the v1.12 download. I replaced the firmware with the file you sent. After unlocking and issuing a z down I receive an error:22.

I suspect user error, but cannot for the life of me figure what I am doing wrong. The z down had been working. Only the probe command was misbehaving. Below is the log.

Serial Messages
Index.html Version: 1.12
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v3.0.x (noGit)]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.7-dirty]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:INFO: Machine Maslow S3 Board]
[MSG:INFO: Board Maslow]
[MSG:INFO: UART1 Tx:gpio.1 Rx:gpio.2 RTS:NO_PIN Baud:115200]
[MSG:INFO: SPI SCK:gpio.12 MOSI:gpio.11 MISO:gpio.13]
[MSG:INFO: SD Card cs_pin:gpio.10 detect:NO_PIN freq:8000000]
[MSG:INFO: Stepping:Timed Pulse:4us Dsbl Delay:0us Dir Delay:0us Idle Delay:240ms]
[MSG:INFO: Axis count 5]
[MSG:INFO: Axis A (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis B (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis C (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis D (-5000.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: Axis Z (-100.000,0.000)]
[MSG:INFO: Motor0]
[MSG:INFO: tmc_2209 UART1 Addr:0 Step:gpio.15 Dir:gpio.16 Disable:NO_PIN R:0.110]
[MSG:INFO: Motor1]
[MSG:INFO: tmc_2209 UART1 Addr:1 Step:gpio.46 Dir:gpio.38 Disable:NO_PIN R:0.110]
[MSG:INFO: Z Axis driver test passed]
[MSG:INFO: Z2 Axis driver test passed]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Connecting to STA SSID:Rldcave]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.0.131]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://maslow.local/\]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
D:Rldcave]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.0.131]
[MSG:INFO: WiFi on]
[MSG:INFO: Start mDNS with hostname:http://maslow.local/\]
[MSG:INFO: SSDP Started]
[MSG:INFO: HTTP started on port 80]
[MSG:INFO: Telnet started on port 23]
[MSG:INFO: Caution: Unlocked]
JogTo: '$J=G91F0Z-5
’
error:22

1 Like
7

I’ve seen that too, but I’m not sure why.

Can you try refreshing the page?

8

I ran the system through calibration, since the yaml was replaced. It did that fine. However, whenever I tell it to move (z, x, or y) I receive the ‘error: 22’ message.

9

I won’t be crazy enough to say I figured it out. It now works.

  1. I reinstalled the modified 1.12 firmware. It works!

  2. I reinstalled the gz and yaml files. Everything works

  3. I modified the yaml with a yaml editor to activate the pin for probe Error 22 (bad encoders or bad file)

  4. I accidentally hit set z home. Errors go away

  5. I am supposing that manually editing the yaml file disturbs it. However, having the software perform a write to the yaml (such as calibration or setting home positions) closes the file properly

  6. if I am just the recipient of happy coincidences, let me know

Thanks for all the help.

1 Like
10

Excellent! :grinning_face:

I’ve merged that change into the firmware so from version 1.13 on it will be included.