Ran it again, this time set the extension value to 1000 (as per my setup)
It ran with tight belts this time. Failed with low fitness value after last rectangular iteration. Was able to take tension, move to centre with Park function and raise and set Z, did an air file cut. Log attached.
Maslow-serial - 2026-05-05T083919.985.log (37.6 KB)
1 Like
Ran the v20.1 version after running LM version, with the modification #943.
Failed to get a good value on the last iteration. Log file attached.
Maslow-serial - 2026-05-06T095759.389.log (29.0 KB)
Also screen dump showing expanded serial file mid run.
Yes, David Right not Left, had my shoes on the wrong feet.
Using the normal V1.20 Find Anchors.
On this serial log, ran it again (3rd time) building from V1.20 maslow.yaml file. Didn’t give a fitness report, went to Belts Extended. Maslow was in Right down corner. I applied tension and moved to the centre, I then loaded my original version back in and ran Find Anchors. It completed with a fitness of 1.677
Find Anchor Values:
Fitness: 1.6772897
Maslow_tlX: -161.7
Maslow_tlY: 3992.4
Maslow_trX: 4552.9
Maslow_trY: 3949.9
Maslow_blX: 0.0
Maslow_blY: 0.0
Maslow_brX: 4580.3
Maslow_brY: 0.0
It then started running the Find Anchors again, probably because I had multiple windows open. I killed it
I think the closer the starting point values for the Anchor points are too actual, the more likely the fitness will be acceptable.
1 Like
I agree, it is very starting value dependent.
That is one of the things which is supposed to be a big improvement in the LM version, it should handle incorrect starting values much better…TBD if that is true though