Works with MoTeC M1 · Beta: free for now

Your ECU logs, explained.

Logwise turns your data logs into a plain-English debrief, then coaches you on three things: your driving, the car, and what to take to your tuner.

Open the app Try an example car

Runs in your browser: your logs never leave your computer. Drag and roll coaching is for the strip.

Example data. Logwise's What to do for a drag car on a strip day. You can change these: the front tyres let go on 1 of 3 runs, in 2nd gear, just after the shift, so make a small change in 2nd only; drop the fronts from 22 to 21 psi; then less boost in 2nd on keypad button 2. Take these to your tuner: four findings from the dyno day the week before (a lean spot, knock on cylinder 3, boost creep and heat soak), cylinder 4 exhaust temperature running 64 °C hotter than the others, and fuel pressure dropping under boost. — **Example data**, not a real car: the app's real analysis of logs generated for a fictional 2,000 hp GT-R drag car, on a strip day.

One download, three answers

Drop in the logs from a day at the strip. Logwise finds every full-throttle run and reads the engine's health across every minute it ran.

What happened

Each run as a timing slip

60 ft, 330 ft, 1/8 and 1/4 mile from GPS or ground speed, with wheelspin, the gear it happened in, every shift and boost against aim.

Is the engine OK

Health checks with what it should be

Oil and fuel pressure, mixture, knock, exhaust temperatures, the rev limiter and more. Each says what it should be and how far off it was.

What to do next

A coach that knows whose job it is

What you can change at the track, what stays inside your tuner's limits, and a one-page report for the tuner.

See where the tyres let go

With wheel speed sensors, Logwise compares front and rear axles and checks them against GPS. With one speed sensor, it looks for a jump the car itself can't make.

Example data. Run 2 as a timing slip: 60 ft 1.201 s, 1/4 mile 7.634 s at 299.3 km/h, flagged wheelspin on the fronts in 2nd. The chart shows the front wheels running faster than the rears just after the 1-2 shift. Below, each shift with its rpm, drop and cut time, and boost against aim in each gear. — **A run in detail.** The slip, what happened, the chart that shows it, each shift and boost by gear. *Example data.*

Example data. Health: 2 for your tuner, 1 to watch, everything else good. The fuel checks each say what they should be: fuel pressure should hold steady at about 580 kPa over manifold and dropped 116 kPa (20%) for half a second under boost, marked for the tuner; injector duty should stay under 85% and peaked at 83%. — **A health check every time.** Good, watch it, or take it to your tuner, with what each reading should be. *Example data.*

Sorted by who makes the change

Logwise never writes to your ECU. You or your tuner make every change; Logwise says which of you it's for.

You can change these

Tyre pressures, launch rpm, boost by gear, dash and keypad settings: things you can change at the track.

Inside your tuner's limits

Rev limits and boost ceilings your tuner has set. Logwise checks your logs against them and keeps its advice inside them.

Take these to your tuner

Fuel, ignition and calibration. Logwise explains what it saw and where, and puts it on a one-page report with the chart that proves it.

The event log

Did the change help?

Note what you changed since the last download: tyre pressures, launch rpm, boost, the converter. Logwise compares the runs before and after, corrects ET for the weather, and only says "helped" or "made it worse" when the difference is bigger than the spread between your runs.

Otherwise it says so: not clear yet, do 2 more passes.

Example data. Before (Fri 13 Feb) and after (Sat 14 Feb) a front tyre pressure drop: 60 ft 1.202 to 1.203 s, not clear yet; 330 ft 3.332 to 3.262 s, helped; weather-corrected 1/4 mile ET 7.794 to 7.538 s, helped; wheelspin 0.45 to 0.10 s a run, helped. Got worse since: oil temperature, good to watch. — **Before and after** dropping the front tyres from 22 to 21 psi: the spin is mostly gone. *Example data.*

Drag and roll coaching is for the strip

Launch, traction and boost advice only switches on when you mark a download as a Strip day. Until then you still see every run, the health checks and everything for your tuner.

Logwise won't help make a car faster on the street.

Example data. What to do with Strip day off: the front wheelspin summary, a note that launch and traction advice shows when the download is marked as a strip day, and the items for the tuner. — The same example logs with Strip day off. *Example data.*

Example data. Logwise's Trackside screen on a phone: the last pass in big figures, 1/4 mile 7.481 s, 60 ft 1.204, 1/8 mile 4.893, trap 306.9 km/h; Clean pass, held traction through every gear; runs 1 and 2 below with spin or held. — Trackside, on a phone. *Example data.*

Built for between rounds

Trackside shows the last pass in big figures, what to change before the next one, and the car's health. Sunlight mode turns it black on white for a phone in full sun.

After your first visit the app opens with no internet, so it works in the pits with no reception. Boost, fuel and oil in kPa or psi; °C or °F; km/h or mph.

Your logs never leave your computer

Logwise reads your logs in your browser. Nothing from them is uploaded and there's no account to make. Your cars and profiles stay in the same browser.

What Logwise does collect is short and listed in full: what Logwise collects.

Works with MoTeC M1 today

Logwise reads the .ld logs M1 Tune saves, from M1 ECUs like the M130 and M150. Haltech, Link Engine Management and Emtron are planned, behind the same debrief and coaching.

Which ECUs, and what to log.

Waiting on your ECU, or Logwise Link?

Join the waitlist and we'll email you when Logwise reads your ECU, when the coaching for how you race is ready, and when Logwise Link is ready.

Bring your last download.

Open Logwise, drop in your logs and read the debrief. Free during the beta.

Open the app