cmorley wrote:hmm no need to beat us up for our advice.
The advice was taken in the nature it was given. '
Better in every way' is a remarkably bold assertion.
And it is possible to have the PID control shutdown the motor if the encoder breaks
Peter has talked of this before. I believe it does it by counting how long the PID is saturated at maximum output
and if too long ( the servo is not keeping track ) it sets the output to zero.
This is my next area of inquiry. How can I find out more about Servo-Loop fault conditions in EMC2?
Who is Peter?
You give very little detail of your situation to recommend much more.
Hope that helps
The information on PID control shutdown is new and helpful to me. I hope someone can follow up with more information about this.
What additional information can I provide. I have ABB/IsoFlux 544 series Servomotors with integrated 0.02V/rpm tachometers. My goal is to drive these motors with 7i29 H-Bridges using EMC2 for control. My machine is also equiped with Heidenhain glass scales and EXE-602E resolvers, that I had thought to use in a secondary feedback loop.
PS if rereading your post - I think you are stuck on trying to get the analog tach signal into linuxcnc via the 7i29.
Not quite. I am stuck on using the existing analog tach signal with EMC2. Period.
What everyone is saying is you don't want the analog signal!
Agreed. But its what I have now to start with.
That both tachometer and encoder feedback are positive logic an therefore subject to runaway in a wire fault condition is troublesome to me. This is also a concern of mine in using the Heidenhain scales in a feedback loop, because they are not robust. I need to learn how EMC2 bounds feedback following errors.
Anyway does it really matter to EMC2 if the primary servo feedback is encoder derived (Radians) or tacho derived (dRadians/dT)?
Thanks for letting me think out loud.
_jC
.