If you need assistance, please send an email to forum at 4hv dot org. To ensure your email is not marked as spam, please include the phrase "4hv help" in the subject line. You can also find assistance via IRC, at irc.shadowworld.net, room #hvcomm.
Support 4hv.org!
Donate:
4hv.org is hosted on a dedicated server. Unfortunately, this server costs and we rely on the help of site members to keep 4hv.org running. Please consider donating. We will place your name on the thanks list and you'll be helping to keep 4hv.org alive and free for everyone. Members whose names appear in red bold have donated recently. Green bold denotes those who have recently donated to keep the server carbon neutral.
Special Thanks To:
Aaron Holmes
Aaron Wheeler
Adam Horden
Alan Scrimgeour
Andre
Andrew Haynes
Anonymous000
asabase
Austin Weil
barney
Barry
Bert Hickman
Bill Kukowski
Blitzorn
Brandon Paradelas
Bruce Bowling
BubeeMike
Byong Park
Cesiumsponge
Chris F.
Chris Hooper
Corey Worthington
Derek Woodroffe
Dalus
Dan Strother
Daniel Davis
Daniel Uhrenholt
datasheetarchive
Dave Billington
Dave Marshall
David F.
Dennis Rogers
drelectrix
Dr. John Gudenas
Dr. Spark
E.TexasTesla
eastvoltresearch
Eirik Taylor
Erik Dyakov
Erlend^SE
Finn Hammer
Firebug24k
GalliumMan
Gary Peterson
George Slade
GhostNull
Gordon Mcknight
Graham Armitage
Grant
GreySoul
Henry H
IamSmooth
In memory of Leo Powning
Jacob Cash
James Howells
James Pawson
Jeff Greenfield
Jeff Thomas
Jesse Frost
Jim Mitchell
jlr134
Joe Mastroianni
John Forcina
John Oberg
John Willcutt
Jon Newcomb
klugesmith
Leslie Wright
Lutz Hoffman
Mads Barnkob
Martin King
Mats Karlsson
Matt Gibson
Matthew Guidry
mbd
Michael D'Angelo
Mikkel
mileswaldron
mister_rf
Neil Foster
Nick de Smith
Nick Soroka
nicklenorp
Nik
Norman Stanley
Patrick Coleman
Paul Brodie
Paul Jordan
Paul Montgomery
Ped
Peter Krogen
Peter Terren
PhilGood
Richard Feldman
Robert Bush
Royce Bailey
Scott Fusare
Scott Newman
smiffy
Stella
Steven Busic
Steve Conner
Steve Jones
Steve Ward
Sulaiman
Thomas Coyle
Thomas A. Wallace
Thomas W
Timo
Torch
Ulf Jonsson
vasil
Vaxian
vladi mazzilli
wastehl
Weston
William Kim
William N.
William Stehl
Wesley Venis
The aforementioned have contributed financially to the continuing triumph of 4hv.org. They are deserving of my most heartfelt thanks.
Registered Member #4266
Joined: Fri Dec 16 2011, 03:15AM
Location:
Posts: 874
Just been working on a design for a project, thought it might of use to you, the larger numbers are the R axis, with the numbers after the commer the Y axis, cos(Y)/R should equal the X axis, the blue line is the bottom of the blade, and the yellow the top.
Registered Member #4266
Joined: Fri Dec 16 2011, 03:15AM
Location:
Posts: 874
Don't know what you mean by drag bucket? The right side is the front of the blade, the left the back, the top part is 20degrees of mid, the bottom blue line is 5 degrees of mid, with rought values that want mean anything apart from a ratio, 400(say Neutons) to 297 for drag the top side.
Registered Member #3414
Joined: Sun Nov 14 2010, 05:05PM
Location: UK
Posts: 4245
Patrick wrote ...
ok we should start with getting and keeping the drag bucket in the first quadrant and the tip below M0.7 ?
Well, this is the way I see it. Several examples I've seen seem to have a drag bucket from Mach 0.5 to Mach 0.7. It seems standard practice and seems easily feasible to get the drag bucket between these values.
Now these figures are for a 'wing section'. In our case this is 'tip speed', or there abouts.
We need to stay within the drag bucket for efficiency, so the 'operating region' has to be from the bottom of the drag bucket to the top, which implies (I assume) that hover equals Mach 0.5 tip speed and max thrust equals Mach 0.7, or there abouts.
With these parameters fixed (approximately), I suggest we design for hover at Mach 0.5, then 'simulate' at 0.7 to test that no part of the flow goes super sonic, and that everything else is ok, but we primarily design for hover at Mach 0.5.
We then, for each blade section, work out the Mach speed at hover, and use a section with suitable Cl and Cd, then simulate for max speed at that section.
We know disc loading (~5kg/m^2) and disc area (0.5m^2 per rotor). We can work out thrust required and hence Cl. Cd just needs to be kept to a minimum.
We may even still be able to use VABS to work out the 'forces on a beam' thing
EDIT: I'm using Mach numbers for velocity as that is apparently what the Pro's do (and that is what XFOIL uses)
EDIT: I'm assuming it will spend most of it's time at, or around, hover, so we design for max efficiency at around that point, or slightly above, to allow for manouvering, stability, etc.
EDIT: If we use the 'forces on a beam' thing to work out how much CF we need to withstand the thrust, we have our CSA. We then design for the Cl we need using that CSA, while ensuring that Cd remains at a minimum. We then end up with long, thin, lightly loaded, low drag blades.
Registered Member #3414
Joined: Sun Nov 14 2010, 05:05PM
Location: UK
Posts: 4245
Patrick wrote ...
ok so lets start getting some pulled together dimensions so i can start a mold. then we'll compare to existing props on my dynomometer.
I just edited the above post while you posted this.
I added:
Ash Small wrote ...
. EDIT: If we use the 'forces on a beam' thing to work out how much CF we need to withstand the thrust, we have our CSA. We then design for the Cl we need using that CSA, while ensuring that Cd remains at a minimum. We then end up with long, thin, lightly loaded, low drag blades.
I think, knowing the max thrust required (or thereabouts, we may need to 'tweak' later), we can work out how much CF we need to use, so, therefore, have our CSA.
Registered Member #3414
Joined: Sun Nov 14 2010, 05:05PM
Location: UK
Posts: 4245
Andy wrote ...
Just been working on a design for a project, thought it might of use to you, the larger numbers are the R axis, with the numbers after the commer the Y axis, cos(Y)/R should equal the X axis, the blue line is the bottom of the blade, and the yellow the top.
There are no units on your graph, Andy. This makes it difficult to even begin to interpret
This site is powered by e107, which is released under the GNU GPL License. All work on this site, except where otherwise noted, is licensed under a Creative Commons Attribution-ShareAlike 2.5 License. By submitting any information to this site, you agree that anything submitted will be so licensed. Please read our Disclaimer and Policies page for information on your rights and responsibilities regarding this site.