Modifying a thrust stand for small motors

When designing flying robots like drones it is important to be able to benchmark and test the propulsion system which in this case is a speed controller, motor and propeller. As we at Bitcraze are mainly working with tiny drones we need a thrust stand designed for small motors and propellers. We have actually already designed our own system identification deck, which can measure overall efficiency, thrust, etc., but is lacking the ability to measure torque. Torque is needed to be able to measure propeller efficiency which is now something we would like to measure. Before we developed the system-id deck we searched for of the shelf solutions that could satisfy our needs and could not find any. This still seems true, please let us know if that isn’t the case.

Expanding the system-id deck to measure torque doesn’t work and building something from scratch was a too big of a project for us. Next natural option would then be to modify an existing thrust stand and our choice fell for the tyro robotics 158X series.

Looking at specifications, images and code we could figure out that replacing the load cells for more sensitive ones should be possible. The stock setup of 5kgf thrust and 2Nm of torque is just too much as we are looking for around 100 grams of thrust and around 10 mNm of torque. So we decided to give the replacement of load cells a shot! Assembly was quite smooth but we managed to break one of the surface mount load cell connectors off, luckily this was easily fixable with a soldering iron. With the stock setup we did some measurements with a 0802 11000KV brushless motor and a 55mm propeller in a pushing setup. It works but the measurements are noisy and repeatability is not great. Next thing would be to replace the load cells. The 158X uses TAL221 sized load cells which are available down to 1kg. We got those and with a calibration-allways-pass code we got from Tyto robotics we could make the calibration pass (note that modifying the thrust stand breaks the warranty). Now the thrust stability was much better but still the torque was a bit to noisy. We decided to go for even smaller thrust cells, the TAL220, and build 3D printable adapters to make them fit.

Now the torque noise level looked much better and so did the repeatability. By empirically measuring the thrust and torque using calibrated weights and by checking the measurements in RCBenchmark we got these values:

Thrust, calibrated weight [g]Measured [g]Noise [g]
2002001
1001001
50500.5
20200.5
10100.5
000.5
Trust (calibrated using 200g weight)
Torque, calibrated weight [g]Measured [mNm]Noise [mNm]
2002572
1001281
50640.3
2025.70.3
1012.70.3
000.2
Torque (calibrated using 200g weight)
Simple repeatability test

The thrust stand modification is still very fresh and we have to figure out some things but it all looks promising. For example we get 13% less overall efficiency when measuring it using our system-id thrust stand. Our guess is that it is due to that the Crazyflie arms in the system-id case blocks the airflow.

If you would like to do this modification yourself there are some simple instructions and STL files over at out mechanical github repository. Have fun!

2 comments on “Modifying a thrust stand for small motors

  • Hi, I read your post impressively.
    It’s a very valuable resource to get the information I need

    Therefore, I would like to follow the test you conducted, so can I know some information?

    My question goes like this.
    1) There are various series depending on the mass in the “tal 220 load cell”. (e.g. 1kg, 3kg, 5kg …etc)
    Which series did you use among them?

    2) In the RC benchmark picture you posted, I can see additional parts in the coupling unlike the existing product.
    The information that I can see is
    – Motor Coupled Part Jig
    – Joints between RC Benchmarks
    If you have any information or 3D file about that additional part, could you share it?

    3) Can I get information about the motor purchase place/spec/prop used for the test if possible?

    4) Did you modify the code from the existing RCBenchmark 1585 and use it? (such as adding a calibration code)

    If you modified the code, can I know about the modification?

    I’ll be waiting for your answer
    Thank you

    Joonyoung

    • Have you checked out the link to the github repo in the bog post text? This should answer 1,2,4. For 3 we can not supply this, sorry. Good luck!

Leave a Reply

Your email address will not be published. Required fields are marked *