Taking a shot at the G record

The Rocketry Forum

Help Support The Rocketry Forum:

This site may earn a commission from merchant affiliate links, including eBay, Amazon, and others.
Checking out the data, here is the acceleration of the apogee deployment:

1713802790876.png
-Z is the direction of forward movement. Lest you think that the charge was over-sized to cause 300 Gs of acceleration, only 0.17 grams of BP were used in this flight. Everything is just very light. You can see 3 sets of reefing tape break before the shock cord goes taut.

Here's the acceleration from liftoff to the apogee deployment:

1713803020090.png

The -Z axis is the motor thrust direction. After the initial kick, the dual thrust motor throttles down and keeps going for a total of a 12 second burn. In the meantime, the centripetal acceleration measured on the X and Y axes exceed the motor thrust.

1713803218823.png

The baro altimeter shows a pretty big transonic effect but then matches up pretty well with the GPS altitude once it slows down. The inertial altitude is low because early on in the flight, the the inertial navigation thought the rocket was more tilted than it actually was:

1713803450866.png

Here are the gyro measurements for the first part of the flight:

1713803564759.png

The roll axis (Z) sensor maxed out about 4 seconds into the flight. The gyro data in the early part of the flight is interesting:

1713803703845.png

Starting at liftoff, you can see some noise from the rocket bouncing around in the tower, which is normal, but then is a bunch of action around 0.5 seconds into the flight. It shows up a bit in the acclerometer data also. The roll rate weirdly goes down a lot between 1.2-2 seconds and then goes back to following the velocity profile.

1713804058648.png
1713804077584.png

I'm guessing that the violent wiggle around 0.5 seconds might be from fin flutter at a resonant velocity? Usually it gets worse as the velocity goes up though, so I'm a little mystified. In the lower plot the accelerometer data is zoomed in enough so you can see some individual impacts inside the 12' tower.

Here's the rocket tilt:

1713804491184.png
The apparent straightening of the rocket at 3 seconds is a little surprising, but there was a very distinct wind shear layer that you can see from the GPS plot:

1713804955017.png
The ground track starts at the top, and the rocket started out weatherocked into the SW wind. But then it drifted on the NW wind until it got back down to the surface layer.
 

Attachments

  • 1713804964182.png
    1713804964182.png
    3.3 MB · Views: 0
Adrian --

Did the 6-inch(ish) G12 motor kick partially out of the booster or was flown that way to make room for recovery ?

Thanks !

-- kjh

EDIT: Thanks for the Data Files ! Q: what was the site temperature ( more -or- less ) ?
It partially kicked out. The temperature was around 50F.
 
I'm testing the latest version of the Featherweight User Interface phone app, and one of its new features is to export the tracker recorded data as a .kml file. Here's the Google Earth view of the flight:
Nice! I guess we won't need fw2kml down the road lol. Are you going to add more tags for flight events? or other details?
 
Nice! I guess we won't need fw2kml down the road lol. Are you going to add more tags for flight events? or other details?
I might like to. Launch and landing would be nice. Do you have other ideas?

Thanks to you and @Arpak for your work on the .kml converter. My developer was able to add this capability quickly because of your work. Next time you want to order something let me know and I'll show my appreciation.
 
I might like to. Launch and landing would be nice. Do you have other ideas?

Thanks to you and @Arpak for your work on the .kml converter. My developer was able to add this capability quickly because of your work. Next time you want to order something let me know and I'll show my appreciation.
Was a fun challenge! Thanks for making a killer piece of kit. 😀
 
I might like to. Launch and landing would be nice. Do you have other ideas?

Thanks to you and @Arpak for your work on the .kml converter. My developer was able to add this capability quickly because of your work. Next time you want to order something let me know and I'll show my appreciation.
Ejection charge/parachute deployment would be nice if you have that information, or can infer it from the data. Another thing I was thinking about adding to the landing marker is lateral distance from launch pad, so that's worth considering.

E: in the same realm as EC/parachutes, airstart/stage tagging would be cool too.
 
Just apogee marker would be nice too. I've used fw2kml to compare launch, apo, and landing vs rocketpy dispersion plots, it's a niche but interesting tool.
 
Adrian,

I focused on your ~1 second flight anomaly during boost between 1 & 2 seconds flight time. This cannot be real data. All three accelerometers producing almost identical patterns with just an offset. A straight line jump into and out of the event with normal data before and after. The roll rate gyro is also a very close match to the accelerometer pattern even in recorded values.
 

Attachments

  • G record Accel.png
    G record Accel.png
    400.7 KB · Views: 0
  • G record Gyros.png
    G record Gyros.png
    433.8 KB · Views: 0
Adrian,

I focused on your ~1 second flight anomaly during boost between 1 & 2 seconds flight time. This cannot be real data. All three accelerometers producing almost identical patterns with just an offset. A straight line jump into and out of the event with normal data before and after. The roll rate gyro is also a very close match to the accelerometer pattern even in recorded values.
What data are you plotting in the first plot? The accel data from the flight looks like this during that time:

1714316668884.png

There us a little wiggle in the accel data around 0.5 seconds that corresponds to larger gyro activity, which makes me think that that gyro oscillation is real. But for the Gyro Z-axis weirdness around 1.5 seconds, there is no corresponding accelerometer activity, so that make me think it is some kind of artifact or anomalous data.
 
Both graphs are from your high_rate_4-21-2024 CSV file data, posted on 4-22-2024. It appeared to me as a high G range switch over.
Try downloading them again. I wondered if the file that I posted was corrupted, so I just downloaded it and plotted the accels in Excel. Here's what I got from the high rate file, matching the Matlab plotting from above:

1714336612697.png
 

Attachments

  • 1714336614465.png
    1714336614465.png
    26.8 KB · Views: 0
Back
Top