Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Rotary Balancing

0 views
Skip to first unread message

RL

unread,
Oct 18, 2006, 11:10:08 PM10/18/06
to
Some time back I asked about a Rotary Balancing Toolset and got a few
replies but was not able to buy any software.  Does anyone know
where to get the 2 plane algorithms that could be used in
Labview?  I am using a 4452 (4 simultaneous channels).  I
would prefer software i.e. VI  but that does not appear to be
likely for less than several thousand dollars.

Raymond

RL

unread,
Oct 20, 2006, 10:10:09 PM10/20/06
to
I want to 2 plane balance a rotor.  This requires the sampling of
two velocity sensors (one at each end of the rotor) and a rotary
position sensor.  The position sensor can be as simple as
recognizing the same point each time the rotor rotates, that point
becomes 0 degrees while the distance to the next 0 is equally divided,
on the screen (polar graph), into 360 equal parts. 

The challenge is calculating where the imbalance is located (between
0-360 degrees) and where the correcting weights have to be applied to
correct the imbalance and at which end of the rotor.   I am
trying to find out if someone has those algorithms and if they will
share them.

I planned to use a 4452 board to minimize the signal skew that could introduce itself especially when turning rapidly.

Raymond

Kevin Price

unread,
Oct 24, 2006, 4:10:08 PM10/24/06
to
Is this an industrial application or an academic project?  It sounds a little underspecified, though I can't claim any special knowledge in the field.
In generic terms, it would seem that a rotary imbalance implies a motion perturbation.  I would have expected this kind of app to use a controlled constant velocity while measuring a difference in bearing reaction forces due to the imbalance.  Since you want to measure a velocity variation, I assume you plan to deliver a constant torque to your rotor and allow the velocity to fluctuate as an indication of imbalance?  Is your shaft horizontal such that gravity contributes a fluctuating torque due to the mass imbalance?
With this in mind, I'd think you'd also benefit from a fairly high resolution encoder rather than just an index mark.  An index mark alone might be more useful at purely constant velocity, but less optimal for your case.
Wouldn't the "algorithm" just be Newton's Laws?
-Kevin P.
 
0 new messages