Firmware 1.16 is out! You can find it here: Release v1.16 · MaslowCNC/Maslow_4 · GitHub
Please let us know how it is and what can be improved!
5 Likes
I have version 1.15, and when I calibrated it, it gave me the best fitness I’ve ever had. The problems I’m having with this version are: the trace boundary issue and the fact that it doesn’t take the Z-axis into account when applying tension.
Today I tried installing version 1.16, and I never achieved good fitness. When I was calibrating, as I approached the TL , the sled tilted. When I finished calibrating with a fitness of 0.8, I tried jogging, but the BR didn’t apply tension, and when I stopped, the belt loosened considerably.
I also noticed that the calibration force (which was working at 750) cannot be adjusted. Is it not possible to adjust this parameter? Does the machine calculate how much force to apply? Or does it now use a standard value for this parameter?
I had to revert to version 1.15.
Did you update the maslow.yaml file? If you saved the old yaml file, you can load the relevant values into the new file. If you had a successful calibration with V1.15 and you copy the values into the new maslow.yaml then you should be able to run without running find anchors.
Don’t copy mine, they are unique to each setup.
1 Like
I’m running into a calibration loop trying to re-calibrate with v1.16. The calibration itself seems to go smoothly enough, except it does display the following message sequence each time the state changed from computing → calibrating. Not sure if this is a sign of the problem or just an extra state change that’s harmless.
[MSG:INFO: Requesting state change from Calibration Computing to Calibrating]
[MSG:INFO: Machine Position found as X: -147.624 Y: 13.309]
[MSG:INFO: Setting motor positions from hardware readings:]
[MSG:INFO: TL: 1928.072 TR: 2160.766 BL: 1932.527 BR: 2171.190]
[MSG:INFO: Succeeded]
[MSG:INFO: Requesting state change from Calibrating to Calibrating]
[MSG:INFO: Cannot start calibration until the belts have been extended]
The real problem seems to be at the end of the calibration process. I get the success popup showing that calibration has been completed successfully, then the machine immediately begins the calibration process fresh. Relevant log segment is inline below showing the last couple calibration points of the first cycle, then the first couple points of the second cycle that it’s trying to do for some reason.
Anyone else running into this or have thoughts on stuff I should try to resolve this?
[MSG:INFO: Succeeded]
[MSG:INFO: Measured waypoint 87]
[MSG:INFO: Measured waypoint 88]
[MSG:INFO: Requesting state change from Calibrating to Calibration Computing]
[MSG:INFO: Succeeded]
CLBM:[{bl:2194.88, br:2193.09, tr:2200.62, tl:2206.51},{bl:2309.57, br:2085.59, tr:2088.88, tl:2315.15},{bl:2401.31, br:2168.29, tr:1994.74, tl:2248.53},{bl:2297.74, br:2280.90, tr:2106.40, tl:2124.70},{bl:2184.96, br:2396.47, tr:2231.07, tl:2002.04},{bl:2085.60, br:2323.18, tr:2313.41, tl:2078.87},{bl:2188.83, br:2201.32, tr:2207.18, tl:2197.74},{bl:2158.58, br:2159.90, tr:2238.42, tl:2239.91},{bl:1986.74, br:2328.96, tr:2409.62, tl:2082.71},{bl:2018.09, br:2366.93, tr:2383.84, tl:2037.77},{bl:2061.93, br:2404.78, tr:2347.02, tl:1994.62},{bl:2228.88, br:2241.93, tr:2167.98, tl:2158.04},{bl:2402.16, br:2075.07, tr:1994.55, tl:2336.96},{bl:2376.11, br:2030.14, tr:2026.20, tl:2375.04},{bl:2339.25, br:1986.99, tr:2070.40, tl:2412.99},{bl:2302.57, br:1943.87, tr:2118.37, tl:2454.72},{bl:2120.71, br:2112.58, tr:2281.48, tl:2292.19},{bl:1943.75, br:2295.48, tr:2451.50, tl:2128.67},{bl:1776.13, br:2479.74, tr:2623.41, tl:1975.84},{bl:1805.46, br:2514.69, tr:2603.59, tl:1927.11},{bl:1850.01, br:2547.74, tr:2568.28, tl:1878.98},{bl:1898.09, br:2582.38, tr:2534.06, tl:1831.98},{bl:1946.84, br:2618.80, tr:2501.25, tl:1786.22},{bl:2106.10, br:2454.92, tr:2314.37, tl:1944.21},{bl:2270.68, br:2282.81, tr:2130.43, tl:2120.88},{bl:2441.76, br:2119.22, tr:1953.60, tl:2304.03},{bl:2614.30, br:1966.32, tr:1785.69, tl:2485.99},{bl:2594.11, br:1917.64, tr:1815.99, tl:2522.66},{bl:2558.73, br:1869.53, tr:1861.74, tl:2555.60},{bl:2524.55, br:1822.54, tr:1910.20, tl:2590.77},{bl:2491.84, br:1776.88, tr:1959.07, tl:2628.50},{bl:2459.87, br:1732.39, tr:2013.87, tl:2668.65},{bl:2270.63, br:1896.09, tr:2165.33, tl:2503.96},{bl:2083.61, br:2076.19, tr:2325.39, tl:2334.98},{bl:1905.04, br:2262.39, tr:2491.35, tl:2175.34},{bl:1731.80, br:2451.71, tr:2663.94, tl:2025.39},{bl:1571.80, br:2636.04, tr:2834.65, tl:1889.31},{bl:1598.00, br:2664.95, tr:2823.58, tl:1837.21},{bl:1643.91, br:2693.71, tr:2789.47, tl:1784.24},{bl:1692.63, br:2725.85, tr:2756.36, tl:1732.07},{bl:1744.65, br:2760.62, tr:2724.64, tl:1681.10},{bl:1797.70, br:2795.03, tr:2694.11, tl:1631.10},{bl:1852.04, br:2831.49, tr:2664.89, tl:1582.36},{bl:2000.26, br:2671.44, tr:2471.92, tl:1731.62},{bl:2155.93, br:2495.07, tr:2279.67, tl:1904.04},{bl:2315.71, br:2325.99, tr:2092.84, tl:2083.81},{bl:2483.35, br:2165.73, tr:1912.57, tl:2269.75},{bl:2653.99, br:2016.31, tr:1740.85, tl:2456.52},{bl:2825.74, br:1880.86, tr:1581.04, tl:2639.03},{bl:2814.41, br:1828.42, tr:1606.26, tl:2675.64},{bl:2780.25, br:1775.33, tr:1653.61, tl:2706.73},{bl:2747.25, br:1723.19, tr:1702.85, tl:2736.71},{bl:2715.45, br:1672.09, tr:1756.13, tl:2769.12},{bl:2685.00, br:1622.07, tr:1809.90, tl:2804.91},{bl:2655.76, br:1573.43, tr:1864.51, tl:2839.87},{bl:2652.68, br:1517.24, tr:1898.27, tl:2889.37},{bl:2457.57, br:1681.14, tr:2038.45, tl:2718.70},{bl:2257.84, br:1865.10, tr:2193.07, tl:2538.98},{bl:2062.20, br:2055.16, tr:2355.49, tl:2365.89},{bl:1871.27, br:2250.88, tr:2529.88, tl:2200.93},{bl:1687.69, br:2450.27, tr:2707.24, tl:2046.36},{bl:1513.23, br:2652.50, tr:2890.38, tl:1904.25},{bl:1351.87, br:2853.52, tr:3077.46, tl:1777.86},{bl:1390.88, br:2881.77, tr:3059.58, tl:1723.87},{bl:1440.29, br:2906.05, tr:3028.65, tl:1668.40},{bl:1491.12, br:2930.82, tr:2999.01, tl:1614.21},{bl:1542.43, br:2958.14, tr:2970.45, tl:1560.53},{bl:1595.79, br:2985.56, tr:2943.20, tl:1508.18},{bl:1648.94, br:3014.60, tr:2917.14, tl:1456.91},{bl:1705.41, br:3045.21, tr:2892.49, tl:1406.88},{bl:1761.36, br:3077.22, tr:2869.13, tl:1358.31},{bl:1887.90, br:2899.94, tr:2668.23, tl:1510.21},{bl:2030.13, br:2714.89, tr:2465.62, tl:1684.00},{bl:2184.00, br:2535.06, tr:2265.96, tl:1867.44},{bl:2347.80, br:2361.99, tr:2070.34, tl:2057.76},{bl:2521.83, br:2197.11, tr:1879.50, tl:2253.17},{bl:2699.06, br:2042.36, tr:1695.75, tl:2452.05},{bl:2882.36, br:1900.35, tr:1521.28, tl:2652.45},{bl:3068.68, br:1774.14, tr:1359.96, tl:2852.84},{bl:3051.48, br:1720.08, tr:1396.99, tl:2881.47},{bl:3020.56, br:1664.73, tr:1447.04, tl:2905.82},{bl:2990.91, br:1610.40, tr:1496.64, tl:2931.22},{bl:2962.40, br:1556.75, tr:1549.66, tl:2958.58},{bl:2935.24, br:1504.44, tr:1603.56, tl:2986.82},{bl:2909.22, br:1453.00, tr:1657.30, tl:3017.46},{bl:2884.55, br:1403.00, tr:1713.22, tl:3046.87},{bl:2861.27, br:1354.43, tr:1770.36, tl:3080.91},{bl:2063.28, br:2057.14, tr:2354.79, tl:2363.94},{bl:2190.63, br:2195.55, tr:2205.54, tl:2203.16},]
Computing... This may take several minutesInitial guess fitness: 0.9054207
Frame dimensions: 3650.4mm x 2453.7mm (aspect ratio: 1.49:1)
Initial fitness >= 0.1 and frame is not square, skipping rectangular optimization and using initial guess directly.
Fitness: 0.9066983 in 100
Fitness: 0.9075103 in 200
Fitness: 0.9079967 in 300
Fitness: 0.9081654 in 400
Fitness: 0.9081654 in 500
Fitness: 0.9081654 in 600
Fitness: 0.9081654 in 700
Fitness: 0.9081654 in 800
Fitness: 0.9081654 in 900
Fitness: 0.9081654 in 1000
Fitness: 0.9081654 in 1100
Fitness: 0.9081654 in 1200
Fitness: 0.9081654 in 1300
Calibration values:
Fitness: 0.9081654
Maslow_tlX: -5.5
Maslow_tlY: 2454.2
Maslow_trX: 3644.7
Maslow_trY: 2457.3
Maslow_blX: 0.0
Maslow_blY: 0.0
Maslow_brX: 3643.1
Maslow_brY: 0.0
A command to save these values has been successfully sent for you. Please check for any error messages.
Calibrate
[MSG:INFO: Requesting state change from Calibration Computing to Calibrating]
[MSG:INFO: Machine Position found as X: -0.222 Y: -7.159]
[MSG:INFO: Setting motor positions from hardware readings:]
[MSG:INFO: TL: 2052.213 TR: 2052.933 BL: 2037.537 BR: 2043.646]
[MSG:INFO: Succeeded]
[MSG:INFO: Calibration state reset]
[MSG:INFO: Requesting state change from Calibrating to Ready To Cut]
[MSG:INFO: Succeeded]
[MSG:INFO: Requesting state change from Ready To Cut to Calibrating]
[MSG:INFO: Machine Position found as X: -0.222 Y: -7.159]
[MSG:INFO: Setting motor positions from hardware readings:]
[MSG:INFO: TL: 2052.213 TR: 2052.933 BL: 2037.537 BR: 2043.656]
[MSG:INFO: Succeeded]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Center point off by: TL: 0.000 TR: 0.000 BL: 0.348 BR: 1.579]
[MSG:INFO: Machine Position computed as X: -0.078 Y: -7.099]
[MSG:INFO: Measured waypoint 1]
[MSG:INFO: Measured waypoint 2]
double check that you don’t have two browsers connected during calibration, that
can cause this.
David Lang
oh goodness - I don’t even want to ask but why would the number of browsers effect machine behavior if I’m only pushing buttons in one?
I did open a second browser on my other computer to check calibration progress - sounds like that’s what did it.
Zach wrote:
oh goodness - I don¢t even want to ask but why would the number of browsers
effect machine behavior if I¢m only pushing buttons in one?
during calibration, the system does the measurements, sends them to the browser,
then the browser does some calculation, and when it’s done, it sends the results
to the machine and tells it to continue the process.
unfortunantly, the command to continue is the same as the command to start the
calibration, so when you have two browsers running, they both get the data, send
the results, then issue the ‘calibrate’ command, which kicks off calibration
again.
David Lang
1 Like
Ahh I see. That’s actually pretty cool to be taking advantage of the browser compute for optimization rather than just the ESP32! Appreciate the context on that.