Yeah, that looks like it should work great.
Can you try changing how much belt is extended at the beginning? Maybe there is something weird about the spot that it is running the calibration?
When you press the âtestâ button you donât see anything weird, right? Firmware and index.html files are both v 0.88?
I am actually using .87. I could not get a good calibration with .88.
Index.html Version: 0.87
[MSG:INFO: Firmware Version: 0.87]
[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]
1 Like
OK, so this is where weâre stuck. We can get through calibration successfully, but then next time the system thinks that the calibration values arenât good enough to be able to move safely.
After calibration finishes if you move the machine around does it seem like everything is normal and moves smoothly?
Yes
So from off state:
I power on Maslow
Retract all
Extract all
Apply Tension
It complains about not being in center
I run calibration, it requires several runs to get to its happy place. A new calibration is generated and the values in the YAML file have not changed. I have downloaded the file several times after several repeats of the same procedure above. I run the files past diff and there are no changes.
The I try to run a part. It gets about 30 seconds in and there is the error.
What I have not done yet (I recently discovered where to see the error messages about what actually is happening) is to see if by moving the arms around the arm that throws the error moves. I have another encoder board ordered with the thought that I have a bad one of them.
The next thing that i am going to try is a horizontal frame that is the full height.
The one thing that I have noticed is that one arm always stays slack. I also noticed that I have the unit upside down in the frame. I got this unit second hand already assembled. I installed it on my frame with the power cord up and the dust port down. Which just seemed to make sense. I have tried running it reverse of how I had it and it made no difference.
Thank you for sticking with me.
Dave
1 Like
This sounds like it could be an issue. Do you mean that they havenât changed at all, or they havenât changed very much?
They change from the original but after calibration runs I do not see them change.
So there are lots of changes on the config yaml file revealed by diff from the original on github. But when I compare the yaml from the latest calibration it does not change values.
1 Like
Dave Waller wrote:
Yes
So from off state:
I power on Maslow
Retract all
Extract all
Apply Tension
It complains about not being in center
I run calibration, it requires several runs to get to its happy place. A new calibration is generated and the values in the YAML file have not changed. I have downloaded the file several times after several repeats of the same procedure above. I run the files past diff and there are no changes.
please post the yaml file. When you say it has not changed, are the anchor
values the default, or still the same as the prior calibration (I would expect
some change, even if itâs to the right of the decimal
The I try to run a part. It gets about 30 seconds in and there is the error.
What I have not done yet (I recently discovered where to see the error
messages about what actually is happening) is to see if by moving the arms
around the arm that throws the error moves. I have another encoder board
ordered with the thought that I have a bad one of them.
The next thing that i am going to try is a horizontal frame that is the full height.
The one thing that I have noticed is that one arm always stays slack. I also
noticed that I have the unit upside down in the frame. I got this unit second
hand already assembled. I installed it on my frame with the power cord up and
the dust port down. Which just seemed to make sense. I have tried running it
reverse of how I had it and it made no difference.
what matters is which arm is where, not the direction of the sled. The normal
direction is both power cord to the electronics and the dust collection down
David Lang
Dave Waller wrote:
They change from the original but after calibration runs I do not see them change.
So there are lots of changes on the config yaml file revealed by diff from the original on github. But when I compare the yaml from the latest calibration it does not change values.
can you please post the Maslow* variable from the yaml file? (or the entire
file)
Iâm surprised that a calibration doesnât change it at all. But if you have a
good calibration, you should not have to run it again. Which would mean we need
to look earlier and figure out why itâs giving the earlier error thatâs
suggesting that you need to calibrate.
@bar, is there a command to list the current belt lengths? (I would suggest that
the âunable to find centerâ error also output the anchor locations and the belt
lengths, more info will let us check the math and logic)
David Lang
Well I have good news to report. It must have not liked being upside downâŚ
I have it on the frame with the top arms on the top and ran the calibration which ended up with very good fitness numbers.
I retracted the belts, powered cycled and retract, extend tension and it is happy now.
Dave
1 Like
Oh and I am on v0.88 now.
1 Like
Dave Waller wrote:
Well I have good news to report. It must have not liked being upside downâŚ
when itâs flat, it wonât care much, but when itâs vertical, there are
assumptions about what belts gravity will keep tight and therefor the order to
tighten the belts.
I have it on the frame with the top arms on the top and ran the calibration which ended up with very good fitness numbers.
I retracted the belts, powered cycled and retract, extend tension and it is happy now.
fantastic, what fitness did you end up with?
David Lang
1 Like
Everything is working much better now. I shut it down and rotated the base so that the dust collection port is on the bottom and when it turned back on it was happy again.
I ran another calibration to get the fitness because i forgot to grab it before.
Fitness: 1.1830199257229108
Thank you very much for sticking with me. I am going to try to make a part now!
Dave
1 Like
Dave Waller wrote:
Everything is working much better now. I shut it down and rotated the base so that the dust collection port is on the bottom and when it turned back on it was happy again.
I ran another calibration to get the fitness because i forgot to grab it before.
Fitness: 1.1830199257229108
I think thatâs the best fitness Iâve seen reported.
Thank you very much for sticking with me. I am going to try to make a part now!
thanks for sticking through the headaches.
David Lang
1 Like
[MSG: /sd/kitchen-rib.nc file job succeeded]
Awesome!
2 Likes
Dave Wallerwrote:
Awesome!
how is the accuracy?
David Lang
1 Like
FANTASTIC!!! 
Great work sticking with it. And great work figuring it out! We had a lot of suggestions, but I didnât think to try that it could be upside down 
I also experience the belts going the wrong direction to retract. It was all 4 and was a big mess. It only happened once, and now I always watch to make sure they are going the correct direction.