We were able to get our Maslow calibrated.
We shut it down, then restarted it later. We retracted the belts, then extended the belts. When we tried to apply only a few of the belts would move. When we tried to move it using the UI we got the message “Maslow is not ready to move.”
Any idea how we can move forward?
I think that this issue might be fixed in the latest firmware. I’d make sure that you are running both the latest firmware and index.html versions. No need to run calibration again after updating (unless you update using the USB cable which wipes everything)
Thanks Bar - we think we have the latest versions of both files loaded (but we loaded them again just to be sure):
Index.html Version: 1.07
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: FluidNC v3.0.x (noGit)]
We’ll try again and let you know what happens. We appreciate the help!
Do you also have firmware version 1.07?
You can check with the “test” button.
I have seen this happen and it is a bug of some sort, but I’m not sure exactly why it happens.
If you see that issue can you open the setup window and at the top of the window it should say what the machines current state is. Can you tell me what it says there?
Yes, we have firmware version 1.07:
[MSG:INFO: Firmware Version: 1.07]
We’ll test again in the morning and get the current machine status should it fail again - thanks again.
This also appears to be my issue. I have not upgraded to 4.1, and have firmware version 1.6. It took a long time to calibrate. After calibration I pushed the “save to serial” button in the set up section of the UI. Now after applying tension, when I attempt to jog, I get the “Maslow is not ready to move” message. I will apply the upgrade to version 1.7 and attempt to jog it again.
I can’t find the file “maslow.yaml” in the 1.7 upgrade section in github. Will it work if I use the maslow.yaml file from version 1.6?
You should not need to replace maslow.yaml unless specifically advised to in the upgrade. It is advised to save a copy of the latest maslow.yaml file so you can copy the values relating to your particular setup. Going from 1.06 to 1.07 does not require you to update maslow.yaml
Thank you Ian. I am currently at version 1.7. After retrying the extend all/apply tension several times, I found that the machine on a horizontal frame, would reset properly by pulling the machine down as if it was on a vertical frame. It seems to want to feel “downward” pressure on the “upper belts” before pushing the “apply tension” button, and re-orienting its coordinate system. That seems to have fixed my problem. Maybe it can help JeffOko.
Hello - I tried this twice again, once without pulling the sled as if it were vertical, the second time pulling the sled as if vertical. Both times failed. Here’s the output from both trials:
Attempt 1
Retract All
Extend All
Apply Tension
[MSG:INFO: Requesting state change from Taking Slack to Belts Extended]
[MSG:INFO: Succeeded]
→ Only upper right, lower left retract
Attempt 2
Retract All
[MSG:INFO: All belts extended to 1630.000mm]
Extend All
[MSG:INFO: Requesting state change from Extending Belts to Belts Extended]
[MSG:INFO: Succeeded]
Pulled sled down (as if hanging vertically)
Apply Tension
MSG:INFO: Requesting state change from Belts Extended to Taking Slack]
[MSG:INFO: Succeeded]
[MSG:INFO: Measured waypoint 2]
[MSG:INFO: Center point deviation: TL: 0.000 TR: -0.000 BL: -1.109 BR: 127.758]
[MSG:ERR: Center point deviation over 12.000mm, your coordinate system is not accurate, maybe try running calibration again?]
[MSG:INFO: Requesting state change from Taking Slack to Belts Extended]
[MSG:INFO: Succeeded]
→ Only upper right, lower left retract
The current state now shows Retract All, Extend All, Apply Tension, Calibrate and Stop all active
This looks to me like the machine is genuinely finding something wrong, not a bug.
Was there anything weird with the bottom right arm? Did you see both of the lower belts pull tight?
It being off by 127mm from where it would expect to be is a red flag that something weird happened for sure.
Bar - it took a while, but we decided to calibrate again, which was successful. After that we had no issues and made our first cut - we’re pumped to get started on projects! Thank you and everyone for your support.
Excellent, that is great to hear 