JPI EDM log file converter

[xander75]

Howdy xander75,

Thank you for doing all of this! While I have a fair amount of software work experience I'm just running a standard x86 based Windows PC right now without doing much development work and don't care to set up any servers on this PC. I actually was looking to get the CSV files so I can combine them using Alteryx script into a flat file that I use as a database for a Tableau workbook of all my flights and engine data. One of the big limitations with the Savvy platform is the inability to easily compare historical data or get data sets beyond a single flight visualized easily. I.e. I like comparing my carb temp vs. OAT and setting like this picture below using a scatter plot. Tableau lets me create all sorts of interesting graphics and, perhaps most importantly, allow me to filter out bad or otherwise erroneous data.

I'll hang tight until another solution comes along. It takes me about an hour to extract a year's worth of CSV files out of the JPI files. And then I have to filter them for all the instances when the JPI instrument was only on for a ground run or something that I don't want to consider as a true "flight". So that's probably a quicker process than setting up a virtual server to run Grafana, mysql, et al.


View attachment 134885

ah thats very cool @Wize !! yeah the mining that one can do from the engine data is amazing!!
if you like to give it a try, install docker desktop and I'll share you the descriptor file to build a container from that descriptor which is then a fully configured and baked linux distro (about 1Gb), you'll point your browser to localhost:8080 (or whichever port you chose for the apache webserver in the container and you're good to go).

If you don't wanna go through that, you can also share your jpi file(s) with me and I'll convert them to csv's if you like no problem!

cheers!
xander

 

[dave5k]

Really great work, thank you for this. It works great for me on MacOS.

Flysto is another free tool that does flight analysis. (I'd link to it but my account is too new to post links)

They accept JPI data but it must be converted to CSV using the JPI Windows tool. Would be amazing if this tool and Flysto worked together!

 

[Chip Sylverne]

So, newb question. My 830 rx 232 gps data for fuel calculations. When I download my JPI from the thumb drive to EZ trends, all I see is graphs of cht and egt data. When I cat the file, I don't really see anything that even looks like gps data. My JPI sw ver 1.4. Which sw version includes GPS data in the download, or am I missing something?

 

[xander75]

Really great work, thank you for this. It works great for me on MacOS.

Flysto is another free tool that does flight analysis. (I'd link to it but my account is too new to post links)

They accept JPI data but it must be converted to CSV using the JPI Windows tool. Would be amazing if this tool and Flysto worked together!

hey dave5k, awesome to hear!! glad it worked out! I never heard of that tool you mentioned, but if you can share a PM or however so a detail on that one I can reach out to them to consolidate efforts!
cheers!
xander

 

[xander75]

So, newb question. My 830 rx 232 gps data for fuel calculations. When I download my JPI from the thumb drive to EZ trends, all I see is graphs of cht and egt data. When I cat the file, I don't really see anything that even looks like gps data. My JPI sw ver 1.4. Which sw version includes GPS data in the download, or am I missing something?

hey chip, few things that I know: even in the latest fw that I have, the gps data reads zero and is not easy to decode based on what the implementation says it should. for sure you need a gps input on your EDM to have ground speed, LAT/LONG data. I'll review from teh info that I have what fw would include the control blocks data that would include the gps info, but you may be out of luck there. for sure, it shoudl export more then just cht and egt. will get back to you. xander

 

[Chip Sylverne]

hey chip, few things that I know: even in the latest fw that I have, the gps data reads zero and is not easy to decode based on what the implementation says it should. for sure you need a gps input on your EDM to have ground speed, LAT/LONG data. I'll review from teh info that I have what fw would include the control blocks data that would include the gps info, but you may be out of luck there. for sure, it shoudl export more then just cht and egt. will get back to you. xander

Thanks. I know the 830 is getting the 232 data, because I get fuel required to waypoint etc. I do get a red x in fuel to destination should I shoot an missed approach and subsequently go direct to a waypoint that was in the flightplan prior to the approach, rather than add a new destination after the missed. I'm trying to figure out if this is bug in the JPI, or if the 232 signal is actually dropping out.

 

[xander75]

Thanks. I know the 830 is getting the 232 data, because I get fuel required to waypoint etc. I do get a red x in fuel to destination should I shoot an missed approach and subsequently go direct to a waypoint that was in the flightplan prior to the approach, rather than add a new destination after the missed. I'm trying to figure out if this is bug in the JPI, or if the 232 signal is actually dropping out.

do you happen to have other devices connecting to the gps info (like an gpss enabled auto pilot or a electronic flight display like an aspen pfd?) that should confirm if the flight plan is automatically pointing to the next (missed approach) waypoint and back to the hold.
If that is the case then it has to be something in the jpi.

I did some more checking, while unrelated to your situation, the engine data logging for LAT/LONG is problematic, but groundspeed recording should work. also hobbs time is not functioning (unrelated also to gps input obviously)
you may want to open a bug report with jpi, although I havent had much luck getting traction on some of the bugs uncovered due to what sounds like prioritization and resourcing.

x

 

[Chip Sylverne]

do you happen to have other devices connecting to the gps info (like an gpss enabled auto pilot or a electronic flight display like an aspen pfd?) that should confirm if the flight plan is automatically pointing to the next (missed approach) waypoint and back to the hold.
If that is the case then it has to be something in the jpi.

I did some more checking, while unrelated to your situation, the engine data logging for LAT/LONG is problematic, but groundspeed recording should work. also hobbs time is not functioning (unrelated also to gps input obviously)
you may want to open a bug report with jpi, although I havent had much luck getting traction on some of the bugs uncovered due to what sounds like prioritization and resourcing.

x

I do have a gpss as well as an mfd that rx RS232 and those did work normally. I haven't had a chance to get out and fly since, but it may be that I just went "direct to" an earlier flightplan waypoint rather than clearing the "suspend" message after the missed first.I plan on doing some more testing next week to see if I can nail it down.

Thanks for looking into it!