Calibration stops at waypoint 0

Troubleshooting
1

I am trying to get my maslow calibrated, but I won’t even get past waypoint 0.
I tried too many times already and even created a drawing to visualize the offsets in relation to the frame, but I dont get anywhere. Maybe one of you has an idea where the problem could be?

I am running my maslow4 with v0.84. My Frame is 3000 mm by 2520 mm with the anchor points inset by 75mm from each border, so the dimensions are 2975 by 2370.
I entered this in the options:

grafik
grafik889×770 40.1 KB

And this is the log that I get:
Serial Messages
Index.html Version: 0.84
[MSG:INFO: FluidNC v0.83 (Maslow-Main-39543985-dirty)]
[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 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[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:Flow42_MK2]
[MSG:INFO: Connecting.]
[MSG:INFO: Connectin[MSG:INFO: FluidNC v0.83 (Maslow-Main-39543985-dirty)]
[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 3]
[MSG:INFO: Axis X (-2438.400,0.000)]
[MSG:INFO: Motor0]
[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:Flow42_MK2]
[MSG:INFO: Connecting.]
[MSG:INFO: Connecting…]
[MSG:INFO: Connecting…]
[MSG:INFO: Connecting…]
[MSG:INFO: Connected - IP is 192.168.2.16]
[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: Channel auto report interval set to 50 ms]
[MSG:INFO: Caution: Unlocked]
[MSG:INFO: Set to comply]
[MSG:INFO: Set to comply]
[MSG:INFO: Retracting all belts]
[MSG:INFO: Bottom Right pulled tight with offset -1661.259]
[MSG:INFO: Bottom Left pulled tight with offset -1627.515]
[MSG:INFO: Top Right pulled tight with offset -1763.048]
[MSG:INFO: Top Left pulled tight with offset -1751.002]
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Setting z-stop position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.125 TR: 0.154 BL: -106.214 BR: -92.808]
[MSG:ERR: Center point deviation over 100.000mmm, your coordinate system is not accurate, adjust your frame dimensions and restart.]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]

2

I’ve had that error before and it is really frustrating. More accurate frame dimensions should solve it (frame dimensions being the distance between the anchor points and not the entire frame).

In the calibration instructions, it says that the frame dimensions that you enter do not need to be accurate. However, they actually do need to be reasonably close to accurate (within an inch or two at very least). Make a measurement as best as you can of the bottom-left anchor point on your frame to the top-left anchor point and bottom-right anchor point to the top-right anchor point. Average the two if there’s a difference and put that measurement into the “Machine Height”. Then do the same with bottom-left to bottom-right and top-left to top-right and enter that into the “Machine Width”. When the frame dimensions are close enough, the machine will do a full calibration and it will automatically update the dimensions with its own calculation.

Also, I would start with a smaller grid size. A 9x9 grid gets a more rigorous and accurate calibration, but is also the very susceptible to failing. You can start with a smaller grid like 3x3 or 5x5, complete a calibration, then use the numbers it comes up with there to do a calibration like 9x9.

1 Like
3

This is the important bit here. Basically what this is saying is that the frame is bigger than the dimensions entered.

4

I’m not sure about this math

1 Like
5

If you anchor point is 75mm from the border, then I’m confused at why you have 2975 as your width dimensions. Shouldn’t it be 150mm less (i.e., 75 on one side and another 75 on another)? That’s assuming you mean a 75mm diagonal line from the border (as opposed to 75 in the x direction and 75 in the y directions resulting in a 106.07 diagonal). It looks like you subtracted 150 in the height, but only 25 from the width.

If you have each anchor inset at a 75mm diagonal, then the frame dimensions above should be 2850 in width (x-axis) and 2370 in height (y-axis).

6

Oh my god!
This actually hurts.
I completely dis- and reassembled the whole thing (adding printed belt guards, so it wasnt completely for nothing) and started looking at the sources trying to find the problem.
Thank all of you!

facepalm_deja_q-1
facepalm_deja_q-11200×871 30.9 KB

2 Likes
7

I definitely know that feeling. It happens to everyone. I was working on making a z-probe for my machine over the weekend and spent about a day and half trying to get some wired connections to work and failing, when I finally realized that I had the control board upside down, so I had been trying to connect to the wrong wires the entire time.

8

Literally everyone. All the darn time.

The good news is that sometimes a second set of eyes is all it takes and that’s what the forums are for!

1 Like