If this is your first visit, be sure to
check out the FAQ by clicking the
link above. You may have to register
before you can post: click the register link above to proceed. To start viewing messages,
select the forum that you want to visit from the selection below.
In my experience doing CNC retrofits using Mitsubishi systems or even home built using the Galil Motion cards, I would consider servo positioning to a dozen encoder counts a gross error and unacceptable.
-I know for a fact that, on my Omniturn with servos, if the "count" is one off from the commanded motion, it stops and throws an alarm.
Gonna set aside the servo/spindle thing for now. It's more work for less gain than I have time for right now. To take care of current needs, I'm going to try and find an indexer that can be used in the CNC mill. Won't be cheap, but it'll be a lot more plug-and-play.
-I know for a fact that, on my Omniturn with servos, if the "count" is one off from the commanded motion, it stops and throws an alarm.
Doc.
that is not possible. Servos work because of error. A quick search for omniturn - it looks like you set the following error during jogs to a max of 70 counts.
5. Re-check Servo Amp following error After re-adjusting the balance, be sure to jog back & forth at Jog 2 and re-adjust the Tach pot for 70 ± 2 counts. Ctrl-E again to close the Following Error box.
A control usually has a minimum following error and max following error - (as the machine moves faster - the error is allowed to increase.)
My little emco compact 5 that I converted to servos - I can deflect the servo with my finger about +/- 4 encoder counts - each count is .000019". At 200ipm - I get a error of .0001" about. That is the best tune I have personally seen. (for something I threw together..)
that is not possible. Servos work because of error. A quick search for omniturn - it looks like you set the following error during jogs to a max of 70 counts.
5. Re-check Servo Amp following error After re-adjusting the balance, be sure to jog back & forth at Jog 2 and re-adjust the Tach pot for 70 ± 2 counts. Ctrl-E again to close the Following Error box.
A control usually has a minimum following error and max following error - (as the machine moves faster - the error is allowed to increase.)
My little emco compact 5 that I converted to servos - I can deflect the servo with my finger about +/- 4 encoder counts - each count is .000019". At 200ipm - I get a error of .0001" about. That is the best tune I have personally seen. (for something I threw together..)
sam
Sam has it correct. There is always some error count in a servo system its just a matter of minimizing that error count.
Also, in the real world you have to consider how servo counts relate to actual position. The number of "lines" resolution of the encoder is one factor there, a encoder can be anywhere from 256 counts/rev up to over 50,000 (some newer fanuc stuff). Then there is a "gear ratio" of sorts determined by the ballscrew pitch and any belt drive ratio that basically forms a multiplier in converting encoder counts to inches.
Moral to the story is that a few encoder counts of error is NOT going to normally relate to any movement/positioning error of a magnitude to be concerned about. Sam's example of his machines numbers shows this well.
True if the system is a "feedback" system. The only thing that makes it move is an error between the "desired" position and the "reported" position from the position feedback. If an external force deflects it from the desired position, or prevents it from moving to the desired position, there will be an error reported, and the system will try to move back to the desired position.
If it ever reaches the desired position, the restoring force would be zero, since there is no error, and no reason to move. Any force applied would move to a position with an error in excess of the desired position, and it would move back
In order to resist a deflecting force, there must be some error sufficient to cause the system to develop the force needed to resist the deflection. In an analog system, the restoring force depends on the deflection. In a digital system, there theoretically would be full restoring force for any detected deflection. In practice, that could lead to an oscillation, so there is some means to avoid that, which may lead to more than one "count" of error, depending on how much force is required to move closer to the desired position.
But the error must always exist, or the system cannot operate.
You can see that actually moving to the desired position would lead to zero force. So then the external force could push the cutter (or whatever) back, at which point the system would see an error and try to correct it. If it did correct the deflection back to zero, the correcting force would go to zero, and the cycle would repeat.
While there cannot be a "resisting force" applied when in the desired position, there can be a "brake" applied, such as holding current in a motor, etc, to hold the existing desired position. That may or may not be sufficient to prevent moving out of the desired position. It is best viewed as "friction" and not as a force that is "actively resisting" any external forces, and has nothing to do with the feedback action, nor required errors.
CNC machines only go through the motions.
Ideas expressed may be mine, or from anyone else in the universe.
Not responsible for clerical errors. Or those made by lay people either.
Number formats and units may be chosen at random depending on what day it is.
I reserve the right to use a number system with any integer base without prior notice.
Generalizations are understood to be "often" true, but not true in every case.
A servo worth a damn has an encoder with enough counts that a small error is of no real world consequence. Besides the servo will hunt the error down and not let it grow.
All I do know is it takes a very, very minor error before the Omni control throws an "out of position" fault.
And either way, it's just not a feasible mod for the Logan right now (cost and time) or for the Omni itself (just cost- to the tune of $5K or more). An indexer for the Trak mill won't be cheap either, but that one would have a lot more utility- I have a fistful of projects lined up for that one.
All I do know is it takes a very, very minor error before the Omni control throws an "out of position" fault.
And either way, it's just not a feasible mod for the Logan right now (cost and time) or for the Omni itself (just cost- to the tune of $5K or more). An indexer for the Trak mill won't be cheap either, but that one would have a lot more utility- I have a fistful of projects lined up for that one.
Doc.
If you follow Skunkworks advice and go with Mesa and Linux CNC, pretty sure there is nothing you can't do, DIY.
If you follow Skunkworks advice and go with Mesa and Linux CNC, pretty sure there is nothing you can't do, DIY.
-Yes, yes, I know, LinuxCNC is the end-all, be-all of CNC software, and it's only the short-sightedness of the manufacturers that anyone is still bothering with inadequate crap like Fanuc and Siemens.
But in this case, the control part is already taken care of. The project is to do some radial drilling in a round part. The Logan, with it's Centroid control, can easily run a "C" axis, the issue is simply the cost and labor of converting the spindle over to a decent servo drive.
The Omniturn control also already has the capability to use a C-axis, and all I'd need to do is buy the parts, off the shelf, from Omni. Unfortunately that's rather expensive at about $5,000.
The Trak mill can natively run most typical indexers, whose control boxes accept fairly standard "start indexing" and "I've stopped indexing" signals. Such indexers are available off the shelf and plug-and play... but also for about $5K, used.
Currently, my cheapest option, is that I have a nearly-completed CNC conversion of a little Grizzly mini-mill. That was a project from a friend, who was supposed to trade me some CNC training, in exchange for my fixing his badly-converted machine. Right now it needs little more than wiring, and I already have a complete, running Centroid PC for it. I figure I get one of those little cheap Chinese $300 "4th axis" units off eBay, and I could be drilling the radial holes for a couple weeks work and maybe $500 in parts.
I will end up with an 5C indexer for the Trak one of these days, I have plenty of other parts that could use it. But right now, funds just aren't there for it.
-Yes, yes, I know, LinuxCNC is the end-all, be-all of CNC software, and it's only the short-sightedness of the manufacturers that anyone is still bothering with inadequate crap like Fanuc and Siemens.
But in this case, the control part is already taken care of. The project is to do some radial drilling in a round part. The Logan, with it's Centroid control, can easily run a "C" axis, the issue is simply the cost and labor of converting the spindle over to a decent servo drive.
The Omniturn control also already has the capability to use a C-axis, and all I'd need to do is buy the parts, off the shelf, from Omni. Unfortunately that's rather expensive at about $5,000.
The Trak mill can natively run most typical indexers, whose control boxes accept fairly standard "start indexing" and "I've stopped indexing" signals. Such indexers are available off the shelf and plug-and play... but also for about $5K, used.
Currently, my cheapest option, is that I have a nearly-completed CNC conversion of a little Grizzly mini-mill. That was a project from a friend, who was supposed to trade me some CNC training, in exchange for my fixing his badly-converted machine. Right now it needs little more than wiring, and I already have a complete, running Centroid PC for it. I figure I get one of those little cheap Chinese $300 "4th axis" units off eBay, and I could be drilling the radial holes for a couple weeks work and maybe $500 in parts.
I will end up with an 5C indexer for the Trak one of these days, I have plenty of other parts that could use it. But right now, funds just aren't there for it.
Doc.
Looking at the HAAS stuff, it was very apparent they are designed around your employees operating the machines, not you. That is one reason you go with industrial controllers I guess.
Looking at the HAAS stuff, it was very apparent they are designed around your employees operating the machines, not you. That is one reason you go with industrial controllers I guess.
-I'm... not really following you.
One, virtually all the indexers you're going to find are "industrial". The 'home shop' stuff is manual- dividing heads and manual rotary tables and the like. You go automatic for production, and production means industrial.
And two... is there a reason you wouldn't want your employees operating the machine?
An indexer (as opposed to a true 4th axis) is generally a stand-alone, add-on device. Like the manual dividing head, you bolt it to the table and mount your parts in it.
The mill mills a flat or drills a hole or whatever, and then sends an "index now" signal to the indexer's controller. The standalone controller then turns the part- you tell it X number of degrees, which direction, how fast, etc. Once the indexer has finished moving, it sends a "I'm done indexing" signal back to the mill, which then proceeds on with the program.
All of this, save for the cheap Chinese "CNC router" axes/indexers you can find on eBay, are all going to be industrial accessories- meant to live in coolant, turn to sub-seconds-of-angle accuracy, and hold solidly enough for high-feed production milling. There is, near as I can tell, literally nothing between a $300 Ebay Special, or a $5,000 industrial unit.
Certainly wouldn't be very difficult to make one. Just get a servo, a brake, a couple of bearings, a few chunks of metal, and some control software. Shouldn't cost more than a few hundred dollars if you're a good shopper.
Oh sure. Something I can do in my spare time, with parts I already have laying around the house.
Realistically, the work I need to do is low-force, and I could probably get away with a cheap Chinese "4th axis" meant for a router or something- basically just a chuck, a bearing block, a stepper and a belt reduction.
And I [i]have[i] been thinking of maybe trying the same thing with something like a spindexer- I'd rather have a 5C than a chintzy 4" Chinese 3-jaw. But no matter what, kind of the last thing I need right now is another project. My "stuff to do" list just for the month of May, already extends into 2025.
One, virtually all the indexers you're going to find are "industrial". The 'home shop' stuff is manual- dividing heads and manual rotary tables and the like. You go automatic for production, and production means industrial.
And two... is there a reason you wouldn't want your employees operating the machine?
An indexer (as opposed to a true 4th axis) is generally a stand-alone, add-on device. Like the manual dividing head, you bolt it to the table and mount your parts in it.
The mill mills a flat or drills a hole or whatever, and then sends an "index now" signal to the indexer's controller. The standalone controller then turns the part- you tell it X number of degrees, which direction, how fast, etc. Once the indexer has finished moving, it sends a "I'm done indexing" signal back to the mill, which then proceeds on with the program.
All of this, save for the cheap Chinese "CNC router" axes/indexers you can find on eBay, are all going to be industrial accessories- meant to live in coolant, turn to sub-seconds-of-angle accuracy, and hold solidly enough for high-feed production milling. There is, near as I can tell, literally nothing between a $300 Ebay Special, or a $5,000 industrial unit.
Doc.
Yeah, I don't want anyone operating my machines if they all require knowledge of the inner workings. Industrial machines have enough polish on them that it shouldn't be an issue.
As to servo position error, for the DIY systems I put together, I used Galil Motion cards, that sit in a PC slot, these are about the closest you can get to a Industrial designed system.
As to PID tuning, you can achieve around 20 pulse error. The Minimum resolution encoders used are 1200 pulse/rev which translates to 1200x4 = 4800 pulses/rev when using the quadrature count.
This error is only meaningful when you then compare this to something Fanuc calls your 'Least Input Increment' or what you desire to be the smallest positioning value, e.g. 2 μm for example.
Comment