I have a 12 x 8 frame with a centered 8 x 4 spoil board. I used 3600x2400 in the yaml.
The sled drives off the spoil board into air during calibration. It is worst top, left and right. The bottom is not as bad in that it only goes to the center of the sled where all the others go past center.
I think that this is normal. You can change the value for Maslow_calibration_offset in the configuration file if you would like to move that point down a bit. A value of 500 (the default) means that it will try to put the top corner calibration point 500mm in X and 500mm in Y from the top anchor point which on a 12’ frame is going to be right about there.
You can tweak that number if you would like, but it looks like that is the correct behavior to me
Any thoughts on Why it quits and never moves on again. It stops where it stops, and the computer never gives any more response, even after Waiting for an extended period of time. I would at least expect to see that it is Computing. I am using a Mac with Safari if that makes any difference
Yes, I think I know exactly why. I think that the calibration answer is appearing in the text box on the right, but it’s not scrolling down automatically to make it visible. That’s on my todo list to investigate and fix today. Try scrolling down in that text box and let me know if the answer is there
Bar, i was watching video of calibration and i am wondering in vertical frame how much would being on an incline affect the calibration. I just ordered lumber for what i was going to build and even our parking spaces are not level. Seems to me it would affect with more weight on one belt vs the other. Wondering of horizontal calibration would be better?
There is something that I don’t understand that I am digging into right now which is that
Someone else pointed this out and I fixed it, but I’m realizing now that I never see this print during the calibration process. I see it in the code, and it seems like I should be seeing it, but I’m not.
Are you running both the latest firmware and latest index.html files from Releases · BarbourSmith/FluidNC · GitHub? (Just to try to make everything the same as possible)
I have an old Intel Mac that has been set to never sleep so I dug that out and used it. It completed the process and gave me the results. Lots of repeating results in brackets. I will need to go decipher that.
I am thinking, maybe your first thought was the correct thought.
I believe this, Mac got further into the process than previously. There is a message that states calibration complete. And then it goes into a bunch of bracketed results.
I’m glad to hear it, but I want to figure out what the issue was.
You think maybe the issue was with the computer falling asleep?
The easiest answer is to install the latest one and then you will know it’s up to date. Adding the firmware version number somewhere in the UI is on my todo list.