Maslow4 calibrates on 0.77 but fails on 0.78.1

Anyone else having trouble with version 0.78.1?

I’ve spent about 10 hours calibrating in the past 2 days. Starting with … can’t remember the version it was shipped with, then with 0.77 and finally with 0.78.

Most of this time I forgot things, like the yaml file, or to release tension before I powered down the maslow4, etc.

I don’t have the router installed, just a marker. On version 0.77 I marked out a 150 x 150 square and the inside is 148 x 148. Maybe the marker is wider than 1/8 inch. Looked good so I upgraded to version 0.78.1 and it won’t calibrate - refer below for all the logs I could get (or that I think I can get)

Version 0.77
Machine width 3884
Machine Height 2642

Calibration grid 1000 x 1000
grid size 9x9
retraction force 1000

As the calibration moves through the different grids, width moves to 3884.8, 3884.7. Height moves from 2642 to 2641.5 to 2641.8 to 2641.7

Log from the attempt to calibrate with 0.78.1

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 v3.6.7 (Bringing-in-Maslow-changes-bit-by-bit-b659ebef-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 Default (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][<Alarm|MPos:0.000,0.000,-46.000|FS:0,0|Ov:100,100,100>
[MSG:INFO: FluidNC v3.6.7 (Bringing-in-Maslow-changes-bit-by-bit-b659ebef-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 Default (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: AP SSID maslow IP 192.168.0.1 mask 255.255.255.0 channel 1]
[MSG:INFO: AP started][MSG:INFO: WiFi on][MSG:INFO: Captive Portal 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: Retracting all belts]
[MSG:INFO: Bottom Right pulled tight with offset -1970.640][MSG:INFO: Bottom Left pulled tight with offset -2254.857]
[MSG:INFO: Top Right pulled tight with offset -2233.599][MSG:INFO: Top Left pulled tight with offset -2423.542]
[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.278 TR: 0.224 BL: 59.042 BR: -3.538]
[MSG:INFO: Measured waypoint 1]
[MSG:INFO: Measured waypoint 2]
[MSG:INFO: Measured waypoint 3]
[MSG:INFO: Measured waypoint 4]
[MSG:INFO: Measured waypoint 5]
[MSG:INFO: Measured waypoint 6]
[MSG:INFO: Measured waypoint 7]
[MSG:INFO: Measured waypoint 8]
CLBM:[{bl:2407.99, br:2346.46, tr:2349.59, tl:2351.11},
{bl:2281.08, br:2282.20, tr:2490.44, tl:2430.54},
{bl:2175.66, br:2401.78, tr:2585.65, tl:2324.37},
{bl:2303.94, br:2453.32, tr:2453.84, tl:2248.81},
{bl:2374.35, br:2521.74, tr:2388.95, tl:2177.83},
{bl:2475.93, br:2422.54, tr:2281.57, tl:2283.99},
{bl:2580.22, br:2323.59, tr:2176.17, tl:2391.25},
{bl:2453.34, br:2247.95, tr:2314.80, tl:2452.77},
{bl:2388.44, br:2176.85, tr:2395.06, tl:2528.15},]
Computing… This may take several minutes
Fitness: 0.4811558 in 100
Fitness: 0.6506239 in 200
Fitness: 0.6908420 in 300
Fitness: 0.6918169 in 400
Fitness: 0.6918169 in 500
Fitness: 0.6918169 in 600
Fitness: 0.6918169 in 700
Fitness: 0.6918169 in 800
Fitness: 0.6918169 in 900
Fitness: 0.6918169 in 1000
Fitness: 0.6918169 in 1100
Fitness: 0.6918169 in 1200
Fitness: 0.6918169 in 1300
Calibration complete Calibration values:Fitness: 0.6918168854791233
Maslow_tlX: 85.4Maslow_tlY: 2642.0
Maslow_trX: 3956.3Maslow_trY: 2642.7
Maslow_blX: 0.0Maslow_blY: 0.0
Maslow_brX: 3972.5Maslow_brY:
0.0A command to save these values has been successfully sent for you. Please check for any error messages.

[MSG:INFO: Setting z-stop position]
[MSG:ERR: Unable to move safely, stopping calibration]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]
[MSG:ERR: Unable to move safely, stopping calibration]

I checked the configuration -
The config has been cleared. Width blank, height blank, calibration grid width and height are blank, 9x9 is still there, Retraction force is blank.

TEST button shows me index.html version 0.78

Power cycle to Maslow4

Width is now 3956.3, height is now 2642.7, horizontal, 1000 x 1000, 9x9 grid, retraction 1000

So it DID save the values, but maybe they didn’t reload so the calibrate could not continue?

Width 3956 is too high. When I run the calibrate again the fitness is too low and fails.

Anything else I can capture to help track this down before I revert to 0.77?

I found another thread - I guess I should have searched harder!

So I guess I purposely make the frame too big and try again. It’ll be good to stay with 0.78.1

I’ll report back tomorrow when I get it done

Thread - V0.78 Is Up - Let us know!

ronlawrence3
8d
or running another calibration.

So I decided to run another calibration. I zeroed Z, retract/extend/hang/apply tension/calibrate.

I got this:

[MSG:INFO: All belts extended to center position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.346 TR: 0.103 BL: -9.229 BR: -10.888]
[MSG:INFO: Center point deviation: TL: 0.346 TR: 0.103 BL: -9.229 BR: -10.888]
[MSG:INFO: Center point deviation within 15.000mm, your coordinate system is accurate]
[MSG:INFO: Setting z-stop position]
[MSG:ERR: Unable to move safely, stopping calibration]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]
[MSG:ERR: Unable to move safely, stopping calibration]
This is with reasonably good numbers in maslow_xxx values given I was jogging and running jobs ok with them (just hitting the overcurrent errors). I don’t understand what might be causing the checkValidMove function to trigger this estop. @bar any ideas? I’m going to do the insane thing and try the rehang dance again…

dlang
8d
Bar has said that this happens because the maslow gets confused about what it’s
supposed to do. It thinks it needs to retract a belt to move left, but the
lengths say that it needs to extend the belt.

there has been talk about disabling this error, but right now the fix is to
change the starting frame size to something larger and try again.

David Lang

You actually don’t need to re-calibrate when you change versions! If you have a good calibration no need to change it!

This error is caused when the machine needs to move in a way which is impossible. For example if it needs to move to the left then the two belts on the left should get shorter and the two belts on the right should get longer…but if the math is telling the machine that to move to the left the left belts need to get longer then we know something funky is going on.

This check was added because without it we were having issues where it would do something unexpected.

Thanks @bar.

Test prints with a marker work fine.

I have some notes on what I did, what order, and what I didn’t catch on to the first time around.

Can I make some edits to a copy of the web page and email it to someone for review?

1000% yes! Suggestions for how we can make things better are always VERY welcome