Initial set up and calibration

How important is the squareness of anchor points? Mine are within 1/4 inch corner to corner. Do I need to get them closer?

Anchor points don’t need to be accurate much at all. Just solid so they don’t flex or move. mine have been inches off from a rectangle. No problem.

Bones wrote:

How important is the squareness of anchor points? Mine are within 1/4 inch
corner to corner. Do I need to get them closer?

I think if they are more than a foot or two out of position it can make the math
harder.

David Lang

1 Like

Just ran a find anchors first 5 waypoints gave me numbers in the mid 40s, 6-14 gave me numbers in the mid 20s and failed with final being .2476913.

I shut it down, ran the set up and still cant get a pass.

Maslow-serial.log (154.0 KB)

please advise.

Ran it one more time and the numbers look even worse.

Maslow-serial (1).log (30.8 KB)

What on earth am I doing wrong?

Frame is rock solid. I’ve torn down and reassembled this thing so many times I could do an instructional video. Corners are within 1/4 inch. Retraction is 725. Z is all the way down and set to zero. I just don’t get it. I have run find anchors so many times I’ve lost count. Ive seen this thing spit out numbers in the .60’s all the way down too .00’s. is something broken? Am I missing something?

I don’t think this is your problem, but you are running inconsistent versions
Index.html Version: v1.18-14-gecc35fa5
[MSG:INFO: FluidNC v1.19]
Update to the latest V1.20
At least that should get rid of the Failed to Compute Spam
Can you also drop a copy of your maslow.yaml file here and confirm the order of the arms is still per previous photo.

Bones wrote:

Ran it one more time and the numbers look even worse.

Maslow-serial (1).log (30.8 KB)

What on earth am I doing wrong?

Frame is rock solid. I’ve torn down and reassembled this thing so many times I could do an instructional video. Corners are within 1/4 inch. Retraction is 725. Z is all the way down and set to zero. I just don’t get it. I have run find anchors so many times I’ve lost count. Ive seen this thing spit out numbers in the .60’s all the way down too .00’s. is something broken? Am I missing something?

If I am reading this correctly, it didn’t get past the first 6 points.

I put them in a different calculation algorithm and it was giving me error bars
of ± 450mm for Z coordinates, so something is very wrong.

if the magnets are in the wrong place, it can have trouble reading their
positions.

when you do a retract-all it reports the difference between where it thinks the
belts would be and where they actually are (which is 0 length)

when you first turn it on and retract the belts, this will in effect tell you
how far out the belts were.

But after that, if you extend and retract the belts, this should give you near
zero measurements (commonly under 0.1mm), if it is giving you different results,
then it could be you put the roller with the magnet in the wrong spot or upside
down.

please do a few extend/retract cycles and see what you get.

a video of the machine doing the find anchors routine may give some clues. the
belts should be pulling tight at each of the 6 measurement points.

David Lang

What happened between Measured waypoint 4 and Measured waypoint 5] the first time. It looks like Stop was pressed and then belts retracted and extended again. If Find Anchors is interrupted, you need to power off, unhook the belts and do the full power on, retract, extend, mount anchors again or the belt readings will be wrong.

I verified all the magnets are in the right location (driven side of belt, magnets facing the sensor)
Spools are stacked in the right order top to bottom
1 bottom left
2 top right
3 bottom right
4 top left

Ran 4 retract extend cycles.

Maslow-serial (2).log (6.4 KB)

the numbers keep coming up different each time, is this normal?

I’ll load a video of the anchor calibration tonight when I get home from work.

The belts are pulling tight at each waypoint measurement. The highest waypoint I’ve achieved thus far in the whole process had been 30.

I ran the Z all the way down and set the home. The small position numbers above the button show Z at zero consistently.

that was the first time it has spit out the spam during this whole ordeal.

maslow.yaml (6.5 KB)

yaml as requested

Can’t see anything wrong in there. I think there is a problem with the find anchors program. Suggest you try reverting back to Version 1.15 to run the Find anchors. If you do, go to the setup menu and set the retract value and config values to 700. Let me know if that works, because it will give us a better idea of what is going wrong in the later versions.

On further looking if I interpreted how your arms are ordered correctly from the photo, then from the bottom we have BR, TL, TR, BL. If this is still how they are set then they don’t match the offsets in your maslow.yaml file. You need to set Z for each as follows tlz: 78, trz: 56, blz: 100 and brz: 34
To change these, go to FluidNC, Config Items then go down to
/kinematics/MaslowKinematics/tlZ and change setting to 78 and Set
Do the same for each of the other Z values then go back up the top and Save
Force a re-read by powering off and back on then
Try Find Anchors again.

I believe i corrected the spool stack.

1 top spool… closest to top of router
4 bottom spool… closest to the sled

I thought that was likely it. Damn. Did you try V1.15? you will get some ignored fields on start up. They shouldn’t matter.
I have tried running V1.20 on my machine with the supplied maslow.yaml and am getting bad results, which is why I suggested you go back to V1.15. Once you have good Anchor Points you should be able to go to the later versions. Calibrate force was changed to just retraction force, which is why I said to set it again if using V1.15.
Also change Maslow_calibration_grid_width_mm_X and Y to 0 from 400
and set grid size to 9

I’ll have to get into github and find 1.15… I actually hate that site its like shopping in a busy walmart full of screaming kids. Too much stuff going on in there.

Go to Maslow Home (At top) then Resources down to Firmware, then go down to V1.15 or here they are

firmware.bin (1.9 MB)
index.html.gz (127.6 KB)

1 Like