For news TAP HERE and scroll down
IMG_20190331_110316.jpg
Likes Like
RocketEZI-65
Launches1
Flight StatusPartial
Event
SRA2.pngSRA-Jason Cook special launch 2019-03-31
Altitude11630 ft
3544.82m
Velocity886 MPH
1426.46km/h
Gs Actual12.2
Weight6.43lb.
2.92kg
StageMotor
1 K300

SRA Launch Special For Me - Thanks a million

2019-03-31 11:03:45Z

Insane Rocketry

Likefileicon launch190331_104355_209.csv

Stratologger

Likefileicon PFBackup.pf2

Description

Insane Rockets data file is raw unaltered data.

If you open in excel, velocity is 10 frames behind (0.5 seconds) and you should adjust accordingly. To find deployment, seconds column value is 34.806. Deployment was forced by value in column AltitudeMSLGPS.

Main @ apogee due to early deployment.

Launch control system super fickle, but we were able to get both rockets launched.

I'll get that cleaned up now that the overall concept is proven.

---

Early Deployment Summary

Deployment of drogue occurred when the rocket was ascending 187 miles per hour. Tim, you heard me, from watching the video, I said I thought it deployed at what looked like 200mph!!!

I do two independent checks on altitude. Up until today, I've not had a problem with these two techniques.

The second check failed, for the first time. I will no longer use it. Instead I'll use G data as a second check instead erroring to caution. G data for deployment is very predictable.

Current Checks:

The first is based off of barometer data, and pretty much works like any barometer based altimeter. For this launch, the code & data was rock solid as always.

Failed Check that will be Replaced to using Gs:

For this launch and previous launches, the second was based off of GPS data. I did this because the GPS ALWAYS lags, so it is a good delayed backup. GPS always gives me vertical accuracy (meters+-), so I always add the uncertainty of both values to the CURRENT value. That way, it errors with current value artificially inflated. That way, it's a great backup, because IF it shows descent, I know for a fact it is descending. I had a lock of 11 satellites.

Failure:

Previous GPS Read Altitude: 3282 meters with a vertical accuracy of +-19 meters.

Next GPS Read Altitude: -23 meters with a vertical accuracy of +-204 meters.

Using my formula, Is 3282(previous read) greater than -23+19+204? Yes, it is really descending FAST deploy! Code is actually more complex to insure values, but keeping it simple for describing.

It gave that bogus reading (altitude -23meters) for 7 seconds of reads.

---

The good news:

The massive two months of changes Insane Rockets App in the rocket code-base I believe are now proven.

For now I'll just disable the GPS check before adding Gs code, it will dual deploy like a standard barometer based tracker for a release or two in the app store.

Over the next few days I'll scour the data more in depth to confirm all telemetry, battery conservation, heat conservation, and Android 8.1 compatibility changes are working correctly. I'll then release.

---

GoPro Ground Zero Launch thanks to Tim.

 

Comments

esotericdude
Like 2019-03-31 20:47:15Z

Deployment of drogue occurred when the rocket was ascending 187 miles per hour. Tim, you heard me, from watching the video, I said I thought it deployed at what looked like 200mph!!!

I do two independent checks on altitude. Up until today, I've not had a problem with these two techniques.

The second check failed, for the first time. I will no longer use it. Instead I'll use G data as a second check instead erroring to caution. G data for deployment is very predictable.

Current Checks:

The first is based off of barometer data, and pretty much works like any barometer based altimeter. For this launch, the code & data was rock solid as always.

Failed Check that will be Replaced to using Gs:

For this launch and previous launches, the second was based off of GPS data. I did this because the GPS ALWAYS lags, so it is a good delayed backup. GPS always gives me vertical accuracy (meters+-), so I always add the uncertainty of both values to the CURRENT value. That way, it errors with current value artificially inflated. That way, it's a great backup, because IF it shows descent, I know for a fact it is descending. I had a lock of 11 satellites.

Failure:

Previous GPS Read Altitude: 3282 meters with a vertical accuracy of +-19 meters.

Next GPS Read Altitude: -23 meters with a vertical accuracy of +-204 meters.

Using my formula, Is 3282(previous read) greater than -23+19+204? Yes, it is really descending FAST deploy! Code is actually more complex to insure values, but keeping it simple for describing.

It gave that bogus reading (altitude -23meters) for 7 seconds of reads.

timcub on 2019-03-31 21:42:10Z wrote:

Figured out why your main popped at the top yet?

esotericdude
Like 2019-03-31 21:36:02Z

The good news:

The massive two months of changes Insane Rockets App in the rocket code-base I believe are now proven.

For now I'll just disable the GPS check before adding Gs code, it will dual deploy like a standard barometer based tracker for a release or two in the app store.

Over the next few days I'll scour the data more in depth to confirm all telemetry, battery conservation, heat conservation, and Android 8.1 compatibility changes are working correctly. I'll then release.

frewi80
Like 2019-04-01 19:24:13Z

Tim has a real nice camera to capture those high altitude images...

esotericdude
Like 2019-04-01 20:06:13Z

Added Insane Rockets CSV file.

Insane Rockets data file is raw unaltered data.If you open in excel, velocity is 10 frames behind (0.5 seconds) and you should adjust accordingly. To find deployment, seconds column value is 34.806. Deployment was forced by value in column AltitudeMSLGPS.

timcub
Like 2019-04-02 07:51:03Z

So did you lose satellite fix for that big change in altitude? I guess that was a risky move to use GPS for deployment. With the exception of long burn, I usually lose GPS fix from boost until I get near apogee when rocket slows down enough to re-acquire sat fix.


Video


Like

Like

Like

Images

IMG_20190331_110316.jpg
Like
vlcsnap-2019-03-31-19h02m39s718.png
Like
vlcsnap-2019-03-31-19h08m14s266.png
Like
vlcsnap-2019-03-31-19h16m00s488.png
Like
vlcsnap-2019-03-31-19h23m15s533.png
Like
vlcsnap-2019-03-31-19h24m54s763.png
Like
vlcsnap-2019-03-31-22h38m51s717.png
Like
vlcsnap-2019-03-31-22h38m51s717_2.png
Like
010.jpg
Like
020.jpg
Like
030.jpg
Like
040.jpg
Like
050.jpg
Like
060.jpg
Like
070.jpg
Like
080.jpg
Like
090.jpg
Like
100.jpg
Like