BirdDog

Yes - But which bit of it specifically?

PS - I have posted on the GoPro forum - days gone by - no response. :(

Thanks man...

OK... Basically here is it in a nutshell....

I know the DATA is good - In Quik, it works fine. If I try to load it up in Dashware, it loads the video file, but no data.

I have followed Dashwares tutorial. The one that states to start with "Quick Project" It load the video file, and the tutorial states it should punch out a CSV file - but that does not happen.

If I try and start a new project and load the video file, I get an error stating "No Data Extracted"

Not sure what else I can tell you. I have spent probably 3 hours on it, and I am no numpty - I know what I am doing. Tried a dozen or so files - same result.

Hi Scott,

Yeah man - Been there and done all that. Following Dashware's own tutorials, it fails. GoPro actually stores the data INSIDE the video file, and Dashware is supposed to extract it - yet it doesn't.

It's driving me mad!

Hi Tyson,

Yeah - I am thinking of finding another way to capture data, as the GoPro is proving problematic. Even in their own software Quik, it gets out of sync etc. So might have to do some research.

Yeah, but my rig is all setup for the Gopro - through the intercom etc. :(

No - They are all standard GoPro footage in 720 and 1080.

What happens is this...

If I use Quik, they work. The gauges are crappy, but they work.

So I try to use Dashware, following the tutorials, and it fails. If I use the "Quick Project" it imports the video, and the gauges look like they are there, but no data, and not all gauges. If I start a new project and then go to import a video file, I get an error stating No Data Extracted.

For a company the size of GoPro, the lack of support is amazing! Might be time to dump GoPro and hit up a Garmin Virb.

Hey all,

Just wondering if anyone here has any experience with Dashware with files captured with a Hero5 black.

It's doing my head in!!

Cheers

John

WOW! I really noticed it when I moved my plane. She was down the coast - 34ft elevation. :) Then when I moved her up on the deck, I could feel how the plane reacted differently when it got hot.

There are some really cool apps that will assist pilots. If they don't know, or can't do the crazy calculations, these apps will go a long way to letting you know what you might be in for. Right now my home strip has an AD of over 4000ft. 2000ft more than it should be. Makes a big difference!! Especially if you are weighted up!

Same here mate. I am always looking at DA. My bird currently sits over 2000ft elevation, and when it gets hot, the DA goes up very quickly!

Normally i fly out in mornings or nights. Its leaving the plane out in the sun in plus 40 degrees that is the show stopper.Seen the media on Wellington's ice problem but I find it a nice town so it might be overstated. Little Antarctica makes a good headline. . Really great place to stay up in the old hospital which has been converted into a hotel with lots of personality.

We use Page 2 of this document, and it stays in the logbook. Then replaced when it's all full. We keep them all in the logbooks.

https://members.raa.asn.au/storage/maintenance-form.pdf

ahahah! Yeah Nev.... The boat when it's hot, the plane when it's not!!

I actually prefer not to fly in the heat. I went for a scoot yesterday and basically got bashed the whole way out and back. :(

Thanks Nathan,

Yep! My Motor RPM has direct connection to how fast my prop spins. Might is not constant speed. Just the pitch is adjustable.

Cheers

John

Thanks Nathan,

Great info.

I have been talking direct to ROTAX and they have been a great help, and he put more emphasis on making sure I kept the motor RPM around the 5300 mark. I guess, if as you say, the prop RPM falls with an increase in pitch, so does the motor RPM fight? Hence the need for more power (more throttle)

Roger (Rotax) has recommended 5300 RPM on motor, with 26-27 on the MP. And that's pretty much where she sat last flight, but had to back off, as it got too quick for the conditions I was flying in. It was not full pitch nor WOT, so not sure what she would actually do at full beans! LOL!

Yep - Same. My Maintenance Release is kept in the binder with the logs on a separate sheet, and is looked after by my LAME. :)

The sequence would be...

Take off - Full fine - After climb, reduce power to bring the RPM back from max (Say 5300rpm) Increase prop pitch a couple of clicks. This will bring RPM down as it courses up. So increase throttle to get RPM back in range. Repeat and rinse!

Then once cruising and you want to come down.... Decrease throttle, and reduce prop pitch. As the prop is reduced in pitch, the RPM will increase. Repeat and rinse!

Take off = Full fine.

Landing = full fine.

Cheers

John

Yep. That’s what the rotax guy told me.

Get up and into cruise. Backing to get stable, then course the prop, increase throttle, then prop, then throttle etc etc until ten desired result is achieved.

That was quick!

No probs. If you want the raw Excel let me know. Happy to share.

Hey @cscotthendry,

Thanks for your example. I took some ideas and came up with this. Fits my binder like a charm!

Thanks for sharing

Sportstar Logbook.pdf

It's all good lads. Like I said, Evektor are coming to the party. I have spoken with them and the Authorisation should be with me next week. :)

I agree with illegal mods - just frustrating - hence why I have gone to Evektor.

Yes it. And yes please that would be great. Do you need an email address. I can PM to you.

Cheers

John.

Nice! They look good! Capture all the bits you need.

I am thinking like you, that I will make my own up. More flexibility that way!

Thanks heaps for that!