I have spent many days attempting to be able to run my first gcode file.
I set the frame anchor dimensions, belt extension length etc and was able to “Find Anchor Points” - but only once.
I updated the firmware to the latest version, 1.25 and wanted to re-confirm the anchor points. I manually set the anchor points in the maslow.yaml. I am no longer able to get the “Find Anchor Points” to work. I have re-watched the videos, I have re-read the setup files.
I get various error messages like cannot find belt dimension. I often get the software stuck in a state and then the various buttons no longer work, so I am stuck, and there is no “cancel” or “reset” other than unplugging and replugging.
I am very frustrated. I am not able to Trace boundary any more, many error messages which do not help since the software does not allow clearing states or completing states without the unplugging and replugging.
I think I might be able to help. I have worked through the calibration many times with very similar results that you are experiencing.
If you are using firmware that is older than 1.24:
The Maslow calculates where the 4 points are using a genetic algorithm that is too big to run on the unit itself.
To get around this, it sends all the points/data to your laptop, so that it can be computed in your browser.
I have found that if your browser boots the tab from memory OR your computer falls asleep, it will cause that state where the buttons no longer work. The process gets broken before it has finished and does not spit out a warning.
My recommendation is to make sure that your computer is set to NOT GO TO SLEEP. This is what saved me from so much strife with the old firmware.
I do highly recommend upgrading to the new 1.24 firmware if you can. I put it off, but wish I had done it as soon as it came out. It switches the type of algorithm that is used to get the locations of the points. It is faster, can be computed on the ESP32 on board the Maslow, and as a result, is much more reliable and less likely to fail.
TLDR: Set your computer to not go to sleep during calculations. Upgrade to firmware 1.24 if possible because it is waaaaay more reliable.
Thanks for the reply. I am using the latest firmware 1.25.
Good advise, but I realised my rookie mistake overnight.
I did retract, but forgot to remove the pins from the anchors, so the belts did not go all the way home.
This morning I removed the anchor pins, did retract, extend, then apply tension and was able to get the Maslow to find the anchor points and replace its measurements in the yaml file with my initial settings.
I am still feeling frustrated, but at least one step forward.
I absolutely agree that simplifying and making the software easier to use is a top priority. It is really really easy to add complexity to software, but so so much harder to make it simpler (without losing functionality). There are just too many steps that have to happen in exactly the right order for everything to work right and it’s too easy to throw something off.
I again unplugged, then replugged in, removed the anchor pins, retracted, extend all then tension.
I did not insert a router bit. I was able to get the Maslow to run my test gcode so I thought I was ready for a first cut.
I removed the anchor pins - again, then went through all the steps - again. I set Z home to just touch the work.
The state is showing “Ready to Run” but when I attempt to run, I only get Z height changes. X and Y are not mowing now. After the code completed, the Serial data shows it completed, I am still showing state “Ready to Run” but I cannot manually jog in X or Y direction.
I am going to have to start all over again. More frustration.
You should not need to remove the anchor pins just to put in a router bit, you can just raise up the z-axis and install it
Can you attach the log files? You can export them with the blue button on the lower right. That will help us a lot to better understand what is happening
Before I attach log files, there may be something odd with communication.
I am using an Android tablet next to the Maslow down in my shop. The tablet Serial log showed the X and Y movements I attempted, but the Maslow did not move. At this time the tablet showed “Ready to Run” state. I unplugged the Maslow, the replugged and reconnected to the network and saw the same “Ready to Run” state.
Upstairs at my computer, I connected to the Maslow, this connection had the status “Unknown”.
I had dinner then went downstairs to the shop to turn off the Maslow and the tablet showed “Unknown” status.
I may have some weird communication issue between the tablet and the Maslow.
So before I send Serial data which may be bogus, how do I know when the Maslow communications with the tablet are correct?
Good question. I usually rely on refreshing the page if I think anything suspect is going on. Browsers can do weird things like keep a cached version of the web page, but refreshing usually fixes it. On a computer I will do control+shift+R which will refresh and clear the cache, but I don’t know how to do that on a keyboard
Today I started over, removed the anchor pins, retract, extend, apply tension and then “Ready to Run” status. The Maslow followed the code, but I did not re-set the Z home so the router bit did not touch the work. So I am not sure when I did wrong on setting Z home.
After the code completed, I re-set the Z home, ran the code again. The router bit still was above the work, but after a short time I heard something break and the Maslow stopped.
The No. 4 belt had twisted between the arms, got jammed and snapped. I had a jam like this before but it happened when jogging so I caught it before the belt snapped.
So now I need to take the Maslow apart so I can fit a shim to reduce the space between the arms to be small enough to prevent a belt from getting caught. I wonder how many parts I will break getting this apart.
I presume I can use the shorted belt since my frame is presently about 30in square so I have extra belt length. I will get a new belt ordered.