|
Register | Options | Profile | Last 1 | 3 | 7 Days | Search | Today's Posts | Mark Forums Read |
|
Thread Tools |
#1
|
|||
|
|||
Using limit/home switches to autosquare the gantry
Originally in another thread
J.R. Are you using one or two limits for the gantry (i.e. at each x motor)? I planning on using two so that the machine is auto squaring every time one zeros but that requires two inputs to the BOB. (one common for Z, Y and X1 and the second for X2) |
#2
|
|||
|
|||
Alan I used 1 limit switch on the gantry. I'm running both steppers with 2 geckos 1 bob signal.
|
#3
|
|||
|
|||
Quote:
When homing a dual drive axis Mach does one side followed by the other. So just as X, Y and Z can share an input so can X slave. (I believe) They can be made to home simultaneously with a custom script but sequentially is the Mach default. I realise if you have not seen this happen it probably sounds far fetched. Why would a slaved axis home sequentially? But when you've seen a slaved axis home you'll say "Oh I see what you mean" Greg |
#4
|
|||
|
|||
I think I said that auto-squaring needs another BOB input, but I might be wrong. The auto square of the gantry could work on one BOB input if the sequence is as follows:
1. both motors drive until input goes off (switch opened) 2. both motors back off until circuit closes 3. one motor (A) drives until circuit opens 4. motor A backs off until circuit closes 5. motor B drives until circuit opens 6. motor B backs off until circuit closes There is a reasonable assumption that the gantry is not far out of square to begin with. Steps 1 & 2 put the gantry in the ballpark. Step 3 might make it worse for a while. After step 6., Mach may do fine tuning and repeat 3 & 4 ? |
#5
|
|||
|
|||
Gerald here is what appears to happen. It happens pretty quick.
You press "Ref All" Z axis does it's homing thing. Then both motors (X axis) wander off toward the home switches. Hits X home switch and backs off. Both motors do this. A axis then goes on it's own. Hits A home and backs off. X motor does not move. Then Y axis does it's homing thing. As I say it happens quick but that's how it happens as Mach default. This is why I say that X and it's slave (A) should be able to share an input. Greg |
#6
|
|||
|
|||
Quote:
The only way your logic (as observed) will work is if A was intenionally lagged (held back) during the run, so that it is known X will touch first. But that could be risky. |
#7
|
|||
|
|||
Yes I see your logic. Gantry out of square and A opening before X
Maybe that is reason enough that separate inputs are in fact needed. Good clear thinking there Gerald. Greg |
#8
|
|||
|
|||
The 1 to 6 logic should work on one input...no?
1. both motors drive until input goes off (switch opened) 2. both motors back off until circuit closes 3. motor A drives until circuit opens 4. motor A backs off until circuit closes 5. motor X drives until circuit opens 6. motor X backs off until circuit closes |
#9
|
|||
|
|||
I'm not sure if this can be done. The slaved axis homing sequence is hard coded.
Whether it can be made to do your sequence by use of a clever script.... I know that I have got mine doing it simultaneously by using the "RefCombination" command. This probably needs some thought and a bit of experimenting. Greg |
#10
|
|||
|
|||
Greg, this may be interesting:
http://groups.yahoo.com/group/mach1m.../message/35535 Greg, having looked at various posts on the Mach forums, the motion you are seeing is the way that Art wrote Mach. That logic does seem faulty. Art also once said . . . "you can home with the switches being the same for limit or home, ( or not) , and home with slaved axis ( the slave mey be the same switch as the master axis, or different if you wish to autosquare. )" ......which left me with the impression that autosquare required 2 switches. I will make a post to the Mach Yahoo to see if I can make some sense of this. |
#11
|
|||
|
|||
Quote:
Greg EDIT, In the second post you linked to he was talking about the G100. The external devices do homing differently anyway so that may not necessarily apply to the LPT. Last edited by Greolt; Sun 03 February 2008 at 02:34.. |
#12
|
|||
|
|||
I'm probably going to open my mouth here and show my ignorance. If you were running the grantry with motors X and A (A as the slave). Could you use softlimits somehow to square the thing??
|
#13
|
|||
|
|||
As great as what soft limits are.....they are unfortunately not that great....
Realise that we only really need to "square" the gantry if it is out of square. ie. we either moved one end of the gantry while the motors were off, or we overloaded the one gantry motor and only that motor skipped steps. Under both of these conditions, soft limits are messed up too. A little demo for you JR; Set your soft limits to stop within 1" of the mechanical stops. Switch motors off. Move gantry 2" by hand. Switch motors back on. See where your soft limits are now located (move slowly - one end will hit the stops). If your soft limits stay set for weeks, then your gantry will stay square as well. |
#14
|
|||
|
|||
In my test set up, autosquaring uses two inputs. One is for Z, Y and X1, the second input is for X2 (or A).
This is the sequence as observed: On ref all... 1. Z moves positive (up) until it reaches the limit, then reverses until the switch closes again... 2. Y moves negative (to 0) until it reaches the limit, then reverses until the switch closes again... 3. Both X motors move negative (to 0) until both limits (two switches) are open... 4. Both motors reverse rotation until the switches close again... 5. X2 (or A) motor then moves negative again until its switch opens, then reverses until the switch closes again. If the switch ramps are correctly positioned, the gantry will now be square. This arrangement uses two inputs to the bob: switches Z.Y and X1 in series to one input and switch X2 to the second input. If autosquaring is not required or if you are using shared drives for the X motors then only one input is required (you dont need the second X2 switch) |
#15
|
|||
|
|||
Alan, that would be square and correct if motor X2(A) has its own switch, like yours does.
But Greg seems to think that only one switch is necessary (post #3)? |
#16
|
|||
|
|||
When Mach is homing the X axis using slaved drives, it must have two inputs for the limits to enable it to square. The motors only get the signal to reverse once the switch is open for that particular side.
If X1 switch opens, X1 motor reverses, but X2 motor continues to move in the original direction until its switch opens therfore they cannot share the same circuit. I tried this on my test rig using two switches, when only one switch is actvated that motor reverses, the second motor continues until the second switch is activated, it then reverses until the switch is closed. when the second switch closes, the motor (X2) again moves to make the gantry approach the limit which makes the switch open again, this sends a signal to reverse the motor again until it is off the limit. the short answer is if you want to autosquare, you MUST have two switches and two inputs. |
#17
|
|||
|
|||
Quote:
However having said that playing around with the scripts which set this in motion has me suspecting Mach may be made do things that the author did not intend. But here is not an appropriate place to get into that. Only offers confusion for MM builders. So lets leave it that two inputs are needed for the X axis auto squaring feature. Greg Last edited by Greolt; Mon 04 February 2008 at 02:00.. |
#18
|
|||
|
|||
Okay, I think we have it clear how the current Mach3 does autosquaring.
Now I just need to convince Brian Barker that he could modify Mach3's embedded scripts so that the process is executed off only one switch circuit. The BOB sales people won't like it though. Sorry if I led you astray Greg - it is a character trait drummed into South Africans to dupe Ozzies whenever they can . |
#19
|
|||
|
|||
I see you are not making much progress on the Yahoo forum.
Questions are often not read very well before an answer is shot off. I have been guilty of this myself. Greg |
#20
|
|||
|
|||
Poor old Brian has a lot on his plate. He is not going to get interested in saving a single BOB input now. Besides, if he does that, he is going to confuse the "old guard" who are wired with 2 switches. The only way to make progress on that forum is to get the "old guard" to bite on an idea - heck, they can't even move to a modern forum!
|
#21
|
|||
|
|||
considering options
Just a stupid addition to an intelligent thread,..
Some months ago I asked about "homing" both X 's. http://www.mechmate.com/forums/showt...13&postcount=6 I was told by Gerald that we never loose steps and a good way of homing is to turn off the motors and push the Gantry against the stop blocks on both sides. That seemed all we would ever need at that time, and, as we didn't need to steer the 2 x's individual, it allowed us to double the x axis and free up one on the BOB board. I do like the idea of having the extra axis as I have the challenge in mind to turn a piece into different planes and then work that plane with all 3 axes. Like, to make corbels and so. So here's an idea, - Go home according to mach3 based on the 1 limit switch on your main X. - Then, ignore the limit switch and run straight through it until you hit the stop blocks on both sides. The Geckos will limit the motor’s current so running both against the stop blocks for half a second should hurt anything - Then, back up until the limit switch goes off - You’re square and home! Right? … Am I making any sense? … Stefan |
#22
|
|||
|
|||
Hi Stefan,
When we are lazy, we do that (drive against the stops). Last year I asked a question over here: http://finance.groups.yahoo.com/grou.../message/12975 And that sure resulted in a heated debate, even some shouting. But, between all the noise, it was clear that neither the motor nor the drive will get damaged. |
#23
|
|||
|
|||
So I don't know Mach3 well enough. But can you override the limit switch, make the X-motors push against the stop blocks, back up, and then home again to make sure you're square? (on one x limit switch)
|
#24
|
|||
|
|||
Yes, you can override limits (left side of Settings screen) to push against the blocks, then re-engage limits to home again. But, if you use this method, why do want to have a switch at all? Push against the stops and call that "home".
There are so many options! |
#25
|
|||
|
|||
Copied from another thread
John, Let's see if I can explain. Mach is funny, that it actually has a built-in homing macro for finding home. It is designed to step through it's seek-n-find sequence going x, then x1, then y, then y 2, then z. Depending on the number of motors you have and such, it will configure the routine to home accordingly. If you have and x1 and x2 motor, then the auto squaring feature will be active. If you choose to use this feature, be prepared to make the eccentric holes in the rail adjustable to fine tune the "perfect square" of the machine. .... back to explaining. Since Mach already does this homing routine, you can wire the contacts in series to one input on the BOB. The downfall to this "series relay logic" is for some reason any of the axis' that is active is triggered by a limit/prox switch not on that axis, the machine will be improperly homed and usually ends up derailing the machine. The only time this happened is when I physically triggered a prox sensor on an "alternate" axis during the routine to see what would happen. Good thing my estops work! The mach3/artsoft manual explains the routine in detail. Does this answer your request? Sorry for the delay - I have been out on vacation for a while. refer to my post WAY back in time for the wiring part of this reply. Sean |
#26
|
|||
|
|||
Sean
Do you have slaved axis homing working to "square the gantry" with all home switches sharing an input? I ask this because it has been my experience after helping many Mach users set up slaved axis homing, that for whatever reason, many can only get it to work by using the RefCombination command. When using RefCombination you must, by definition, have the slaved axis home switches on separate inputs. Brian of Artsoft, always recommends using RefCombination for slaved axis homing. In fact, I think he believes it is the only way it will work, although I know that is not so. I don't use it. Greg |
#27
|
|||
|
|||
Greg,
Good to hear from you. I haven't tried this in a while so your most likely right about the RefCombo. I found that the machine actually works better (both of them #5 and #28) by NOT using them. I just mechanically set the square of the machine on the hard stops, engage the racks. I only use the prox sensor on the x2 rail for sensing "home" during the routine. My x1 and x2 motors share steps between the BOB and the G203 drives via a "Y" cable. Note: this is so I have the 4th step/dir output available for my indexer. ...Now I just might go and try it sometime soon during my next build which starts next week! Yeah - machine # 3 - PLASMA cutter. |
#28
|
|||
|
|||
G'day Sean
My recommendation would be to have the two home switches on the slaved axis to be on separate inputs. Until I hear of a couple of users with equivalent experience to yourself, successfully using a shared input for slaved axis homing, I will stick with that recommendation. Greg |
#29
|
|||
|
|||
Quote:
As far as Mach is concerned you do not have a slaved axis. You have a cloned axis. There is a big difference. X axis signals are being sent to both motors driving the X axis by virtue of the way you have it wired. It is not possible to "Auto square the Gantry" with Mach using this setup. When Mach homes a slaved axis, it first de-couples the two axis, deals with them separately, and then re-couples them together at the end of the homing routine. Of course this is not possible when both sides are running from the X axis signals. As far as Mach is concerned there is only one motor on X. So if you have slaved motors driving the X axis, and you have a home switch on both sides with the intention of "auto squaring the gantry" then they must not share an input. Greg |
#30
|
|||
|
|||
Greg,
I won't spend a lot of time here, but you are correct. My point that I didn't get across was I had them separate and slaved and didn't get the added benefit of auto squaring when the machine design allows for mechanical squaring of the y axis. Thus, I freed up my BOB output #4 so I didn't have to buy another card for the added axis. Plus, on my Multicam 1000 series, the 3:1 drive belts always seem to break when the machine was "auto squaring". Which was about 1 to 2 times per year. Really annoying. But, in retrospect, it was fun trying the auto squaring function before I changed it back on this MM. The machines that I am aware that are similar in control this sharing of the axis steps are: #5 Nils MM #28 ...Any others? Sean |
Register | Options | Profile | Last 1 | 3 | 7 Days | Search | Today's Posts | Mark Forums Read |
Thread Tools | |
|
|