Larry Grater's Posts (3)

Sort by

3689474659?profile=original

On 5/18/12 North Texas Near Space (NTNS-2) achieved a maximum altitude of 87959 ft over a sparsely populated section of North Texas. The flight was partially successful and full duration telemetry and camera data were recoverd. 

 

• Vehicle departed from controlled flight, did not navigate to the landing site and was severely damaged
• Modified SW version 2.50 to utilize new AHRS code
• Modified Stinger 64 airframe
• Surface winds calm
• Trajectory was close to prediction
• Ascent was nominal
• Ascent terminated early on balloon failure at 88k ft.  APM released on free fall indication and routed autopilot outputs to servos.  Balloon not recommended since bursts at 86k and 88k on NTNS-1&2.  2# free lift.
• Higher than expected descent rate experienced and the plane spun down to ~17000 ft and began semi-controlled flight.  The A/F managed to fly despite issues with the attitude reference and control saturation.
• Impact occured due to additional loss of reference.  The roll autopilot was tracking commands.
• Maximum Mach number was about 0.5
• Minimum internal temperature was 48F.
• Airframe held up very well.  One aileron horn was damaged (inconclusive considering the impact).
• Just Plain Strange: Almost crashed on my ranch.  The airspeed probe is re-usable.
• Likely root case (s):
       - dynamic pressure measurement low by 0.5
       - gain scaling issues causing pitch and roll oscillations.
       - pitch reference and finally roll reference is lost
       - roll reference loss responsible for final dive
       - contributing: agressive airspeed targets
• Todo:
       - duplicate pitch oscillation with the stinger UAV; may need to duplicate A/S measurement issue in SW
       - simulation reconstruction
       - new A/F build, upgrades, noted SW changes (see spreadsheet), merge to 2.60 or latest stable build, gains

Read more…

3689469578?profile=originalI've just finished the build and will begin early full up integration testing in the next day or so on NTNS-2.  This is a highly modified Stinger 64 with APM2.  There are really 2 airframes.  One is for flight testing, gain tuning, learning a little about APM2.  I have to admit that there have been several issues.  The two that i know that I have are the flash card slot being a bit less than tight, perhaps some formatting issues -and- the stock GPS lock issue.  For my installation this doesn't seem to bother time to 1st fix, but I am loosing lock in flight, dropping satellites.  I am NOT using a downlink, have the jumper removed, and power is being applied to the input and output sides with a Castle BEC Pro set at 5.05V.  SW version is 2.40.  Of course no red wire from the ESC.  The GPS is somewhat masked by some wires and the EDF mtr wires run just behind APM down to the fan.  It's not ideal for EMI.

Not to worry since this isn't the objective configuration and I just "score" APM when it has lock and the altitude is reasonable.  My 100 mph Stinger flight test bird:

 

Here's a picture from the Stinger HAB build.  It's pretty tight inside the bay:

3689469547?profile=original

Some of the BOM:

2-Castle BEC Pros (5.3 and 12V)

3-Omega Kapton heaters

1-external relay + helpful external LED

3-Airtronics 94761 servos for flight control

1-analog servo for the sailplane towhook release

APM2

Venus GPS/regulator/logic level converter

SparkFun datalogger

ReplayHD 1080p (heated) and externally powered

4s 5000 mAh battery

airspeed probe and pressure sensor

voltage and current sensor

Airtronics 10ch rcvr, Airtronics SD-10g TX

Very much modified Stinger 64 airframe (the only inexpensive component)

BRB APRS

I'm about 1/2 # lighter than NTNS-1; 1200g Kaymont

Total weight is 3# 2oz vs. the flight test bird at 2# (identical XCG and flight control setups)

Ballast is 2.3oz in the forward bay.

The result:

3689469624?profile=original

Testing, SW version catch up/merges, HIL testing with FlightGear/X-Planes, Temperature testing with APM1, duration testing, log testing...camera testing.... to follow.

 

Read more…

3689459066?profile=original

On 5/20/12 North Texas Near Space (NTNS) and Project Soar collaborated on a dual launch during the annular eclipse. Albuquerque was directly in path of the eclipse. The NTNS payload had most of the electronics that I had intended for a guided flight. That airframe is no more, but I have some data that I'd like to share with the group as a result. The dual launch was a great target of opportunity for looking at APM data at altitude. Most of the flight objectives were met.

KML:

NTNS-1 at Altitude.

3689459118?profile=original

Project Soar Payload at Altitude:

3689459162?profile=original

The NTNS-1 payload captured the Soar payload during descent.  I don't know if this has been done before.

3689459144?profile=original

I'm glossing over the APM data because most of the setup, objectives, data plots, lessons learned, future activity are documented below.  The APM data was converted to CSV so that it's fairly easy to read.  I really brute forced this and should have written a script.  SW V2.28 was somewhat modified to reduce the data frequency to a constant 0.5 Hz.  It turned out that the flight time from turn on to recovery was just under 3 hours and produced only an 805 kb log file.  Obviously I needed to gather more variables or choose a higher rate. I was lucky enough to be able to walk up to the payload and turn it off.  APM operated through the landing.  There is another thread that we did pre-launch discussing tailoring of the data stream.  Unfortunately I didn't get to far mainly due to time.  I was done with SW the day before the launch.

Postflight Data and Reconstructions: Postflight

Data Spreadsheet and Plots: Analysis Spreadsheet

Log Files and other data: TM

Preliminary Video Rendering: Best in 1080p setting

If you poke around in the site you can find 1920X1080 frame captures for most events.

We're getting collectively closer to making some guided flights. Now we have 2 data sets.  Best of luck to all.

 

Regards,

Larry D. Grater

 

Read more…