Unterschiede zwischen den Revisionen 2 und 81 (über 79 Versionen hinweg)
Revision 2 vom 27.08.2009 18:31
Größe: 369
Autor: fredericg
Kommentar:
Revision 81 vom 15.10.2009 14:09
Größe: 11807
Autor: fredericg
Kommentar: a few more links
Gelöschter Text ist auf diese Art markiert. Hinzugefügter Text ist auf diese Art markiert.
Zeile 1: Zeile 1:
VibrationTest Tool
[[TableOfContents]]
[[TableOfContents(2)]]
Zeile 5: Zeile 4:
The tool measures the vibration generated by the motors using the MK build-in sensors. This allows to balance motor/prop assemblies and to experiment with different motor-mounts. The tool evaluates the vibration generated by the motors which allows balancing motor/prop assemblies and experimenting with different motor-mounts. The test uses the MK build-in sensors, so no extra hardware is required.
Zeile 7: Zeile 6:
= Why is it important to reduce vibrations? =
The FlightControl sensors pickup the vibrations and this deteriorates performance; the new FC ME comes with vibration dampers in order to reduce the vibrations transferred to the FC.

Reducing vibration is very important, especially for Aerial Photography or Video. Vibrations result in blurry footage. Some claim that high frequency vibrations can be picked up by the Optical Image Stabilization lens assembly which is incorporated in almost all recent cameras. The OIS is not designed for these vibrations and makes thing worse, even when you switch the OIS feature off in the camera menu.

Propellers can be balanced the traditional way. However it was discovered that also the motors need balancing. One way to accomplish this is let a small unbalance in the prop compensate the motor unbalance, so the orientation of the prop is important (see [http://www.rcgroups.com/forums/showpost.php?p=12832508&postcount=228 this post]). Looking at the vibraions of a running motor allows balancing the prop/motor assembly as a whole.

= How does it work? =
The standard FlightControl program samples all sensors periodically and provides a command to read the latest sample from all sensors. The MKTool uses this command to generate graphs of the analog values. In a first approach the VibrationTest used this standard command to monitor vibrations. The problem is that this mechanism only allows to sample the values 30 times a second. The actual shape of the signals cannot be determined and one can only hope to catch the peak values. In order to get reliable results the values need to be monitored for a long time (a minute for example).

This new approach is based on dedicated FlightControl software providing a new command. The new command instructs the FC to sample one of the sensors as fast as possible and store the info in its internal memory. Afterwards the recorded data can be read to analysis. This allows to grab a reliable signal in a very short time. This approach can capture about 11000 samples a second, 500 times more than the MKTool can.

This is an example of the signal measured by the Roll-ACC sensor:
[[BR]]
[[Anchor(SampleSignalJpg)]]
attachment:test.jpg

[[BR]][[BR]][[BR]]
= Current Project status =
/!\ ~+'''The version available now (version 0.9) is an beta version; it was only tested by a limited amount of people.
[[BR]]More testers/evaluators are very welcome!'''+~
[[BR]][[BR]]
At the time of writing, the tool was tested in combination with:
 * PC/Windows XP and Vista
 * FC 1.2 and FC 1.3
Theoretically the tool should also run on MAC and Linux.
[[BR]][[BR]]
Features in the pipeline
 * Integrated backup and restore of flight settings
 * Integrated installing and restore of FC code
[[BR]][[BR]]
{i} [http://forum.mikrokopter.de/topic-11446.html MK Forum thread for discussions]
[[BR]]
{i} [[MailTo(frederic AT rc-flight DOT be)]]


[[BR]][[BR]][[BR]]
[[Anchor(Install)]]
Zeile 8: Zeile 45:
The tool is written in programming language called [http://en.wikipedia.org/wiki/Python_(programming_language) Python].
Zeile 9: Zeile 47:
= How do I use it? = The most logic way to run the tool is to install support for Python on your PC (if you do not have it already) and the Python libraries the tool depends on.
Python is also available for Linux and MAC; the tool should also run on these platforms, but I have never tried it.
Zeile 11: Zeile 50:
/!\ ToDo: Almost everything :) If you do not feel like installing Python, a version that is compiled to a windows executable is provided.

So, you have two options.

[[Anchor(InstallPython)]]
== Option 1: Install Python and required libraries ==
For a Windows machine I propose you install:

 * [http://www.activestate.com/activepython/ ActivePython for Windows] Press the big "ActivePython Download Now" button.
 * [http://sourceforge.net/projects/pyserial/files/ PySerial (support for serial port access)] Select "pyserial-2.5-rc1.win32.exe" on that page.
 * [http://www.wxpython.org/download.php wxPython wxWidgets for Python] Select the the win32-unicode version for Python 2.6
 * [http://sourceforge.net/projects/numpy/ NumPy, the fundamental package needed for scientific computing with Python]
Once you have Python support on your PC, unzip [http://www.rc-flight.be/VibrationTest/VibrationTest_0_9.zip VibrationTest_0_9.zip] to a directory on your PC.

== Option 2: Get the compiled version ==
unzip [http://www.rc-flight.be/VibrationTest/VibrationTestExe_0_9.zip VibrationTestExe_0_9.zip] to a directory on your PC


[[BR]][[BR]][[BR]]
= How do I use the tool? =
== Prepare your MK ==

=== Secure your MK ===
I use luggage straps to secure my MK to the table while it is still able to vibrate:

attachment:mk1InTest.jpg

=== Installing the FlightControl software ===
The VibrationTest tool only works in combination with a special version of the FlightControl software. It must be flashed in the FC board before using the test and '''you need to reinstall your regular software version afterwards'''. This just takes a few minutes. Switching the software is done the usual way, using the MKTool.

You will find the required hex file in the same directory with the VibrationTest tool.

/!\ '''The FC code for the VibrationTest is based 0.74d but is not fit for flying! Before flying, you will need to reinstall your initial FC code. When the version you use for flying is 0.74d, your settings should be preserved. In combination with other versions, it might not be the case. It is a good idea to backup yout settings to PC (via the MKTool) before installing the VibrationTest FC code. '''

After insatlling the FC code for the VibrationTest, the LC-Display in the MKTool will look like this:

attachment:LCDisplay.jpg

== Starting the VibrationTest tool ==
In the directory where you unzipped the tool, dubbleclick VibrationTestGui.py (in case of the Python version) or VibrationTestGui.exe

== Using the VibrationTest tool ==
[[BR]]
[[Vimeo(6948282)]]
[[BR]]

== Checking the reliability/accuracy of the results ==
Before you start, it is good to check the reliability of the test and setup.

You should alway start with a sweep and look at different sensors. If the vibrations is rather constant over motor-speed, the combination might be well balanced or you might not be measuring what you are hoping to measure. In this case, sticking some tape to the prop should should unbalance it and you should see a difference.

You can have a look at the recorded signals, the filtered signals and perhaps the spectrum. If this seems ok, you can repeat the sweep multiple times, using one of the sensors. Each time you should get similar results. Results will never be 100% the same.

Another test you should do, is let the tool measure multiple times at the same speed; for example "10*100,10*200". The measurement at the same speed should report the about the same amount of vibrations.

The figure below shows the result of such test with a "Roxxy 2824-34 / EPP1045 / 3s / Standard ESC" combination. All but the green line are from the Nick sensor. The black line are vibrations measured at speeds 130 and 185. The other lines are sweeps. This does not look too bad.

attachment:acuracy1.jpg
Zeile 14: Zeile 110:
When the results are disappointing, one can experiment with the way the MK is attached to the desk. It is also possible that the filter parameters might not be optimal for your setup. In the figure below I have almost disabled the filter and switched to "pp" measurement:

attachment:acuracy2.jpg

[[BR]]
This is another example of such a test (Turnigy 2836-750 / APC 12x3.8 / 4s / TowerPro ESC):

attachment:acuracy3.jpg

[[BR]][[BR]]
= Examples =

== Balancing example: Roxxy 2824-34 / EPP1045 / 3s / Standard ESC ==
[[Vimeo(7011506)]]

[[BR]]
== Effect of prop position, Roxxy 2824-34 / EPP1045 3s / Standard ESC ==
The importance of the position of the propeller relative to the motor was first reported by RCGroups member "Old Man Mike", see [http://www.rcgroups.com/forums/showpost.php?p=12832508&postcount=228 this post]. My tool also shows this effect. However, I observed that sometimes rotating the prop did not produce significant variations...

I discovered that when I first balance the prop as good as I can using the VibrationTest, rotating the prop produced very little difference.

I come to the conclusion that I need to deliberately unbalance the prop a bit in order to find the "sweet spot". I also observed that when I unbalance the prop by sticking some tape on one side of the prop the vibrations peak while they go trough a minimum when I stick some tape to the other side.
I think this supports the theory that the slightly unbalanced prop can compensate for unbalances in the motor.
[[BR]][[BR]]
attachment:StudyRotation.jpg
[[BR]][[BR]]
On the X-asis the rotation of the prop in steps of 60 degrees. The red line is with a prop that I balanced before (needs some tape opposite to the prop size-markers). The green line shows vibrations when I attach an additional strip of tape (so unbalancing it). The blue line shows what happens when I attach tape to the other side (where the markers are).

== Balancing example: Turnigy 2836-750 / APC 12x3.8 / 4s / TowerPro ESC ==

/!\ For this setup I have found that setting the LP Filter cutoff frequency to 200 Hz
[[BR]]
attachment:Mk2BalancingExample1.jpg
[[BR]]
The red line is the initial balancing. The prop seemed best balanced with no additional tape.[[BR]]
The green line are the measurement while rotating the prop (steps of 45 degrees)[[BR]]
The blue line is the re-balancing, due to the repositioning of the prop the results are better. The first 3 measurements showed that no tape produced the best results. In the last 3 measurements of the blue line, I experimented with smaller strips and this produced the best result.

[[BR]][[BR]]
= Links =

=== VibrationTest related ===
 * [http://svn.mikrokopter.de/mikrowebsvn/listing.php?repname=Projects&path=/VibrationTest/#_VibrationTest_ VibrationTest Project in Subversion]
 * [http://forum.mikrokopter.de/topic-11446.html MK Forum thread for discussions]
 * Mail FredericG: [[MailTo(frederic AT rc-flight DOT be)]]

=== Related Threads ===
 * [http://forum.mikrokopter.de/topic-7794-1.html Thread: Vibrationsdämpfung der Antriebsmotoren]
 * [http://forum.mikrokopter.de/topic-post106888.html Thread: Tilt servo play => Vibrations]
 * [http://www.mk-fr.info/forum/index.php/topic,812.msg12038.html Thread: Equilibrage des Hélices RC (French)]
 * [http://www.vimeo.com/4257366 Video: Is the Optical Image Stabilization of the FX35 causing problems?]
 * [http://www.rcgroups.com/forums/showthread.php?t=807347 Thread: Multikopter (mikrokopter, UAVP, x-ufo-3rd, etc) AP pictures]

=== Related Projects ===
 * [http://www.rcgroups.com/forums/showthread.php?t=1006721 Old Man Mike "Test Fixture Evaluates Motors/Props/ESCs for Quadcopter Performance"]

=== Used Libraries and Tools ===
 * [http://www.python.org/ Python]
 * [http://www.wxpython.org/ wxPython]
 * [http://wxglade.sourceforge.net/ wxGlade]
 * [http://numpy.scipy.org/ NumPy]
 * [http://www.py2exe.org/ py2exe]

=== Technical references ===
 * [http://en.wikipedia.org/wiki/Sampling_(signal_processing) Sampling]
 * [http://en.wikipedia.org/wiki/Fourier_analysis Fourier Analysis]

[[BR]]

## [[AttachList]]
Zeile 15: Zeile 182:
 . KategorieTools KategorieProjekte KategorieEnglish KategorieAnleitung

TableOfContents(2)

What is the VibrationTest Tool?

The tool evaluates the vibration generated by the motors which allows balancing motor/prop assemblies and experimenting with different motor-mounts. The test uses the MK build-in sensors, so no extra hardware is required.

Why is it important to reduce vibrations?

The FlightControl sensors pickup the vibrations and this deteriorates performance; the new FC ME comes with vibration dampers in order to reduce the vibrations transferred to the FC.

Reducing vibration is very important, especially for Aerial Photography or Video. Vibrations result in blurry footage. Some claim that high frequency vibrations can be picked up by the Optical Image Stabilization lens assembly which is incorporated in almost all recent cameras. The OIS is not designed for these vibrations and makes thing worse, even when you switch the OIS feature off in the camera menu.

Propellers can be balanced the traditional way. However it was discovered that also the motors need balancing. One way to accomplish this is let a small unbalance in the prop compensate the motor unbalance, so the orientation of the prop is important (see [http://www.rcgroups.com/forums/showpost.php?p=12832508&postcount=228 this post]). Looking at the vibraions of a running motor allows balancing the prop/motor assembly as a whole.

How does it work?

The standard FlightControl program samples all sensors periodically and provides a command to read the latest sample from all sensors. The MKTool uses this command to generate graphs of the analog values. In a first approach the VibrationTest used this standard command to monitor vibrations. The problem is that this mechanism only allows to sample the values 30 times a second. The actual shape of the signals cannot be determined and one can only hope to catch the peak values. In order to get reliable results the values need to be monitored for a long time (a minute for example).

This new approach is based on dedicated FlightControl software providing a new command. The new command instructs the FC to sample one of the sensors as fast as possible and store the info in its internal memory. Afterwards the recorded data can be read to analysis. This allows to grab a reliable signal in a very short time. This approach can capture about 11000 samples a second, 500 times more than the MKTool can.

This is an example of the signal measured by the Roll-ACC sensor: BR Anchor(SampleSignalJpg) attachment:test.jpg

BRBRBR

Current Project status

/!\ The version available now (version 0.9) is an beta version; it was only tested by a limited amount of people. BRMore testers/evaluators are very welcome! BRBR At the time of writing, the tool was tested in combination with:

  • PC/Windows XP and Vista
  • FC 1.2 and FC 1.3

Theoretically the tool should also run on MAC and Linux. BRBR Features in the pipeline

  • Integrated backup and restore of flight settings
  • Integrated installing and restore of FC code

BRBR {i} [http://forum.mikrokopter.de/topic-11446.html MK Forum thread for discussions] BR {i} MailTo(frederic AT rc-flight DOT be)

BRBRBR Anchor(Install)

How do I install the tool?

The tool is written in programming language called [http://en.wikipedia.org/wiki/Python_(programming_language) Python].

The most logic way to run the tool is to install support for Python on your PC (if you do not have it already) and the Python libraries the tool depends on. Python is also available for Linux and MAC; the tool should also run on these platforms, but I have never tried it.

If you do not feel like installing Python, a version that is compiled to a windows executable is provided.

So, you have two options.

Anchor(InstallPython)

Option 1: Install Python and required libraries

For a Windows machine I propose you install:

Once you have Python support on your PC, unzip [http://www.rc-flight.be/VibrationTest/VibrationTest_0_9.zip VibrationTest_0_9.zip] to a directory on your PC.

Option 2: Get the compiled version

unzip [http://www.rc-flight.be/VibrationTest/VibrationTestExe_0_9.zip VibrationTestExe_0_9.zip] to a directory on your PC

BRBRBR

How do I use the tool?

Prepare your MK

Secure your MK

I use luggage straps to secure my MK to the table while it is still able to vibrate:

attachment:mk1InTest.jpg

Installing the FlightControl software

The VibrationTest tool only works in combination with a special version of the FlightControl software. It must be flashed in the FC board before using the test and you need to reinstall your regular software version afterwards. This just takes a few minutes. Switching the software is done the usual way, using the MKTool.

You will find the required hex file in the same directory with the VibrationTest tool.

/!\ The FC code for the VibrationTest is based 0.74d but is not fit for flying! Before flying, you will need to reinstall your initial FC code. When the version you use for flying is 0.74d, your settings should be preserved. In combination with other versions, it might not be the case. It is a good idea to backup yout settings to PC (via the MKTool) before installing the VibrationTest FC code.

After insatlling the FC code for the VibrationTest, the LC-Display in the MKTool will look like this:

attachment:LCDisplay.jpg

Starting the VibrationTest tool

In the directory where you unzipped the tool, dubbleclick VibrationTestGui.py (in case of the Python version) or VibrationTestGui.exe

Using the VibrationTest tool

BR Vimeo(6948282) BR

Checking the reliability/accuracy of the results

Before you start, it is good to check the reliability of the test and setup.

You should alway start with a sweep and look at different sensors. If the vibrations is rather constant over motor-speed, the combination might be well balanced or you might not be measuring what you are hoping to measure. In this case, sticking some tape to the prop should should unbalance it and you should see a difference.

You can have a look at the recorded signals, the filtered signals and perhaps the spectrum. If this seems ok, you can repeat the sweep multiple times, using one of the sensors. Each time you should get similar results. Results will never be 100% the same.

Another test you should do, is let the tool measure multiple times at the same speed; for example "10*100,10*200". The measurement at the same speed should report the about the same amount of vibrations.

The figure below shows the result of such test with a "Roxxy 2824-34 / EPP1045 / 3s / Standard ESC" combination. All but the green line are from the Nick sensor. The black line are vibrations measured at speeds 130 and 185. The other lines are sweeps. This does not look too bad.

attachment:acuracy1.jpg

BR When the results are disappointing, one can experiment with the way the MK is attached to the desk. It is also possible that the filter parameters might not be optimal for your setup. In the figure below I have almost disabled the filter and switched to "pp" measurement:

attachment:acuracy2.jpg

BR This is another example of such a test (Turnigy 2836-750 / APC 12x3.8 / 4s / TowerPro ESC):

attachment:acuracy3.jpg

BRBR

Examples

Balancing example: Roxxy 2824-34 / EPP1045 / 3s / Standard ESC

Vimeo(7011506)

BR

Effect of prop position, Roxxy 2824-34 / EPP1045 3s / Standard ESC

The importance of the position of the propeller relative to the motor was first reported by RCGroups member "Old Man Mike", see [http://www.rcgroups.com/forums/showpost.php?p=12832508&postcount=228 this post]. My tool also shows this effect. However, I observed that sometimes rotating the prop did not produce significant variations...

I discovered that when I first balance the prop as good as I can using the VibrationTest, rotating the prop produced very little difference.

I come to the conclusion that I need to deliberately unbalance the prop a bit in order to find the "sweet spot". I also observed that when I unbalance the prop by sticking some tape on one side of the prop the vibrations peak while they go trough a minimum when I stick some tape to the other side. I think this supports the theory that the slightly unbalanced prop can compensate for unbalances in the motor. BRBR attachment:StudyRotation.jpg BRBR On the X-asis the rotation of the prop in steps of 60 degrees. The red line is with a prop that I balanced before (needs some tape opposite to the prop size-markers). The green line shows vibrations when I attach an additional strip of tape (so unbalancing it). The blue line shows what happens when I attach tape to the other side (where the markers are).

Balancing example: Turnigy 2836-750 / APC 12x3.8 / 4s / TowerPro ESC

/!\ For this setup I have found that setting the LP Filter cutoff frequency to 200 Hz BR attachment:Mk2BalancingExample1.jpg BR The red line is the initial balancing. The prop seemed best balanced with no additional tape.BR The green line are the measurement while rotating the prop (steps of 45 degrees)BR The blue line is the re-balancing, due to the repositioning of the prop the results are better. The first 3 measurements showed that no tape produced the best results. In the last 3 measurements of the blue line, I experimented with smaller strips and this produced the best result.

BRBR

Links

Used Libraries and Tools

Technical references

BR