Auto Square - Axis Homing Wizard (Resolved)

[cnckeith]

hello. the entire process is described in the manual. please follow the auto squaring instructions to the letter and it works.
https://www.centroidcnc.com/centroid_di ... _guide.pdf
typically losing travel limits by interrupting the autosquare macro (at just the right moment) happens during setup and configuration. after you get is all working this rarely happens. and even if it does you have a good report.zip you made (dont you?) after you got it all working, so all you have to do to recover from an episode like mashing estop in the middle of a autosquare, would be to simple "restore report" to get right back where you were.

[martyscncgarage]

I had this same issue when setting up a dual Y axis machine recently and thought it was a bug in 4.20.1. I was confused why the limits would reset to zero during the auto squaring routine, this was Keith's response to me.....

"its not a bug, the auto square routines sets travel limits to 0 so it can move beyond them seeking the switch. then once home is set the routine puts the travel limits back in place.

if you interrupt the auto square routine at this point where the software limits are set to 0, they you get the result you observed.

restore report or hand enter the travel limits back and set up your switches correctly so slave hit first."

It seems a better way would be to "ignore" them during the auto square routine and not set them to zero but what do I know?

Gerald, I also like the individual inputs for each limit switch, this is how I wired my machine at home as I dont need all the available inputs. The machine I just retrofit used proximity switches and I wired 3 in series to one input with no issues.

It is not a bug and it's part of the auto squaring process.
The soft limits must be removed so as they are violated during the Autosquaring process, once completed they are restored. It the process is interrupted with an Estop, it's possible they aren't restored. Usually this may occur when the user is setting up Autosquaring. It is always advisable to have a known good report to fall back to by restoring it. Once Autosquaring is setup properly, create a fresh report again. It's usually not an issue after the machine is properly set up.

This will not be changed at this time, but may be revisited in the future.

[gerald martin]

Just wanted to update this thread that my question is resolved, thanks to help from Eric Schimelpfenig! I modified a macro that Eric developed (was able to keep all of my prox sensors on separate inputs) and my machine does home correctly and autosquares as well. Thanks Eric!

[martyscncgarage]

[url][/url]

Just wanted to update this thread that my question is resolved, thanks to help from Eric Schimelpfenig! I modified a macro that Eric developed (was able to keep all of my prox sensors on separate inputs) and my machine does home correctly and autosquares as well. Thanks Eric!

Good to hear!
It would be nice if someone did a video, and explained said macro
Marty

[gerald martin]

Hey Eric! Go right ahead!

[cnckeith]

the stock wizard generated autosquare method/macors is just one way of doing it. its my understanding that eric completely wrote his own gantry autosquare macro which is great thing that he did! we put the power to do that into our customers hands so they can modify and customize their machines tool they way they want.

[RichMaple]

This was a very helpful thread for me. Over the weekend I was adjusting some things on my machine, including playing with an oldham coupling on the slave Y drive. I must have turned it a few turns while working on it. When I told my machine to set home later on, it faulted out that the home switch triggered first on the master and not slave axis. I fixed this by manually turning my slave axis such that it would trigger slave home first as intended. But later on I crashed my gantry into the end bumpers and in trying to troubleshoot, saw that my software limits were all 0 (they previously had values in them). Yes, I can restore a report or just re-enter them, but knowing if homing doesn't complete, it leaves them at 0 is a VERY important and useful piece of info.

Can somebody tell me if they are left reset until I re-set them or whether closing down Centroid and restarting re-institutes the soft limits? Sorry if that's a stupid question.... I'm pretty new here

[martyscncgarage]

The auto squaring routine must complete in order to restore the soft limits.
Keep this in mind if your auto squaring routine does not complete. If it does not, you have to manually enter the original soft limits.

[ShawnM]

Can somebody tell me if they are left reset until I re-set them or whether closing down Centroid and restarting re-institutes the soft limits? Sorry if that's a stupid question.... I'm pretty new here

You have to manually reset them yourself, if the auto home does not complete they will be left at zero until you reset them in the wizard. The software will not reset them after a restart. I found this out just like you did when I retrofit a dual Y axis router and had the master trip before the slave while adjusting the home switches.

[RichMaple]

I know it's "not a bug" and I get that if a program/macro closes out on an error, there's no way to complete the script. But as person familiar with other programming languages, it's a little baffling. The program is still running if it's even capable of presenting the user with that "master tripped before slave" message, no? So why not save the soft limits in variables and reinstate them right before that error message (in that code block)?
I get that if you e-stop out the homing macro, you can't recover those soft limits. But it seems like that master tripping first is a fairly common problem, even if only for new users. Reinstating those limits in the same procedure as showing that error block seems doable. But again, I don't know how to code in this language, whatever it is....