|
|
|
|
|||||
| Product Tip of the Month | |||||
|
|
|||||
| September
2000 |
|||||
|
Model 2020 ProBalancer Analyzer | ||||
| Efficient Use of Setups | |||||
|
We've been
hearing some general comments recently that the Model 2020 ProBalancer Analyzer still
takes three and sometimes four runs to balance a prop. That is not necessarily the norm.
With efficient use of setups, balancing can be completed much quicker. The Model 2020 ProBalancer Analyzer is a learning system. When you first enter a setup into its memory and before you use it to actually accomplish a balance, the Model 2020 is working on some large assumptions. The configuration data you enter into the setup is used to calculate a rough coefficient influence. This influence is then used to suggest the first weight addition to the prop assembly. This weight is effectively a "test" weight because its main purpose is to induce a change in the balance condition so the analyzer can measure the magnitude of the change and recalculate a new influence coefficient. The vibration may actually increase in some cases but that is of little consequence since the only important thing is that a change was induced and measured. It is always important to enter the solution you installed back into the analyzer as accurately as possible. This information is then used to recalculate, and the process is refined with each successive run. So, the first use of a particular setup may require three or four runs to acheive balance. In the final run, the influence has been refined to a point that the vibration level should be very low. Throughout the process the influence has been updated in the setup you are running. When the job is complete, the new influence is stored within the setup and ready to use when this setup is run again. Whenever possible, you should use the same setup to balance other assemblies of the same engine and prop combination. The accuracy of the first weight is much closer to actually completing the job and in fact will be the last required solution you apply. Every time you use the setup, it becomes more accurate and requires fewer runs. You should always create setups for applications you frequently do and reuse them as often as possible. The least efficient process is to create a new setup for every job you do, regardless of whether or not you've balanced the same assembly before with an existing setup. |
||||
|
|||||
|
Top | ||||
![]()
Copyright © 1999 TEC. All Rights Reserved.
Contact the webmaster if you have comments about this site.