After boot no X/Y movement [Solved]

Troubleshooting
1

Yesterday, everything was working correctly. I was experimenting with the movement buttons in the UI without encountering any issues.

Today, when I started the system, the X/Y movement is no longer functioning. However, the Z movement is working properly.

Here is what I do:
Upon booting, I press the Alarm button to unlock. Then, when I press a direction button, the fan of the PCB starts spinning, and I see the values in the UI changing. Nevertheless, nothing happens, and then the fan stops.

I have attempted several power cycles, but nothing is moving.

Do you have any idea what might be going wrong or if I am overlooking something?

My version of FluidNC is 0.74
And this is my serial log

Serial Messages
[MSG:INFO: Channel auto report interval set to 50 ms]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: FluidNC v0.74]
[MSG:INFO: Compiled with ESP32 SDK:v4.4.4]
[MSG:INFO: Local filesystem type is littlefs]
[MSG:INFO: Configuration file:maslow.yaml]
[MSG:WARN: Ignored key cs_pin]
[MSG:WARN: microsteps value 0 constrained to range (1,256)]
[MSG:WARN: Ignored key cs_pin]
[MSG:WARN: microsteps value 0 constrained to range (1,256)]
[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 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO:   Motor0]
[MSG:INFO: Config messages ran]
[MSG:INFO: Axis Y (-1219.200,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: Kinematic system: Cartesian]
[MSG:INFO: Using spindle NoSpindle]
[MSG:INFO: Connecting to STA SSID:marzsman]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting..]
[MSG:INFO: Connected - IP is 192.168.2.13]
[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]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: Caution: Unlocked]
2

Maybe I damaged my maslow.yaml file.

I have a local YAML file with a lot more data in it than the one I downloaded. I have only updated the part until #################### (line 53) and then uploaded the file. But now I see there are a lot more lines in that older file.

I guess this is all important data?
I’ll try to merge the 2 YAML files and see what happens.

3

If you have a power cycle, you do have to do the “rehang dance” as I call it.

take machine off, retract/extend/ put it back, apply tension

1 Like
4

About the missing data in my YAML, I noticed that when I click on “Save Config” in the UI, my YAML contains a lot more data when I download it.

Should I be concerned about this when I upload a new version? Or can I simply update the frame settings when I upload a new YAML?

The machine was still not moving after re-uploading the YAML.

I just performed a “Release tension,” and that worked. The motors where moving.
However, I am not going to remove and reattach the Maslow again at this moment, so I will do that tomorrow.

5

yes, unfortunately whenever the maslow is off, it loses its home and has to “re-zero” the belts with retract/extend. There are efforts underway to help remove this limitation, but that is the way it is now.

6

You made me laugh and cry at the same time, hahaha

But any idea why there was no movement after the boot up from yesterday?
Is there a ‘wrong’ way to shut down the machine? I just pull the power plug.

7

This is normal, however others are also reporting issues vs the stock maslow.yaml. After calibration, the ones starting with Maslow are important to save off so you can re-enter them if needed in future maslow.yaml releases.

2 Likes
8

no, that is fine… it has nothing to do with “how” right now, it just does not save its last known belt lengths ever at this point in time, so if its off, it has to do the re-hang dance.

2 Likes
9

Ok, thx a lot for the clarification!

2 Likes