Warning fitness too low

Troubleshooting
1

I can’t seem to get my maslow4 to calibrate. I thought maybe an issue was with the motor idler being to tight so I tore it apart and adjusted all the motors back to losen the fitness. I’ve tried extending and retracting multiple times to see if it zeros I get the following:

[MSG:INFO: Retracting all belts]
[MSG:INFO: Top Left pulled tight with offset 0.011]
[MSG:INFO: Top Right pulled tight with offset 0.032]
[MSG:INFO: Bottom Right pulled tight with offset 0.011]
[MSG:INFO: Bottom Left pulled tight with offset 0.000]

Below is the full log of the session but I’ve reattemped 20ish times now all with basically the same results. I checked my frame and it’s about .5" out of square im going to try and adjust that but it seems pretty voilent when doing the calibration. I’m not sure if I’m missing something or if I just have an issue with my build.

Serial Messages
[MSG:INFO: Channel auto report interval set to 50 ms]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[GC:G0 G54 G17 G21 G90 G94 M5 M9 T0 F0 S0]
[MSG:INFO: Caution: Unlocked]
[MSG:INFO: Zeroing z-axis position]
[MSG:INFO: Zeroing z-axis position]
[G54:0.000,0.000,-4.000]
[MSG:INFO: Zeroing z-axis position]
[G54:0.000,0.000,-10.000]
[MSG:INFO: Retracting all belts]
[MSG:INFO: Top Right pulled tight with offset -1726.598]
[MSG:INFO: Top Left pulled tight with offset -1720.447]
[MSG:INFO: Bottom Right pulled tight with offset -1856.580]
[MSG:INFO: Bottom Left pulled tight with offset -1831.877]
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Retracting all belts]
[MSG:INFO: Top Left pulled tight with offset 0.011]
[MSG:INFO: Top Right pulled tight with offset 0.032]
[MSG:INFO: Bottom Right pulled tight with offset 0.011]
[MSG:INFO: Bottom Left pulled tight with offset 0.000]
[MSG:INFO: Extending all belts]
[MSG:INFO: All belts extended to center position]
[MSG:INFO: Zeroing z-axis position]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point deviation: TL: 0.230 TR: 0.351 BL: 18.237 BR: 2.882]
[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:1919.35,   br:1905.29,   tr:1901.98,   tl:1903.66},{bl:1824.68,   br:1930.23,   tr:2003.14,   tl:1870.84},{bl:1657.58,   br:2027.87,   tr:2146.23,   tl:1807.42},{bl:1731.58,   br:2101.85,   tr:2101.49,   tl:1717.70},{bl:1821.56,   br:2176.43,   tr:2032.57,   tl:1632.71},{bl:1998.73,   br:1983.75,   tr:1825.59,   tl:1842.79},{bl:2192.62,   br:1805.97,   tr:1630.63,   tl:2045.97},{bl:2100.67,   br:1850.30,   tr:1795.01,   tl:1947.60},{bl:2031.78,   br:1631.49,   tr:1835.15,   tl:2172.08},]
Computing... This may take several minutesFitness: 0.1159719 in 100
Fitness: 0.1159719 in 200
Fitness: 0.1159719 in 300
Fitness: 0.1159719 in 400
Fitness: 0.1159719 in 500
Fitness: 0.1159719 in 600
Fitness: 0.1159719 in 700
Fitness: 0.1159719 in 800
Fitness: 0.1159719 in 900
Fitness: 0.1159719 in 1000

WARNING FITNESS TOO LOW. DO NOT USE THESE CALIBRATION VALUES!
2

I plugged this CLBM value in to https://m4cal.etskinner.com/ (which got about the same fitness, not surprisingly) but this pattern looks quite drastically different than I’ve seen before.

I don’t have insight into what would cause this, but I just thought I’d mention that especially measurement 7 is really off rrom the rest. When I exclude it it still gets only .23 fitness. I’ll check and make sure this visualization tool is still using the same code as maslow, but I think it is. There is also an excel spreadsheet floating around that may have another answer.

image
image1000×602 32.9 KB

1 Like
3

Thanks so much for looking at this. I was starting to get bummed out last night that I was having so many issues and then I found another post mentioning after updating the maslow.yaml they forgot to change the orientation for calibration to vertical and it clicked in my brain I did the same thing. So I’ve restarted with clean yaml and currently its running through the process and is looking WAYYYY better. I’ll report when im done but I think it may be fixed at this time.

2 Likes