V-22 Osprey Project - Selecting the right battery

-
Recently, I've been able to successfully hover the V-22 around the yard and start to tune some of the control parameters.  However, each of these flights is not very long and it has me concerned about battery selection and flight times.  The stock 450-sized helicopters recommend a 3S 2200mAh Lipo battery for an estimated flight time of 6 mins.  I started testing with two of these in parallel to make a 3S 4400mAh source for the Osprey.

There's no beating around the bush, this machine is heavy.  Weighing in at 2lbs, 9.75oz (1186g) without batteries, it's a beast.  I've tried to be conscious of weight throughout the build, but with so much structure required for rigidity, it's hard to skimp out on materials knowing that any failure would be catastrophic.

So what's the right mix of battery size to maximize flight time?  I had on-hand pairs of 3S 2200mAh, 4S 2200 mAh, and 4S 3000mAh.  To round out the selection, I ordered a pair of 3S 3300mAh batteries for testing.  I set a couple of timers in my Taranis at 2 minutes and 4 minutes, and with a full battery to start, I took off and hovered around gently until the 2 minutes elapsed.  I landed as close to the mark as I could and then recorded the battery level.  I took off again and hovered for another 2 minutes and landed again as close to the 4-minute mark as possible.  I then took the battery reading and noted it down.  Using Google Sheets, I graphed these 3 data points per battery and enabled the trendline to estimate when the battery voltage would drop to a discharged state.

Somewhat surprising, the 3S 3300mAh battery lasted the longest.  I had expected more life out of the 4S packs, but they didn't necessarily perform as well.  I also compared the expected run-time to the weight of the battery pack to get a "flight time per gram" efficiency number as shown below.

Battery Estimated Flight (s) Weight (g) Flight / weight ratio
Turnigy 3S 2200mAh 25-35C 372 337 1.104
Turnigy Graphene 4S 2200mAh 65C 432 559 0.773
HRB 3S 3300mAh 60C 522 529 1.549
Zippy 4S 3000mAh 20C 489 660 1.451

As with any aircraft, the more weight you carry makes the airframe and motors work harder.  From my selection of batteries that new 3S 3300mAh looks to be the best bang for the buck balancing runtime and weight.

I also redesigned the wing retention mechanism forgoing the rubberbands in favor of a couple of nylon bolts.  I've also been redoing the foamboard fuselage.  I should have an update soon with new versions of those.





Comments

Post a Comment

Popular posts from this blog

V-22 Osprey Project - Design Changes for v3

-
Image
It's been a busy end of 2021, and as we start 2022 I'm getting closer to building version 3 of the Osprey wing.  The single biggest problem I've faced is the amount of backlash in the direct spur gear drive of the tilt mechanism.  It introduces some nasty instability that, left unchecked, would likely destroy the model in flight. I've investigated other tilt mechanisms, but the one I keep coming back to is the rack and pinion design that Tom Mast uses in his model at Rotormast.  His design uses a high-torque digital servo with a small pinion gear driving a rack attached to the rotor nacelle.  The servo has been modified with an external potentiometer that's driven by a gear on the translation tube to give positional feedback to the servo.  I like this design a lot because 1) It works, and his model is proof, and 2) it requires less torque from the servo and has less backlash. I ordered the pair of modified servos, potentiometer, and rack from Tom's site and star
Read more

V-22 Osprey Project - Flight Control

-
Image
Now that I have a conceptual idea of how to build a V-22 using leftover mCPX BL parts, how do I go about controlling such an aircraft? I own a Taranis X9D+, and it can control up to 32 channels using dual receivers, so that won’t be a problem. I’m sure that I can create a mixing profile in the transmitter to handle just about anything, but I’m also sure that just like any multi-rotor “drone," this thing will need some form of automatic flight stabilization. I own a few multirotor aircraft and I’m familiar with how they function. Some research into the popular flight control software (Betaflight, iNav, Cleanflight, LIbrepilot, etc.) all came up short. No one has written code for off-the-shelf flight controllers to manage a dual-swashplate aircraft. I would have to build my own. I have not delved into writing code for flight controllers, but I have built a number of Arduino projects, and some of them utilize RC inputs to control servos and motors. It occurred to me that I
Read more

Whereabouts Clock Update

-
Image
After a few months, Life360 has gone the way of Apple and locked down the API I used to get location data from the phones.  This is disappointing, but inevitable. I found on a forum for Home Assistant that the app OwnTracks might be a suitable alternative. It's a neat little app that will trigger the phone to send its location data via MQTT to a server that you specify. I had to rework the code a bit, but the new operation is as follows: OwnTracks on the phone will push location data per its configuration to the MQTT server (Docker container) The Mosquitto (MQTT Broker) container will receive the data and forward the data to its subscribers The MQTTWarn container is a subscriber and translates the received data and adds it to the MariaDB database The Apache web server hosts a Python CGI script that is checked each minute by the Arduino microcontroller.  If the data has changed, the hands are moved to the new location. The only exposed port to the Internet is TCP 1883 for MQTT
Read more