Hi, just finished (ish) building my M4 and did the firmware update and uploaded the 2 other files needed. I can move my z-axis to touch the bottom and retract and extend the belts. I mounted my Maslow on a temporary frame (just 4 screws lol) and got it to the stage where you extend after retracting and mount the belt ends on the anchor.
Problem is, when clicking “find anchor points” it says that the initial position is way way off and does an emergency stop, so I have to restart the machine and start the whole process again. I did everything in this video and chose horizontal mode.
What went wrong? I’m a new user so can’t upload attachments so I will have the log and picture after the end of this topic
Thanks,
Eldar
Log:
Serial Messages
Index.html Version: 1.11
[MSG:INFO: Channel auto report interval set to 50 ms]
Retract All
[MSG:INFO: Retracting all belts]
[MSG:INFO: Requesting state change from Unknown to Retracting Belts]
[MSG:INFO: Succeeded]
[MSG:INFO: Bottom Left pulled tight with offset -2173.467]
[MSG:INFO: Top Right pulled tight with offset -2176.773]
[MSG:INFO: Bottom Right pulled tight with offset -2165.597]
[MSG:INFO: Top Left pulled tight with offset -2185.180]
[MSG:INFO: Requesting state change from Retracting Belts to Belts Retracted]
[MSG:INFO: Succeeded]
[MSG:INFO: Spoilboard thickness set to 0.000 mm]
[MSG:INFO: Work thickness set to 0.000 mm]
[MSG:INFO: Spoilboard thickness set to 0.000 mm]
[MSG:INFO: Work thickness set to 0.000 mm]
[MSG:INFO: Spoilboard thickness set to 0.000 mm]
[MSG:INFO: Work thickness set to 0.000 mm]
[MSG:INFO: Spoilboard thickness set to 0.000 mm]
[MSG:INFO: Work thickness set to 0.000 mm]
Extend All
[MSG:INFO: Extending all belts]
[MSG:INFO: Requesting state change from Belts Retracted to Extending Belts]
[MSG:INFO: Center coordinates updated in MaslowKinematics: X=2197.631 Y=1647.726]
[MSG:INFO: Succeeded]
[MSG:INFO: All belts extended to 1000.000mm]
[MSG:INFO: Requesting state change from Extending Belts to Belts Extended]
[MSG:INFO: Succeeded]
Calibrate
[MSG:INFO: Requesting state change from Belts Extended to Calibrating]
[MSG:INFO: Calibration starting in HORIZONTAL orientation mode]
[MSG:INFO: Setting z-stop position]
[MSG:INFO: Center coordinates updated in MaslowKinematics: X=2197.631 Y=1647.726]
[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: -1518.593 TR: -1517.345 BL: -1631.172 BR: -1612.061]
[MSG:ERR: Center point off by over 100.000mm]
[MSG:ERR: Unable to adjust frame size. Not centered.]
[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 a valid frame size to match the first measurement]
[MSG:INFO: Channel auto report interval set to 50 ms]
[MSG:INFO: Channel auto report interval set to 50 ms]
What went wrong? I¢m a new user so can¢t upload attachments so I will have the
log and picture after the end of this topic
I just saw some work that @bar was doing on github that may be related. the
system is doing position determination in cases where it’s known to not have
enough information to do so.
he was supressing messages, but it may be that he needs to supress the check
entirely, not just the message.
I would suggest waiting until the next firmware update and give that a try
(unless bar speaks up and suggests something else)
How far apart are your anchor points? In the photo they look pretty close.
Starting with the Maslow power cord positioned on one of the longer sides, the power cord side is considered down. So the anchor points on power cord side are BL (Bottom Left) and BR. The opposite (Up) direction TL & TR.
Also press the Test button on the Setup menu and confirm that both version numbers are the same
eg
Test
Index.html Version: 1.11
[MSG:INFO: Firmware Version: 1.11]
[MSG:INFO: I2C Timeout: ]
[MSG:INFO: 10]
[MSG:INFO: All tests passed on Top Left]
[MSG:INFO: All tests passed on Top Right]
[MSG:INFO: All tests passed on Bottom Left]
[MSG:INFO: All tests passed on Bottom Right]
Thanks, I will do the measurements, and my “frame” is about 1.5m on 2m
”TR → TL, BR →”, do you mean that I should put this values somewhere or just write them down by this order and reply to you?
I did noticed now that my top left anchor was off where it should have been by 10cm downwards, but the error I got is much much bigger so I don’t think that was it, but will test it again tomorrow with the right placement
First of all I LOVE your minimal frame. That is fantastic.
The issue seems to be these lines of code which have been in the firmware for a long time now, but I haven’t seen them triggered before:
//Check that we are in fact on the center line. The math assumes that we are roughly centered on the frame and so
//the topleft and topright measurements should be roughly the same. It doesn't need to be exact.
if (std::abs(tlLen - trLen) > 20) {
log_error("Unable to adjust frame size. Not centered."); //There exists a more generalized solution which should be implimented here: https://math.stackexchange.com/questions/5013127/find-square-size-from-inscribed-triangles?noredirect=1#comment10752043_5013127
return false;
}
I think that what is going on here is that we used to keep the top two belts still and tighten the lower two belts so it was safe to assume that we would always be on the center line.
Since we’re now retracting all four belts it is easier for one of the top two belts to end up being shorter or longer than the other one.
The comment shows that I already had a plan to implement a more generalized solution which handles that case so I will make that a priority and get that implemented ASAP.
Can you try running it again and see if it happens consistently? I’m curious if it happens every time or if it was a fluke.
Thanks! Inner sloth is happy
Just tried in on a bigger frame, got the same error but this time the numbers were off by about 900mm each instead of 1500mm, could it be that for any small frame this error will happen? maybe i should change the values here?
And now my belt got stuck and came out in a bad shape
Maybe I should cut it there lose that extra meter but wont have to order wait and install a new one? In the way it does calibration it seems it wont matter right?
measure the diagonal distances and set the distance to extend to (the longest
diagonal - 250m)/2
I am thinking that you are extending it out the default amount, and with your
smaller frame, it’s then not retracting evenly.
by setting the distance to extend close to what you actually use, i’m thinking
it will improve your problem (the actual minimum length will be about (diagonal
-300)/2 but using 250 will give you a bit of slack)
