Kai wrote:
Yep, the idea is to use the SD slot as an interface and read out data in real-time and display it on an external device.
Kai,
The data written to the SD card (every second if i am not mistaking) is already displayed on the G1000, so I don't see much interest in displaying them on another external device.
I use an old HP PDA that I carry in my bag to download the data directly from the SD card an then I transfer it to my PC at home.
imagine you could follow your flight on other maps than from Jeppesen, maybe even Google Earth as well as many other free or cheaper charting products. You could even have SVT for free. Imagine you could display the average fuel flow of the last 30-60-120 seconds instead of the ever changing and oscillating readout we see at the moment.
And imagine you could have a touch-screen display where you could quickly make changes to a flightplan on a touchscreen. A lot of other readouts and information would be possible to be displayed and customized.
Kai wrote:Yep, the idea is to use the SD slot as an interface and read out data in real-time and display it on an external device.
How fast would you expect to consume the data? I just want to point out that if the G1000 believes it is writing to an SD card, it may very well buffer a bunch of data up internally and write it out at a slower update rate than what you might want.
I haven't seen a piece of hardware that does what you want, but it's certainly possible in theory.
How fast? That is another good point I haven't thought about. Of course, the faster the better and if you wouldn't see the data of the last few seconds, it wouldn't work. Nevertheless, this is something we'd need to check but I wouldn't know how to find out if we wouldn't try.
If it really doesn't work, we'd have to tab the stream somewhere else, maybe as Rick suggested. But this would all sound like a major intervention with need for STCs. When I get my update done next week, I hope to get some information from the avionics-specialist in the service center.
Please, report bugs on the reports feature if you find any. Just the recent flight of Paul from Oakland to Ogden showed me that there are still bugs in the application. He raced with ground speeds of up to 160 kts in 4 hours, yet, his average speed appeared to be only 108 kts and the total distance covered showed as 435 nms.
It looks the distance is at least 520 nms and we are trying to figure out what produced this bug.
Kai,
I compared my last Flight report (LFQQ EBST) with cirrusreports and the numbers don't match.
The times are OK (I guess that TTime is Tach time)
The distance is 81.25 instead of 95.58 on CR.
The speed is 104.13 instead of 123.13.
The altidude is 5000 instead of 7000 (which altitude are we measuring ?)
Robin wrote:Is there a way of seeing what type of Diamond is on the report. ie trying to compare my DA 40 to other DA 40s
Robin, I'm not sure there is enough information in the log files to actually tell the DA40's apart. But maybe we could post information for each user name so you can tell who has what kind of plane - then you would know which users you wanted to compare with.
Robin wrote:Is there a way of seeing what type of Diamond is on the report. ie trying to compare my DA 40 to other DA 40s
The only DA40 with another engine than yours would be a DA40F, I believe. All other Diamonds have the same Lycoming IO-360-M1A engine or Diesel, of course, but we still have no Diesel-owners who have upped their reports and we still don't even know if the reports page will work for them without any further modifications.
To make it short: any of the files we have there right now should be o.k. for you to compare with your engine.