Post your Raven FIPa files here

[HOBOjr]

That one worked. Looks great! An almost classically clean file. Looks like you had your main set to 1400 feet; does that sound about right? Congrats on the Level 3.

Yes it is as close to 1400 feet as I could set the program. Thanks it was a great flight and everything worked as planned.
@ blackbrandt, Thanks for the laugh, it is fixed now!

 

[Adrian A]

I had a second ballistic recovery Saturday due to Raven failure. The Formula 98 impacted in the far south field after a long slow boost to an estimated 6000 feet on a K160. Impact sheared off the supercap, beeper, and terminal block. I was able to connect power and the FIP was able to connect to the Raven. Although the Raven was beeping correctly on the pad, it never detected liftoff and there was no data file. I was able to read the 2 previous flight data files from the Raven. If my twist and tape down wires hadn't been sheared off by impact, there would have been power - the battery was still at 9.24V.
The first failure was in June with a Raven version 1, this was a Raven version 2 (on it's third flight).
Video of the boost:

The Raven checks for a reasonable G reading before it beeps out the normal pre-launch beeps. So if it's beeping correctly on the pad, then everything needed to detect liftoff was working at the time. The Raven will keep recording for a few seconds after power is removed, so if it had a power loss in flight, it still would have recorded a new flight file. Maybe the twist&tape came loose between when you walked away and when the rocket was launched?

 

[dickmoran]

Flew at MDRA Red Glare on Friday 11-16-12 and today 11-17-12. Friday was with a P38 H123 Skidmark. Went to 2080'. Looks like #3 went before Apogee. Today was on a P38 I180 Skidmark. Went to 3855'. #3 went before Apogee again. Any ideas? 1st time this has happened. Did my parms change?

Dick
NAR6306 L1
Trip 14074 L1
MDRA 254

 

[CCotner]

Yes it is as close to 1400 feet as I could set the program.

I recognize that other people on the forum have bigger raven problems than this, but it's always bothered me. How come the user can't simply set a variable value like AGL1 or VEL2 (etc) ? One types it in, and hits program, and what actually gets saved is always a little bit different, within %5 or so. What's up with that?

 

[dickmoran]

Here are the settings for my Raven. Need to find out why 3 is going before Apogee.

Dick

View attachment DickMoran Raven Parms.doc

 

[Adrian A]

I recognize that other people on the forum have bigger raven problems than this, but it's always bothered me. How come the user can't simply set a variable value like AGL1 or VEL2 (etc) ? One types it in, and hits program, and what actually gets saved is always a little bit different, within %5 or so. What's up with that?

It's just a matter of resolution. There are 10 bits worth of altitude settings available in the firmware for those settings, or 1024 different possibilities. The setting resolution was chosen to be 32 feet so that it would cover over 32,000 feet. (Why only 10 bits? It had to to with fitting the whole Parrot firmware into 8 k and using type-able ASCII characters for programming)

 

[Adrian A]

How does one get at the raw data in a FIP file, i.e. bring it into a spreadsheet? The raw data tab doesn't appear very useful in the format displayed.

You can right-click in the parameter window in the graphing part of the FIP to copy or save the selected raw data. I need to get this into the user's manual sometime.

-Adrian

 

[Adrian A]

Here are the settings for my Raven. Need to find out why 3 is going before Apogee.

Dick

Looks like you're using standard settings. The two channels are detecting apogee in completely different ways, one using the baro sensor and the other by integrating the acceleration. The accel sensor isn't as accurate as the baro sensor for this application. See the last paragraph in post #89 for more information.

 

[Rocketjunkie]

The Raven checks for a reasonable G reading before it beeps out the normal pre-launch beeps. So if it's beeping correctly on the pad, then everything needed to detect liftoff was working at the time. The Raven will keep recording for a few seconds after power is removed, so if it had a power loss in flight, it still would have recorded a new flight file. Maybe the twist&tape came loose between when you walked away and when the rocket was launched?

Why twice with Ravens, never in literally hundreds of other flights using other altimeters? If a Raven rides in another of my rockets, it will NOT be alone.

 

[Kollár]

i am just planning to use these stuffs named Power Perch and 3.7V LiPo. so i would just want to ask that will it be suitable for me to use these versions and also what will be the cost which i have to bear for these versions

 

[JDcluster]

I flew my Raven 3 twice and on the second flight (which was also flown at RG); I added a 1/2 sec to the accel apogee (first channel) as the first flight seemed a bit early.
I looked at the flight profile ( FIPa coming tomorrow) and it was closer to actual apogee.

JD

 

[patelldp]

Flew my Raven 2 twice in my Competitor 5 this past weekend.

The first flight was on a Cesaroni M840 moon burn for my L3.

Second flight was on an EX white for the Loki 76-8000 case. Look at the file and see if you can tell me what's wrong or what may have happened during the flight.

View attachment Competitor5_M2800_11_17_12.FIPa

 

[Adrian A]

Flew my Raven 2 twice in my Competitor 5 this past weekend.

The first flight was on a Cesaroni M840 moon burn for my L3.

Second flight was on an EX white for the Loki 76-8000 case. Look at the file and see if you can tell me what's wrong or what may have happened during the flight.

Congrats on your L3.

Looks like it after most of the drogue descent, it got tangled or something that caused some major spinning, and then it recovered fine when the main deployed.

 

[patelldp]

Congrats on your L3.

Looks like it after most of the drogue descent, it got tangled or something that caused some major spinning, and then it recovered fine when the main deployed.

Not quite. Main deployed on time at 700', but did not inflate. Specifically look at the descent at ~7,000'.

Any other guesses?

 

[cvanc]

Not quite. Main deployed on time at 700', but did not inflate. Specifically look at the descent at ~7,000'.

Any other guesses?

I think I'm looking at the same knee in the baro data that Adrian is.

'Something' happened on the way down at about 7,000 feet; and after that it fell faster until the main deployment. Did you strip your drouge? Did the shock cord break, causing the 2 halves to fall seperately? If the latter, obviously the altimeter was in the half that held the main, right?

 

[patelldp]

I think I'm looking at the same knee in the baro data that Adrian is.

'Something' happened on the way down at about 7,000 feet; and after that it fell faster until the main deployment. Did you strip your drouge? Did the shock cord break, causing the 2 halves to fall seperately? If the latter, obviously the altimeter was in the half that held the main, right?

Close enough!

The booster on this rocket tends to pinwheel all the way down. Interestingly enough, the repetitive spinning wraps up the cord and hits the quick link against the u-bolt. On 2 flights now, the quick link has either partially or entirely opened. On this flight, the booster separated from the upper section (which held the main) and spun in. Thankfully, the only damage was a popped fillet and the rocket will be ready to fly for next season.

 

[cvanc]

The booster on this rocket tends to pinwheel all the way down.

Hey I got it! Cool (pats self on shoulder).

Very interesting behavior of your booster, especially if it pinwheels on many flights. I wonder if there is a way to 'detune' that so it doesn't happen? Weight the top end of the tube? Put a drouge as close to the booster end of the harness as practical? There must be some way to make it stop.

I forgot to congratulate you on your L3 before, so... congrats!

 

[JDcluster]

View attachment EuFLT7.FIPa


Nothing too special. This was it's 7th or 8th flight ( can't recall)
This time on a 38mm x 6 grain EX load.
On the previous flight I flew it on a CTI J330 classic and got about the same altitude except it flew less than vertical.
The pad was knocked over sending it off of vertical about 15 degrees or so.

JD

 

[cvanc]

View attachment 104899


Nothing too special. This was it's 7th or 8th flight ( can't recall)
This time on a 38mm x 6 grain EX load.
On the previous flight I flew it on a CTI J330 classic and got about the same altitude except it flew less than vertical.
The pad was knocked over sending it off of vertical about 15 degrees or so.

JD

Really nice. Another classically clean file. Love it when the data is so smooth.

 

[JordanT]

I guess I ought to post this here. Take a look at the negative velocity/altitude at the beginning of the flight. Of course, this rocket shredded into a million little teeny pieces sending the nosecone (with the altimeter inside) off in one direction while (what was left of) the streamer and baffle went a different direction. The flight was a 24mm minimum diameter rocket weighing ~50g dry plus an ~80g CTI F240 for a pad mass of 130g.



View attachment 2012-11-22 Dont Blink F240 Shred.FIPa

 

[CarVac]

Disappearing Act, my 38mm minium diameter minimum mass rocket built for the Aerotech I1299, flying on the much gentler I49 with a temporary fincan.
The simulations (with actual launch weight measured right before the RSO check) stated that the rocket would reach 8773 feet, but it actually went around 9100 despite some mild weathercocking; it was a slooooooow, clean liftoff.
View attachment disappearing_act_prelude_i49.FIPa

Things to note:

• Though this is a 250g single axis Raven2, the lateral axis is smoother during ascent.
• The temperature spikes at apogee because of the deployment charge.
• The voltages do all sorts of weird things during the flight; the battery voltage spikes at apogee, falls to zero, spikes higher, and slowly declines; the apogee has a voltage drop during the firing of the charge but it spikes upwards and declines; the main voltage increases at apogee but then drops to a clean zero immediately once the charge goes off.
• What on earth are 'p' and 'v'? They appear to be related to the flight at some points, but not at all at others.

video video video
[video=youtube;nYVKN0ehHxM]https://www.youtube.com/watch?v=nYVKN0ehHxM[/video]

 

[Larry Curcio]

Really nice. Another classically clean file. Love it when the data is so smooth.

Now I'm really confused. Could you tell me what is classically clean about this file?

 

[cvanc]

Now I'm really confused. Could you tell me what is classically clean about this file?

Hehheh my exwife never understood me either :lol:


I guess what I mean is the data, especially the baro data, is very smooth and almost completely devoid of jaggies. It almost looks like it was a simulated flight.

Look around at many of the files posted on this thread. A large percentage of them have very jittery baro data, mostly during descent. I've been wondering aloud as to why this occurs... I suspect it is evidence of the rocket spinning, or maybe tumbling? I'm not suggesting this signifies a Raven problem; I think the data is showing what's actually occuring in flight.

Anyway some data sets are almost completely smooth like this one was.

(and just to be clear my comment was about the file JDcluster posted in msg 139 of this thread)

 

[CarVac]

Anyone know the answers to my questions?

1. What is the voltage doing? and
2. What are p and v?

 

[cvanc]

Anyone know the answers to my questions?

1. What is the voltage doing? and
2. What are p and v?

I'll answer the second one first - I have no idea what you're referring to when you say P and V. I don't see anything like that on my laptop. Post a screengrab, maybe, so we can see what you see?

As for the voltage, something kind of odd is going on. Look at just the raw battery data around apogee. It's normal for the battery voltage to sag when igniters go off. But after the apogee event your battery voltage momentarily *rises* more than 2 volts above the pre-apogee value. Beats me why that happens. I have not seen that before.

All the other voltage data (the 4 outputs) look pretty normal to me?

 

[CarVac]

I don't have my laptop with the FIP on it at the moment, so I can't show a screenshot, but in the box where you can select what variables to graph, at the end of the non-binary variable list there are two variables: p and v. P spikes up and down, and then settles. V consists of periodic spikes with slow downward slides. I'll post a screenshot sometime.

Regarding the battery, there was a little ejection charge intrusion into the av-bay, so it warmed up, but I'm not sure that would cause the battery voltage to jump so dramatically.

 

[Adrian A]

Wow, that's impressive data. The only comparable flight data I've seen is from a 38mm research L.

 

[Adrian A]

I don't have my laptop with the FIP on it at the moment, so I can't show a screenshot, but in the box where you can select what variables to graph, at the end of the non-binary variable list there are two variables: p and v. P spikes up and down, and then settles. V consists of periodic spikes with slow downward slides. I'll post a screenshot sometime.

Regarding the battery, there was a little ejection charge intrusion into the av-bay, so it warmed up, but I'm not sure that would cause the battery voltage to jump so dramatically.

I think that could explain the readings. When there is conductive gas, it could bypass the resistors that reduce the voltage going into the A/D converter. Hot smoke or something like that could explain the temperature readings, also.

 

[CarVac]

Interesting; I didn't think of the gas itself affecting the readings.

With regards to the mysterious 'p' and 'v' channels: here's a screenshot.

 

[cvanc]

Interesting; I didn't think of the gas itself affecting the readings.

With regards to the mysterious 'p' and 'v' channels: here's a screenshot.

View attachment 107387

Huh! I don't see those parameters on either of the 2 laptops I have. My FIP version is dated March 1, 2012. What's yours?