JPI to FlySto CSV Converter

Upload one or more J.P. Instruments .JPI engine-monitor files and download FlySto.net-compatible CSVs.

Drag and drop one or more .JPI files here, or
Notes

What this tool does

This is a free online converter that turns J.P. Instruments JPI / EDM engine-monitor download files (the .JPI files your engine monitor saves to a USB stick) into a CSV that FlySto.net accepts. FlySto rejects the raw .JPI format, so the analog step most pilots reach for is JPI's own EZTrends desktop software — which is Windows-only, dated, and exports one flight at a time. This tool does the same job in your browser: drag in one or more .JPI files, get FlySto-ready CSVs back. Nothing to install, and it runs on Mac, Windows, Linux, and phones. Your files are processed in memory for a single request and are not stored on the server.

Supported hardware

This converter is tested against EDM-830 downloads. If you fly behind an EDM-830, you are on the tested path.

Other J.P. Instruments monitors — the EDM-700, 730, 800, 900, 930 and 960 — write the same family of JPI download files and may well work, but they are not tested here, so results are not guaranteed. If you try one of these and it converts cleanly (or fails), that feedback is genuinely useful. Where a model isn't listed, treat it as untested rather than supported.

How to convert a JPI file to CSV

1. Download the data from your EDM to USB

On the engine monitor, insert a USB stick and use the unit's Download / Dump function to save the recorded flights. This writes a .JPI file to the stick. (The exact key sequence varies by model and firmware — check your EDM manual.)

2. Convert it here

Drag the .JPI file onto the box at the top of this page (or click to browse), then press Convert. You can select several files at once. A single file downloads as a CSV; multiple files come back as a ZIP with one CSV each.

3. Upload the CSV to FlySto

In FlySto, import the CSV as engine-monitor data. Because the output already matches FlySto's expected column layout, no further editing is needed.

What's in the output CSV

The output follows FlySto's 39-column "V1" template (INDEX through MARK), with a leading tach-summary row showing the start, end, and total engine-on duration for the file. You get one CSV per .JPI, with every flight in that file concatenated and a continuous row index. Engine data — per-cylinder EGT and CHT, RPM, manifold pressure, fuel flow, oil pressure, battery voltage, percent power and more — is written in the units FlySto expects. When the EDM logged a GPS feed, latitude, longitude, altitude and groundspeed are decoded too; samples taken before a GPS lock simply leave those cells blank.

Known limitations

Newer EDM-830 firmware sometimes emits a record the parser can't fully interpret. The converter recovers as much of the affected flight as possible, then moves on to the next one. In practice this affects roughly one flight in fifteen, and only truncates the tail of that single flight — the rest of your data converts normally. OILT (oil temperature) is sensor-dependent: if your aircraft doesn't wire that sensor, the column comes out blank. That's expected, not a fault of the tool.

Frequently asked questions

Do I need EZTrends to use this?

No. EZTrends is J.P. Instruments' Windows-only desktop program. This converter runs in any modern web browser on Mac, Windows, Linux, iOS or Android and reads the same .JPI download file, so no EZTrends install is required.

Are my flight files uploaded or stored anywhere?

The .JPI file's bytes are processed in memory for a single request and are never written to disk on the server. Nothing is retained after the CSV is returned.

Which EDM models are supported?

The converter is tested against EDM-830 downloads. Other units such as the EDM-700, 730, 800, 900, 930 and 960 use the same JPI download format and may work, but they are not tested here, so results are not guaranteed.

Does it work on a Mac?

Yes. Because it is browser-based, it works on macOS, Windows, Linux, iOS and Android with nothing to install.

Why are some GPS columns blank?

GPS latitude, longitude, altitude and groundspeed are decoded only when the EDM had a GPS feed and a satellite lock at the time of the sample. Samples recorded without a lock leave those cells blank.

What format is the output CSV?

It is the 39-column FlySto V1 template with a tach summary row. You get one CSV per .JPI file with all of that file's flights concatenated; upload several files and they come back as a ZIP of CSVs.

Is it free?

Yes. It is completely free to use and open source under the MIT license.

Why did one flight get cut short?

Newer EDM-830 firmware occasionally writes a record the parser cannot fully decode. When that happens the converter keeps everything decoded up to that point and moves on. In practice this affects roughly one flight in fifteen and only truncates the tail of that single flight.

Decoding adapted from 2sec/python-edm, with additional details from openenginedata.org and wannamak/edmtools. Source on GitHub; open source under MIT.