another thing you can try is to carefully measure the 6 distances between your
anchors (including the diagonals) and put them in to one of the manual
calibration options instead of continuing to fight the automatic calibration
routine.
David Lang
another thing you can try is to carefully measure the 6 distances between your
anchors (including the diagonals) and put them in to one of the manual
calibration options instead of continuing to fight the automatic calibration
routine.
David Lang
The machine doesn’t stay connected long enough to complete the calibration. I wish this machine had an option to tethered. The wiring harness is there regardless, the computer being used will only be running the machine as well. So many people are having issues with connectivity.
So I am trying it again. I updated the .yaml file in case the old measurements were throwing it off and now I get the error “Calibrate
[MSG:INFO: Requesting state change from Belts Extended to Calibrating]
[MSG:INFO: Setting z-stop position]
[MSG:INFO: Unable to determine machine position]
[MSG:INFO: Succeeded]
[MSG:INFO: Measured waypoint 0]
[MSG:INFO: Unable to determine machine position]
[MSG:INFO: Center point off by: TL: nan TR: nan BL: nan BR: nan]
[MSG:INFO: Unable to determine machine position]
[MSG:ERR: Emergency stop! Stopping all motors]
[MSG:WARN: The machine will not respond until turned off and back on again]
[MSG:INFO: Requesting state change from Calibrating to Belts Extended]
[MSG:ERR: Unable to find machine position from measurements].
And here is the video of what I am doing.
Any help would be greatly appreciated!
Hmm yeah it looks like we’re getting some values that aren’t numbers in the system somehow. “nan” stands for “not a number” which is not what we want for our numbers. I will see if I can replicate that right now
Thanks! I am running v1.07 for firmware if that helps
That absolutely helps. I re-wrote basically all of the math in 1.08 so I was thinking maybe I just introduced this bug.
Can you try updating to 1.09 (which requires replacing the maslow.yaml file, the index.html file, and installing the firmware)?
There’s a chance that this bug is already fixed since this is exactly the bit of code that got heavily re-written.
sure, I’ll give that a try.
It fixed that error! we will see if it will finish now.
Excellent! Good progress ![]()
Joey Bassraft wrote:
It fixed that error! we will see if it will finish now.
If it doesn’t, let’s go down the path of manual measurements + calculations to
see if we can get you a usable system to ease your frustration. We still want to
track down what’s going wrong here so that others don’t have the same problem,
but at some point it’s better to get you working and ask for your help later.
David Lang
Well it got stuck… it completed the first round of calculations and them would go on for ever (I left it for about 4 hours)
I’m not going to mess with it this weekend, maybe next week I will keep working on it ![]()
I really appreciate this forum and look forward to getting my maslow up and running again!
Maslow-serial (4).log (317.4 KB)
This is REALLY close.
I wouldn’t worry about waiting for four hours, if it’s not done in 5min then I think it’s not worth waiting longer.
I would try again with a slightly smaller grid. I think that I changed the default to 500x500 in 1.09 and I think that was a bad call. It’s too tall and not wide enough.
I would try something way smaller like 300x300 first or 500 wide, 300 tall.
I waited 5 hours and it never finished calibrating. I tried using a smaller grid to calibrate, a larger grid to calibrate, and nothing made a difference. I tried pulling as advice via the video reposted everywhere on here but didn’t get a different result, even in the latest package. I tried to make it work for 2 month but nothing ![]()
Juan Salgado wrote:
I waited 5 hours and it never finished calibrating. I tried using a smaller
grid to calibrate, a larger grid to calibrate, and nothing made a difference.
I tried pulling as advice via the video reposted everywhere on here but didn¢t
get a different result, even in the latest package. I tried to make it work
for 2 month but nothing
have you tried doing a manual calibration to see if that gets you a usable
machine?
David Lang
Hey David, yes, my biggest issue is staying connected long enough to finish the calibration. I followed the advice from other uses of switching setting in the wifi properties and such. I was also in the garage so there were no other wifi enabled electronics around. I used the wifi created to maslow and never went through a home wifi or anything like that.
Juan Salgado wrote:
Hey David, yes, my biggest issue is staying connected long enough to finish
the calibration. I followed the advice from other uses of switching setting in
the wifi properties and such. I was also in the garage so there were no other
wifi enabled electronics around. I used the wifi created to maslow and never
went through a home wifi or anything like that.
a manual calibration is you measuring the 6 distances between the anchors,
entering them into a calculator, and then taking the resulting numbers and
putting them in the maslow.yaml file (either manually editing it, or through the
fluidnc config tab) this takes very little time.
the fact that you are still talking about the time to complete the calibration
tells me that you are still trying to run the automatic calibration
@bar I really do like the idea of renaming ‘calibration’ to ‘find anchors’, it
would need to happen throughout the documentation as well, along with notes that
it used to be called calibration.
David Lang
Hey David, yes, my biggest issue is staying connected long enough to finish the calibration. I followed the advice from other uses of switching setting in the wifi properties and such. I was also in the garage so there were no other wifi enabled electronics around. I used the wifi created to maslow and never went through a home wifi or anything like that.
I had connectivity issues when i was directly connecting to the maslow wifi as well, super frustrating, would disconnect all the time and couldnt reconnect without a power cycle. Get your home wifi so that the signal is nice and strong/close to the maslow and then connect to the maslow through your home wifi (There will be a tutorial somewhere) This fixed the connectivity issues. I agree that the device was released to the public with way too many issues but if you keep at it, make your own thread on here for support then you can get it working
Sounds like it could work, however, my home wifi signal does not reach all the way outside in the garage. I know there are portable wifis by the same companies like comcast and such but that would be an extra subscription. Its funny I’d need to pay a subscription to use Maslow lol.
WiFi extenders are fairly cheap. And no you don’t need to pay a subscription.