Sign in, say "hi", ... and be welcomed.

Re: Predator Model

Postby Chris McKeon » Tue Oct 05, 2021 9:44 pm

Well that accident I had Eleven Years Six Months, 14 Days ago was for Me a real Game changer. I am actively trying to develop new Game Changers in My life. B8ut there is something that causes Me to take time to consider what risk I would be indulging in if I were to do anything that put my skull in motion with a possible sudden stop. si regarding riding My Bike I have not ridden yet. But I know that I could Ride one of My bikes. There are other things that I could possibly do also.For I could possibly ride. and jump a Thoroughbred. or a Warmblood Horse. For on My Bucket list I really do want to jump a Horse Seven Feet or more. For those who do not know much about jumping a Horse, check this out; A Horse that can Jump 7' or higher is what I like to call "RARE AIR". Maybe this simply My Pipe-Dream. But it's my Dream Speaking of My dreams; IO dream of flying My Predator 100 Miles in under Four Hours. I also dream of flying My Predator to Twenty Thousand Feet or More. And Yes I hope to blow through twenty thousand feet MSL legally.

But there is a Caveat.; I have learned that since I did indeed did |Pound My Predator Eleven Years ago> I have come to learn that a second Brain injury is cattroscopic. I know from Personal experience. THat a first Head injury is astroscopic.
Chris McKeon
User avatar
Contributor
Contributor
 
Posts: 1566
Joined: Wed Jul 31, 2013 7:46 pm

Re: Predator Model

Postby Chris McKeon » Fri Oct 08, 2021 6:39 pm

1: 234" 2: 117" 3: 142" 4: 24" 5: 206" 6: 63" 7: 70" 8"57" 9: 60" 10: 60" 11: 32"

15: 48"
Chris McKeon
User avatar
Contributor
Contributor
 
Posts: 1566
Joined: Wed Jul 31, 2013 7:46 pm

Re: Predator Model

Postby Bob Kuczewski » Sat Oct 09, 2021 1:10 am

Chris McKeon wrote:1: 234" 2: 117" 3: 142" 4: 24" 5: 206" 6: 63" 7: 70" 8"57" 9: 60" 10: 60" 11: 32"

15: 48"


Good progress Chris!!

But there are a few things "Abby Normal" about those measurements:




















#Name Value     Description
1Length of Leading Edge234"Length of the leading edge from nose to tip
2Length of Keel117"Length of the keel
3Keel Front y142"Distance from the origin to the front tip of the keel
4Keel Rear y24"Distance from the origin to the rear tip of the keel
5Wing Tip x206"Distance from the origin to the right wing tip
6Wing Tip z63"Vertical distance between the origin and right wing tip (this might be hard to measure, so just estimate it)
7Control Bar Height70"Vertical distance from the base tube to the keel (perpendicular distance from the keel to the base tube)
8Control Bar Width57"Width of the base tube from corner to corner
9Control Bar Location60"Distance along the keel from the nose to the apex of the control frame
10Control Bar Rake60"Horizontal distance along the keel from the apex of the control frame to the base tube (this may be hard to measure, so just estimate it)
11Cross Bar at Leading Edge32"Distance along the leading edge from nose to cross bar junction where the cross bar meets the leading edge
12Cross Bar at Keel        Distance along the keel from the nose to the cross bar where it crosses the keel
13Cross Bar z from Keel        Vertical distance between the keel and the cross bar (typically 0 to a few inches)
14Kingpost at Keel        Distance along the keel from the nose to the kingpost (you can also measure from the rear of the keel and subtract from the keel length)
15Kingpost Height48"Vertical distance (perpendicular to keel) from the keel to top of the kingpost
16Kingpost Rake        Horizontal distance (parallel to keel) between top and bottom of kingpost
17Trailing Edge        Distance along the keel from the nose to the trailing edge of the sail
18Rear Wire        Distance along the keel from the nose to the rear wire where it attaches to the keel

First, the Keel Front y plus the Keel Rear y should equal the Length of Keel:


Length of Keel=Keel Front y+Keel Rear y                                        
117"=142"+24"                                        

But    117    does not equal    142 + 24    so something is wrong there.

Also, number 11 should be the "Distance along the leading edge from nose to cross bar junction". It's hard to believe that's only 32 inches. So please recheck that measurement.

But you're making progress, and that's the most important thing!!    :thumbup:
Join a National Hang Gliding Organization: US Hawks at ushawks.org
View my rating at: US Hang Gliding Rating System
Every human at every point in history has an opportunity to choose courage over cowardice. Look around and you will find that opportunity in your own time.
Bob Kuczewski
User avatar
Contributor
Contributor
 
Posts: 8373
Joined: Fri Aug 13, 2010 2:40 pm
Location: San Diego, CA

Re: Predator Model

Postby Bob Kuczewski » Thu Dec 09, 2021 1:00 am

That last post was from October 9th, 2021. Unfortunately, Chris sustained an unrelated injury at that time, and we didn't finish the Predator Model.

Also, I think I may have made a mistake in my analysis of the measurements. Chris had posted values of 142 and 24 which didn't add up to 117. However, if 24 is subtracted from 142, then the answer is 118. That's pretty close to 117, so there may just be a sign interpretation difference in that measurement. We'll have to reconfirm those numbers.

Since that time, we've also gained a new member of the U.S. Hawks from the Rio Grande Soaring Association. Finis appears to have done a lot of work with Blender, and I am hoping that he can lend a hand with some of our computer modelling efforts. This will be most helpful for the training manual which has been on hold for quite some time.

Until then, let's see if we can get (or estimate) the final measurements to finish the Predator model.

I think this is the current JSON model:

{
'Version': 1.0,
'KeelFrontPoint': [0,94,0],
'KeelRearPoint': [0,-119,0],
'WingTipPoint': [291,-60,6],
'TrailingEdgePercentKeel': 52.5821596244,
'RearWirePercentKeel': 75,
'ControlBar': {
'Height': 65,
'Width': 107,
'ApexPercentKeel': 42,
'RakeDistance': 27,
},
'CrossBar': {
'PercentKeel': 35,
'PercentLeadingEdge': 59.0060240964,
'HeightAboveKeel': 7,
},
'KingPost': {
'PercentKeel': 42,
'Height': 50,
'RakeDistance': 3,
},
'Battens': {
'NumPerSide': 2,
'BattenList': [
{
'PercentLeadingEdge': 0,
'Segments': 20,
'LeadingEdge': [50,165],
'LeadingEdgeControl': [125,20],
'TrailingEdgeControl': [275,150],
'TrailingEdge': [685,160]
},
{
'PercentLeadingEdge': 100,
'Segments': 20,
'LeadingEdge': [225,305],
'LeadingEdgeControl': [240,295],
'TrailingEdgeControl': [283.5,297.1666717529297],
'TrailingEdge': [404.5,318.1666717529297]
}
]
}
}


If you copy and paste that into the "Glider Data (JSON format)" window of the modeling program (at https://ushawks.org/designer), and click "Update Model From Text" button, and then set the "Zoom" to 1.0, you should get this image:

Screenshot_2021-12-08c.png
Screenshot_2021-12-08c.png (60.12 KiB) Viewed 1953 times


That's pretty close, but it's not complete yet.

I've written two Python programs to help with this project. They convert between the measured format (the table that Chris has been filling out) to the JSON format shown above in this post.

Here's the Python program that converts the Raw Measurements to the JSON model:

Standard_Model = {
'Version': 1.0,
'KeelFrontPoint': [0,5,0],
'KeelRearPoint': [0,-5,0],
'WingTipPoint': [15,-3,0.2],
'TrailingEdgePercentKeel': 80,
'RearWirePercentKeel': 82,
'ControlBar': {
'Height': 3.5,
'Width': 3.2,
'ApexPercentKeel': 40,
'RakeDistance': 1.0,
},
'CrossBar': {
'PercentKeel': 33,
'PercentLeadingEdge': 60,
'HeightAboveKeel': 0.1,
},
'KingPost': {
'PercentKeel': 40,
'Height': 3,
'RakeDistance': 0.1,
},
'Battens': {
'NumPerSide': 2,
'BattenList': [
{
'PercentLeadingEdge': 0,
'Segments': 20,
'LeadingEdge': [50.0,165.0],
'LeadingEdgeControl': [125.0,20.0],
'TrailingEdgeControl': [275.0,150.0],
'TrailingEdge': [685.0,160.0]
},
{
'PercentLeadingEdge': 100,
'Segments': 20,
'LeadingEdge': [225.0,305.0],
'LeadingEdgeControl': [240.0,295.0],
'TrailingEdgeControl': [260.0,300.0],
'TrailingEdge': [350.0,315.0]
}
]
}
}

# These are pixel measurements taken from the standard glider
# The resulting glider is nearly identical to the standard glider
# So the conversion from Raw to Percent seems to work.

LenLE_Meas = [512,3] # 452x241 pixels = 512.2352974952039
LenKeel_Meas = [301,0]
KeelFrontY_Meas = [242,0]
KeelRearY_Meas = [60,0]
WingTipX_Meas = [452,0]
WingTipZ_Meas = [3,0]
CtlBarH_Meas = [107,0]
CtlBarW_Meas = [96,0]
CtlBarLoc_Meas = [122,0]
CtlBarRake_Meas = [31,0]
CrossBarLE_Meas = [305,7] #>>> math.sqrt((269*269)+(145*145)) = 305.5912302406599
CrossBarKeel_Meas = [102,0]
CrossBarZ_Meas = [3,0]
KingPostKeel_Meas = [121,0]
KingPostH_Meas = [91,0]
KingPostRake_Meas = [4,0]
TrailingEdge_Meas = [242,0]
RearWire_Meas = [246,0]

# These are pixel measurements taken from the standard glider multiplied by 0.038716814
# The values have been scaled to match the Predator's 35' 4" span (35.33')
# The model appears to be correct, which indicates that Convert_Raw_to_Percent.py is good.

LenLE_Meas = [19,9.88]
LenKeel_Meas = [11,7.85]
KeelFrontY_Meas = [9,4.43]
KeelRearY_Meas = [2,3.88]
WingTipX_Meas = [17,8] # Predator span of 35' 4" / 2 = 17' 8"
WingTipZ_Meas = [0,1.39]
CtlBarH_Meas = [4,1.71]
CtlBarW_Meas = [3,8.6]
CtlBarLoc_Meas = [4,8.68]
CtlBarRake_Meas = [1,2.4]
CrossBarLE_Meas = [11,9.7]
CrossBarKeel_Meas = [3,11.39]
CrossBarZ_Meas = [0,1.39]
KingPostKeel_Meas = [4,8.22]
KingPostH_Meas = [3,6.28]
KingPostRake_Meas = [0,1.86]
TrailingEdge_Meas = [9,4.43]
RearWire_Meas = [9,6.29]

# These are the pixel measurements from Joe Faust's posted Predator image:

LenLE_Meas = [332,0]
LenKeel_Meas = [213,0]
KeelFrontY_Meas = [154,0]
KeelRearY_Meas = [59,0]
WingTipX_Meas = [291,0] # Predator span of 35' 4" / 2 = 17' 8"
WingTipZ_Meas = [6,0]
CtlBarH_Meas = [70,0]
CtlBarW_Meas = [107,0]
CtlBarLoc_Meas = [180,0]
CtlBarRake_Meas = [65,0]
CrossBarLE_Meas = [195.9,0]
CrossBarKeel_Meas = [68,0]
CrossBarZ_Meas = [7,0]
KingPostKeel_Meas = [181,0]
KingPostH_Meas = [137,0]
KingPostRake_Meas = [7,0]
TrailingEdge_Meas = [112,0]
RearWire_Meas = [120,0]



# Convert [feet,inches] to feet
LenLE = LenLE_Meas[0] + (LenLE_Meas[1]/12.0)
LenKeel = LenKeel_Meas[0] + (LenKeel_Meas[1]/12.0)
KeelFrontY = KeelFrontY_Meas[0] + (KeelFrontY_Meas[1]/12.0)
KeelRearY = - ( KeelRearY_Meas[0] + (KeelRearY_Meas[1]/12.0) )
WingTipX = WingTipX_Meas[0] + (WingTipX_Meas[1]/12.0)
WingTipZ = WingTipZ_Meas[0] + (WingTipZ_Meas[1]/12.0)
CtlBarH = CtlBarH_Meas[0] + (CtlBarH_Meas[1]/12.0)
CtlBarW = CtlBarW_Meas[0] + (CtlBarW_Meas[1]/12.0)
CtlBarLoc = CtlBarLoc_Meas[0] + (CtlBarLoc_Meas[1]/12.0)
CtlBarRake = CtlBarRake_Meas[0] + (CtlBarRake_Meas[1]/12.0)
CrossBarLE = CrossBarLE_Meas[0] + (CrossBarLE_Meas[1]/12.0)
CrossBarKeel = CrossBarKeel_Meas[0] + (CrossBarKeel_Meas[1]/12.0)
CrossBarZ = CrossBarZ_Meas[0] + (CrossBarZ_Meas[1]/12.0)
KingPostKeel = KingPostKeel_Meas[0] + (KingPostKeel_Meas[1]/12.0)
KingPostH = KingPostH_Meas[0] + (KingPostH_Meas[1]/12.0)
KingPostRake = KingPostRake_Meas[0] + (KingPostRake_Meas[1]/12.0)
TrailingEdge = TrailingEdge_Meas[0] + (TrailingEdge_Meas[1]/12.0)
RearWire = RearWire_Meas[0] + (RearWire_Meas[1]/12.0)

# Convert certain values to percents
CtlBarPctKeel = 100.0 * CtlBarLoc / LenKeel
CrossBarPctLE = 100.0 * CrossBarLE / LenLE
CrossBarPctKeel = 100.0 * CrossBarKeel / LenKeel
KingPostPctKeel = 100.0 * KingPostKeel / LenKeel
TrailingEdgePctKeel = 100.0 * TrailingEdge / LenKeel
RearWirePctKeel = 100.0 * RearWire / LenKeel

# Generate and print the model in JSON format
print ( "{" )
print ( " 'Version': 1.0," )
print ( " 'KeelFrontPoint': [0," + str(KeelFrontY) + ",0]," )
print ( " 'KeelRearPoint': [0," + str(KeelRearY) + ",0]," )
print ( " 'WingTipPoint': [" + str(WingTipX) + ",0," + str(WingTipZ) + "]," )
print ( " 'TrailingEdgePercentKeel': " + str(TrailingEdgePctKeel) + "," )
print ( " 'RearWirePercentKeel': " + str(RearWirePctKeel) + "," )
print ( " 'ControlBar': {" )
print ( " 'Height': " + str(CtlBarH) + "," )
print ( " 'Width': " + str(CtlBarW) + "," )
print ( " 'ApexPercentKeel': " + str(CtlBarPctKeel) + "," )
print ( " 'RakeDistance': " + str(CtlBarRake) + "," )
print ( " }," )
print ( " 'CrossBar': {" )
print ( " 'PercentKeel': " + str(CrossBarPctKeel) + "," )
print ( " 'PercentLeadingEdge': " + str(CrossBarPctLE) + "," )
print ( " 'HeightAboveKeel': " + str(CrossBarZ) + "," )
print ( " }," )
print ( " 'KingPost': {" )
print ( " 'PercentKeel': " + str(KingPostPctKeel) + "," )
print ( " 'Height': " + str(KingPostH) + "," )
print ( " 'RakeDistance': " + str(KingPostRake) + "," )
print ( " }," )
print ( " 'Battens': {" )
print ( " 'NumPerSide': 2," )
print ( " 'BattenList': [" )
print ( " {" )
print ( " 'PercentLeadingEdge': 0," )
print ( " 'Segments': 20," )
print ( " 'LeadingEdge': [50.0,165.0]," )
print ( " 'LeadingEdgeControl': [125.0,20.0]," )
print ( " 'TrailingEdgeControl': [275.0,150.0]," )
print ( " 'TrailingEdge': [685.0,160.0]" )
print ( " }," )
print ( " {" )
print ( " 'PercentLeadingEdge': 100," )
print ( " 'Segments': 20," )
print ( " 'LeadingEdge': [225.0,305.0]," )
print ( " 'LeadingEdgeControl': [240.0,295.0]," )
print ( " 'TrailingEdgeControl': [260.0,300.0]," )
print ( " 'TrailingEdge': [350.0,315.0]" )
print ( " }" )
print ( " ]" )
print ( " }" )
print ( "}" )


It's a pretty simple program, and the data is all hard-coded. The variables are reassigned several times before doing the actual calculations, and only the last set counts. The earlier values are just there for documentation of those models.

While that version builds a model from measurements, I also wrote a program to generate "measurements" from a model. This was mostly used to confirm that the earlier program worked properly, but it may have other uses. Here's the code:

import math

# This is the standard glider model

Standard_Model = {
'Version': 1.0,
'KeelFrontPoint': [0,5,0],
'KeelRearPoint': [0,-5,0],
'WingTipPoint': [15,-3,0.2],
'TrailingEdgePercentKeel': 80,
'RearWirePercentKeel': 82,
'ControlBar': {
'Height': 3.5,
'Width': 3.2,
'ApexPercentKeel': 40,
'RakeDistance': 1.0,
},
'CrossBar': {
'PercentKeel': 33,
'PercentLeadingEdge': 60,
'HeightAboveKeel': 0.1,
},
'KingPost': {
'PercentKeel': 40,
'Height': 3,
'RakeDistance': 0.1,
},
'Battens': {
'NumPerSide': 2,
'BattenList': [
{
'PercentLeadingEdge': 0,
'Segments': 20,
'LeadingEdge': [50.0,165.0],
'LeadingEdgeControl': [125.0,20.0],
'TrailingEdgeControl': [275.0,150.0],
'TrailingEdge': [685.0,160.0]
},
{
'PercentLeadingEdge': 100,
'Segments': 20,
'LeadingEdge': [225.0,305.0],
'LeadingEdgeControl': [240.0,295.0],
'TrailingEdgeControl': [260.0,300.0],
'TrailingEdge': [350.0,315.0]
}
]
}
}

# This is a "pixel scale" model of a Predator from photo
# This model should use a "Zoom" of around 1.5 to fit
# This model has a shifted origin (by 60) to rotate nicely.

Model = {
'Version': 1.0,
'KeelFrontPoint': [0,94,0],
'KeelRearPoint': [0,-119,0],
'WingTipPoint': [291,-60,6],
'TrailingEdgePercentKeel': 52.5821596244,
'RearWirePercentKeel': 75,
'ControlBar': {
'Height': 65,
'Width': 107,
'ApexPercentKeel': 42,
'RakeDistance': 27,
},
'CrossBar': {
'PercentKeel': 35,
'PercentLeadingEdge': 59.0060240964,
'HeightAboveKeel': 7,
},
'KingPost': {
'PercentKeel': 42,
'Height': 50,
'RakeDistance': 3,
},
'Battens': {
'NumPerSide': 2,
'BattenList': [
{
'PercentLeadingEdge': 0,
'Segments': 20,
'LeadingEdge': [50,165],
'LeadingEdgeControl': [125,20],
'TrailingEdgeControl': [275,150],
'TrailingEdge': [685,160]
},
{
'PercentLeadingEdge': 100,
'Segments': 20,
'LeadingEdge': [225,305],
'LeadingEdgeControl': [240,295],
'TrailingEdgeControl': [283.5,297.1666717529297],
'TrailingEdge': [404.5,318.1666717529297]
}
]
}
}


# Convert from dictionary to named variables
KeelFrontY = Model['KeelFrontPoint'][1]
KeelRearY = Model['KeelRearPoint'][1]
WingTipX = Model['WingTipPoint'][0]
WingTipZ = Model['WingTipPoint'][2]
TrailingEdgePctKeel = Model['TrailingEdgePercentKeel']
RearWirePctKeel = Model['RearWirePercentKeel']
CtlBarH = Model['ControlBar']['Height']
CtlBarW = Model['ControlBar']['Width']
CtlBarPctKeel = Model['ControlBar']['ApexPercentKeel']
CtlBarRake = Model['ControlBar']['RakeDistance']
CrossBarPctKeel = Model['CrossBar']['PercentKeel']
CrossBarPctLE = Model['CrossBar']['PercentLeadingEdge']
CrossBarZ = Model['CrossBar']['HeightAboveKeel']
KingPostPctKeel = Model['KingPost']['PercentKeel']
KingPostH = Model['KingPost']['Height']
KingPostRake = Model['KingPost']['RakeDistance']

# Generate additional scalar values

LenKeel = KeelFrontY - KeelRearY # Note that KeelRearY will normally be negative
LenLE = math.sqrt ( (KeelFrontY * KeelFrontY) + (WingTipX * WingTipX) )

# Convert from percent values to scalar values
CtlBarLoc = CtlBarPctKeel * LenKeel / 100.0
CrossBarLE = CrossBarPctLE * LenLE / 100.0
CrossBarKeel = CrossBarPctKeel * LenKeel / 100.0
KingPostKeel = KingPostPctKeel * LenKeel / 100.0
TrailingEdge = TrailingEdgePctKeel * LenKeel / 100.0
RearWire = RearWirePctKeel * LenKeel / 100.0

# Print the scalar values as measured values
def ft_in_from_ft ( ft ):
return [int(ft), int(100*12*(ft-int(ft)))/100.0 ]

print ( "LenLE_Meas = " + str(ft_in_from_ft(LenLE)) )
print ( "LenKeel_Meas = " + str(ft_in_from_ft(LenKeel)) )
print ( "KeelFrontY_Meas = " + str(ft_in_from_ft(KeelFrontY)) )
print ( "KeelRearY_Meas = " + str(ft_in_from_ft(-KeelRearY)) )
print ( "WingTipX_Meas = " + str(ft_in_from_ft(WingTipX)) )
print ( "WingTipZ_Meas = " + str(ft_in_from_ft(WingTipZ)) )
print ( "CtlBarH_Meas = " + str(ft_in_from_ft(CtlBarH)) )
print ( "CtlBarW_Meas = " + str(ft_in_from_ft(CtlBarW)) )
print ( "CtlBarLoc_Meas = " + str(ft_in_from_ft(CtlBarLoc)) )
print ( "CtlBarRake_Meas = " + str(ft_in_from_ft(CtlBarRake)) )
print ( "CrossBarLE_Meas = " + str(ft_in_from_ft(CrossBarLE)) )
print ( "CrossBarKeel_Meas = " + str(ft_in_from_ft(CrossBarKeel)) )
print ( "CrossBarZ_Meas = " + str(ft_in_from_ft(CrossBarZ)) )
print ( "KingPostKeel_Meas = " + str(ft_in_from_ft(KingPostKeel)) )
print ( "KingPostH_Meas = " + str(ft_in_from_ft(KingPostH)) )
print ( "KingPostRake_Meas = " + str(ft_in_from_ft(KingPostRake)) )
print ( "TrailingEdge_Meas = " + str(ft_in_from_ft(TrailingEdge)) )
print ( "RearWire_Meas = " + str(ft_in_from_ft(RearWire)) )


As with the other program, this program contains several "hard-coded" models, and only the last one is actually used in the computation.
Join a National Hang Gliding Organization: US Hawks at ushawks.org
View my rating at: US Hang Gliding Rating System
Every human at every point in history has an opportunity to choose courage over cowardice. Look around and you will find that opportunity in your own time.
Bob Kuczewski
User avatar
Contributor
Contributor
 
Posts: 8373
Joined: Fri Aug 13, 2010 2:40 pm
Location: San Diego, CA

Predator Model

Postby Chris McKeon » Sat Dec 11, 2021 8:30 pm

TOO TIGHT IS NOT RITE.

I believe that I will get off My rear-end, and get My Predator Set-up again. It really is weird, well to Me anyways it is weird. My Predator has become so hard to Tension. John told Me that His Predator has become harder to tension also. John said to Me that He does not know why. Does anyone have an idea as to why My Predator has become so hard to tension?

Too Tight is not rite. Heck I believe that I will fabricate a device that will aid Me in tightening My Sail.
Chris McKeon
User avatar
Contributor
Contributor
 
Posts: 1566
Joined: Wed Jul 31, 2013 7:46 pm

Re: Predator Model

Postby Bob Kuczewski » Sun Dec 12, 2021 2:34 am

Chris McKeon wrote:Too Tight is not rite. Heck I believe that I will fabricate a device that will aid Me in tightening My Sail.

I agree that too tight is not right. I have had a hard time setting up gliders that have "shrunk" from sitting in the bag for too long. But they haven't been as tight as you described. When I have experienced that degree of tightness it's always been because something else was misconfigured. Examples include a bridle line wrapped around a batten, a side wire looped around the kingpost, tip bags too tight around the sail, the nose wire being attached, or the wrong length base tube. So be very careful that everything else is set up right before forcing it with any kind of device.

I did a search for the predator manual, and I found this article:

     https://delta-club-82.com/bible/876-han ... edator.htm

I was hoping to find a description of the setup procedure, but that "manual" is really more of an review/advertisement. You might check with John to see if he has a manual before trying to force anything.

With all those warnings in mind, you may still decide that applying more force is needed. My thought there is that you might use a small set of pulleys between the keel and the haul-back handle. You could anchor it to the keel with either hose clamps or some kind of cap over the end of the keel. An advantage of using that kind of device is that you can apply some tension and tie it off for a few hours while the sail slowly stretches. You can get some nice little block and tackle pulleys at Home Depot for a few dollars. I've used them to design a pulley system for storing my glider on the garage ceiling and they worked great.
Join a National Hang Gliding Organization: US Hawks at ushawks.org
View my rating at: US Hang Gliding Rating System
Every human at every point in history has an opportunity to choose courage over cowardice. Look around and you will find that opportunity in your own time.
Bob Kuczewski
User avatar
Contributor
Contributor
 
Posts: 8373
Joined: Fri Aug 13, 2010 2:40 pm
Location: San Diego, CA

Re: Predator Model

Postby JoeF » Sat Oct 01, 2022 9:07 pm

Join a National Hang Gliding Organization: US Hawks at ushawks.org

View pilots' hang gliding rating at: US Hang Gliding Rating System
JoeF
User avatar
Contributor
Contributor
 
Posts: 4553
Joined: Sat Aug 14, 2010 3:41 pm

Re: Predator Model

Postby Chris McKeon » Sat Oct 01, 2022 10:20 pm

Bad Dog, I loved, I love that. What a sense of Humor the Guy Has.
Chris McKeon
User avatar
Contributor
Contributor
 
Posts: 1566
Joined: Wed Jul 31, 2013 7:46 pm

Re: Predator Model

Postby Bob Kuczewski » Sun Oct 02, 2022 3:21 am

Chris McKeon wrote:Bad Dog, I loved, I love that. What a sense of Humor the Guy Has.


Bad_Dog.png
Bad_Dog.png (351.96 KiB) Viewed 1325 times


It's been about a year since you last set up your Predator. Maybe it's time to try again?
Join a National Hang Gliding Organization: US Hawks at ushawks.org
View my rating at: US Hang Gliding Rating System
Every human at every point in history has an opportunity to choose courage over cowardice. Look around and you will find that opportunity in your own time.
Bob Kuczewski
User avatar
Contributor
Contributor
 
Posts: 8373
Joined: Fri Aug 13, 2010 2:40 pm
Location: San Diego, CA

Re: Predator Model

Postby Chris McKeon » Sun Oct 02, 2022 7:36 am

Setting up My Predator; Bob really what will I accomplish by setting up My Predator? The only issue that makes setting up My Predator is that Tensioning My Predator is Quite difficult to do. I had to have My Sister Kathleen assist Me. Sh pulled the Haul-Back, while I helped by pushing the Cross-Bars back. Do You believe that If I set-up My Glider over and over, that the tightness in the Sail will subside? I do not know, fot this is an entirely new deal for Me. But heck if by setting the Glider over and over, if by doing so would indeed stretch My sail. Therefore losing the sail, thus making the sail easier to tension, i will initiate the process of setting up My Predator. Bob You might be on to something here, please give Me Your thoughts, or maybe even Your experiences regarding; Having a Wing getting to Tight over time.

Also Bob thanks for showing some interest in My too Tight a Sail Predator Deal.
Chris McKeon
User avatar
Contributor
Contributor
 
Posts: 1566
Joined: Wed Jul 31, 2013 7:46 pm

PreviousNext
Forum Statistics

Who is online

Users browsing this forum: No registered users and 23 guests

Options

Return to Hang Gliding General